Thanks Alex, This was very helpful and complete explanation.
I now use the "os-nosdn-nofeature-noha". I earlier used my own
(os-nosdn-nofeature-noha-doctor) only as thought I need the support for the
third compute.
Just introduced the dummy third controller to pdf. There is still very similar
kind of error coming that I have not been able to figure out. Some indexing
just do not go right. If there only was more debug information.
sudo ./deploy.sh -b file:///home/jenkins/fuel/mcp/deploy/config -l nokia-pod1
-p nokia-pod1 -s os-nosdn-nofeature-noha -D
...
Traceback (most recent call last):
File "./pharos/config/utils/generate_config.py", line 72, in <module>
OUTPUT = TEMPLATE.render(conf=DICT).replace('__slash__', '/')
File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 1008, in
render
return self.environment.handle_exception(exc_info, True)
File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 780, in
handle_exception
reraise(exc_type, exc_value, tb)
File
"/home/tojuvone/fuel/mcp/reclass/classes/cluster/all-mcp-arch-common/infra/config_pdf.yml.j2",
line 62, in top-level template code
pxe_admin_interface: {{
conf.idf.fuel.network.node[i].interfaces[nm.idx_admin] }}
File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 430, in
getattr
return getattr(obj, attribute)
jinja2.exceptions.UndefinedError: list object has no element 5
+ notify_e '[ERROR] Could not convert PDF to network definitions!'
+ local 'msg=[ERROR] Could not convert PDF to network definitions!'
+ shift
+ notify_i '\n[ERROR] Could not convert PDF to network definitions!\n\n'
+ tput setaf 1
+ echo -en '\n[ERROR] Could not convert PDF to network definitions!\n\n'
[ERROR] Could not convert PDF to network definitions!
There would actually be 2 more interfaces in jumphost as well as controllers,
but they are not used for anything. So tried to keep just those interfaces used
in all definitions in pdf as well as idf. I also tried with those extra
interfaces in idf and pdf, but doesn't change the result.
Thanks,
Tomi
From: Alexandru Avadanii <alexandru.avada...@enea.com>
Sent: Tuesday, October 1, 2019 11:41 PM
To: Juvonen, Tomi (Nokia - FI/Espoo) <tomi.juvo...@nokia.com>;
opnfv-tech-discuss@lists.opnfv.org
Cc: wenjuan dong <dongwenjuan1...@gmail.com>
Subject: Re: [Fuel] 3 computes and baremetal
Hi, Tomi,
Fuel already supports a dynamic number of compute nodes based on the total
number of nodes in PDF/IDF and assumes the following node definition ordering
in both files:
* the first 3 nodes in PDF/IDF are controller/gateway or opendaylight
roles, depending on the current scenario and its type (ha/noha) - sometimes the
3rd node remaining unused, in which case a dummy node should be defined just to
keep this indexing assumption in place;
* (later edit): I see you are targeting a noha scenario, so you should
definitely add one dummy node before the computes in PDF/IDF, just to keep our
hardcoded indexing happy - a total a 6 nodes will be present, but the 3rd one
will be ignores;
* any number of remaining nodes will be assigned the compute role (cmp001,
cmp002, cmp003? etc.);
However, the scenario description file you attached looks a bit different than
what I expected (also may be a bit outdated since I see the maas state in
there):
* cluster:domain should match an existing directory in
mcp/reclass/classes/cluster, so mcp-nosdn-noha.local might need to be renamed
to mcp-ovs-noha.local (I assume you are targeting the os-nosdn-nofeature-noha
OPNFV scenario);
* cluster:states should not contain maas & baremetal_init, they have been
abstracted into the defaults.yaml used by all scenarios;
* virtual:nodes:control and virtual:nodes:compute should contain node roles
(generic and not tied to the specific POD), e.g. ctl01,gtw01,cmp001,cmp002;
* this is probably the important bit: you don't need to define more than 2
computes in the scenario file you attached, as long as the PDF/IDF has more
nodes than the ones defined in that scenario file, all remaining nodes will
also become computes;
* defining 3 computes in that scenario file will make the mininum nodes
requirement 6 instead of 5, so it's up to you if you want to enforce this;
Please let me know if you need some help with adding this scenario, as Fuel
scenario black magic is not very well documented and full of footguns ...
BR,
Alex
________________________________
From:
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
on behalf of Tomi Juvonen
<tomi.juvo...@nokia.com<mailto:tomi.juvo...@nokia.com>>
Sent: Tuesday, October 1, 2019 8:22 AM
To:
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: wenjuan dong <dongwenjuan1...@gmail.com<mailto:dongwenjuan1...@gmail.com>>
Subject: [opnfv-tech-discuss] [Fuel] 3 computes and baremetal
Hi,
Currently Doctor can test fault management use case with Fuel, but maintenance
use case will need at least 3 compute nodes.
I got things through without this pdf check error earlier when only had 2
computes (then it went as far as complaining my bridges). I guess it is not
just having my scenario with 3 computes, but something else need to be changed
too.
I sure need to work on the idf-file and those bridges, but before that my issue
seems to relate to supporting 3 computes. For now also single controller is
just fine, tried with 2 as there seems to be some controller + gw node in
existing setups.
./deploy.sh -b file:///home/jenkins/fuel/mcp/deploy/config -l nokia-pod1 -p
nokia-pod1 -s os-nosdn-nofeature-noha-doctor -D
...
File "/home/tojuvone/fuel/mcp/scripts/xdf_data.sh.j2", line 66, in template
{%- if ( section_map[section] < conf.nodes | length and
File "/usr/lib/python2.7/site-packages/jinja2/environment.py", line 430, in
getattr
return getattr(obj, attribute)
jinja2.exceptions.UndefinedError: list object has no element 5
+ notify_e '[ERROR] Could not convert PDF to network definitions!
Any pointers to have this forwards? Is there an easy way to get more debugging
data?
Br,
Tomi
Doctor PTL
This message, including attachments, is CONFIDENTIAL. It may also be privileged
or otherwise protected by law. If you received this email by mistake please let
us know by reply and then delete it from your system; you should not copy it or
disclose its contents to anyone. All messages sent to and from Enea may be
monitored to ensure compliance with internal policies and to protect our
business. Emails are not secure and cannot be guaranteed to be error free as
they can be intercepted, a mended, lost or destroyed, or contain viruses. The
sender therefore does not accept liability for any errors or omissions in the
contents of this message, which arise as a result of email transmission. Anyone
who communicates with us by email accepts these risks.
idf-nokia-pod1.yaml
Description: idf-nokia-pod1.yaml
nokia-pod1.yaml
Description: nokia-pod1.yaml
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23615): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23615 Mute This Topic: https://lists.opnfv.org/mt/34354279/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
