Jump to: navigation, search

Difference between revisions of "Nova-Cells-v2"

(Nova Cells v2)
(Nova Cells v2)
Line 12: Line 12:
 
* The deployment/upgrade process needs to be documented in more than just the release notes.
 
* The deployment/upgrade process needs to be documented in more than just the release notes.
 
** dansmith was going to work on a blog post to start this.
 
** dansmith was going to work on a blog post to start this.
 +
** On a side note, we should also have man pages for the cell_v2 commands because there is confusion around the inputs and outputs and how return codes should be treated, i.e. is 1 an error or not?
 
** alaski's older docs patch (which is probably out of date now but might be useful) is here: https://review.openstack.org/#/c/267153/
 
** alaski's older docs patch (which is probably out of date now but might be useful) is here: https://review.openstack.org/#/c/267153/
 
* Integrate the 'nova-status upgrade check' CLI into the CI/QA system (grenade).
 
* Integrate the 'nova-status upgrade check' CLI into the CI/QA system (grenade).

Revision as of 16:39, 13 January 2017

Nova Cells v2

Bugs

TODOs

Open Questions

  • Should the computes self-register with a cell when the compute_nodes record is created from the ResourceTracker? https://review.openstack.org/#/c/369634/
  • Why can't we create an empty cell, i.e. a cell mapping with no computes? This is a fresh-install scenario.

Manifesto

http://docs.openstack.org/developer/nova/cells.html#manifesto

Testing

https://etherpad.openstack.org/p/nova-cells-testing

DB Table Analysis

https://etherpad.openstack.org/p/nova-cells-table-analysis

Scheduling requirements

https://etherpad.openstack.org/p/nova-cells-scheduling-requirements

Code Review

References