Bug 1312342 - Deployment configuration for "cell of one"
Summary: Deployment configuration for "cell of one"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-26 13:28 UTC by Stephen Gordon
Modified: 2019-09-09 15:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-04 15:33:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Stephen Gordon 2016-02-26 13:28:13 UTC
Description of problem:

Starting with Mitaka Cells V2 is (apparently) at the point that deployments will be a cell of one. This carries with it some additional setup tasks, particularly creating the separate nova api database.

We (nova) team need to document exactly what is required here and feed it into tripleo and as a result OSP-D.

Version-Release number of selected component (if applicable):

Red Hat OpenStack Platform 9/"Mitaka"

Comment 2 Stephen Gordon 2016-02-26 13:33:19 UTC
Relevant upstream docs patch: https://review.openstack.org/#/c/284803/

Comment 3 Stephen Gordon 2016-02-26 14:07:18 UTC
As part of this we need to confirm:

(1) Is this absolutely mandatory to do in Mitaka.
(2) What is the upgrade process for existing users, how does the new API DB get populated?

Comment 4 Stephen Gordon 2016-02-26 14:10:50 UTC
Looks like this may already be actioned in TripleO:

https://review.openstack.org/#/c/276790/

Comment 5 Dan Smith 2016-02-26 14:31:46 UTC
I believe the only thing that will be required will be create, configure and sync the new database. If we don't land the flavor migration in Mitaka, then there won't really be any additional upgrade steps. All three steps can be done in Liberty before the upgrade, and then we just do the additional api_db sync alongside the normal db sync when we roll forward.


Note You need to log in before you can comment on or make changes to this bug.