[opnfv-tech-discuss] Cancelled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
PRODID://Yahoo//Calendar//EN
VERSION:2.0
METHOD:CANCEL
BEGIN:VEVENT
SUMMARY:OPNFV Doctor weekly meeting
DESCRIPTION:Doctor is a fault management and maintenance project to develop
  and realize the consequent implementation for the OPNFV reference platfor
 m.\n\n?   Doctor page: https://wiki.opnfv.org/doctor\n?   When: Ev
 ery Tuesday 6:00-7:00 PT (Your local time)\n?   Agenda: https://etherpad.o
 pnfv.org/p/doctor_meetings\n?   IRC channel: #opnfv-doctor @ Freenode 
 (Web Chat)\n?   To
  join: https://global.gotomeeting.com/join/819733085\n?   You can also
  dial in using your phone.\no   Access Code: 819-733-085\n\no   Un
 ited States +1 (312) 757-3126\no   Australia +61 2 8355 1040\no   
 Austria +43 7 2088 0034\no   Belgium +32 (0) 28 93 7018\no   Canad
 a +1 (647) 497-9350\no   Denmark +45 69 91 88 64\no   Finland +358
  (0) 923 17 0568\no   France +33 (0) 170 950 592\no   Germany +49 
 (0) 692 5736 7211\no   Ireland +353 (0) 15 360 728\no   Italy +39 
 0 247 92 13 01\no   Netherlands +31 (0) 208 080 219\no   New Zeala
 nd +64 9 280 6302\no   Norway +47 75 80 32 07\no   Spain +34 911 8
 2 9906\no   Sweden +46 (0) 853 527 836\no   Switzerland +41 (0) 43
 5 0167 13\no   United Kingdom +44 (0) 330 221 0086\n\n\nThanks\,\nThe 
 OPNFV Doctor team\n\n\n
CLASS:PUBLIC
DTSTART;TZID=Europe/London:20150120T14
DTEND;TZID=Europe/London:20150120T15
LOCATION:GoToMeeting
PRIORITY:0
SEQUENCE:13
STATUS:CONFIRMED
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
DTSTAMP:20161206T210551Z
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=opnfv-tech-discuss@lists.opnfv.org;ROLE=R
 EQ_PARTICIPANT;RSVP=TRUE:mailto:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=Fatemeh Abdollahei;ROLE=REQ_PARTICIPANT;R
 SVP=TRUE:mailto:f.abdolla...@yahoo.com
ORGANIZER;CN=Carlos Goncalves:mailto:carlos.goncal...@neclab.eu
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=1;BYDAY=TU
EXDATE;TZID=Europe/London:20151027T06,20151110T06,20160315T06,2
 0160426T07,20160621T07,20160823T07
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-YAHOO-YID:yahoo.calendar.acl.writer
X-YAHOO-YID:yahoo.calendar.acl.writer
TRANSP:OPAQUE
STATUS:TENTATIVE
X-YAHOO-USER-STATUS:TENTATIVE
X-YAHOO-EVENT-STATUS:BUSY
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/London
TZURL:http://tzurl.org/zoneinfo/Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19810329T01
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19961027T02
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:-000115
TZOFFSETTO:+
TZNAME:GMT
DTSTART:18471201T00
RDATE:18471201T00
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19160521T02
RDATE:19160521T02
RDATE:19170408T02
RDATE:19180324T02
RDATE:19190330T02
RDATE:19200328T02
RDATE:19210403T02
RDATE:19220326T02
RDATE:19230422T02
RDATE:19240413T02
RDATE:19250419T02
RDATE:19260418T02
RDATE:19270410T02
RDATE:19280422T02
RDATE:19290421T02
RDATE:19300413T02
RDATE:19310419T02
RDATE:19320417T02
RDATE:19330409T02
RDATE:19340422T02
RDATE:19350414T02
RDATE:19360419T02
RDATE:19370418T02
RDATE:19380410T02
RDATE:19390416T02
RDATE:19400225T02
RDATE:19460414T02
RDATE:19470316T02
RDATE:19480314T02
RDATE:19490403T02
RDATE:19500416T02
RDATE:19510415T02
RDATE:19520420T02
RDATE:19530419T02
RDATE:19540411T02
RDATE:19550417T02
RDATE:19560422T02
RDATE:19570414T02
RDATE:19580420T02
RDATE:19590419T02
RDATE:19600410T02
RDATE:19610326T02
RDATE:19620325T02
RDATE:19630331T02
RDATE:19640322T02
RDATE:19650321T02
RDATE:19660320T02
RDATE:19670319T02
RDATE:19680218T02
RDATE:19720319T02
RDATE:19730318T02
RDATE:19740317T02
RDATE:19750316T02
RDATE:19760321T02
RDATE:19770320T02
RDATE:19780319T02
RDATE:19790318T02
RDATE:19800316T02
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19161001T03
RDATE:19161001T03
RDATE:19170917T03
RDATE:19180930T03
RDATE:19190929T03
RDATE:19201025T03
RDATE:19211003T03
RDATE:19221008T03
RDATE:19230916T03
RDATE:19240921T03

[opnfv-tech-discuss] Cancelled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
PRODID://Yahoo//Calendar//EN
VERSION:2.0
METHOD:CANCEL
BEGIN:VEVENT
SUMMARY:OPNFV Doctor weekly meeting
DESCRIPTION:Doctor is a fault management and maintenance project to develop
  and realize the consequent implementation for the OPNFV reference platfor
 m.\n\n?   Doctor page: https://wiki.opnfv.org/doctor\n?   When: Ev
 ery Tuesday 6:00-7:00 PT (Your local time)\n?   Agenda: https://etherpad.o
 pnfv.org/p/doctor_meetings\n?   IRC channel: #opnfv-doctor @ Freenode 
 (Web Chat)\n?   To
  join: https://global.gotomeeting.com/join/819733085\n?   You can also
  dial in using your phone.\no   Access Code: 819-733-085\n\no   Un
 ited States +1 (312) 757-3126\no   Australia +61 2 8355 1040\no   
 Austria +43 7 2088 0034\no   Belgium +32 (0) 28 93 7018\no   Canad
 a +1 (647) 497-9350\no   Denmark +45 69 91 88 64\no   Finland +358
  (0) 923 17 0568\no   France +33 (0) 170 950 592\no   Germany +49 
 (0) 692 5736 7211\no   Ireland +353 (0) 15 360 728\no   Italy +39 
 0 247 92 13 01\no   Netherlands +31 (0) 208 080 219\no   New Zeala
 nd +64 9 280 6302\no   Norway +47 75 80 32 07\no   Spain +34 911 8
 2 9906\no   Sweden +46 (0) 853 527 836\no   Switzerland +41 (0) 43
 5 0167 13\no   United Kingdom +44 (0) 330 221 0086\n\n\nThanks\,\nThe 
 OPNFV Doctor team\n\n\n
CLASS:PUBLIC
DTSTART;TZID=Europe/London:20150120T14
DTEND;TZID=Europe/London:20150120T15
LOCATION:GoToMeeting
PRIORITY:0
SEQUENCE:13
STATUS:CONFIRMED
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
DTSTAMP:20161206T210551Z
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=opnfv-tech-discuss@lists.opnfv.org;ROLE=R
 EQ_PARTICIPANT;RSVP=TRUE:mailto:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;PARTSTAT=NEEDS-ACTION;CN=wonstonx;ROLE=REQ_PARTICIPANT;RSVP=TRUE:m
 ailto:wonst...@yahoo.com
ORGANIZER;CN=Carlos Goncalves:mailto:carlos.goncal...@neclab.eu
RRULE:FREQ=WEEKLY;WKST=SU;INTERVAL=1;BYDAY=TU
EXDATE;TZID=Europe/London:20151027T06,20151110T06,20160315T06,2
 0160426T07,20160621T07,20160823T07
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-YAHOO-YID:yahoo.calendar.acl.writer
X-YAHOO-YID:yahoo.calendar.acl.writer
TRANSP:OPAQUE
STATUS:TENTATIVE
X-YAHOO-USER-STATUS:TENTATIVE
X-YAHOO-EVENT-STATUS:BUSY
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/London
TZURL:http://tzurl.org/zoneinfo/Europe/London
X-LIC-LOCATION:Europe/London
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19810329T01
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19961027T02
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:STANDARD
TZOFFSETFROM:-000115
TZOFFSETTO:+
TZNAME:GMT
DTSTART:18471201T00
RDATE:18471201T00
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:+
TZOFFSETTO:+0100
TZNAME:BST
DTSTART:19160521T02
RDATE:19160521T02
RDATE:19170408T02
RDATE:19180324T02
RDATE:19190330T02
RDATE:19200328T02
RDATE:19210403T02
RDATE:19220326T02
RDATE:19230422T02
RDATE:19240413T02
RDATE:19250419T02
RDATE:19260418T02
RDATE:19270410T02
RDATE:19280422T02
RDATE:19290421T02
RDATE:19300413T02
RDATE:19310419T02
RDATE:19320417T02
RDATE:19330409T02
RDATE:19340422T02
RDATE:19350414T02
RDATE:19360419T02
RDATE:19370418T02
RDATE:19380410T02
RDATE:19390416T02
RDATE:19400225T02
RDATE:19460414T02
RDATE:19470316T02
RDATE:19480314T02
RDATE:19490403T02
RDATE:19500416T02
RDATE:19510415T02
RDATE:19520420T02
RDATE:19530419T02
RDATE:19540411T02
RDATE:19550417T02
RDATE:19560422T02
RDATE:19570414T02
RDATE:19580420T02
RDATE:19590419T02
RDATE:19600410T02
RDATE:19610326T02
RDATE:19620325T02
RDATE:19630331T02
RDATE:19640322T02
RDATE:19650321T02
RDATE:19660320T02
RDATE:19670319T02
RDATE:19680218T02
RDATE:19720319T02
RDATE:19730318T02
RDATE:19740317T02
RDATE:19750316T02
RDATE:19760321T02
RDATE:19770320T02
RDATE:19780319T02
RDATE:19790318T02
RDATE:19800316T02
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0100
TZOFFSETTO:+
TZNAME:GMT
DTSTART:19161001T03
RDATE:19161001T03
RDATE:19170917T03
RDATE:19180930T03
RDATE:19190929T03
RDATE:19201025T03
RDATE:19211003T03
RDATE:19221008T03
RDATE:19230916T03
RDATE:19240921T03
RDATE:19251004T03

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Umar Faroo
 q:MAILTO:umar.far...@neclab.eu
DESCRIPTION;LANGUAGE=en-US:Doctor is a fault management and maintenance pro
 ject to develop and realize the consequent implementation for the OPNFV re
 ference platform.\n\n•   Doctor page: https://wiki.opnfv.org/doctor\
 n•   When: Every Tuesday 6:00-7:00 PT (Your local time)\n•   Agend
 a: https://etherpad.opnfv.org/p/doctor_meetings\n•   IRC channel: #o
 pnfv-doctor @ Freenode (Web Chat)\n•   To join: https://global.gotomeeting.com/join/819733
 085\n•   You can also dial in using your phone.\no   Access Code
 : 819-733-085\n\no   United States +1 (312) 757-3126\no   Australi
 a +61 2 8355 1040\no   Austria +43 7 2088 0034\no   Belgium +32 (0
 ) 28 93 7018\no   Canada +1 (647) 497-9350\no   Denmark +45 69 91 
 88 64\no   Finland +358 (0) 923 17 0568\no   France +33 (0) 170 95
 0 592\no   Germany +49 (0) 692 5736 7211\no   Ireland +353 (0) 15 
 360 728\no   Italy +39 0 247 92 13 01\no   Netherlands +31 (0) 208
  080 219\no   New Zealand +64 9 280 6302\no   Norway +47 75 80 32 
 07\no   Spain +34 911 82 9906\no   Sweden +46 (0) 853 527 836\no  
  Switzerland +41 (0) 435 0167 13\no   United Kingdom +44 (0) 330 2
 21 0086\n\n\nThanks\,\nThe OPNFV Doctor team\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU;WKST=SU
EXDATE;TZID=Pacific Standard Time:20151027T06,20151110T06,20160315T
 06,20160426T06,20160621T06,20160823T06,20161220T06,201
 61227T06,20170103T06,20170221T06,20170509T06,20170613T0600
 00
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150120T06
DTEND;TZID=Pacific Standard Time:20150120T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170710T113841Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:20
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:20
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150616T06
DTEND;TZID=Pacific Standard Time:20150616T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20150616T00
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170710T113841Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:20
LOCATION:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:20
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150623T06
DTEND;TZID=Pacific Standard Time:20150623T07

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alan McNa
 mee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kedalagud
 de, Meghashree Dattatri'":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Umar Faroo
 q:MAILTO:umar.far...@neclab.eu
DESCRIPTION;LANGUAGE=en-US:Most Doctor team members will be meeting at the 
 OPNFV Summit Beijing.\nWe will resume the week after\, June 20.\n\nSafe tr
 avels\, everyone!\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20170613T06
DTEND;TZID=Pacific Standard Time:20170613T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20170613T06
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170606T133351Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:19
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:19
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [doctor] Beijing Design Summit: breakout sessions scheduling

[Carlos Goncalves]

Doctors,

So far we've received 3 good session proposals [1]. Thanks everyone and feel 
free to propose more!

I would like to start scheduling them taking into account the current room 
booking [2] as well as participants' agenda because we have people across 
multiple projects (QTIP, Barometer, etc) with their own project sessions (e.g. 
Yujun with QTIP).

Proposal draft:

Text in bold means Doctor specific sessions; others are recommended to Doctor 
folks.

