Team,

I'm proposing that we move the date for M2/M3 to Jan 21.  This pushes
Frankfurt signoff to May 5.  We will be discussing the schedule change in
upcoming TSC and PTL meetings.  However, feel free to comment or ask
questionsl in this thread.

David

On Fri, Nov 15, 2019 at 1:22 PM Yipan Deng <[email protected]> wrote:

> Yes, we probably should have a planning session to make sure everything
> will run smoothly. I will defer your questions to Stephen Gooch from Wind
> River who is supporting the lab.
>
>
>
> Anyone from the community should own this planning meeting? Please include
> Stephen and myself in the meeting.
>
>
>
> Thanks,
>
> Yipan
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of *Brian
> Freeman
> *Sent:* Friday, November 15, 2019 11:38 AM
> *To:* [email protected]
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Yipan,
>
>
>
> Staring on Jan 6th seems like a very reasonable start date. We would plan
> for a week as you suggest just in case.
>
> I assume all the data will be preserved (cinder volumes, vm’s and stacks
> etc) ?
>
> Will we need to help gracefully shutdown things in advance ?
>
>
>
> Probably need to have a planning session on anything we can do to help
> ensure success as tenants :)
>
>
>
> David,
>
>
>
> We need to make sure that M2/M3 is after Jan 14th . Right now per
> https://wiki.onap.org/display/DW/Release+Planning%3A++Frankfurt I think
> its January 9th.
>
>
>
> Brian
>
>
>
>
>
>
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of *Yipan
> Deng
> *Sent:* Friday, November 15, 2019 2:17 PM
> *To:* [email protected]
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Hi David & TSC,
>
>
>
> For Intel/Windriver Integration Lab located at Intel campus in Oregon,
> currently we are looking at moving the physical Lab starting from Jan. 6th,
> 2020 for about a week (or shorter). During that period of time, there won’t
> be any remote access to the lab.
>
>
>
> We tentatively shooting for this window considering the New Year holiday
> impact and believed this might create the least disruption to the ONAP
> community. Please feel free to let us know if you have different opinion
> and we are open for community feedbacks on lab move window.
>
>
>
> Thanks,
>
> Yipan
>
> Intel ONAP/Akraino PM
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of *David
> McBride
> *Sent:* Friday, November 15, 2019 9:05 AM
> *To:* onap-tsc <[email protected]>
> *Subject:* Re: [onap-tsc] Lab closure clarification
>
>
>
> Who can provide detailed input about these events?
>
>
>
> For both, we need to know:
>
>    - Start date
>    - Duration
>    - Degree of confidence in timing
>    - Scope of impact
>
> David
>
>
>
> On Thu, Nov 14, 2019 at 11:06 AM Brian Freeman <[email protected]> wrote:
>
> Two different events but need to undertand the timing with the latest
> Frankfurt schedule to assess impact.
>
>
>
> Brian
>
>
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf Of *Kenny
> Paul
> *Sent:* Thursday, November 14, 2019 2:02 PM
> *To:* [email protected]
> *Subject:* [onap-tsc] Lab closure clarification
>
>
>
> From the minutes today Srini brought up the Intel lab closure in January.
>
> Brian asked a schedule question resulting from the Windriver lab closure.
>
>
>
> In this context, one in the same or 2 different events?
>
>
>
> Thanks!
>
> -kenny
>
>
>
>
>
>
> --
>
> *David McBride*
>
> Release Manager
>
> Linux Foundation Networking (LFN)
>
> Mobile: +1.805.276.8018
>
> Email/Google Talk: [email protected]
>
> IRC: dmcbride
>
> 
>
>

-- 
*David McBride*
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: [email protected]
IRC: dmcbride

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5672): https://lists.onap.org/g/onap-tsc/message/5672
Mute This Topic: https://lists.onap.org/mt/57995264/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to