Re: [opnfv-tech-discuss] [release][euphrates] Milestone 5 / July 28

2017-07-28 Thread David McBride 
Team,

So far, I've heard from less than half of the projects about MS5.  If you
are participating in the Euphrates release, please report your status to me
ASAP.  See my previous email for details.  Thanks.

David

On Thu, Jul 27, 2017 at 12:32 PM, David McBride <
dmcbr...@linuxfoundation.org> wrote:

> Team,
>
> Tomorrow (Fri, July 28) is MS5.  If you are a feature project that depends
> on a scenario for deployment, *please send me a link to a Jenkins job in
> OPNFV CI for each scenario* with which you are integrating your feature.
>
> For all other projects that are developing code but are NOT dependent on
> scenario integration for deployment, recall that MS5 marks the end of
> feature development.  All development effort for the remainder of the
> release should be dedicated to test case implementation or bug fixes. * Please
> respond to this email and acknowledge that you have completed your feature
> development.*
>
> If you are unable to complete scenario integration, or complete feature
> development, by Friday, please let me know whether you intend to submit a 
> milestone
> exception request
> ,
> or withdraw from the release. * If I haven't heard from you by Aug 4, I
> will assume that you are withdrawing from the release. *
>
> Let me know if you have questions.
>
> David
>
> On Mon, Jul 24, 2017 at 9:50 AM, David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Reminder...
>>
>> On Thu, Jul 20, 2017 at 12:16 PM, David McBride <
>> dmcbr...@linuxfoundation.org> wrote:
>>
>>> Team,
>>>
>>> Milestone 5 is just over one week away, on July 28.  Here's a summary of
>>> the requirements:
>>>
>>>- Completion of scenario integration for projects that rely on
>>>scenarios for deployment.  The scenario deployment must be represented 
>>> in a
>>>Jenkins job running on OPNFV CI.
>>>- Feature freeze for all projects.  This means that all planned
>>>features have been implemented and the code has been committed to your
>>>project repo.  From this point forward, all coding should be related to
>>>test case implementation or bug fixing.
>>>
>>> As you know, we implemented a milestone exception process earlier this
>>> year.  So, if you are unable to meet the requirements of this milestone,
>>> you will have the option of submitting a milestone exception request, or
>>> withdrawing from the release.  If you already know that you will not be
>>> able to meet the requirements, please contact me ASAP and let me know
>>> whether you plan to submit a milestone exception request.
>>>
>>> Let me know if you have any questions.
>>>
>>> David
>>>
>>> --
>>> *David McBride*
>>> Release Manager, OPNFV
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> Skype: davidjmcbride1
>>> IRC: dmcbride
>>>
>>
>>
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
>
> --
> *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] Milestone 5 / July 28

2017-07-27 Thread Tim Rozet 
Hi David,
For Apex you can find our baremetal daily scenarios here:
https://build.opnfv.org/ci/view/apex/job/apex-daily-master/56/

Note we refactored the jobs due to the issues in D3.0.  Click each build#11 
link to see the sub jobs (deploy and test) of each scenario job.  The 
baremetal-deploy-master job will show blue for each scenario indicating they 
deploy.

Also note, we have patch combined with a jenkins reboot this coming weekend 
which will allow us to make the status of each scenario job yellow (instead of 
red) if the deployment passed, but the tests failed.  If deployment fails the 
scenario job will show red.  That will make it easier to tell just from looking 
at the daily job if deployments are passing for each scenario.

The only scenarios not there which are *owned* by Apex are:
os-odl-ovs_dpdk-ha
os-odl-ovs_dpdk-noha

os-odl-k8s_coe-noha
os-odl-k8s_coe-ha

The ovs_dpdk scenarios I requested an exception for.  For k8s_coe, we will 
defer those 5.1.

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "David McBride" <dmcbr...@linuxfoundation.org>
To: "TECH-DISCUSS OPNFV" <opnfv-tech-discuss@lists.opnfv.org>, 
"opnfv-project-leads" <opnfv-project-le...@lists.opnfv.org>
Sent: Thursday, July 27, 2017 3:32:42 PM
Subject: Re: [opnfv-tech-discuss] [release][euphrates] Milestone 5 / July 28

Team, 

Tomorrow (Fri, July 28) is MS5. If you are a feature project that depends on a 
scenario for deployment, please send me a link to a Jenkins job in OPNFV CI for 
each scenario with which you are integrating your feature. 

For all other projects that are developing code but are NOT dependent on 
scenario integration for deployment, recall that MS5 marks the end of feature 
development. All development effort for the remainder of the release should be 
dedicated to test case implementation or bug fixes. Please respond to this 
email and acknowledge that you have completed your feature development. 

If you are unable to complete scenario integration, or complete feature 
development, by Friday, please let me know whether you intend to submit a 
milestone exception request , or withdraw from the release. If I haven't heard 
from you by Aug 4, I will assume that you are withdrawing from the release. 

Let me know if you have questions. 

David 

On Mon, Jul 24, 2017 at 9:50 AM, David McBride < dmcbr...@linuxfoundation.org > 
wrote: 



Reminder... 

On Thu, Jul 20, 2017 at 12:16 PM, David McBride < dmcbr...@linuxfoundation.org 
> wrote: 



Team, 

Milestone 5 is just over one week away, on July 28. Here's a summary of the 
requirements: 


* Completion of scenario integration for projects that rely on scenarios 
for deployment. The scenario deployment must be represented in a Jenkins job 
running on OPNFV CI. 
* Feature freeze for all projects. This means that all planned features 
have been implemented and the code has been committed to your project repo. 
From this point forward, all coding should be related to test case 
implementation or bug fixing. 

As you know, we implemented a milestone exception process earlier this year. 
So, if you are unable to meet the requirements of this milestone, you will have 
the option of submitting a milestone exception request, or withdrawing from the 
release. If you already know that you will not be able to meet the 
requirements, please contact me ASAP and let me know whether you plan to submit 
a milestone exception request. 

Let me know if you have any questions. 

David 

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



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



-- 
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][euphrates] Milestone 5 / July 28

2017-07-27 Thread David McBride 
Team,

Tomorrow (Fri, July 28) is MS5.  If you are a feature project that depends
on a scenario for deployment, *please send me a link to a Jenkins job in
OPNFV CI for each scenario* with which you are integrating your feature.

For all other projects that are developing code but are NOT dependent on
scenario integration for deployment, recall that MS5 marks the end of
feature development.  All development effort for the remainder of the
release should be dedicated to test case implementation or bug fixes. * Please
respond to this email and acknowledge that you have completed your feature
development.*

If you are unable to complete scenario integration, or complete feature
development, by Friday, please let me know whether you intend to
submit a milestone
exception request
,
or withdraw from the release. * If I haven't heard from you by Aug 4, I
will assume that you are withdrawing from the release. *

Let me know if you have questions.

David

On Mon, Jul 24, 2017 at 9:50 AM, David McBride  wrote:

> Reminder...
>
> On Thu, Jul 20, 2017 at 12:16 PM, David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> Milestone 5 is just over one week away, on July 28.  Here's a summary of
>> the requirements:
>>
>>- Completion of scenario integration for projects that rely on
>>scenarios for deployment.  The scenario deployment must be represented in 
>> a
>>Jenkins job running on OPNFV CI.
>>- Feature freeze for all projects.  This means that all planned
>>features have been implemented and the code has been committed to your
>>project repo.  From this point forward, all coding should be related to
>>test case implementation or bug fixing.
>>
>> As you know, we implemented a milestone exception process earlier this
>> year.  So, if you are unable to meet the requirements of this milestone,
>> you will have the option of submitting a milestone exception request, or
>> withdrawing from the release.  If you already know that you will not be
>> able to meet the requirements, please contact me ASAP and let me know
>> whether you plan to submit a milestone exception request.
>>
>> Let me know if you have any questions.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



-- 
*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] Milestone 5 / July 28

2017-07-24 Thread David McBride 
Reminder...

On Thu, Jul 20, 2017 at 12:16 PM, David McBride <
dmcbr...@linuxfoundation.org> wrote:

> Team,
>
> Milestone 5 is just over one week away, on July 28.  Here's a summary of
> the requirements:
>
>- Completion of scenario integration for projects that rely on
>scenarios for deployment.  The scenario deployment must be represented in a
>Jenkins job running on OPNFV CI.
>- Feature freeze for all projects.  This means that all planned
>features have been implemented and the code has been committed to your
>project repo.  From this point forward, all coding should be related to
>test case implementation or bug fixing.
>
> As you know, we implemented a milestone exception process earlier this
> year.  So, if you are unable to meet the requirements of this milestone,
> you will have the option of submitting a milestone exception request, or
> withdrawing from the release.  If you already know that you will not be
> able to meet the requirements, please contact me ASAP and let me know
> whether you plan to submit a milestone exception request.
>
> Let me know if you have any questions.
>
> David
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



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