DAY 1/MONDAY
11:15 - 12:15: Doctor: Host maintenance [room Sculpture]
15:30 - 16:00: Doctor's achievements and what else you can do with it! [plenary]
13:45 - 14:15: Doctor: Overview of Doctor tests refactoring to Python [room 
Sculpture]
14:45 - 15:15: Barometer: Taking the pressure off of assurance and resource 
contention scenarios for NFVI [plenary]
16:30 - 17:00: OPNFV XCI: How to work with OpenStack Master

DAY 2/TUESDAY
09:15 - 10:45: OPNFV XCI Intro, Hands on [Room Pastel]
09:45 - 10:16: Enabling Carrier-Grade availability within a cloud 
infrastructure [plenary]
14:00 - 15:00: Doctor: performance & profiling [room Pastel]


Please let us know in case you have a conflict or have other 
proposals/suggestions.

[1] https://etherpad.opnfv.org/p/doctor_meetings
[2] https://wiki.opnfv.org/display/EVNT/Beijing+Design+Summit+Schedule

Thanks,
Carlos

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
DESCRIPTION;LANGUAGE=en-US:Many Doctor team members will be at the OpenStac
 k Summit Boston.\n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20170509T06
DTEND;TZID=Pacific Standard Time:20170509T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20170509T06
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170503T114900Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:18
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:18
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

[Carlos Goncalves]

Hi Morgan,

Ryota submitted today a patch for fixing under Apex: 
https://gerrit.opnfv.org/gerrit/#/c/30011/
The way I see it, the patch is a workaround for what seems to be a regression 
in Apex. It should be removed once fixed and verified in Apex.

Carlos

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: 08 March 2017 15:48
To: Ryota Mibu; Jose Lausuch (jose.laus...@ericsson.com); 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

I do confirm most of the Fuel scenarios seem OK from a Doctor point of view now 
:)

However Doctor is still FAIL on Apex and Joid scenarios and is not run on 
Compass for Danube do you plan any restrictions on some installers?

/Morgan

Le 06/03/2017 à 15:11, Ryota Mibu a écrit :
> Morgan,
>
>
> Thanks! Now, we got "OK" for doctor test in functest daily job.
>
> https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-d
> aily-master/1251/consoleFull
>
>
> BR,
> Ryota
>
>> -Original Message-
>> From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
>> Sent: Monday, March 06, 2017 4:59 PM
>> To: Mibu Ryota(壬生 亮太) ; Jose Lausuch 
>> (jose.laus...@ericsson.com) ; 
>> opnfv-tech-discuss@lists.opnfv.org
>> Subject: Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario 
>> debugging
>>
>> Hi Ryota,
>>
>> when we produce Functest docker, we are currently cloning the Doctor 
>> master repo the last Functest docker has been successfully produced 1 
>> h ago (started at at 6:10 - Jenkins Time) - previous one was produced 
>> on the 3rd of March so I assume your changes are taken into account 
>> since this time
>>
>> Last CI run I found was on fuel started at 6:19 jenkins and should 
>> not include the change but next run should include it, wait and see...
>>
>> /Morgan
>>
>> Le 06/03/2017 à 01:16, Ryota Mibu a écrit :
>>> Jose, Functest team,
>>>
>>>
>>> Quick report: We've fixed bugs in doctor test script [1,2] and got OK in 
>>> doctor's verify job [3].
>>>
>>> However, functest daily job is using old code even in the latest job 
>>> [4]. Maybe we should wait next daily job set. But,
>> I'll be happy if you can check whether the functest jobs use the latest 
>> codes of included repos or not.
>>> [1]
>>> https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=commit;h=8f72e
>>> 69 5538c2281f923bdbf7a6d7b1d1763c70c [2] 
>>> https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=commit;h=7c34d
>>> 9e cbd17053ca9d14cc518b11e501b66cbeb [3] 
>>> https://build.opnfv.org/ci/job/doctor-verify-fuel-sample-master/93/
>>> [4]
>>> https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal
>>> -d
>>> aily-master/1247/
>>>
>>>
>>> Thanks,
>>> Ryota
>>>
 -Original Message-
 From: opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
 Ryota Mibu
 Sent: Wednesday, March 01, 2017 12:34 AM
 To: opnfv-tech-discuss@lists.opnfv.org
 Subject: [opnfv-tech-discuss] [doctor][functest] doctor scenario 
 debugging

 Hi,


 As we discussed in doctor meeting today, I created JIRA tickets for 
 tracking status of our debug in each installer. We need to get 
 green lights in doctor scenario test in functest report. As we may 
 need to track different bugs for each installer, I created
>> three tickets for each.
   Fuel --> https://jira.opnfv.org/browse/DOCTOR-95
   Apex --> https://jira.opnfv.org/browse/DOCTOR-96
   Joid --> https://jira.opnfv.org/browse/DOCTOR-97

 One of barriers is lack of info due to no access to CI pod. In 
 order to ease our debug, I propose to print logs of forked 
 processes in doctor scenario if the test failed, so that we can see 
 log messages in doctor.log . I believe it won't bother functest
>> main log (Jenkins console).
   https://gerrit.opnfv.org/gerrit/29489


 BR,
 Ryota


 ___
 opnfv-tech-discuss mailing list
 opnfv-tech-discuss@lists.opnfv.org
 https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>> ___
>>> opnfv-tech-discuss mailing list
>>> opnfv-tech-discuss@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
>> --
>> Morgan Richomme
>> Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>>
>> Network architect for innovative services Future of the Network 
>> community member Open source Orange community manager
>>
>>
>> tel. +33 (0) 296 072 106
>> mob. +33 (0) 637 753 326
>> morgan.richo...@orange.com
>>
>>
>> _
>> ___
>> _
>>
>> Ce message et ses pieces jointes peuvent 

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Pierre Ly
 nch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
DESCRIPTION;LANGUAGE=en-US:Many members of the team will be absent (OpenSta
 ck PTG\, vacation\, …).\nResuming on Feb 28th.\n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20170221T06
DTEND;TZID=Pacific Standard Time:20170221T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20170221T06
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170214T152019Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:17
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:17
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
DESCRIPTION;LANGUAGE=en-US:Doctor is a fault management and maintenance pro
 ject to develop and realize the consequent implementation for the OPNFV re
 ference platform.\n\n\n\n•   Doctor page: https://wiki.opnfv.org/doc
 tor\n\n•   When: Every Tuesday 6:00-7:00 PT (Your local time)\n\n•
