[opnfv-tech-discuss] [opnfvdocs] doumentation link patch?

2016-08-16 Thread joehuang 
Multisite documentation is ready for configuration guide, installation guide 
and user guide. https://git.opnfv.org/cgit/opnfvdocs/tree/docs

I am confused with the https://wiki.opnfv.org/display/DOC/Userguide, 
https://wiki.opnfv.org/display/DOC/Configurartion+guide, 
https://wiki.opnfv.org/display/DOC/Installation+procedure

Should we submit a pacth in OPNFV doc git repository to include multisite 
documentation? In release B, only need to submit documentation to Multisite 
project folder, and then the documentation is merged automatically in OPNFV 
documentation.

Look forward to your reply. Thanks

Best Regards
Chaoyi Huang(joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] jenkins postbuildscript plugin

2016-08-16 Thread Dan Radez 
Fatih was your suggestion to use the postbuildscript plugin an
endorsement to install it too?

Aric wanted to double check that you were on board with it before it was
installed. I could always just to a clean up a the start of the build
instead of at the end of every build.

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

[opnfv-tech-discuss] Updated Invitation: OPNFV Colorado Release meeting @ Tue Aug 23, 2016 7am - 8am (PDT) (dmcbr...@linuxfoundation.org)

2016-08-16 Thread dmcbride 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20160823T07
DTEND;TZID=America/Los_Angeles:20160823T08
DTSTAMP:20160816T175407Z
ORGANIZER;CN=dmcbr...@linuxfoundation.org:mailto:dmcbride@linuxfoundation.o
 rg
UID:9pcd4v7qpnvh1jgev4igbqf...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=hkirk...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:hkirksey@linuxfo
 undation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-project-le...@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-pro
 ject-le...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=dmcbr...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:dmcbride@linuxfounda
 tion.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Narinder Gupta;X-NUM-GUESTS=0;X-RESPONSE-COMMENT="will join after 3
 0 minutes as in partner call from 10:00 till 10:30":mailto:narinder.gupta@c
 anonical.com
RECURRENCE-ID;TZID=America/Los_Angeles:20160823T08
CREATED:20160328T215211Z
DESCRIPTION:IRC channel:  opnfv-release\n\nPlease join my meeting from your
  computer\, tablet or smartphone.\nhttps://www.gotomeeting.com/join/9717896
 29\n\nYou can also dial in using your phone.\n\nAustralia: +61 2 8355 1039\
 nAustralia (toll-free): 1 800 189 049\nCanada: +1 (647) 497-9379\nCanada (t
 oll-free): 1 888 299 1889\nChina (toll-free): 4008 866143\nFrance: +33 (0) 
 170 950 589\nFrance (toll-free): 0 805 541 043\nGermany: +49 (0) 692 5736 7
 301\nGermany (toll-free): 0 800 723 5120\nHong Kong (toll-free): 30713171\n
 India (toll-free): 000 800 852 1424\nIreland (toll-free): 1 800 946 534\nIr
 eland: +353 (0) 15 360 757\nIsrael (toll-free): 1 809 452 627\nJapan (toll-
 free): 0 120 352 900\nKorea\, Republic of (toll-free): 0806110880\nRussian 
 Federation (toll-free): 8 800 100 6217\nSpain: +34 932 75 1230\nSpain (toll
 -free): 800 900 578\nSweden: +46 (0) 852 500 516\nSweden (toll-free): 020 9
 80 768\nTaiwan (toll-free): 0 800 666 674\nUnited Kingdom: +44 (0) 330 221 
 0099\nUnited Kingdom (toll-free): 0 800 031 4726\nUnited States: +1 (669) 2
 24-3318\nUnited States (toll-free): 1 866 899 4679\n\nAccess Code: 971-789-
 629\nView your event at https://www.google.com/calendar/event?action=VIEW
 id=OXBjZDR2N3FwbnZoMWpnZXY0aWdicWZ2dnNfMjAxNjA4MjNUMTUwMDAwWiBvcG5mdi10ZWNo
 LWRpc2N1c3NAbGlzdHMub3BuZnYub3Jn=MjgjZG1jYnJpZGVAbGludXhmb3VuZGF0aW9uLm
 9yZzY1YmY4N2YwODM2ZTM4ZDZkZGJlYmEwYTNhMGMzMjRkNmEwYTcxY2Y=America/Los_A
 ngeles=en.
