search

redhat-cip / spinalstack-doc

Official manual of Spinal Stack
Apache License 2.0
3 stars 11 forks source link

How jenkins intervenes in the deployment, with the 5 steps? #14

Open marcosgm opened 10 years ago

marcosgm commented 10 years ago

I don't fully understand the involved pieces described here: http://spinalstack.enovance.com/en/latest/deploy/configuration.html#during-the-configuration

I thought Ansible was moving the system from one step to another, but it seems that is actually jenkins by checking serverspec to be OK, then launching the next step (how? shell? ansible jobs?) . But we do use Ansible via jenkins for upgrades, right? http://spinalstack.enovance.com/en/latest/deploy/upgrade.html

I haven't found any reference of this in the code (via grep)

Please develop further (maybe refer to the improved Architecture as described in another bug)

lebauce commented 10 years ago

Regarding the deployment, Jenkins task is just to run the "configure.sh" script of the config-tools repository. That is this script that runs Puppet, checks serverspec and then moves to the next step.

You can see the YAML description of the jobs in the https://github.com/enovance/jjb-openstack repository (file puppet.yaml of jjb-openstack)

Ansible is used mainly for the upgrade process : Jenkins runs ansible, then configure.sh (as in the deployment phase), then runs ansible again (file upgrade.yaml of jjb-openstack).

----- Mail original ----- De: "Marcos Garcia" notifications@github.com À: "enovance/spinalstack-doc" spinalstack-doc@noreply.github.com Envoyé: Mercredi 8 Octobre 2014 22:38:27 Objet: [spinalstack-doc] How jenkins intervenes in the deployment, with the 5 steps? (#14)

I don't fully understand the involved pieces described here: http://spinalstack.enovance.com/en/latest/deploy/configuration.html#during-the-configuration

I though Ansible was moving the system from one step to another, but it seems that is actually jenkins by checking serverspec to be OK, then launching (how?) the next step

I haven't found any reference of this in the code (via grep)

Please develop further (maybe refer to the improved Architecture as described in another bug)

Reply to this email directly or view it on GitHub: https://github.com/enovance/spinalstack-doc/issues/14

marcosgm commented 10 years ago

Thanks! I appreciate the explanation. Now we just need to put it in the documentation.

I will go ahead and add some bits, but overall I think the overall explanation on how stuff works for installation and upgrades are not clear. I've been asked similar questions like this a dozen times this week, by people trying spinalstack at RedHat.