Agenda: https://etherpad.opnfv.org/p/doctor_meetings\n\n•   IRC c
 hannel: #opnfv-doctor @ Freenode (Web Chat)\n\n•   To join: https://global.gotomeeting.com
 /join/819733085\n\n•   You can also dial in using your phone.\n\no  
  Access Code: 819-733-085\n\n\n\no   United States +1 (312) 757-31
 26\n\no   Australia +61 2 8355 1040\n\no   Austria +43 7 2088 0034
 \n\no   Belgium +32 (0) 28 93 7018\n\no   Canada +1 (647) 497-9350
 \n\no   Denmark +45 69 91 88 64\n\no   Finland +358 (0) 923 17 056
 8\n\no   France +33 (0) 170 950 592\n\no   Germany +49 (0) 692 573
 6 7211\n\no   Ireland +353 (0) 15 360 728\n\no   Italy +39 0 247 9
 2 13 01\n\no   Netherlands +31 (0) 208 080 219\n\no   New Zealand 
 +64 9 280 6302\n\no   Norway +47 75 80 32 07\n\no   Spain +34 911 
 82 9906\n\no   Sweden +46 (0) 853 527 836\n\no   Switzerland +41 (
 0) 435 0167 13\n\no   United Kingdom +44 (0) 330 221 0086\n\n\n\n\n\nT
 hanks\,\n\nThe OPNFV Doctor team\n
SUMMARY;LANGUAGE=en-US:OPNFV Doctor weekly meeting
DTSTART;TZID=America/Los_Angeles:20170207T06
DTEND;TZID=America/Los_Angeles:20170207T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=America/Los_Angeles:20170207T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170207T140058Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
DESCRIPTION;LANGUAGE=en-US:Doctor is a fault management and maintenance pro
 ject to develop and realize the consequent implementation for the OPNFV re
 ference platform.\n\n\n\n•   Doctor page: https://wiki.opnfv.org/doc
 tor\n\n•   When: Every Tuesday 6:00-7:00 PT (Your local time)\n\n•
Agenda: https://etherpad.opnfv.org/p/doctor_meetings\n\n•   IRC c
 hannel: #opnfv-doctor @ Freenode (Web Chat)\n\n•   To join: https://global.gotomeeting.com
 /join/819733085\n\n•   You can also dial in using your phone.\n\no  
  Access Code: 819-733-085\n\n\n\no   United States +1 (312) 757-31
 26\n\no   Australia +61 2 8355 1040\n\no   Austria +43 7 2088 0034
 \n\no   Belgium +32 (0) 28 93 7018\n\no   Canada +1 (647) 497-9350
 \n\no   Denmark +45 69 91 88 64\n\no   Finland +358 (0) 923 17 056
 8\n\no   France +33 (0) 170 950 592\n\no   Germany +49 (0) 692 573
 6 7211\n\no   Ireland +353 (0) 15 360 728\n\no   Italy +39 0 247 9
 2 13 01\n\no   Netherlands +31 (0) 208 080 219\n\no   New Zealand 
 +64 9 280 6302\n\no   Norway +47 75 80 32 07\n\no   Spain +34 911 
 82 9906\n\no   Sweden +46 (0) 853 527 836\n\no   Switzerland +41 (
 0) 435 0167 13\n\no   United Kingdom +44 (0) 330 221 0086\n\n\n\n\n\nT
 hanks\,\n\nThe OPNFV Doctor team\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU;WKST=SU
EXDATE;TZID=America/Los_Angeles:20151027T06,20151110T06,20160315T06
 ,20160426T06,20160621T06,20160823T06,20161220T06,20161
 227T06,20170103T06
SUMMARY;LANGUAGE=en-US:OPNFV Doctor weekly meeting
DTSTART;TZID=America/Los_Angeles:20150120T06
DTEND;TZID=America/Los_Angeles:20150120T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161206T210551Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

[Carlos Goncalves]

Sounds good to me.
Thanks Aaron and Maryam!

Carlos

On 26 Jan 2017, at 20:23, Aaron Smith 
> wrote:

Hi,
 Maybe we could dedicate a portion of an upcoming Barometer meeting to discuss 
and put together talking points for a longer meeting?
We have been encourage by the alignment that has been happening within the 
Barometer project.  (VES and the telemetry / event
definition work)

Aaron

On Thu, Jan 26, 2017 at 8:03 AM, Tahhan, Maryam 
> wrote:
Hi Folks
On the barometer side, we’ve been 
looking and actively contributing to collectd to collect system statistics and 
to enable the monitoring of Events and metrics for the NFVI, with the goal of 
leveraging the features it has under the topics you mention. We’d be very 
interested in partaking in a discussion around the topics below to see how 
aligned we are, or if/how we can align. I think there’s a strong alignment with 
VES here also.

One possibility is through the Weekly Technical Discussion forum, another would 
be to dedicate a few of the barometer weekly calls to this (which we would be 
happy to do, as an open call and without project focus).

BR
Maryam


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Tuesday, January 24, 2017 7:12 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP 
monitoring

Hi,
  Would there be interest in a separate meeting to discussion what an "ideal" 
monitoring framework might look like.

Topics might include:
  - Polling vs Event capture
  - Platform independent monitor agent
- Network Interfaces
- Kernel events
- VM / Container monitoring
- Common bus for Events / Telemetry / Config
  -  Common Object model
- Agent configuration
- Performance
   - <<50ms

This would be an informal brainstorming activity with more emphasis on
concepts than existing projects (unless necessary).

Thoughts?

Aaron

--
Aaron Smith | Senior Principal Software Engineer
NFV Partner Engineering
Red Hat
aasm...@redhat.com

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com



--
Aaron Smith | Senior Principal Software Engineer
NFV Partner Engineering
Red Hat
aasm...@redhat.com

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-docs] References in documentation to master or release files?

[Carlos Goncalves]

Hello Docs team,

I was wondering if any decision has been made...?
Personally I'm for option A.

Thanks,
Carlos

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: 19 January 2017 09:33
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [opnfv-docs] References in documentation to 
master or release files?

Dear OPNFVDOCS Team,

We are discussing about the pros/cons of referencing in documentation to master 
or release files.


A) The correct (?) way: always refer to master files/URLs in master branch 
and refer to release files/URLs in release branches.
For example, someone trying to git clone origin/stable/danube as documented in 
master branch will fail. Instead, pointing to a specific release should only 
happen in the corresponding release branch.

Also, rendered files in artifacts.opnfv.org from master branch (e.g. 
http://artifacts.opnfv.org/doctor/docs/manuals/mark-host-down_manual.html) 
should be placed under a 'master' directory just like it happens to rendered 
files from release branches.

Consequences:  When updating the documentation prior to branch split, we would 
have to use references to master and at branch split update all references to 
release branch. And patches that are being cherry picked to the release would 
require changing the links contained in it. Also, the references would have to 
be updated for each release.


B)  The pragmatic way: reduce the need/effort to update such links from 
release to release and use references to master for those parts of the 
documentation that will not change for the release, e.g. references to some 
manuals where we don't have any plans to update those parts of the code.

See also the discussion and example in 
https://gerrit.opnfv.org/gerrit/#/c/24365/

We are not sure what would be the preferred/recommended way.
Some recommendations by the opnfvdocs team would help the different projects to 
use a common approach.

I would like to get some more feedback from other OPNFV'ers on how to best 
address this.

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] congress support in compass4nfv