LAST-MODIFIED:20160816T175407Z
LOCATION:https://www.gotomeeting.com/join/971789629
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:OPNFV Colorado Release meeting
TRANSP:OPAQUE
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
BEGIN:VALARM
ACTION:NONE
TRIGGER;VALUE=DATE-TIME:19760401T005545Z
X-WR-ALARMUID:0A12D53D-754E-4D89-8287-131EBB31D4D9
UID:0A12D53D-754E-4D89-8287-131EBB31D4D9
ACKNOWLEDGED:20160816T145024Z
X-APPLE-DEFAULT-ALARM:TRUE
END:VALARM
END:VEVENT
END:VCALENDAR


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

[opnfv-tech-discuss] Pharos Planning Week

2016-08-16 Thread Morgan, Jack 
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Malla, Mal
 athi":MAILTO:malathi.ma...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Daniel Smi
 th:MAILTO:daniel.sm...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sen, Prodi
 p":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Roberttao:
 MAILTO:robert...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mario Torr
 ecillas Rodriguez:MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Fatih Degi
 rmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dan Wester
 berg:MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mishael We
 xler:MAILTO:mishael.wex...@huawei.com
DESCRIPTION;LANGUAGE=en-US:Resending this as we swapped Wednesday and Thurs
 day’s topics\n\n\nPharos Team..\n\nThere are several issues that need in
 put and focus. I’m scheduling a daily meeting for next week. I’ll be m
 eeting at the same time and location each day to work through the agenda b
 elow.  All are welcome to join any of these meetings and provide your inpu
 t. Pharos committers should attend as many meetings as they can. Thanks in
  advance!\n\n\nGoToMeeting (6:00 am PST / 14:00 GMT)\nPlease join my meeti
 ng from your computer\, tablet or smartphone.\nhttps://global.gotomeeting.
 com/join/349781141\n\nYou can also dial in using your phone.\nUnited State
 s (Toll-free): 1 866 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess
  Code: 349-781-141\n\nMore phone numbers\nAustralia : +61 2 8355 1039\nAus
 tria : +43 7 2088 1033\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 49
 7-9379\nDenmark : +45 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance 
 : +33 (0) 170 950 585\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0)
  19 030 050\nItaly : +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208
 \nNew Zealand : +64 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 
 82 9890\nSweden : +46 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\n
 United Kingdom : +44 (0) 330 221 0099\nFirst GoToMeeting? Try a test sessi
 on: http://help.citrix.com/getready\n\n\nAgenda\n\nMonday:\n•   Phar
 os LAAS -  topics\no  
  discussion on scope of project\no   define milestones and roadmap\n
 •   Pharos JIRA project clean up (link)\n
 \nTuesday:\n•   Pharos Specification\no   discussion current sta
 te and updates needed for Colorado release\n\nWednesday\n•   Pharos 
 Dashboard - topics\no
discussion on scope of project\no   define milestones and roadm
 ap\n\nThursday\n•   Pharos Validator (link)\no   discussion on scope of project\no   
 define milestones and roadmap\n\nFriday\n•   Colorado Release (l
 ink)\n
 o   git branching – final review\no   documentation – final re
 view\n•   D release planning: Wiki and JIRA\n\n
SUMMARY;LANGUAGE=en-US:Pharos Planning Week
DTSTART;TZID=Pacific Standard Time:20160817T06
DTEND;TZID=Pacific Standard Time:20160817T07
UID:04008200E00074C5B7101A82E00800A51F19A6F3D101000
 01D9CF122929DF842A5845D63E9C5CE86
RECURRENCE-ID;TZID=Pacific Standard Time:20160817T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160816T150421Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:GTM

[opnfv-tech-discuss] Pharos Planning Week

2016-08-16 Thread Morgan, Jack 
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@li
 sts.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Malla, Mal
 athi":MAILTO:malathi.ma...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Daniel Smi
 th:MAILTO:daniel.sm...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sen, Prodi
 p":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Roberttao:
 MAILTO:robert...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mario Torr
 ecillas Rodriguez:MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Fatih Degi
 rmenci:MAILTO:fatih.degirme...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Dan Wester
 berg:MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Mishael We
 xler:MAILTO:mishael.wex...@huawei.com
DESCRIPTION;LANGUAGE=en-US:Resending this as we swapped Wednesday and Thurs
 day’s topics\n\n\nPharos Team..\n\nThere are several issues that need in
 put and focus. I’m scheduling a daily meeting for next week. I’ll be m
 eeting at the same time and location each day to work through the agenda b
 elow.  All are welcome to join any of these meetings and provide your inpu
 t. Pharos committers should attend as many meetings as they can. Thanks in
  advance!\n\n\nGoToMeeting (6:00 am PST / 14:00 GMT)\nPlease join my meeti
 ng from your computer\, tablet or smartphone.\nhttps://global.gotomeeting.
 com/join/349781141\n\nYou can also dial in using your phone.\nUnited State
 s (Toll-free): 1 866 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess
  Code: 349-781-141\n\nMore phone numbers\nAustralia : +61 2 8355 1039\nAus
 tria : +43 7 2088 1033\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 49
 7-9379\nDenmark : +45 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance 
 : +33 (0) 170 950 585\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0)
  19 030 050\nItaly : +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208
 \nNew Zealand : +64 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 
 82 9890\nSweden : +46 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\n
 United Kingdom : +44 (0) 330 221 0099\nFirst GoToMeeting? Try a test sessi
 on: http://help.citrix.com/getready\n\n\nAgenda\n\nMonday:\n•   Phar
 os LAAS -  topics\no  
  discussion on scope of project\no   define milestones and roadmap\n
 •   Pharos JIRA project clean up (link)\n
 \nTuesday:\n•   Pharos Specification\no   discussion current sta
 te and updates needed for Colorado release\n\nWednesday\n•   Pharos 
 Dashboard - topics\no
discussion on scope of project\no   define milestones and roadm
 ap\n\nThursday\n•   Pharos Validator (link)\no   discussion on scope of project\no   
 define milestones and roadmap\n\nFriday\n•   Colorado Release (l
 ink)\n
 o   git branching – final review\no   documentation – final re
 view\n•   D release planning: Wiki and JIRA\n\n
SUMMARY;LANGUAGE=en-US:Pharos Planning Week
DTSTART;TZID=Pacific Standard Time:20160818T06
DTEND;TZID=Pacific Standard Time:20160818T07
UID:04008200E00074C5B7101A82E00800A51F19A6F3D101000
 01D9CF122929DF842A5845D63E9C5CE86
RECURRENCE-ID;TZID=Pacific Standard Time:20160818T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160816T150422Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:3
LOCATION;LANGUAGE=en-US:GTM

[opnfv-tech-discuss] Bin will stand in today at TSC

2016-08-16 Thread SULLIVAN, BRYAN L 

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

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

2016-08-16 Thread 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

Re: [opnfv-tech-discuss] [SFC] multiple compute nodes with Tacker

2016-08-16 Thread Manuel Buil 
Hi Tim,

You still need to do the vxlan workaround. OVS 2.5.90 supports two 
alternatives: eth+nsh or vxlan-gpe+eth+nsh between SF <> SFF. However, ODL 
is currently not capable to render the first one, so we need to do the 
vxlan-gpe+eth+nsh and thus, the workaround. Brady started to implement the 
support for eth+nsh but he did not manage to do it before his vacations. 
Hopefully, we'll get that in September.

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Monday, August 15, 2016 11:39 PM
To: Manuel Buil; Yi Y Yang; Sam Hague
Cc: Brady Allen Johnson; OPNFV Tech
Subject: [SFC] multiple compute nodes with Tacker

Expanding to larger audience...

I tested out Apex today with the ODL build Brady provided.  I found there were 
a few updates needed in Tacker and pushed a patch to the colorado branch:
https://github.com/trozet/tacker/commit/d876584242781726d2e4403e69b9d15c08765625

I then created the following nova instances/tacker VNFs:
https://goo.gl/photos/F59h6V31fcQSzVFt6

The chain I created was this:
testVNF4->testVNF5

The curl to the http server failed (typical classifier matching on source port 
2000, dest port 80), and I don't see any packets hitting the vxlan tool on 
either VNF.  However, I do see packets hitting the classifier.  Flow gist:
https://gist.github.com/trozet/3161092c62fdc6582508e7779e445bf1

I did not use the VXLAN workaround (aka the kernel host route).  I thought this 
was not required anymore with OVS 2.5.90.  Yi can you comment here?

I haven't had a chance to dig into the flows yet, but if anyone sees the root 
cause of the problem, let me know.

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" 
Cc: "Brady Allen Johnson" 
Sent: Monday, August 15, 2016 12:27:23 PM
Subject: RE: Creating symmetric chains with tacker

Ok!

I did not have time to try that as we are encountering some bugs in Netvirt and 
I am preparing the demo for Seattle. Please update us if you make it work with 
several compute nodes :).

Regards,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Monday, August 15, 2016 3:00 PM
To: Manuel Buil
Cc: Brady Allen Johnson
Subject: Re: Creating symmetric chains with tacker

Hi Manuel,
Yeah I don't think I ever accounted for that.  We would need to look at the 
driver call when ODL creates the reverse chain, and instantiate 2 chains in 
tacker to do that.  I just got my setup to work with the ODL Brady provided and 
have a clean deployment.  I was going to start looking at using 2 compute nodes 
today and coming up with a fix for that one.

Will respond to this email when I have more info/fixes.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Manuel Buil" 
To: "Tim Rozet" , "Brady Allen Johnson" 

Sent: Monday, August 15, 2016 8:22:55 AM
Subject: RE: Creating symmetric chains with tacker

Hey Tim,

I tried today and it works :). However, it is impossible to create a 
classification rule on the second chain which is created (the symmetric chain), 
right? 

Thanks,
Manuel

-Original Message-
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Tuesday, August 09, 2016 5:25 PM
To: Brady Allen Johnson
Cc: Manuel Buil
Subject: Re: Creating symmetric chains with tacker

Hi Guys,
Simply invoke --symmetrical True when creating a chain:
https://github.com/trozet/python-tackerclient/blob/SFC_refactor/tackerclient/tacker/v1_0/sfc/sfc.py#L41

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Brady Allen Johnson" 
To: "Manuel Buil" , "Tim Rozet" 
Sent: Tuesday, August 9, 2016 7:58:42 AM
Subject: Re: Creating symmetric chains with tacker

Tim,

Just a bit of context: to create symmetric service chains, there is a boolean 
field in the SFC, SFP, and RSP called "is_symmetric" (or something very 
similar) that would need to be set to true. Im pretty sure now you either dont 
set it, or explicitly set it to false. When the field is true, then ODL SFC 
will create a second, symmetric service chain.

Thanks,

Brady


On 09/08/16 11:21, Manuel Buil wrote:
>
> Hi Tim,
>
> Is it possible to create symmetric chains in ODL with a tacker 
> command? I cannot find the command to do so L.
>
> Thanks,
>
> Manuel
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

2016-08-16 Thread Kunzmann, Gerald 
Hi all,

+1 to go for the least risky approach for Colorado.

For D release and after the Fuel bug is fixed, we can optimize and change to a 
different approach.

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Dienstag, 16. August 2016 07:33
To: Yujun Zhang ; TECH-DISCUSS OPNFV 

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

Hi,


> 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.

> 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.


Best,
Ryota

> -Original Message-
> From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
> Sent: Tuesday, August 16, 2016 11:51 AM
> To: TECH-DISCUSS OPNFV
> Cc: Mibu Ryota(壬生 亮太); carlos.goncal...@neclab.eu; 
> dong.wenj...@zte.com.cn
> Subject: ##freemail## [doctor][fuel] how to modify ceilometer 
> configuration for doctor testing
> 
> There has been quite a lot of discussion on how to deploy doctor test with 
> fuel installer [1] [2].
> 
> 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`
> 
> 
> On both sides, we agree that the configuration required for one 
> scenario should not affect other scenarios. And we almost agree that 
> it can hardly be done if the scenarios requires different configuration. We 
> need either modify the configuration with a scenario based plugin 
> (fuel-doctor-plugin) [3] or the affected service (ceilometer).
> 
> 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.
> 
> We may leave the dispute on how to handle it gracefully and safely to next 
> release. What do you guys think?
> 
> [1] https://gerrit.opnfv.org/gerrit/#/c/18285/
> [2] https://jira.opnfv.org/browse/FUEL-159
> [3] https://github.com/openzero-zte/fuel-plugin-doctor
> 

___
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