yahoo-eng-team team mailing list archive

[Jesse Pretorius <jesse.pretorius@xxxxxxxxxxxxxxx>]

Public bug reported:

In the automation of deployments and upgrades it would be useful to be
able to check whether there are any database actions outstanding so that
the action can be determined and executed.

Effectively I'm thinking something along the lines of this experience:

Operator (or automation tool) executes: keystone-manage db_sync --check

The tool checks the db state and returns whether there are any
migrations to execute (ie --expand), whether there is a --migrate
outstanding, whether there is a --contract outstanding, or any
combination of the above. If there is nothing left to do, that should be
reported too.

Ideally the output should take two forms:

1 - stdout messages... obviously this is useful when executing this by hand
2 - return codes... this is very useful when executing via automation tooling

The return codes need to be actionable - ie I must know which actions
are required based on the return code with no ambiguity.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1642212

Title:
  RFE: keystone-manage db_sync --check

Status in OpenStack Identity (keystone):
  New

Bug description:
  In the automation of deployments and upgrades it would be useful to be
  able to check whether there are any database actions outstanding so
  that the action can be determined and executed.

  Effectively I'm thinking something along the lines of this experience:

  Operator (or automation tool) executes: keystone-manage db_sync
  --check

  The tool checks the db state and returns whether there are any
  migrations to execute (ie --expand), whether there is a --migrate
  outstanding, whether there is a --contract outstanding, or any
  combination of the above. If there is nothing left to do, that should
  be reported too.

  Ideally the output should take two forms:

  1 - stdout messages... obviously this is useful when executing this by hand
  2 - return codes... this is very useful when executing via automation tooling

  The return codes need to be actionable - ie I must know which actions
  are required based on the return code with no ambiguity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1642212/+subscriptions