From manderse at redhat.com Sun Jan 16 18:01:06 2022 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sun, 16 Jan 2022 19:01:06 +0100 Subject: [Devtools] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: Message-ID: <47abd573-885b-44a1-92da-04247bf2450c@Spark> Cc?ing devtools as this affects devtools tooling infrastructure. On 15 Jan 2022, 17:42 +0100, Mark Newton , 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 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 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 > > > > > > > > > > > > > > > > > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Sun Jan 16 18:01:43 2022 From: manderse at redhat.com (Max Rydahl Andersen) Date: Sun, 16 Jan 2022 19:01:43 +0100 Subject: [Devtools] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: Message-ID: <8bb65b4f-371f-480b-ae33-48bca89da87f@Spark> Cc?ing devtools original message too as this affects devtools tooling infrastructure. On 15 Jan 2022, 17:42 +0100, Mark Newton , 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 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 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 > > > > > > > > > > > > > > > > > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Thu Jan 20 09:20:39 2022 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 20 Jan 2022 10:20:39 +0100 Subject: [Devtools] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> Message-ID: <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> Hi, I reached out to the Marks (Newton, Eastman and Little) and are working on getting some clarifications in place. For now just await an update. /max > I don't understand why a structure like RH cannot offer such a service > for > the amount of projects requiring such a service. > > On Wed, Jan 19, 2022 at 8:08 PM Max Rydahl Andersen > > wrote: > >> Any updates /feedback here ? >> >> Are we really saying that it is cheaper to tell countless projects to >> migrate data to random places, have engineering staff setup and >> update >> alternative ci pipelines than maintain a static backed storage ? >> >> Any docs on how to retain urls etc. so we don't break users and >> customers ? >> >> /max >> >> As i wrote in my first response to this thread i was worrying about >> it, >> but now with the latest Mark Newton's msg it is even worse. So we are >> encouraged to migrate websites completely or active access for >> uploading to >> it is discontinued? >> >> I think that change would deserve a special email with different >> topic as >> it changes what is bringing to us as original msg was nothing changes >> for >> projects only the datacenter. >> Dne 1/16/22 v 18:58 Max Rydahl Andersen napsal(a): >> >> On 15 Jan 2022, 17:42 +0100, mlittle-all at redhat.com, wrote: >> >> >> 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. >> >> >> What does this mean exactly ? That we can?t upload new content via >> file >> Mgmt or that the data goes away ? >> >> The latter I can?t see as an option as that is where basically all >> intelli, vscode and eclipse plugins been served out of so it will >> break >> tons of active projects. >> >> In any case what is the plans to make sure urls used in lots of our >> tools >> and ci processes can continue to work after filemgt no longer can be >> used >> for upload ? >> >> -- >> Marek Novotny >> -- >> >> RedHat JBoss Middleware >> >> Red Hat Czech s.r.o. >> Purkynova 111 >> 612 45 Brno >> >> >> /max >> https://xam.dk/about >> > > > -- > > Jeff Maury > > Manager, DevTools > > Red Hat EMEA > > jmaury at redhat.com > @RedHat Red Hat > Red Hat > > > /max https://xam.dk/about -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbouchet at redhat.com Thu Jan 20 09:26:56 2022 From: sbouchet at redhat.com (Stephane Bouchet) Date: Thu, 20 Jan 2022 10:26:56 +0100 Subject: [Devtools] [devtools-team] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> Message-ID: Great, thank you max for this. I'm looking forward to have some clarification for the future releases of JbossTools/Codeready studio as we are heavily using Rsync on filemgmt.jboss.org to make our release available to the public. Regards, Le jeu. 20 janv. 2022 ? 10:23, Max Rydahl Andersen a ?crit : > Hi, > > I reached out to the Marks (Newton, Eastman and Little) and are working on > getting some clarifications in place. For now just await an update. > > /max > > I don't understand why a structure like RH cannot offer such a service for > the amount of projects requiring such a service. > > On Wed, Jan 19, 2022 at 8:08 PM Max Rydahl Andersen > wrote: > >> Any updates /feedback here ? >> >> Are we really saying that it is cheaper to tell countless projects to >> migrate data to random places, have engineering staff setup and update >> alternative ci pipelines than maintain a static backed storage ? >> >> Any docs on how to retain urls etc. so we don't break users and customers >> ? >> >> /max >> >> As i wrote in my first response to this thread i was worrying about it, >> but now with the latest Mark Newton's msg it is even worse. So we are >> encouraged to migrate websites completely or active access for uploading to >> it is discontinued? >> >> I think that change would deserve a special email with different topic as >> it changes what is bringing to us as original msg was nothing changes for >> projects only the datacenter. >> Dne 1/16/22 v 18:58 Max Rydahl Andersen napsal(a): >> >> On 15 Jan 2022, 17:42 +0100, mlittle-all at redhat.com, wrote: >> >> >> 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. >> >> >> What does this mean exactly ? That we can?t upload new content via file >> Mgmt or that the data goes away ? >> >> The latter I can?t see as an option as that is where basically all >> intelli, vscode and eclipse plugins been served out of so it will break >> tons of active projects. >> >> In any case what is the plans to make sure urls used in lots of our tools >> and ci processes can continue to work after filemgt no longer can be used >> for upload ? >> >> -- >> Marek Novotny >> -- >> >> RedHat JBoss Middleware >> >> Red Hat Czech s.r.o. >> Purkynova 111 >> 612 45 Brno >> >> >> /max >> https://xam.dk/about >> > > > -- > > Jeff Maury > > Manager, DevTools > > Red Hat EMEA > > jmaury at redhat.com > @RedHat Red Hat > Red Hat > > > > > > /max > https://xam.dk/about > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://listman.redhat.com/mailman/listinfo/devtools > -- St?phane Bouchet Senior Software Engineer, R&D Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From odockal at redhat.com Thu Jan 20 11:51:49 2022 From: odockal at redhat.com (Ondrej Dockal) Date: Thu, 20 Jan 2022 12:51:49 +0100 Subject: [Devtools] [devtools-team] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> Message-ID: Again, thanks Max for that! I have created a jira to have a visible place for JBT/Studio efforts to keep track of this. Adding Fuse tooling team to the loop. Ondrej [1]: https://issues.redhat.com/browse/JBIDE-28286 On Thu, Jan 20, 2022 at 10:31 AM Stephane Bouchet wrote: > Great, thank you max for this. > I'm looking forward to have some clarification for the future releases of > JbossTools/Codeready studio as we are heavily using Rsync on > filemgmt.jboss.org to make our release available to the public. > > Regards, > > Le jeu. 20 janv. 2022 ? 10:23, Max Rydahl Andersen > a ?crit : > >> Hi, >> >> I reached out to the Marks (Newton, Eastman and Little) and are working >> on >> getting some clarifications in place. For now just await an update. >> >> /max >> >> I don't understand why a structure like RH cannot offer such a service >> for the amount of projects requiring such a service. >> >> On Wed, Jan 19, 2022 at 8:08 PM Max Rydahl Andersen >> wrote: >> >>> Any updates /feedback here ? >>> >>> Are we really saying that it is cheaper to tell countless projects to >>> migrate data to random places, have engineering staff setup and update >>> alternative ci pipelines than maintain a static backed storage ? >>> >>> Any docs on how to retain urls etc. so we don't break users and >>> customers ? >>> >>> /max >>> >>> As i wrote in my first response to this thread i was worrying about it, >>> but now with the latest Mark Newton's msg it is even worse. So we are >>> encouraged to migrate websites completely or active access for uploading to >>> it is discontinued? >>> >>> I think that change would deserve a special email with different topic >>> as it changes what is bringing to us as original msg was nothing changes >>> for projects only the datacenter. >>> Dne 1/16/22 v 18:58 Max Rydahl Andersen napsal(a): >>> >>> On 15 Jan 2022, 17:42 +0100, mlittle-all at redhat.com, wrote: >>> >>> >>> 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. >>> >>> >>> What does this mean exactly ? That we can?t upload new content via file >>> Mgmt or that the data goes away ? >>> >>> The latter I can?t see as an option as that is where basically all >>> intelli, vscode and eclipse plugins been served out of so it will break >>> tons of active projects. >>> >>> In any case what is the plans to make sure urls used in lots of our >>> tools and ci processes can continue to work after filemgt no longer can be >>> used for upload ? >>> >>> -- >>> Marek Novotny >>> -- >>> >>> RedHat JBoss Middleware >>> >>> Red Hat Czech s.r.o. >>> Purkynova 111 >>> 612 45 Brno >>> >>> >>> /max >>> https://xam.dk/about >>> >> >> >> -- >> >> Jeff Maury >> >> Manager, DevTools >> >> Red Hat EMEA >> >> jmaury at redhat.com >> @RedHat Red Hat >> Red Hat >> >> >> >> >> >> /max >> https://xam.dk/about >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://listman.redhat.com/mailman/listinfo/devtools >> > > > -- > > St?phane Bouchet > > Senior Software Engineer, R&D > > Red Hat > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://listman.redhat.com/mailman/listinfo/devtools > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nboldt at redhat.com Thu Jan 20 18:17:05 2022 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 20 Jan 2022 14:17:05 -0400 Subject: [Devtools] [devtools-team] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> Message-ID: Looks like CodeReady Workspaces & Eclipse Che will also have to investigate how and where to move our hoted vsix plugin content. https://issues.redhat.com/browse/CRW-2662 Is Mar 31 2022 a hard drop-dead date? Or is there any flexibility in that timeline? Nick On Thu, Jan 20, 2022 at 7:53 AM Ondrej Dockal wrote: > Again, thanks Max for that! > > I have created a jira to have a visible place for JBT/Studio efforts to > keep track of this. > > Adding Fuse tooling team to the loop. > > Ondrej > > [1]: https://issues.redhat.com/browse/JBIDE-28286 > > On Thu, Jan 20, 2022 at 10:31 AM Stephane Bouchet > wrote: > >> Great, thank you max for this. >> I'm looking forward to have some clarification for the future releases of >> JbossTools/Codeready studio as we are heavily using Rsync on >> filemgmt.jboss.org to make our release available to the public. >> >> Regards, >> >> Le jeu. 20 janv. 2022 ? 10:23, Max Rydahl Andersen >> a ?crit : >> >>> Hi, >>> >>> I reached out to the Marks (Newton, Eastman and Little) and are working >>> on >>> getting some clarifications in place. For now just await an update. >>> >>> /max >>> >>> I don't understand why a structure like RH cannot offer such a service >>> for the amount of projects requiring such a service. >>> >>> On Wed, Jan 19, 2022 at 8:08 PM Max Rydahl Andersen >>> wrote: >>> >>>> Any updates /feedback here ? >>>> >>>> Are we really saying that it is cheaper to tell countless projects to >>>> migrate data to random places, have engineering staff setup and update >>>> alternative ci pipelines than maintain a static backed storage ? >>>> >>>> Any docs on how to retain urls etc. so we don't break users and >>>> customers ? >>>> >>>> /max >>>> >>>> As i wrote in my first response to this thread i was worrying about it, >>>> but now with the latest Mark Newton's msg it is even worse. So we are >>>> encouraged to migrate websites completely or active access for uploading to >>>> it is discontinued? >>>> >>>> I think that change would deserve a special email with different topic >>>> as it changes what is bringing to us as original msg was nothing changes >>>> for projects only the datacenter. >>>> Dne 1/16/22 v 18:58 Max Rydahl Andersen napsal(a): >>>> >>>> On 15 Jan 2022, 17:42 +0100, mlittle-all at redhat.com, wrote: >>>> >>>> >>>> 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. >>>> >>>> >>>> What does this mean exactly ? That we can?t upload new content via file >>>> Mgmt or that the data goes away ? >>>> >>>> The latter I can?t see as an option as that is where basically all >>>> intelli, vscode and eclipse plugins been served out of so it will break >>>> tons of active projects. >>>> >>>> In any case what is the plans to make sure urls used in lots of our >>>> tools and ci processes can continue to work after filemgt no longer can be >>>> used for upload ? >>>> >>>> -- >>>> Marek Novotny >>>> -- >>>> >>>> RedHat JBoss Middleware >>>> >>>> Red Hat Czech s.r.o. >>>> Purkynova 111 >>>> 612 45 Brno >>>> >>>> >>>> /max >>>> https://xam.dk/about >>>> >>> >>> >>> -- >>> >>> Jeff Maury >>> >>> Manager, DevTools >>> >>> Red Hat EMEA >>> >>> jmaury at redhat.com >>> @RedHat Red Hat >>> Red Hat >>> >>> >>> >>> >>> >>> /max >>> https://xam.dk/about >>> _______________________________________________ >>> Devtools mailing list >>> Devtools at redhat.com >>> https://listman.redhat.com/mailman/listinfo/devtools >>> >> >> >> -- >> >> St?phane Bouchet >> >> Senior Software Engineer, R&D >> >> Red Hat >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://listman.redhat.com/mailman/listinfo/devtools >> > -- Nick Boldt (he/him/his) Principal Software Engineer, RHCSA Productization Lead :: CodeReady Workspaces IM: @nickboldt / @nboldt / https://divbyzero.neocities.org TRIED. TESTED. TRUSTED. @ @redhatnews Red Hat ?The Only Thing That Is Constant Is Change? - Heraclitus -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Thu Jan 20 19:00:57 2022 From: manderse at redhat.com (Max Rydahl Andersen) Date: Thu, 20 Jan 2022 20:00:57 +0100 Subject: [Devtools] Fwd: Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <1c2e0692-da0f-2ec0-6966-f92058e3c758@redhat.com> <291bd428-75d9-c7b8-c2c6-f448656b671a@redhat.com> Message-ID: <1886bf9e-bef6-4814-973b-aea5386f5dcc@Spark> More updates. Please See spreadsheet and add the sites You want us to be aware about and what issues/concerns You have. ---------- Forwarded message ---------- From: Mark Newton Date: 20 Jan 2022, 16:48 +0100 To: mlittle-all at redhat.com Cc: Core, The Subject: Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown > Hi Andrew, > > Apologies for the delay in responding. A number of similar concerns have been raised by other people in this thread and elsewhere so we wanted to make sure we created one response that addressed all of them. > > > 1. > You?re correct that the current work in progress is simply a relocation of the SFTP and rsync services that constitute filemgmt.jboss.org to another place. That was going to be OpenShift in IAD2 but due to issues provisioning the services there we?re now using OpenStack in IAD2. I?ll address accessing the content at URLs serviced by filemgmt.jboss.org below. > > > > 2. > As filemgmt.jboss.org is used to upload content and all the other domains are used to access/read content they are being treated differently. > a. > Some domains such as developer.jboss.org which used to be served by a Jive server (forums, wiki and blogs) have been archived in the sense that the webpages are now flat HTML as we?ve decommissioned Jive. The Confluence server at docs.jboss.org/author (used to create project documentation) is another example of this. > b. > Other domains like doc.jboss.org (without the /author path) and issues.jboss.org have been moved to spaces.redhat.com and issues.redhat.com respectively as the Confluence and JIRA servers behind them are now owned by the Portfolio Lifecycle Management team in Engineering. Due to an error redirecting traffic from docs.jboss.org to spaces.redhat.com that didn?t account for subpaths, some of the project documentation available at docs.jboss.org/ was temporarily unavailable (as it was redirected to spaces.redhat.com) but we?ve since fixed this. > c. > www.jboss.org is now owned by MW Engineering who use GitHub to author content instead of the Magnolia CMS which has been shutdown. > d. > static.jboss.org and .jboss.org (along with some .org domains) use Apache httpd servers which are being relocated from virtualized machines in PHX2 to OpenShift in IAD2. > > > > 3. > Content made available from the URLs mentioned in item 2 above will continue to be be accessible after Dec 2022 but without further action those domains will be considered archived in the sense that you will no longer be able to upload content there (as filemgmt.jboss.org is currently scheduled to be shutdown at the end of Dec 2022). > > > > 4. > What this means for projects like Byteman that have content at byteman.jboss.org is that they would need to move to another hosting provider like GitHub Pages ***by the end of Dec 2022*** if they wanted to continue uploading content to their domain. I understand we can move subdomains like byteman.jboss.org to GitHub while keeping other jboss.org subdomains hosted by Red Hat. As such you wouldn?t have to *personally* host your own web/file service but you would be expected to perform the migration along with any necessary maintenance after that. We will provide some instructions in Confluence on how to move to GitHub Pages as we?ve already done this ourselves for some legacy projects to reduce the amount of Akamai configuration needed for the overall jboss.org migration out of PHX2. > > > Max Andersen has also raised concerns about the impact of these changes to DevTools as they use downloads.jboss.org to serve tooling binaries which are considered pseudo-products and therefore treated differently from projects. This argument may impact whether or not we keep the content upload service at filemgmt.jboss.org living beyond Dec 2022 but the most appropriate solution still needs to be determined and project teams are still encouraged to move their project sites to GitHub Pages if possible as that service is actively developed to provide modern project site hosting capabilities. > > Ultimately we?re trying to establish the most appropriate balance of product/project concerns in terms of what Red Hat should be providing services for. Given all the recent reorganizations across the company to focus on capturing the Open Hybrid Cloud market the hosting of community projects is not something that is being considered part of our core business. As such we should look to externalize it if possible using companies that do treat it as their core business such as GitHub. > > It?s less clear cut to say that services such as Nexus and downloads for dev tooling, that are used in the overall software productization process or in support of our products, shouldn?t be provided by Red Hat which is why we?re having conversations with the related teams to determine the most appropriate outcomes. > > Max has started the following spreadsheet for MW Engineering to co-ordinate what the plans are for various jboss.org domains following the PHX2 shutdown so there?s one place to go: > > ?https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 - *.jboss.org transition > > I hope this helps to clear things up a bit. > > Mark > > > > > On Thu, 20 Jan 2022 at 11:42, Andrew Dinn wrote: > > > Hi Mark (Newton), > > > > > > Is that just the sound of tumbleweeds rolling down main street on an > > > east wind that I can hear? Or did I miss a response to the questions below? > > > > > > I really need to know the answers to these questions quite soon, > > > especially question 4, and I am sure I am not alone in that regard. > > > > > > If projects are really being expected to find somewhere to store > > > web/download content then that's going to require time to plan, not > > > simply to provision the relevant services but also to deal with the > > > disruption (both to project processes and to users) that may arise from > > > having existing content relocated. > > > > > > Can we please have some clarification and advice here? > > > > > > regards, > > > > > > > > > Andrew Dinn > > > ----------- > > > > > > On 17/01/2022 11:06, Andrew Dinn wrote: > > > > Can you be more explicit about a few points made in this post: > > > > > > > > 1) Is the current work in progress simply a relocation of > > > > filemgmt.jboss.org to a virtualized server running inside OpenShift in > > > > IAD2? Or does it actually entail disabling access to content addressed > > > > with URLs based on the name filemgmt.jboss.org before or by 31 March? > > > > > > > > 2) Is the story regarding current WIP for docs.jboss.org, > > > > developer.jboss.org, www.jboss.org,? static.jboss.org, and > > > > project.jboss.org the same as for filemgmt.jboss.org If not then what is > > > > the difference? > > > > > > > > 3) Are you saying that all content made available via URLs based on the > > > > above list of names will need to be relocated to servers provided by the > > > > relevant projects before end of Dec 2022? > > > > > > > > 4) What does this mean for projects like Byteman that essentially belong > > > > within JBoss/Red Hat? Am I expected *personally* to host my own web/file > > > > service to serve Byteman related content? Am I also expected to provide > > > > my own domain and/or relocate the content from byteman.jboss.org Or is > > > > there some common Red Hat server resource I can use which keeps the > > > > content in the jboss domain? > > > > > > -- > Mark Newton > Director, Customer Digital Experience > Red Hat > +44 7795 520655 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nboldt at redhat.com Thu Jan 20 21:13:45 2022 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 20 Jan 2022 17:13:45 -0400 Subject: [Devtools] [devtools-team] Fwd: Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: <1886bf9e-bef6-4814-973b-aea5386f5dcc@Spark> References: <1c2e0692-da0f-2ec0-6966-f92058e3c758@redhat.com> <291bd428-75d9-c7b8-c2c6-f448656b671a@redhat.com> <1886bf9e-bef6-4814-973b-aea5386f5dcc@Spark> Message-ID: Thanks, CodeReady Workspaces & Eclipse Che concerns added to https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 If PSSC proposes a new place to host these files that's safe enough for supply chain security concerns, we can move our content to a new host. Has anyone from PSSC been looped in on this? Nick On Thu, Jan 20, 2022 at 3:03 PM Max Rydahl Andersen wrote: > More updates. > > Please See spreadsheet and add the sites You want us to be aware about and > what issues/concerns You have. > ---------- Forwarded message ---------- > *From:* Mark Newton > *Date:* 20 Jan 2022, 16:48 +0100 > *To:* mlittle-all at redhat.com > *Cc:* Core, The > *Subject:* Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 > Shutdown > > Hi Andrew, > > Apologies for the delay in responding. A number of similar concerns have > been raised by other people in this thread and elsewhere so we wanted to > make sure we created one response that addressed all of them. > > > 1. > > You?re correct that the current work in progress is simply a > relocation of the SFTP and rsync services that constitute > filemgmt.jboss.org to another place. That was going to be OpenShift in > IAD2 but due to issues provisioning the services there we?re now using > OpenStack in IAD2. I?ll address accessing the content at URLs serviced by > filemgmt.jboss.org below. > > > > 1. > > As filemgmt.jboss.org is used to upload content and all the other > domains are used to access/read content they are being treated differently. > 1. > > Some domains such as developer.jboss.org which used to be served by > a Jive server (forums, wiki and blogs) have been archived in the sense that > the webpages are now flat HTML as we?ve decommissioned Jive. The Confluence > server at docs.jboss.org/author (used to create project > documentation) is another example of this. > 2. > > Other domains like doc.jboss.org (without the /author path) and > issues.jboss.org have been moved to spaces.redhat.com and > issues.redhat.com respectively as the Confluence and JIRA servers > behind them are now owned by the Portfolio Lifecycle Management team in > Engineering. Due to an error redirecting traffic from docs.jboss.org > to spaces.redhat.com that didn?t account for subpaths, some of the > project documentation available at docs.jboss.org/ was > temporarily unavailable (as it was redirected to spaces.redhat.com) > but we?ve since fixed this. > 3. > > www.jboss.org is now owned by MW Engineering who use GitHub to > author content instead of the Magnolia CMS which has been shutdown. > 4. > > static.jboss.org and .jboss.org (along with some > .org domains) use Apache httpd servers which are being relocated > from virtualized machines in PHX2 to OpenShift in IAD2. > > > > 1. > > Content made available from the URLs mentioned in item 2 above will > continue to be be accessible after Dec 2022 but without further action > those domains will be considered archived in the sense that you will no > longer be able to upload content there (as filemgmt.jboss.org is > currently scheduled to be shutdown at the end of Dec 2022). > > > > 1. > > What this means for projects like Byteman that have content at > byteman.jboss.org is that they would need to move to another hosting > provider like GitHub Pages ***by the end of Dec 2022*** if they wanted to > continue uploading content to their domain. I understand we can move > subdomains like byteman.jboss.org to GitHub while keeping other > jboss.org subdomains hosted by Red Hat. As such you wouldn?t have to > *personally* host your own web/file service but you would be expected to > perform the migration along with any necessary maintenance after that. We > will provide some instructions in Confluence on how to move to GitHub Pages > as we?ve already done this ourselves for some legacy projects to reduce the > amount of Akamai configuration needed for the overall jboss.org > migration out of PHX2. > > > Max Andersen has also raised concerns about the impact of these changes to > DevTools as they use downloads.jboss.org to serve tooling binaries which > are considered pseudo-products and therefore treated differently from > projects. This argument may impact whether or not we keep the content > upload service at filemgmt.jboss.org living beyond Dec 2022 but the most > appropriate solution still needs to be determined and project teams are > still encouraged to move their project sites to GitHub Pages if possible as > that service is actively developed to provide modern project site hosting > capabilities. > > Ultimately we?re trying to establish the most appropriate balance of > product/project concerns in terms of what Red Hat should be providing > services for. Given all the recent reorganizations across the company to > focus on capturing the Open Hybrid Cloud market the hosting of community > projects is not something that is being considered part of our core > business. As such we should look to externalize it if possible using > companies that do treat it as their core business such as GitHub. > > It?s less clear cut to say that services such as Nexus and downloads for > dev tooling, that are used in the overall software productization process > or in support of our products, shouldn?t be provided by Red Hat which is > why we?re having conversations with the related teams to determine the most > appropriate outcomes. > > Max has started the following spreadsheet for MW Engineering to > co-ordinate what the plans are for various jboss.org domains following > the PHX2 shutdown so there?s one place to go: > > > https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 - > *.jboss.org transition > > I hope this helps to clear things up a bit. > > > Mark > > > > On Thu, 20 Jan 2022 at 11:42, Andrew Dinn wrote: > >> Hi Mark (Newton), >> >> Is that just the sound of tumbleweeds rolling down main street on an >> east wind that I can hear? Or did I miss a response to the questions >> below? >> >> I really need to know the answers to these questions quite soon, >> especially question 4, and I am sure I am not alone in that regard. >> >> If projects are really being expected to find somewhere to store >> web/download content then that's going to require time to plan, not >> simply to provision the relevant services but also to deal with the >> disruption (both to project processes and to users) that may arise from >> having existing content relocated. >> >> Can we please have some clarification and advice here? >> >> regards, >> >> >> Andrew Dinn >> ----------- >> >> On 17/01/2022 11:06, Andrew Dinn wrote: >> > Can you be more explicit about a few points made in this post: >> > >> > 1) Is the current work in progress simply a relocation of >> > filemgmt.jboss.org to a virtualized server running inside OpenShift in >> > IAD2? Or does it actually entail disabling access to content addressed >> > with URLs based on the name filemgmt.jboss.org before or by 31 March? >> > >> > 2) Is the story regarding current WIP for docs.jboss.org, >> > developer.jboss.org, www.jboss.org, static.jboss.org, and >> > project.jboss.org the same as for filemgmt.jboss.org If not then what >> is >> > the difference? >> > >> > 3) Are you saying that all content made available via URLs based on the >> > above list of names will need to be relocated to servers provided by the >> > relevant projects before end of Dec 2022? >> > >> > 4) What does this mean for projects like Byteman that essentially belong >> > within JBoss/Red Hat? Am I expected *personally* to host my own web/file >> > service to serve Byteman related content? Am I also expected to provide >> > my own domain and/or relocate the content from byteman.jboss.org Or is >> > there some common Red Hat server resource I can use which keeps the >> > content in the jboss domain? >> >> > > -- > Mark Newton > Director, Customer Digital Experience > Red Hat > +44 7795 520655 > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://listman.redhat.com/mailman/listinfo/devtools > -- Nick Boldt (he/him/his) Principal Software Engineer, RHCSA Productization Lead :: CodeReady Workspaces IM: @nickboldt / @nboldt / https://divbyzero.neocities.org TRIED. TESTED. TRUSTED. @ @redhatnews Red Hat ?The Only Thing That Is Constant Is Change? - Heraclitus -------------- next part -------------- An HTML attachment was scrubbed... URL: From manderse at redhat.com Fri Jan 21 12:51:54 2022 From: manderse at redhat.com (Max Rydahl Andersen) Date: Fri, 21 Jan 2022 13:51:54 +0100 Subject: [Devtools] [devtools-team] Fwd: Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <1c2e0692-da0f-2ec0-6966-f92058e3c758@redhat.com> <291bd428-75d9-c7b8-c2c6-f448656b671a@redhat.com> <1886bf9e-bef6-4814-973b-aea5386f5dcc@Spark> Message-ID: <39060108-B075-46C8-9373-C55212653FD6@redhat.com> On 20 Jan 2022, at 22:13, Nick Boldt wrote: > Thanks, CodeReady Workspaces & Eclipse Che concerns added to > https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 Thanks. > > > If PSSC proposes a new place to host these files that's safe enough for > supply chain security concerns, we can move our content to a new host. > > Has anyone from PSSC been looped in on this? PSSC? /max > Nick > > > On Thu, Jan 20, 2022 at 3:03 PM Max Rydahl Andersen > wrote: > >> More updates. >> >> Please See spreadsheet and add the sites You want us to be aware about and >> what issues/concerns You have. >> ---------- Forwarded message ---------- >> *From:* Mark Newton >> *Date:* 20 Jan 2022, 16:48 +0100 >> *To:* mlittle-all at redhat.com >> *Cc:* Core, The >> *Subject:* Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 >> Shutdown >> >> Hi Andrew, >> >> Apologies for the delay in responding. A number of similar concerns have >> been raised by other people in this thread and elsewhere so we wanted to >> make sure we created one response that addressed all of them. >> >> >> 1. >> >> You?re correct that the current work in progress is simply a >> relocation of the SFTP and rsync services that constitute >> filemgmt.jboss.org to another place. That was going to be OpenShift in >> IAD2 but due to issues provisioning the services there we?re now using >> OpenStack in IAD2. I?ll address accessing the content at URLs serviced by >> filemgmt.jboss.org below. >> >> >> >> 1. >> >> As filemgmt.jboss.org is used to upload content and all the other >> domains are used to access/read content they are being treated differently. >> 1. >> >> Some domains such as developer.jboss.org which used to be served by >> a Jive server (forums, wiki and blogs) have been archived in the sense that >> the webpages are now flat HTML as we?ve decommissioned Jive. The Confluence >> server at docs.jboss.org/author (used to create project >> documentation) is another example of this. >> 2. >> >> Other domains like doc.jboss.org (without the /author path) and >> issues.jboss.org have been moved to spaces.redhat.com and >> issues.redhat.com respectively as the Confluence and JIRA servers >> behind them are now owned by the Portfolio Lifecycle Management team in >> Engineering. Due to an error redirecting traffic from docs.jboss.org >> to spaces.redhat.com that didn?t account for subpaths, some of the >> project documentation available at docs.jboss.org/ was >> temporarily unavailable (as it was redirected to spaces.redhat.com) >> but we?ve since fixed this. >> 3. >> >> www.jboss.org is now owned by MW Engineering who use GitHub to >> author content instead of the Magnolia CMS which has been shutdown. >> 4. >> >> static.jboss.org and .jboss.org (along with some >> .org domains) use Apache httpd servers which are being relocated >> from virtualized machines in PHX2 to OpenShift in IAD2. >> >> >> >> 1. >> >> Content made available from the URLs mentioned in item 2 above will >> continue to be be accessible after Dec 2022 but without further action >> those domains will be considered archived in the sense that you will no >> longer be able to upload content there (as filemgmt.jboss.org is >> currently scheduled to be shutdown at the end of Dec 2022). >> >> >> >> 1. >> >> What this means for projects like Byteman that have content at >> byteman.jboss.org is that they would need to move to another hosting >> provider like GitHub Pages ***by the end of Dec 2022*** if they wanted to >> continue uploading content to their domain. I understand we can move >> subdomains like byteman.jboss.org to GitHub while keeping other >> jboss.org subdomains hosted by Red Hat. As such you wouldn?t have to >> *personally* host your own web/file service but you would be expected to >> perform the migration along with any necessary maintenance after that. We >> will provide some instructions in Confluence on how to move to GitHub Pages >> as we?ve already done this ourselves for some legacy projects to reduce the >> amount of Akamai configuration needed for the overall jboss.org >> migration out of PHX2. >> >> >> Max Andersen has also raised concerns about the impact of these changes to >> DevTools as they use downloads.jboss.org to serve tooling binaries which >> are considered pseudo-products and therefore treated differently from >> projects. This argument may impact whether or not we keep the content >> upload service at filemgmt.jboss.org living beyond Dec 2022 but the most >> appropriate solution still needs to be determined and project teams are >> still encouraged to move their project sites to GitHub Pages if possible as >> that service is actively developed to provide modern project site hosting >> capabilities. >> >> Ultimately we?re trying to establish the most appropriate balance of >> product/project concerns in terms of what Red Hat should be providing >> services for. Given all the recent reorganizations across the company to >> focus on capturing the Open Hybrid Cloud market the hosting of community >> projects is not something that is being considered part of our core >> business. As such we should look to externalize it if possible using >> companies that do treat it as their core business such as GitHub. >> >> It?s less clear cut to say that services such as Nexus and downloads for >> dev tooling, that are used in the overall software productization process >> or in support of our products, shouldn?t be provided by Red Hat which is >> why we?re having conversations with the related teams to determine the most >> appropriate outcomes. >> >> Max has started the following spreadsheet for MW Engineering to >> co-ordinate what the plans are for various jboss.org domains following >> the PHX2 shutdown so there?s one place to go: >> >> >> https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 - >> *.jboss.org transition >> >> I hope this helps to clear things up a bit. >> >> >> Mark >> >> >> >> On Thu, 20 Jan 2022 at 11:42, Andrew Dinn wrote: >> >>> Hi Mark (Newton), >>> >>> Is that just the sound of tumbleweeds rolling down main street on an >>> east wind that I can hear? Or did I miss a response to the questions >>> below? >>> >>> I really need to know the answers to these questions quite soon, >>> especially question 4, and I am sure I am not alone in that regard. >>> >>> If projects are really being expected to find somewhere to store >>> web/download content then that's going to require time to plan, not >>> simply to provision the relevant services but also to deal with the >>> disruption (both to project processes and to users) that may arise from >>> having existing content relocated. >>> >>> Can we please have some clarification and advice here? >>> >>> regards, >>> >>> >>> Andrew Dinn >>> ----------- >>> >>> On 17/01/2022 11:06, Andrew Dinn wrote: >>>> Can you be more explicit about a few points made in this post: >>>> >>>> 1) Is the current work in progress simply a relocation of >>>> filemgmt.jboss.org to a virtualized server running inside OpenShift in >>>> IAD2? Or does it actually entail disabling access to content addressed >>>> with URLs based on the name filemgmt.jboss.org before or by 31 March? >>>> >>>> 2) Is the story regarding current WIP for docs.jboss.org, >>>> developer.jboss.org, www.jboss.org, static.jboss.org, and >>>> project.jboss.org the same as for filemgmt.jboss.org If not then what >>> is >>>> the difference? >>>> >>>> 3) Are you saying that all content made available via URLs based on the >>>> above list of names will need to be relocated to servers provided by the >>>> relevant projects before end of Dec 2022? >>>> >>>> 4) What does this mean for projects like Byteman that essentially belong >>>> within JBoss/Red Hat? Am I expected *personally* to host my own web/file >>>> service to serve Byteman related content? Am I also expected to provide >>>> my own domain and/or relocate the content from byteman.jboss.org Or is >>>> there some common Red Hat server resource I can use which keeps the >>>> content in the jboss domain? >>> >>> >> >> -- >> Mark Newton >> Director, Customer Digital Experience >> Red Hat >> +44 7795 520655 >> >> _______________________________________________ >> Devtools mailing list >> Devtools at redhat.com >> https://listman.redhat.com/mailman/listinfo/devtools >> > > > -- > > Nick Boldt (he/him/his) > > Principal Software Engineer, RHCSA > > Productization Lead :: CodeReady Workspaces > > IM: @nickboldt / @nboldt / https://divbyzero.neocities.org > > TRIED. TESTED. TRUSTED. > @ @redhatnews Red Hat > > > > > ?The Only Thing That Is Constant Is Change? - Heraclitus /max https://xam.dk/about From nboldt at redhat.com Fri Jan 21 18:48:26 2022 From: nboldt at redhat.com (Nick Boldt) Date: Fri, 21 Jan 2022 14:48:26 -0400 Subject: [Devtools] [devtools-team] Fwd: Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: <39060108-B075-46C8-9373-C55212653FD6@redhat.com> References: <1c2e0692-da0f-2ec0-6966-f92058e3c758@redhat.com> <291bd428-75d9-c7b8-c2c6-f448656b671a@redhat.com> <1886bf9e-bef6-4814-973b-aea5386f5dcc@Spark> <39060108-B075-46C8-9373-C55212653FD6@redhat.com> Message-ID: PSSC = Product Security Supply Chain, the paperwork-intensive and acronym-happy sub-sect of Product Security. For example, see https://groups.google.com/u/1/a/redhat.com/g/PSSC-Announce/c/56WCwggY-w4?hl=en&pli=1 Nick On Fri, Jan 21, 2022 at 8:52 AM Max Rydahl Andersen wrote: > On 20 Jan 2022, at 22:13, Nick Boldt wrote: > > > Thanks, CodeReady Workspaces & Eclipse Che concerns added to > > > https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 > > Thanks. > > > > > > > If PSSC proposes a new place to host these files that's safe enough for > > supply chain security concerns, we can move our content to a new host. > > > > Has anyone from PSSC been looped in on this? > > PSSC? > > /max > > > Nick > > > > > > On Thu, Jan 20, 2022 at 3:03 PM Max Rydahl Andersen > > > wrote: > > > >> More updates. > >> > >> Please See spreadsheet and add the sites You want us to be aware about > and > >> what issues/concerns You have. > >> ---------- Forwarded message ---------- > >> *From:* Mark Newton > >> *Date:* 20 Jan 2022, 16:48 +0100 > >> *To:* mlittle-all at redhat.com > >> *Cc:* Core, The > >> *Subject:* Re: [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 > >> Shutdown > >> > >> Hi Andrew, > >> > >> Apologies for the delay in responding. A number of similar concerns have > >> been raised by other people in this thread and elsewhere so we wanted to > >> make sure we created one response that addressed all of them. > >> > >> > >> 1. > >> > >> You?re correct that the current work in progress is simply a > >> relocation of the SFTP and rsync services that constitute > >> filemgmt.jboss.org to another place. That was going to be OpenShift > in > >> IAD2 but due to issues provisioning the services there we?re now > using > >> OpenStack in IAD2. I?ll address accessing the content at URLs > serviced by > >> filemgmt.jboss.org below. > >> > >> > >> > >> 1. > >> > >> As filemgmt.jboss.org is used to upload content and all the other > >> domains are used to access/read content they are being treated > differently. > >> 1. > >> > >> Some domains such as developer.jboss.org which used to be served > by > >> a Jive server (forums, wiki and blogs) have been archived in the > sense that > >> the webpages are now flat HTML as we?ve decommissioned Jive. The > Confluence > >> server at docs.jboss.org/author (used to create project > >> documentation) is another example of this. > >> 2. > >> > >> Other domains like doc.jboss.org (without the /author path) and > >> issues.jboss.org have been moved to spaces.redhat.com and > >> issues.redhat.com respectively as the Confluence and JIRA servers > >> behind them are now owned by the Portfolio Lifecycle Management > team in > >> Engineering. Due to an error redirecting traffic from > docs.jboss.org > >> to spaces.redhat.com that didn?t account for subpaths, some of > the > >> project documentation available at docs.jboss.org/ was > >> temporarily unavailable (as it was redirected to > spaces.redhat.com) > >> but we?ve since fixed this. > >> 3. > >> > >> www.jboss.org is now owned by MW Engineering who use GitHub to > >> author content instead of the Magnolia CMS which has been > shutdown. > >> 4. > >> > >> static.jboss.org and .jboss.org (along with some > >> .org domains) use Apache httpd servers which are being > relocated > >> from virtualized machines in PHX2 to OpenShift in IAD2. > >> > >> > >> > >> 1. > >> > >> Content made available from the URLs mentioned in item 2 above will > >> continue to be be accessible after Dec 2022 but without further > action > >> those domains will be considered archived in the sense that you will > no > >> longer be able to upload content there (as filemgmt.jboss.org is > >> currently scheduled to be shutdown at the end of Dec 2022). > >> > >> > >> > >> 1. > >> > >> What this means for projects like Byteman that have content at > >> byteman.jboss.org is that they would need to move to another hosting > >> provider like GitHub Pages ***by the end of Dec 2022*** if they > wanted to > >> continue uploading content to their domain. I understand we can move > >> subdomains like byteman.jboss.org to GitHub while keeping other > >> jboss.org subdomains hosted by Red Hat. As such you wouldn?t have to > >> *personally* host your own web/file service but you would be > expected to > >> perform the migration along with any necessary maintenance after > that. We > >> will provide some instructions in Confluence on how to move to > GitHub Pages > >> as we?ve already done this ourselves for some legacy projects to > reduce the > >> amount of Akamai configuration needed for the overall jboss.org > >> migration out of PHX2. > >> > >> > >> Max Andersen has also raised concerns about the impact of these changes > to > >> DevTools as they use downloads.jboss.org to serve tooling binaries > which > >> are considered pseudo-products and therefore treated differently from > >> projects. This argument may impact whether or not we keep the content > >> upload service at filemgmt.jboss.org living beyond Dec 2022 but the > most > >> appropriate solution still needs to be determined and project teams are > >> still encouraged to move their project sites to GitHub Pages if > possible as > >> that service is actively developed to provide modern project site > hosting > >> capabilities. > >> > >> Ultimately we?re trying to establish the most appropriate balance of > >> product/project concerns in terms of what Red Hat should be providing > >> services for. Given all the recent reorganizations across the company to > >> focus on capturing the Open Hybrid Cloud market the hosting of community > >> projects is not something that is being considered part of our core > >> business. As such we should look to externalize it if possible using > >> companies that do treat it as their core business such as GitHub. > >> > >> It?s less clear cut to say that services such as Nexus and downloads for > >> dev tooling, that are used in the overall software productization > process > >> or in support of our products, shouldn?t be provided by Red Hat which is > >> why we?re having conversations with the related teams to determine the > most > >> appropriate outcomes. > >> > >> Max has started the following spreadsheet for MW Engineering to > >> co-ordinate what the plans are for various jboss.org domains following > >> the PHX2 shutdown so there?s one place to go: > >> > >> > >> > https://docs.google.com/spreadsheets/d/1SXlCkp_Ok0vw1ArCA8UjpWAyfqQLfZ96rK3ridnB1Eo/edit#gid=0 > - > >> *.jboss.org transition > >> > >> I hope this helps to clear things up a bit. > >> > >> > >> Mark > >> > >> > >> > >> On Thu, 20 Jan 2022 at 11:42, Andrew Dinn wrote: > >> > >>> Hi Mark (Newton), > >>> > >>> Is that just the sound of tumbleweeds rolling down main street on an > >>> east wind that I can hear? Or did I miss a response to the questions > >>> below? > >>> > >>> I really need to know the answers to these questions quite soon, > >>> especially question 4, and I am sure I am not alone in that regard. > >>> > >>> If projects are really being expected to find somewhere to store > >>> web/download content then that's going to require time to plan, not > >>> simply to provision the relevant services but also to deal with the > >>> disruption (both to project processes and to users) that may arise from > >>> having existing content relocated. > >>> > >>> Can we please have some clarification and advice here? > >>> > >>> regards, > >>> > >>> > >>> Andrew Dinn > >>> ----------- > >>> > >>> On 17/01/2022 11:06, Andrew Dinn wrote: > >>>> Can you be more explicit about a few points made in this post: > >>>> > >>>> 1) Is the current work in progress simply a relocation of > >>>> filemgmt.jboss.org to a virtualized server running inside OpenShift > in > >>>> IAD2? Or does it actually entail disabling access to content addressed > >>>> with URLs based on the name filemgmt.jboss.org before or by 31 March? > >>>> > >>>> 2) Is the story regarding current WIP for docs.jboss.org, > >>>> developer.jboss.org, www.jboss.org, static.jboss.org, and > >>>> project.jboss.org the same as for filemgmt.jboss.org If not then what > >>> is > >>>> the difference? > >>>> > >>>> 3) Are you saying that all content made available via URLs based on > the > >>>> above list of names will need to be relocated to servers provided by > the > >>>> relevant projects before end of Dec 2022? > >>>> > >>>> 4) What does this mean for projects like Byteman that essentially > belong > >>>> within JBoss/Red Hat? Am I expected *personally* to host my own > web/file > >>>> service to serve Byteman related content? Am I also expected to > provide > >>>> my own domain and/or relocate the content from byteman.jboss.org Or > is > >>>> there some common Red Hat server resource I can use which keeps the > >>>> content in the jboss domain? > >>> > >>> > >> > >> -- > >> Mark Newton > >> Director, Customer Digital Experience > >> Red Hat > >> +44 7795 520655 > >> > >> _______________________________________________ > >> Devtools mailing list > >> Devtools at redhat.com > >> https://listman.redhat.com/mailman/listinfo/devtools > >> > > > > > > -- > > > > Nick Boldt (he/him/his) > > > > Principal Software Engineer, RHCSA > > > > Productization Lead :: CodeReady Workspaces > > > > IM: @nickboldt / @nboldt / https://divbyzero.neocities.org > > > > TRIED. TESTED. TRUSTED. > > @ @redhatnews Red Hat > > > > > > > > > > ?The Only Thing That Is Constant Is Change? - Heraclitus > > /max > https://xam.dk/about > > -- Nick Boldt (he/him/his) Principal Software Engineer, RHCSA Productization Lead :: CodeReady Workspaces IM: @nickboldt / @nboldt / https://divbyzero.neocities.org TRIED. TESTED. TRUSTED. @ @redhatnews Red Hat ?The Only Thing That Is Constant Is Change? - Heraclitus -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgrunber at redhat.com Mon Jan 24 17:19:06 2022 From: rgrunber at redhat.com (Roland Grunberg) Date: Mon, 24 Jan 2022 12:19:06 -0500 Subject: [Devtools] [devtools-team] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> Message-ID: <5a86dbdd2335722f21c2f83963cb64b14f3228fa.camel@redhat.com> On Thu, 2022-01-20 at 14:17 -0400, Nick Boldt wrote: > Looks like CodeReady Workspaces & Eclipse Che will also have to > investigate how and where to move our hoted vsix plugin content.? > > https://issues.redhat.com/browse/CRW-2662 > > Is Mar 31 2022 a hard drop-dead date? Or is there any flexibility in > that timeline?? Based on updates from the above issue, and reports I've heard from others, there are problems consuming content from https://download.jboss.org/jbosstools already (specifically 504s) . Some have issues others don't, and this includes build systems. The problems started about 3 days ago and continues even now. -- Roland Grunberg From sbouchet at redhat.com Tue Jan 25 16:31:43 2022 From: sbouchet at redhat.com (Stephane Bouchet) Date: Tue, 25 Jan 2022 17:31:43 +0100 Subject: [Devtools] [devtools-team] [IMPORTANT INFORMATION - PLEASE READ] jboss.org PHX2 Shutdown In-Reply-To: <5a86dbdd2335722f21c2f83963cb64b14f3228fa.camel@redhat.com> References: <7965f08d-49ff-466f-8d1f-c00222276a9a@Spark> <583b6f7c-26cc-60ee-2571-12c0ccfeb425@redhat.com> <7F70411A-F639-4E13-9AA1-AE36E2D6191D@redhat.com> <5a86dbdd2335722f21c2f83963cb64b14f3228fa.camel@redhat.com> Message-ID: this issue seems to be resolved for now. redirections were dropped and are now restored. Le lun. 24 janv. 2022 ? 18:29, Roland Grunberg a ?crit : > On Thu, 2022-01-20 at 14:17 -0400, Nick Boldt wrote: > > Looks like CodeReady Workspaces & Eclipse Che will also have to > > investigate how and where to move our hoted vsix plugin content. > > > > https://issues.redhat.com/browse/CRW-2662 > > > > Is Mar 31 2022 a hard drop-dead date? Or is there any flexibility in > > that timeline? > > Based on updates from the above issue, and reports I've heard from > others, there are problems consuming content from > https://download.jboss.org/jbosstools already (specifically 504s) . > Some have issues others don't, and this includes build systems. > > The problems started about 3 days ago and continues even now. > > -- > Roland Grunberg > > _______________________________________________ > Devtools mailing list > Devtools at redhat.com > https://listman.redhat.com/mailman/listinfo/devtools > -- St?phane Bouchet Senior Software Engineer, R&D Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: