SharePoint 2013 Multi-tenant Feature Packs

Question

I have not seen any information in regards to multi-tenancy feature packs for SharePoint 2013. Currently it seems, with the new end user licencing, when you install the Enterprise bits you can license a user for either Standard or Enterprise but not
Foundation. In SharePoint 2010 you could use the Enterprise bits then create defined feature packs to give a site collection Foundation, Standard or Enterprise features. Do updated defined feature packs exist for 2013? 
There is mention of them here http://www.harbar.net/articles/sp2013mt.aspx 
"Feature Packs provide the ability to constrain the Features available for a given tenant. The fundamental capability
isn’t changed in any way here, but of course the Features in the product have. Thus the old Feature Pack definitions for SKUs are no longer valid. A new set of feature pack definitions are required encompassing all of the new Features in SharePoint 2013."
But nothing else anywhere on the net, anyone have any ideas?

Answer 1

Hi all,
I thought I'd give an update.  I too have worked through official channels and I believe I'm making progress but not a solution unfortunately.  When you run Get-SPFeature, you get 409 different features.  One thing I noticed, was the features
ending with Stapler that Spence didn't add to his foundation features suggests that adding these could be erroneous.  This led me to believe that my ignorance in the above message was bliss and that my idea was not going to fly.  Take for example
this:
AutohostedAppLicensing
AutohostedAppLicensingStapling
So is AutohostedAppLicensingStapling a Standard or Enterprise Feature, or something internal that should not be added as it gives bad results?  What about the others I don't find?
Then I posed the question - what do the ID's with EDU* in them mean?  They don't exist in product info - perhaps it's education specific SKU's?  Does that expose customers to use SharePoint for Internet Sites without the SKU as we assume Enterprise
would be the baseline for all 409 features and we work our way back?
Or even this - MS Access Services is a feature, yet there are 10 Feature ID's associated with it.  With Exchange, there are PS commands that refer to MS Internal only and for O365 use only.  What
if the 209 features Microsoft sent me as a descriptor for onprem cannot correlate to the 409 Get-SPFeature ID's I have in my bag that render my farm useless?
I've also done research around the net and it looks like everyone went the inefficient, non-multitenant way - that is, either do foundation and try to compete with O365, or offer dedicated VM farms for clients with Standard or Enterprise installs and centralise
the SQL back-end.
Surely noone has done true multitenant... Have they?
Question.  If i provision a client with no -Featurepack ID, do they get nothing or the default which is Enterprise Edition?  I'd presume I will get nothing or an error for not specifying a switch but I would have to build another environment to
test.... which brings me to my last point.  Based on the way Std and Ent can be enabled for on-prem customers on an individual basis and I installed Standard edition on its own VM then enumerated the Get-SPFeature cmdlet, surely I'd see all the features,
not just the standard edition install features.  right?  If not then I'll build it, enumerate the list and my 2013 Feature pack is sorted.
The biggest fear I have on this is going it alone and if I stuff up, having a non-compliant licensing solution for every user on the system and MS banging down my door for noncompliance on something they didn't provide guidance on in the first place.
Jason. 
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au