search

redhat-openstack / tripleo-quickstart

Ansible roles for setting up TripleO virtual environments and building images
16 stars 15 forks source link

As a consumer of tripleo-quickstart, I want to run my own automation from some defined stopping points. #12

Closed trown closed 8 years ago

trown commented 8 years ago

Initial idea for the 'breakpoints':

  1. undercloud booted
  2. undercloud install complete
  3. ready to run deploy
  4. ready to run validation
  5. the kitchen sink

CI would then use different settings YAMLs to define the different scenarios, all of which would be run against the full deploy and test scenario.

trown commented 8 years ago

This could be done via tags, or via extra playbooks.

The breakpoints above would translate to the following using tags:

  1. undercloud booted = --tags untagged
  2. undercloud install complete = --tags "untagged, undercloud-scripts, undercloud-install"
  3. ready to run deploy = --tags "untagged, undercloud-scripts, undercloud-install, undercloud-post-install"
  4. ready to run validation = --skip-tags "overcloud-validate"
  5. the kitchen sink - everything
trown commented 8 years ago

We could have two more "breakpoints" too.

  1. undercloud booted w/ all scripts needed for install but not run= --tags "untagged, undercloud-scripts"
  2. undercloud booted w/ all scripts needed for install, deploy, and test, but not run= --tags "untagged, undercloud-scripts, overcloud-scripts"
trown commented 8 years ago

I created https://review.gerrithub.io/#/c/265466 to address this issue.