[opnfv-tech-discuss] Canceled Event: OPNFV Danube 3 Release Daily (IRC only) @ Fri Jun 30, 2017 6:30am - 7am (PDT) (opnfv-tech-discuss@lists.opnfv.org)

2017-06-29 Thread dmcbride 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20170630T063000
DTEND;TZID=America/Los_Angeles:20170630T07
DTSTAMP:20170630T044707Z
ORGANIZER;CN=dmcbr...@linuxfoundation.org:mailto:dmcbride@linuxfoundation.o
 rg
UID:k07b67k90paa5t7bh30b8m7...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=op
 nfv-tech-disc...@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech-discuss@l
 ists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=op
 nfv-project-le...@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-project-leads
 @lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=dmcbri
 d...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:dmcbr...@linuxfoundation.org
RECURRENCE-ID;TZID=America/Los_Angeles:20170630T063000
CREATED:20170625T235514Z
DESCRIPTION:Discuss Danube 3 release.
LAST-MODIFIED:20170630T044707Z
LOCATION:IRC channel: opnfv-release
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:OPNFV Danube 3 Release Daily (IRC only)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

[opnfv-tech-discuss] 答复: Proposal to implement installers' quickstart wrapper scripts

2017-06-29 Thread Chigang (Justin) 
Pretty cool!

It seems that there are already two installers that support a quick virtual 
deployment without any setup. 

As Luke mentioned, if the security problems can be resolved, it will give users 
lots of convenience to use OPNFV.

Regards
Justin

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Tim Rozet
发送时间: 2017年6月29日 21:09
收件人: Luke Hinds
抄送: bryan sullivan; narinder gupta; opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

A script like this exists for Apex today:
https://github.com/opnfv/apex/blob/stable/danube/contrib/simple_deploy.sh

Thanks to Nikolas for contributing it.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Luke Hinds" 
To: "liangqi (D)" 
Cc: "bryan sullivan" , 
opnfv-tech-discuss@lists.opnfv.org, "narinder gupta" 

Sent: Thursday, June 29, 2017 6:32:21 AM
Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

Hi, 

Don't want to detract from the topic, but please do not use curl | bash, its 
dangerous and if opnfv.org is every compromised, scripts like this could be 
used to back door all the PODS and test sites deployed by end users. 

If deploying a system this way, then use a checksum (with sha256 or stronger) 
to first to insure the script has not been tampered with (I have examples if 
some are needed). 

Cheers, 

Luke 

On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D) < liang...@huawei.com > wrote: 



Hi, 

In OPNFV we have 4 installers in Danube release, we will have more in the next 
release. Each of them supports multiple scenarios and has different install 
user steps. This is quite confusing and difficult to use, especially for the 
newbies. 

In releng we already have scripts to trigger all installers' deploy and test, 
but the scripts are CI oriented, not user oriented. 

So I proposal to implement wrapper scripts in releng to provide easy way for 
people to try opnfv. With minimum requirement(a server with Ubuntu 14.04/16.04 
or CentOS7 installed and with internet connectivity), without checking detail 
installers' install guide, just run one command you will get your environment 
ready. 

The simplest way to install opnfv environment will be like: 
`curl https://get.opnfv.org/ephrates/quickstart.sh | bash`. 

For each installer we may have one command deploy like: 
`curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash` 

Basic virtual deploy workflows: 

1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh | 
bash`) 2. Check environment 3. Fetch supported installers and select one 
installer 4. Generate the deploy command and execute 5. Verify the deployed 
environment 6. Deploy success 

For BareMetal deployment the workflow are almost the same, the only different 
is you need prepare physical servers/switches, connect the cables, setup the 
switches, create a pod-descriptor file, and run the deploy command with the 
pod-descriptor file. 

The attached slide illustrate the initial idea, which was shared by Justin at 
the OPNFV Summit in Beijing. 
Here is the initial script patch: https://gerrit.opnfv.org/gerrit/#/c/36711/ 

@Uli, I saw you've sent the latest infra working group meeting agenda in the 
mailing list. Could you please include the topic to the infra working group 
meeting agenda. 

Welcome feedback, comments, discuss here or at the infra working group meeting. 

Best Regards,
Qi Liang 

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




--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 
12 52 36 2483 

___
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] [Infra][Pharos][Releng][Octopus] Proposal to implement installers' quickstart wrapper scripts

2017-06-29 Thread liangqi (D) 
Thanks for pointing out this security issue.

I think curl | bash install is the easiest way to deploying a system, and with 
minimum dependency. Could you please some examples on how to use checksum to 
insure the script is securely executed.

I saw at the head of https://get.docker.com/ has the info like:

```bash
# This script is meant for quick & easy install via:
#   $ curl -fsSL get.docker.com -o get-docker.sh
#   $ sh get-docker.sh
#
# For test builds (ie. release candidates):
#   $ curl -fsSL test.docker.com -o test-docker.sh
#   $ sh test-docker.sh
#
# NOTE: Make sure to verify the contents of the script
#   you downloaded matches the contents of install.sh
#   located at https://github.com/docker/docker-install
#   before executing.
```

Best Regards,
Qi Liang

From: Luke Hinds [lhi...@redhat.com]
Sent: Thursday, June 29, 2017 18:32
To: liangqi (D)
Cc: opnfv-tech-discuss@lists.opnfv.org; bryan.sulli...@att.com; 
narinder.gu...@canonical.com
Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

Hi,

Don't want to detract from the topic, but please do not use curl | bash, its 
dangerous and if opnfv.org is every compromised, scripts like 
this could be used to back door all the PODS and test sites deployed by end 
users.

If deploying a system this way, then use a checksum (with sha256 or stronger) 
to first to insure the script has not been tampered with (I have examples if 
some are needed).

Cheers,

Luke

On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D) 
mailto:liang...@huawei.com>> wrote:
Hi,

In OPNFV we have 4 installers in Danube release, we will have more in the next 
release. Each of them supports multiple scenarios and has different install 
user steps. This is quite confusing and difficult to use, especially for the 
newbies.

In releng we already have scripts to trigger all installers' deploy and test, 
but the scripts are CI oriented, not user oriented.

So I proposal to implement wrapper scripts in releng to provide easy way for 
people to try opnfv. With minimum requirement(a server with Ubuntu 14.04/16.04 
or CentOS7 installed and with internet connectivity), without checking detail 
installers' install guide, just run one command you will get your environment 
ready.

The simplest way to install opnfv environment will be like:
`curl https://get.opnfv.org/ephrates/quickstart.sh | bash`.

For each installer we may have one command deploy like:
`curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash`

Basic virtual deploy workflows:

1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh | bash`)
2. Check environment
3. Fetch supported installers and select one installer
4. Generate the deploy command and execute
5. Verify the deployed environment
6. Deploy success

For BareMetal deployment the workflow are almost the same, the only different 
is you need prepare physical servers/switches, connect the cables, setup the 
switches, create a pod-descriptor file, and run the deploy command with the 
pod-descriptor file.

The attached slide illustrate the initial idea, which was shared by Justin at 
the OPNFV Summit in Beijing.
Here is the initial script patch: https://gerrit.opnfv.org/gerrit/#/c/36711/

@Uli, I saw you've sent the latest infra working group meeting agenda in the 
mailing list. Could you please include the topic to the infra working group 
meeting agenda.

Welcome feedback, comments, discuss here or at the infra working group meeting.

Best Regards,
Qi Liang

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




--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 
77 45 63 98 84 | t: +44 12 52 36 2483
___
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][Pharos][Releng][Octopus] Proposal to implement installers' quickstart wrapper scripts

2017-06-29 Thread liangqi (D) 
That is great and a very good start. I'll try this script.

Best Regards,
Qi Liang

From: Tim Rozet [tro...@redhat.com]
Sent: Thursday, June 29, 2017 21:09
To: Luke Hinds
Cc: liangqi (D); bryan sullivan; opnfv-tech-discuss@lists.opnfv.org; narinder 
gupta; Nikolas Hermanns
Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

A script like this exists for Apex today:
https://github.com/opnfv/apex/blob/stable/danube/contrib/simple_deploy.sh

Thanks to Nikolas for contributing it.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Luke Hinds" 
To: "liangqi (D)" 
Cc: "bryan sullivan" , 
opnfv-tech-discuss@lists.opnfv.org, "narinder gupta" 

Sent: Thursday, June 29, 2017 6:32:21 AM
Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

Hi,

Don't want to detract from the topic, but please do not use curl | bash, its 
dangerous and if opnfv.org is every compromised, scripts like this could be 
used to back door all the PODS and test sites deployed by end users.

If deploying a system this way, then use a checksum (with sha256 or stronger) 
to first to insure the script has not been tampered with (I have examples if 
some are needed).

Cheers,

Luke

On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D) < liang...@huawei.com > wrote:



Hi,

In OPNFV we have 4 installers in Danube release, we will have more in the next 
release. Each of them supports multiple scenarios and has different install 
user steps. This is quite confusing and difficult to use, especially for the 
newbies.

In releng we already have scripts to trigger all installers' deploy and test, 
but the scripts are CI oriented, not user oriented.

So I proposal to implement wrapper scripts in releng to provide easy way for 
people to try opnfv. With minimum requirement(a server with Ubuntu 14.04/16.04 
or CentOS7 installed and with internet connectivity), without checking detail 
installers' install guide, just run one command you will get your environment 
ready.

The simplest way to install opnfv environment will be like:
`curl https://get.opnfv.org/ephrates/quickstart.sh | bash`.

