Cc’ing devtools original message too as this affects devtools tooling infrastructure. On 15 Jan 2022, 17:42 +0100, Mark Newton <[email protected]>, wrote: > Dear jboss.org community, > > We have been granted an extension to the previous deadline of 14th Jan 2022 > to migrate the remaining jboss.org services out of PHX2 with the new deadline > being 31st Mar 2022. > > An email entitled 'Middleware/jboss.org project sites serving migration to > new infrastructure' was sent earlier this week on 12th Jan detailing the plan > to complete the migration of static content websites by the end of Jan. > > We're currently setting up SFTP and rsync services on OpenStack in the IAD2 > datacentre to provide continuity of the file upload service at > filemgmt.jboss.org after 31st Mar but please be aware that this service is > due to be shutdown completely at the end of 2022. As such project teams are > encouraged to look for alternative hosting providers for any static content > they wish to host before then and should take the opportunity to do so before > 31st Mar if they want to avoid any unforeseen issues with the > filemgmt.jboss.org migration. > > The migration of the Nexus server at https://repository.jboss.org/nexus has > encountered a number of issues related to provisioning storage on OpenShift > in IAD2 so we're now looking at provisioning the service using OpenStack. The > aim is still to provide continuity of the Nexus service past 31st Mar in the > medium-term with a longer-term centralised solution for managing project > artifacts still being determined. > > thanks, > > Mark > > > > > On Thu, 16 Dec 2021 at 11:08, Mark Newton <[email protected]> wrote: > > > Hi Marek, > > > > > > The aim of this migration is primarily to provide continued availability > > > of the Nexus service at repository.jboss.org but given it uses a new > > > architecture including Akamai for edge caching of content we also hope it > > > will improve performance and stability. > > > > > > Determining formal requirements for performance, uptime, stability and > > > availability is something I expect to happen once the migration is done > > > and is something I've already discussed with Mark Little. > > > > > > The teams historically involved in the development and support of Nexus > > > have now gone through two re-orgs and are now performing different > > > functions at Red Hat so this is also something that needs to be resolved > > > next year. We agree that if this system is supposed to be something you > > > must use and rely on then it needs to be addressed in the same way as > > > other systems like email, chat and workday as you point out. > > > > > > We had hoped that the new system being used to manage product artifacts > > > at maven.repository.redhat.com would also be something that could be used > > > for project artifacts as this could have addressed our concerns but that > > > wasn't the direction that the Software Production group wanted to go in. > > > > > > I hope that provides more clarity around the situation. > > > > > > Mark > > > > > > > > > > On Thu, 16 Dec 2021 at 09:38, Marek Novotny <[email protected]> wrote: > > > > > Hi MarkN, > > > > > this migration worries me more and more as our own community team > > > > > for Business Automation is waving and started to discuss (before > > > > > voting) for migration from JBoss.org repository and other places for > > > > > websites to somewhere else. Not the actual migration but the past > > > > > weeks/months stability of jboss.org repository and Maven Central > > > > > synchronizations is on sub-optimal level of service. > > > > > So my question is if such core service like Nexus instance stability > > > > > is promised to be on higher level of stability and SLA or we should > > > > > migrate to OSS Sonatype repository straightforwardly. Is there some > > > > > promise to have JBoss.org repository service better and supported > > > > > like any other internal service we must use and can rely on it. (like > > > > > for instance email, chat, workday) ? > > > > > > > > > > Dne 12/15/21 v 17:48 Mark Newton napsal(a): > > > > > > Dear jboss.org community, > > > > > > > > > > > > As some of you may already know, Red Hat is in the process of > > > > > > leaving the PHX2 data center with any remaining hardware either > > > > > > sent to eWaste or moved to another location. > > > > > > > > > > > > This impacts a number of jboss.org services hosted there so we > > > > > > would like to take this opportunity to explain what this means in > > > > > > the coming weeks and months. > > > > > > > > > > > > To provide continued availability for the Nexus server at > > > > > > repository.jboss.org we are migrating it to the new IAD2 data > > > > > > center in Washington using the new MP+ platform from IT where > > > > > > possible. We originally aimed to have completed the migration by > > > > > > the end of Wednesday 22nd Dec 2021 but given the remaining > > > > > > challenges we’ve agreed an extension to Friday 14th Jan 2022. Our > > > > > > largest concern at this point is provisioning and configuring an > > > > > > rsync service in OpenStack so that Sonatype can synchronise Maven > > > > > > artifacts from repository.jboss.org to Maven Central. > > > > > > > > > > > > If we’re not able to do this by 14th Jan 2022 along with completing > > > > > > our testing of the new infrastructure then it’s possible there > > > > > > could be some disruption to the service around this time. > > > > > > > > > > > > We’re also in the process of migrating a large number of websites > > > > > > containing static content to MP+ in IAD2 including: > > > > > > > > > > > > downloads.jboss.org > > > > > > docs.jboss.org > > > > > > developer.jboss.org > > > > > > www.jboss.org > > > > > > static.jboss.org > > > > > > <project.jboss.org> > > > > > > > > > > > > A lot of progress has been made but we still need to test the > > > > > > reading of content from the sites and provision and configure an > > > > > > SFTP service to allow uploading of content at filemgmt.jboss.org > > > > > > which is used by several project teams. > > > > > > > > > > > > Again we will try to have everything ready by Friday 14th Jan 2022 > > > > > > but given the upcoming shutdown over the end of year there may > > > > > > again be some disruption to these sites and the filemgmt.jboss.org > > > > > > service. > > > > > > > > > > > > Lastly we are migrating anonsvn.jboss.org to MP+ in IAD2 but will > > > > > > be shutting down svn.jboss.org in January as our research indicates > > > > > > that this is no longer used by Red Hat. If you know of any > > > > > > dependencies on svn.jboss.org that will be impacted by this then > > > > > > please let us know by replying to this email otherwise we’ll > > > > > > respond to any unforeseen issues if they arise in Jan. > > > > > > > > > > > > While we will perform as much testing as we can for these services > > > > > > prior to completing the migrations please listen out for any > > > > > > further emails requesting teams to perform their own tests for > > > > > > services/sites where we know they’re still active. In this way we > > > > > > hope to provide a smooth migration and allow everyone to enjoy a > > > > > > productive start to 2022. > > > > > > > > > > > > many thanks, > > > > > > > > > > > > Mark Newton > > > > > > DXP Application Development > > > > > > *formerly known as Middleware Engineering Services (MWES) > > > > > > > > > > > > Mark Eastman > > > > > > Application Services > > > > > -- > > > > > Marek Novotny > > > > > -- > > > > > > > > > > RedHat JBoss Middleware > > > > > > > > > > Red Hat Czech s.r.o. > > > > > Purkynova 111 > > > > > 612 45 Brno > > > > > > > > > -- > > > Mark Newton > > > Director, DXP Application Development > > > Red Hat > > > +44 7795 520655 > > > -- > Mark Newton > Director, DXP Application Development > Red Hat > +44 7795 520655
_______________________________________________ Devtools mailing list [email protected] https://listman.redhat.com/mailman/listinfo/devtools
