Hello,
On 11/16/2016 07:52 AM, Tristan Cacqueray wrote:
Hello folks,
here is a break down of the shell scripts in SF code base:
A) Image building
* Build cache
* Build image
* Logic to know when to build cache or image
B) Functional test runner
* Call image building
* Deploy image
* Do action such as turn off/turn on, run backup, ...
C) Configuration script (sfconfig.sh)
* Generate secrets
* Generate playbook/inventory
* Call configuration playbook
D) Generated script by sfconfig (/root/*.sh)
* Create user
* Set acls
E) Random scripts such as build doc, publish and fetch image
It seems like each of above point could be replaced by a better tool:
A) Use DIB
I agree with that point, but what about the upgrade process with only an
image build with DIB instead edeploy ? Not sure will be able to use the
same upgrade path.
B and E) Rewrite in Ansible playbooks (which is more zuulV3 friendly)
+1
C) A python based script that would subprocess ansible commands
Why do not use only ansible ? What is the benefit to use a python script ?
Nico
D) Those are remaining legacy stuff from the puppet era that could
easily be integrated into SF roles.
Well if you thing that's worthy, then let's create stories and address
above point!
Yours,
-Tristan
_______________________________________________
Softwarefactory-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/softwarefactory-dev
_______________________________________________
Softwarefactory-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/softwarefactory-dev
