aboutsummaryrefslogtreecommitdiffstats
path: root/labs/zte/pod3
AgeCommit message (Collapse)AuthorFilesLines
2017-09-14Support daisy on zte-pod3Alex Yang2-0/+157
Change-Id: I4bdf8a4a083d5731849aef40473eec2198d3a9b2 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-05-19Hello, OPNFV installer projectsagardner1-216/+0
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>
2017-03-09Add POD3 yaml fileJulien1-0/+216
Change-Id: I2e1dfbfecf48a3b6719697fa60f27e6480a306ed Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2017-01-23Update dea file for ZTE PODswu.zhihui1-97/+0
- remove repos info. Use repos which is defined in dea_base.yml. - remove storage info which is already defined by scenario file. Change-Id: I8c8150ddebfbb143408ed1fbd456e0d30aca6a9f Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-11-17Update repos urlwu.zhihui1-12/+12
- ubuntu version: trusty -> xenial - mos and Auxiliary version: mitaka9.0 -> newton10.0 Change-Id: Ifa11140d6afe71c9d996cab786e97ad004e1bac4 Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-10-09fix version value in dha.yamlwu.zhihui1-1/+1
According to ci log https://build.opnfv.org/ci/job/fuel-deploy-zte-pod3-daily-colorado/38/console, I modify version value. Change-Id: I9fc72ed7ff1f56e6f77fbbde05c9d92dc45a5e50 Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-08-10Add ZTE POD3 adaption infoJulien2-0/+415
Add ZTE POD3 adaption info for Fuel installer. JIRA: PHAROS-247 Change-Id: I591db92684189f37e2af9888eca7c59dc82b2a2a Signed-off-by: Julien-zte <zhang.jun3g@zte.com.cn>