Re: [opnfv-tsc] FW: [opnfv-tech-discuss] [ovno] New PTL for OVNO project

[Stuart Mackie via Lists.Opnfv.Org]

From the small OVNO community, Alex got a majority of votes, and there were no 
other nominees, so Alex is the new PTL.

Cheers

Stuart
-914 886 2534

From:  on behalf of "HU, BIN" 
Date: Friday, February 1, 2019 at 10:13 AM
To: "opnfv-...@lists.opnfv.org" 
Subject: [opnfv-tsc] FW: [opnfv-tech-discuss] [ovno] New PTL for OVNO project

Forward to TSC mailing list

From: opnfv-tech-discuss@lists.opnfv.org  
On Behalf Of Stuart Mackie
Sent: Friday, February 1, 2019 9:30 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [ovno] New PTL for OVNO project

Hi folks,

Following some reallocation of responsibilities in Juniper, I will be stepping 
down as PTL for the OpenContrail Virtual Networking for OPNFV (OVNO) project.

I am nominating Alex Levine to formally take over (he is already involved in 
Hunter activities).

The following are currently listed as committers
Stuart Mackie (wsmac...@juniper.net<mailto:wsmac...@juniper.net>)
Artur Tyloch (artur.tyl...@canonical.com<mailto:artur.tyl...@canonical.com>)
Narinder Gupta 
(narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>)
Tim Rozet (tro...@redhat.com<mailto:tro...@redhat.com>)
Iben Rodriguez (iben.rodriq...@vmsec.com<mailto:iben.rodriq...@vmsec.com>)

I vote +1 for this change.

Cheers

Stuart

……..

Stuart Mackie
SDN/NFV Architect

+1 914 886 2534

[/Users/wsmackie/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1425239323]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22853): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22853
Mute This Topic: https://lists.opnfv.org/mt/2024/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Stuart Mackie]

+1

Stuart
-914 886 2534

From:  on behalf of David McBride 

Date: Wednesday, October 4, 2017 at 2:44 PM
To: TECH-DISCUSS OPNFV 
Cc: opnfv-project-leads , TSC OPNFV 
, Raymond Paik , Tapio 
Tallgren 
Subject: [opnfv-project-leads] [release][euphrates] proposal to eliminate one 
of the two point releases for Euphrates

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

[opnfv-tech-discuss] OpenContrail support in OPNFV

[Stuart Mackie]

Original reply got caught by some Microsoft security “feature”


We didn’t make it with Danube due to lack of OpenContrail support for Mikata in 
time.

We are very close to a working deployment with Euphrates (but fighting a 
hardware issue in our lab right now). We should make it into Euphrates release. 
These are “vanilla” OpenContrail scenarios just testing with Tempest and Rallye 
– but include all the standard OpenContrail features, like L2/L3 networks, L3 
services like ACL-based network policy, ECMP, service chaining, BGP peering 
from controller to gateways, BPGaaS in vRouter, etc.

What specific requirements do you have?

Stuart
-914 886 2534


On 9/8/17, 1:08 PM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
SULLIVAN, BRYAN L (BRYAN L)"  wrote:

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let 
me know the status of that work, e.g. which scenarios are deployable, and what 
is the latest build that is deployable. We had not been actively testing with 
OCL but it is a key part of our AIC (AT Integrated Cloud) platform, and I 
need to be sure that it's included in OPNFV supported scenarios. So though we 
are not the technical experts that would develop the scenarios, we would like 
to work with whoever is, to test the scenarios and ensure that they are 
supported in Dovetail asap.

Looking forward to any advice on this.
…
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OpenContrail support in OPNFV

[Stuart Mackie]

We didn’t make it with Danube due to lack of OpenContrail support for Mikata in 
time. 

We are very close to a working deployment with Euphrates (but fighting a 
hardware issue in our lab right now). We should make it into Euphrates release. 
These are “vanilla” OpenContrail scenarios just testing with Tempest and Rallye 
– but include all the standard OpenContrail features, like L2/L3 networks, L3 
services like ACL-based network policy, ECMP, service chaining, BGP peering 
from controller to gateways, BPGaaS in vRouter, etc.

What specific requirements do you have?

Stuart
-914 886 2534

On 9/8/17, 1:08 PM, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
SULLIVAN, BRYAN L (BRYAN L)"  wrote:

Hi all,

Whoever is working on any OCL scenarios for Danube or Euphrates, please let 
me know the status of that work, e.g. which scenarios are deployable, and what 
is the latest build that is deployable. We had not been actively testing with 
OCL but it is a key part of our AIC (AT Integrated Cloud) platform, and I 
need to be sure that it's included in OPNFV supported scenarios. So though we 
are not the technical experts that would develop the scenarios, we would like 
to work with whoever is, to test the scenarios and ensure that they are 
supported in Dovetail asap.

Looking forward to any advice on this.
___
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

[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] TSC vote requested for security fix

