[opnfv-tech-discuss] Weekly Technical Discussion #153

[HU, BIN]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tsc@
 lists.opnfv.org:MAILTO:opnfv-...@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:https://zoom.us/j/2362828999\n+1-877-369-0926 or
  +1-855-880-1246 / Meeting ID: 236 282 8999\n\nHello community:\n\nThis is
  our 153rd weekly technical discussion at 6am PDT / 9am EDT Monday October
  7th\, 2019\, which is 13:00 UTC.\n\nSridhar Rao will share an idea of community development and attracti
 ng more developers. More specifically\, he will talk about how to recogniz
 e those student volunteers that have made significant contributions to com
 munity.\n\nYou can find your local time here http://www.timeanddate.com/wo
 rldclock/fixedtime.html?msg=OPNFV-Technical-Discussion=20191007T13=
 1\n\nPlease refer to https://wiki.opnfv.org/display/PROJ/Weekly+Technical+
 Discussion for details of dialing logistics and tentative agenda.\n\nPleas
 e let me know if you want to add anything to agenda for discussion in the 
 community.\n\nFor your convenience:\n\n  *   Zoom Meeting: https://zoom.us
 /j/2362828999\n  *   You can also dial in using your phone:\n *   Unit
 ed States (Long distance): +1-669-900-6833 or +1 646 558 8656\n *   Un
 ited States (Toll Free): +1-877-369-0926 or +1-855-880-1246\n *   Meet
 ing ID: 236 282 8999\n *   International numbers available: https://zo
 om.us/zoomconference?m=Xn-Kas4jq2GuyfbCCKYpwvi6FpHEYX8n\n  *   More inform
 ation about OPNFV Conferencing Bridge:\n\nThanks\nBin\n\n
SUMMARY;LANGUAGE=en-US:Weekly Technical Discussion #153
DTSTART;TZID=Pacific Standard Time:20191007T06
DTEND;TZID=Pacific Standard Time:20191007T07
UID:04008200E00074C5B7101A82E008E05A9E02377AD501000
 0100017154C7172928C40972795C418F672EE
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20191004T051218Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/2362828999
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-830232605
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#23618): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/23618
Mute This Topic: https://lists.opnfv.org/mt/34390879/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [opnfv-tech-discuss] [Fuel] 3 computes and baremetal

[Tomi Juvonen]

Hi,

It was my idf file missing 3 compute. Getting forward now. Coming back if need 
more assistance.

Thanks,
Tomi

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of Tomi Juvonen via Lists.Opnfv.Org
Sent: Wednesday, October 2, 2019 7:01 PM
To: Alexandru Avadanii ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] 3 computes and baremetal

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 
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 
mailto:alexandru.avada...@enea.com>>
Sent: Tuesday, October 1, 2019 11:41 PM
To: Juvonen, Tomi (Nokia - FI/Espoo) 
mailto:tomi.juvo...@nokia.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Cc: wenjuan dong mailto: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: