ONAP Community, As you have already known, Intel is actively working with ONAP TSC to figure out a solution to replace the current ONAP Open Lab hosted by Intel. Intel will be providing new H/W once the ONAP community hosting site can be finalized.
In the meanwhile, although we are still keeping the current Open Lab functioning, our security waiver from Intel INFOSEC will be expired this Friday 08/07/2021 and can't be extended. For Intel's best effort to support ONAP community during the transition, we need to upgrade the gateway for addressing the security concerns before the lab can continue servicing the community. To meet the INFOSEC deadline on 08/07/2021 , the upgrade needs to be done no later than Wednesday 08/04/2021. Therefore, we are here to communicate that the Intel ONAP Open Lab will be temporary offline starting from 1PM PST on Wed. 08/04/2021. We will notify the community once the upgrade & security patching is completed. Once again, as a precaution, we would still encourage the community to backup all the data that would be needed for future project activities at your earliest convenience. Best Regards, Yipan From: Deng, Yipan Sent: Friday, April 30, 2021 12:05 PM To: [email protected]; [email protected]; Kadera, Michael J <[email protected]>; Monkman, Bob <[email protected]>; [email protected]; Mishra, Sharad D <[email protected]>; [email protected]; [email protected] Cc: David McBride <[email protected]>; Gooch, Stephen <[email protected]>; [email protected]; Kenny Paul <[email protected]>; Arpit Joshipura <[email protected]>; Gadiyar, Rajesh <[email protected]> Subject: RE: [onap-tsc] ONAP and Community Lab Requirements - Intel ONAP Lab Shutdown on 4/30/2021 <Postponed> ONAP Community, We came in to the TSC call this week communicated the temporary shutdown of the Intel ONAP Lab, plus the proposal of possibly EOL of the lab. I have an AR to "provide security patching path minimizing community's impacts". The temporary shutdown of the lab for security patching plus other issues related to VPN server will take about three weeks to complete. According to the immediate feedback from Catherine in the TSC call, even a couple of weeks of downtime will also impact the community. With that in mind, while we are working with ONAP and LFN on long term plan of the integration lab, we have decided to temporarily postpone the lab shutdown for security patching which was scheduled for today 4/30/2021 until future notice. As we shared in the TSC call, the servers in the lab are old enough for potential H/W failures. As a precaution, we would still encourage the community to backup all the data that would be needed for future project activities at your earliest convenience. We will work with ONAP TSC to communicate future options, stay tuned. Best Regards, Yipan From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Yipan Deng Sent: Friday, April 23, 2021 4:13 PM To: onap-tsc <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Kadera, Michael J <[email protected]<mailto:[email protected]>>; Monkman, Bob <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Mishra, Sharad D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: David McBride <[email protected]<mailto:[email protected]>>; Gooch, Stephen <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] ONAP and Community Lab Requirements - Intel ONAP Lab Shutdown on 4/30/2021 Importance: High ONAP Community, With all the communications earlier, we are here to communicate that we will be shutting down the Intel ONAP Integration and Deployment Labs<https://wiki.onap.org/pages/viewpage.action?pageId=75300917> next Friday, Apr. 30th, 2021. This will allow Intel to address the outstanding security patching to the lab among others issues and it will take at least a couple of weeks. Kindly reminder please make sure backup all the data that would be needed for future project activities by EOD Friday, Apr. 30th, 2021. Please feel free to let us know if you need any help in this process and/or have any concerns. Best Regards, Yipan From: Kadera, Michael J <[email protected]<mailto:[email protected]>> Sent: Friday, April 2, 2021 3:56 PM To: Monkman, Bob <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; Mishra, Sharad D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Deng, Yipan <[email protected]<mailto:[email protected]>> Cc: David McBride <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>>; Gooch, Stephen <[email protected]<mailto:[email protected]>> Subject: RE: ONAP and Community Lab Requirements Hi Everyone, I would like to bring in @Deng, Yipan<mailto:[email protected]> who has returned from his sabbatical to help us in the planning and communication with the community. The proposed dates for the end of April should be OK for us to address the security patches we are targeting. We will confirm with our project team next week. Additionally, we would also like to make sure the community has targeted all required data in this lab that they will require for future project activity. We can work through with Yipan to support the communication of the shutdown and the transition/backup of any critical information. Apologies for the late reply. This was buried in my stack of emails on return from my vacation. Michael From: Monkman, Bob <[email protected]<mailto:[email protected]>> Sent: Tuesday, March 23, 2021 4:37 PM To: [email protected]<mailto:[email protected]>; Kadera, Michael J <[email protected]<mailto:[email protected]>>; Mishra, Sharad D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: David McBride <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>>; Gooch, Stephen <[email protected]<mailto:[email protected]>> Subject: RE: ONAP and Community Lab Requirements Morgan, I believe we can work with that and wait for a signal confirming from the ONAP team near the end of April for us to go off-line. Note: Michael is out this week on vacation. Michael, Sharad, Would you agree? Regards, Bob From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Sent: Tuesday, March 23, 2021 7:45 AM To: Kadera, Michael J <[email protected]<mailto:[email protected]>>; Monkman, Bob <[email protected]<mailto:[email protected]>>; Mishra, Sharad D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: David McBride <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>>; Gooch, Stephen <[email protected]<mailto:[email protected]>> Subject: RE:ONAP and Community Lab Requirements Hi are you OK with the timing (just after Honolulu ..in April..we never released the date we planned but never months after either :) ) ? Morgan ________________________________ De : RICHOMME Morgan TGI/OLN Envoyé : vendredi 12 mars 2021 19:36 À : Kadera, Michael J; Monkman, Bob; Mishra, Sharad D; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc : David McBride; [email protected]<mailto:[email protected]>; onap-tsc; Gooch, Stephen Objet : RE:ONAP and Community Lab Requirements Hi I shared the info with the community during the last PTL meeting A consensus would be to plan the operation just after the release H Sign Off is planned on the 8th of April so end of April sounds OK /Morgan ________________________________ De : Kadera, Michael J [[email protected]] Envoyé : jeudi 4 mars 2021 11:13 Obligatoire : Kadera, Michael J; RICHOMME Morgan TGI/OLN; Monkman, Bob; Mishra, Sharad D; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : ONAP and Community Lab Requirements Quand : jeudi 4 mars 2021 18:00-18:30. Où : Microsoft Teams Meeting Hi everyone, This looks like our best option this week for us to meet and discuss the plans for the ONAP community labs. Items to discuss: · ONAP lab community goals for 2021 · Community hosting options and Intel lab status · Next steps ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_NjU1Y2JlYTgtNmJmMy00OTFjLTgzZDYtMjM2MTNlOGU5ZTYy%40thread.v2/0?context=%7b%22Tid%22%3a%2246c98d88-e344-4ed4-8496-4ed7712e255d%22%2c%22Oid%22%3a%22947caa7e-d2e6-4d6d-b1d4-f93b0454c64a%22%7d> Join with a video conferencing device [email protected]<mailto:[email protected]> Video Conference ID: 114 621 047 9 Alternate VTC dialing instructions<https://conf.intel.com/teams/?conf=1146210479&ivr=teams&d=conf.intel.com&test=test_call> Or call in (audio only) +1 916-245-6934,,322721328#<tel:+19162456934,,322721328> United States, Sacramento Phone Conference ID: 322 721 328# Find a local number<https://dialin.teams.microsoft.com/d195d438-2daa-420e-b9ea-da26f9d1d6d5?id=322721328> | Reset PIN<https://mysettings.lync.com/pstnconferencing> Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=947caa7e-d2e6-4d6d-b1d4-f93b0454c64a&tenantId=46c98d88-e344-4ed4-8496-4ed7712e255d&threadId=19_meeting_NjU1Y2JlYTgtNmJmMy00OTFjLTgzZDYtMjM2MTNlOGU5ZTYy@thread.v2&messageId=0&language=en-US> ________________________________________________________________________________ _____________________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Sent: Monday, March 01, 2021 2:07 AM To: Kadera, Michael J <[email protected]<mailto:[email protected]>> Cc: Monkman, Bob <[email protected]<mailto:[email protected]>>; Mishra, Sharad D <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: RE:ONAP and Community Lab Requirements Hi sure we can plan an ad hoc meeting on the topic this week. I would suggest the following time slots: - Tuesday 4 PM UTC / 9 AM PDT - Wednesday 4 PM UTC / 9 AM PDT - Thursday 4 PM UTC / 9 AM PDT NB I added Daniel and Xin who are also supporting the community in the Windriver/Intel lab /Morgan ________________________________ De : Kadera, Michael J [[email protected]] Envoyé : mardi 23 février 2021 20:30 À : RICHOMME Morgan TGI/OLN Cc : Monkman, Bob; Mishra, Sharad D Objet : ONAP and Community Lab Requirements Hi Morgan, My team is leading the support efforts for the Intel ONAP community lab and we would like to get your input on the lab needs and hosting requirements for the community. We have a few hosting decisions to plan for the future needs and we would like to make sure the community needs are considered. More specifically, we would like to know what community labs are also available, future plans for ONAP and how the Intel lab and other community labs will coordinate to meet the needs. Would you have time to meet in the near future? Bob, Sharad and I are all on the west coast of the US so a time near the end of your day would probably work best assuming you are in or near the Paris office. Could you provide a few suggestions? Thanks, Michael Kadera Intel Corporation Intel Architecture, Graphics and Software | System Software Engineering _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8021): https://lists.onap.org/g/onap-tsc/message/8021 Mute This Topic: https://lists.onap.org/mt/84643615/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
