[opnfv-tech-discuss] Canceled: Pharos Bi-Weekly Meeting

[Morgan, Jack]

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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, February 15\, 2017 6:00 AM-7:0
 0 AM. (UTC-08:00) Pacific Time (US & Canada)\nWhere: GTM and #opnfv-pharos
 \n\n*~*~*~*~*~*~*~*~*~*\n\nCanceling due to Open Source Leadership Summit\
 n\nPharos Bi-Weekly Meeting Details\n\n   *   Weekly on Wednesday at 6:00 
 PST or 14:00 UTC\n   *   GTM Link https://global.gotomeeting.com/join/8197
 33085\n   *   Meeting Agenda at Pharos Meetings in Pharos wiki page\n   *   Minutes at Pharos
  Meetings wiki page\n   * 
   IRC #opnfv-pharos on freenode.net\n   *   You can also dial in using you
 r phone with Access Code: 819-733-085\n   *   United States +1 (312) 757-3
 126\n   *   Australia +61 2 8355 1040\n   *   Austria +43 7 2088 0034\n   
 *   Belgium +32 (0) 28 93 7018\n   *   Canada +1 (647) 497-9350\n   *   De
 nmark +45 69 91 88 64\n   *   Finland +358 (0) 923 17 0568\n   *   France 
 +33 (0) 170 950 592\n   *   Germany +49 (0) 692 5736 7211\n   *   Ireland 
 +353 (0) 15 360 728\n   *   Italy +39 0 247 92 13 01\n   *   Netherlands +
 31 (0) 208 080 219\n   *   New Zealand +64 9 280 6302\n   *   Norway +47 7
 5 80 32 07\n   *   Spain +34 911 82 9906\n   *   Sweden +46 (0) 853 527 83
 6\n   *   Switzerland +41 (0) 435 0167 13\n   *   United Kingdom +44 (0) 3
 30 221 0086\n   *\n
SUMMARY;LANGUAGE=en-US:Canceled: Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20170215T06
DTEND;TZID=Pacific Standard Time:20170215T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20170215T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170215T045831Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:14
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:14
X-MICROSOFT-CDO-OWNERAPPTID:529696736
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
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] [mano-wg] support Keystone Api V2 and V3 in OPNFV Release D and E

[Prakash Ramchandran]

Hi all,

We have some indication from Compass as they need to downgrade their efforts to 
support Keystone V2.0  for Opera in D , where as JOID needs to upgrade its 
support for Keystone v3.0 API for E.

Please comment if my understanding is correct by installers and we can discuss 
this in tomorrow's MANO WG meeting  for E-Release minimum baselines suggested 
by  David  McBride Release manager OPNFV as OpenStack Ocata and Keystone API 
v3.0.

Thanks
Prakash

[cid:jira-generated-image-avatar-b775a13f-c1b8-459a-a31f-4cc6ffefbeb8]

Harry Huang 
commented on [Improvement] 
COMPASS-524




Re: Support Keystone Api V2 



Compass now has a open-o scenario (os-nosdn-openo-noha) has this Api issue 
which mainly because open-o sun release and juju2.0 are using keystone Api v2 
while compass creates keystone Api v3 as default. This is the only scenario 
which may fail because of Api v3 in compass. However you can still be 
authorized with api v2 openrc file to access almost full openstack service 
except some identity function. So far compass manage to install open-o and 
juju-controller using api v2 rc file to authorize with v3. Considering open-o 
mercury is scheduled to release in this April, we may not be talking this issue 
two months later.


[Add Comment]

Add Comment






This message was sent by Atlassian JIRA (v7.0.4#70113-sha1:3aced62)

[Atlassian logo]




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

Re: [opnfv-tech-discuss] Functest ODL-SFC

[Manuel Buil]

Hi Pau,

It seems like the classifier rules are not in place when doing the first 
test. Do you get something like this:


2017-02-14 09:19:38,750 - ODL_SFC - INFO - It took 197.696654081 seconds

Before your first like ". INFO - Test SSH"?

How many computes are you using? It is the first time I see such a big 
number of seconds!


Thanks,
Manuel


On 02/14/2017 06:46 PM, KA PDE wrote:

Hi Michael, thanks for checking. I've progressed a bit on my side.

I'm using matching Fuel and Functest versions. I've been able to test 
successfully on the non-HA scenario only, though.


2017-02-14 09:19:11,691 - ODL_SFC - INFO - Test SSH
2017-02-14 09:19:12,900 - ODL_SFC - INFO - Connection to 11.0.0.4 22 
port [tcp/ssh] succeeded!
2017-02-14 09:19:12,901 - ODL_SFC - ERROR - TEST 1 [FAILED] ==> SSH 
NOT BLOCKED

2017-02-14 09:19:14,029 - ODL_SFC - INFO - Test HTTP
2017-02-14 09:19:14,603 - ODL_SFC - INFO - Connection to 11.0.0.4 80 
port [tcp/http] succeeded!

2017-02-14 09:19:14,604 - ODL_SFC - INFO - TEST 2 [PASSED] ==> HTTP WORKS
2017-02-14 09:19:14,604 - ODL_SFC - INFO - Changing the classification
2017-02-14 09:19:38,750 - ODL_SFC - INFO - It took 197.696654081 seconds
2017-02-14 09:21:07,920 - ODL_SFC - INFO - Test HTTP
2017-02-14 09:21:13,412 - ODL_SFC - INFO - nc: connect to 11.0.0.4 
port 80 (tcp) timed out: Operation now in progress
2017-02-14 09:21:13,413 - ODL_SFC - INFO - TEST 3 [PASSED] ==> HTTP 
Blocked

2017-02-14 09:21:13,413 - ODL_SFC - INFO - Test SSH
2017-02-14 09:21:14,056 - ODL_SFC - INFO - Connection to 11.0.0.4 22 
port [tcp/ssh] succeeded!

2017-02-14 09:21:14,057 - ODL_SFC - INFO - TEST 4 [PASSED] ==> SSH Works
2017-02-14 09:21:14,057 - ODL_SFC - ERROR - SFC TESTS: FAIL :( FOUND 1 
FAIL )


I guess this error is minor.

Thanks again and best regards,

Pau

2017-02-14 11:24 GMT+01:00 Michael Polenchuk >:


Hi,

We've rechecked it out twice.
With fuel colorado 3.0 iso and functest docker image (tag;
colorado.3.0) we've successful tests run:
  * healthcheck,
  * sdn_suites: ['odl'],
  * features: ['promise', 'odl-sfc']

I guess you're using latest functest image against fuel colorado
iso or vice versa.


On Tue, Feb 14, 2017 at 1:24 AM, KA PDE > wrote:

After using the compressed image shared in this list some
weeks ago I progressed a bit more until...:


+--+--+-+---++
| id   | name |
description | acl_match_criteria  
 | status |


+--+--+-+---++
| 8b04a3b5-8316-4415-aa04-6c8454ec78a4 | red_ssh  |  
  | {u'source_port': 0, u'protocol': 6, u'dest_port': 22} |

ACTIVE |
| e6e14d65-8adf-4cb9-970f-545c433723c4 | red_http |  
  | {u'source_port': 0, u'protocol': 6, u'dest_port': 80} |

ACTIVE |

+--+--+-+---++
2017-02-13 19:40:08,943 - ODL_SFC - INFO - Instance name and
ip
ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142
2017-02-13 19:40:08,944 - ODL_SFC - INFO - Waiting for
instance
ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142
to come up
2017-02-13 19:40:22,996 - ODL_SFC - INFO - SF:172.16.0.142 is
reachable
2017-02-13 19:40:33,554 - ODL_SFC - INFO - Instance name and
ip
ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143
2017-02-13 19:40:33,554 - ODL_SFC - INFO - Waiting for
instance
ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143
to come up
2017-02-13 19:40:36,577 - ODL_SFC - INFO - SF:172.16.0.143 is
reachable
2017-02-13 19:40:42,271 - ODL_SFC - INFO - Instance name and
ip server:172.16.0.144
2017-02-13 19:40:42,271 - ODL_SFC - INFO - Waiting for
instance server:172.16.0.144 to come up
2017-02-13 19:40:46,299 - ODL_SFC - INFO - Server:172.16.0.144
is reachable
2017-02-13 19:40:53,037 - ODL_SFC - INFO - Instance name and
ip client:172.16.0.145
2017-02-13 19:40:53,037 - ODL_SFC - INFO - Waiting for
instance client:172.16.0.145 to come up
2017-02-13 19:40:59,077 - ODL_SFC - INFO - Client:172.16.0.145
is reachable
2017-02-13 19:41:08,133 - ODL_SFC - INFO - Instance name and
ip server:172.16.0.146
2017-02-13 19:41:08,133 - ODL_SFC - INFO - Waiting for
instance 

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #36497] Apply to contribute to compass4nfv

[Aric Gardner via RT]

Hi, Qiwei Li

I have sent you an invite to join the compass4nfv contributors group.
If you don't have one, this will prompt you to create a linux
foundation account.
Please choose a username without spaces or special characters as
gerrit requires a valid unix username.
You will also need to sign the individual CLA and Upload an ssh key in
gerrit, this can be done by clicking on your user name once logged
into gerrit.

Don't hesitate to contact me via helpdesk
(opnfv-helpd...@rt.linuxfoundation.org ) if you have any further
questions.

Regards,
Aric

On Thu, Feb 9, 2017 at 9:58 PM, Qiwei Li via RT
 wrote:
>
> Thu Feb 09 21:58:19 2017: Request 36497 was acted upon.
>  Transaction: Ticket created by qiwei...@huawei.com
>Queue: OPNFV Helpdesk
>  Subject: Apply to contribute to compass4nfv
>Owner: Nobody
>   Requestors: qiwei...@huawei.com
>   Status: new
>  Ticket https://rt.linuxfoundation.org/Ticket/Display.html?id=36497 >
>
>
> Hi there,
>
> Could I ask for a permission to contribute to compass4nfv project? I am 
> interested in this project.
>
> My email is qiwei...@huawei.com and my username 
> in gerrit is qiwei-li-huawei.
>
> Thank you,
> Qiwei Li
>

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

Re: [opnfv-tech-discuss] [releng] No project folders/yaml files for Models & VES

[Fatih Degirmenci]

Hi,

We can create initial jobs for these projects by putting yaml files and you can 
take it from there, adding the pieces into the jobs.
Please let us know if this is good for you so we fix it.

/Fatih

On 2017-02-14, 06:05, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
GUPTA, ALOK"  wrote:

Team:

I am working within AT to define the yaml onboarding for VES. I should 
have first draft to share with the team by end of this month.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aimee Ukasick
Sent: Monday, February 13, 2017 6:47 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] No project folders/yaml files for 
Models & VES


