For me to know, you expect the cloud to keep a record of the relationship?
It would be great if so, but so far in experience, that's really out- of-band information kept in HTML/PDF somewhere.
Not having looked at PaaS too much. THis seems to be a model of multi tenancy as many single tenant platform instances. Is that how Google Apps and others approach the issue? Or, do they support multi- tenant containers?
I think true PaaS is like Google AppEngine, Facebook Apps, where it's a singular instance of "the platform", and you write a small chunk for your portion of it.
I'm calling JBossAS a PaaS, also, though. Even though it's an application, it's fairly useless as-is. When the chunk you've written in a .war/.ear, you just want a j2ee platform to deploy it upon. That could be any one-of-many. So, trying to make it easy to launch a JEE platform, based upon JBoss of course.
Rebundling here seems very EC2/Stateless oriented. Is that the model we want to address?
If I'm building a derivative work from some previously published thing, I want to be able to snapshot my combined resulting product. Imaging taking the RHT CSB, adding a few apps for your department/ group, and then republishing that for use by new hires. That's the sort of additive use-case I'm aiming for. Trying to minimize the steps (manual or otherwise) from 0-to-Go. "Boot up CSB+ThincrustDev image" is easier than "boot up CSB, install these X packages, configure per instructions.html".
Though, could be a bad use-case. Just throwing it out there.
-Bob