← Back to team overview

fuel-dev team mailing list archive

FUEL feature request(--no-op or --dry-run)

 

Hello.

For development and debugging propose it would be nice if Fuel can perform
all deployment steps without actually deploy it:

   1. provisioning;
   2. pre deployment steps (sync repositories and puppet modules, generate
   and upload ssh keys, sync time);
   3. upload Astute.yaml for each role (and support multi roles case).

As result we will get cluster which ready for debugging and development
proposes.

Possible solution:

   - add new cluster parameter "dry_run" like "debug";
   - run all pre deploy and deployment steps;
   - upload astute.yaml for each role separately (/etc/<role>.yaml) and do
   symbolic to /etc/astute.yaml (https://review.openstack.org/#/c/124728/)

Current workflow:

We can do it by hands using fuel-cli or UI, but this step require to spoil
site.pp. Also without https://review.openstack.org/#/c/124728/ we loosing
multi roles support and this workaround will not work with granular
deployment because no single site.pp exists.

Unresolved issues:

   - 'dry run' in web UI;
   - final status for node and cluster in case of dry run deployment;
   - small separate action in fuel-cli available for provisioned nodes only
   or as special parameter for deploy action like debug.

Follow ups