For each installer we may have one command deploy like:
`curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash`

Basic virtual deploy workflows:

1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh | bash`)
2. Check environment
3. Fetch supported installers and select one installer
4. Generate the deploy command and execute
5. Verify the deployed environment
6. Deploy success

For BareMetal deployment the workflow are almost the same, the only different 
is you need prepare physical servers/switches, connect the cables, setup the 
switches, create a pod-descriptor file, and run the deploy command with the 
pod-descriptor file.

The attached slide illustrate the initial idea, which was shared by Justin at 
the OPNFV Summit in Beijing.
Here is the initial script patch: https://gerrit.opnfv.org/gerrit/#/c/36711/

@Uli, I saw you've sent the latest infra working group meeting agenda in the 
mailing list. Could you please include the topic to the infra working group 
meeting agenda.

Welcome feedback, comments, discuss here or at the infra working group meeting.

Best Regards,
Qi Liang

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




--
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 
12 52 36 2483

___
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] KDDI monitoring proposal from the summit

2017-06-29 Thread Ryota Mibu 
Bryan,


Here's the short version of the slide deck presented by the idea from KDDI Labs:

   
https://www.slideshare.net/kimw001/kddi-openstack-summit-2016red-hat-nfv-mini-summit

We also have updates presented in OpenStack Summit Boston. You can get slides 
and video from the official site:

   
https://www.openstack.org/videos/boston-2017/distributed-monitoring-and-analysis-for-telecom-requirements

You can find the members working in this project at the first slide in the 
second presentation slide deck. I'm also CCing them in this email. Feel free to 
ask any question you may have.


BR,
Ryota

> -Original Message-
> From: Bryan Sullivan [mailto:bls...@hotmail.com]
> Sent: Friday, June 30, 2017 2:17 AM
> To: Mibu Ryota(壬生 亮太) ; 
> opnfv-tech-discuss@lists.opnfv.org
> Subject: KDDI monitoring proposal from the summit
> 
> Ryota,
> 
> Do you have any info about the proposal presented by KDDI (I think) at the 
> summit Monitoring Team Gathering session? If
> there was a deck or other info we can reference, or you can share who we 
> should reach out to for more info, it would be
> great.
> 
> Thanks,
> Bryan Sullivan
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [daisy4nfv] Agenda for IRC meeting 0800UTC Jun. 30 2017

2017-06-29 Thread hu.zhijiang 
1.ODL L2/L3 Integration 

2.Scenario in JJB


3.Documentation task

4.AoB











B. R.,

Zhijiang___
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] sdnvpn test cases with dovetail.cvp.0.1.0 throw an error

2017-06-29 Thread xudan (N) 
Hi Srikanth,

We have tested dovetail:cvp.0.1.0 locally and have not found this ERROR. Maybe 
there are something wrong when you create the Dovetail container.

Can you show us the command. According to the log, the right command for you is:

 sudo docker run -it --privileged=true -e DOVETAIL_HOME=/root/dovetail 
-v /root/dovetail: /root/dovetail -v /var/run/docker.sock:/var/run/docker.sock 
opnfv/dovetail:cvp.0.1.0 /bin/bash

Thanks
Dan Xu

发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Srikanth Vavilapalli
发送时间: 2017年6月30日 7:03
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [Dovetail] sdnvpn test cases with dovetail.cvp.0.1.0 
throw an error

Hi

When I run the `sdnvpn’ dovetail test cases, I see the below error for each 
run. I have ensured that the ubuntu cloudimg is present under 
$(DOVETAIL_HOME)/pre_config folder on the host before executing these tests. 
The failure is happening when the dovetail container is trying to copy the file 
from one location to other location in the functest container & this folder 
/home/opnfv/userconfig/pre_config/ does not exist in the functest container. 
Can any one plz help me with this error?


root@98da04f3fb76:/usr/local/lib/python2.7/dist-packages/dovetail#
 dovetail run --testsuite proposed_tests --testarea sdnvpn
2017-06-29 23:38:07,875 - run - INFO - 

2017-06-29 23:38:07,875 - run - INFO - Dovetail compliance: proposed_tests!
2017-06-29 23:38:07,875 - run - INFO - 

2017-06-29 23:38:07,875 - run - INFO - Build tag: 
daily-master-350ba85a-b2bf-4693-a107-ca25af60b925
2017-06-29 23:38:08,109 - run - INFO - >>[testcase]: dovetail.sdnvpn.tc001
2017-06-29 23:38:09,428 - container.Container - INFO - get hosts info
2017-06-29 23:38:09,947 - container.Container - ERROR - The command 'sudo 
docker exec 4e7f920152d3 /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/ubuntu-16.04-server-cloudimg-amd64-disk1.img 
/home/opnfv/functest/images"' failed.
2017-06-29 23:38:10,010 - container.Container - ERROR - The command 'sudo 
docker exec 4e7f920152d3 /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/sdnvpn_config_testcase1.yaml 
/home/opnfv/repos/sdnvpn/sdnvpn/test/functest/config.yaml"' failed.
2017-06-29 23:39:19,314 - run - ERROR - Fail to store results with file 
/root/dovetail/results/functest_results.txt.
2017-06-29 23:39:19,315 - report.FunctestCrawler - INFO - result file not 
found: /root/dovetail/results/functest_results.txt
2017-06-29 23:39:19,315 - run - INFO - >>[testcase]: dovetail.sdnvpn.tc002
2017-06-29 23:39:19,317 - container.Container - INFO - get hosts info
2017-06-29 23:39:19,788 - container.Container - ERROR - The command 'sudo 
docker exec 25805da3d12b /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/ubuntu-16.04-server-cloudimg-amd64-disk1.img 
/home/opnfv/functest/images"' failed.
….


root@98da04f3fb76:/usr/local/lib/python2.7/dist-packages/dovetail#
 ls /root/dovetail/pre_config/
env_config.sh sdnvpn_config_testcase3.yaml
hosts.yamlsdnvpn_config_testcase4.yaml
pod.yaml.sample   sdnvpn_config_testcase8.yaml
sdnvpn_config_testcase1.yaml  ubuntu-16.04-server-cloudimg-amd64-disk1.img
sdnvpn_config_testcase2.yaml


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

[opnfv-tech-discuss] [Dovetail] sdnvpn test cases with dovetail.cvp.0.1.0 throw an error

2017-06-29 Thread Srikanth Vavilapalli 
Hi

