<div dir="ltr">I think the ability to migrate instances and projects between clouds is very valid and applies to other use cases besides avoiding an upgrade.<div><br></div><div>The instance migration process that Tim describes is one that we use, too. It's relatively easy for end-users and requires no admin intervention.</div>
<div><br></div><div>Project migration is a very interesting concept. I'd imagine it would include things like users, key pair entries, security groups, networks, etc.</div><div><br></div><div>I agree with Joshua about why it's bad to avoid upgrades. I've seen a ton of effort go into making in-place upgrades possible and safe and it's very much appreciated. I upgraded an environment from Folsom to Grizzly a few weeks ago and none of the users noticed it happened. </div>
<div><br></div><div>I definitely don't recommend blindly doing "apt-get dist-upgrade" on a production environment, though :)</div><div><br></div><div>On the flip side, sometimes it can be easier to just migrate rather than upgrade in-place. I think where the line is drawn with that decision varies from person to person.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 24, 2013 at 2:56 PM, Joshua Harlow <span dir="ltr"><<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>I agree its not simple (from experience),</div>
<div><br>
</div>
<div>There is a difference though between 'simpler for now' and the 'right thing to do',</div>
<div><br>
</div>
<div>If software doesn't support the right thing to do ('upgrade', 'dist-upgrade' - or yum equivalent) then the community needs to make that work (and stop with new features).</div>
<div><br>
</div>
<div>Otherwise the community is in a whole world of trouble. If openstack is to make the life of operations & other people better and the only way to operate it is to build new regions, then something feels backwards in this equation.</div>
<div><br>
</div>
<div>IMHO bypassing the problem is not a long-term solution (and is not healthy for openstack to even recommend this). </div>
<div><br>
</div>
<div>I don't even think its a short-term solution honestly since building a new region costs $$ and downtime. Who wants to do that every 6 months, I can surely tell u I don't :)</div>
<div><br>
</div>
<span>
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span>Martinx - ジェームズ <<a href="mailto:thiagocmartinsc@gmail.com" target="_blank">thiagocmartinsc@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, October 24, 2013 1:17 PM<br>
<span style="font-weight:bold">To: </span>Joshua Harlow <<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>><br>
<span style="font-weight:bold">Cc: </span>Tim Bell <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>>, Alexander Stellwag <<a href="mailto:openstack@stellwag.net" target="_blank">openstack@stellwag.net</a>>, "<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a>"
<<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack] Migrate instances/tenants between clouds<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<div dir="ltr">I do not even want to try to upgrade my system...
<div><br>
<div>I know that DPKG is awesome and handle system upgrades carefully but, sounds more simpler to just build a new Region...</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>This doesn't sound trivial (like `apt-get update ; apt-get dist-upgrade`):</div>
<div><br>
</div>
<div> <a href="http://www.openstack.org/summit/portland-2013/session-videos/presentation/getting-from-grizzly-to-havana-a-devops-upgrade-pattern" target="_blank">http://www.openstack.org/summit/portland-2013/session-videos/presentation/getting-from-grizzly-to-havana-a-devops-upgrade-pattern</a></div>
<div><br>
</div>
<div>Don't you think!?</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 24 October 2013 17:48, Joshua Harlow <span dir="ltr">
<<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Whatever happened to doing in-place upgrades?<br>
<br>
Has that been problematic for u, are people just not doing it? If they are<br>
avoiding it, why?<br>
<br>
Shouldn't just going from folsom->havana work, if not, why not; it worries<br>
me that this isn't priority #0 if it doesn't work.<br>
<div>
<div><br>
On 10/24/13 10:51 AM, "Tim Bell" <<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>> wrote:<br>
<br>
><br>
>Have you tried<br>
><br>
>- snapshot<br>
>- glance download of the snapshot<br>
>- glance upload of the snapshot to new instance<br>
>- boot from snapshot<br>
><br>
>The process we use at CERN is documented at<br>
><a href="http://information-technology.web.cern.ch/book/cern-cloud-infrastructure-u" target="_blank">http://information-technology.web.cern.ch/book/cern-cloud-infrastructure-u</a><br>
>ser-guide/images/migrating-using-images<br>
><br>
>This could be a good technique to document in the standard CERN openstack<br>
>user guide.<br>
><br>
>BTW, this does increase the storage in your glance server since you'll<br>
>loose any commonality between multiple images. So, make sure you've lots<br>
>of space on Glance.<br>
><br>
>Tim<br>
><br>
>> -----Original Message-----<br>
>> From: Alexander Stellwag [mailto:<a href="mailto:openstack@stellwag.net" target="_blank">openstack@stellwag.net</a>]<br>
>> Sent: 24 October 2013 16:53<br>
>> To: <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>> Subject: [Openstack] Migrate instances/tenants between clouds<br>
>><br>
>> Hi stackers,<br>
>><br>
>> we're looking for a tool / script / blueprint to migrate instances or<br>
>>even complete tenants between multiple installations of OpenStack<br>
>> (possibly running different versions).<br>
>><br>
>> I searched around the net but didn't find anything appropriate. Is any<br>
>>of you aware of such a tool?<br>
>><br>
>> The current use-case is a migration from a folsom/nova-network based<br>
>>installation into our new havana/neutron based cloud. It is not<br>
>> necessary to migrate instances and volumes online but it should work at<br>
>>least semi-automatically to make it usable in large deployments.<br>
>><br>
>> Any hints would be greatly appreciated.<br>
>><br>
>> Cheers,<br>
>> Alex<br>
>> --<br>
>> Alexander Stellwag<br>
>> Deutsche Telekom AG Products & Innovation Infrastructure Design<br>
><br>
><br>
>_______________________________________________<br>
>Mailing list:<br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
>Unsubscribe :<br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div></div></span>
</div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Joe Topjian<div>Systems Architect</div><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div>
</div>