Age | Commit message (Collapse) | Author | Files | Lines |
|
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: Iaf6f6e01ffbe2d899e1ff9b84d07e38447ce9357
Signed-off-by: Jack Morgan <jack.morgan@intel.com>
|
|
Values come from a pod config file.
This is just an example, only ipmi_ips are templated at this time.
eg: address: {{ config['global_details']['ipmi_ips'][0] }}
test like this:
./utils/generate_config.py -y labs/intel/pod5/pod.yaml -j
installers/joid/labconfig.jinja2
releng should have a new job, validate-templates
that looks for
pattern: 'utils/generate_config.yml'
pattern: '**/*.jinja2'
and tests that templating does not error.
Change-Id: I7f781abb702afcfccf7ed17674378cffe4a7177d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
JIRA: FUEL-243
Change-Id: Id077221fa5c43d3924ac2b829621814233f3cff9
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
JIRA: FUEL-220
Change-Id: I96b1b3fb397ed2f957c0e865cc6f071b42698970
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
Change-Id: I05437371f3a789ce3f8f5333dec0ed0d477710cc
Related-change: https://gerrit.opnfv.org/gerrit/#/c/21153/
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
To contain m1.small flavor instances increase
disk size for co-located ceph storage.
Change-Id: Ib4da248ec5182c98464457b5b84de51cc2ae5d6d
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
* increase the memory/cpu of controller
* reduce the memory of computes
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Added interface mappings and transformations for running OVS
scenarios with DPDK on intel and ericsson virtual environments
JIRA: FUEL-168
Change-Id: Ia359fb8a958ca94a64cf9ae74733ed43b2589495
Signed-off-by: Fedor Zhadaev <fzhadaev@mirantis.com>
|
|
|
|
Functest framework is trying to access internal endpoints from host
level which currently is not possible in virtual deployments.
Related: https://gerrit.opnfv.org/gerrit/#/c/18259/
JIRA: FUEL-167
Change-Id: Id5155116f1d1f6e55810b03fe264d74fe01979f3
Signed-off-by: Michal Skalski <mskalski@mirantis.com>
|
|
Do not block connection in case of test framework try to connect from
different subnet.
Change-Id: I32b4b52d41286c9f906d70d846e28081bbcd055f
Signed-off-by: Fedor Zhadaev <fzhadaev@mirantis.com>
|
|
and Ericsson-1 virtual deployment
NOT VERIFIED
DO NOT MERGE
Change-Id: I643674caad64af3b89da484261044d4136061e64
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Change-Id: Ia5c5efcad438ca9bec20b9e6ce8dcf8eb60307b0
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
Change-Id: I56ef6360fc41b9fee81365d2e4d9ecf8f1fe00a0
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|
|
This patch provides a common configuration structure, providing separation of concern between:
1) Base installer configuration
2) Per Lab/POD specific configuration
3) Per installer feature/plugin configuration
4) Deployment scenario configuration.
It is not yet aligned across installers - but provides a structure for
future alignment.
It relates to the implementation provided here:
https://gerrit.opnfv.org/gerrit/#/c/3995/
Also see the README file
VERIFIED
READY TO MERGE
JIRA:
Change-Id: I852376ba4b500cc50cba6cb3c2634533fc6426a6
Signed-off-by: Jonas Bjurel <jonas.bjurel@ericsson.com>
|