date:20180109

[opnfv-tech-discuss] [Testperf] APAC Meeting Call

2018-01-09 Thread Yuyang (Gabriel)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=test-wg@li
 sts.opnfv.org:MAILTO:test...@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Brattain, 
 Ross B":MAILTO:ross.b.bratt...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jose Angel
  Lausuch:MAILTO:jalaus...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.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=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.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="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Rajesh Kum
 ar Tewari:MAILTO:rajesh.tew...@hsc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Radhakrish
 nan Govindan:MAILTO:gradh...@sandvine.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Randy Leve
 nsalor:MAILTO:r.levensa...@cablelabs.com
DESCRIPTION;LANGUAGE=zh-CN:Test Working Group APAC Meeting: 2nd Wednesday o
 f the month UTC 8:00-9:00 / PST  24:00-1:00 / Beijing 16:00-17:00 / IST 13
 :30-14:30\n\nWednesday GTM https://global.gotomeeting.com/join/819733085\n
 Access Code: 819-733-085\nIRC channel: #opnfv-testperf @ Freenode\n\n\nBest\,\nGabriel\n\n
SUMMARY;LANGUAGE=zh-CN:[Testperf] APAC Meeting Call
DTSTART;TZID=W. Australia Standard Time:20180110T16
DTEND;TZID=W. Australia Standard Time:20180110T17
UID:04008200E00074C5B7101A82E0082047C9BBAF57D301000
 01000E99CE5519199B2418097634502056EB9
RECURRENCE-ID;TZID=W. Australia Standard Time:20180110T16
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180110T075207Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=zh-CN:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:-926435359
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] [Bottlenecks] Minutes for Weekly Call 20180110

2018-01-09 Thread Yuyang (Gabriel)

Minutes of Bottlenecks Discussion on Jan. 10th, 2018

  *   Date and Time
 *   Thursday at 
0300-0400
 UTC, Jan. 10th, 2018
 *   Thursday at 1100-1200 Beijing, Jan. 10th, 2018
 *   Wednesday at 0800-0900 PDT, Jan. 10th, 2018
  *   Minutes
 *   Yang Yu
  *   Participants (5 peoples):
 *   Ace Lee
 *   Rutuja
 *   Shubham
 *   Gary
Agenda:

  *   Intern Reports
  *   Stress/Long Duration Testing Discussion
  *   Release Discussion
  *   Action Items Review
Discussion & Action Item

1.  IRC Minutes

  *   
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-bottlenecks/2018/opnfv-bottlenecks.2018-01-10-03.02.html

2.  Action Items

a)Ruruja investigate on stats_exporter

b)Rutuja replace collectd by barometer to see if it is able to receive 
any metric from host1

c) Shubham prepare a presentation regarding the storage testing workfow 
and explanation of the testing results

3.  Work Plan Review

  *   https://wiki.opnfv.org/display/bottlenecks/Release+Plan
  Fraser:

  *   Stress Testing in OpenStack
 *   projects in Openstack
 *   plan in its QA team
  *   Testing Framework Refactoring
 *   service registration
 *   plugin mechanism
 *   environment preparation
 *   serial or parallel executing tests
  *   Bottlenecks Analysis
 *   Algorithm & tools to determine system bottlenecks
 *   Monitoring module
  *   Stress testing
 *   Advanced stress test cases
 *   CI chain for long duration pod
 *   Reporting for long duration test
 *   VNF Scaling tests
  *   Initiate Tuning Test
  *   Initiate Container Testing
 *   K8S stress testing
 *   Container4nfv, unicore
 *   Work with installers team for Kola deployment testing
  *   Security testing
 *   Work with moon projects for test cases



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

Re: [opnfv-tech-discuss] Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

Also - any particular reason this thread is not on the tech-discuss and TSC 
list? This goes to my point about transparency. We have to always remember we 
are an open community and any proposals that affect the community need to be 
openly shared on the lists. Especially ones that address organizational issues.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: SULLIVAN, BRYAN L (BRYAN L) 
Sent: Tuesday, January 09, 2018 7:12 PM
To: 'Christopher Donley (Chris)' ; Dave Neary 
; Christopher Price ; 
m...@linuxfoundation.org; hkirk...@linuxfoundation.org; Lincoln Lavoie 
; fzdar...@redhat.com; denglin...@chinamobile.com; 
fbroc...@cisco.com; ljlam...@vmware.com; Scott Nicholas 
; trevor.coo...@intel.com; Wenjing Chu 
; glenn.sei...@windriver.com; Tianhongbo 
; dmcbr...@linuxfoundation.org; 
fuq...@chinamobile.com; Raymond Paik ; 
t.nakam...@cablelabs.com; juha.oravai...@nokia.com; tapio.tallg...@nokia.com; 
morgan.richo...@orange.com; Tim Irnich ; 
feng.xiao...@zte.com.cn; Edward Abou Arrage (Eddie Arrage, Silicon Valley NFV 
Competency Center) 
Subject: RE: Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 
11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

Note also that any member of any LFN project is (or can easily become) a member 
of all LFN projects - at least there is no financial obligation beyond LFN 
membership. So if Amdocs wants to participate in OPNFV, nothing is stopping 
them.

Infra synergy is clearly an opportunity with the LFN but we should ensure that 
any discussion on that (beyond selling proactivity toward it) is kept at a 
cross-community basis in the technical community, and not at the Board or Board 
committee level. The TAC may provide a venue for finalizing cross-community 
infra strategy but all the detailed discussion on it (including the CVP) should 
be at the level of inter-TSC dialog. We can setup cross-community focus groups 
as needed to facilitate that cross-community dialog, but it needs to remain 
open to community-level participation, and transparent.

Thanks,
Bryan Sullivan | AT

-Original Message-
From: Christopher Donley (Chris) [mailto:christopher.don...@huawei.com] 
Sent: Tuesday, January 09, 2018 11:08 AM
To: SULLIVAN, BRYAN L (BRYAN L) ; Dave Neary 
; Christopher Price ; 
m...@linuxfoundation.org; hkirk...@linuxfoundation.org; Lincoln Lavoie 
; fzdar...@redhat.com; denglin...@chinamobile.com; 
fbroc...@cisco.com; ljlam...@vmware.com; Scott Nicholas 
; trevor.coo...@intel.com; Wenjing Chu 
; glenn.sei...@windriver.com; Tianhongbo 
; dmcbr...@linuxfoundation.org; 
fuq...@chinamobile.com; Raymond Paik ; 
t.nakam...@cablelabs.com; juha.oravai...@nokia.com; tapio.tallg...@nokia.com; 
morgan.richo...@orange.com; Tim Irnich ; 
feng.xiao...@zte.com.cn; Edward Abou Arrage (Eddie Arrage, Silicon Valley NFV 
Competency Center) 
Subject: RE: Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 
11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

In the short term, my understanding is the main impact of having C under the 
LFN Board is that it opens us up for further participation (for example, from 
Amdocs, who is an LFN member but not an OPNFV member) and allows greater 
transparency.  It also encourages more cross-project discussion (you're right 
that it will take some time to work out any such details - this would just 
provide a vehicle). For OVP, I think we proceed as planned as soon as we have 
the C rechartered (which has to happen, regardless of where we put it, since 
we were originally chartered as a Board committee).

Longer-term, we'll have to work out logistical issues with how we work inside 
LFN.  As you mention, questions of scope and passing criteria would go to the 
TSC through Dovetail and/or other OPNFV testing projects.  Likewise, I think 
tests/requirements generated by other communities should be governed by their 
TSC and branding/marketing handled in the respective communities, as well (the 
top-level LFN may need to weigh in if there's a gray area between llcs).  From 
the work we've done so far, I think a lot could be reused in a combined 
environment, including the governance document, committee structure, 
operational practices, Dovetail testing framework,  and back-end 
infrastructure.  

For OPNFV, I don't anticipate a change in scope in the near term (as Dave 
mentioned). We're not talking about re-tooling.  Longer-term, maybe we add some 
tests, which

[opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 10 Jan 2017 (ww51)

2018-01-09 Thread Rao, Sridhar

Hi All,

The agenda for this week's meeting:


  1.  Development Update.
  2.  Progress Review.
  3.  TGAAS.
  4.  Consolidation of the Discussion Topics.

Meeting minutes

  *   WW50 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-12-20-16.01.html
  *   WW49 
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-12-13-16.00.html
  *   WW48  
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-11-29-16.14.html


Time: Wednesday UTC 16h00, Ireland (UTC) 16h00, PST 8h00 (UTC/GMT -8)

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings


Regards,
Sridhar K. N. Rao (Ph. D)
Architect
+91-9900088064





Spirent Communications e-mail confidentiality.

This e-mail contains confidential and / or privileged information belonging to 
Spirent Communications plc, its affiliates and / or subsidiaries. If you are 
not the intended recipient, you are hereby notified that any disclosure, 
copying, distribution and / or the taking of any action based upon reliance on 
the contents of this transmission is strictly forbidden. If you have received 
this message in error please notify the sender by return e-mail and delete it 
from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread Tina Tsou

Yes, I think so.

Thank you,
Tina

On Jan 9, 2018, at 3:50 PM, SULLIVAN, BRYAN L (BRYAN L) 
> wrote:

Re ARM arch, good point. I don’t have ARM hw and did not build this for ARM. 
You can try to build it using the script (tacker.sh) in the models build 
folder. If it works, you will need to push the container to docker hub and 
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it 
as a local container image.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com 
[mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) 
>; Tina 
Tsou >; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>; Joe Kidder 
>
Cc: 
'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows “standard_init_linux.go:178: exec user 
process caused "exec format error"”. The “sudo docker image inspect 
blsaws/models-tacker” shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) 
>; Tina Tsou 
>; Eric DMaye (Product Engineering 
Service) >; UKASICK, AIMEE L 
(AIMEE L) >
Cc: 
'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I’m not sure 
what’s going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)

Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' 
>; Tina Tsou 
>; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>
Cc: 
'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what’s going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the “tacker vnf-create” step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line

[opnfv-tech-discuss] [yardstick]//RE: yardstick tc046 failure HA test case: Control node Openstack service down - keystone

2018-01-09 Thread limingjiang

Hi Ting,

As I see from the log, it is not tc046 test case fail to pass the criteria.
It happens when the atacker ssh to log in to the controller node you specified 
in the pod.yaml,
the ssh encoutered time out and the test case failed.

This means it is not able to ssh to your node to kill the keystone process.
Could you share your pod.yaml and what kind of ssh method are you using? 
Password or pubilckey?
Also I suggest you can try to ssh to the controller node in yardstick docker 
manually to check if it's ok.

BRs,
Rex

+---+
[cid:image001.png@01D0A50A.DD5A8F20]
+ Mingjiang Li (Rex) Mobile: +86 13761275017
+ Shanghai Institute, Huawei
+ No. , Xinjinqiao Road, Pudong, Shanghai, 201206, P.R.China
+---+

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ting Wu
Sent: Tuesday, January 09, 2018 9:48 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] yardstick tc046 failure HA test case: Control 
node Openstack service down - keystone

Hi,

We are running yardstick in our arm-pod with fuel installation, there are few 
failed testcases. One of them is "opnfv_yardstick_tc046.yaml"

The testcase is to check if the keystone service is alive in all controllers in 
HA scenario.

When we manually check on the nodes,  the keystone is alive but the test case 
reported failure.  Does someone know what the pass criteria of this test case?

//login to cfg and manually check  service status, according to 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide/troubleshooting/service-status.html



ubuntu@cfg01:~$ sudo salt "ctl*" service.status apache2

ctl02.baremetal-mcp-pike-ovs-ha.local:

True

ctl01.baremetal-mcp-pike-ovs-ha.local:

True

ctl03.baremetal-mcp-pike-ovs-ha.local:

True

ubuntu@cfg01:~$ sudo salt "ctl*" cmd.run "netstat -nltp | egrep '5000|35357'"

ctl03.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.13:5000   0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14059/haproxy

tcp0  0 172.16.10.13:35357  0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14059/haproxy

ctl02.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.12:5000   0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14095/haproxy

tcp0  0 172.16.10.12:35357  0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14095/haproxy

ctl01.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.11:5000   0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14105/haproxy

tcp0  0 172.16.10.11:35357  0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14105/haproxy


//yardstick printout
2018-01-09 10:08:29,150 [INFO] yardstick.benchmark.core.task task.py:483 
Parsing task config: 
/home/opnfv/repos/yardstick/tests/opnfv/test_cases/opnfv_yardstick_tc046.yaml
2018-01-09 10:08:29,218 [INFO] yardstick.benchmark.contexts.node node.py:57 
Parsing pod file: etc/yardstick/nodes/fuel_baremetal/pod.yaml
2018-01-09 10:08:29,257 [INFO] yardstick.benchmark.core.task task.py:373 
Starting runner of type 'Duration'
Background task ended
Background task ended
Background task ended
2018-01-09 10:08:29,274 [INFO] yardstick.benchmark.runners.duration 
duration.py:46 Worker START, duration is 1s
Process Duration-ServiceHA-7429:
Traceback (most recent call last):
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/runners/duration.py", 
line 52, in _worker_process
benchmark.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/serviceha.py",
 line 47, in setup