[Carlos Goncalves]

Hi Harry,

So sorry I missed your email.

Thank you a lot for all your efforts to support Congress in Compass!
The Doctor team will give you feedback once we try it out with our test cases.

Cheers,
Carlos

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: 28 November 2016 02:54
To: huangxiangyu; SULLIVAN, BRYAN L; Carlos Goncalves
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi, Bryan, Carlos

 Congress support in compass4nfv is finished. It will be a default 
ansible role in our Mitaka and Newton scenario for ubuntu and for mitaka we 
also support congress on centos7. Congress will be installed  in all three 
controller nodes with ha by hapoxy. There is a patch about congress support on 
compass4nfv gerrit and I can deploy a virtual pod with congress if you'd like 
to check it out. You can contact me if you need further support from compass 
team.

Best regards
Harry Huang

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of huangxiangyu
Sent: Tuesday, November 01, 2016 12:31 PM
To: SULLIVAN, BRYAN L; Carlos Goncalves
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] congress support in compass4nfv

Hi, Bryan

The error log is a little too long to post on IRC, so I just send you via 
email. But IRC is good place to communicate, we can talk about the further 
detail there. for the deploy environment, I am using  ubuntu 16.04.1 on my 
hosts and this version  of ubuntu has official congress debs. Here is what I 
got using apt list command:
 congress-common/unknown,now 3.0.0+dfsg1-1 all
 congress-server/unknown,now 3.0.0+dfsg1-1 all
 python-congress/now 4.0.0.0rc2~dev80-1
 python-congressclient/unknown 1.2.3-2 all
after configuration and database operations, I  encounter the no module named 
antlr3 error. I try to fix it by installing antlr_python_runtime but I got 
error_log_1 when installed runtime V3.0.1 , error_log_2 when installed V3.1.3.

Thanks
Harry huang

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Monday, October 31, 2016 11:39 PM
To: huangxiangyu; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Harry,

Can you drop a console log or other details on the process you are using to IRC 
(#opnfv-copper) or on an etherpad somethere etc? I need to understand where you 
are getting the Congress code (e.g. "congress debs") and what 
environment/process you are using to install it. I'm not familiar with antlr 
and don't know what role it might have in the install. But I can probably 
figure it out with more info.

Thanks,
Bryan Sullivan | AT

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Wednesday, October 26, 2016 8:28 PM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>; Carlos Goncalves 
<carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>>
Cc: Xueyifei (Yifei Xue) <xueyi...@huawei.com<mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi, I encounter some problem when I start congress-server after I installed 
congress using congress debs: when I used antlr V3.0.1 runtime returns 
"ParserRuleReturnScope  is not defined" error while  other antlr  runtime has 
ANTLR version mismatch problem saying 'The recognizer has been generated by 
V3.0.1. Please use the V3.0.1 runtime '. So which antlr runtime should I use?

Thanks
Harry huang


From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Thursday, October 13, 2016 1:19 AM
To: huangxiangyu; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Email is OK, but you can also edit the Copper wiki at 
https://wiki.opnfv.org/display/copper/Installer+Support or provide a link to 
where you are describing the work on your wiki or JIRA. I'll also try to 
capture the status there as it gets developed.

Thanks,
Bryan Sullivan | AT

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Tuesday, October 11, 2016 6:45 PM
To: Carlos Goncalves 
<carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>>; huangxiangyu 
<huangxiang...@huawei.com<mailto:huangxiang...@huawei.com>>
Cc: Xueyifei (Yifei Xue) <xueyi...@huawei.com<mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>
Subject: R

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
DESCRIPTION;LANGUAGE=en-US:[Cancellation reason: holiday season\; resuming 
 January 10th\, 2017]\n\nDoctor is a fault management and maintenance proje
 ct to develop and realize the consequent implementation for the OPNFV refe
 rence platform.\n\n•   Doctor page: https://wiki.opnfv.org/doctor\n
 •   When: Every Tuesday 6:00-7:00 PT (Your local time)\n•   Agenda
 : https://etherpad.opnfv.org/p/doctor_meetings\n•   IRC channel: #op
 nfv-doctor @ Freenode (Web Chat)\n•   To join: https://global.gotomeeting.com/join/8197330
 85\n•   You can also dial in using your phone.\no   Access Code:
  819-733-085\n\no   United States +1 (312) 757-3126\no   Australia
  +61 2 8355 1040\no   Austria +43 7 2088 0034\no   Belgium +32 (0)
  28 93 7018\no   Canada +1 (647) 497-9350\no   Denmark +45 69 91 8
 8 64\no   Finland +358 (0) 923 17 0568\no   France +33 (0) 170 950
  592\no   Germany +49 (0) 692 5736 7211\no   Ireland +353 (0) 15 3
 60 728\no   Italy +39 0 247 92 13 01\no   Netherlands +31 (0) 208 
 080 219\no   New Zealand +64 9 280 6302\no   Norway +47 75 80 32 0
 7\no   Spain +34 911 82 9906\no   Sweden +46 (0) 853 527 836\no   
 Switzerland +41 (0) 435 0167 13\no   United Kingdom +44 (0) 330 22
 1 0086\n\n\nThanks\,\nThe OPNFV Doctor team\n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20170103T06
DTEND;TZID=Pacific Standard Time:20170103T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20170103T06
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20161215T131354Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:16
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:16
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'GUPTA, AL
 OK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
DESCRIPTION;LANGUAGE=en-US:[Cancellation reason: holiday season\; resuming 
 January 10th\, 2017]\n\nDoctor is a fault management and maintenance proje
 ct to develop and realize the consequent implementation for the OPNFV refe
 rence platform.\n\n•   Doctor page: https://wiki.opnfv.org/doctor\n
 •   When: Every Tuesday 6:00-7:00 PT (Your local time)\n•   Agenda
 : https://etherpad.opnfv.org/p/doctor_meetings\n•   IRC channel: #op
 nfv-doctor @ Freenode (Web Chat)\n•   To join: https://global.gotomeeting.com/join/8197330
 85\n•   You can also dial in using your phone.\no   Access Code:
  819-733-085\n\no   United States +1 (312) 757-3126\no   Australia
  +61 2 8355 1040\no   Austria +43 7 2088 0034\no   Belgium +32 (0)
  28 93 7018\no   Canada +1 (647) 497-9350\no   Denmark +45 69 91 8
 8 64\no   Finland +358 (0) 923 17 0568\no   France +33 (0) 170 950
  592\no   Germany +49 (0) 692 5736 7211\no   Ireland +353 (0) 15 3
 60 728\no   Italy +39 0 247 92 13 01\no   Netherlands +31 (0) 208 
 080 219\no   New Zealand +64 9 280 6302\no   Norway +47 75 80 32 0
 7\no   Spain +34 911 82 9906\no   Sweden +46 (0) 853 527 836\no   
 Switzerland +41 (0) 435 0167 13\no   United Kingdom +44 (0) 330 22
 1 0086\n\n\nThanks\,\nThe OPNFV Doctor team\n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20161220T06
DTEND;TZID=Pacific Standard Time:20161220T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20161220T06
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20161215T131313Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:14
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:14
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [doctor] New GTM account

[Carlos Goncalves]

Hello Doctors,

Please note that the GoToMeeting account to our weekly meetings has changed.
Starting from this week, the link to join is 
https://global.gotomeeting.com/join/819733085.

Last week I sent out an updated Outlook calendar to the mailing list, and 
updated three wiki pages:

https://wiki.opnfv.org/display/doctor/Doctor+Home
https://wiki.opnfv.org/display/meetings/Doctor
https://wiki.opnfv.org/display/meetings/Meetings#Meetings-DoctorProjectTeamMeeting

If you find references to the old GTM account, please feel free to edit them or 
let me know.

Thanks,
Carlos

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

[Carlos Goncalves]

Locked to the ool-virtual1 POD: 
https://git.opnfv.org/releng/tree/jjb/doctor/doctor.yml

Carlos

From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: 07 December 2016 02:07
To: Ryota Mibu; Carlos Goncalves; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] doctor CI now available

