date:20170501

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

2017-05-01 Thread HU, BIN

Guys,

What I see here is power struggle. We all have seen this type of things many 
times before, especially with strong opinion.

Here are my 2 cents:

(1) TSC shouldn't interfere with the internal management of a project. It will 
be a bad precedent for TSC to intervene a project's internal matters here 
unless there is an evidenced misconduct. Otherwise it will open a can of worm 
for future.

(2) One vote per committer cannot be changed at project level. Again, it will 
be a bad precedent to introduce one vote per company within a project. Project 
is contribution driven, and committer promotion is based on merit. That's the 
principle. If one person has made significant contribution, the person deserves 
the promotion no matter what company he works for. If we change the principle, 
basically we lose the credibility as an open source community.

(3) All of those different opinion should be addressed at project level. If you 
are not the majority of opinion, and you lose the vote, sorry you lose. You 
have to accept the result of the voting. Power struggling happens everywhere, 
and I personally experienced it too. You have to negotiate and make compromise, 
even if you have strong opinion. Sorry, you need to learn "compromise". 
Exaggerating power struggle is not a right way to move forward.

(4) If there is an *evidence* that there is a *misconduct* within a project, 
please submit the evidence, and describe the nature of misconduct. TSC can 
discuss the nature of the misconduct based on evidence, further investigate it 
and take disciplinary actions based on the result of investigation of the 
misconduct according to authorized power by TSC Charter.

(5) If there is a concern that a project is driven by a single vendor, TSC 
should take one or more of the following actions:
- Appreciate that company's investment in supporting our open source community. 
Everyone is volunteer here. We should appreciate the investment instead of 
discouraging the investment. We want more company to invest more resources in 
OPNFV.
- Encourage more contributors from other companies to this project. This is a 
hard part we need to know:
   * What is the percentage of code that is contributed by this single vendor 
v.s. others?
   * Are others code contribution intentionally blocked by this single vendor? 
Or just lack of code contribution from others?
- Investigate if there is misconduct
   * Is your code carefully reviewed by others?
   * How many code rejections did you get?
   * Are those rejection reasonable?
   * If you suspect misconduct in code review and your code is rejected 
unreasonably, please submit evidence.
- TSC may make a motion to defer this project's participation in E Release, and 
may suggest to Board to defer CVP, if majority concerns single vendor-driven.

So there are many things TSC can do - to appreciate investment, to encourage 
contribution, to investigate misconduct if evidence is provided, and to defer 
its participation in E Release, and to recommend to Board to defer CVP until 
single vendor concern is addressed.

But the last thing we want to do is to interfere with project's internal 
management, change the principle of contribution-driven, and meritocracy-based 
committer election, change the voting model, or discourage investment. Those 
are fundamental to an open source community. We cannot change the cornerstone 
of a house.

My 2 cents.
Thanks
Bin
-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor
Sent: Monday, May 01, 2017 6:39 PM
To: Dave Neary ; opnfv-tech-discuss@lists.opnfv.org; 
Tallgren, Tapio (Nokia - FI/Espoo) 
Subject: Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on 
DoveTail

Dovetail is a unique project because there can only be one CVP implementation 
and CVP will no doubt have impact on the OPNFV brand (either positively or 
negatively). Without reasonably wide involvement and representation the 
viability of the CVP program is questionable IMO. I think that the TSC should 
consider rules that strongly encourage or even enforce a composition that would 
adequately represent the community as a whole for launch of the program 

/Trevor 


-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Monday, May 01, 2017 10:40 AM
To: opnfv-tech-discuss@lists.opnfv.org; Tallgren, Tapio (Nokia - FI/Espoo) 

Subject: Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on 
DoveTail

Hi,

In light of Chris's resignation and request, I would like to propose that we 
bring our plans to evolve the project to the TSC sooner, rather than later, and 
get TSC guidance on a number of key questions related to Dovetail, which is not 
like other projects because of its relationship

[opnfv-tech-discuss] availability project meeting

2017-05-01 Thread Fu Qiao

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN="Power, Damien";RSVP=TRUE:mailto:damien.po...@intel.com
ATTENDEE;CN="Mcmahon, Tony B";RSVP=TRUE:mailto:tony.b.mcma...@intel.com
ATTENDEE;CN="Aaron Smith";RSVP=TRUE:mailto:aasm...@redhat.com
ATTENDEE;CN="Tahhan, Maryam";RSVP=TRUE:mailto:maryam.tah...@intel.com
ATTENDEE;CN=greg.wai...@windriver.com;RSVP=TRUE:mailto:greg.waines@windrive
	r.com
ATTENDEE;CN="'Jolliffe, Ian'";RSVP=TRUE:mailto:ian.jolli...@windriver.com
ATTENDEE;CN="'Stefan Arntzen'";RSVP=TRUE:mailto:stefan.arnt...@huawei.com
ATTENDEE;CN="'Yue Yuan'";RSVP=TRUE:mailto:yuan@zte.com.cn
ATTENDEE;CN="'Yin Tony'";RSVP=TRUE:mailto:14_...@tongji.edu.cn
ATTENDEE;CN='juan_qiu';RSVP=TRUE:mailto:juan_...@tongji.edu.cn
ATTENDEE;CN="TECH-DISCUSS OPNFV";RSVP=TRUE:mailto:opnfv-tech-discuss@lists.
	opnfv.org
CLASS:PUBLIC
CREATED:20170502T022233Z
DESCRIPTION:Next Meeting on 13:00-14:00 UTC\, Wednesday\, Mar. 3rd\n\nhttps
	://global.gotomeeting.com/join/391235029\n\nToll free NO.\nUSA: +1 (571) 3
	17-3116\n \nMeeting ID: 391-235-029\nAgenda:\ncoordination with Barometer 
	team about the HA API\n\n
DTEND;TZID="China Standard Time":20170503T22
DTSTAMP:20170502T022233Z
DTSTART;TZID="China Standard Time":20170503T21
LAST-MODIFIED:20170502T022233Z
ORGANIZER;CN="Fu Qiao":mailto:fuq...@chinamobile.com
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=zh-cn:availability project meeting
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E00890C243032EC3D201000
	010004B9253F68713D442A8B07B718804C078
X-ALT-DESC;FMTTYPE=text/html:\n\n\n\n\n\n\n\n\nNext Meeting on 13:00-
	14:00 UTC\, Wednesday\, Mar. 3rd\n\n\n\nhttps://global.gotomeetin
	g.com/join/391235029">https://global.gotomeeting.com/join/391235029\n\n\n\n
	Toll free NO.\n\nUSA: +1 (571) 317-3116\n\n \n\nMeeting ID: 391-235-029\n\n
	Agenda:\n\ncoordination with Barome
	ter team about the HA API\n\n\n\n\n
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
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] [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

2017-05-01 Thread Wenjing Chu

I have a question that we didn’t have a chance to loop back while we were in 
the plugfest.
Did the discussion on test API’s extension on login with credentials reached a 
conclusion that can be implemented in time for CVP?
Jose, Serena, can you give an update?

Thanks.
Wenjing

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor
Sent: Friday, April 28, 2017 7:36 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [test-wg] Notes from OPNFV Plugfest meeting - 
"Testing group Euphrates collaborative work"

Status of Danube and what improved

1. landing page
- 
http://testresults.opnfv.org/reporting2/reporting/index.html
- 
http://testresults.opnfv.org/reporting2/reporting/index.html#!/landingpage/table
§ Meaning of info displayed? Test ran, test 
passed … agree for consistency … TBD

2. catalogue - diagram with roll-over
- 
http://testresults.opnfv.org/reporting2/reporting/index.html#!/select/visual
- All PTLs to review if test cases are valid and if not 
remove
- Add short description that is human readable (add API 
field)
○ Define test domain categories - start by using labels 
on test ecosystem diagram

3. Stress tests - video of presentation is available - simultaneous 
vPING which increases until system fails

4. Documentation
○ Ecosystem diagram
○ Testing guide
○ Add agenda item to TWG in June (2 sessions on how to 
improve)
○ New test projects … add to common docs
○ Developer guide - move to docs

5. Reporting status / dashboard
○ Bottlenecks TBD?

6. Bitergia
○ Morgan meeting 10th May
○ 
https://wiki.opnfv.org/display/testing/Result+alignment+for+ELK+post-processing
○ Add to TWG agenda next week to revisit

Wish list for Infra group

- One POD dedicated to long duration tests (with reservation 
mechanism)

- Per installer
○ Stable of previous release
○ Master

- OPNFV POD on demand for tester (before merging)
○ Per installer if possible
○ Infra group working on it
○ Today can fill a ticket to ask if there is a free 
resource

Micro services
- Deploy VNF
○ Retrieve image
○ Deploy
○ Prebuild image with tools - standardise on a framework
○ Take image and copy over tools - Ansible (infra doing 
this with Open Stack Ansible)
○ Catalog of roles for Ansible?
§ Ansible Galaxy is a tool for deploying 
and managing roles
□ e.g. Install TREX TG
□ Turn on live migration in Nova

- Test generator?

- Collect / display results
○ Test API and DB
○ Reuse collectd lib for VNF KPIs

- Analytics of results

- What APIs to expose to other test projects?
○ Functest
§ Deploy orchestrator VNF
§ Use Traffic gen and generate load


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

[opnfv-tech-discuss] [infra] [release] Upgrading Jenkins after Danube 2.0 Release

2017-05-01 Thread Trevor Bramwell

Hello,

A recent CVE was published for Jenkins[1] necessitating an upgrade from
2.32.1 to 2.46.2.

Given the 2.0 release is coming up shortly, I'd like to propose holding
off on the upgrade until just after 2.0 is out. Assuming there are no
delays to the release (there don't appear to be), that would mean
upgrading Jenkins either this Friday (05/05/2017) or Saturday
(05/06/2017).

We could at most push this back till next week (05/10, 05/11).

David, are you expecting any delay in the 2.0 release?

Are there any concerns about the timing of this upgrade?

Regards,
Trevor Bramwell

[1] https://jenkins.io/security/advisory/2017-04-26/


signature.asc
Description: PGP 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] [release][danube] more detailed scheduling for Danube 2.0

2017-05-01 Thread David McBride

REMINDER..

You should be completing your testing on Tuesday (tomorrow).

David

On Thu, Apr 27, 2017 at 3:06 AM, David McBride  wrote:

> Team,
>
> I took an action during the TSC call this week to provide more detailed
> scheduling for the Danube 2.0 release on Thursday, May 4.
>
> Here's my proposal:
>
>- Tuesday, May 2 - Complete formal testing
>- Wednesday, May 3 - Complete documentation / JIRA cleanup
>- Thursday, May 4 - tagging
>
>
> 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

Re: [opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

2017-05-01 Thread David McBride

For some reason the link didn't work:  CI Resource Requirements




On Mon, May 1, 2017 at 2:35 PM, David McBride 
wrote:

> I neglected one item for release planning (new for Euphrates):
>
>- Create and publish a release plan
>- Fill out the summary
>
> 
>- Add your scenarios to the scenario status page
>
>- Specify your CI requirements in the CI Resource Requirements table
>
>
> On Mon, May 1, 2017 at 8:57 AM, David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> Euphrates MS1 is Tuesday, May 2 (5 p.m. Pacific).  Please confirm that
>> your project is on the intent-to-participate
>> 
>>  list.  If your project is not listed and you are planning to
>> participate, please follow the process
>>  and
>> send mail to the TSC mailing list immediately.
>>
>> In addition, MS1 is also the deadline for release planning:
>>
>>1. Create and publish a release plan
>>2. Fill out the summary
>>
>> 
>>3. Add your scenarios to the scenario status page
>>
>>
>> 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
>



-- 
*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][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

2017-05-01 Thread David McBride

I neglected one item for release planning (new for Euphrates):

   - Create and publish a release plan
   - Fill out the summary
   
   - Add your scenarios to the scenario status page
   
   - Specify your CI requirements in the CI Resource Requirements table
   


On Mon, May 1, 2017 at 8:57 AM, David McBride 
wrote:

> Team,
>
> Euphrates MS1 is Tuesday, May 2 (5 p.m. Pacific).  Please confirm that
> your project is on the intent-to-participate
> 
>  list.  If your project is not listed and you are planning to
> participate, please follow the process
>  and
> send mail to the TSC mailing list immediately.
>
> In addition, MS1 is also the deadline for release planning:
>
>1. Create and publish a release plan
>2. Fill out the summary
>
> 
>3. Add your scenarios to the scenario status page
>
>
> 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

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

2017-05-01 Thread Wenjing Chu

I agree that getting TSC guidance in the way forward is the right next
step.

Tapio, Ray,

Can we add in the agenda tomorrow on TSC for this topic? The committers
have been discussing how to restructure the dovetail project to broaden
talent pool and represent diverse community interests, but do not have
unanimous opinion on how to approach it. The majority of us would like to
extend invitations to a group of contributors to the dovetail project, who
can then vote for a new PTL, as a normal transition to a more diverse set
of committers. Chris, who dissents on this approach, and prefers to enact a
one vote per company rule to committers. With Chris now resigned, the rest
of the committers would like TSC to give guidance on these important
questions:

1) How to handle the committer expansion process for restructuring dovetail?
2) Should Dovetail add an additional rule in committer voting?

When I joined Dovetail, my understanding is that it works on technical
aspects of CVP, policy decisions are made in C committee which has voting
restrictions per company, and TSC, which has similar rules. Pushing these
responsibilities and rules to committers, I think, puts undue burden on
developers. Important decisions that the member companies need a fair say
should be made in the C Committee (on behalf of the Board) and TSC, not
in Dovetail. And that's also how we are operating in Dovetail as far as I
can see.

Regards
Wenjing

On Mon, May 1, 2017 at 10:40 AM, Dave Neary  wrote:

> Hi,
>
> In light of Chris's resignation and request, I would like to propose
> that we bring our plans to evolve the project to the TSC sooner, rather
> than later, and get TSC guidance on a number of key questions related to
> Dovetail, which is not like other projects because of its relationship
> to the CVP:
>
> * Should we allow multiple committers from a single vendor?
> * How should we handle the expansion of the committers during the
> restructuring of the Dovetail project?
>
> I do not believe that another project has considered, as we have
> recently, an addition of many new committers to a project, nor is there
> another project so directly related to a board committee. I think it
> will be useful and necessary for us to get TSC guidance on any changes
> to the project - and with Chris stepping down, I think we should get
> this guidance before extending invitations to new committer candidates.
>
> Thanks,
> Dave.
>
> On 05/01/2017 12:11 PM, Christopher Price wrote:
> > Hi Hongbo,
> >
> >
> >
> > I will be standing down as a committer on the Dovetail project.
> >
> >
> >
> > When I established the project it was intended to reflect as fairly as
> > possible a common set of voices from all member companies that had a
> > stake in our project.
> >
> > I feel that the balance in the project is not ideal today, I certainly
> > feel that my voice counts for little and is often ignored by the
> > majority votes and I do not think I am able to provide value as a
> > committer in the current structure.
> >
> >
> >
> > I strongly urge you to approach the TSC for support in re-structuring
> > DoveTail in as meritocratic manner as possible, committers contributing
> > to the repo, with a structure that limits the votes for any single
> > commercial interest on the project.  I believe this would be in the best
> > interest of the project.
> >
> >
> >
> > Regards,
> >
> > Chris
> >
> >
> >
> > ___
> > opnfv-tech-discuss mailing list
> > opnfv-tech-discuss@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> >
>
> --
> Dave Neary - NFV/SDN Community Strategy
> Open Source and Standards, Red Hat - http://community.redhat.com
> Ph: +1-978-399-2182 / Cell: +1-978-799-3338
> ___
> 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] [dovetail] Standing down as a committer on DoveTail

2017-05-01 Thread Dave Neary

Hi,

In light of Chris's resignation and request, I would like to propose
that we bring our plans to evolve the project to the TSC sooner, rather
than later, and get TSC guidance on a number of key questions related to
Dovetail, which is not like other projects because of its relationship
to the CVP:

* Should we allow multiple committers from a single vendor?
* How should we handle the expansion of the committers during the
restructuring of the Dovetail project?

I do not believe that another project has considered, as we have
recently, an addition of many new committers to a project, nor is there
another project so directly related to a board committee. I think it
will be useful and necessary for us to get TSC guidance on any changes
to the project - and with Chris stepping down, I think we should get
this guidance before extending invitations to new committer candidates.

Thanks,
Dave.

On 05/01/2017 12:11 PM, Christopher Price wrote:
> Hi Hongbo,
> 
>  
> 
> I will be standing down as a committer on the Dovetail project.
> 
>  
> 
> When I established the project it was intended to reflect as fairly as
> possible a common set of voices from all member companies that had a
> stake in our project. 
> 
> I feel that the balance in the project is not ideal today, I certainly
> feel that my voice counts for little and is often ignored by the
> majority votes and I do not think I am able to provide value as a
> committer in the current structure.
> 
>  
> 
> I strongly urge you to approach the TSC for support in re-structuring
> DoveTail in as meritocratic manner as possible, committers contributing
> to the repo, with a structure that limits the votes for any single
> commercial interest on the project.  I believe this would be in the best
> interest of the project.
> 
>  
> 
> Regards,
> 
> Chris
> 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

2017-05-01 Thread Christopher Price

Hi Hongbo,

I will be standing down as a committer on the Dovetail project.

When I established the project it was intended to reflect as fairly as possible 
a common set of voices from all member companies that had a stake in our 
project.
I feel that the balance in the project is not ideal today, I certainly feel 
that my voice counts for little and is often ignored by the majority votes and 
I do not think I am able to provide value as a committer in the current 
structure.

I strongly urge you to approach the TSC for support in re-structuring DoveTail 
in as meritocratic manner as possible, committers contributing to the repo, 
with a structure that limits the votes for any single commercial interest on 
the project.  I believe this would be in the best interest of the project.

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

[opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

2017-05-01 Thread David McBride

Team,

Euphrates MS1 is Tuesday, May 2 (5 p.m. Pacific).  Please confirm that your
project is on the intent-to-participate

list.
If your project is not listed and you are planning to participate, please
follow the process
 and
send mail to the TSC mailing list immediately.

In addition, MS1 is also the deadline for release planning:

   1. Create and publish a release plan
   2. Fill out the summary
   
   3. Add your scenarios to the scenario status page
   

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] Updated Invitation: Parser Asia-Euro Meeting @ Weekly from 4:30am to 5:30am on Monday from Mon Jun 6, 2016 to Mon May 1 (EDT) (opnfv-tech-discuss@lists.opnfv.org)

2017-05-01 Thread zhipengh512

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Shanghai
X-LIC-LOCATION:Asia/Shanghai
BEGIN:STANDARD
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:CST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Shanghai:20160606T163000
DTEND;TZID=Asia/Shanghai:20160606T173000
RRULE:FREQ=WEEKLY;WKST=MO;UNTIL=20170501T082959Z;BYDAY=MO
DTSTAMP:20170501T084415Z
ORGANIZER;CN=Zhipeng Huang:mailto:zhipengh...@gmail.com
UID:ntbhdg0873ig1fpe10hbh7e...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Zhipeng Huang;X-NUM-GUESTS=0:mailto:zhipengh...@gmail.com
CREATED:20160606T041249Z
DESCRIPTION:Hi there\, \n\nHoward Huang is inviting you to a scheduled Zoom
  meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/
 j/334408464\n\nOr iPhone one-tap (US Toll):  14157629988\,334408464# or 164
 65687788\,334408464#\n\nOr Telephone:\nDial: +1 415 762 9988 (US Toll) 
 or +1 646 568 7788 (US Toll)\nMeeting ID: 334 408 464\nInternationa
 l numbers available: https://zoom.us/zoomconference?m=fZiAhme-PcazTbskdxXRo
 55E41dRbRhy\n\n\nView your event at https://www.google.com/calendar/event?a
 ction=VIEW=bnRiaGRnMDg3M2lnMWZwZTEwaGJoN2U5aTggb3BuZnYtdGVjaC1kaXNjdXNz
 QGxpc3RzLm9wbmZ2Lm9yZw=MjEjemhpcGVuZ2g1MTJAZ21haWwuY29tMzVlYzNiYjFmNGY0
 NDc5MjM2ZGFlOWY5ZTBiZTI0YWExYWNiNmU4MA=America/New_York=en.
LAST-MODIFIED:20170501T084415Z
LOCATION:https://zoom.us/j/334408464
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Parser Asia-Euro Meeting
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

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

[opnfv-tech-discuss] availability project meeting

Re: [opnfv-tech-discuss] [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

[opnfv-tech-discuss] [infra] [release] Upgrading Jenkins after Danube 2.0 Release

Re: [opnfv-tech-discuss] [release][danube] more detailed scheduling for Danube 2.0

Re: [opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

Re: [opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

[opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

[opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

[opnfv-tech-discuss] Updated Invitation: Parser Asia-Euro Meeting @ Weekly from 4:30am to 5:30am on Monday from Mon Jun 6, 2016 to Mon May 1 (EDT) (opnfv-tech-discuss@lists.opnfv.org)

12 matches

Site Navigation

Mail list logo

Footer information