attacker_ins.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/attacker/attacker_process.py",
 line 28, in setup
self.connection.wait(timeout=600)
  File "/home/opnfv/repos/yardstick/yardstick/ssh.py", line 374, in wait
raise SSHTimeout("Timeout waiting for '%s'", self.host)
SSHTimeout: ("Timeout waiting for '%s'", '172.16.10.12')
2018-01-09 10:18:30,210 [ERROR] yardstick.benchmark.core.task task.py:276

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread Alexandru Avadanii

Hi,
Actually you can run x86_64 containers on AArch64 just fine (and the other way 
around), provided you use the appropiate translation tools, like 
qemu-user-static.
See [1], I can't find a guide that explains how to do this step-by-step for 
containers, but I'm quite sure it's possible (I think it's enough to set up 
binfmt on the host system and mount the binary of qemu-x86_64-static in the 
expected location inside the container).

BR,
Alex

[1] https://wiki.debian.org/QemuUserEmulation


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of UKASICK, AIMEE 
L (AIMEE L)
Sent: Wednesday, January 10, 2018 2:19 AM
To: SULLIVAN, BRYAN L (BRYAN L); pramod.sud...@wipro.com; Tina Tsou; 
eric.dm...@wipro.com; Joe Kidder
Cc: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for 
Euphrates

Yes you need a Docker image compiled on ARM in order for it to run on ARM.
I've never created a Docker image for multiple architectures but I did read 
about the capability last year:
https://blog.docker.com/2017/11/multi-arch-all-the-things/
https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/

Good luck!
-
Aimee Ukasick
AT Research Advanced Technology

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 17:50
To: pramod.sud...@wipro.com; Tina Tsou; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L); 
Joe Kidder
Cc: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
Re ARM arch, good point. I don't have ARM hw and did not build this for ARM. 
You can try to build it using the script (tacker.sh) in the models build 
folder. If it works, you will need to push the container to docker hub and 
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it 
as a local container image.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com 
[mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) 
>; Tina 
Tsou >; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>; Joe Kidder 
>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows "standard_init_linux.go:178: exec user 
process caused "exec format error"". The "sudo docker image inspect 
blsaws/models-tacker" shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) 
>; Tina Tsou 
>; Eric DMaye (Product Engineering 
Service) >; UKASICK, AIMEE L 
(AIMEE L) >
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates


** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook):

Re: [opnfv-tech-discuss] yardstick tc046 failure HA test case: Control node Openstack service down - keystone

2018-01-09 Thread Lvjing (Jing Lu)

Hi,

According to the Yardstick console log, it seems that Yardstick is failed to 
login to the cfg01 node@172.16.10.12 via SSH.
What TC046 do is logining to the target node and terminating the apache2 
processes and check if the terminated processes will recover and the keystone 
service is not affected. If the process recovery time is shorter than 10s and 
the keystone service outage is within 5s, this test case will be considered as 
Pass.

The SSH info that Yardstick uses to login to the target node is written in 
'/etc/yardstick/pod.yaml'
Can you checkout this file and make sure the info is correct.
Regards,
Jing Lu
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ting Wu
Sent: Tuesday, January 09, 2018 9:48 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] yardstick tc046 failure HA test case: Control 
node Openstack service down - keystone

Hi,

We are running yardstick in our arm-pod with fuel installation, there are few 
failed testcases. One of them is "opnfv_yardstick_tc046.yaml"

The testcase is to check if the keystone service is alive in all controllers in 
HA scenario.

When we manually check on the nodes,  the keystone is alive but the test case 
reported failure.  Does someone know what the pass criteria of this test case?

//login to cfg and manually check  service status, according to 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide/troubleshooting/service-status.html



ubuntu@cfg01:~$ sudo salt "ctl*" service.status apache2

ctl02.baremetal-mcp-pike-ovs-ha.local:

True

ctl01.baremetal-mcp-pike-ovs-ha.local:

True

ctl03.baremetal-mcp-pike-ovs-ha.local:

True

ubuntu@cfg01:~$ sudo salt "ctl*" cmd.run "netstat -nltp | egrep '5000|35357'"

ctl03.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.13:5000   0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14059/haproxy

tcp0  0 172.16.10.13:35357  0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14059/haproxy

ctl02.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.12:5000   0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14095/haproxy

tcp0  0 172.16.10.12:35357  0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14095/haproxy

ctl01.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.11:5000   0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14105/haproxy

tcp0  0 172.16.10.11:35357  0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14105/haproxy


//yardstick printout
2018-01-09 10:08:29,150 [INFO] yardstick.benchmark.core.task task.py:483 
Parsing task config: 
/home/opnfv/repos/yardstick/tests/opnfv/test_cases/opnfv_yardstick_tc046.yaml
2018-01-09 10:08:29,218 [INFO] yardstick.benchmark.contexts.node node.py:57 
Parsing pod file: etc/yardstick/nodes/fuel_baremetal/pod.yaml
2018-01-09 10:08:29,257 [INFO] yardstick.benchmark.core.task task.py:373 
Starting runner of type 'Duration'
Background task ended
Background task ended
Background task ended
2018-01-09 10:08:29,274 [INFO] yardstick.benchmark.runners.duration 
duration.py:46 Worker START, duration is 1s
Process Duration-ServiceHA-7429:
Traceback (most recent call last):
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/runners/duration.py", 
line 52, in _worker_process
benchmark.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/serviceha.py",
 line 47, in setup
attacker_ins.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/attacker/attacker_process.py",
 line 28, in setup
self.connection.wait(timeout=600)
  File "/home/opnfv/repos/yardstick/yardstick/ssh.py", line 374, in wait
raise SSHTimeout("Timeout waiting for '%s'", self.host)
SSHTimeout: ("Timeout waiting for '%s'", '172.16.10.12')
2018-01-09 10:18:30,210 [ERROR] yardstick.benchmark.core.task task.py:276 
Scenario NO.1: "ServiceHA" ERROR!
2018-01-09 10:18:30,212 [ERROR] yardstick.benchmark.core.task task.py:127 
Testcase: "opnfv_yardstick_tc046" FAILED!!!
Traceback (most recent call last):
  File

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread UKASICK, AIMEE L (AIMEE L)