Is this verification job locked to a speciific POD or runnable in all CI PODs 
deployed by APEX?
On Tue, Dec 6, 2016 at 7:13 PM Ryota Mibu 
<r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>> wrote:
Hi,

Let me explain current status in today’s meeting.


BR,
Ryota

From: Carlos Goncalves 
[mailto:carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>]
Sent: Monday, December 05, 2016 11:52 AM
To: Yujun Zhang <zhangyujun+...@gmail.com<mailto:zhangyujun%2b...@gmail.com>>; 
Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [doctor] doctor CI now available

Yujun, it still cares for further (human) validation before we can make it 
voting – the email I sent earlier shows that it’s not 100% ready yet.

Carlos

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: 05 December 2016 02:00
To: Ryota Mibu; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [doctor] doctor CI now available

Nice job!

One comment inline.

On Sun, Dec 4, 2016 at 3:55 PM Ryota Mibu 
<r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>> wrote:
Hi,


Doctor CI jobs are now available and I confirmed those returns green lights 
with current codes on the master branch.

Reviewers, please check the CI results before merging a patch set.

So the verification job is not voting? Why not?

If the CI jobs were run before Dec 2nd, just trigger CI jobs again by leaving 
comment "recheck".

   doctor-verify-apex-sample-master
   doctor-verify-apex-congress-master

Note: congress works fine, with some quick hack on the POD after I installed 
OPNFV with latest apex. I'll work with apex team to fix issues I found.

Let me know if you find any problems in those CI jobs.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

[Carlos Goncalves]

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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
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:Doctor is a fault management and maintenance pro
 ject to develop and realize the consequent implementation for the OPNFV re
 ference platform.\n\n•   Doctor page: https://wiki.opnfv.org/doctor\
 n•   When: Every Tuesday 6:00-7:00 PT (Your local time)\n•   Agend
 a: https://etherpad.opnfv.org/p/doctor_meetings\n•   IRC channel: #o
 pnfv-doctor @ Freenode (Web Chat)\n•   To join: https://global.gotomeeting.com/join/819733
 085\n•   You can also dial in using your phone.\no   Access Code
 : 819-733-085\n\no   United States +1 (312) 757-3126\no   Australi
 a +61 2 8355 1040\no   Austria +43 7 2088 0034\no   Belgium +32 (0
 ) 28 93 7018\no   Canada +1 (647) 497-9350\no   Denmark +45 69 91 
 88 64\no   Finland +358 (0) 923 17 0568\no   France +33 (0) 170 95
 0 592\no   Germany +49 (0) 692 5736 7211\no   Ireland +353 (0) 15 
 360 728\no   Italy +39 0 247 92 13 01\no   Netherlands +31 (0) 208
  080 219\no   New Zealand +64 9 280 6302\no   Norway +47 75 80 32 
 07\no   Spain +34 911 82 9906\no   Sweden +46 (0) 853 527 836\no  
  Switzerland +41 (0) 435 0167 13\no   United Kingdom +44 (0) 330 2
 21 0086\n\n\nThanks\,\nThe OPNFV Doctor team\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=TU;WKST=SU
EXDATE;TZID=Pacific Standard Time:20151027T06,20151110T06,20160315T
 06,20160426T06,20160621T06,20160823T06
SUMMARY;LANGUAGE=en-US:OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150120T06
DTEND;TZID=Pacific Standard Time:20150120T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161206T210551Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:13
LOCATION;LANGUAGE=en-US:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VEVENT
SUMMARY:OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150616T06
DTEND;TZID=Pacific Standard Time:20150616T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20150616T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161206T210551Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:13
LOCATION:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150623T06
DTEND;TZID=Pacific Standard Time:20150623T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20150623T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161206T210551Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:13
LOCATION:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
BEGIN:VEVENT
SUMMARY:OPNFV Doctor weekly meeting
DTSTART;TZID=Pacific Standard Time:20150630T06
DTEND;TZID=Pacific Standard Time:20150630T07
UID:04008200E00074C5B7101A82E00870C7A6EE7031D001000
 01000F6864C6EE62FD74FBF335584FBF65967
RECURRENCE-ID;TZID=Pacific Standard Time:20150630T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161206T210551Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:13
LOCATION:GoToMeeting
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:1571821535
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

[Carlos Goncalves]

Hi Ryota,

Really great job setting up the CI infrastructure and Doctor verify jobs! Thank 
you very much!

I found a false positive. Jenkins verifies (+1) but the job have actually 
failed. The Doctor functest exists with an error exit code (!=0), though.

https://gerrit.opnfv.org/gerrit/#/c/24399/

We can take care of this in person tomorrow at the Hackfest :-)

Carlos

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 04 December 2016 08:54
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] doctor CI now available

Hi,


Doctor CI jobs are now available and I confirmed those returns green lights 
with current codes on the master branch.

Reviewers, please check the CI results before merging a patch set. If the CI 
jobs were run before Dec 2nd, just trigger CI jobs again by leaving comment 
"recheck".

   doctor-verify-apex-sample-master
   doctor-verify-apex-congress-master

Note: congress works fine, with some quick hack on the POD after I installed 
OPNFV with latest apex. I'll work with apex team to fix issues I found.

Let me know if you find any problems in those CI jobs.


Best regards,
Ryota

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] congress support in compass4nfv

[Carlos Goncalves]

Hi Henry,

Thanks for working on adding Congress support to Compass!

>From the Doctor side, we also just need Congress installed as a base service 
>available in all Compass scenarios.
There are no patches needing to be backported if Compass in Danube releases 
with OpenStack Newton or later.

Thanks,
Carlos

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: 09 October 2016 05:24
To: 'huangxiangyu'; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Herry,

Glad to be working with Compass on in this!

