<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.StylE-mailovZprvy18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=CS link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In our cloud, we offer the possibility to reinstall the same or another OS on a VPS (Virtual Private Server). Unfortunately, we couldn</span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>’</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>t use the rebuild function because of the VPS‘s use of Cinder for root disk. We create a new instance and inject the same User Data so that the new instance has the same password and key as the last one. It also has the same name, and the same floating IP is attached. I believe it even has the same IPv6 through some Neutron port magic.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>BTW, you wouldn’t believe how often people use the Reinstall feature.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Tomas from Homeatcloud<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Belmiro Moreira [mailto:moreira.belmiro.email.lists@gmail.com] <br><b>Sent:</b> Wednesday, October 04, 2017 5:34 PM<br><b>To:</b> Chris Friesen<br><b>Cc:</b> openstack-operators@lists.openstack.org<br><b>Subject:</b> Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>In our cloud rebuild is the only way for a user to keep the same IP. Unfortunately, we don't offer floating IPs, yet.<o:p></o:p></p></div><div><p class=MsoNormal>Also, we use the user_data to bootstrap some actions in new instances (puppet, ...).<o:p></o:p></p></div><div><p class=MsoNormal>Considering all the use-cases for rebuild it would be great if the user_data can be updated at rebuild time.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Oct 4, 2017 at 5:15 PM, Chris Friesen <<a href="mailto:chris.friesen@windriver.com" target="_blank">chris.friesen@windriver.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>On 10/03/2017 11:12 AM, Clint Byrum wrote:<o:p></o:p></p><p class=MsoNormal>My personal opinion is that rebuild is an anti-pattern for cloud, and<br>should be frozen and deprecated. It does nothing but complicate Nova<br>and present challenges for scaling.<br><br>That said, if it must stay as a feature, I don't think updating the<br>user_data should be a priority. At that point, you've basically created an<br>entirely new server, and you can already do that by creating an entirely<br>new server.<o:p></o:p></p><p class=MsoNormal><br>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.<span style='color:#888888'><br><br><span class=hoenzb>Chris</span></span><o:p></o:p></p><div><div><p class=MsoNormal><br><br><br>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>