[Stuart Mackie]

+1 - Either

Stuart
-914 886 2534

From:  on behalf of Raymond Paik 

Date: Tuesday, June 20, 2017 at 3:07 PM
To: "opnfv-...@lists.opnfv.org" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] TSC vote requested for security fix

OPNFV TSC Members:

Sorry for the short notice, but earlier today the Linux Foundation IT team has 
been made aware of a high priority security issue (see 
https://access.redhat.com/security/vulnerabilities/stackguard) and need to 
apply package errata and perform systems reboot as soon as possible.  We 
tentatively scheduled 1-hour window on June 24th @01:00 - 02:00 UTC for this 
work, but if the TSC agrees, we'd like fix this sooner.

I realize the timing is not ideal as people are working on Danube 3.0, but two 
options I'd like to propose are 22:00 - 23:00 UTC on June 21st or June 22nd.

Could I ask the TSC members to send your votes on the following as soon as 
possible?
· Do you approve an earlier security fix window? (Y/N)
· If you answered Y above, are you OK with June 21st, June 22nd, or are 
you OK with either?
Thanks,

Ray


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

Re: [opnfv-tech-discuss] Vote for the new Danube 3.0 release date

[Stuart Mackie]

I vote +1

Stuart
-914 886 2534

From:  on behalf of Raymond Paik 

Date: Wednesday, June 7, 2017 at 9:04 PM
To: "opnfv-...@lists.opnfv.org" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] Vote for the new Danube 3.0 release date

TSC members,

Apologies for a little delay on this.

As David 
communicated 
yesterday, he is recommending postponing the Danube 3.0 release date to June 
23rd (2-week delay) as community members experienced technical issues over the 
weekend.

I'd like to start an email vote among the TSC members on the following:

"Does the TSC approve changing the Danube 3.0 release date to June 23, 2017?  
(+1, 0, -1)"

Could you send me your vote by 6pm Pacific Time on June 8th (Thursday)?

Thanks,

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

Re: [opnfv-tech-discuss] Vote for the new Danube 3.0 release date

[Stuart Mackie]

+1

Stuart
-914 886 2534

From:  on behalf of Raymond Paik 

Date: Wednesday, June 7, 2017 at 9:04 PM
To: "opnfv-...@lists.opnfv.org" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: [opnfv-tech-discuss] Vote for the new Danube 3.0 release date

TSC members,

Apologies for a little delay on this.

As David 
communicated 
yesterday, he is recommending postponing the Danube 3.0 release date to June 
23rd (2-week delay) as community members experienced technical issues over the 
weekend.

I'd like to start an email vote among the TSC members on the following:

"Does the TSC approve changing the Danube 3.0 release date to June 23, 2017?  
(+1, 0, -1)"

Could you send me your vote by 6pm Pacific Time on June 8th (Thursday)?

Thanks,

Ray
___
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] [opnfvdocs] Documentation update for Danube release

[Stuart Mackie]

Hi Sofia

I am attempting to check out the docs toolchain.

There’s an instruction in 1.8.1 of 
http://artifacts.opnfv.org/opnfvdocs/docs/how-to-use-docs/documentation-example.html
 that you have to submit a patch for jjb/opnfv/opnfv-docs.yml.

Where is this file?

Thanks

Stuart
-914 886 2534

From:  on behalf of Sofia Wallin 

Date: Tuesday, February 14, 2017 at 10:40 AM
To: "TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org)" 
, "opnfv-project-le...@lists.opnfv.org" 

Subject: Re: [opnfv-project-leads] [opnfv-tech-discuss] [opnfvdocs] 
Documentation update for Danube release

Here is an example based on SFC for mapping existing documents to the new 
structure,
https://docs.google.com/presentation/d/1_PszNevu1J7KK_46p8K9L4y5AjbnDWnXfsxQN-SmETI/edit#slide=id.g20d735f830_0_0

Thanks Brady!

BR,
Sofia

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin
Sent: den 7 februari 2017 14:26
To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) 
; opnfv-project-le...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube 
release

To all projects that plans to contribute with documentation to the Danube 
release.

Hi,
As a reminder that documentation is part of the release even this time, 
following email contains some useful information and links.

Since we are moving to read the docs 
(NOTE: this page is still work in progress) for the Danube release some 
structural changes has been made. Please have a look at the wiki page linked 
below to make sure that you store your documentation according to directives.

Wiki
Information on general documentation handling can be found 
here

Milestones relevant for documentation is MS6 and MS10.
MS6 17/2 – Preliminary documentation completed
Documentation outlines or placeholders committed to repo for all project and 
release documentation
MS10 24/3 – Documentation completed
All project and release documentation reviewed and approved.

Since we still haven’t manage to establish or communicate a review process for 
release related documentation it is important to always add one or two members 
from the docs project as reviewer on documentation related additions or changes.

Everyone is welcome to join the docs 
meeting held every second 
week.

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