Re: [opnfv-tech-discuss] Fraser community award winners

[Beierl, Mark]

Congratulations to each winner.  This is what I love about OPNFV, all the 
people and the sense of community and support for each other.

And, Ray, we are going to miss you.  You definitely have shaped the OPNFV 
spirit!

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mark.bei...@dell.com

On Jun 19, 2018, at 18:35, Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:

All,

My apologies for the delay on this as it took a lot longer than expected to 
procure the award items.  I was hoping to make the announcement at the Plugfest 
a few weeks ago.

First of all, below are the award winners for each category (there was a tie in 
the testing category).  I'd like to congratulate & thank all the award winners 
for their contribution to OPNFV during the Fraser release cycle...

Code Development:

  *   Cedric Ollivier (Orange)
  *   Harry Huang (Huawei)
  *   Tianwei Wu (Huawei)

Community support/leadership:

  *   Alexandru Avadanii (ENEA)
  *   Fatih Degirmenci (Ericsson)
  *   Georg Kunz (Ericsson)

Integration:

  *   Dimitrios Markou (Intracom Telecom)
  *   Ramamani Yeleswarapu (Intel)
  *   Yibo Cai (ARM)

Testing

  *   Delia Popescu (ENEA)
  *   Gabriel Yu (Huawei)
  *   Linda Wang (Huawei)
  *   Rex Li (Huawei)

Interns:

  *   Konrad Djimeli
  *   Sofia Enriquez

As for the award itself, we went with a summer themed merchandise that people 
can use as they visit the beach, pool, etc.  (image attached below). The awards 
will be available through the OPNFV 
store and winners will be 
given a code to order the merchandise for free (incl. shipping).  As for the 
new OPNFV store, Brandon will tell you more about it at an upcoming TSC call :-)

Thanks,

Ray
___
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] [storperf] Intern Project Incubation Page

[Beierl, Mark]

Hello, StorPerf committers and contributors (as well as the rest of the OPNFV 
community at large)!

I have started a page [1] for ideas of different intern projects that could be 
tackled during the Gambia release.  Please feel free to add ideas or comments 
to the document.

[1] https://wiki.opnfv.org/display/storperf/Project+Proposal+Incubation+Page

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [yardstick] TC074

[Beierl, Mark]

Hello,

I'm still trying to recreate a problem with TC0074, and am not quite sure how 
to run it.  Following the guide [1], I have done the env prepare and 
successfully run the ping test case.  I am now trying to get StorPerf started.  
I ran the install, which completed successfully in very little time:

2018-06-01 15:29:10,120 [INFO] yardstick.benchmark.core.plugin plugin.py:41 
Installing plugin: storperf
2018-06-01 15:29:10,632 [INFO] yardstick.benchmark.core.plugin plugin.py:97 
copying script to host: ~/storperf.sh
2018-06-01 15:29:12,708 [INFO] yardstick.benchmark.core.plugin plugin.py:127 
Executing command: sudo bash storperf.sh
2018-06-01 15:29:12,864 [INFO] yardstick.benchmark.core.plugin plugin.py:51 
Total finished in 2 secs
2018-06-01 15:29:12,865 [INFO] yardstick.benchmark.core.plugin plugin.py:53 
Plugin storperf Done, exiting

But when I try to run tc074, it still fails to connect.  What am I missing?

2018-06-01 15:29:50,161 [INFO] yardstick.cmd.commands.task task.py:52 Task START
2018-06-01 15:29:50,163 [INFO] yardstick.benchmark.core.task task.py:543 
Parsing task config: ./tests/opnfv/test_cases/opnfv_yardstick_tc074.yaml
2018-06-01 15:29:50,176 [INFO] yardstick.benchmark.core.task task.py:402 
Starting runner of type 'Iteration'
2018-06-01 15:29:50,566 [INFO] yardstick.benchmark.runners.iteration 
iteration.py:51 worker START, iterations 1 times, class 
2018-06-01 15:29:50,567 [INFO] yardstick.benchmark.scenarios.storage.storperf 
storperf.py:101 Creating a stack on node 192.168.200.1 with parameters 
{'agent_count': 1, 'volume_size': 4, 'public_network': u'ext-net', 
'agent_flavor': u'storperf', 'agent_image': u'Ubuntu-16.04'}
Process Iteration-StorPerf-2686:
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/iteration.py", 
line 57, in _worker_process
benchmark.setup()
  File 
"/home/opnfv/repos/yardstick/yardstick/benchmark/scenarios/storage/storperf.py",
 line 103, in setup
% self.target, json=env_args)
  File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 110, in 
post
return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/requests/api.py", line 56, in 
request
return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 475, 
in request
resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 596, 
in send
r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 487, 
in send
raise ConnectionError(e, request=request)
ConnectionError: HTTPConnectionPool(host='192.168.200.1', port=5000): Max 
retries exceeded with url: /api/v1.0/configurations (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 110] 
Connection timed out',))
2018-06-01 15:31:57,897 [ERROR] yardstick.benchmark.core.task task.py:280 
Scenario NO.1: "StorPerf" ERROR!
2018-06-01 15:31:57,898 [ERROR] yardstick.benchmark.core.task task.py:281 
Iteration runner status 1
2018-06-01 15:31:57,898 [INFO] yardstick.benchmark.core.task task.py:283 Runner 
ended
2018-06-01 15:31:57,898 [ERROR] yardstick.benchmark.core.task task.py:132 
Testcase: "opnfv_yardstick_tc074" FAILED!!!
Traceback (most recent call last):
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 68, 
in start
output_config = utils.parse_ini_file(CONF_FILE)
  File "/home/opnfv/repos/yardstick/yardstick/common/utils.py", line 176, in 
parse_ini_file
raise RuntimeError('file not exist')
RuntimeError: file not exist
2018-06-01 15:31:57,900 [INFO] yardstick.benchmark.core.task task.py:146 Task 
./tests/opnfv/test_cases/opnfv_yardstick_tc074.yaml finished in 127 secs
2018-06-01 15:31:57,910 [INFO] yardstick.benchmark.core.task task.py:167 Report 
can be found in '/tmp/report.html'
2018-06-01 15:31:57,911 [INFO] yardstick.benchmark.core.task task.py:155 Total 
finished in 127 secs
2018-06-01 15:31:57,912 [INFO] yardstick.benchmark.core.task task.py:158 To 
generate report, execute command "yardstick report generate 
0aa16398-5f3f-41cd-90dc-dddbb2916f8b "
2018-06-01 15:31:57,912 [INFO] yardstick.benchmark.core.task task.py:159 Task 
ALL DONE, exiting
2018-06-01 15:31:57,913 [INFO] yardstick.cmd.commands.task task.py:63 Task 
FAILED


[1] 
http://docs.opnfv.org/en/latest/submodules/yardstick/docs/testing/user/userguide/06-yardstick-plugin.html

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

Re: [opnfv-tech-discuss] [yardstick] Docs not working

[Beierl, Mark]

Hello, Jing.

The docs did not mention anything about changing directories after the docker 
exec, so in the base directory /home/opnfv/repos.  I did a cd into 
/home/opnfv/repos/yardstick and that works now, thanks.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On May 30, 2018, at 04:51, Lvjing (Jing Lu) 
mailto:lvji...@huawei.com>> wrote:

Hi mark，

In which directory did you execute these two commands?
The error message ‘[Errno 2] No such file or directory: 'plugin/storperf.yaml'’ 
seems indicating that there is no such file in the current directory.
But this file does exist in the yardstick repo.

Regards,
Jing

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Beierl, Mark
发送时间: 2018年5月30日 4:24
收件人: TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
主题: [opnfv-tech-discuss] [yardstick] Docs not working

Hello,

I am trying to help troubleshoot the execution of TC 74 (StorPerf) in 
Yardstick.  I have Apex installed, and have the OS credentials file mounted in 
the Yardstick container.  The yardstick env prepare command succeeded, but when 
I continued in the installation guide, the following command failed:

yardstick task start samples/ping.yaml
... output omitted ...
Traceback (most recent call last):
  File "/usr/local/bin/yardstick", line 11, in 
load_entry_point('yardstick', 'console_scripts', 'yardstick')()
  File "/home/opnfv/repos/yardstick/yardstick/main.py", line 49, in main
YardstickCLI().main(sys.argv[1:])
  File "/home/opnfv/repos/yardstick/yardstick/cmd/cli.py", line 165, in main
self._dispatch_func_notask()
  File "/home/opnfv/repos/yardstick/yardstick/cmd/cli.py", line 143, in 
_dispatch_func_notask
func(CONF.category)
  File "/home/opnfv/repos/yardstick/yardstick/cmd/commands/task.py", line 54, 
in do_start
result = Task().start(param, **kwargs)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
103, in start
task_args_fnames)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
328, in _parse_tasks
task_args_fnames[i]))
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
545, in parse_task
cfg, rendered = self._render_task(task_args, task_args_file)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
535, in _render_task
raise y_exc.TaskReadError(task_file=self.path)
TaskReadError: Failed to read task samples/ping.yaml

I then attempted to follow this section of the guide: 
http://docs.opnfv.org/en/latest/submodules/yardstick/docs/testing/user/userguide/06-yardstick-plugin.html#installing-storperf-into-yardstick

It also failed as follows:

yardstick plugin install plugin/storperf.yam
No handlers could be found for logger "yardstick.common.utils"
/usr/local/lib/python2.7/dist-packages/flask/exthook.py:71: 
ExtDeprecationWarning: Importing flask.ext.restful is deprecated, use 
flask_restful instead.
  .format(x=modname), ExtDeprecationWarning
Parsing plugin config: plugin/storperf.yaml
[Errno 2] No such file or directory: 'plugin/storperf.yaml'

Is there something fundamental that I missed?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

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

[opnfv-tech-discuss] [yardstick] Docs not working

[Beierl, Mark]

Hello,

I am trying to help troubleshoot the execution of TC 74 (StorPerf) in 
Yardstick.  I have Apex installed, and have the OS credentials file mounted in 
the Yardstick container.  The yardstick env prepare command succeeded, but when 
I continued in the installation guide, the following command failed:

yardstick task start samples/ping.yaml
... output omitted ...
Traceback (most recent call last):
  File "/usr/local/bin/yardstick", line 11, in 
load_entry_point('yardstick', 'console_scripts', 'yardstick')()
  File "/home/opnfv/repos/yardstick/yardstick/main.py", line 49, in main
YardstickCLI().main(sys.argv[1:])
  File "/home/opnfv/repos/yardstick/yardstick/cmd/cli.py", line 165, in main
self._dispatch_func_notask()
  File "/home/opnfv/repos/yardstick/yardstick/cmd/cli.py", line 143, in 
_dispatch_func_notask
func(CONF.category)
  File "/home/opnfv/repos/yardstick/yardstick/cmd/commands/task.py", line 54, 
in do_start
result = Task().start(param, **kwargs)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
103, in start
task_args_fnames)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
328, in _parse_tasks
task_args_fnames[i]))
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
545, in parse_task
cfg, rendered = self._render_task(task_args, task_args_file)
  File "/home/opnfv/repos/yardstick/yardstick/benchmark/core/task.py", line 
535, in _render_task
raise y_exc.TaskReadError(task_file=self.path)
TaskReadError: Failed to read task samples/ping.yaml

I then attempted to follow this section of the guide: 
http://docs.opnfv.org/en/latest/submodules/yardstick/docs/testing/user/userguide/06-yardstick-plugin.html#installing-storperf-into-yardstick

It also failed as follows:

yardstick plugin install plugin/storperf.yam
No handlers could be found for logger "yardstick.common.utils"
/usr/local/lib/python2.7/dist-packages/flask/exthook.py:71: 
ExtDeprecationWarning: Importing flask.ext.restful is deprecated, use 
flask_restful instead.
  .format(x=modname), ExtDeprecationWarning
Parsing plugin config: plugin/storperf.yaml
[Errno 2] No such file or directory: 'plugin/storperf.yaml'

Is there something fundamental that I missed?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [dovetail] agenda for weekly call on 2018-05-30

[Beierl, Mark]

Hello,

Unfortunately this conflicts with the Edge Cloud project meeting, so I might 
not be able to attend this week's Dovetail to talk about an OVP performance 
proposal.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On May 29, 2018, at 12:30, Georg Kunz 
mailto:georg.k...@ericsson.com>> wrote:

Hi,

I forgot to mention: this week’s call will be one hour earlier than usual:
13:00-14:00 UTC (6:00-7:00AM Pacific Daylight Time)

Best regards
Georg

From: Georg Kunz
Sent: Tuesday, May 29, 2018 5:28 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss][dovetail] agenda for weekly call on 2018-05-30

Hi all,

This is the preliminary agenda for tomorrow’s Dovetail call:
• web portal update
• proposal for a first performance for OVP
• critical bug: vping reported as passed despite failing
• plugfest preparation
• CI status
• AOB

Best regards
Georg
___
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] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Beierl, M
 ark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-CA:Hello\,\n\nPlease feel free to join us for the S
 torPerf team meeting.  This schedule runs until the Daylight Savings time 
 ends in North America.\n\nhttps://zoom.us/j/5014627785 and #opfnv-meeting\
 n\nAgendas and minutes will be published here:\n\nhttps://wiki.opnfv.org/d
 isplay/meetings/Storperf+Team+Weekly+Meeting\n
SUMMARY;LANGUAGE=en-CA:[StorPerf] Weekly Meeting
DTSTART;TZID=America/New_York:20180524T10
DTEND;TZID=America/New_York:20180524T11
UID:DA85607B-3CE3-4CB4-8C47-903ED6B43DDD
RECURRENCE-ID;TZID=America/New_York:20180524T10
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180523T070559Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:0
LOCATION;LANGUAGE=en-CA:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
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
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] [dovetail] Agenda for weekly meeting - 2018-05-23

[Beierl, Mark]

Had a brief conversation with Georg about setting a bar for entering into the 
performance phase of Dovetail:

The concept is to run a tenant network workload (Vsperf or NFVBench) and 
capture the baseline. Next run a storage network workload (StorPerf) and 
capture its baseline. Next run both together and if there is a significant drop 
in either (ie don’t record the actual throughputs, just the delta) report that 
as non compliant because storage and tenant networks are colliding.

Perhaps we can discuss this concept in an upcoming meeting?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On May 22, 2018, at 17:52, Georg Kunz 
> wrote:

Hi Dovetailers,

This is the preliminary agenda for tomorrow’s weekly Dovetail call:


  *   web portal update
  *   plugfest preparation
  *   CI status
  *   AOB

Best regards
Georg
___
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] Request for Network Administration tools

[Beierl, Mark]

Hello, Parker.

There is another, non OpenStack project, RackHD, which claims to support 
provisioning for Cisco.

Here’s a note from one of their devs:

Our team worked on cisco support for discovery, FW update and configuration. 
Here is the microservice code : https://github.com/RackHD/on-network
It also has all the workflows hooks in RackHD workflow engine.

If you’re interested in exploring that, I can be a point of contact to see what 
automation can be done with RackHD.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On May 22, 2018, at 17:31, MORTON, ALFRED C (AL) 
> wrote:

Hi Parker,

OPNFV has a controller performance project, CPERF,
which doesn’t participate in releases but continues its work
on controller testing. The project is also a resource for collaboration
between ODL and OPNFV when issues come up.  This sounds like
yet another opportunity for collaboration.

I’ve CC’d our PTL, Sai, and Daniel, Luis, and Jamo who are
other Cperf regulars. Both Jamo and I attended the LaaS
presentation you did with Jack at ONS 2018 and asked several questions.

I’m taking some time off this week, but I’m sure a
Cperf’er can help. We also have a mini-meeting at
2:15pm ET Thursday for more interactive discussions.

regards,
Al

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Parker 
Berberian
Sent: Friday, May 18, 2018 12:41 PM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Request for Network Administration tools

Hi All,

If you don't know me, I am Parker Berberian. I am running the Lab as a Service 
at the UNH Interoperability Lab.

We are beginning development on supporting dynamic pod allocation. To do this, 
we need to be able to manipulate our underlay network in an automated fashion 
in order to create opnfv "pods" from any arbitrary machines we host.

Essentially, when a deployment happens, we need to be able to take any of our 
available machines and add them to the appropriate vlans and make sure they can 
all talk to each other. There may be as many as 4 switches between different 
machines, so all the necessary switches need to be configured to forward the 
given vlans.

We use Cisco 9300 switches 
(here)
 which support OpenFlow. So we originally considered used an SDN controller 
such as OpenDaylight.

Has anyone used a tool that might accomplish what we need? Any recommendations 
are welcome.

Thank you,
Parker Berberian.
___
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] [apex] Fraser installation failure

[Beierl, Mark]

Hello,

I downloaded the latest Fraser from https://www.opnfv.org/software/downloads 
and followed the installation guide from 
http://docs.opnfv.org/en/stable-fraser/submodules/apex/docs/release/installation/virtual.html

I tried this on two different systems (one inside Dell, and the other a LaaS 
system).  Both failed in the same spot with these errors.  Has anyone seen this 
before and where I can look for more info on the error?

2018-05-17 11:18:52,767 INFO: TASK [Show overcloud failures] 
*
task path: /usr/share/opnfv-apex/ansible/playbooks/deploy_overcloud.yml:85
changed: [192.168.122.51] => {"changed": true, "cmd": "source 
/home/stack/stackrc && openstack stack failures list overcloud --long", 
"delta": "0:00:11.941587", "end": "2018-05-17 15:18:52.659738", "rc": 0, 
"start": "2018-05-17 15:18:40.718151", "stderr": "", "stderr_lines": [], 
"stdout": "overcloud.Controller.0.NetworkDeployment:
  resource_type: OS::TripleO::SoftwareDeployment
  physical_resource_id: d861b564-989f-4c68-88f6-cffdc14a92d0
  status: CREATE_FAILED
  status_reason: |
CREATE aborted
overcloud.Compute.1.NetworkDeployment:
  resource_type: OS::TripleO::SoftwareDeployment
  physical_resource_id: 218b77b8-dfb0-4cb4-bb06-dd0a74e7c4dc
  status: CREATE_FAILED
  status_reason: |
CREATE aborted
overcloud.Compute.0.NetworkDeployment:
  resource_type: OS::TripleO::SoftwareDeployment
  physical_resource_id: 8096400a-27fe-4fa6-b1dc-4ed386dc4af1
  status: CREATE_FAILED
  status_reason: |
CREATE aborted
overcloud.Compute.2.NetworkDeployment:
  resource_type: OS::TripleO::SoftwareDeployment
  physical_resource_id: 7aa0ea73-4a95-4cce-8252-838a5f4403a7
  status: CREATE_FAILED
  status_reason: |
Error: resources.NetworkDeployment: Deployment to server failed: 
deploy_status_code : Deployment exited with non-zero status code: 1", 
"stdout_lines": ["overcloud.Controller.0.NetworkDeployment:", "  resource_type: 
OS::TripleO::SoftwareDeployment", "  physical_resource_id: 
d861b564-989f-4c68-88f6-cffdc14a92d0", "  status: CREATE_FAILED", "  
status_reason: |", "CREATE aborted", 
"overcloud.Compute.1.NetworkDeployment:", "  resource_type: 
OS::TripleO::SoftwareDeployment", "  physical_resource_id: 
218b77b8-dfb0-4cb4-bb06-dd0a74e7c4dc", "  status: CREATE_FAILED", "  
status_reason: |", "CREATE aborted", 
"overcloud.Compute.0.NetworkDeployment:", "  resource_type: 
OS::TripleO::SoftwareDeployment", "  physical_resource_id: 
8096400a-27fe-4fa6-b1dc-4ed386dc4af1", "  status: CREATE_FAILED", "  
status_reason: |", "CREATE aborted", 
"overcloud.Compute.2.NetworkDeployment:", "  resource_type: 
OS::TripleO::SoftwareDeployment", "  physical_resource_id: 
7aa0ea73-4a95-4cce-8252-838a5f4403a7", "  status: CREATE_FAILED", "  
status_reason: |", "Error: resources.NetworkDeployment: Deployment to 
server failed: deploy_status_code : Deployment exited with non-zero status 
code: 1"]}


2018-05-17 11:18:54,030 INFO: TASK [Show Keystone output] 

task path: /usr/share/opnfv-apex/ansible/playbooks/deploy_overcloud.yml:87
failed: [192.168.122.51] (item=openstack endpoint list) => {"changed": true, 
"cmd": "source /home/stack/overcloudrc && openstack endpoint list", "delta": 
"0:00:00.005832", "end": "2018-05-17 15:18:53.376600", "item": "openstack 
endpoint list", "msg": "non-zero return code", "rc": 1, "start": "2018-05-17 
15:18:53.370768", "stderr": "/bin/sh: /home/stack/overcloudrc: No such file or 
directory", "stderr_lines": ["/bin/sh: /home/stack/overcloudrc: No such file or 
directory"], "stdout": "", "stdout_lines": []}
failed: [192.168.122.51] (item=openstack service list) => {"changed": true, 
"cmd": "source /home/stack/overcloudrc && openstack service list", "delta": 
"0:00:00.005790", "end": "2018-05-17 15:18:53.949966", "item": "openstack 
service list", "msg": "non-zero return code", "rc": 1, "start": "2018-05-17 
15:18:53.944176", "stderr": "/bin/sh: /home/stack/overcloudrc: No such file or 
directory", "stderr_lines": ["/bin/sh: /home/stack/overcloudrc: No such file or 
directory"], "stdout": "", "stdout_lines": []}
to retry, use: --limit 
@/usr/share/opnfv-apex/ansible/playbooks/deploy_overcloud.retry


2018-05-17 11:18:54,030 INFO: PLAY RECAP 
*
192.168.122.51 : ok=13   changed=11   unreachable=0failed=2


2018-05-17 11:18:54,099 ERROR: Ansible playbook failed. See Ansible logs for 
details.
2018-05-17 11:18:54,099 ERROR: Deployment Failed.  Please check log
Traceback (most recent call last):
  File "/usr/bin/opnfv-deploy", line 10, in 
sys.exit(main())
  File "/usr/lib/python3.4/site-packages/apex/deploy.py", line 499, in main
user='stack', tmp_dir=APEX_TEMP_DIR)
  File "/usr/lib/python3.4/site-packages/apex/common/utils.py", line 141, in 
run_ansible
raise Exception(e)
Exception: Ansible playbook failed. See 

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Thursday from 10:00 AM to 11:
 00 AM effective 5/17/2018 until 11/1/2018. (UTC-05:00) Eastern Time (US & 
 Canada)\nWhere: https://zoom.us/j/5014627785\n\n*~*~*~*~*~*~*~*~*~*\n\nHel
 lo\,\n\nPlease feel free to join us for the StorPerf team meeting.  This s
 chedule runs until the Daylight Savings time ends in North America.\n\nhtt
 ps://zoom.us/j/5014627785 and #opfnv-meeting\n\nAgendas and minutes will b
 e published here:\n\nhttps://wiki.opnfv.org/display/meetings/Storperf+Team
 +Weekly+Meeting\n
RRULE:FREQ=WEEKLY;UNTIL=20181101T14Z;INTERVAL=1;BYDAY=TH;WKST=SU
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20180517T10
DTEND;TZID=Eastern Standard Time:20180517T11
UID:DA85607B-3CE3-4CB4-8C47-903ED6B43DDD
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180511T141002Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116377944
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] [storperf] Nomination of Shrenik Jain as committer

[Beierl, Mark]

Hello, StorPerf committers.

I'd like to redo the committer nomination for Shrenik now that I understand the 
new INFO.yaml file.  Please vote here:

https://gerrit.opnfv.org/gerrit/57293

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [Docs] Missing links for StorPerf docs

[Beierl, Mark]

Thanks very much, Sofia!

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On May 9, 2018, at 11:24, Sofia Wallin 
<sofia.wal...@ericsson.com<mailto:sofia.wal...@ericsson.com>> wrote:

Hi Mark,
From what I can see the StorPerf project doesn’t have a reference added in any 
of these two documents.
I’ll fix it and add you as reviewer.

BR,
Sofia

From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Date: Wednesday, 9 May 2018 at 16:28
To: OPNFV 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [Docs] Missing links for StorPerf docs

Hello,

I'm updating some documentation for StorPerf Fraser 2.0, and gerrit gave me the 
following link for docs [1].  In the Project Release Notes section, there is no 
entry for StorPerf.  StorPerf is also missing from the Testing Developer 
Guides.  What do I need to do in order for the docs (release notes [2], and dev 
guide [3]) from StorPerf to be visible?

[1] 
http://artifacts.opnfv.org/opnfvdocs/review/57075/index.html#document-release/release-notes
[2] 
https://gerrit.opnfv.org/gerrit/gitweb?p=storperf.git;a=tree;f=docs/release/release-notes;h=d2cbcf88cb98ff4721e4aaf01ad2e4c30c57b735;hb=HEAD
[3] 
https://gerrit.opnfv.org/gerrit/gitweb?p=storperf.git;a=tree;f=docs/dev;h=a78df3c6877c8ee9f2cb79e2bd2ba5efc2131544;hb=HEAD

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

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

[opnfv-tech-discuss] [Docs] Missing links for StorPerf docs

[Beierl, Mark]

Hello,

I'm updating some documentation for StorPerf Fraser 2.0, and gerrit gave me the 
following link for docs [1].  In the Project Release Notes section, there is no 
entry for StorPerf.  StorPerf is also missing from the Testing Developer 
Guides.  What do I need to do in order for the docs (release notes [2], and dev 
guide [3]) from StorPerf to be visible?

[1] 
http://artifacts.opnfv.org/opnfvdocs/review/57075/index.html#document-release/release-notes
[2] 
https://gerrit.opnfv.org/gerrit/gitweb?p=storperf.git;a=tree;f=docs/release/release-notes;h=d2cbcf88cb98ff4721e4aaf01ad2e4c30c57b735;hb=HEAD
[3] 
https://gerrit.opnfv.org/gerrit/gitweb?p=storperf.git;a=tree;f=docs/dev;h=a78df3c6877c8ee9f2cb79e2bd2ba5efc2131544;hb=HEAD

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [compass] Virtual install on single node

[Beierl, Mark]

Hello, Mika.

Sorry, no I have not been able to figure it out and due to my erratic schedule 
I am not able to lock down a time to troubleshoot remotely.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On May 7, 2018, at 06:04, Rautakumpu, Mika (Nokia - FI/Espoo) 
<mika.rautaku...@nokia.com<mailto:mika.rautaku...@nokia.com>> wrote:

Hi Mark and Tianwei,

Did you solve this issue? I am also trying to deploy virtual compass on a 
single node and I am getting same error message.

Thanks,

Br,
Mika Rautakumpu
Nokia

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of wutianwei
Sent: Friday, April 20, 2018 4:15 AM
To: Beierl, Mark <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [compass] Virtual install on single node

Hi Mark,


  1.  Make sure ports 67, 69, 80, 443 are free on your node.
  2.  Make sure the docker storage is not overlay(overlay2).
  3.  When deploying nosdn-nofeature-noha scenario

   1). please set the VIRT_NUMBER=2
   2). Please set the 
DHA=./deploy/conf/vm_environment/os-nosdn-nofeature-noha.yml

You can also find us in the IRC channel “#opnfv-compass4nfv”

Thanks,
Tianwei Wu

发件人: Beierl, Mark [mailto:mark.bei...@dell.com]
发送时间: 2018年4月20日 2:29
收件人: wutianwei <wutianw...@huawei.com<mailto:wutianw...@huawei.com>>
抄送: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
主题: Re: [opnfv-tech-discuss] [compass] Virtual install on single node

Hello, and thank you for the information.

I tried a single node installation (Ubuntu 16.04, 512G ram, 88 cores), with 
internet, as follows:

export SCENARIO=os-nosdn-nofeature-noha.yml
export VIRT_NUMBER=4
export VIRT_CPUS=16
export VIRT_MEM=65536
export VIRT_DISK=200G
export DHA=./deploy/conf/vm_environment/os-nosdn-nofeature-ha.yml
export NETWORK=./deploy/conf/vm_environment/unh-virtual1/network.yml
./build.sh (completed successfully)
./deploy.sh

That failed with the following error:

