date:20171127

Re: [opnfv-tech-discuss] [stor4nfv] Invitation: Stor4NFV weekly project meeting

2017-11-27 Thread Wang, Shane

Hi,

Some US colleagues said this time is not friendly for US, since this time is 
their dinner time.
Do you have any objections if I push it out by 2 hours, i.e., 11am, the same 
day?

Thanks.
--
Shane
-Original Appointment-
From: Wang, Shane
Sent: Monday, October 23, 2017 9:35 AM
To: Wang, Shane; 'opnfv-tech-discuss@lists.opnfv.org'; Gohad, Tushar; Li, 
Xiaoyan; 'wangzhengy...@cmss.chinamobile.com'; Ren, Qiaowei; 
'wanghu...@huawei.com'; 'helu...@huawei.com'; 'luo.ke...@zte.com.cn'; 
'hao...@xsky.com'; 'liuy...@cmss.chinamobile.com'; 
'liujun...@cmss.chinamobile.com'; Skerry, Brian J; 'huangzhip...@huawei.com'; 
'haojin...@huawei.com'; 'mark.bei...@dell.com'; 'xu...@lenovo.com'; 
'gu...@lenovo.com'; 'xie.xing...@zte.com.cn'
Cc: Kedalagudde, Meghashree Dattatri; Canio Cillis; Maria Toeroe; Jose Angel 
Lausuch; Seiler, Glenn (Wind River); GUPTA, ALOK; Bernier, Daniel; Alan 
McNamee; Frattura, David; George Zhao; Gabor Halász; Vul, Alex; Cathy Zhang; 
Alam, Taimoor; Piyush Sarwal; Ahmed Elbornou (amaged)
Subject: [stor4nfv] Invitation: Stor4NFV weekly project meeting
When: Thursday, November 30, 2017 9:00 AM-10:00 AM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
Where: https://zoom.us/j/957741156


Hi there,

Shane Wang is inviting you to a scheduled Zoom meeting.

Topic: Stor4NFV meeting
Time: Oct 26, 2017 9:00 AM Beijing, Shanghai
Every week on Thu, until Dec 07, 2017, 7 occurrence(s)
Oct 26, 2017 9:00 AM
Nov 2, 2017 9:00 AM
Nov 9, 2017 9:00 AM
Nov 16, 2017 9:00 AM
Nov 23, 2017 9:00 AM
Nov 30, 2017 9:00 AM
Dec 7, 2017 9:00 AM
Please download and import the following iCalendar (.ics) files to your 
calendar system.
Weekly: 
https://zoom.us/meeting/957741156/ics?icsToken=05f8771546adb18950f8ba1b3e40c19ec8c339af18827234791e6585985fe708

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/957741156

Or iPhone one-tap :
US: +16468769923,,957741156#  or +16699006833,,957741156#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
US: +1 646 876 9923  or +1 669 900 6833
Meeting ID: 957 741 156
International numbers available: 
https://zoom.us/zoomconference?m=xhG06uADpUCj4FFLKw25tHJTW00qMahg


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

Re: [opnfv-tech-discuss] [barometer] weekly meeting

2017-11-27 Thread SULLIVAN, BRYAN L (BRYAN L)

If it helps, I have some logs from the:

  *   VES Agent (ves_app.log)
  *   VES Collector (monitor.log and collector.log)
  *   collectd-kafka traffic (stdout from the test kafka consumer)

These could be used to correlate what is sent when, and trace back the lineage 
of values and timestamps as suggested. But I recommend first we get the 
Barometer team to describe how that lineage is intended to work – and we can 
then verify it.

Thanks,
Bryan Sullivan | AT&T

From: MORTON, ALFRED C (AL)
Sent: Monday, November 27, 2017 6:19 PM
To: SULLIVAN, BRYAN L (BRYAN L) ; Aaron Smith 
; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [barometer] weekly meeting

Hi Aaron, Bryan, and all,

I’d like to add a brief discussion to the agenda tomorrow,
related to the thread that many project members participated
in last week, the subject was:
“ves_app.py exception when collecting from multiple collectd clients”

In short, I’m interested in the steps that measured results
follow to arrive at any VIM, and what information accompanies
the results.

One of our barometer wiki pages gives the collectd 101,
https://wiki.opnfv.org/display/fastpath/Collectd+101
gives the contents of a value list for collectd statistics.
The most important ones to this discussion are:
•  Values
•  Value length: the number of values in the data set.
•  Time: timestamp at which the value was collected.
•  Interval: interval at which to expect a new value.
•  Host: used to identify the host.

As I have mentioned before, TST008 requires that
measured values be accompanied by the time they are measured.
I now wonder if the collectd Time: when the value was “collected”
is close enough to the actual time when the hypervisor reads
the meter or gauge and passes the value to libvirtd API & virt plugin
to ignore the difference (time error). It could simplify
life on earth if the error is small.

Please give this a little thought before we meet, thanks!
Al


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L (BRYAN L)
Sent: Monday, November 27, 2017 10:15 AM
To: Aaron Smith; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [barometer] weekly meeting

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes 
stack.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

--

AARON

Re: [opnfv-tech-discuss] [barometer] weekly meeting

2017-11-27 Thread MORTON, ALFRED C (AL)

Hi Aaron, Bryan, and all,

I’d like to add a brief discussion to the agenda tomorrow,
related to the thread that many project members participated
in last week, the subject was:
“ves_app.py exception when collecting from multiple collectd clients”

In short, I’m interested in the steps that measured results
follow to arrive at any VIM, and what information accompanies
the results.

One of our barometer wiki pages gives the collectd 101,
https://wiki.opnfv.org/display/fastpath/Collectd+101
gives the contents of a value list for collectd statistics.
The most important ones to this discussion are:
•  Values
•  Value length: the number of values in the data set.
•  Time: timestamp at which the value was collected.
•  Interval: interval at which to expect a new value.
•  Host: used to identify the host.

As I have mentioned before, TST008 requires that
measured values be accompanied by the time they are measured.
I now wonder if the collectd Time: when the value was “collected”
is close enough to the actual time when the hypervisor reads
the meter or gauge and passes the value to libvirtd API & virt plugin
to ignore the difference (time error). It could simplify
life on earth if the error is small.

Please give this a little thought before we meet, thanks!
Al


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L (BRYAN L)
Sent: Monday, November 27, 2017 10:15 AM
To: Aaron Smith; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [barometer] weekly meeting

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes 
stack.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

--

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat



314 Littleton Rd, Westford, MA 01886

aasm...@redhat.comM: 
617.877.4814
[https://www.redhat.com/files/brand/email/sig-redhat.png]


___
opnfv-tech-discuss mai

Re: [opnfv-tech-discuss] ovn4nfv weekly meeting

2017-11-27 Thread Trinath Somanchi

Weekly Meeting - MoM.

http://ircbot.wl.linuxfoundation.org/meetings/ovn4nfv-meeting/2017/ovn4nfv-meeting.2017-11-28-01.00.html

Best Regards,
Trinath Somanchi | NXP | HSDC, INDIA

From: Trinath Somanchi
Sent: Monday, November 27, 2017 1:55 PM
To: TECH-DISCUSS OPNFV 
Cc: 'Aakash Kt' ; Narinder Gupta 
; 'Vikram Dham' ; 'prakash 
RAMCHANDRAN' ; Sridhar Pothuganti 
; 'Addepalli, Srinivasa R' 
; 'Dan Radez' 
Subject: ovn4nfv weekly meeting

Hi OVN4NFV team-

Please join for Project's Weekly meeting on Tuesdays, 01:00 HRS UTC to 02:00 
HRS UTC at IRC Chat #ovn4nfv-meeting.

Agenda


  *   Openstack-OVN charm - design.
  *   JOID and APEX PODs
  *   Installer discussion.


Reference links:

Project: 
https://wiki.opnfv.org/display/PROJ/Ovn4nfv
Git: 
https://git.opnfv.org/ovn4nfv
Meeting IRC: #ovn4nfv-meeting
IRC Channel: #opnfv-ovn4nfv


Best Regards,
/ Trinath Somanchi.

Trinath Somanchi.
Hyderabad Software Development Center (HSDC), GSD , DN,
NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
Hyderabad, Telangana, 500032, India

Email: trinath.soman...@nxp.com  | Mobile: +91 
9866235130 | Off: +91 4033504051
[cid:image002.png@01D28854.B7934C80]




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

[opnfv-tech-discuss] Regarding the Testperf meeting this week

2017-11-27 Thread Yuyang (Gabriel)

Hi,

Plugfest is in next week and we're all busy preparing for it.
According to the discussion/suggestions from last usual and APAC Testperf 
meeting, we'll decide if we should cancel it after sending out an email 
collecting topics.
If there is no specific topic we'd like to talk about, we'd better cancel the 
meeting.
So please feedback if you need something to be discussed.

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

Re: [opnfv-tech-discuss] ovn4nfv weekly meeting

2017-11-27 Thread Trinath Somanchi

Remainder!


Best Regards,
Trinath Somanchi | NXP | HSDC, INDIA

From: Trinath Somanchi
Sent: Monday, November 27, 2017 1:55 PM
To: TECH-DISCUSS OPNFV 
Cc: 'Aakash Kt' ; Narinder Gupta 
; 'Vikram Dham' ; 'prakash 
RAMCHANDRAN' ; Sridhar Pothuganti 
; 'Addepalli, Srinivasa R' 
; 'Dan Radez' 
Subject: ovn4nfv weekly meeting

Hi OVN4NFV team-

Please join for Project's Weekly meeting on Tuesdays, 01:00 HRS UTC to 02:00 
HRS UTC at IRC Chat #ovn4nfv-meeting.

Agenda


  *   Openstack-OVN charm - design.
  *   JOID and APEX PODs
  *   Installer discussion.


Reference links:

Project: 
https://wiki.opnfv.org/display/PROJ/Ovn4nfv
Git: 
https://git.opnfv.org/ovn4nfv
Meeting IRC: #ovn4nfv-meeting
IRC Channel: #opnfv-ovn4nfv


Best Regards,
/ Trinath Somanchi.

Trinath Somanchi.
Hyderabad Software Development Center (HSDC), GSD , DN,
NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
Hyderabad, Telangana, 500032, India

Email: trinath.soman...@nxp.com  | Mobile: +91 
9866235130 | Off: +91 4033504051
[cid:image002.png@01D28854.B7934C80]




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

Re: [opnfv-tech-discuss] [test-wg] Monitoring dashboard for long duration test

2017-11-27 Thread Julien

It's really cool.

As Kubi mentioned, it is useful to support POD level metrics info including
containers, nodes, disk/memory usage.
For network traffic, it is too sensitive when we use the instant traffic,
can we provide the daily data?
The config file "prototype_prometheus_dashboard" in review is 2000 lines
long. I suggest to use a simple Jinja2 template to produce this file. It
will more easily to use and maintain.

BR/Julien



Rutuja Surve 于2017年11月26日周日 下午6:05写道：

> Hi Kubi,
> Thanks for reviewing the dashboard.
> It is possible to monitor multiple hosts (the jump server and its
> corresponding compute and controller nodes) with this dashboard. The
> 'instance' parameter for every metric corresponds to the IP address of the
> node, hence its possible to filter it by node IP. The whole physical
> deployment is configured in the pod.yaml file where we can see information
> regarding the compute and controller nodes.
> We have scripts for installing the statistics collecting daemons (Cadvisor
> and Collectd) on the jump-server and the client nodes (Compute and
> controller) that send the metrics to the jump server.
> The 'Load' corresponds to the CPU load and can be best explained with this
> Prometheus query that is used for collecting it:
>
> node_load1{instance=~\"$server:.*\"} / count by(job, instance)(count
> by(job, instance, cpu)(node_cpu{instance=~\"$server:.*\"}))
>
> CPU Usage per container corresponds to :
>
> sum(rate(container_cpu_usage_seconds_total{name=~\".+\"}[$interval])) by
> (name) * 100
>
> So, if the sum of the rate for a particular interval exceeds 1, it can
> cross 100% and reach upto 400%. It's more about how the query is framed.
> The network traffic apparently monitors the http port of the host.
>
> Do let me know if you have more questions.
>
> Thanks,
>
> Rutuja
>
>
>
>
>
>
>
> On Wed, Nov 22, 2017 at 8:25 AM, Gaoliang (kubi)  > wrote:
>
>> Hi Rutuja,
>>
>>
>>
>> The dashboard looks pretty good J
>>
>>
>>
>> Only few questions about the dashboard.
>>
>>
>>
>> What kind of  SUT you can monitor?  A single host or 5 hosts (OPNFV
>> physical HA deployment)?  It seems that It can be filtered by Node IP. Do
>> we have a whole view for a physical deployment POD?
>>
>>
>>
>> What does the “Load” mean? CPU Load?  Why “CPU usage” can go to 400%?
>> Does the “Network Traffic” monitor one port or all of the ports of host?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kubi
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* test-wg-boun...@lists.opnfv.org [mailto:
>> test-wg-boun...@lists.opnfv.org] *On Behalf Of *Rutuja Surve
>> *Sent:* Tuesday, November 21, 2017 4:42 PM
>> *To:* opnfv-tech-discuss@lists.opnfv.org; test...@lists.opnfv.org
>> *Subject:* [test-wg] Monitoring dashboard for long duration test
>>
>>
>>
>> Hi,
>>
>> I am currently working on Bottlenecks intern project focusing on
>> monitoring/dashboarding for long duration test.
>> We have been closing to a protoype. We need your opinions/comments on how
>> to organize the dashboard, what metrics/plugins should be included, etc.
>> The screenshots/details for the pre-protoype dashboard are provided
>> below. Please comment on that.
>> Currently, we do not have a public access to the dashboard. If you'd like
>> to know more details/operations, please refer to the gerrit patch:
>>
>> https://gerrit.opnfv.org/gerrit/#/c/47567/
>>
>> and give your review there or attend the Bottlenecks meeting tomorrow
>> (Wednesday) at 8.30 am IST where I will provide regular reports for the
>> progress and show customization of the dashboard.
>>
>>
>> Also find the screenshot-pdf of the dashboard attached with this e-mail.
>> We are using Prometheus for querying and as datasource, Cadvisor and
>> Collectd plugins for collecting system metrics and Grafana for displaying
>> the dashboard.
>>
>> Thanks,
>> Rutuja
>>
>>
>>
>
> ___
> 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] [barometer] weekly meeting

2017-11-27 Thread SULLIVAN, BRYAN L (BRYAN L)

FYI, I updated the VES tools to build a container for the VES Agent (ves_app.py 
in the Barometer repo). Using it now with the latest tests for the Models 
kubernetes stack.
Also built the VES Collector as a container. Using my personal docker hub 
account for now:
https://hub.docker.com/u/blsaws/

Scripts that build these containers are in the VES repo: 
https://github.com/opnfv/ves/tree/master/build

Still trying to figure out how I can do the same with collectd – having to 
build collectd and librdkafka at deploy time really extends the test cycle, so 
it’s a priority.

Pretty soon I will be using Cloudify-kubernetes blueprints to deploy the Agent, 
Collector, and other components (Prometheus, InfluxDB, Grafana) as services on 
the k8s master node (using labels to deploy them there).

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aaron Smith
Sent: Monday, November 27, 2017 6:37 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [barometer] weekly meeting

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming what 
packages are available.  Install guide should be detailed and include 
installation of any required rpms, libraries, etc…  For example, Ubuntu / MOSS 
vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

--

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat



314 Littleton Rd, Westford, MA 01886

aasm...@redhat.comM: 
617.877.4814
[https://www.redhat.com/files/brand/email/sig-redhat.png]


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

[opnfv-tech-discuss] [barometer] weekly meeting

2017-11-27 Thread Aaron Smith

11/21/17 --

  Small crowd :)
  Welcomed a new attendee from the ARMBAND project.
  Container discussion
  How are the Barometer containers going to be distributed?
  Docker hub
  Contact Fativ about access
   Need to be careful about the underlying OS and available and assuming
what packages are available.  Install guide should be detailed and include
installation of any required rpms, libraries, etc…  For example, Ubuntu /
MOSS vs. Ubuntu ISO.  How to handle kernel versions?

Agenda for tomorrow:

More discussion on containers, VES, etc...

Aaron

-- 

AARON SMITH

SENIOR PRINCIPAL SOFTWARE ENGINEER, NFVPE

Red Hat



314 Littleton Rd, Westford, MA 01886

aasm...@redhat.comM: 617.877.4814

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

[opnfv-tech-discuss] ovn4nfv weekly meeting

2017-11-27 Thread Trinath Somanchi

Hi OVN4NFV team-

Please join for Project's Weekly meeting on Tuesdays, 01:00 HRS UTC to 02:00 
HRS UTC at IRC Chat #ovn4nfv-meeting.

Agenda


  *   Openstack-OVN charm - design.
  *   JOID and APEX PODs
  *   Installer discussion.


Reference links:

Project: 
https://wiki.opnfv.org/display/PROJ/Ovn4nfv
Git: 
https://git.opnfv.org/ovn4nfv
Meeting IRC: #ovn4nfv-meeting
IRC Channel: #opnfv-ovn4nfv


Best Regards,
/ Trinath Somanchi.

Trinath Somanchi.
Hyderabad Software Development Center (HSDC), GSD , DN,
NXP India Pvt Limited, 1st Floor, Block 3, DLF Cyber City, Gachibowli,
Hyderabad, Telangana, 500032, India

Email: trinath.soman...@nxp.com  | Mobile: +91 
9866235130 | Off: +91 4033504051
[cid:image002.png@01D28854.B7934C80]




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

Re: [opnfv-tech-discuss] [stor4nfv] Invitation: Stor4NFV weekly project meeting

Re: [opnfv-tech-discuss] [barometer] weekly meeting

Re: [opnfv-tech-discuss] [barometer] weekly meeting

Re: [opnfv-tech-discuss] ovn4nfv weekly meeting

[opnfv-tech-discuss] Regarding the Testperf meeting this week

Re: [opnfv-tech-discuss] ovn4nfv weekly meeting

Re: [opnfv-tech-discuss] [test-wg] Monitoring dashboard for long duration test

Re: [opnfv-tech-discuss] [barometer] weekly meeting

[opnfv-tech-discuss] [barometer] weekly meeting

[opnfv-tech-discuss] ovn4nfv weekly meeting

10 matches

Site Navigation

Mail list logo

Footer information