When I run the `sdnvpn' dovetail test cases, I see the below error for each 
run. I have ensured that the ubuntu cloudimg is present under 
$(DOVETAIL_HOME)/pre_config folder on the host before executing these tests. 
The failure is happening when the dovetail container is trying to copy the file 
from one location to other location in the functest container & this folder 
/home/opnfv/userconfig/pre_config/ does not exist in the functest container. 
Can any one plz help me with this error?


root@98da04f3fb76:/usr/local/lib/python2.7/dist-packages/dovetail# dovetail run 
--testsuite proposed_tests --testarea sdnvpn
2017-06-29 23:38:07,875 - run - INFO - 

2017-06-29 23:38:07,875 - run - INFO - Dovetail compliance: proposed_tests!
2017-06-29 23:38:07,875 - run - INFO - 

2017-06-29 23:38:07,875 - run - INFO - Build tag: 
daily-master-350ba85a-b2bf-4693-a107-ca25af60b925
2017-06-29 23:38:08,109 - run - INFO - >>[testcase]: dovetail.sdnvpn.tc001
2017-06-29 23:38:09,428 - container.Container - INFO - get hosts info
2017-06-29 23:38:09,947 - container.Container - ERROR - The command 'sudo 
docker exec 4e7f920152d3 /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/ubuntu-16.04-server-cloudimg-amd64-disk1.img 
/home/opnfv/functest/images"' failed.
2017-06-29 23:38:10,010 - container.Container - ERROR - The command 'sudo 
docker exec 4e7f920152d3 /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/sdnvpn_config_testcase1.yaml 
/home/opnfv/repos/sdnvpn/sdnvpn/test/functest/config.yaml"' failed.
2017-06-29 23:39:19,314 - run - ERROR - Fail to store results with file 
/root/dovetail/results/functest_results.txt.
2017-06-29 23:39:19,315 - report.FunctestCrawler - INFO - result file not 
found: /root/dovetail/results/functest_results.txt
2017-06-29 23:39:19,315 - run - INFO - >>[testcase]: dovetail.sdnvpn.tc002
2017-06-29 23:39:19,317 - container.Container - INFO - get hosts info
2017-06-29 23:39:19,788 - container.Container - ERROR - The command 'sudo 
docker exec 25805da3d12b /bin/bash -c "cp 
/home/opnfv/userconfig/pre_config/ubuntu-16.04-server-cloudimg-amd64-disk1.img 
/home/opnfv/functest/images"' failed.



root@98da04f3fb76:/usr/local/lib/python2.7/dist-packages/dovetail# ls 
/root/dovetail/pre_config/
env_config.sh sdnvpn_config_testcase3.yaml
hosts.yamlsdnvpn_config_testcase4.yaml
pod.yaml.sample   sdnvpn_config_testcase8.yaml
sdnvpn_config_testcase1.yaml  ubuntu-16.04-server-cloudimg-amd64-disk1.img
sdnvpn_config_testcase2.yaml


Thanks
Srikanth
___
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-tsc] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Ross Brattain 
+1

--

Ross Brattain (proxy for Jack Morgan)


On 06/29/2017 01:59 PM, David McBride wrote:
+Ross

On Thu, Jun 29, 2017 at 12:21 PM, Tim Irnich mailto:tim.irn...@ericsson.com>> wrote:

+1

Regards, Tim

Von meinem iPhone gesendet

Am 29.06.2017 um 17:05 schrieb Frank Brockners (fbrockne) 
mailto:fbroc...@cisco.com>>:

> +1
>
> Frank
>
> Am 28.06.2017 um 11:12 schrieb David McBride 
> mailto:dmcbr...@linuxfoundation.org>>:
>
>> TSC,
>>
>> After examining status and considering various alternatives, Ray and I 
>> have agreed to propose July 14 as the new release date for Danube 3.  We 
>> believe that this will give project and installer teams time to overcome 
>> current issues, as well as allowing us to avoid the 4th of July holiday in 
>> the U.S., when many community members will be away on vacation.
>>
>> Assuming that the TSC approves this change, then I would suggest the 
>> following schedule:
>>
>>   * July 12 - complete testing
>>   * July 13 - finish document updates / update JIRA
>>   * July 14 - tag repos and release
>>   * Week of July 17 - download page goes live
>>
>> TSC members, *please respond to this email with your vote on the 
>> following by EOD PT June 30*:
>>
>> Does the TSC approve moving the Danube 3.0 release date to July 
>> 14th? (+1, 0, -1)
>>
>> 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-tsc mailing list
> opnfv-...@lists.opnfv.org 
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc 
> 




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

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread David McBride 
+Ross

On Thu, Jun 29, 2017 at 12:21 PM, Tim Irnich 
wrote:

> +1
>
> Regards, Tim
>
> Von meinem iPhone gesendet
>
> Am 29.06.2017 um 17:05 schrieb Frank Brockners (fbrockne) <
> fbroc...@cisco.com>:
>
> +1
>
> Frank
>
> Am 28.06.2017 um 11:12 schrieb David McBride  >:
>
> TSC,
>
> After examining status and considering various alternatives, Ray and I
> have agreed to propose July 14 as the new release date for Danube 3.  We
> believe that this will give project and installer teams time to overcome
> current issues, as well as allowing us to avoid the 4th of July holiday in
> the U.S., when many community members will be away on vacation.
>
> Assuming that the TSC approves this change, then I would suggest the
> following schedule:
>
>- July 12 - complete testing
>- July 13 - finish document updates / update JIRA
>- July 14 - tag repos and release
>- Week of July 17 - download page goes live
>
> TSC members, *please respond to this email with your vote on the
> following by EOD PT June 30*:
>
> Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1,
> 0, -1)
>
> 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-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
>
>


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

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Tim Irnich 
+1

Regards, Tim

Von meinem iPhone gesendet

> Am 29.06.2017 um 17:05 schrieb Frank Brockners (fbrockne) 
> :
> 
> +1
> 
> Frank
> 
> Am 28.06.2017 um 11:12 schrieb David McBride :
> 
>> TSC,
>> 
>> After examining status and considering various alternatives, Ray and I have 
>> agreed to propose July 14 as the new release date for Danube 3.  We believe 
>> that this will give project and installer teams time to overcome current 
>> issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
>> when many community members will be away on vacation.
>> 
>> Assuming that the TSC approves this change, then I would suggest the 
>> following schedule:
>> July 12 - complete testing
>> July 13 - finish document updates / update JIRA
>> July 14 - tag repos and release
>> Week of July 17 - download page goes live
>> TSC members, please respond to this email with your vote on the following by 
>> EOD PT June 30:
>> 
>> Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 
>> 0, -1)
>> 
>> 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-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc


smime.p7s
Description: S/MIME cryptographic signature
___
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-tsc] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Dave Neary 
+1
- Stuart Mackie  wrote:
> +1
> 
> Stuart
> -914 886 2534
> 
> From:  on behalf of David McBride 
> 
> Date: Wednesday, June 28, 2017 at 2:11 PM
> To: TSC OPNFV 
> Cc: TECH-DISCUSS OPNFV 
> Subject: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / 
> proposed change to release date for Danube 3.0
> 
> TSC,
> 
> After examining status and considering various alternatives, Ray and I have 
> agreed to propose July 14 as the new release date for Danube 3.  We believe 
> that this will give project and installer teams time to overcome current 
> issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
> when many community members will be away on vacation.
> 
> Assuming that the TSC approves this change, then I would suggest the 
> following schedule:
> · July 12 - complete testing
> · July 13 - finish document updates / update JIRA
> · July 14 - tag repos and release
> · Week of July 17 - download page goes live
> TSC members, please respond to this email with your vote on the following by 
> EOD PT June 30:
> 
> Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
> -1)
> 
> 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] KDDI monitoring proposal from the summit

2017-06-29 Thread Bryan Sullivan 
Ryota,

Do you have any info about the proposal presented by KDDI (I think) at the 
summit Monitoring Team Gathering session? If there was a deck or other info we 
can reference, or you can share who we should reach out to for more info, it 
would be great.

Thanks,
Bryan Sullivan   
___
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][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Frank Brockners (fbrockne) 
+1

Frank

Am 28.06.2017 um 11:12 schrieb David McBride 
mailto:dmcbr...@linuxfoundation.org>>:

TSC,

After examining status and considering various alternatives, Ray and I have 
agreed to propose July 14 as the new release date for Danube 3.  We believe 
that this will give project and installer teams time to overcome current 
issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
when many community members will be away on vacation.

Assuming that the TSC approves this change, then I would suggest the following 
schedule:

  *   July 12 - complete testing
  *   July 13 - finish document updates / update JIRA
  *   July 14 - tag repos and release
  *   Week of July 17 - download page goes live

TSC members, please respond to this email with your vote on the following by 
EOD PT June 30:

Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
-1)

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] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Stuart Mackie 
+1

Stuart
-914 886 2534

From:  on behalf of David McBride 

Date: Wednesday, June 28, 2017 at 2:11 PM
To: TSC OPNFV 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed 
change to release date for Danube 3.0

TSC,

After examining status and considering various alternatives, Ray and I have 
agreed to propose July 14 as the new release date for Danube 3.  We believe 
that this will give project and installer teams time to overcome current 
issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
when many community members will be away on vacation.

Assuming that the TSC approves this change, then I would suggest the following 
schedule:
· July 12 - complete testing
· July 13 - finish document updates / update JIRA
· July 14 - tag repos and release
· Week of July 17 - download page goes live
TSC members, please respond to this email with your vote on the following by 
EOD PT June 30:

Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
-1)

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

Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to implement installers' quickstart wrapper scripts

2017-06-29 Thread Tim Rozet 
A script like this exists for Apex today:
https://github.com/opnfv/apex/blob/stable/danube/contrib/simple_deploy.sh

Thanks to Nikolas for contributing it.

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Luke Hinds" 
To: "liangqi (D)" 
Cc: "bryan sullivan" , 
opnfv-tech-discuss@lists.opnfv.org, "narinder gupta" 

Sent: Thursday, June 29, 2017 6:32:21 AM
Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to 
implement installers' quickstart wrapper scripts

Hi, 

Don't want to detract from the topic, but please do not use curl | bash, its 
dangerous and if opnfv.org is every compromised, scripts like this could be 
used to back door all the PODS and test sites deployed by end users. 

If deploying a system this way, then use a checksum (with sha256 or stronger) 
to first to insure the script has not been tampered with (I have examples if 
some are needed). 

Cheers, 

Luke 

On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D) < liang...@huawei.com > wrote: 



Hi, 

In OPNFV we have 4 installers in Danube release, we will have more in the next 
release. Each of them supports multiple scenarios and has different install 
user steps. This is quite confusing and difficult to use, especially for the 
newbies. 

In releng we already have scripts to trigger all installers' deploy and test, 
but the scripts are CI oriented, not user oriented. 

So I proposal to implement wrapper scripts in releng to provide easy way for 
people to try opnfv. With minimum requirement(a server with Ubuntu 14.04/16.04 
or CentOS7 installed and with internet connectivity), without checking detail 
installers' install guide, just run one command you will get your environment 
ready. 

The simplest way to install opnfv environment will be like: 
`curl https://get.opnfv.org/ephrates/quickstart.sh | bash`. 

For each installer we may have one command deploy like: 
`curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash` 

Basic virtual deploy workflows: 

1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh | 
bash`) 
2. Check environment 
3. Fetch supported installers and select one installer 
4. Generate the deploy command and execute 
5. Verify the deployed environment 
6. Deploy success 

For BareMetal deployment the workflow are almost the same, the only different 
is you need prepare physical servers/switches, connect the cables, setup the 
switches, create a pod-descriptor file, and run the deploy command with the 
pod-descriptor file. 

The attached slide illustrate the initial idea, which was shared by Justin at 
the OPNFV Summit in Beijing. 
Here is the initial script patch: https://gerrit.opnfv.org/gerrit/#/c/36711/ 

@Uli, I saw you've sent the latest infra working group meeting agenda in the 
mailing list. Could you please include the topic to the infra working group 
meeting agenda. 

Welcome feedback, comments, discuss here or at the infra working group meeting. 

Best Regards, 
Qi Liang 

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




-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat 
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 
12 52 36 2483 

___
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] Roll out of CI Gate Security (please read if PTL)

2017-06-29 Thread Luke Hinds 
Hi,

Over the 30 days we will be rolling out CI gate security checks (anteater)
to all projects.

The checks will be non-voting for the E release cycle, and voting for F, so
there is plenty of time for people to get used to what anteater reports on.

A full schedule can be seen here:
https://wiki.opnfv.org/display/INF/Project+Roll+Out+for+Anteater

All projects have been added, apart from those that are locked.

Some key points:

If anteater reports a failure, please add myself or someone from releng,
infra-wg as reviewers (handy way of notifying us).  We can then help create
an exception for you.

Each project, will have its own exception file (think of this as a filter
that allows certain strings to pass unchallenged). For reference, you can
see how functest are starting to work with their own file [1]

[1] https://git.opnfv.org/releng-anteater/commit/exceptions/functest.yaml

Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
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][Pharos][Releng][Octopus] Proposal to implement installers' quickstart wrapper scripts

2017-06-29 Thread Luke Hinds 
Hi,

Don't want to detract from the topic, but please do not use curl | bash,
its dangerous and if opnfv.org is every compromised, scripts like this
could be used to back door all the PODS and test sites deployed by end
users.

If deploying a system this way, then use a checksum (with sha256 or
stronger) to first to insure the script has not been tampered with (I have
examples if some are needed).

Cheers,

Luke

On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D)  wrote:

> Hi,
>
> In OPNFV we have 4 installers in Danube release, we will have more in the
> next release. Each of them supports multiple scenarios and has different
> install user steps. This is quite confusing and difficult to use,
> especially for the newbies.
>
> In releng we already have scripts to trigger all installers' deploy and
> test, but the scripts are CI oriented, not user oriented.
>
> So I proposal to implement wrapper scripts in releng to provide easy way
> for people to try opnfv. With minimum requirement(a server with Ubuntu
> 14.04/16.04 or CentOS7 installed and with internet connectivity), without
> checking detail installers' install guide, just run one command you will
> get your environment ready.
>
> The simplest way to install opnfv environment will be like:
> `curl https://get.opnfv.org/ephrates/quickstart.sh | bash`.
>
> For each installer we may have one command deploy like:
> `curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash`
>
> Basic virtual deploy workflows:
>
> 1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh |
> bash`)
> 2. Check environment
> 3. Fetch supported installers and select one installer
> 4. Generate the deploy command and execute
> 5. Verify the deployed environment
> 6. Deploy success
>
> For BareMetal deployment the workflow are almost the same, the only
> different is you need prepare physical servers/switches, connect the
> cables, setup the switches, create a pod-descriptor file, and run the
> deploy command with the pod-descriptor file.
>
> The attached slide illustrate the initial idea, which was shared by Justin
> at the OPNFV Summit in Beijing.
> Here is the initial script patch: https://gerrit.opnfv.org/
> gerrit/#/c/36711/
>
> @Uli, I saw you've sent the latest infra working group meeting agenda in
> the mailing list. Could you please include the topic to the infra working
> group meeting agenda.
>
> Welcome feedback, comments, discuss here or at the infra working group
> meeting.
>
> Best Regards,
> Qi Liang
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
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][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Ulrich Kleber 
+1

Uli

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tianhongbo
Sent: Thursday, 29 June, 2017 02:52
To: HU, BIN; Beierl, Mark; David McBride
Cc: TSC OPNFV; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] 答复: [release][announce] RESPONSE REQUIRED / 
proposed change to release date for Danube 3.0

+1

Hongbo

发件人: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 HU, BIN
发送时间: 2017年6月29日 6:40
收件人: Beierl, Mark; David McBride
抄送: TSC OPNFV; 
opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed 
change to release date for Danube 3.0

+1.

Bin
From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Wednesday, June 28, 2017 11:24 AM
To: David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Cc: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / 
proposed change to release date for Danube 3.0

Vote: +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 Jun 28, 2017, at 14:11, David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:

TSC,

After examining status and considering various alternatives, Ray and I have 
agreed to propose July 14 as the new release date for Danube 3.  We believe 
that this will give project and installer teams time to overcome current 
issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
when many community members will be away on vacation.

Assuming that the TSC approves this change, then I would suggest the following 
schedule:

  *   July 12 - complete testing
  *   July 13 - finish document updates / update JIRA
  *   July 14 - tag repos and release
  *   Week of July 17 - download page goes live
TSC members, please respond to this email with your vote on the following by 
EOD PT June 30:

Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
-1)

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] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
On behalf of Frank Brockners,

+1

Juraj

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Wednesday, 28 June, 2017 20:11
To: TSC OPNFV 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed 
change to release date for Danube 3.0

TSC,

After examining status and considering various alternatives, Ray and I have 
agreed to propose July 14 as the new release date for Danube 3.  We believe 
that this will give project and installer teams time to overcome current 
issues, as well as allowing us to avoid the 4th of July holiday in the U.S., 
when many community members will be away on vacation.

Assuming that the TSC approves this change, then I would suggest the following 
schedule:

  *   July 12 - complete testing
  *   July 13 - finish document updates / update JIRA
  *   July 14 - tag repos and release
  *   Week of July 17 - download page goes live
TSC members, please respond to this email with your vote on the following by 
EOD PT June 30:

Does the TSC approve moving the Danube 3.0 release date to July 14th? (+1, 0, 
-1)

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

Re: [opnfv-tech-discuss] [release][announce] RESPONSE REQUIRED / proposed change to release date for Danube 3.0

2017-06-29 Thread morgan.richomme 

+1

On 28/06/2017 20:11, David McBride wrote:

TSC,

After examining status and considering various alternatives, Ray and I 
have agreed to propose July 14 as the new release date for Danube 3.  
We believe that this will give project and installer teams time to 
overcome current issues, as well as allowing us to avoid the 4th of 
July holiday in the U.S., when many community members will be away on 
vacation.


Assuming that the TSC approves this change, then I would suggest the 
following schedule:


  * July 12 - complete testing
  * July 13 - finish document updates / update JIRA
  * July 14 - tag repos and release
  * Week of July 17 - download page goes live

TSC members, *please respond to this email with your vote on the 
following by EOD PT June 30*:


Does the TSC approve moving the Danube 3.0 release date to July
14th? (+1, 0, -1)

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



--
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA

Network architect for innovative services
Future of the Network community member
Open source Orange community manager


tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.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
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss