[openstack-dev] [trove] Configuration API BP

Michael Basnight mbasnight at gmail.com
Wed Oct 2 16:39:38 UTC 2013

On Oct 2, 2013, at 9:21 AM, Craig Vyvial wrote:

> If a configuration is updated that is attached to N instances then those instances will be updated with the configuration overrides. This will keep the configuration n-sync[hah 90s boy band reference] with instances that have it attached. I'm not sure that this is really a "confusing situation" because you are updating the configuration key/values. This will not update the UUID of the configuration because we are not trying to make the changes like a sub-versioned system. 

ok if thats the expected behavior, im ok with that. ByeByeBye with the other options ;)

> 'configuration' is a resource that can be applied only to instances. Making it a sub-resource of '/instances' is an option but does that warrant it always being tied to an instance?


> Each configuration is unique to a tenant and therefore doesnt allow a reseller to create a tweaked out config. I see value in allowing resellers to do this but currently they can update the templates that are used in the system.

I mean a single tenant being that reseller. He has 1 template he applies to all his db instances for his customers, which he supports outside of trove.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131002/acccc134/attachment.pgp>

More information about the OpenStack-dev mailing list