In our cloud rebuild is the only way for a user to keep the same IP. Unfortunately, we don't offer floating IPs, yet. Also, we use the user_data to bootstrap some actions in new instances (puppet, ...). Considering all the use-cases for rebuild it would be great if the user_data can be updated at rebuild time.
On Wed, Oct 4, 2017 at 5:15 PM, Chris Friesen <chris.frie...@windriver.com> wrote: > On 10/03/2017 11:12 AM, Clint Byrum wrote: > > My personal opinion is that rebuild is an anti-pattern for cloud, and >> should be frozen and deprecated. It does nothing but complicate Nova >> and present challenges for scaling. >> >> That said, if it must stay as a feature, I don't think updating the >> user_data should be a priority. At that point, you've basically created an >> entirely new server, and you can already do that by creating an entirely >> new server. >> > > If you've got a whole heat stack with multiple resources, and you realize > that you messed up one thing in the template and one of your servers has > the wrong personality/user_data, it can be useful to be able to rebuild > that one server without affecting anything else in the stack. That's just > a convenience though. > > Chris > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
