Logical puzzles in tripleo CLI

[Sergii Golovatiuk]

At the moment the workflow is

openstack overcloud container image prepare \
  --output-images-file container_images_13.yaml \
  ...

which prepares a a config which can be used for populating local registry.

Then, the second step is

openstack overcloud container image upload \
  --config-file container_images_13.yaml \
  ...

which consumes the config from step one but has different key name (--config-file)

Then, the third step is

openstack overcloud container image prepare \
  --output-env-file container_env_13.yaml \

though it can be run as

openstack overcloud container image prepare \
  --output-env-file container_env_13.yaml \
  --config-file <name>

which should be prohibited as it puzzles operator, as he will generate config for 'openstack overcloud upgrade prepare' as well as container image file for uploading to local registry. However, the third step should be renamed as

openstack overcloud container env prepare \

which will generate env file for 'openstack overcloud upgrade prepare'

Also all keys should be unified as

openstack overcloud container image prepare \
  --images-file container_images_13.yaml \

openstack overcloud container image upload \
  --images-file container_images_13.yaml

openstack overcloud container env prepare
  --env-file <name>.yaml

openstack overcloud upgrade prepare \
  --env-file <name>.yaml

[Sergii Golovatiuk (sgolovatiuk)]

As a result,

openstack overcloud container env prepare

may be extended to generate config automatically scanning specified registry.

[Marios Andreou (marios-b)]

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]