Age | Commit message (Collapse) | Author | Files | Lines |
|
Old Fuel (up to and including Danube release) relied on a DEA/DHA
pair of configuration files, usually constructed based on information
collected from a manually deployed POD using a "reap" procedure.
Starting with Euphrates, Fuel will use the PDF as input, so DEA/DHA,
as well as reap data are now obsolete.
Some PODs (arm-pod5, lf-pod2) still have a "local_env" configuration
file, which is a leftover from old Fuel, but can only be dropped
after Fuel automatically detects the jumphost bridge names (either by
matching the IP addresses on the jumphost to the networks in PDF, or
by using a static mapping defined in a PDF companion file, e.g. IDF).
Remove all obsolete configuration, including useless directories.
Change-Id: I9eae2067d83347409c17126aadb19e3d6b95d4b6
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.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>
|
|
update according to the final decision.
Change-Id: Id7e9c52506e54399a079ba13ea29e9490a0a0749
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Change-Id: I6f34f7bc66f1dd5e2140d7ce3815440fd24a1ba7
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
- 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>
|
|
JIRA: FUEL-243
Change-Id: Id077221fa5c43d3924ac2b829621814233f3cff9
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
- 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>
|
|
Change-Id: Ib87cf003c8019c03670b14f3a3c6e683dcbf7df8
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Due to migration, update zte-pod1 configuration files.
JIRA: PHAROS-246
Change-Id: Iefb589d5f12cb0f63b2e64be7314ad09908b209f
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: Ifbd6552b79e5894d87d5d0887c606653b7e17d6f
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: Id1f051599b5d92a0d84aea3b221d09de9f4570ee
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|