That was indeed a rather long (and insightful) thread on the topic. It sounds like there are still some healthy discussions worth having on the subject -- either exploring your [potentially superseding] proposal, or minimally rounding out the existing server group API to support "add existing VM"  and "remove VM" -- I think these would make it a lot more usable (I'm thinking of the poor cloud administrator that makes a mistake when they boot an instance and either forgets to put it in a group or puts it in the wrong group -- it's square 1 for them)?
Is this queued up as a discussion point for Paris? If so, count me in! Thanks, Joe On Mon, Aug 25, 2014 at 11:08 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 08/25/2014 11:31 AM, Joe Cropper wrote: >> >> Thanks Jay. Those are the same types of questions I was pondering as >> well when debating how someone might use this. I think what we have >> is fine for a first pass, but that's what I was poking at... whether >> some of the abilities to add/remove members dynamically could exist >> (e.g., I no longer want this VM to have an anti-affinity policy >> relative to the others, etc.). > > > I guess what I was getting at is that I think the whole interface is flawed > and it's not worth putting in the effort to make it slightly less flawed. > > Best, > -jay > > >> - Joe >> >> On Mon, Aug 25, 2014 at 10:16 AM, Jay Pipes <jaypi...@gmail.com> wrote: >>> >>> On 08/25/2014 11:10 AM, Joe Cropper wrote: >>>> >>>> >>>> Hello, >>>> >>>> Is our long-term vision to allow a VMs to be dynamically added/removed >>>> from a group? That is, unless I'm overlooking something, it appears >>>> that you can only add a VM to a server group at VM boot time and >>>> effectively remove it by deleting the VM? >>>> >>>> Just curious if this was a design point, or merely an approach at a >>>> staged implementation [that might welcome some additions]? :) >>> >>> >>> >>> See here: >>> >>> http://lists.openstack.org/pipermail/openstack-dev/2014-April/033746.html >>> >>> If I had my druthers, I would revert the whole extension. >>> >>> -jay >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStackfirstname.lastname@example.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStackemail@example.com >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev