aboutsummaryrefslogtreecommitdiffstats
path: root/labs/zte/pod3.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-09-26PDF: Fix yamllint warnings & fold reusable codeAlexandru Avadanii1-2/+2
- ericsson-pod{1,2}: Fold node, disk params; - lf-pod4: Jump server uses same disk params; - zte-pod{2,3}: only minor formatting; Change-Id: Ib280aca93f9d6ab1768afa369b922c71485cf79c Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit a9aeec02c2c649b01ef9aad20c0c89f723a1f356)
2017-09-22labs: PDF: s/pod owner/pod_owner/gAlexandru Avadanii1-1/+1
Change-Id: Idc72cc6c0c8f13410adbb3478f811a8ee8563223 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit fe7a758541590ee51b6fbf95534163532568bbca)
2017-08-24Correct typos to avoid failure in jenkins-ci checkBlaisonneau David1-6/+6
Change-Id: I2e8b789cbc10def76a1b7ee673bc1ca6d7f4137f Signed-off-by: Blaisonneau David <david.blaisonneau@orange.com>
2017-05-19Hello, OPNFV installer projectsagardner1-0/+217
Firstly, this patchset looks a bit messy at the onset. relevant parts are installers/apex/*.j2 installers/joid/*.j2 installers/compass4nfv/*.j2 and the new verify job that runs check-jinja2.sh If you look at installers/*/pod_config.yaml.j2 you will see the network settings for apex joid and compass4nfv installers, the possible to template hard coded values have been replaced with jinja2 vales, that are populated by reading one of labs/*/*/config/pod.yaml eg: nodes: - name: pod1-node1 becomes - name: {{ conf['nodes'][0]['name'] }} In my last patchset I had ignored data already present in the pod.yaml (which is defined in the pharos spec here: https://gerrit.opnfv.org/gerrit/gitweb?p=pharos.git;a=blob;f=config/pod1.yaml ) I created by own yaml file in an attempt to figure out what all the installers needed to know to install on any given pod. this was counter productive. I have included a script (securedlab/check-jinja2.sh) that will check all securedlab/installers/*/pod_config.yaml.j2 against all securedlab/labs/*/pod*.yaml This is a first step towards having your installers run on any pod that has a pod file created for it. (securedlab/labs/*/pod[pod-number].yaml) Moving forward I would like your input on identifing variables in your installers configs that are needed for deployment but not covered by securedlab/labs/*/pod*.yaml Thanks for your time and feedback Best Regards, Aric Change-Id: I5f2f2b403f219a1ec4b35e46a5bc49037a0a89cf Signed-off-by: agardner <agardner@linuxfoundation.org>