Age | Commit message (Collapse) | Author | Files | Lines |
|
Synced with old DHA from Danube branch.
Change-Id: I696638003f49bdb1a095c92fcd1440cb56c09c59
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Based on old Fuel DEA from stable/danube:
eno1: # new interface index 4
- fuelweb_admin
ens2f0: # new interface index 2
- public
- management
- storage
ens2f1: # new interface index 3
- private
While at it, use '|' as NIC feature separator to align with the PDF
spec.
Change-Id: I2f9404dd811ecc4826e7ce1d0aebded820777dd2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: If0e7fd76850f0610bd9b899a2a4847428a5472b0
Signed-off-by: mting <dianfeng.du@ericsson.com>
|
|
- 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>
|
|
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>
|
|
Change-Id: I9ba68c0ad5f1f10a714f584f3f974a52558dcaba
Signed-off-by: mting <dianfeng.du@ericsson.com>
|