Age | Commit message (Collapse) | Author | Files | Lines |
|
It conflicts with INSTALLER_IP.
Change-Id: I4ec6476c4a7674576fee2510770f0354ad9fd0e1
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
1. Add IDF of zte pod2 and pod3
2. Update PDF of zte pod2 and pod3
3. Update pod config template for yaml-lint
Change-Id: I30f644009ab270f929fe3ee41171986a0e0bde63
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I5c0f01db5bc984067d737f89e424378b88298610
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
For supporting MCP deployment, update the PDF and IDF files
for zte-pod1
Change-Id: I835b5b6fd864f8f6110921ac4b508996b5844216
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: Idc72cc6c0c8f13410adbb3478f811a8ee8563223
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I2e8b789cbc10def76a1b7ee673bc1ca6d7f4137f
Signed-off-by: Blaisonneau David <david.blaisonneau@orange.com>
|
|
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>
|