FAILED - RETRYING: cobbler import iso (1 retries left).
failed: [localhost] (item={'key': u'CentOS-7', 'value': {u'cobbler_arch': 
u'x86_64', u'kickstart': u'default.ks', u'iso_name': 
u'CentOS-7-x86_64-Minimal-1708', u'breed': u'redhat', u'ppa_name': 
u'centos7-pike-ppa', u'version': u'centos', u'cobbler_name': 
u'CentOS-7-Minimal-1708', u'aliase': u'centos7'}}) => {"attempts": 10, 
"changed": true, "cmd": "name=\"CentOS-7-Minimal-1708\"\n docker exec 
compass-cobbler bash -c \"service cobblerd restart;\nsleep 3;\ncobbler import 
--name $name \\\n--path /mnt/CentOS-7-x86_64-Minimal-1708 
\\\n--arch x86_64 \\\n--kickstart 
/var/lib/cobbler/kickstarts/default.ks \\\n--breed redhat\"", 
"delta": "0:00:03.602367", "end": "2018-04-19 14:27:34.678629", "failed": true, 
"item": {"key": "CentOS-7", "value": {"aliase": "centos7", "breed": "redhat", 
"cobbler_arch": "x86_64", "cobbler_name": "CentOS-7-Minimal-1708", "iso_name": 
"CentOS-7-x86_64-Minimal-1708", "kickstart": "default.ks", "ppa_name": 
"centos7-pike-ppa", "version": "centos"}}, "rc": 155, "start": "2018-04-19 
14:27:31.076262", "stderr": "Redirecting to /bin/systemctl restart 
cobblerd.service\nhttpd does not appear to be running and proxying cobbler, or 
SELinux is in the way. Original traceback:\nTraceback (most recent call 
last):\n  File \"/usr/lib/python2.7/site-packages/cobbler/cli.py\", line 252, 
in check_setup\ns.ping()\n  File \"/usr/lib64/python2.7/xmlrpclib.py\", 
line 1233, in __call__\nreturn self.__send(self.__name, args)\n  File 
\"/usr/lib64/python2.7/xmlrpclib.py\", line 1587, in __request\n
verbose=self.__verbose\n  File \"/usr/lib64/python2.7/xmlrpclib.py\", line 
1273, in request\nreturn self.single_request(host, handler, request_body, 
verbose)\n  File \"/usr/lib64/python2.7/xmlrpclib.py\", line 1321, in 
single_request\nresponse.msg,\nProtocolError: ", "stderr_lines": ["Redirecting to 
/bin/systemctl restart cobblerd.service", "httpd does not appear to be running 
and proxying cobbler, or SELinux is in the way. Original traceback:", 
"Traceback (most recent call last):", "  File 
\"/usr/lib/python2.7/site-packages/cobbler/cli.py\", line 25

[opnfv-tech-discuss] Release Plan Pages Locked

[Beierl, Mark]

Hello, David

I accidentally forgot to put the StorPerf name into the title of my release 
plan, and it appears to have inherited permissions from the parent page, so I 
cannot edit my release plan:

https://wiki.opnfv.org/display/SWREL/%3CProject+Name%3E+Release+Plan+for+OPNFV+Gambia

Please update the name to StorPerf Release Plan for OPNFV Gambia, thanks.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [release] Fwd: Build failed in Jenkins: storperf-httpfrontend-docker-build-arm-push-fraser #4

[Beierl, Mark]

Hello,

Every StorPerf docker build (x86_64 and arm) failed with the same error:

fatal: //opnfv-6.0.0: '//opnfv-6.0.0' is outside repository
The tag //opnfv-6.0.0 doesn't exist in the repository.

Anyone know what is happening with the docker push job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

Begin forwarded message:

From: Jenkins Notifications 
>
Subject: Build failed in Jenkins: 
storperf-httpfrontend-docker-build-arm-push-fraser #4
Date: April 28, 2018 at 13:18:11 EDT
To: >, 
>, 
>

See 


--
Triggered by Gerrit: https://gerrit.opnfv.org/gerrit/
[EnvInject] - Loading node environment variables.
Building remotely on arm-build5 (opnfv-build-ubuntu-arm ci-resource) in 
workspace 

[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-AuYZf7fw1RMa/agent.43371
SSH_AGENT_PID=43373
[ssh-agent] Started.
$ ssh-add 

Identity added: 

 
(
[ssh-agent] Using credentials jenkins-ci (Jenkins Master SSH)
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://gerrit.opnfv.org/gerrit/storperf
git init 

 # timeout=10
Fetching upstream changes from https://gerrit.opnfv.org/gerrit/storperf
git --version # timeout=10
git fetch --tags --progress https://gerrit.opnfv.org/gerrit/storperf 
+refs/heads/*:refs/remotes/origin/* # timeout=15
git config remote.origin.url https://gerrit.opnfv.org/gerrit/storperf # 
timeout=10
git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
timeout=10
git config remote.origin.url https://gerrit.opnfv.org/gerrit/storperf # 
timeout=10
Fetching upstream changes from https://gerrit.opnfv.org/gerrit/storperf
git fetch --tags --progress https://gerrit.opnfv.org/gerrit/storperf 
+refs/heads/*:refs/remotes/origin/* # timeout=15
git rev-parse refs/remotes/origin/stable/fraser^{commit} # timeout=10
git rev-parse refs/remotes/origin/origin/stable/fraser^{commit} # timeout=10
Checking out Revision 2f8c1546ee5d79f9b4c46e960a74930cfe0fe50e 
(refs/remotes/origin/stable/fraser)
git config core.sparsecheckout # timeout=10
git checkout -f 2f8c1546ee5d79f9b4c46e960a74930cfe0fe50e # timeout=15
Commit message: "Update release notes"
git rev-list --no-walk 2f8c1546ee5d79f9b4c46e960a74930cfe0fe50e # timeout=10
No emails were triggered.
[storperf-httpfrontend-docker-build-arm-push-fraser] $ /bin/bash 
/tmp/jenkins1368040929478355984.sh
Using Docker Docker version 18.01.0-ce, build 03596f5 on arm-build5
Starting Docker build for opnfv/storperf-httpfrontend ...


Current branch: stable/fraser
fatal: //opnfv-6.0.0: '//opnfv-6.0.0' is outside repository
The tag //opnfv-6.0.0 doesn't exist in the repository. Existing tags are:
brahmaputra.1.0
colorado.1.0
danube.1.0
danube.2.0
danube.3.0
opnfv-5.0.0
opnfv-5.0.RC1
opnfv-5.1.0
opnfv-6.0.0
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 43373 killed;
[ssh-agent] Stopped.

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

Re: [opnfv-tech-discuss] [release][gambia] MS1 - project release plans - May 11

[Beierl, Mark]

Hello, David.

What does a release plan look like for the Continuous track?  Is it the same 
plan?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Apr 30, 2018, at 16:09, David McBride 
> wrote:

Team,

We are approaching our first milestone for Gambia, MS1 - release plans.  Please 
create your release plan, then complete the release plan 
summary.

Also, recall that MS1 marks the close of the 
intent-to-participate
 window.  Please make sure that you've sent notification for your project.

Let me know if you have any questions.  Thanks.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
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] [Functest] Healthcheck from Docs Not Working

[Beierl, Mark]

Hello,

I am so sorry, for some reason, I ended up with a directory called 
openstack.creds with a file called openstack.creds in it.  Moving out of the 
directory and having it be a plain file worked.  I don't know how I did that.

Thanks for the quick response.  Also, I will change to fraser-1.0 once it's 
released.  Or should I just use stable for now?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 27, 2018, at 12:10, 
ollivier.ced...@gmail.com<mailto:ollivier.ced...@gmail.com> wrote:

Hello Mark,

I don't think so. I think it's working very well like that.
Could you please double check that you created openstack.creds in the working 
dir as expected ?

Yes, the symlink is already defined:
https://git.opnfv.org/functest/tree/docker/core/Dockerfile#n22

BYW, you're selecting the Gambia version.

Thank you for your feedbacks,
Cédric

On ven., 2018-04-27 at 08:33 -0700, David McBride wrote:
+Trevor, Sofia, Aric

On Fri, Apr 27, 2018 at 6:10 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello,

This might be me doing something incorrectly, but here is my experience.  I 
followed the online documentation [1] to create the environment files and 
execute the health check.  Here is the command I used:

docker run --env-file env \
-v $(pwd)/openstack.creds:/home/opnfv/functest/conf/env_file \
-v $(pwd)/images:/home/opnfv/functest/images \
opnfv/functest-healthcheck

It gave the following error:

IOError: [Errno 2] No such file or directory: '/var/lib/xtesting/conf/env_file'

Do I need to use  -v $(pwd)/openstack.creds:/var/lib/xtesting/conf/env_file 
instead?  If so, should I open a JIRA for the docs?

[1] 
http://docs.opnfv.org/en/latest/submodules/functest/docs/testing/user/configguide/configguide.html

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>


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




--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018<tel:%2B1.805.276.8018>
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride

___
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

[opnfv-tech-discuss] [Functest] Healthcheck from Docs Not Working

[Beierl, Mark]

Hello,

This might be me doing something incorrectly, but here is my experience.  I 
followed the online documentation [1] to create the environment files and 
execute the health check.  Here is the command I used:

docker run --env-file env \
-v $(pwd)/openstack.creds:/home/opnfv/functest/conf/env_file \
-v $(pwd)/images:/home/opnfv/functest/images \
opnfv/functest-healthcheck

It gave the following error:

IOError: [Errno 2] No such file or directory: '/var/lib/xtesting/conf/env_file'

Do I need to use  -v $(pwd)/openstack.creds:/var/lib/xtesting/conf/env_file 
instead?  If so, should I open a JIRA for the docs?

[1] 
http://docs.opnfv.org/en/latest/submodules/functest/docs/testing/user/configguide/configguide.html

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] Functest reporting page 404

[Beierl, Mark]

Hello,

All the Functest reports for Master and Fraser are giving 404 from testresults:

http://testresults.opnfv.org/master/functest/functest.html
http://testresults.opnfv.org/fraser/functest/functest.html

Does anyone know why?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [release][documentation][fraser] MS9 - final documentation (TODAY)

[Beierl, Mark]

Hello, David.

I have merged the release notes for StorPerf [1], but they are not showing up 
in docs.opnfv.org.  What am I missing in the procedure?

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

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Apr 25, 2018, at 13:32, David McBride 
> wrote:

Team,

Please complete your project documentation today.

  1.  Make sure that you complete the documentation compliance 
page
 so that I can credit you for complying with MS9.
  2.  Create a link to your release 
notes.

IMPORTANT NOTE:  Sofia informs me that some people are using the wrong version 
number in the project release notes.  The version number for the April 27 
release is:  6.0.0 (unless, of course, you have one or more minor changes 
following tagging, then it will be 6.0.1, 6.0.2, etc.)

Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
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] [compass] Virtual install on single node

[Beierl, Mark]

Hello,

What are the requirements for deploying compass in a virtual environment.  I am 
trying to use the LaaS pods, and I only have one IP address for management.  
Therefore, there is no provider network.  Can I just create a non-routed 
interface on one of the unused NICs, or do I need to have multiple physical 
networks in place?  Alternatively, should I create a VM with the networks in 
place and use that for all the deployments?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [JOID] Virtual installation

[Beierl, Mark]

Hello,

I'm trying to install JOID in one of the OPNFV LaaS servers.  I cannot seem to 
find documentation on how to do a virtual deployment, and was wondering if 
anyone can point me in the right direction.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Beierl, Mark]

Thanks everyone.

That is consistent then with what I thought I understood the state of the LaaS 
setup.

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 10, 2018, at 15:22, Joe Kidder 
<joe.kid...@5thlayer.com<mailto:joe.kid...@5thlayer.com>> wrote:

Mark
  In the current LaaS setup, you can’t connect servers together to form a pod.
  That will come later.

  For now, on arm64 servers in LaaS, you would have to a bare metal one node 
deployment which is not supported by fuel/Mcx at this time.

Joe

On Apr 10, 2018, at 3:09 PM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:

Hello, Alex, and thanks!

I did not realize that one could combine reservations into a single FUEL 
deployment.  I thought I read somewhere that they were not interconnected other 
than management, but I can't find that statement anymore.

Would you have a sample config file for FUEL that would get me pointed in the 
right direction if I want to look at this?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 9, 2018, at 19:08, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:

Hi,
+Joe

Lincoln is right, you could spawn a VM, but it would be emulated without hw 
acceleration, so not really useful.
Reserving a single aarch64 node might be limiting though, Armband Fuel requires 
at least 6 nodes (1 jump server + 5 cluster nodes) right now.
Not sure what the mininum requirement for Compass4NFV + k8 are, but if you want 
to stick to Openstack, you should try reserving more nodes (afaik, there are 
enough available in UNH lab).

BR,
Alex

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Lincoln Lavoie <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>
Sent: Friday, April 6, 2018 4:48:18 PM
To: Beierl, Mark
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Parker Berberian
Subject: Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on 
LaaS ARM

Hi Mark,

I think you can do a virtual deployment, which is 1 level of VMs.  But, I don't 
think you can host a VM on top of the open stack deployment (because that's 
nested).

Cheers,
Lincoln

On Fri, Apr 6, 2018 at 9:45 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, Parker, and thanks for the quick response.

So to be clear, I cannot deploy OPNFV on this system at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 6, 2018, at 09:43, Parker Berberian 
<pberber...@iol.unh.edu<mailto:pberber...@iol.unh.edu>> wrote:

Mark,

You have to be mindful that ARM does not support nested virtualization (and 
therefore virtual deployments with openstack are impossible). If Fuel does not 
support Kubernetes, then you may be out of luck until we can provide pharos 
POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>






--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=CsROVeRb2MMZnSYARa9RdXeTTOZdd-weGwrgnEAGPZ9c7-pubt0BVhEGk5FByPLSEnH9XZh9bKigGlcsA8wezQfaSi-KNgxaHXb0YMM7H1EwrZsC3F2-h7610pC0dvDKA4lvCpdSXIdvsSadLtGtDwDbsNBVTY_Bkvevgvu4d4jIJp0QOjwIFeCv1ws1hJt_fVkPWMjhMzl1pa8vjf2PJ9RWDM-00xNZ9mggQ30tFK4>
www.iol.unh.edu<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=CsROVeRb2MMZnSYARa9RdXeTTOZdd-weGwrgnEAGPZ9c7-pubt0BVhEGk5FByPLSEnH9XZh9bKigGlcsA8wezQfaSi-KNgxaHXb0YMM7H1EwrZsC3F2-h7610pC0dvDKA4lvCpdSXIdvsSadLtGtDwDbsNBVTY_Bkvevgvu4d4jIJp0QOjwI

Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Beierl, Mark]

Hello, Alex, and thanks!

I did not realize that one could combine reservations into a single FUEL 
deployment.  I thought I read somewhere that they were not interconnected other 
than management, but I can't find that statement anymore.

Would you have a sample config file for FUEL that would get me pointed in the 
right direction if I want to look at this?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 9, 2018, at 19:08, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:

Hi,
+Joe

Lincoln is right, you could spawn a VM, but it would be emulated without hw 
acceleration, so not really useful.
Reserving a single aarch64 node might be limiting though, Armband Fuel requires 
at least 6 nodes (1 jump server + 5 cluster nodes) right now.
Not sure what the mininum requirement for Compass4NFV + k8 are, but if you want 
to stick to Openstack, you should try reserving more nodes (afaik, there are 
enough available in UNH lab).

BR,
Alex

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Lincoln Lavoie <lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>>
Sent: Friday, April 6, 2018 4:48:18 PM
To: Beierl, Mark
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Parker Berberian
Subject: Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on 
LaaS ARM

Hi Mark,

I think you can do a virtual deployment, which is 1 level of VMs.  But, I don't 
think you can host a VM on top of the open stack deployment (because that's 
nested).

Cheers,
Lincoln

On Fri, Apr 6, 2018 at 9:45 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, Parker, and thanks for the quick response.

So to be clear, I cannot deploy OPNFV on this system at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 6, 2018, at 09:43, Parker Berberian 
<pberber...@iol.unh.edu<mailto:pberber...@iol.unh.edu>> wrote:

Mark,

You have to be mindful that ARM does not support nested virtualization (and 
therefore virtual deployments with openstack are impossible). If Fuel does not 
support Kubernetes, then you may be out of luck until we can provide pharos 
POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>






--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=CsROVeRb2MMZnSYARa9RdXeTTOZdd-weGwrgnEAGPZ9c7-pubt0BVhEGk5FByPLSEnH9XZh9bKigGlcsA8wezQfaSi-KNgxaHXb0YMM7H1EwrZsC3F2-h7610pC0dvDKA4lvCpdSXIdvsSadLtGtDwDbsNBVTY_Bkvevgvu4d4jIJp0QOjwIFeCv1ws1hJt_fVkPWMjhMzl1pa8vjf2PJ9RWDM-00xNZ9mggQ30tFK4>
www.iol.unh.edu<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=CsROVeRb2MMZnSYARa9RdXeTTOZdd-weGwrgnEAGPZ9c7-pubt0BVhEGk5FByPLSEnH9XZh9bKigGlcsA8wezQfaSi-KNgxaHXb0YMM7H1EwrZsC3F2-h7610pC0dvDKA4lvCpdSXIdvsSadLtGtDwDbsNBVTY_Bkvevgvu4d4jIJp0QOjwIFeCv1ws1hJt_fVkPWMjhMzl1pa8vjf2PJ9RWDM-00xNZ9mggQ30tFK4>
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=zGhpII7F5ErXzy8oUlI-H3jlbiUCA-_BHzzWbxyR1OS3Q2vxkeD_fetUw0QFvEDvG0ZE7gIxewjTwwIeYYyf_FPZ_xZwnTi80GyJlTeD_jiGpfcDmvpQ1Tdr77TPByjF5A69AkdXuYqmSx-BFNAqBiWS5qUbe02W7JRG21lQ3j0shzs0g-pBASqVz-U4h9ZxGK5GbK6WvThJ9wIWDmXT2kRR7ff1opp5siompkP2p-Q>
  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png] 
<https://url10.mailanyone.net/v1/?m=1f4RjW-0002ZB-4t=57e1b682=ZgygfqHLXZEiIpzALM0BiBInhTVv1dBG41Rl2AUhbTbKpQPawsYT2f--JUZjoUDjt7vnrzE4iPAGxQUsnFSx80iLOC9duj

Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Beierl, Mark]

Hello,

That is consistent then with my prior experience in the Flex pod.  When I 
launched a VM it took forever to boot :)

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 6, 2018, at 09:48, Lincoln Lavoie 
<lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>> wrote:

Hi Mark,

I think you can do a virtual deployment, which is 1 level of VMs.  But, I don't 
think you can host a VM on top of the open stack deployment (because that's 
nested).

Cheers,
Lincoln

On Fri, Apr 6, 2018 at 9:45 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, Parker, and thanks for the quick response.

So to be clear, I cannot deploy OPNFV on this system at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 6, 2018, at 09:43, Parker Berberian 
<pberber...@iol.unh.edu<mailto:pberber...@iol.unh.edu>> wrote:

Mark,

You have to be mindful that ARM does not support nested virtualization (and 
therefore virtual deployments with openstack are impossible). If Fuel does not 
support Kubernetes, then you may be out of luck until we can provide pharos 
POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>






--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://www.iol.unh.edu/>
www.iol.unh.edu<https://www.iol.unh.edu/>
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]<http://www.facebook.com/UNHIOL#>
  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png] 
<https://twitter.com/#!/UNH_IOL>   
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png] 
<http://www.linkedin.com/company/unh-interoperability-lab>

Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.

Broadband Forum Gfast Certified Product 
List<https://www.broadband-forum.org/implementation/interop-certification/gfast-certified-products>
***
___
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] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Beierl, Mark]

Hello, Parker, and thanks for the quick response.

So to be clear, I cannot deploy OPNFV on this system at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Apr 6, 2018, at 09:43, Parker Berberian 
<pberber...@iol.unh.edu<mailto:pberber...@iol.unh.edu>> wrote:

Mark,

You have to be mindful that ARM does not support nested virtualization (and 
therefore virtual deployments with openstack are impossible). If Fuel does not 
support Kubernetes, then you may be out of luck until we can provide pharos 
POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>



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

[opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Beierl, Mark]

Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] yardstick

[Beierl, Mark]

Hello,

Which version of StorPerf are you using?  You should be able to change the port 
for StorPerf HTTP Front End in the docker-compose.yaml file to a different 
port.  What is the error you are seeing, please?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Apr 4, 2018, at 03:04, Rawzan Masood 
> wrote:

We are trying to install StorPerf plugin to the yardstick environment  for 
storage testing , the storperf swagger uses port 5000  which is the default for 
storperf plugin . In the same time we are using Yardstick REST APIs which use 
the same port too (5000)
We tried to install storPerf plugin as docker on another port , but it didn't 
work
so , how we can install it on a specific port without facing conflicts which 
the REST APIs.
___
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] [TestResults DB] Cannot create pod in testresults db

[Beierl, Mark]

Hello, everyone.

I'm trying to create a pod entry for flex-pod2 in the testresults db using the 
swagger API.  I'm logged in, but the post is returning HTTPError: HTTP 401: 
TestAPI id is not provided.  Here is the payload:

{
  "role": "",
  "name": "flex-pod2",
  "details": "5 bare metal servers",
  "mode": "metal"
 }

And the full response from Swagger UI:

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1401, in 
_stack_context_handle_exception
raise_exc_info((type, value, traceback))
  File "/usr/local/lib/python2.7/dist-packages/tornado/stack_context.py", line 
314, in wrapped
ret = fn(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1613, in 
future_complete
f.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 
232, in result
raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014, in 
run
yielded = self.gen.throw(*exc_info)
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py", 
line 62, in wrapper
ret = yield gen.coroutine(method)(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008, in 
run
value = future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 
232, in result
raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014, in 
run
yielded = self.gen.throw(*exc_info)
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py", 
line 85, in wrap
ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008, in 
run
value = future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 
232, in result
raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014, in 
run
yielded = self.gen.throw(*exc_info)
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py", 
line 100, in wrap
ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008, in 
run
value = future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 
232, in result
raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1014, in 
run
yielded = self.gen.throw(*exc_info)
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py", 
line 144, in wrap
ret = yield gen.coroutine(xstep)(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 1008, in 
run
value = future.result()
  File "/usr/local/lib/python2.7/dist-packages/tornado/concurrent.py", line 
232, in result
raise_exc_info(self._exc_info)
  File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 282, in 
wrapper
yielded = next(result)
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/check.py", 
line 27, in wrapper
raises.Unauthorized(message.not_login())
  File "/usr/local/lib/python2.7/dist-packages/opnfv_testapi/common/raises.py", 
line 18, in __init__
raise web.HTTPError(self.code, reason=reason)
HTTPError: HTTP 401: TestAPI id is not provided

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] cannot git push

[Beierl, Mark]

Hello,

I am not sure if this has been mentioned already.

Please be aware that git push is not supported by the OPNFV Gerrit workflow.  
You must install git review [1] and issue a git review command after your 
commits.  This will trigger an upload of the change set and create a new 
review.  Only a committer can cause the change to be submitted (pushed) from 
Gerrit into the main git repo.

[1] https://www.mediawiki.org/wiki/Gerrit/git-review

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Jan 30, 2018, at 05:05, Trinath Somanchi 
> wrote:

Please ensure that your Firewall doesn’t block the port 29418.

As a test, verify the same git push from your CORP/Company network and Home 
Network.


/ Trinath
NXP | HSDC | INDIA



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of ??
Sent: Monday, January 29, 2018 2:56 PM
To: agardner >
Cc: opnfv-tech-discuss 
>;
 eric.dmaye >
Subject: [opnfv-tech-discuss] cannot git push

 hi,

i'm trying to do the git review operation,but it always fail. it warns me that 
"ssh://zc9...@gerrit.opnfv.org:29418/auto.git did not work. Description: 
Permission denied (publickey)",but i don't know why

this is my gerrit page information:





this is the ~/.ssh/id_rsa.pub on my linux:



and i have confirmed that the public key is added with the below configuration:


eval `ssh-agent -s`ssh-add ~/.ssh/id_rsa.pub

ssh-add ~/.ssh/id_rsa.pub

when i do the "git review -v" operation, the terminal warns:



plz help me with the problem, thx very much!


Regards,
Chen

___
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] Any installer support for Swift?

[Beierl, Mark]

Hello,

I am wondering if any of the OPNFV installers support Swift at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Committer nomination for Shrenik Jain

[Beierl, Mark]

Hello,

I would like to nominate Shrenik Jain as a committer for StorPerf.  Since being 
an intern last summer, Shrenik has been a valuable contributor to the project.

StorPerf members, please vote +1/-1.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] Collecting questions for the Biterg Dashboard Training //RE: Issues/Needs/requirements for Biterg dashboard

[Beierl, Mark]

Hello, folks.

This is the test results dashboard, not analytics on git/wiki/mailing list, 
etc, usage.  Bitergia has a second contract with LF to provide visualizations 
for the various test projects output.  Hope that clears things up :)

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Jan 11, 2018, at 11:12, SULLIVAN, BRYAN L (BRYAN L) 
> wrote:

If it results in some gaps being better socialized and prioritized, it's a good 
idea to meet. E.g. I sent a request back in Nov and got no response... it was:

I’d like the ability to view/download the full set of data for a particular 
query, e.g. as you have from stackalytics (setting for “Show  entries”).

Thanks,
Bryan Sullivan | AT

-Original Message-
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Thursday, January 11, 2018 6:50 AM
To: Yuyang (Gabriel) 
>; 
'opnfv-tech-discuss@lists.opnfv.org' 
>;
 test...@lists.opnfv.org
Cc: Alberto Pérez García-Plaza 
>; Alvaro del Castillo 
>; Jesus M. Gonzalez-Barahona 
>
Subject: Re: [opnfv-tech-discuss] Collecting questions for the Biterg Dashboard 
Training //RE: Issues/Needs/requirements for Biterg dashboard

Hi,

Is the goal to get a better idea of how we can use the dashboard ("How
can I tell how many companies were active in a project between date 1
and date 2, excluding LF employees? What data sources are available for
query?" type questions), or is it to identify qualitative questions we
would like to answer with data ("Are we keeping participants over time?
Are there projects for which timely  patch review/acknowledgement of
issues is a challenge?") - understanding the goal of the tutorial would
help with identifying the right questions to ask.

Thanks,
Dave.

On 01/11/2018 04:40 AM, Yuyang (Gabriel) wrote:
Hi Community,



As discussed, Biterg will arrange a training session of OPNFV statistics
dashboard for the community in test working group meeting.

Basically, it will last about 1 hour as the usual first training
covering the needs of navigating through panels, filtering the relevant
results, sharing and exporting capabilities, etc.

Before this wonderful thing could happen, it would better if you look at
the dashboard first and feedback questions regarding the operations,
visualizations,  settings, statistics results and etc. as input for the
training.

So that the training session could meet your needs in more efficient manner.



During last Testperf meeting, we have already discussed some needs and
questions which are listed below. Please post your questions/needs behind.

1.   How the commit number is calculated? What are involved in this
metric? Including review?

2.   When searching commit number for a specific person, there will
be other persons involved in the results page. Are these persons for the
calculation of reviews?

3.   How should I search for the statistics results (commits, code
line, patchsets, etc., ) of a project with aggregation results of
companies, persons involved in this project

4.   Needs for comprehensive introduction of the dashboard including
every operations, filtering relevant information, where the dashboard
retrieve datas, etc.?



Thanks,

Gabriel



*From:*Yuyang (Gabriel)
*Sent:* Thursday, January 04, 2018 9:43 AM
*To:* 'Alberto Pérez García-Plaza' 
>
*Cc:* 'Alvaro del Castillo' >; 
'Raymond Paik'
>; 
'mark.bei...@emc.com'
>; 'Brandon Wick' 
>;
'jalaus...@suse.com' 
>; 'Rao, Sridhar'
>; 'Jesus M. 
Gonzalez-Barahona'
>; 
'cedric.olliv...@orange.com'
>; 'Brattain, 
Ross B'
>; 'Cooper, Trevor' 
>;
'test...@lists.opnfv.org' 

[opnfv-tech-discuss] Anyone using GTM time slot Thursday 16:00 UTC?

[Beierl, Mark]

Hello,

I'd like to find a new time slot for the StorPerf weekly meeting, and while the 
main calendar shows QTIP at that time [1], according to the QTIP page [2] it's 
at 0730 UTC on Mondays.

So is anyone using the 16:00-17:00 UTC time slot on Thursday?

[1] https://wiki.opnfv.org/display/meetings
[2] 
https://wiki.opnfv.org/display/qtip/Platform+Performance+Benchmarking#PlatformPerformanceBenchmarking-Meeting

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [SNAPS] Support for multi-part HOT

[Beierl, Mark]

Hello,

It looks like it is not possible to create a Heat stack that requires two 
parts: the main template, then a secondary template to repeat N number of 
times.  See [1] for a reference.  The way it works is there is a master 
template to define the overall stack, and then pass a second template for the 
group that repeats.  This is how we create multiple VMs with the same Cinder 
volume attached in StorPerf.

Can anyone from SNAPS confirm if this can be done with the current 
implementation, or if a change is required to support this?

[1] 
https://developer.rackspace.com/blog/openstack-orchestration-in-depth-part-3-multi-instance-deployments/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] Docker builds failing for ARM

[Beierl, Mark]

Hello,

All the StorPerf docker builds on ARM have been failing since some time in 
November.  Here is the last successful build [1], which shows the --build-arg 
for ARCH in place:

docker build --no-cache -t opnfv/storperf-master:aarch64-latest --build-arg 
BRANCH=master --build-arg ARCH=aarch64 -f Dockerfile

The next build no longer has that code in place [2]:

docker build --no-cache -t opnfv/storperf-master:aarch64-latest --build-arg 
BRANCH=master -f Dockerfile .

This appears to be the related change [3].  Can we get that put back?  The git 
review to re-instate it is here [4].  I cannot push the OPNFV 5.1.0 release of 
StorPerf without it.

[1] 
https://build.opnfv.org/ci/view/storperf/job/storperf-master-docker-build-arm-push-master/22/console
[2] 
https://build.opnfv.org/ci/view/storperf/job/storperf-master-docker-build-arm-push-master/23/console
[3] 
https://github.com/opnfv/releng/commit/e25af7fd788db267247abb6b4efa4cf2dff73f32#diff-80ab330132d9f5ae6e27a1ae7b186eb8
[4] https://gerrit.opnfv.org/gerrit/49565

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] StorPerf weekly meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=siddharth.
 go...@flex.com:MAILTO:siddharth.go...@flex.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Shrenik Ja
 in:MAILTO:shrenik.j...@research.iiit.ac.in
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=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Taseer Ahm
 ed:MAILTO:tasee...@gmail.com
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, December 21\, 2017 9:00 AM-10:0
 0 AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotome
 eting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nI think the Test Workin
 g Group meeting occurs the hour after this\, so I will try to hold the Sto
 rPerf meeting at this time.\n\nThe TC meeting also occurs at this same tim
 e\, so hopefully we are using the correct GTM account and do not conflict 
 with them.\n\nIf needed\, we will use #opnfv-storperf IRC channel.\n\nhttp
 s://global.gotomeeting.com/join/819733085\n
SUMMARY;LANGUAGE=en-US:StorPerf weekly meeting
DTSTART;TZID=Eastern Standard Time:20171221T09
DTEND;TZID=Eastern Standard Time:20171221T10
UID:9EB516FC-E685-4FC5-A71F-28643A77A9AC
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171220T164250Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115805861
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] [test-wg] New meeting series

[Beierl, Mark]

Hello,

Has the test working group meeting series been set up yet?  The old invite 
expired and I don't seem to have a new one.  When is it now that the times have 
changed for some countries?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] JetBrains Licenses

[Beierl, Mark]

Hello,

Just a heads up that JetBrains has revised the terms of their license which 
will exclude most of us from applying for the free license under the Open 
Source Project terms:

"The rules of the Program have changed since last year. If there is a company 
or an organization (NGO, educational, research or governmental) behind the OS 
project if the developers are employed to work on the project or it receives 
sponsorship we can no longer issue the free licenses on general 
terms, sorry."

Because I work for a company that pays me a salary to contribute to OPNFV, I'm 
not allowed to apply for the free licence anymore.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] Multi-Arch Docker Blog

[Beierl, Mark]

Thanks, Cédric

Unfortunately I will not be at the Plugfest, so if you do a session, is it 
possible to record it?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Dec 1, 2017, at 09:58, 
cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com> wrote:

Hello,

Functest containers already leverage on Docker manifests. It's part of our 
docker refactoring which included slicing, manifests, releng multijobs...

I will introduce it next week if you're interested in and the changes required.

Cédric

---- Beierl, Mark a écrit 

Hello,

Here is an overview of using manifests to specify architecture for Docker 
containers [1].  This could simplify the approach that I used in StorPerf where 
I put the Arch into the tag, so I have taken an action item for myself as part 
of StorPerf.  If anyone already has experience with this, or has started moving 
towards using manifest instead, I'd love to hear your feedback.

[1] https://blog.docker.com/2017/11/multi-arch-all-the-things/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


___
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

[opnfv-tech-discuss] Multi-Arch Docker Blog

[Beierl, Mark]

Hello,

Here is an overview of using manifests to specify architecture for Docker 
containers [1].  This could simplify the approach that I used in StorPerf where 
I put the Arch into the tag, so I have taken an action item for myself as part 
of StorPerf.  If anyone already has experience with this, or has started moving 
towards using manifest instead, I'd love to hear your feedback.

[1] https://blog.docker.com/2017/11/multi-arch-all-the-things/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [Infra] Request for a StorPerf pod

[Beierl, Mark]

Hello, Fatih!

Ticket created [1], thanks.

[1] https://jira.opnfv.org/browse/INFRA-195

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Nov 29, 2017, at 14:08, Fatih Degirmenci 
<fatih.degirme...@ericsson.com<mailto:fatih.degirme...@ericsson.com>> wrote:

Hi Mark,

Can you please put this request to JIRA INFRA project so we can follow it up 
properly?
We can include this as a topic to Infra WG Meeting so please keep an eye on the 
meeting agenda and join if possible.

Please note that we haven’t decided if we will have the Infra WG Meeting on 
December 4th due to OPNFV Plugfest so your ticket might be discussed on 
December 11th – if you still don’t have a BM POD/vPOD by then.

/Fatih

From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Date: Wednesday, 29 November 2017 at 15:15
To: 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [Infra] Request for a StorPerf pod

Hello,

Since Intel is no longer able to provide their pod 24 for StorPerf, we are now 
in the position of seeing if there is any other pod or vpod that we can use for 
StorPerf development and testing.  Please let me know what the procedure is to 
request a new pod.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>



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

[opnfv-tech-discuss] [Infra] Request for a StorPerf pod

[Beierl, Mark]

Hello,

Since Intel is no longer able to provide their pod 24 for StorPerf, we are now 
in the position of seeing if there is any other pod or vpod that we can use for 
StorPerf development and testing.  Please let me know what the procedure is to 
request a new pod.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] Canceled: [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, October 26\, 2017 2:00 PM-3:00 
 PM. UTC\nWhere: https://global.gotomeeting.com/join/819733085\n\n*~*~*~*~*
 ~*~*~*~*~*\n\nHello\,\n\nPlease feel free to join us for the StorPerf team
  meeting.  This schedule runs until the Daylight Savings time change in No
 rth America.\n\nhttps://global.gotomeeting.com/join/819733085\n\nhttps://w
 iki.opnfv.org/display/meetings/Storperf+Team+Weekly+Meeting\n
SUMMARY;LANGUAGE=en-US:Canceled: [StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20171026T10
DTEND;TZID=Eastern Standard Time:20171026T11
UID:F813D04F-8EEC-49A9-BAA6-FA12447ABCA3
RECURRENCE-ID;TZID=Eastern Standard Time:20171026T10
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171024T134537Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:3
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:3
X-MICROSOFT-CDO-OWNERAPPTID:2115579989
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: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] [functest] Alpine for arch

[Beierl, Mark]

Cédric,

I am curious, how does the manifest help with avoiding FROM? Is it that we 
would use that to pull the correct base Alpine image?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Oct 15, 2017, at 23:55, 
"cedric.olliv...@orange.com" 
> wrote:

Alex,

Yes. You know I was waiting for tests from your side. As manifest works as 
expected, we can remove most of them.

But I will keep the one to build/publish containers in any repo as it's very 
useful.

My sentence was focused on Functest.

Cédric

 Alexandru Avadanii a écrit 

Hi,

> -Original Message-
> From: Cedric OLLIVIER [mailto:ollivier.ced...@gmail.com]
> Sent: Sunday, October 15, 2017 8:27 PM
> To: Alec Hothan (ahothan)
> Cc: Alexandru Avadanii; Fatih Degirmenci; 
> cedric.olliv...@orange.com; opnfv-
> tech-discuss; Delia Popescu; David McBride; 
> morgan.richo...@orange.com
> Subject: Re: [opnfv-tech-discuss] [functest] Alpine for arch
>
> Hello Alec,
>
> Please find several answers inline.
>
> Cédric
>
> 2017-10-14 20:55 GMT+02:00 Alec Hothan (ahothan) 
> >:
> >
> >
> > Alex: this looks like a good plan and seems to take care of all
> > functest requirements wrt build.
> >
>
> [Cédric]
> Absolutly not as the second point is false from our point of view.
> We prefer Docker manifests to useless variables in FROM instructions what
> would break the current builds.
> I will translate my travis-ci jobs to releng jjobs after E is published.

[Alex]
For the record, the cost of dismissing FROM ARG is duplicating the Dockerfile 
(either with a patch, or with a series of runtime sed, e.g. [1] vs [2]).
Also, Storperf requires the latest Docker, and has no issues on the current 
OPNFV builders, so those are already up to date.
I'm not saying FROM ARG should be enforced, but if some projects want to use 
it, they should be allowed to, instead of juggling with FROM using sed or 
patches.

BR,
Alex

[1] https://gerrit.opnfv.org/gerrit/#/c/44999/1/build.sh
[2] 
https://github.com/opnfv/storperf/blob/master/docker/storperf-graphite/Dockerfile#L17-L19

>
> >
> >
> > What we need to nail down next is the versioning and how it plays out
> > with Functest CI, Functest XCI and lastly to the release.
> >
> >
> >
> > It is critical to nail down the versioning and branching model first
> > before rushing to modify the releng tools/scripts. The current
> > versioning and branching model is insufficient (as a proof see what
> > functest is doing to overcome the limitations). We need direction and
> > the XCI project is the right place to determine the overall versioning
> > model for all OPNFV projects.
> >
> >
>
> >
> > Cedric: your wiki on releng requirements is a good start. It will be
> > great if it could also have the following information:
>
> [Cédric]
>
> I think it's quite clear how Functest must be improved to implement a real
> Functest Functional gating via XCI.
> I believe releng could have been updated as soon as Functest started splitting
> the containers. We have developped build.sh as initially proposed.
> For your information, the wiki page is hugely completed by my previous email
> and the travis-ci jobs already published (and running in my private repo):
> https://git.opnfv.org/functest/tree/.travis.yml?h=stable/euphrates
> https://travis-ci.org/collivier/functest/builds/287849046
> https://travis-ci.org/collivier/functest/builds/287745681
>
> >
> > Functest CI: what is gating every functest commit? (this is normally
> > the script that gates every gerrit commit on functest master) Functest
> > XCI: how is a new version of Functest gated for XCI use Functest
> > release: how is the right version of Functest picked for release (I
> > think I know how this works based on emails with you/Morgan, but it is
> > good to put this down)
> >
> >
>
> [Cédric]
> It's triggered as soon as a change is merged on github.
> Could you please have a look to the next wiki page which lists the first 
> steps to
> implement a real Functional gating.
> Technically speaking, the main difficulties have been done for E release
> (Docker slicing, requirements management...).
> https://wiki.opnfv.org/display/functest/Functional+testing+gating
>
> Of course we require releng jjobs to manage gerrit patchset. It has been clear
> for a while.
> I agreed to work on it to go further even.
>
> >
> > If we look at the git tags and the container tags:
> >
> > From a quick look at the git repo, Functest currently only uses the
> > release git tags as imposed by the release (the “danube.1.0.0” and now
> > “opnfv-5.0.0”). So we can say that functest does not have any project
> > specific versioning per se.
> >
> > However it is unclear if the 

Re: [opnfv-tech-discuss] [announce] user support topic for the TSC call

[Beierl, Mark]

So far I have had a good experience with users reporting issues via JIRA. I 
must admit the askbot site has not been very useful for me at this time.

Perhaps we need to highlight it more in the user guides?  I know I have not 
done that.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Oct 15, 2017, at 15:19, Raymond Paik 
> wrote:

All,

I'd like to propose having a discussion on user support in an upcoming TSC 
call.  We have two primary channels for user support which are opnfv-user 
mailing list plus our Askbot site (https://ask.opnfv.org/questions/).

Over the past several quarters the activity on the Askbot site in particular 
has gone down (see 
https://opnfv.biterg.io:443/goto/5f1aedc882d4c3e33a1e3bab812e353e), and I'd 
like to start a discussion on support channel for OPNFV users plus other tools 
(e.g. documentation, wiki, etc.).

I'll add this as a topic for the TSC call on the 17th, but I think it'd also 
make sense to have follow-up discussions with anyone interested in 
participating following the TSC call.

In the mean time, if you have any suggestions or thoughts on this topic, please 
feel free to chime in

Thanks,

Ray
___
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] StorPerf talk at OpenStack Days Canada

[Beierl, Mark]

Hello,

Probably not a lot of folks will be in Ottawa, Canada on the 19, but if you 
are, I have a talk on OPNFV StorPerf at the OpenStack Days Canada conference at 
2:10.

https://www.openstackcanada.com/schedule/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] Swift Support

[Beierl, Mark]

Hello,

I was wondering what installers or use cases we have in OPNFV for Swift object 
storage.  One of the planning activities for StorPerf Fraser would be Swift 
profiling, but I am not sure how useful that is to the community.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Taseer Ahm
 ed:MAILTO:tasee...@gmail.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=s.pisarski
 @cablelabs.com:MAILTO:s.pisar...@cablelabs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, October 12\, 2017 11:00 AM-12:0
 0 PM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotome
 eting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nThis is a sp
 ecial\, one time change to StorPerf so we can sync up with  Steven Pisarsk
 i of SNAPS-OO and how StorPerf can leverage it.\n\nhttps://global.gotomeet
 ing.com/join/819733085\n\nhttps://wiki.opnfv.org/display/meetings/Storperf
 +Team+Weekly+Meeting\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20171012T11
DTEND;TZID=Eastern Standard Time:20171012T12
UID:F813D04F-8EEC-49A9-BAA6-FA12447ABCA3
RECURRENCE-ID;TZID=Eastern Standard Time:20171012T10
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171011T141221Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:2
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:2
X-MICROSOFT-CDO-OWNERAPPTID:2115579989
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:-PT5M
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] [StorPerf] Cancelling weekly meeting

[Beierl, Mark]

Hello,

I won't be able to chair the meeting today, so I am cancelling it, sorry.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Beierl, Mark]

+1

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Oct 4, 2017, at 14:44, David McBride 
> wrote:

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, or 
alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
Euphrates release (5.0) to October 20.  In addition, I also proposed 
eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
The reasoning was as follows:

  1.  Moving the 5.0 release to Oct 20 places that release just 3 weeks before 
the planned release of 5.1 (Nov 10).
  2.  Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
release, as happened with Euphrates when we decided to slip Danube 3.0.

Therefore, the proposal is to eliminate the planned release on Nov 10, so that 
there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented 
during the TSC 
meeting (see 
link labeled "euphrates contingency.pptx" under the heading "Euphrates update").

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-project-leads mailing list
opnfv-project-le...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads

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

[opnfv-tech-discuss] Many failed docker builds

[Beierl, Mark]

Hello,

Not sure who can help with this.  Right now there are 4 or more executor slots 
than can execute any given opnfv-docker.sh script.  The problem is with so many 
docker jobs being introduced in Euphrates, we are getting a lot of failures due 
to timeouts.  For example, on arm-build4, 4 docker builds can start in 
parallel, but only one will pass the build in progress check.  The other 3 jobs 
will wait for the first build to complete, and then the next will start.  If 
the total wait time for any of the builds exceeds 30 minutes, we get a failure.

This is happening more frequently.  There are a couple options that I can see:

*  Reduce the number of executors to 1.  This might have unintended 
side-effects on build times for other jobs.
*  Reduce the number of executors to 1 and add more slaves for the given 
hardware (both ARM and x86)
*  Fix the opnfv-docker.sh script so that it can allow more than one docker 
build to execute simultaneously.  I don't know what this would encompass.

I would really love to hear other's opinions on what can be done.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] stable branch window

[Beierl, Mark]

Hello, Alec.

In Confluence, you can "watch" a space and will then receive email 
notifications every time a page is created/updated/deleted.  It's the little 
[cid:A519D3C8-5EB4-4FEF-ABBA-D8F70441C283@corp.emc.com] icon for a page, or 
from the home page of a space this will poop up:

[cid:D6DC9ADC-66DC-40ED-8382-3547FD324A68@corp.emc.com]

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Sep 15, 2017, at 15:24, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:

Thanks Mark,

That is exactly what I was looking for and your explanation below makes perfect 
sense (and should be added to that page).

I wonder how do we get to know when these wiki pages are created? Do I need to 
attend release meetings or subscribe to some mailer?
I am relieved the tags have a “Euphrates” prefix ;-)

  Alec


From: "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Date: Friday, September 15, 2017 at 12:04 PM
To: "Alec Hothan (ahothan)" <ahot...@cisco.com<mailto:ahot...@cisco.com>>
Cc: David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>,
 opnfv-project-leads 
<opnfv-project-le...@lists.opnfv.org<mailto:opnfv-project-le...@lists.opnfv.org>>,
 Tapio Tallgren <tapio.tallg...@nokia.com<mailto:tapio.tallg...@nokia.com>>, 
Raymond Paik <rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>>, 
Trevor Bramwell 
<tbramw...@linuxfoundation.org<mailto:tbramw...@linuxfoundation.org>>, "Aric 
Gardner (agard...@linuxfoundation.org<mailto:agard...@linuxfoundation.org>)" 
<agard...@linuxfoundation.org<mailto:agard...@linuxfoundation.org>>
Subject: Re: [opnfv-project-leads] [release][euphrates] stable branch window

Hello, Alec.

The process for the euphrates.1.0, 2.0 etc is documented here: 
https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Euphrates

The stable branch essentially means that no code review can be directly 
submitted against stable/euphrates.  Essentially all bug fixes and changes 
should go to master and then get independently cherry pick git Gerrit to the 
stable/euphrates branch.

Once you are happy with the state of your stable branch, the tagging 
instructions are followed.  This ultimately boils down to this one step:

git tag -am "euphrates.5.0" euphrates.5.0
git push origin euphrates.5.0

Once that is done, the tag is publicly visible and whatever build procedure you 
require for publishing (i.e. docker container, VM, ISO, RPM...) can be executed 
through Jenkins using that tag.

David, others, please correct if I have stated something incorrectly.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Sep 15, 2017, at 14:41, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:

David,

That might look obvious but perhaps you could confirm the exact branch name 
moving forward (or perhaps this has not changed).
From the look of existing branches, looks like it will be
“stable/euphrates”

I assume projects can/will commit stuff on that branch until some code freeze 
milestone? Could you point to the remaining limestone agenda for euphrates?

And I assume there will be at some point tags to point to subrelease (5.0, 
5.1…) on that branch?
When will these tags be created and what format will they have?
I’m trying to get a proposal out for tagging/CD and would like to avoid OPNFV 
release tags with “5.0.0” format if possible (will explain why in my proposal).

Sorry if I ask many questions,

Thanks

  Alec





From: 
<opnfv-project-leads-boun...@lists.opnfv.org<mailto:opnfv-project-leads-boun...@lists.opnfv.org>>
 on behalf of David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>
Date: Friday, September 15, 2017 at 11:26 AM
To: TECH-DISCUSS OPNFV 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>,
 opnfv-project-leads 
<opnfv-project-le...@lists.opnfv.org<mailto:opnfv-project-le...@lists.opnfv.org>>
Cc: Aric Gardner 
<agard...@linuxfoundation.org<mailto:agard...@linuxfoundation.org>>, Raymond 
Paik <rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>>, Trevor 
Bramwell <tbramw...@linuxfoundation.org<mailto:tbramw...@linuxfoundation.org>>, 
Tapio Tallgren <tapio.tallg...@nokia.com<mailto:tapio.tallg...@nokia.com>>
Subject: Re: [opnfv-projec

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] stable branch window

[Beierl, Mark]

Hello, Alec.

The process for the euphrates.1.0, 2.0 etc is documented here: 
https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Euphrates

The stable branch essentially means that no code review can be directly 
submitted against stable/euphrates.  Essentially all bug fixes and changes 
should go to master and then get independently cherry pick git Gerrit to the 
stable/euphrates branch.

Once you are happy with the state of your stable branch, the tagging 
instructions are followed.  This ultimately boils down to this one step:

git tag -am "euphrates.5.0" euphrates.5.0
git push origin euphrates.5.0

Once that is done, the tag is publicly visible and whatever build procedure you 
require for publishing (i.e. docker container, VM, ISO, RPM...) can be executed 
through Jenkins using that tag.

David, others, please correct if I have stated something incorrectly.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Sep 15, 2017, at 14:41, Alec Hothan (ahothan) 
> wrote:

David,

That might look obvious but perhaps you could confirm the exact branch name 
moving forward (or perhaps this has not changed).
From the look of existing branches, looks like it will be
“stable/euphrates”

I assume projects can/will commit stuff on that branch until some code freeze 
milestone? Could you point to the remaining limestone agenda for euphrates?

And I assume there will be at some point tags to point to subrelease (5.0, 
5.1…) on that branch?
When will these tags be created and what format will they have?
I’m trying to get a proposal out for tagging/CD and would like to avoid OPNFV 
release tags with “5.0.0” format if possible (will explain why in my proposal).

Sorry if I ask many questions,

Thanks

  Alec





From: 
>
 on behalf of David McBride 
>
Date: Friday, September 15, 2017 at 11:26 AM
To: TECH-DISCUSS OPNFV 
>,
 opnfv-project-leads 
>
Cc: Aric Gardner 
>, Raymond 
Paik >, Trevor 
Bramwell >, 
Tapio Tallgren >
Subject: Re: [opnfv-project-leads] [release][euphrates] stable branch window

Reminder...

In a few minutes, Aric will begin generating branches for projects that have 
not yet been branched.

Exceptions:
• RelEng
• Projects that did not participate in the release
• Projects that withdrew from the release
List:
1.   Apex
2.   Armband
3.   Bamboo
4.   Barometer
5.   Bottlenecks
6.   Calipso
7.   Compass4nfv
8.   Daisy4NFV
9.   Doctor
10.   Domino
11.   FastDataStacks
12.   Fuel@OPNFV
13.   FUNCTEST
14.   High availability (HA)
15.   IPv6
16.   JOID
17.   KVMforNFV
18.   Moon
19.   NFVBench
20.   Octopus
21.   OpenRetriever
22.   OPNFVDOCS
23.   OVNO
24.   Orchestra
25.   OVN4NFV
26.   Parser
27.   Pharos
28.   Promise
29.   QTIP
30.   SampleVNF
31.   SDNVPN
32.   SFC
33.   StorPerf
34.   VSPerf
35.   Yardstick

On Fri, Sep 8, 2017 at 4:24 PM, David McBride 
> wrote:
Reminder...

The stable branch window closes as of MS7, one week from today, on September 15 
at 12 p.m. (PT). PTLs - please contact Aric as soon as you're ready to branch.  
Aric will branch any projects that have not already been branched on Sept 15.

Let me know if you have any questions.

David

On Tue, Aug 29, 2017 at 3:23 PM, David McBride 
> wrote:
Team,

As you know, MS6 was this past Friday, Aug 25.  In addition to the requirements 
associated with MS6, this milestone also marks the opening of the stable branch 
window, which subsequently ends with MS7 on Sept 15.

This means that PTLs may request to branch their project any time before Sept 
15.  Note that I erroneously told the release meeting this morning that PTLs 
may create their own branch.  That's not the case.  Instead, please contact 
Aric (copied) and request that he create the branch for you.

Also, as a reminder, we have changed the version number format as of the 
Euphrates release.
• 5.0.0 - Euphrates initial release version
• 5.1.0 - Euphrates SR1
• 5.2.0 - Euphrates SR2
Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 

[opnfv-tech-discuss] StorPerf ARM images available

[Beierl, Mark]

Hello,

It is with immense pleasure that I would like to announce that with a great 
community effort, StorPerf now has published its Docker images for aarch64 as 
well as x86_64.  This is done using the same docker file, and passing the 
Architecture in as a build argument.  I want to thank the following people for 
their help:

Alex Avadanii for his tireless and flexible hours collaborating on how to 
change the Releng JJBs and scripts so that we don't interfere with the existing 
docker jobs.
Fatih Degirmenci, Trevor Bramwell and Aric Gardener for being so responsive 
when a Releng merge did have an unintended side effect and helping out.
Shrenik Jain for laying the groundwork in StorPerf container breakdown and 
migration to Alpine that made this change possible.

I am sure there are others who I forgot to mention, as this was truly a cross 
project, community effort.  To the whole OPNFV community, I extend my thanks.  
This was a significant accomplishment and I am grateful to all!  My next goal 
is to get StorPerf daily running on ARM/Fuel :)

https://hub.docker.com/r/opnfv/storperf-master/tags/
https://hub.docker.com/r/opnfv/storperf-httpfrontend/tags/
https://hub.docker.com/r/opnfv/storperf-graphite/tags/
https://hub.docker.com/r/opnfv/storperf-swaggerui/tags/
https://hub.docker.com/r/opnfv/storperf-reporting/tags/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [release][euphrates] stable branch window

[Beierl, Mark]

+1.  Would not want changes to the opnfv-docker.sh script for F to impact 
building of E maintenance releases.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Sep 11, 2017, at 09:26, Alexandru Avadanii 
> wrote:

Hi,
How about tagging releng, without branching it?

Alex

-Original Message-
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-
boun...@lists.opnfv.org] On Behalf Of Cedric 
OLLIVIER
Sent: Monday, September 11, 2017 7:51 AM
To: David McBride
Cc: opnfv-project-leads; TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] [release][euphrates] stable branch window

Hello,

Could you please confirm that no stable/euphrates branch will be created for
releng again?
Else we are obliged to select a specific git commit id to build our Functest
stable containers which is not the best way.
I precise Functest depends on the opnfv python package which is hosted by
releng (https://git.opnfv.org/releng/tree/modules).

Cédric

2017-09-09 1:24 GMT+02:00 David McBride 
>:
Reminder...

The stable branch window closes as of MS7, one week from today, on
September
15 at 12 p.m. (PT). PTLs - please contact Aric as soon as you're ready
to branch.  Aric will branch any projects that have not already been
branched on Sept 15.

Let me know if you have any questions.

David

On Tue, Aug 29, 2017 at 3:23 PM, David McBride
> wrote:

Team,

As you know, MS6 was this past Friday, Aug 25.  In addition to the
requirements associated with MS6, this milestone also marks the
opening of the stable branch window, which subsequently ends with MS7 on
Sept 15.

This means that PTLs may request to branch their project any time
before Sept 15.  Note that I erroneously told the release meeting
this morning that PTLs may create their own branch.  That's not the
case.  Instead, please contact Aric (copied) and request that he create the
branch for you.

Also, as a reminder, we have changed the version number format as of
the Euphrates release.

5.0.0 - Euphrates initial release version
5.1.0 - Euphrates SR1
5.2.0 - Euphrates SR2

Let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride




--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride

___
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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Docs] Manually test .rst?

[Beierl, Mark]

Yes, thanks Wenjing. That was the guide I was looking for.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Sep 7, 2017, at 17:41, Wenjing Chu 
<wenjing@huawei.com<mailto:wenjing@huawei.com>> wrote:

Does this help?
http://docs.opnfv.org/en/stable-danube/how-to-use-docs/include-documentation.html#in-your-project-repository

Wenjing

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Thursday, September 07, 2017 1:57 PM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Sofia Wallin <sofia.wal...@ericsson.com<mailto:sofia.wal...@ericsson.com>>
Subject: [opnfv-tech-discuss] [Docs] Manually test .rst?

Hello, Docs team (and possibly Sofia in particular?)

Is there still a method to generate the html from .rst files for a project from 
a local git clone?  I seem to remember there was, but I am not able to find the 
documentation on how to do that anymore.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

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

[opnfv-tech-discuss] [Docs] Manually test .rst?

[Beierl, Mark]

Hello, Docs team (and possibly Sofia in particular?)

Is there still a method to generate the html from .rst files for a project from 
a local git clone?  I seem to remember there was, but I am not able to find the 
documentation on how to do that anymore.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] DevStack help

[Beierl, Mark]

Hello,

Reaching out to the broader community here (although perhaps it would be better 
for me to ask about virtual OPNFV installer deployment).

I have set up DevStack on one of the bare metal servers in Intel Pod 24 so that 
we can have a second OpenStack instance to test with.  I have hit a problem 
with Heat that I would like to get advice on.  The glance.image constraint does 
not seem to be registered, therefore I cannot create any stacks.  The error 
message is:

ERROR: Property error: : resources.server.properties.image: : 
"cirros-0.3.5-x86_64-disk" does not validate glance.image (constraint not found)

I checked the heat/setup.cfg and I see

glance.image = heat.engine.clients.os.glance:ImageConstraint

is present, but it does not seem to be registering.  Does anyone have any 
advice?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] Update the list, please feedback if there is any addition //RE: Bulk access to the long duration POD - Intel18

[Beierl, Mark]

Hello, Gabriel.

I would like to add Taseer Ahmed 
(tasee...@gmail.com) and Taimoor Alam 
(taimoor.a...@tum.de) to the list as they are both 
StorPerf members that may be assisting with the long running tests.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Sep 7, 2017, at 05:22, Yuyang (Gabriel) 
> wrote:

Hi,

As a reminder and clarification, I will create the JIRA ticket on next Monday.
So please feedback if there is any addition before that.

Thanks,
Gabriel

From: Yuyang (Gabriel)
Sent: Wednesday, September 06, 2017 3:44 PM
To: 'MORTON, ALFRED C (AL)'; 
morgan.richo...@orange.com; Jose Lausuch; 
Brattain, Ross B; Cooper, Trevor; 
mark.bei...@emc.com
Cc: infra...@lists.opnfv.org; 
test...@lists.opnfv.org; opnfv-tech-discuss
Subject: Update the list, please feedback if there is any addition //RE: Bulk 
access to the long duration POD - Intel18



From: MORTON, ALFRED C (AL) [mailto:acmor...@att.com]
Sent: Friday, September 01, 2017 8:38 PM
To: Yuyang (Gabriel); 
morgan.richo...@orange.com; Jose Lausuch; 
Brattain, Ross B; Cooper, Trevor; 
mark.bei...@emc.com
Cc: infra...@lists.opnfv.org; 
test...@lists.opnfv.org; opnfv-tech-discuss
Subject: RE: Bulk access to the long duration POD - Intel18

Hi Gabriel,

please add me under the VSPERF list:

Al: acmor...@att.com


From: test-wg-boun...@lists.opnfv.org 
[mailto:test-wg-boun...@lists.opnfv.org] On Behalf Of Yuyang (Gabriel)
Sent: Thursday, August 31, 2017 11:55 PM
To: morgan.richo...@orange.com; Jose 
Lausuch; Brattain, Ross B; Cooper, Trevor; 
mark.bei...@emc.com
Cc: infra...@lists.opnfv.org; 
test...@lists.opnfv.org; opnfv-tech-discuss
Subject: [test-wg] Bulk access to the long duration POD - Intel18

Hi,

As we discussed in the Testperf meeting and the alignment with Infra group, we 
will need access to the Intel-18 POD for the long duration test.
To avoid duplicated requests, we decide to create a ticket to collect name list 
for bulk access subscription.
A action item has been assigned to me to collect the name list though email. 
Please provide your feedback below so that I could create the ticket.

Bottlenecks:
Gabriel Yu: gabriel.yuy...@huawei.com
Ace Lee: liyi...@huawei.com

VSPERF:
Trevor: trevor.coo...@intel.com
Al: acmor...@att.com

STORPERF:
Mark: mark.bei...@emc.com

Yardstick:
Ross: ross.b.bratt...@intel.com


Functest:
Morgan: morgan.richo...@orange.com
Jose Lausuch: jose.laus...@ericsson.com



Best,
Gabriel

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting Notes

[Beierl, Mark]

Hello,

Thanks to all who attended today's call.  We had a good discussion on the wrap 
up of tasks for Euphrates, and I have started the kickoff for F release 
planning [1].  Minutes from todays' meeting can be found here [2].

[1] https://wiki.opnfv.org/display/storperf/F+Release+Planning
[2] https://wiki.opnfv.org/display/meetings/StorPerf+2017-09-07+Meeting+Notes

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Thursday from 10:00 AM to 11:
 00 AM effective 9/7/2017 until 11/2/2017. (UTC-05:00) Eastern Time (US & C
 anada)\nWhere: https://global.gotomeeting.com/join/819733085\n\n*~*~*~*~*~
 *~*~*~*~*\n\nHello\,\n\nPlease feel free to join us for the StorPerf team 
 meeting.  This schedule runs until the Daylight Savings time change in Nor
 th America.\n\nhttps://global.gotomeeting.com/join/819733085\n\nhttps://wi
 ki.opnfv.org/display/meetings/Storperf+Team+Weekly+Meeting\n
RRULE:FREQ=WEEKLY;UNTIL=20171102T14Z;INTERVAL=1;BYDAY=TH;WKST=SU
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170907T10
DTEND;TZID=Eastern Standard Time:20170907T11
UID:F813D04F-8EEC-49A9-BAA6-FA12447ABCA3
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170906T154646Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2115579989
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, September 7\, 2017 10:00 AM-11:
 00 AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotom
 eeting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nPlease feel
  free to join us for the StorPerf team meeting.  This schedule runs until 
 the Daylight Savings time change in North America.\n\nhttps://global.gotom
 eeting.com/join/819733085\n\nhttps://wiki.opnfv.org/display/meetings/Storp
 erf+Team+Weekly+Meeting\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170907T10
DTEND;TZID=Eastern Standard Time:20170907T11
UID:F813D04F-8EEC-49A9-BAA6-FA12447ABCA3
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170906T154610Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115579989
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] StorPerf multi-arch verify includes ARM

[Beierl, Mark]

Hello,

I would like to extend a big thank you to Alex Avadanii and Fatih Degirmenci 
(and probably others too!) for their help in reaching this important milestone 
in StorPerf.  New patches now go through 3 verification jobs prior to Jenkins 
giving a +1:

1) Unit tests, python formatting and code coverage are run
2) Docker containers are built locally, started and checked for basic health on 
x86_64
3) Docker containers are built locally, started and checked for basic health on 
ARM aarch64!

Is it this last step that I am most excited about.  It validates that the 
docker containers build and can start successfully on ARM, and this will be 
done automatically for each Gerrit patchset going forward.  Note: this does not 
yet mean that docker images for StorPerf are built and published to Dockerhub 
for ARM.  That is for another day...

[1] https://build.opnfv.org/ci/job/storperf-verify-master/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Thursday\, August 31\, 2017 10:00 AM-11:00
  AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://global.gotomee
 ting.com/join/819733085\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nPlease join u
 s for the weekly StorPerf team meeting at its new time of 14:00 UTC Thursd
 ay.\n\nhttps://global.gotomeeting.com/join/819733085\n#opnfv-meeting\n\nht
 tps://wiki.opnfv.org/display/meetings/Storperf\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170831T10
DTEND;TZID=Eastern Standard Time:20170831T11
UID:4C5AEB77-D003-492B-BD78-809B84E592B6
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170830T213427Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115563791
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] I am taking GTM2 slot Thursdays at 1400 UTC.

[Beierl, Mark]

Hello,

At this time, I do not see anyone signed up to use the GTM account for 1400 UTC 
on Thursday, so I would like to use that for StorPerf.

That would be the GTM 2 account: https://global.gotomeeting.com/join/819733085

I would also like to ask all the PTLs to take a moment to ensure the calendar 
on the meeting wiki is up to date:

https://wiki.opnfv.org/display/meetings

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] GPG Keyserver Failure

[Beierl, Mark]

Hello,

Hoping someone has figured this one out already.  I am trying to set up SSL for 
http server during a build, but frequently the following command will fail:

hkp://p80.pool.sks-keyservers.net:80 --recv-keys "$GPG_KEYS"' returned a 
non-zero code: 2

Anyone else seen this, or should I abandon HTTPS for now?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] Willingness to contribute to OPNFV

[Beierl, Mark]

Hello, Taimoor.

I have added you as a contributor to StorPerf on the wiki [1].  Once you have 
your LFID, and have signed into the wiki, please let me know and I can @mention 
you by name.

As mentioned, we are currently in the final stages of the Euphrates release, so 
there is not a lot of new work at the moment, but I will be looking at the F 
release planning soon and hope to have a better idea of where we can have you 
starting.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Aug 22, 2017, at 17:49, Raymond Paik 
> wrote:

Hi Taimoor,

Welcome to OPNFV.  Let me send you an individual contributor agreement in a 
separate email so that you can start contributing

Thanks,

Ray

On Tue, Aug 22, 2017 at 10:58 AM, Alam, Taimoor 
> wrote:
Hello

I am a masters student in Germany, and I want to proceed to contribute to OPNFV 
projects particulary in Storperf. I have also talked to the PTL. My linux 
foundation account is taimoor.alam. Please let me know about the further steps.

Taimoor Alam
MSc. Informatik
Technische Universität München




___
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

Re: [opnfv-tech-discuss] Delays due to Intel outage

[Beierl, Mark]

It looks to be resolved now, although the ticket remains open.  Thanks to the 
team that restored the connectivity!

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 22, 2017, at 16:29, Manuel Buil <mb...@suse.com<mailto:mb...@suse.com>> 
wrote:

Hello David, Mark,

Thanks for bringing this up Mark. SFC is also impacted by this outage :(

Regards,
Manuel

On Tue, 2017-08-22 at 19:59 +, Beierl, Mark wrote:
Hello, David.

I am sending this as a heads up.  There has been an outage in Intel [1] since 
yesterday and it is causing a minor impact to StorPerf as we have been without 
our primary development and CI pod since it started.  Right now, I don't 
anticipate any problems with the next milestone for StorPerf.

If this lasts much longer, there may be other projects that are impacted too.

[1] https://jira.opnfv.org/projects/INFRA/issues/INFRA-161

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>


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


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

[opnfv-tech-discuss] [StorPerf] No meeting today

[Beierl, Mark]

Hello,

Sorry, I have a conflict and cannot host the meeting today.  If there are any 
questions or ideas, please feel free to ping me in #opnfv-storperf.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] Delays due to Intel outage

[Beierl, Mark]

Hello, David.

I am sending this as a heads up.  There has been an outage in Intel [1] since 
yesterday and it is causing a minor impact to StorPerf as we have been without 
our primary development and CI pod since it started.  Right now, I don't 
anticipate any problems with the next milestone for StorPerf.

If this lasts much longer, there may be other projects that are impacted too.

[1] https://jira.opnfv.org/projects/INFRA/issues/INFRA-161

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [Stor4NFV] Contributor Request

[Beierl, Mark]

Hello,

I'd like to become a contributor to Stor4NFV, thanks!

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Graphite Alpine

[Beierl, Mark]

Hello, Shrenik.

I see there is already an alpine based Graphite that is being developed here 
[1].  Do you think it is worth using instead of the hopsoft one?

[1] https://hub.docker.com/r/diceone/alpine-graphite/~/dockerfile/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

[Beierl, Mark]

Hello, Gabriel.

The idea behind starting one first is so we can see the delta at the point 
where it started.  We certainly can run both independently as a baseline, and 
then run them together can measure the delta that way...

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 17, 2017, at 04:20, Yuyang (Gabriel) 
<gabriel.yuy...@huawei.com<mailto:gabriel.yuy...@huawei.com>> wrote:

Hi Mark,

I fully support the idea here. I think it is time testing projects together 
develop some sophisticated stress test cases across components of the system.
Just 1 question, why start VSPERF and STORPERF separately. Why not start both 
tests simultaneously and monitoring/reporting the throughput variation along 
time.

Thanks,
Gabriel


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Thursday, August 17, 2017 12:17 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

Hello, Trevor and VSPERF team.

I'd like to get a quick overview of VSPERF and how the metrics are captured.  
Sorry if these are dumb questions :)

First, is there a test that simply pushes packets over the network to see what 
the maximum throughput is, like a saturation test?

Does VSPERF capture periodic metrics, or just a summary report at the end?  If 
I change something in the network while the test is running (such as adding 
more traffic outside of VSPERF), is there a way to see the impact of that while 
the test is running?

The reason behind the questions are for the following scenario:

1) I start up VSPERF on the NICs that represent the tenant network in an 
OpenStack installation.
2) After 10 minutes, start up StorPerf read/write test that should stress the 
OpenStack storage network
3) See if there is a change to the VSPERF throughput.

Alternatively, as StorPerf does have minute by minute metrics, we can do this:

1) Start StorPerf read/write
2) After 10 minutes, start VSPERF to stress the tenant network NICs
3) Look at the change in StorPerf throughput at the time that VSPERF starts.

Thoughts?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

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

Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

[Beierl, Mark]

Alec,

It is completely up to you how you want to structure your project and your 
deliverables.  If you don't want the extra hassle of supporting ARM, then don't.

As for my project and the other ones that happen to support ARM, we will 
continue this discussion to see what makes sense.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 16, 2017, at 21:02, HU, BIN <bh5...@att.com<mailto:bh5...@att.com>> 
wrote:

Alec,

Thank you for your input, and letting know you won’t be able to make the 
meeting tomorrow.

Mark,

Do you still want to discuss in the meeting tomorrow? (my only concern is the 
attendance, which  may not warrant an effective live discussion.

Or do you think the discussion on mailing list should be good enough?

If we all think the discussion on mailing list is good enough, we don’t need to 
discuss it in the meeting tomorrow.

Thanks
Bin

From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Wednesday, August 16, 2017 5:47 PM
To: HU, BIN <bh5...@att.com<mailto:bh5...@att.com>>; Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion


Mark,

Thanks for updating me on the ARM situation. My only comment is that it could 
have been easier to perhaps have an x86 server/jump host servicing an ARM pod 
given that testing tools do not exactly have to run on the same arch than the 
pod under test, but I guess decision has been made - now we need every test 
tool to also support ARM (that in addition to more work to support 2 arch, more 
test to do…).

On my side, I’ll need to check with the TRex team if they support ARM. If it 
does not work, every data plane test tool that uses TRex will be impacted (at 
least vsperf + nfvbench).
It really seems to me that we could have saved all the extra hassle of ARM 
support with an x86 jump host (VMs is another story but we could have limited 
the overhead to VM artifacts only).

Bin: unfortunately, I won’t be able to make it at the technical discussion 
meeting as it will be in the middle of my Thursday commute.

Thanks

  Alec



From: "HU, BIN" <bh5...@att.com<mailto:bh5...@att.com>>
Date: Tuesday, August 15, 2017 at 5:00 PM
To: "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>, "Alec 
Hothan (ahothan)" <ahot...@cisco.com<mailto:ahot...@cisco.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

Good discussion and suggestion, thank you Alec and Mark.

We can discuss this on Thursday. I put it on the agenda “Container Versioning / 
Naming Schema for x86 and ARM”.

Talk to you all on Thursday
Bin

From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Tuesday, August 15, 2017 10:23 AM
To: Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>>
Cc: HU, BIN <bh5...@att.com<mailto:bh5...@att.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

Hello, Alec.

Fair questions, but in the ARM pods there are not necessarily x86 servers to 
act as the host for the container.  It is also my desire to support ARM for the 
various pods we have, and not make it difficult for them to run.  We already 
support ARM containers for functest, yardstick, qtip and dovetail, just with a 
different naming scheme than other projects in docker hub.

If you look at the way multiarch alpine structures their tags, yes, it is 
arch-version, so x86-euphrates.1.0 would be the correct way of labelling it.  I 
realize we are getting close to Euphrates release date, so this might be 
postponed to F, but I would like to have a community discussion about this to 
see if it makes sense, or if we want to continue with creating repos to match 
the architecture.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 15, 2017, at 12:03, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:


We need to look at the impact on versioning since the docker container tag 
reflects the release (e.g. euphrates-5.0.0), since this proposal prepends an 
arch field (x86-euphrates-5.0.0 ?).
How many OPNFV containers will have to support more arch than just x86?
I was under the impression that most test containers could manage to run on x86 
only (since we can pick the server 

[opnfv-tech-discuss] [VSPERF] [Bottlenecks] VSPERF and StorPerf

[Beierl, Mark]

Hello, Trevor and VSPERF team.

I'd like to get a quick overview of VSPERF and how the metrics are captured.  
Sorry if these are dumb questions :)

First, is there a test that simply pushes packets over the network to see what 
the maximum throughput is, like a saturation test?

Does VSPERF capture periodic metrics, or just a summary report at the end?  If 
I change something in the network while the test is running (such as adding 
more traffic outside of VSPERF), is there a way to see the impact of that while 
the test is running?

The reason behind the questions are for the following scenario:

1) I start up VSPERF on the NICs that represent the tenant network in an 
OpenStack installation.
2) After 10 minutes, start up StorPerf read/write test that should stress the 
OpenStack storage network
3) See if there is a change to the VSPERF throughput.

Alternatively, as StorPerf does have minute by minute metrics, we can do this:

1) Start StorPerf read/write
2) After 10 minutes, start VSPERF to stress the tenant network NICs
3) Look at the change in StorPerf throughput at the time that VSPERF starts.

Thoughts?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] 2017-08-16 Meeting Notes

[Beierl, Mark]

Hello, everyone.

Thanks to those who attended today's meeting.  Minutes can be found here [1].

We had a good discussion about approaches for Bottlenecks to run VSPERF and 
StorPerf at the same time.  This resulted in a great idea from Ace about 
enhancing StorPerf to support multiple stacks with multiple jobs running at the 
same time.

Graphite container decomposition is proceeding well, and it was confirmed that 
we will clone the Dockerfile so we can base it on multiarch/alpine to be able 
to support ARM and x86 in the same docker file, as we have started doing for 
Swagger and nginx.

[1] https://wiki.opnfv.org/display/meetings/StorPerf+2017-08-16+Meeting+Notes

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 16\, 2017 10:00 AM-11:0
 0 AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://meet.emc.com/
 mark.beierl/69MEZFLU\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nPlease join us f
 or the weekly StorPerf team meeting starting in 1.5 hours.\n\nhttps://meet
 .emc.com/mark.beierl/69MEZFLU\n\nFind a local number:\nhttp://www.emcconfe
 rencing.com/globalaccess/\n\nConference ID: 58108948\n\nhttps://wiki.opnfv
 .org/display/meetings/Storperf\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170816T10
DTEND;TZID=Eastern Standard Time:20170816T11
UID:955400D7-B224-4AA9-A75F-E22E44B1909E
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170816T123722Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://meet.emc.com/mark.beierl/69MEZFLU 
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115536732
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

[Beierl, Mark]

Hello, Alec.

Fair questions, but in the ARM pods there are not necessarily x86 servers to 
act as the host for the container.  It is also my desire to support ARM for the 
various pods we have, and not make it difficult for them to run.  We already 
support ARM containers for functest, yardstick, qtip and dovetail, just with a 
different naming scheme than other projects in docker hub.

If you look at the way multiarch alpine structures their tags, yes, it is 
arch-version, so x86-euphrates.1.0 would be the correct way of labelling it.  I 
realize we are getting close to Euphrates release date, so this might be 
postponed to F, but I would like to have a community discussion about this to 
see if it makes sense, or if we want to continue with creating repos to match 
the architecture.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 15, 2017, at 12:03, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:


We need to look at the impact on versioning since the docker container tag 
reflects the release (e.g. euphrates-5.0.0), since this proposal prepends an 
arch field (x86-euphrates-5.0.0 ?).
How many OPNFV containers will have to support more arch than just x86?
I was under the impression that most test containers could manage to run on x86 
only (since we can pick the server where these test containers will run), but I 
am missing the arm context and why (some) test containers need to support ARM… 
Is that a mandate for all OPNFV test containers?

Thanks

  Alec




From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Date: Tuesday, August 15, 2017 at 8:18 AM
To: "HU, BIN" <bh5...@att.com<mailto:bh5...@att.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] Topics for Weekly Technical Discussion

Hello,

Is this the right place to discuss changing the docker image names from 
containing the architecture to having the tag contain it instead?  For example 
(from a previous email):

Alpine tags as follows:

multiarch/alpine:x86-latest-stable
multiarch/alpine:aarch64-latest-stable

Vs. in OPNFV we use the image name to specify the architecture [2], [3]:

opnfv/functest:latest
opnfv/functest_aarch64:latest

I think the way multiarch/alpine does it is preferable so that there is only 
one repository name, but I think we need to discuss this across the different 
projects and releng to make these changes.

[1] https://hub.docker.com/r/multiarch/alpine/tags/
[2] https://hub.docker.com/r/opnfv/functest/
[3] https://hub.docker.com/r/opnfv/functest_aarch64/tags/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 15, 2017, at 10:52, HU, BIN <bh5...@att.com<mailto:bh5...@att.com>> 
wrote:

Hello community,

Just a friendly reminder that if you want to discuss any item/topic/issue at 
our weekly technical discussion this Thursday 08/17, please feel free to let me 
know.

Thanks
Bin


___
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

[opnfv-tech-discuss] Topics for Weekly Technical Discussion

[Beierl, Mark]

Hello,

Is this the right place to discuss changing the docker image names from 
containing the architecture to having the tag contain it instead?  For example 
(from a previous email):

Alpine tags as follows:

multiarch/alpine:x86-latest-stable
multiarch/alpine:aarch64-latest-stable

Vs. in OPNFV we use the image name to specify the architecture [2], [3]:

opnfv/functest:latest
opnfv/functest_aarch64:latest

I think the way multiarch/alpine does it is preferable so that there is only 
one repository name, but I think we need to discuss this across the different 
projects and releng to make these changes.

[1] https://hub.docker.com/r/multiarch/alpine/tags/
[2] https://hub.docker.com/r/opnfv/functest/
[3] https://hub.docker.com/r/opnfv/functest_aarch64/tags/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Aug 15, 2017, at 10:52, HU, BIN > 
wrote:

Hello community,

Just a friendly reminder that if you want to discuss any item/topic/issue at 
our weekly technical discussion this Thursday 08/17, please feel free to let me 
know.

Thanks
Bin


___
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] [StorPerf] Committer nomination

[Beierl, Mark]

Hello,

I would like to nominate Taseer Ahmed to StorPerf committer.  As Jose is 
currently on leave until September, I will be leaving the nomination open until 
then.

Please vote, or +2 here:

https://gerrit.opnfv.org/gerrit/38979

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 9\, 2017 10:00 AM-11:00
  AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://hangouts.googl
 e.com/call/6bimzgl5mng7dg7zhn3obxagueu\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n
 \nPlease note today we will be using Google Hangouts instead of Skype.\n\n
 Google Hangouts Link:\n\nhttps://hangouts.google.com/call/6bimzgl5mng7dg7z
 hn3obxagueu\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170809T10
DTEND;TZID=Eastern Standard Time:20170809T11
UID:E896C8E5-DF22-4F51-9584-0D667EA4F8C0
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170809T135135Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://hangouts.google.com/call/6bimzgl5mng7dg7zhn
 3obxagueu
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115520986
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] Docker verify jobs

[Beierl, Mark]

Hello, Aric.

In relation to your review [1] for docker verify jobs, I would like to request 
that the build architecture is also added to the Jenkins environment variables. 
 Eventually, I would like to spin up a local docker container and do a quick 
sanity on the docker build and run steps on both x86 and arm64 platforms.  How 
can we have make changes to have verify jobs run on two servers?  Would I need 
two verify jobs?

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

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Thanks!  That is exactly what we're looking at, and with the newer docker ce we 
should be able to put the arch into a variable in the FROM line and have only 1 
dockerfile.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 3, 2017, at 17:00, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:

Hi,
It looks like 17.06 CE is not officially out for ARMV8 yet, but there is a test 
binary at [1]. To use it with apt:
„deb [arch=arm64] https://download.docker.com/linux/ubuntu/ xenial test”
$ sudo apt-get install docker-ce

You can always try building from sources, but you might run into unexpected 
issues.
Btw, for Alpine/Ubuntu AArch64 docker base images, check out [2].

Alex

[1] https://download.docker.com/linux/ubuntu/dists/xenial/pool/test/arm64/
[2] https://hub.docker.com/u/arm64v8/ (used to be 
https://hub.docker.com/u/aarch64)


From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, August 03, 2017 11:43 PM
To: Alexandru Avadanii; Taseer Ahmed
Cc: Bob Monkman; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Alexandru Nemes
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Hello,

I think the docker version is too old for the build and docker-compose that I 
am using in StorPerf.  We currently require docker ce 17.06 to do multi-stage 
builds.

I have looped in Taseer (cc) as he is the one who has access to the Cavium ARM 
server.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 3, 2017, at 16:28, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:

Hi, Mark,
armhf won’t work, that is ARMv7, while we target ARMv8 (aarch64). The 
appropiate arch qualifier would be (for a Debian system like Ubuntu):
[arch=arm64]
But unless you are trying to do something extremely specific, that should not 
be needed, stock Ubuntu 16.04 already has a working docker for AArch64.

Btw, we are already building a few AArch64 Docker images, for functest [1], 
dovetail [2], soon yardstick etc.
The releng bit handling AArch64 can be found at [3] and works like this:
-  If DOCKERFILE parameter is passed to build job (in format 
„Dockerfile.aarch64” usually) and the file exists in the git repo, it will be 
used instead of default „Dockerfile”;
-  If DOCKERFILE parameter is passed (same „Dockerfile.aarch64”), but 
it doesn’t exist, releng will look for „Dockerfile.aarch64.patch”, apply that 
on top of „Dockerfile”, then use it;

The builder machine handling [2] and [3] is arm-build3 [4], an AArch64 VM on a 
ThunderX node.
It runs Ubuntu Xenial (16.04.2), and docker was installed from Ubuntu repos 
using apt (no custom repository was necessary afaik).

CC’in Alex Nemes from our side, as he recently worked on this and might have 
things fresh in his memory for further queries.

BR,
Alex

[1] 
https://build.opnfv.org/ci/view/functest/job/functest-docker-build-arm-push-master/
[2] https://build.opnfv.org/ci/job/dovetail-docker-build-arm-push-master/
[3] 
https://github.com/opnfv/releng/blob/master/jjb/releng/opnfv-docker.sh#L58-L71
[4] https://build.opnfv.org/ci/computer/arm-build3/builds


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bob Monkman
Sent: Thursday, August 03, 2017 11:11 PM
To: Beierl, Mark
Cc: Måns Söderberg; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Mark,
  I am sorry that am not close to the technical mechanisms by which 
this works. I have directly copied a couple of Armbanders to see if they can 
provide a quick answer. The caveat is that a number of developers may be on 
holiday and the remaining team is pressed trying to create bare metal deploys 
for MCP with the new MS5 just 8 days away. Sorry, bad timing but let’s see if 
something can be provided for a pointer.

Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, August 3, 2017 1:03 PM
To: Beierl, Mark <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Cc: Bob Monkman <bob.monk...@arm.com<mailto:bob.monk...@arm.com>>; Måns 
Söderberg <mans.soderb...@enea.com<mailto:mans.soderb...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for developme

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Hello,

I think the docker version is too old for the build and docker-compose that I 
am using in StorPerf.  We currently require docker ce 17.06 to do multi-stage 
builds.

I have looped in Taseer (cc) as he is the one who has access to the Cavium ARM 
server.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Aug 3, 2017, at 16:28, Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>> wrote:

Hi, Mark,
armhf won’t work, that is ARMv7, while we target ARMv8 (aarch64). The 
appropiate arch qualifier would be (for a Debian system like Ubuntu):
[arch=arm64]
But unless you are trying to do something extremely specific, that should not 
be needed, stock Ubuntu 16.04 already has a working docker for AArch64.

Btw, we are already building a few AArch64 Docker images, for functest [1], 
dovetail [2], soon yardstick etc.
The releng bit handling AArch64 can be found at [3] and works like this:
-  If DOCKERFILE parameter is passed to build job (in format 
„Dockerfile.aarch64” usually) and the file exists in the git repo, it will be 
used instead of default „Dockerfile”;
-  If DOCKERFILE parameter is passed (same „Dockerfile.aarch64”), but 
it doesn’t exist, releng will look for „Dockerfile.aarch64.patch”, apply that 
on top of „Dockerfile”, then use it;

The builder machine handling [2] and [3] is arm-build3 [4], an AArch64 VM on a 
ThunderX node.
It runs Ubuntu Xenial (16.04.2), and docker was installed from Ubuntu repos 
using apt (no custom repository was necessary afaik).

CC’in Alex Nemes from our side, as he recently worked on this and might have 
things fresh in his memory for further queries.

BR,
Alex

[1] 
https://build.opnfv.org/ci/view/functest/job/functest-docker-build-arm-push-master/
[2] https://build.opnfv.org/ci/job/dovetail-docker-build-arm-push-master/
[3] 
https://github.com/opnfv/releng/blob/master/jjb/releng/opnfv-docker.sh#L58-L71
[4] https://build.opnfv.org/ci/computer/arm-build3/builds


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bob Monkman
Sent: Thursday, August 03, 2017 11:11 PM
To: Beierl, Mark
Cc: Måns Söderberg; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Mark,
  I am sorry that am not close to the technical mechanisms by which 
this works. I have directly copied a couple of Armbanders to see if they can 
provide a quick answer. The caveat is that a number of developers may be on 
holiday and the remaining team is pressed trying to create bare metal deploys 
for MCP with the new MS5 just 8 days away. Sorry, bad timing but let’s see if 
something can be provided for a pointer.

Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, August 3, 2017 1:03 PM
To: Beierl, Mark <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Cc: Bob Monkman <bob.monk...@arm.com<mailto:bob.monk...@arm.com>>; Måns 
Söderberg <mans.soderb...@enea.com<mailto:mans.soderb...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Hello, again, Bob.

Is Armband running Ubuntu on the servers?  How did you get docker on there to 
run Functest?  We have access to a Cavium ARM based server and I want to make 
sure we are running the correct architecture.  I see instructions [1] that say 
to use [arch=armhf].  Will that work?

[1] 
https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-using-the-repository

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 28, 2017, at 09:41, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:

Thanks very much, Bob.

I should not need any cycles for help.  I'm not looking at a test run or 
developing new functionality.  All I really need to do is verify the docker 
build process and that the packages StorPerf depends on are available in the 
Alpine docker base.  So, more of a packaging exercise if that is a good way to 
describe it?

This is not an immediate activity, so no rush :)

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 21:13, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Hello, again, Bob.

Is Armband running Ubuntu on the servers?  How did you get docker on there to 
run Functest?  We have access to a Cavium ARM based server and I want to make 
sure we are running the correct architecture.  I see instructions [1] that say 
to use [arch=armhf].  Will that work?

[1] 
https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-using-the-repository

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 28, 2017, at 09:41, Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:

Thanks very much, Bob.

I should not need any cycles for help.  I'm not looking at a test run or 
developing new functionality.  All I really need to do is verify the docker 
build process and that the packages StorPerf depends on are available in the 
Alpine docker base.  So, more of a packaging exercise if that is a good way to 
describe it?

This is not an immediate activity, so no rush :)

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 21:13, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>> wrote:

Thanks, Mark,
  I think the Armband team can help here. We have no cycles to help 
too much but we apparently have a small and full pod available (latter for a 
short time only) and we would need to see if we can get some Pharos credentials 
for you.

I have copied Mans who recently provided me with a set of VPN credentials. Or 
maybe Alex has a difference suggestion.

Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, July 27, 2017 6:07 PM
To: Bob Monkman <bob.monk...@arm.com<mailto:bob.monk...@arm.com>>
Cc: David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>; Alexandru 
Avadanii <alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>>; 
Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Hello,

My hope was to test the docker build for Euphrates.  I don't need a dedicated 
pod, in fact, just being able to spin up the image and point it to an OPNFV 
installation for a quick Cinder quota query would be good enough.  Is there 
anything I can piggy back onto?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 19:31, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>> wrote:

Thanks Dave, I did see this and, thanks to Mark for bringing this to our 
attention. We have had our head down on MS5 for Euphrates and the labs in 
Sweden are a bit light on manpower given July holiday for most folks.

Mark,
  Are you seeking to get this in for Euphrates? I will check into 
but most pods are allocated to E-release development and CI, plus other clients 
working projects.

  Some of our other ecosystem partners may be able to help.
Regards,
bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, July 27, 2017 3:31 PM
To: Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>>; Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>; Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>>; Cristina Pauna 
<cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

+Bob, Alex, Cristina

On Wed, Jul 26, 2017 at 8:25 AM Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, team!

As StorPerf is published as a Docker container, and after looking at Functest, 
I realized that StorPerf not run natively on ARM.  I need to create ARM based 
images, and therefore would like to ask if there is any pod or resources that 
have an existing OPNFV installation on them where I can run StorPerf for 
validation testing?

Please let me know if this is something your team can provide.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
m

[opnfv-tech-discuss] [StorPerf] Re: [Docker Multi Arch]

[Beierl, Mark]

Hello,

Added the mailing list.

It looks promising.  The emulators look like they are for testing only.  If you 
have access to ARM hardware, can you give it a try with a simple:


docker run -it --rm multiarch/alpine:armhf-edge /bin/sh

And see if that results in a docker container that gives you /bin/sh access?  
If so, then see if FROM can take "armhf-edge" as a variable to the docker build 
and we can use that as the base for all our images?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Aug 2, 2017, at 13:09, Taseer Ahmed 
> wrote:

Hi,

Thanks for the suggestion to subscribe for the technical discussion. I have it 
done.

Secondly, I have been looking around a solution for StorPerf docker image on 
ARM architectures. And I came across some interesting things. I found some 
multiarch support for Docker images, including Alpine. However, I am just 
confused if these are just ARM emulations on an x86_64 architecture.

Could you also please take a look [1], and leave your comments on it, so we may 
be able to learn about it together ?

Thanks

[1] https://hub.docker.com/r/multiarch/alpine/

Regards,
Taseer

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

[opnfv-tech-discuss] [StorPerf] Weekly Meeting

[Beierl, Mark]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Beierl, Mark":MAILTO:mark.bei...@emc.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Taseer Ahm
 ed:MAILTO:tasee...@gmail.com
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=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=saksham115
 @gmail.com:MAILTO:saksham...@gmail.com
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, August 2\, 2017 10:00 AM-11:00
  AM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://meet.emc.com/m
 ark.beierl/69MEZFLU\n\n*~*~*~*~*~*~*~*~*~*\n\nHello\,\n\nPlease feel free 
 to joing us for the next StorPerf weekly meeting.  Agenda and logistics ar
 e:\n\nhttps://wiki.opnfv.org/display/meetings/StorPerf+2017-08-02+Meeting+
 Notes\n\nSkype Online Meeting:\nhttps://meet.emc.com/mark.beierl/69MEZFLU\
 n\n\nFind a local number:\nhttp://www.emcconferencing.com/globalaccess/\n\
 nConference ID: 58108948\n
SUMMARY;LANGUAGE=en-US:[StorPerf] Weekly Meeting
DTSTART;TZID=Eastern Standard Time:20170802T10
DTEND;TZID=Eastern Standard Time:20170802T11
UID:AF6EB3DD-34AF-4006-B1EE-DCA937BE44AF
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170801T140221Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://meet.emc.com/mark.beierl/69MEZFLU 
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115504562
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT5M
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] Kernel version and Docker build failures (aka Shrenik, you were right)

[Beierl, Mark]

Hello,

Well I have had a little journey down the road of obscure bugs this past week.  
I messed up the docker installation on Intel pod 24, and so had to re-install 
it.  From that point forward, I got this really annoying error when attempting 
to upgrade python's setuptools:

OSError: [Errno 22] Invalid argument: 
'/usr/lib/python2.7/site-packages/pkg_resources/_vendor/packaging'

If I started a new container, entered it and executed the pip install of newer 
version of setuptools, it worked just fine.  Of course, this container build 
step worked on my laptop, on Ericsson slave 3, etc, etc.

I turned to our good friends in the Apex team for help.  When I was chatting 
with Tim Rozet he mentioned that they switched to overlay instead of loop 
devices due to having problems with loop devices.  Great!  I'll try that.

Did a little reading of some sites from Tim, plus this particularly helpful one 
[1].  Turns out that when I reinstalled docker, it was a newer version that 
already uses overlays.  So I didn't have to change anything.  But still it 
wasn't working.  Then I re-read [1].  To quote:

"While testing overlay on kernel 3.10, I got errors while running docker build. 
Specifically I got errors when doing an rm on files of an underlying layer."

Oh.  Upgrade of setuptools is removing the previous version.  From an 
underlying layer!  Quick: uname -a.  Yes!  I was on 3.10.

Upgrade to 4.10 as per the instructions in [1] and it's all working again.  
Hopefully this long rant might save someone else headache in the future.

[1] https://adminswerk.de/overlayfs-docker-storage-driver-centos-7/

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Thanks very much, Bob.

I should not need any cycles for help.  I'm not looking at a test run or 
developing new functionality.  All I really need to do is verify the docker 
build process and that the packages StorPerf depends on are available in the 
Alpine docker base.  So, more of a packaging exercise if that is a good way to 
describe it?

This is not an immediate activity, so no rush :)

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 21:13, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>> wrote:

Thanks, Mark,
  I think the Armband team can help here. We have no cycles to help 
too much but we apparently have a small and full pod available (latter for a 
short time only) and we would need to see if we can get some Pharos credentials 
for you.

I have copied Mans who recently provided me with a set of VPN credentials. Or 
maybe Alex has a difference suggestion.

Bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, July 27, 2017 6:07 PM
To: Bob Monkman <bob.monk...@arm.com<mailto:bob.monk...@arm.com>>
Cc: David McBride 
<dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>; Alexandru 
Avadanii <alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>>; 
Cristina Pauna <cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

Hello,

My hope was to test the docker build for Euphrates.  I don't need a dedicated 
pod, in fact, just being able to spin up the image and point it to an OPNFV 
installation for a quick Cinder quota query would be good enough.  Is there 
anything I can piggy back onto?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 19:31, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>> wrote:

Thanks Dave, I did see this and, thanks to Mark for bringing this to our 
attention. We have had our head down on MS5 for Euphrates and the labs in 
Sweden are a bit light on manpower given July holiday for most folks.

Mark,
  Are you seeking to get this in for Euphrates? I will check into 
but most pods are allocated to E-release development and CI, plus other clients 
working projects.

  Some of our other ecosystem partners may be able to help.
Regards,
bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, July 27, 2017 3:31 PM
To: Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>>; Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>; Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>>; Cristina Pauna 
<cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

+Bob, Alex, Cristina

On Wed, Jul 26, 2017 at 8:25 AM Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, team!

As StorPerf is published as a Docker container, and after looking at Functest, 
I realized that StorPerf not run natively on ARM.  I need to create ARM based 
images, and therefore would like to ask if there is any pod or resources that 
have an existing OPNFV installation on them where I can run StorPerf for 
validation testing?

Please let me know if this is something your team can provide.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose th

Re: [opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Hello,

My hope was to test the docker build for Euphrates.  I don't need a dedicated 
pod, in fact, just being able to spin up the image and point it to an OPNFV 
installation for a quick Cinder quota query would be good enough.  Is there 
anything I can piggy back onto?

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 27, 2017, at 19:31, Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>> wrote:

Thanks Dave, I did see this and, thanks to Mark for bringing this to our 
attention. We have had our head down on MS5 for Euphrates and the labs in 
Sweden are a bit light on manpower given July holiday for most folks.

Mark,
  Are you seeking to get this in for Euphrates? I will check into 
but most pods are allocated to E-release development and CI, plus other clients 
working projects.

  Some of our other ecosystem partners may be able to help.
Regards,
bob

Robert (Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, July 27, 2017 3:31 PM
To: Alexandru Avadanii 
<alexandru.avada...@enea.com<mailto:alexandru.avada...@enea.com>>; Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>>; Bob Monkman 
<bob.monk...@arm.com<mailto:bob.monk...@arm.com>>; Cristina Pauna 
<cristina.pa...@enea.com<mailto:cristina.pa...@enea.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing

+Bob, Alex, Cristina

On Wed, Jul 26, 2017 at 8:25 AM Beierl, Mark 
<mark.bei...@dell.com<mailto:mark.bei...@dell.com>> wrote:
Hello, team!

As StorPerf is published as a Docker container, and after looking at Functest, 
I realized that StorPerf not run natively on ARM.  I need to create ARM based 
images, and therefore would like to ask if there is any pod or resources that 
have an existing OPNFV installation on them where I can run StorPerf for 
validation testing?

Please let me know if this is something your team can provide.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

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

Re: [opnfv-tech-discuss] OPNFV Docker builds on Dockerhub account

[Beierl, Mark]

Hello, Alec.

I think the decision from the Infra WG was to stick with jobs run under the 
control of OPNFV Jenkins and not to use Docker Hub for anything at this time.  
I have not seen any meeting notes or updates after the Monday meeting (which I 
was only able to attend via IRC).

Hopefully there will be some clarifications on what approach is being taken, 
and how to use it.

As for the versioning, I think we should start a new wiki page on that to keep 
it clean.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 25, 2017, at 21:33, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:

Hi Mark,

I started to add few notes and will keep adding as I get more time. The title 
could perhaps be changed to something more general than multi docker images per 
project?
I’m not sure where to put notes related to versioning – which I think should 
predate any tooling/workflow/solution discussion. We can use that same wiki 
page or use a different one.

Thanks

  Alec


From: "Beierl, Mark" <mark.bei...@dell.com<mailto:mark.bei...@dell.com>>
Date: Thursday, July 20, 2017 at 9:19 AM
To: "Alec Hothan (ahothan)" <ahot...@cisco.com<mailto:ahot...@cisco.com>>
Cc: Fatih Degirmenci <fde...@gmail.com<mailto:fde...@gmail.com>>, Jose Lausuch 
<jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>,
 test-wg <test...@lists.opnfv.org<mailto:test...@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] OPNFV Docker builds on Dockerhub account

Hello,

The decision in the Test WG meeting today was to write up our different 
proposals with pros/cons and take it to the Infra WG for the decision to be 
made there.  I have started a wiki page [1] for review and for everyone to add 
their ideas and comments.  Please edit or mark up the page with your feedback.

[1] https://wiki.opnfv.org/display/INF/Multiple+Docker+Images+Per+Project

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Jul 20, 2017, at 11:09, Alec Hothan (ahothan) 
<ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote:


I second the concerns of Fatih with risk of having to manage 2 paths for 
building containers if the dockerhup automated build cannot fully satisfy our 
requirements.
Before we make a decision I’d like to suggest that we first iron out our 
requirements, then it will be easier to make a decision.




From: 
<opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Fatih Degirmenci <fde...@gmail.com<mailto:fde...@gmail.com>>
Date: Wednesday, July 19, 2017 at 7:11 AM
To: Jose Lausuch <jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>>, 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
<opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] OPNFV Docker builds on Dockerhub account

Hi,

It looks nice!

Here are some comments.

The most important comment I have is the ability to run docker builds for 
patches as part of verify jobs and post feedback to OPNFV Gerrit. If we go this 
path, we will have pre-merge builds done on our machines and post-merge builds 
done on docker hub, which will result in at least same amount of maintenance 
effort if not more. Also things might result differently due to having 2 
different environments where the builds are done.

[Alec]
you’re touching a very important point which is how do teams verify that their 
commit “works”.
Work could mean “my container builds properly” or could mean “it builds and it 
runs properly”.
Obviously the latter is better but generally requires heavier logistics (such 
as having a reference openstack pod used for validating containers). I have no 
idea if OPNFV has that luxury – you tell me as I’m interested as well ;-)

In any case we see that there are 2 types of container images:

  *   Those that are used to validate commits only (possibly not as stable as 
needed for external consumption)
  *   Those that are to be used by external users (presumably in a much more 
stable state)


In the first case, you’re not as committed to keep all built images (it would 
take way too much space) – in general you just want to keep the last build(s).
In the second case you’re pretty much forced to strictly version all images and 
you need to trace each image version to the exact repo commit. In terms of 
storage you need to store

[opnfv-tech-discuss] [StorPerf] Weekly Meeting Minutes 2017-07-26

[Beierl, Mark]

Hello,

You can find the weekly meeting notes in the wiki here [1].  The team reviewed 
the switch for the base container to use Alpine for all images produced, as 
well as confirmed that we are going to pursue ARM based images for Euphrates.

[1] https://wiki.opnfv.org/display/meetings/StorPerf+2017-07-26+Meeting+Notes

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] [armband] Resource for development or testing

[Beierl, Mark]

Hello, team!

As StorPerf is published as a Docker container, and after looking at Functest, 
I realized that StorPerf not run natively on ARM.  I need to create ARM based 
images, and therefore would like to ask if there is any pod or resources that 
have an existing OPNFV installation on them where I can run StorPerf for 
validation testing?

Please let me know if this is something your team can provide.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

[opnfv-tech-discuss] StorPerf at OpenStack

[Beierl, Mark]

I have submitted a StorPerf talk for the upcoming summit. Please take a moment 
to cast your vote if you have some spare time :)

https://www.openstack.org/summit/sydney-2017/vote-for-speakers/#/19163

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Jenkins servers Docker versions?

[Beierl, Mark]

Hello,

The latest storperf-master docker build is failing [1] on ericsson-build3 as it 
is unable to parse the FROM source AS label syntax [2] for Dockerfiles.  What 
version is installed and how do I request it be upgraded?  It works on Intel 
pod 24, which has docker 17.05 installed.

[1] 
https://build.opnfv.org/ci/view/storperf/job/storperf-master-docker-build-push-master/4/console
[2] https://docs.docker.com/engine/reference/builder/#from

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] update to milestone exception request process

[Beierl, Mark]

Hello, Frank.

One of the requirements of Confluence is that each page has a unique name.  
(Or, one could say that is a bug...)

This is why when creating templates, we usually put " Title..." 
or something like that into the newly created page as a temporary title so that 
the end users know they need to change the name to something unique.  That 
appears to have been overlooked in this case.  Please insert the name of the 
project requesting the exception into the title, and I'll work with David to 
change the template.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

On Jul 25, 2017, at 04:55, Frank Brockners (fbrockne) 
> wrote:

David,

I just tried to use your wiki... but unfortunately the system comes back with 
an error – see screenshot below.

Cheers, Frank



From: 
opnfv-project-leads-boun...@lists.opnfv.org
 [mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Freitag, 21. Juli 2017 20:06
To: TECH-DISCUSS OPNFV 
>;
 opnfv-project-leads 
>
Cc: Raymond Paik >; 
Tapio Tallgren >
Subject: [opnfv-project-leads] [release] update to milestone exception request 
process

Team,

After processing our first two exception requests, I found that using email was 
awkward and messy.  It's also hard to keep track of exception requests, since 
they're buried in email threads.

Therefore, I created a wiki template and enabled it via a button that can be 
used to create a new form, based on the template.  Each form that is completed 
will be listed in a table.  This is identical to how the release plan summary 
is implemented.

You may find the wiki page 
here.
  Feel free to experiment with it.  Let me know if you have questions or 
comments.  Thanks.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-project-leads mailing list
opnfv-project-le...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads

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

Re: [opnfv-tech-discuss] [infra] xci-aio How to consume as a user for hands-on investigation and manual testing

[Beierl, Mark]

Hello, Dave.  

I realize you're running on Windows, so this won't help you, but for those who 
use Linux or MacOSX, there is a terrific little python script that goes by the 
name of sshuttle [1].  It does more than just a port forward, it actually sets 
up iptables rules for all subnets on the other side of an ssh tunnel and routes 
through automatically.

I use this in Intel pod 24 from my laptop to the jumphost, which then gives me 
full connectivity to all the subnets of the OPNFV OpenStack installation :)

[1] https://github.com/apenwarr/sshuttle


Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

> On Jul 20, 2017, at 16:58, Dave Urschatz  wrote:
> 
> Thanks Markos.
> 
> It turns out the dashboard can be found by obtaining the value of 
> “external_lb_vip_address“ from the openstack_user_config.yml file under 
> xci/file/[ha|mini|noha] directories in the releng repo.  However, there is no 
> file for aio.
> 
> The only VM address on the 192.168.122.0 network is .2 and that turns out to 
> serve the horizon dashboard for the aio flavor.
> 
> The next issue is turning off https on the dashboard.  That way I would be 
> able to port forward port 80 to my desktop for access.  
> I’m looking at https://docs.openstack.org/openstack-ansible-os_horizon/latest/
> 
> Best Regards,
> 
> Dave
> 
> 
> 
> Dave Urschatz
> Senior Technical Lead
> 
> 555 Legget Drive| Tower A | Suite 600| Ottawa ON | K2K 2X3 | 613-963-1201
> 
> 
> On 2017-07-20, 3:10 AM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf 
> of Markos Chandras"  mchand...@suse.de> wrote:
> 
>On 19/07/17 21:37, Dave Urschatz wrote:
>> I’m able to run openstack commands from the ansible_ssh_host but I would
>> also like to use the horizon dashboard and console to VMs. 
>> 
>> 
>> 
>> Is there an easy way to get the horizon dashboard url in the all-in-one
>> deployment? 
>> 
>> Is there a default user and password? 
>> 
>> Any documentation?
>> 
>> 
> 
>Hello,
> 
>The documentation you are looking for is the upstream one
> 
>https://docs.openstack.org/openstack-ansible/latest/
> 
>For horizon specifically, you are probably looking at this
> 
>
> https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/verify-operation.html
> 
> 
>-- 
>markos
> 
>SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
>HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
>___
>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