Yes you need a Docker image compiled on ARM in order for it to run on ARM.
I've never created a Docker image for multiple architectures but I did read 
about the capability last year:
https://blog.docker.com/2017/11/multi-arch-all-the-things/
https://developer.ibm.com/linuxonpower/2017/07/27/create-multi-architecture-docker-image/

Good luck!

-
Aimee Ukasick
AT Research Advanced Technology

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 17:50
To: pramod.sud...@wipro.com; Tina Tsou; eric.dm...@wipro.com; UKASICK, AIMEE L 
(AIMEE L); Joe Kidder
Cc: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Re ARM arch, good point. I don’t have ARM hw and did not build this for ARM. 
You can try to build it using the script (tacker.sh) in the models build 
folder. If it works, you will need to push the container to docker hub and 
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it 
as a local container image.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) ; Tina Tsou 
; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
; Joe Kidder 
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows “standard_init_linux.go:178: exec user 
process caused "exec format error"”. The “sudo docker image inspect 
blsaws/models-tacker” shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) 
>; Tina Tsou 
>; Eric DMaye (Product Engineering 
Service) >; UKASICK, AIMEE L 
(AIMEE L) >
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates


** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I’m not sure 
what’s going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' 
>; Tina Tsou 
>; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what’s going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the “tacker vnf-create” step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

Re ARM arch, good point. I don't have ARM hw and did not build this for ARM. 
You can try to build it using the script (tacker.sh) in the models build 
folder. If it works, you will need to push the container to docker hub and 
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it 
as a local container image.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) ; Tina Tsou 
; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
; Joe Kidder 
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows "standard_init_linux.go:178: exec user 
process caused "exec format error"". The "sudo docker image inspect 
blsaws/models-tacker" shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) 
>; Tina Tsou 
>; Eric DMaye (Product Engineering 
Service) >; UKASICK, AIMEE L 
(AIMEE L) >
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates


** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I'm not sure 
what's going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' 
>; Tina Tsou 
>; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread pramod.sud...@wipro.com

Hi Bryan,

I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in 
this ARM Pod.

The sudo docker logs -f tacker shows "standard_init_linux.go:178: exec user 
process caused "exec format error"". The "sudo docker image inspect 
blsaws/models-tacker" shows "Architecture": "amd64", so I was wondering whether 
we need specific docker image for ARM architecture.

Regards,
Pramod

From: SULLIVAN, BRYAN L (BRYAN L) [mailto:bryan.sulli...@research.att.com]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service) ; Tina 
Tsou ; Eric DMaye (Product Engineering Service) 
; UKASICK, AIMEE L (AIMEE L) 
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates


** This mail has been sent from an external source **
Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I'm not sure 
what's going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' 
>; Tina Tsou 
>; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:
1)  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
2)  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55.
3)   Note that you can dump the tacker container log with "sudo docker logs 
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you 
will likely see the issue that led to the endpoint not being created. If the 
container is running, you can use "sudo docker exec -it /bin/bash" to poke 
around in the container, e.g. to debug using the openstack CLI etc from within 
the container.
4)   I have no idea where "fatal: /home/ubuntu/auto/keystonercv3: 
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks 
like something Fuel is complaining about.
5)   "internal endpoint for nfv-orchestration service in RegionOne region 
not found" is a bug, but one due to a persistent problem with OPNFV ... in that 
the different distros use inconsistent naming for key common attributes such as 
the region name. In Apex, this is "regionOne" and the case difference matters. 
But I will try to find a way for the test to be more intelligent, i.e. discover 
the actual value and use it. I've done this in the past, I just need to recall 
where and how.

For reference, For Apex the whole test process including the following is 
posted at

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread Ozgur

  10.01.2018, 01:13, "SULLIVAN, BRYAN L (BRYAN L)" :Can you send directly the info/process you used to deploy Fuel, in as much detail as possible? I will try to duplicate it in my lab so I have enough info to see what’s going on. My tests so far were under Centos with Apex. Some answers to your specific questions:If the tacker container exited, then there is an issue with the tacker setup and I would not expect the “tacker vnf-create” step to work.The nfv-orchestration endpoint is created in the process of start.sh in the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 55.Note that you can dump the tacker container log with “sudo docker logs tacker” or follow it (tail) with “sudo docker logs -f tacker”. Do that and you will likely see the issue that led to the endpoint not being created. If the container is running, you can use “sudo docker exec -it /bin/bash” to poke around in the container, e.g. to debug using the openstack CLI etc from within the container.I have no idea where “fatal: /home/ubuntu/auto/keystonercv3: '/home/ubuntu/auto/keystonercv3' is outside repository” comes from. This looks like something Fuel is complaining about.“internal endpoint for nfv-orchestration service in RegionOne region not found” is a bug, but one due to a persistent problem with OPNFV … in that the different distros use inconsistent naming for key common attributes such as the region name. In Apex, this is “regionOne” and the case difference matters. But I will try to find a way for the test to be more intelligent, i.e. discover the actual value and use it. I’ve done this in the past, I just need to recall where and how.  Hello, this is openstack bug, please run orchestration --debug parameters check command: $ openstack orchestration service list $ heat stack-list and $ keystone (check v3)  For reference, For Apex the whole test process including the following is posted at https://etherpad.opnfv.org/p/bryan-models:Test setupTacker container logsTest startOutput of CLI calls for openstack user, endpoint, and serviceTest stopTest cleanOutput of CLI calls for openstack user, endpoint, and service (verifying cleanup) Note you will still see some reports of “Neutron CLI is deprecated….” Since it’s taking time to convert all the CLI calls to use the openstack client. But they work. Thanks,Bryan Sullivan | AT  Regards, Ozgur From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]Sent: Tuesday, January 09, 2018 12:43 PMTo: SULLIVAN, BRYAN L (BRYAN L) ; Tina Tsou ; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) Cc: 'opnfv-tech-discuss@lists.opnfv.org' Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates Thanks Bryan for the changes. I tried the latest Models Project in ARM Pod (with OPNFV) and found that the setup for vHello_Tacker.sh indicates that it succeeded, but the session logs (as attached) show some issues. I did not see the logic to create an endpoint nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution fails to find this endpoint during “tacker vnf-create” processing. Is this endpoint not needed anymore with this change ? The logs are given below.The docker status also shows as exited.(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -aCONTAINER ID    IMAGE     COMMAND  CREATED STATUS PORTS   NAMES982486b7290c    blsaws/models-tacker:latest   "/bin/bash /opt/ta..."   About an hour ago   Exited (1) About an hour ago   tacker ~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3setup:165 (Tue Jan  9 18:28:11 UTC 2018) run tacker-setup.sh…snip…create_container:99 (Tue Jan  9 18:28:23 UTC 2018) Start tacker container with image blsaws/models-tacker:latestMissing parameter(s): Set a username with --os-username, OS_USERNAME, or auth.usernameSet an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_urlSet a scope, such as a project or domain, set a project scope with --os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name982486b7290c9338979d216dbb8b285431f275028754e75605dbef160501a21epass:40 (Tue Jan  9 18:28:26 UTC 2018) Hooray!…snip…Create virtualenvNew python executable in /home/ubuntu/venv/bin/python..snip…fatal: /home/ubuntu/auto/keystonercv3: '/home/ubuntu/auto/keystonercv3' is outside repository…snip..setup:232 (Tue Jan  9 18:32:25 UTC 2018) Add router interface for vnf_private networkneutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.Added interface f2a6a8b3-bb70-4587-958b-3903629973b9 to router vnf_private_router.pass:100 (Tue Jan  9 18:32:38 UTC 2018) Hooray!pass:103 (Tue Jan  9 18:32:38 UTC 2018) Test Duration = 267 seconds ubuntu@localhost:

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

Two minor edits:

  1.  The link to start.sh (thanks, outook): 
https://git.opnfv.org/models/tree/build/tacker/start.sh
  2.  start.sh already discovers the region name via the API so I'm not sure 
what's going on as reported in your log. See the line:

region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)


Thanks,
Bryan Sullivan | AT

From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: 'pramod.sud...@wipro.com' ; Tina Tsou 
; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 

Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55.
  3.  Note that you can dump the tacker container log with "sudo docker logs 
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you 
will likely see the issue that led to the endpoint not being created. If the 
container is running, you can use "sudo docker exec -it /bin/bash" to poke 
around in the container, e.g. to debug using the openstack CLI etc from within 
the container.
  4.  I have no idea where "fatal: /home/ubuntu/auto/keystonercv3: 
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks 
like something Fuel is complaining about.
  5.  "internal endpoint for nfv-orchestration service in RegionOne region not 
found" is a bug, but one due to a persistent problem with OPNFV ... in that the 
different distros use inconsistent naming for key common attributes such as the 
region name. In Apex, this is "regionOne" and the case difference matters. But 
I will try to find a way for the test to be more intelligent, i.e. discover the 
actual value and use it. I've done this in the past, I just need to recall 
where and how.

For reference, For Apex the whole test process including the following is 
posted at https://etherpad.opnfv.org/p/bryan-models:

  *   Test setup
  *   Tacker container logs
  *   Test start
  *   Output of CLI calls for openstack user, endpoint, and service
  *   Test stop
  *   Test clean
  *   Output of CLI calls for openstack user, endpoint, and service (verifying 
cleanup)

Note you will still see some reports of "Neutron CLI is deprecated" Since 
it's taking time to convert all the CLI calls to use the openstack client. But 
they work.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com 
[mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 12:43 PM
To: SULLIVAN, BRYAN L (BRYAN L) 
>; Tina 
Tsou >; 
eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 
>
Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Thanks Bryan for the changes.

I tried the latest Models Project in ARM Pod (with OPNFV) and found that the 
setup for vHello_Tacker.sh indicates that it succeeded, but the session logs 
(as attached) show some issues. I did not see the logic to create an endpoint 
nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution 
fails to find this endpoint during "tacker vnf-create" processing. Is this 
endpoint not needed anymore with this change ? The logs are given below.
The docker status also shows as exited.
(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -a
CONTAINER IDIMAGE COMMAND  
CREATED STATUS PORTS   NAMES
982486b7290cblsaws/models-tacker:latest   "/bin/bash /opt/ta..."   
About an hour ago   Exited (1) About an hour ago   tacker

~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3
setup:165 (Tue Jan  9 18:28:11 UTC 2018) run tacker-setup.sh
...snip...
create_container:99 (Tue Jan  9 18:28:23 UTC 2018) Start tacker container with 
image blsaws/models-tacker:latest
Missing parameter(s):
Set a username with --os-username, OS_USERNAME, or auth.username
Set an authentication URL, with --os-auth-url, OS_AUTH_URL or

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

Can you send directly the info/process you used to deploy Fuel, in as much 
detail as possible? I will try to duplicate it in my lab so I have enough info 
to see what's going on. My tests so far were under Centos with Apex.

Some answers to your specific questions:

  1.  If the tacker container exited, then there is an issue with the tacker 
setup and I would not expect the "tacker vnf-create" step to work.
  2.  The nfv-orchestration endpoint is created in the process of start.sh in 
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line 
55.
  3.  Note that you can dump the tacker container log with "sudo docker logs 
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you 
will likely see the issue that led to the endpoint not being created. If the 
container is running, you can use "sudo docker exec -it /bin/bash" to poke 
around in the container, e.g. to debug using the openstack CLI etc from within 
the container.
  4.  I have no idea where "fatal: /home/ubuntu/auto/keystonercv3: 
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks 
like something Fuel is complaining about.
  5.  "internal endpoint for nfv-orchestration service in RegionOne region not 
found" is a bug, but one due to a persistent problem with OPNFV ... in that the 
different distros use inconsistent naming for key common attributes such as the 
region name. In Apex, this is "regionOne" and the case difference matters. But 
I will try to find a way for the test to be more intelligent, i.e. discover the 
actual value and use it. I've done this in the past, I just need to recall 
where and how.

For reference, For Apex the whole test process including the following is 
posted at https://etherpad.opnfv.org/p/bryan-models:

  *   Test setup
  *   Tacker container logs
  *   Test start
  *   Output of CLI calls for openstack user, endpoint, and service
  *   Test stop
  *   Test clean
  *   Output of CLI calls for openstack user, endpoint, and service (verifying 
cleanup)

Note you will still see some reports of "Neutron CLI is deprecated" Since 
it's taking time to convert all the CLI calls to use the openstack client. But 
they work.

Thanks,
Bryan Sullivan | AT

From: pramod.sud...@wipro.com [mailto:pramod.sud...@wipro.com]
Sent: Tuesday, January 09, 2018 12:43 PM
To: SULLIVAN, BRYAN L (BRYAN L) ; Tina Tsou 
; eric.dm...@wipro.com; UKASICK, AIMEE L (AIMEE L) 

Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates

Thanks Bryan for the changes.

I tried the latest Models Project in ARM Pod (with OPNFV) and found that the 
setup for vHello_Tacker.sh indicates that it succeeded, but the session logs 
(as attached) show some issues. I did not see the logic to create an endpoint 
nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution 
fails to find this endpoint during "tacker vnf-create" processing. Is this 
endpoint not needed anymore with this change ? The logs are given below.
The docker status also shows as exited.
(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -a
CONTAINER IDIMAGE COMMAND  
CREATED STATUS PORTS   NAMES
982486b7290cblsaws/models-tacker:latest   "/bin/bash /opt/ta..."   
About an hour ago   Exited (1) About an hour ago   tacker

~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3
setup:165 (Tue Jan  9 18:28:11 UTC 2018) run tacker-setup.sh
...snip...
create_container:99 (Tue Jan  9 18:28:23 UTC 2018) Start tacker container with 
image blsaws/models-tacker:latest
Missing parameter(s):
Set a username with --os-username, OS_USERNAME, or auth.username
Set an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_url
Set a scope, such as a project or domain, set a project scope with 
--os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope 
with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name
982486b7290c9338979d216dbb8b285431f275028754e75605dbef160501a21e
pass:40 (Tue Jan  9 18:28:26 UTC 2018) Hooray!
...snip...
Create virtualenv
New python executable in /home/ubuntu/venv/bin/python
..snip...
fatal: /home/ubuntu/auto/keystonercv3: '/home/ubuntu/auto/keystonercv3' is 
outside repository
...snip..
setup:232 (Tue Jan  9 18:32:25 UTC 2018) Add router interface for vnf_private 
network
neutron CLI is deprecated and will be removed in the future. Use openstack CLI 
instead.
Added interface f2a6a8b3-bb70-4587-958b-3903629973b9 to router 
vnf_private_router.
pass:100 (Tue Jan  9 18:32:38 UTC 2018) Hooray!
pass:103 (Tue Jan  9 18:32:38 UTC 2018) Test Duration = 267 seconds

ubuntu@localhost:

[opnfv-tech-discuss] [OPNFV Helpdesk #50829] [linuxfoundation.org #50829] Re: [Pharos] New Pharos Committers

2018-01-09 Thread Ozgur via RT

09.01.2018, 23:56, "Sofia Enriquez" :

  Welcome! 2018-01-08 21:44 GMT-03:00 Jack Morgan < jack.mor...@intel.com 
(mailto:jack.mor...@intel.com)>:

OPNFV,

Please help me to welcome the following new committers to the Pharos
project. I really appreciated the help they have provided on the POD
descriptor file, the Pharos Dashboard, Lab-as-a-Service and
documentation. I look forward to seeing the Pharos project continue to
improve with their help.

Alexandru Avadanii (ENEA)
Aric Gardner (Linux Foundation)
Guillermo Herrero (ENEA)
Parker Berberian (UNH)
Trevor Bramwell (Linux Foundation)

it was nice to seen friends from the Linux family :)Welcome, Ozgur

Thanks,

--
Jack Morgan
Network SW Engineer
DNSG SW Engineering

___
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




  --Sofia Enriquez,

  ___
  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] [Pharos] New Pharos Committers

2018-01-09 Thread Ozgur

09.01.2018, 23:56, "Sofia Enriquez" :Welcome! 2018-01-08 21:44 GMT-03:00 Jack Morgan :OPNFV,Please help me to welcome the following new committers to the Pharos project. I really appreciated the help they have provided on the POD descriptor file, the Pharos Dashboard, Lab-as-a-Service  and documentation. I look forward to seeing the Pharos project continue to improve with their help.Alexandru Avadanii (ENEA)Aric Gardner (Linux Foundation)Guillermo Herrero (ENEA)Parker Berberian (UNH)Trevor Bramwell (Linux Foundation)  it was nice to seen friends from the Linux family :)Welcome, Ozgur  Thanks,--Jack MorganNetwork SW EngineerDNSG SW Engineering___opnfv-tech-discuss mailing listopnfv-tech-discuss@lists.opnfv.orghttps://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss--Sofia Enriquez,___opnfv-tech-discuss mailing listopnfv-tech-discuss@lists.opnfv.orghttps://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] [OPNFV Helpdesk #50829] [linuxfoundation.org #50829] Re: [Pharos] New Pharos Committers

2018-01-09 Thread lsofia.enriq...@gmail.com via RT

Welcome!

2018-01-08 21:44 GMT-03:00 Jack Morgan :

> OPNFV,
>
> Please help me to welcome the following new committers to the Pharos
> project. I really appreciated the help they have provided on the POD
> descriptor file, the Pharos Dashboard, Lab-as-a-Service  and documentation.
> I look forward to seeing the Pharos project continue to improve with their
> help.
>
> Alexandru Avadanii (ENEA)
> Aric Gardner (Linux Foundation)
> Guillermo Herrero (ENEA)
> Parker Berberian (UNH)
> Trevor Bramwell (Linux Foundation)
>
>
> Thanks,
>
> --
> Jack Morgan
> Network SW Engineer
> DNSG SW Engineering
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>



-- 
Sofia Enriquez

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

Re: [opnfv-tech-discuss] [Pharos] New Pharos Committers

2018-01-09 Thread Sofia Enriquez

Welcome!

2018-01-08 21:44 GMT-03:00 Jack Morgan :

> OPNFV,
>
> Please help me to welcome the following new committers to the Pharos
> project. I really appreciated the help they have provided on the POD
> descriptor file, the Pharos Dashboard, Lab-as-a-Service  and documentation.
> I look forward to seeing the Pharos project continue to improve with their
> help.
>
> Alexandru Avadanii (ENEA)
> Aric Gardner (Linux Foundation)
> Guillermo Herrero (ENEA)
> Parker Berberian (UNH)
> Trevor Bramwell (Linux Foundation)
>
>
> Thanks,
>
> --
> Jack Morgan
> Network SW Engineer
> DNSG SW Engineering
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>



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

[opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

Pramod,

Bringing this offline discussion to the list...

The Models vHello_Tacker test is now updated/merged and working for Euphrates 
(verified for Apex virtual install). There were a variety of API/CLI and other 
changes in OpenStack Ocata, and I took the opportunity to refactor the test. It 
now uses a docker container for Tacker, that is pre-built and downloaded from 
docker hub (https://hub.docker.com/r/blsaws/models-tacker/). The test overall 
runs much faster. The comments at the start of the script describe the updated 
process. The main difference is that the OpenStack commands require activation 
of a virtual env that is installed in the setup step.

Thanks,
Bryan Sullivan | AT

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

[opnfv-tech-discuss] [Infra] Intel Pharos Lab maintenance

2018-01-09 Thread Jack Morgan


OPNFV,

The Intel Pharos lab will be down for maintenance from Friday, January 
12th from 12:00 PM (PST) to Tuesday, January 16th. Intel will complete 
upgrading electrical and power equipment it started over the 
Thanksgiving weekend. All lab access and servers will be powered off 
during this time.



Thanks,

--
Jack Morgan
Network SW Engineer
DNSG SW Engineering

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

Re: [opnfv-tech-discuss] Licenses for OPNFV docker images

2018-01-09 Thread SULLIVAN, BRYAN L (BRYAN L)

I have a proposed text, included in the containers I have published at 
https://hub.docker.com/u/blsaws/. Here is an example for 
https://hub.docker.com/r/blsaws/ves-agent/
This container provides the "VES Agent" function of the OPNFV VNF Event Stream 
(VES) project. The container is built via the "ves-agent.sh" script in the VES 
repo folder https://github.com/opnfv/ves/tree/master/build. For more 
information, see https://wiki.opnfv.org/display/ves/VES+Home.
The container includes code developed under the OPNFV project and distributed 
under the license below (# LICENSE #), and other code installed as part of the 
container build process, separately licensed per the source of that code.
LICENSE
Copyright 2017-2018 AT Intellectual Property, Inc
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0


Thanks,
Bryan Sullivan | AT

From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Tuesday, January 09, 2018 8:55 AM
To: SULLIVAN, BRYAN L (BRYAN L) 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Licenses for OPNFV docker images

Hi Bryan,

So you're looking for a license text for OPNFV users to use the contents in 
OPNFV docker hub?  Let me know if I'm mistaken.  I can check with the legal 
team on this...

Thanks,

Ray

On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) 
> wrote:
Hi all,

Should we be adding license descriptions to the 
https://hub.docker.com/u/opnfv
 images? I have seen a recommendation that the license be included in the repo 
description field. Just wondering, since otherwise per the docker hub TOS 
(https://www.docker.com/docker-terms-service):

6.4 The Service allows you to specify or upload the terms under which other 
users of the Service will be licensed to use your User Content. If you do not 
specify or upload such license terms with respect to any User Content, you 
hereby grant to any other users of the Service, a non-exclusive license to 
access, download, use, modify or otherwise exploit such part of your User 
Content for any personal or business purposes.

Thanks,
Bryan Sullivan | AT


___
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] Licenses for OPNFV docker images

2018-01-09 Thread Raymond Paik

Hi Bryan,

So you're looking for a license text for OPNFV users to use the contents in
OPNFV docker hub?  Let me know if I'm mistaken.  I can check with the legal
team on this...

Thanks,

Ray

On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) <
bryan.sulli...@research.att.com> wrote:

> Hi all,
>
>
>
> Should we be adding license descriptions to the
> https://hub.docker.com/u/opnfv images? I have seen a recommendation that
> the license be included in the repo description field. Just wondering,
> since otherwise per the docker hub TOS (https://www.docker.com/
> docker-terms-service):
>
>
>
> *6.4 *The Service allows you to specify or upload the terms under which
> other users of the Service will be licensed to use your User Content. If
> you do not specify or upload such license terms with respect to any User
> Content, you hereby grant to any other users of the Service, a
> non-exclusive license to access, download, use, modify or otherwise exploit
> such part of your User Content for any personal or business purposes.
>
>
>
> Thanks,
>
> Bryan Sullivan | AT
>
>
>
> ___
> 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] Agenda Item of Technical Community Discussion this Thursday Jan 11

2018-01-09 Thread HU, BIN

Hello community,

I am looking for agenda items of technical community discussion this Thursday 
Jan 11. Please let me know if there is any topic you want to discuss.

Thank you
Bin

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

[opnfv-tech-discuss] OpenSDS introduce in Compass integration discuss meeting.

2018-01-09 Thread Chigang (Justin)

Hi team,

Just had a great F2F meeting with Stor4nfv team yesterday, we know that there 
will be two components, OpenSDS and Ceph in the first release of Stor4nfv.
Stor4nfv team will focus on how to integrate ceph into OpenSDS, and enable 
stor4nfv CI workflow, including building packages and uploading to OPNFV 
artfacts.
Shobha and Compass team will focus on how to integrate OpenSDS with Compass.
So I invite Leon participate in Compass integration meeting on Beijing time 
9:00 am in Thursday.
He will give us a introduce of OpenSDS, and how to intergrate OpenSDS with K8s. 
if you are available, please join the meeting.

Meeting info:
https://wiki.opnfv.org/display/meetings/Compass4NFV+Integration+Discuss+Meeting

Please correct me if I miss something, thanks

Regards
Justin

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

[opnfv-tech-discuss] yardstick tc046 failure HA test case: Control node Openstack service down - keystone

2018-01-09 Thread Ting Wu

Hi,

We are running yardstick in our arm-pod with fuel installation, there are few 
failed testcases. One of them is "opnfv_yardstick_tc046.yaml"

The testcase is to check if the keystone service is alive in all controllers in 
HA scenario.

When we manually check on the nodes,  the keystone is alive but the test case 
reported failure.  Does someone know what the pass criteria of this test case?

//login to cfg and manually check  service status, according to 
https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide/troubleshooting/service-status.html



ubuntu@cfg01:~$ sudo salt "ctl*" service.status apache2

ctl02.baremetal-mcp-pike-ovs-ha.local:

True

ctl01.baremetal-mcp-pike-ovs-ha.local:

True

ctl03.baremetal-mcp-pike-ovs-ha.local:

True

ubuntu@cfg01:~$ sudo salt "ctl*" cmd.run "netstat -nltp | egrep '5000|35357'"

ctl03.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.13:5000   0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14059/haproxy

tcp0  0 172.16.10.13:35357  0.0.0.0:*   LISTEN  
1051/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14059/haproxy

ctl02.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.12:5000   0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14095/haproxy

tcp0  0 172.16.10.12:35357  0.0.0.0:*   LISTEN  
1164/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14095/haproxy

ctl01.baremetal-mcp-pike-ovs-ha.local:

tcp0  0 172.16.10.11:5000   0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:5000   0.0.0.0:*   LISTEN  
14105/haproxy

tcp0  0 172.16.10.11:35357  0.0.0.0:*   LISTEN  
2124/apache2

tcp0  0 172.16.10.10:35357  0.0.0.0:*   LISTEN  
14105/haproxy


//yardstick printout
2018-01-09 10:08:29,150 [INFO] yardstick.benchmark.core.task task.py:483 
Parsing task config: 
/home/opnfv/repos/yardstick/tests/opnfv/test_cases/opnfv_yardstick_tc046.yaml
2018-01-09 10:08:29,218 [INFO] yardstick.benchmark.contexts.node node.py:57 
Parsing pod file: etc/yardstick/nodes/fuel_baremetal/pod.yaml
2018-01-09 10:08:29,257 [INFO] yardstick.benchmark.core.task task.py:373 
Starting runner of type 'Duration'
Background task ended
Background task ended
Background task ended
2018-01-09 10:08:29,274 [INFO] yardstick.benchmark.runners.duration 
duration.py:46 Worker START, duration is 1s
Process Duration-ServiceHA-7429:
Traceback (most recent call last):
  File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
self.run()
  File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/runners/duration.py", 
line 52, in _worker_process
benchmark.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/serviceha.py",
 line 47, in setup
attacker_ins.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/availability/attacker/attacker_process.py",
 line 28, in setup
self.connection.wait(timeout=600)
  File "/home/opnfv/repos/yardstick/yardstick/ssh.py", line 374, in wait
raise SSHTimeout("Timeout waiting for '%s'", self.host)
SSHTimeout: ("Timeout waiting for '%s'", '172.16.10.12')
2018-01-09 10:18:30,210 [ERROR] yardstick.benchmark.core.task task.py:276 
Scenario NO.1: "ServiceHA" ERROR!
2018-01-09 10:18:30,212 [ERROR] yardstick.benchmark.core.task task.py:127 
Testcase: "opnfv_yardstick_tc046" FAILED!!!
Traceback (most recent call last):
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
123, in start
data = self._run(scenarios, run_in_parallel, args.output_file)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
278, in _run
"{0} runner status {1}".format(runner.__execution_type__, status))
RuntimeError: Duration runner status 1
2018-01-09 10:18:30,214 [INFO] yardstick.benchmark.core.task task.py:143 Task 
/home/opnfv/repos/yardstick/tests/opnfv/test_cases/opnfv_yardstick_tc046.yaml 
finished in 601 secs


Best Regards
Ting Wu
NFV Engineer, ARMBand Team
ENEA R Cloud Technologies
Email  ting...@enea.com
Phone  +46 709714003

Enea Software AB
Jan Stenbecks Torg 17
Box 1033, SE-164 21 Kista, Sweden
www.enea.com

[cid:image002.png@01D00576.7D651240]
This message, including attachments, is CONFIDENTIAL. It may also be privileged 
or otherwise protected by law. If you received this email by mistake please let 
us know by reply and then delete it

[opnfv-tech-discuss] [Bottlenecks] Weekly Call

2018-01-09 Thread Yuyang (Gabriel)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Australia Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yuyang (Gabriel):MAILTO:gabriel.yuy...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -discuss:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Brattain,
  Ross B'":MAILTO:ross.b.bratt...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'S, Deepak
 '":MAILTO:deepa...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Rutuja Su
 rve':MAILTO:rutuja.r.su...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=AMIT KUMAR
  JAISWAL:MAILTO:amitkumarj...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Manuel Reb
 ellon:MAILTO:mrebel...@sandvine.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangyaogua
 ng (A):MAILTO:sunshine.w...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Liyin (Ace
 ):MAILTO:liyi...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Manoj Nir
 ania':MAILTO:manojnira...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shubham A
 garwal':MAILTO:shubham.agarwal.co...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=limingjian
 g:MAILTO:limingji...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=chenjianku
 n:MAILTO:chenjiank...@huawei.com
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='Maria Toe
 roe':MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Bernier, 
 Daniel'":MAILTO:daniel.bern...@bell.ca
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='Jose Ange
 l Lausuch':MAILTO:jalaus...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Anubhav G
 uleria':MAILTO:anugule...@grads.cds.iisc.ac.in
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ray Wong'
 :MAILTO:ray.w...@deltaww.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Nicolas B
 outhors':MAILTO:nicolas.bouth...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sun, Jimi
 ng'":MAILTO:jiming@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Cooper, T
 revor'":MAILTO:trevor.coo...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Carlos Br
 avo':MAILTO:carlos.br...@ericsson.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="'Ramia, Ka
 nnan Babu'":MAILTO:kannan.babu.ra...@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="'Wang, Sha
 ne'":MAILTO:shane.w...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tim Irnic
 h':MAILTO:tim.irn...@ericsson.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="'Seiler, G
 lenn'":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Perala, T
 imo (Nokia - FI/Espoo)'":MAILTO:timo.per...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ahmed Elb
 ornou (amaged)':MAILTO:ama...@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="'Reddy, Ra
 ghuveer'":MAILTO:raghuveer.re...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='최강일
 ':MAILTO:forerun...@etri.re.kr
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Kevin Gla
 vin':MAILTO:kevin.gla...@riverbed.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei

[opnfv-tech-discuss] [Testperf] APAC Meeting Call

[opnfv-tech-discuss] [Bottlenecks] Minutes for Weekly Call 20180110

Re: [opnfv-tech-discuss] Updated invitation: OPNFV C Committee Call @ Every 2 weeks from 11pm to 12am on Monday (SGT) (christopher.don...@huawei.com)

[opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 10 Jan 2017 (ww51)

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[opnfv-tech-discuss] [yardstick]//RE: yardstick tc046 failure HA test case: Control node Openstack service down - keystone

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] yardstick tc046 failure HA test case: Control node Openstack service down - keystone

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

Re: [opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[opnfv-tech-discuss] [OPNFV Helpdesk #50829] [linuxfoundation.org #50829] Re: [Pharos] New Pharos Committers

Re: [opnfv-tech-discuss] [Pharos] New Pharos Committers

[opnfv-tech-discuss] [OPNFV Helpdesk #50829] [linuxfoundation.org #50829] Re: [Pharos] New Pharos Committers

Re: [opnfv-tech-discuss] [Pharos] New Pharos Committers

[opnfv-tech-discuss] [Models][Auto] vHello_Tacker updated for Euphrates

[opnfv-tech-discuss] [Infra] Intel Pharos Lab maintenance

Re: [opnfv-tech-discuss] Licenses for OPNFV docker images

Re: [opnfv-tech-discuss] Licenses for OPNFV docker images

[opnfv-tech-discuss] Agenda Item of Technical Community Discussion this Thursday Jan 11

[opnfv-tech-discuss] OpenSDS introduce in Compass integration discuss meeting.

[opnfv-tech-discuss] yardstick tc046 failure HA test case: Control node Openstack service down - keystone

[opnfv-tech-discuss] [Bottlenecks] Weekly Call

26 matches

Site Navigation

Mail list logo

Footer information