Hi all - I would like to add the shellcheck call to Models and VES yaml 
files, but there aren't any folders and yaml files for those two projects.
Missing:
releng/jjb/models/models.yaml
releng/jjb/ves/ves.yaml

Can I just commit those files or does some sort of infra configuration have 
to be done in addition to committing those files? If yes, do I submit a ticket 
to opnfv-helpdesk for that?

Thanks in advance for your guidance.


Aimee Ukasick
AT Open Source
___
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] 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

Re: [opnfv-tech-discuss] [releng] No project folders/yaml files for Models & VES

[GUPTA, ALOK]

Team:

I am working within AT to define the yaml onboarding for VES. I should have 
first draft to share with the team by end of this month.


Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aimee Ukasick
Sent: Monday, February 13, 2017 6:47 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] No project folders/yaml files for Models 
& VES


Hi all - I would like to add the shellcheck call to Models and VES yaml files, 
but there aren't any folders and yaml files for those two projects.
Missing:
releng/jjb/models/models.yaml
releng/jjb/ves/ves.yaml

Can I just commit those files or does some sort of infra configuration have to 
be done in addition to committing those files? If yes, do I submit a ticket to 
opnfv-helpdesk for that?

Thanks in advance for your guidance.


Aimee Ukasick
AT Open Source
___
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] [SFC] Nice-to-have improvements

[Juan Vidal ALLENDE]

Hello,

In the last days we have been trying to stabilize SFC test cases and fix some 
bugs, and while doing so we discovered some other improvements that could be 
interesting. To avoid forgetting about them, I created an epic in JIRA [0]. 
Although the sprint assigned to them is Danube 1.0, this is nice-to-have, so no 
need to worry if we can't fit them into Danube.

I will ask Brady for 5 minutes to raise the topic tomorrow in the weekly 
meeting, but if you have any comments feel free to discuss them here. I hope 
that you find this useful and contribute your own suggestions as well!

Regards,
Juan

[0] https://jira.opnfv.org/browse/SFC-76
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV][VNF] VNF Upgrade

[lương hữu tuấn]

Hi,

I have a question related to the upgrade process of vnf. As mentioned in
ETSI that VNF should be upgraded. However, i do not see detailed
information about this process.

Could you guys please give me more information about it? How it is defined,
what should be done in upgrade process? Another concern is how does OPNFV
deal with the case of changing image of vnf?

Br,

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

Re: [opnfv-tech-discuss] Functest ODL-SFC

[Michael Polenchuk]

Hi,

We've rechecked it out twice.
With fuel colorado 3.0 iso and functest docker image (tag; colorado.3.0)
we've successful tests run:
  * healthcheck,
  * sdn_suites: ['odl'],
  * features: ['promise', 'odl-sfc']

I guess you're using latest functest image against fuel colorado iso or
vice versa.


On Tue, Feb 14, 2017 at 1:24 AM, KA PDE  wrote:

> After using the compressed image shared in this list some weeks ago I
> progressed a bit more until...:
>
> +--+--+-
> +---++
> | id   | name | description |
> acl_match_criteria| status |
> +--+--+-
> +---++
> | 8b04a3b5-8316-4415-aa04-6c8454ec78a4 | red_ssh  | |
> {u'source_port': 0, u'protocol': 6, u'dest_port': 22} | ACTIVE |
> | e6e14d65-8adf-4cb9-970f-545c433723c4 | red_http | |
> {u'source_port': 0, u'protocol': 6, u'dest_port': 80} | ACTIVE |
> +--+--+-
> +---++
> 2017-02-13 19:40:08,943 - ODL_SFC - INFO - Instance name and ip
> ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142
> 2017-02-13 19:40:08,944 - ODL_SFC - INFO - Waiting for instance
> ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142 to
> come up
> 2017-02-13 19:40:22,996 - ODL_SFC - INFO - SF:172.16.0.142 is reachable
> 2017-02-13 19:40:33,554 - ODL_SFC - INFO - Instance name and ip
> ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143
> 2017-02-13 19:40:33,554 - ODL_SFC - INFO - Waiting for instance
> ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143 to
> come up
> 2017-02-13 19:40:36,577 - ODL_SFC - INFO - SF:172.16.0.143 is reachable
> 2017-02-13 19:40:42,271 - ODL_SFC - INFO - Instance name and ip
> server:172.16.0.144
> 2017-02-13 19:40:42,271 - ODL_SFC - INFO - Waiting for instance
> server:172.16.0.144 to come up
> 2017-02-13 19:40:46,299 - ODL_SFC - INFO - Server:172.16.0.144 is reachable
> 2017-02-13 19:40:53,037 - ODL_SFC - INFO - Instance name and ip
> client:172.16.0.145
> 2017-02-13 19:40:53,037 - ODL_SFC - INFO - Waiting for instance
> client:172.16.0.145 to come up
> 2017-02-13 19:40:59,077 - ODL_SFC - INFO - Client:172.16.0.145 is reachable
> 2017-02-13 19:41:08,133 - ODL_SFC - INFO - Instance name and ip
> server:172.16.0.146
> 2017-02-13 19:41:08,133 - ODL_SFC - INFO - Waiting for instance
> server:172.16.0.146 to come up
> 2017-02-13 19:41:16,160 - ODL_SFC - INFO - Server:172.16.0.146 is reachable
> Traceback (most recent call last):
>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py", line
> 584, in 
> main()
>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py", line
> 485, in main
> nova_client, neutron_client)
>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py", line
> 284, in get_floating_ips
> instance.add_floating_ip(floatip)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
> line 161, in add_floating_ip
> return self.manager.add_floating_ip(self, address, fixed_address)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
> line 883, in add_floating_ip
> return self._action('addFloatingIp', server, {'address': address})
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
> line 1845, in _action
> info=info, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
> line 1856, in _action_return_resp_and_body
> return self.api.client.post(url, body=body)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
> line 483, in post
> return self._cs_request(url, 'POST', **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
> line 458, in _cs_request
> resp, body = self._time_request(url, method, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
> line 431, in _time_request
> resp, body = self.request(url, method, **kwargs)
>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
> line 425, in request
> raise exceptions.from_response(resp, body, url, method)
> novaclient.exceptions.BadRequest: No nw_info cache associated with
> instance (HTTP 400) (Request-ID: req-dd67a9f7-a992-4221-b523-891351ae9b8d)
> Exception in thread Thread-19 (most likely raised during interpreter
> shutdown):Unhandled exception in thread started by  capture_time_log at 0x7f8c6e1d3488>
> Traceback (most recent call last):
>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py", line
> 410, in capture_time_log
> rsps = ovs_logger.ofctl_time_counter(compute_clients[0])
>   File 

[opnfv-tech-discuss] [openretriever]OpenRetriever Meeting Minites

[jiaxuan]

Hi OpenRetrieverer:
1.This patch needs to be reviewed :
https://gerrit.opnfv.org/gerrit/#/c/28583/1 
2. Action for Matthew : Check whether compass know how to integrate
magnum/Ironic/Kuryr . If not, what else need we supply?
3. Ansible code which can setup container environment will be
uploaded in few days. I keep talking with the contributor. 
4. We need to provide requirements for compass4nfv before May 1. We
want to make it happen in March. 
5. Matthew create the Jenkins for openretriever.
https://git.opnfv.org/releng/tree/jjb/openretriever 
6. As Xuan Jia will be on a vacation, the meeting in 21th and 28th
will be canceled. 

Other notes please check this page :
https://etherpad.opnfv.org/p/openretriever

The next meeting will be on Marth 7th 9:00-10:00 UTC.
Xuan Jia
Project Manager
Big Data & IT Technology Research Center China Mobile Research Institute
32 Xuanwumen West Street, Xicheng Distirct, Beijing 100032, China
Mobile: (+86) 13811000575
E-mail: jiax...@chinamobile.com




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