Congress should be installed as a basic service that is available in all 
Compass scenarios. This is what we did for Apex and JOID. There's no need for a 
specific scenario.

You can see they types of policy use cases that are in development for Congress 
at https://wiki.opnfv.org/display/copper/testing. The test cases shown there 
are integrated into Functest.

The Doctor project also depends upon Congress for some of its features.

I have an existing Ansible 
module<https://git.opnfv.org/cgit/copper/tree/components/congress/install/ansible>
 in the copper repo, that needs to be updated since I moved to a simple 
bash-script 
approach<https://git.opnfv.org/cgit/copper/tree/components/congress/install/bash>
 back in Brahmaputra, and then worked with the JOID and Apex teams on their 
installer tools (JuJu and Puppet). We can talk about updating that script at 
some meeting if you want to set it up. We don't have regular meetings in Copper 
at this time.

Thanks,
Bryan Sullivan | AT

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Friday, October 07, 2016 9:26 PM
To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>>; 
carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>
Cc: Xueyifei (Yifei Xue) <xueyi...@huawei.com<mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] congress support in compass4nfv

1.Hi, I am from compass4nfv team and see your Jira 
COMPASS-367<https://jira.opnfv.org/browse/COMPASS-367>. We can integrate 
congress into compass4nfv using ansible and want to check few things with you :

1.   How would you like to use congress? You just use its function or you 
have things based on it.

2.   Do you need a single congress scenario or a scenario with congress and 
what roles this scenario should have.

Best regards
Herry Huang

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] For the issue about the notification time is large than 1S

[Carlos Goncalves]

Hi Yujun,

Sorry for the delay...

I don’t have a local Apex environment to extract and provide you with the 
information you requested, sorry.

Carlos

From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: 12 September 2016 08:58
To: Souville, Bertrand; Carlos Goncalves; dong.wenj...@zte.com.cn; 
r-m...@cq.jp.nec.com; tomi.juvo...@nokia.com
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] For the issue about the notification 
time is large than 1S

Hi, Carlos

According to the data collected by @Wenjuan, it seems when the test fails, most 
time is consumed by the inspector api disable_compute_host[1]

if event_type == 'compute.host.down':
inspector.disable_compute_host(hostname)

I checked the source code and it looks it will iterate through the server list 
to set them to error state. So I wonder if it is related to the total number of 
server in the test environment.

Could you please provide the log in apex environment so we can dig further to 
find out the root cause?

BTW: as @Tomi pointed out, the inspector should be topology aware, knowing all 
VM's on the host, so I think we may create the server list
in initialization phase and use the saved list when processing 
`compute.host.down` event. This will be a better emulation of real inspector.

[1] https://git.opnfv.org/cgit/doctor/tree/tests/inspector.py#n63


On Fri, Sep 9, 2016 at 7:15 PM Souville, Bertrand 
<souvi...@docomolab-euro.com<mailto:souvi...@docomolab-euro.com>> wrote:
My understanding is that Fuel team/experts are now investigating the issue. 
Let’s give them few more days…

Bertrand

From: Carlos Goncalves 
[mailto:carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>]
Sent: Friday, September 09, 2016 11:06 AM
To: dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn>; Souville, Bertrand 
<souvi...@docomolab-euro.com<mailto:souvi...@docomolab-euro.com>>; 
r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>; 
tomi.juvo...@nokia.com<mailto:tomi.juvo...@nokia.com>; Kunzmann, Gerald 
<kunzm...@docomolab-euro.com<mailto:kunzm...@docomolab-euro.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] [doctor] For the issue about the notification 
time is large than 1S

As I’ve already commented in the patch you submitted to Gerrit [1]: no, we 
should not extend the accepted max notification time from 1s to anything higher 
than that.

Currently our Doctor tests are passing in Apex in all available PODs as well as 
local environments (e.g. devstack). For Apex, the notification time is around 
250ms which is much lower than the max 1 second. If we cannot get it green 
light in any other scenario/installer, we don’t claim any support.

Carlos

[1] https://gerrit.opnfv.org/gerrit/#/c/20627

From: dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn> 
[mailto:dong.wenj...@zte.com.cn]
Sent: 09 September 2016 07:00
To: Carlos Goncalves; 
souvi...@docomolab-euro.com<mailto:souvi...@docomolab-euro.com>; 
r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>; 
tomi.juvo...@nokia.com<mailto:tomi.juvo...@nokia.com>; 
kunzm...@docomolab-euro.com<mailto:kunzm...@docomolab-euro.com>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [doctor] For the issue about the notification 
time is large than 1S


Hi doctors,

For the issue about the notification time is large than 1S.
I check the log and find out that from the inspector received the event to 
nova-api begin to handle the reset_state is taken up most of the time, about 
over 80%. For example, the total notification time is 2.26s, the process of 
inspector takes 1.983s.

In the test inspector script, we find all the VM under all telant, and then set 
all the VM states as error.
As we need to improve the performance,but it can not be handle in a short time.

Shall we extned 1S to 3S or change back to no failed to notification time 
calculation to let functest green?
Meanwhile doing the performance improvement, then change it back?

Any suggestions will be welcome. Thank you~

BR,
dwj



董文娟   Wenjuan Dong

控制器四部 / 无线产品   Controller Dept Ⅳ. / Wireless Product Operation

[image003.jpg]

[image004.jpg]
上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922M: +86 13661996389
E: dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn>
www.ztedevice.com<http://www.ztedevice.com/>



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Stop commit count!

[Carlos Goncalves]

Hi Luke,

The point I'm trying to make is that when the work covers one change we don't 
need multiple commits and JIRA issues per file.

Two examples I've seen this happening:
  1) s/brahmaputra/colorado/ (in docs, for instance)
  2) adding license headers

I think these are good examples that we don't need a commit per file needed to 
be updated, but rather one single commit is enough and still small to review 
(even it it's +500-1000 lines in case of adding license headers). Committers 
and PTL should spot these cases and merge in one before accepting.

Maybe it' not about commit count but less experience contributing in OSS 
communities, may be it is...

Carlos

> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On Behalf Of Luke Hinds
> Sent: 30 August 2016 15:23
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] Stop commit count!
> 
> Hi Carlos,
> 
> Are we sure its not a process the PTL may prefer? I find some folk don't like
> commits that cover more then one change, and instead prefer a single jira /
> commit to be used, even piecemeal for small changes.
> 
> To digress though, Open Source projects do have a lot of cases of people
> bending the rules to appear more prolific (stackalytics.com has had its fair
> share). This is where I wonder if we should not tout 'top contributors' as
> metric of merit.
> 
> Luke
> 
> 
> On 30/08/16 13:40, Carlos Goncalves wrote:
> > Hi folks,
> >
> >
> >
> > I'm sorry for bringing this up to the list but it came to my attention
> > some time ago now of a continued practice carried by some
> > contributors/committers that I don't think we as community would like
> > to continue supporting, not to say tolerant. I'm talking about commit
> > counts for the sake of whatever reasons you/your organization may have
> > behind.
> >
> >
> >
> > While I don't want to go into details and list individual
> > contributions, one example is creating JIRA issues and commits per small
> change (e.g.
> > adding license headers to files) when it is more than obvious and
> > desired to everyone to have just a single JIRA and commit. Commit
> > count is not the way how you can show the project you're involved in
> > is more or less active or meeting expected goals, and bumping up
> > yourself/organization in the top committer list is, well, you know...!
> >
> >
> >
> > Commit count can be an excellent metric to evaluate how an
> > individual/organization/project performs when done well. Trying to
> > work-around that, cheat if you will, should be pinpointed and resolved
> > -- in the open or not, I personally don't care.
> >
> >
> >
> > 
> >
> >
> >
> > Thanks,
> >
> > Carlos
> >
> >
> >
> >
> >
> > ___
> > opnfv-tech-discuss mailing list
> > opnfv-tech-discuss@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> >
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Stop commit count!

