diff options
| author | Adam Gandelman <adamg@ubuntu.com> | 2015-04-08 14:36:14 -0700 |
|---|---|---|
| committer | Chris Krelle <nobodycam@gmail.com> | 2015-04-09 09:30:53 -0700 |
| commit | 995999730ac563d61b0c8357e3796ff874df7a69 (patch) | |
| tree | 43dc48fb06aa27c6f566ae5027233df4879f1b56 | |
| parent | 631e284c0d5256fd69de6520e0b359da54384891 (diff) | |
| download | ironic-995999730ac563d61b0c8357e3796ff874df7a69.tar.gz | |
Add notes about upgrading juno->kilo to docs
This adds a new section to docs to outline special considerations
for the juno -> kilo upgrade, specifically around how to upgrade
Nova and Ironic together.
Change-Id: Idf7efb7438217f5132f6a8581c591a04c76b1abb
Closes-bug: #1433727
| -rw-r--r-- | doc/source/deploy/upgrade-guide.rst | 36 | ||||
| -rw-r--r-- | doc/source/index.rst | 1 |
2 files changed, 37 insertions, 0 deletions
diff --git a/doc/source/deploy/upgrade-guide.rst b/doc/source/deploy/upgrade-guide.rst new file mode 100644 index 000000000..2ce9e0952 --- /dev/null +++ b/doc/source/deploy/upgrade-guide.rst @@ -0,0 +1,36 @@ +.. _upgrade-guide: + +===================================== +Bare Metal Service Upgrade Guide +===================================== + +This document outlines various steps and notes for operators to consider when +upgrading their Ironic-driven clouds from previous versions of OpenStack. + +The Ironic service is tightly coupled with the Ironic driver that is shipped +with Nova. Currently, some special considerations must be taken into account +when upgrading your cloud from previous versions of OpenStack. + +Upgrading from Juno to Kilo +=========================== + +When upgrading a cloud from Juno to Kilo, users must ensure the Nova +service is upgraded prior to upgrading the Ironic service. Additionally, +users need to set a special config flag in Nova prior to upgrading to ensure +the newer version of Nova is not attempting to take advantage of new Ironic +features until the Ironic service has been upgraded. The steps for upgrading +your Nova and Ironic services are as follows: + +- Edit nova.conf and ensure force_config_drive=False is set in the [DEFAULT] + group. Restart nova-compute if necessary. +- Install new Nova code, run database migrations +- Install new python-ironicclient code. +- Restart Nova services. +- Install new Ironic code, run database migrations, restart Ironic services. +- Edit nova.conf and set force_config_drive to your liking, restaring + nova-compute if necessary. + +Note that during the period between Nova's upgrade and Ironic's upgrades, +instances can still be provisioned to nodes, however, any attempt by users +to specify a config drive for an instance will cause error until Ironic's +upgrade has completed. diff --git a/doc/source/index.rst b/doc/source/index.rst index a3339207d..7ea533fdb 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -57,6 +57,7 @@ Overview deploy/user-guide deploy/install-guide + deploy/upgrade-guide deploy/drivers deploy/cleaning |