Given where we are in the release cycle, I've asked IT to hang off on this pending input form the TSC. This down time has been requested as the result of a call this morning discussing extremely long durations to pull docker images. The expectation is this will improve that issue.
Basically, I'm looking for a thumbs-up from the TSC Members before proceeding with scheduling down time. Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected], 510.766.5945 San Francisco Bay Area, Pacific Time Zone From: <[email protected]> on behalf of Jeremy Phelps <[email protected]> Date: Tuesday, April 17, 2018 at 4:15 PM To: <[email protected]> Subject: Re: [Onap-lf-announce] Jenkins and Nexus downtime Date correction in the year: Start Date/Time: - 8:30 am Pacific April 18, 2018 - https://www.worldtimebuddy.com/?qm=1&lid=8,100,4641239&h=8&date=2018-4-18&sln=8.5-10 Systems affected: - jenkins.onap.org - nexus3.onap.org Why: - LF IT is migrating the nexus3 system to a new node Expected Downtime: - 1.5 hours On Tue, Apr 17, 2018 at 6:10 PM, Jeremy Phelps <[email protected]> wrote: Start Date/Time: - 8:30 am Pacific April 18, 2019 - https://www.worldtimebuddy.com/?qm=1&lid=8,100,4641239&h=8&date=2018-4-18&sln=8.5-10 Systems affected: - jenkins.onap.org - nexus3.onap.org Why: - LF IT is migrating the nexus3 system to a new node Expected Downtime: - 1.5 hours _______________________________________________ Onap-lf-announce mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-lf-announce
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