[Carlos Goncalves]

Hi folks,

I'm sorry for bringing this up to the list but it came to my attention some 
time ago now of a continued practice carried by some contributors/committers 
that I don't think we as community would like to continue supporting, not to 
say tolerant. I'm talking about commit counts for the sake of whatever reasons 
you/your organization may have behind.

While I don't want to go into details and list individual contributions, one 
example is creating JIRA issues and commits per small change (e.g. adding 
license headers to files) when it is more than obvious and desired to everyone 
to have just a single JIRA and commit. Commit count is not the way how you can 
show the project you're involved in is more or less active or meeting expected 
goals, and bumping up yourself/organization in the top committer list is, well, 
you know...!

Commit count can be an excellent metric to evaluate how an 
individual/organization/project performs when done well. Trying to work-around 
that, cheat if you will, should be pinpointed and resolved -- in the open or 
not, I personally don't care.



Thanks,
Carlos

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

[Carlos Goncalves]

BEGIN:VCALENDAR
METHOD:CANCEL
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=Carlos Goncalves:MAILTO:carlos.goncal...@neclab.eu
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='fuqiao':M
 AILTO:fuq...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='zhang.jun
 3...@zte.com.cn':MAILTO:zhang.ju...@zte.com.cn
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Juvonen, 
 Tomi (NSN - FI/Espoo)'":MAILTO:tomi.juvo...@nsn.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ryota Mib
 u':MAILTO:r-m...@cq.jp.nec.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dirk Kutsc
 her:MAILTO:dirk.kutsc...@neclab.eu
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kunzmann,
  Gerald'":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ken Gray 
 (kegray)':MAILTO:keg...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Piyush Sa
 rwal':MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'CHIOSI, M
 ARGARET T'":MAILTO:mc3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'BRAGG, DE
 AN L'":MAILTO:db2...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Paul-Andr
 e Raymond':MAILTO:paul-andre.raym...@nexius.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dilip D K
 andlur':MAILTO:kand...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Seiler, G
 lenn'":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jeff Shar
 pe':MAILTO:jeff.sha...@adlinktech.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yunchao h
 u':MAILTO:yunchao...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Raymond N
 ugent':MAILTO:raymond.nug...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ganesh Ra
 jan':MAILTO:gan...@pensanetworks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Peter Poz
 ar':MAILTO:peter.po...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tom Nadea
 u':MAILTO:tnad...@brocade.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Saxena, V
 inay (DT - HP)'":MAILTO:vinay.sax...@hp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Charles H
 ale':MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Terry Dav
 is':MAILTO:tda...@clearpathnet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Smith, Ke
 vin M'":MAILTO:kevin.m.sm...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Scott Man
 sfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Brian Lee
 ':MAILTO:b...@ait.ie
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Fahd Abid
 i':MAILTO:fab...@ezchip.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Manuel Re
 bellon':MAILTO:mrebel...@sandvine.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'SULLIVAN,
  BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'MORTON, A
 LFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Snigs_Muk
 hopadh...@dell.com':MAILTO:snigs_mukhopadh...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Don Clark
 e':MAILTO:d.cla...@cablelabs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'HU, BIN'":
 MAILTO:bh5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Alexandru
  Vaduva':MAILTO:alexandru.vad...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Finucane,
  Stephen'":MAILTO:stephen.finuc...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Christoph
 er Adams':MAILTO:chris.ad...@itential.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Michael C
 ameron':MAILTO:michael.came...@ericsson.com

Re: [opnfv-tech-discuss] ##freemail## [doctor][fuel] how to modify ceilometer configuration for doctor testing

[Carlos Goncalves]

Please see my comments in-line.

> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> Sent: 16 August 2016 07:33
> To: Yujun Zhang; TECH-DISCUSS OPNFV
> Cc: Carlos Goncalves; dong.wenj...@zte.com.cn; Daniel Smith
> (daniel.sm...@ericsson.com)
> Subject: RE: ##freemail## [doctor][fuel] how to modify ceilometer
> configuration for doctor testing
> > If I understand it correctly, the major issue is that by default fuel
> > installs ceilometer with no notifiers configured, i.e. `- notifier://`
> > while doctor requires a topic setting i.e. `-
> > notifier://?topic=alarm.all`
> 
> Doctor team is not only one who need this config, but there could be other
> users who need this config in order to use/provide event-alarm. Actually,
> fuel seems to install aodh-listener, which is for event-alarm evaluation and
> listens bus with topic=alarm.all, in default. Fuel, however, doesn't configure
> event_pipeline.yaml of ceilometer correctly, so aodh-listener would be
> hanging a silent message bus. This is certainly a bug in fuel.
> 
> Apex had the same issue, but they already fixed it.
> 
> In ceilometer project, we had a discussion that we shouldn't send notification
> to aodh by setting this config *in default*, as it is different service, 
> although
> is in the same telemetry umbrella. And, we left this config to an integrator
> and a packager.

+1.


> > Since there is no perfect way to resolve it, I would propose we choose
> > a less risky way at the release window. What about we modify the
> > configuration on the fly in doctor testing script and restore to origin when
> the test is done. This could be considered as part of the preparation of
> testing environment.
> 
> +1
> 
> It should be easier to land.

I do not agree with this approach. I am not going to repeat myself here again 
(please refer to my comments in Gerrit [1]). I will only add that activating 
the plugin only during doctor test scripts means we don't test for possible 
conflicts with other scenarios which may happen later on at production stage. 
OPNFV as software is supposed to deliver an integrated NFV platform. If we 
cannot even validate that OPNFV-enabled scenarios are functional and don't 
conflict among each other we are failing at fundamental key points 
(integration, testing and validation) we so much try to achieve and deliver.

This is my personal view as things should be conducted and I would expect to 
see in any integrated open-source platform. In the end democracy should win, 
and I am only one of many Doctor contributors with +2 vote rights.

[1] https://gerrit.opnfv.org/gerrit/18285

Thanks,
Carlos

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss