[Openstack-operators] OSA upgrading Ubuntu14.04 Newton to Ubuntu16.04 Ocata
Grant Morley
grant at absolutedevops.io
Wed Oct 4 15:03:46 UTC 2017
Hi Amy,
Many thanks for this, pleased to know that it is doable :) - We will
test this on our dev environment first to see if there are any issues or
not.
Will be sure to join the #openstack-ansible channel if we get stuck.
Thanks again,
Grant
On 04/10/17 15:56, Amy Marrich wrote:
> Hi Grant,
>
> We actually have the process documented here:
>
> https://etherpad.openstack.org/p/osa-newton-xenial-upgrade
>
> It does make a few assumptions so make sure you meet them before
> starting. Please join us on Freenode in the #openstack-ansible channel
> and we'll give you a hand if we can.
>
> Thanks,
>
> Amy (spotz)
>
> On Wed, Oct 4, 2017 at 9:42 AM, Grant Morley <grant at absolutedevops.io
> <mailto:grant at absolutedevops.io>> wrote:
>
> Hi All,
>
> Just have a quick question regarding upgrading from Newton to
> Ocata using OSA. We have a small installation ( 4 compute. 3
> management, 2 network and some Ceph storage nodes ) And we are
> looking to upgrade from Ubuntu 14.04 Newton to Ubuntu 16.04 Ocata.
>
> Does anyone have any good tips on how to do this at all? We are
> not sure whether it is best to decommission a single node at a
> time, upgrade that to Ubuntu 16.04 and then get Ocata installed
> onto that. Or whether there is a better method at all?
>
> We are conscious that if we bootstrap our ansible deployer machine
> for Ocata, it will then not be able to manage the nodes that are
> running 14.04 Newton we assume?
>
> Another thing we were thinking was to possibly get some more kit
> and just install Ocata from scratch on that and start to migrate
> customers over, but again we assume would need a separate deployer
> to do so?.
>
> We would prefer to be able to upgrade both the OS for Ubuntu and
> Openstack to Ocata using our current set up and just wondered if
> this was even possible with OSA? Unfortunately we do not have the
> budget to simply keep on getting more and more kit, so we have to
> be quite tactile about how we do things.
>
> We are going to test this on our dev environment and see what
> breaks, but just wondered if anyone here has come across this
> already and suffered the pain :)
>
> Any suggestions would be much appreciated.
>
> Many thanks,
>
> --
> Grant Morley
> Senior Cloud Engineer
> Absolute DevOps Ltd
> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
> www.absolutedevops.io <http://www.absolutedevops.io/>
> grant at absolutedevops.io <mailto:grant at absolutedevops.io> 0845 874
> 0580
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> <mailto:OpenStack-operators at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
>
>
--
Grant Morley
Senior Cloud Engineer
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io <http://www.absolutedevops.io/>
grant at absolutedevops.io <mailto:grant at absolutedevops.io> 0845 874 0580
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20171004/ae2dc102/attachment.html>
More information about the OpenStack-operators
mailing list