From 15a4f1d4d1406f4de76e148bd35e354f2dad9069 Mon Sep 17 00:00:00 2001 From: John Fulton Date: Tue, 17 Oct 2017 14:20:28 -0400 Subject: [PATCH] Update upgrade documentation with non-container support plans This change was discussed during the TripleO meeting on 17 Oct 2017 [1] [1] http://eavesdrop.openstack.org/meetings/tripleo/2017/tripleo.2017-10-17-14.00.html Change-Id: I6cbf84dff8830a28486358a11167a097082426c2 --- doc/source/install/post_deployment/upgrade.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/source/install/post_deployment/upgrade.rst b/doc/source/install/post_deployment/upgrade.rst index b1c97d33..56743e58 100644 --- a/doc/source/install/post_deployment/upgrade.rst +++ b/doc/source/install/post_deployment/upgrade.rst @@ -136,6 +136,12 @@ mechanism and the steps are invoked with the same cli. A big difference however is that after upgrading to Pike most of the overcloud services will be running in containers. +.. note:: + + Upgrades to Pike or Queens will only be tested with containers. Baremetal + deployments, which don't use containers, will be deprecated in Queens and + have full support removed in Rocky. + The operator starts the upgrade with a ``openstack overcloud deploy`` that includes the major-upgrade-composable-steps.yaml_ environment file (or the docker variant for the `containerized upgrade to Pike`__)