Migrating git repos to OpenDev
Hi, As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects. We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects. In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change. Gerrit ====== Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors. Repository Browsing =================== Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name).
From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are: * Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org. This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/ Please let us know if you encounter any problems. If you would like to read more about the design of this system and the transition, see the infra-spec[2]. GitHub ====== Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so. We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub. Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition. Logistics ========= We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it. Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations. For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc. This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same. If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace. Therefore, we need your help: Action Items ============ We need each of the following projects: * OpenStack * Airship * StarlingX * Zuul To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition. If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4]. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
James E. Blair wrote:
[...] Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
I think that would be a great idea, removing a /lot/ of confusion. Four questions: 1/ how much consent do we need from the unofficial project itself before renaming it to something that does not use the OpenStack name? A lot of them are abandoned so it might be hard to get all of them to agree before cleaning things up... 2/ what would, say, openstack/ailuropoda be renamed to ? https://opendev.org/ailuropoda ? or https://opendev.org/opendev/ailuropoda ? Something else ? 3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ? 4/ the reason why we created unofficial projects under openstack/ in the first place was that it was hard to rename projects afterwards when they actually became official. We have much less incoming openstack projects those days, so it might not be as much of a problem, but I was wondering if that was somehow simpler to do today ? -- Thierry Carrez (ttx)
Thierry Carrez <thierry@openstack.org> writes:
I think that would be a great idea, removing a /lot/ of confusion. Four questions:
1/ how much consent do we need from the unofficial project itself before renaming it to something that does not use the OpenStack name? A lot of them are abandoned so it might be hard to get all of them to agree before cleaning things up...
My personal opinion is that OpenStack, represented by the TC in this case, owns the openstack/ namespace, and since the TC chose to let projects use it previously, can revoke that permission. But I'll defer to the TC to decide how much authority it has. :)
2/ what would, say, openstack/ailuropoda be renamed to ? https://opendev.org/ailuropoda ? or https://opendev.org/opendev/ailuropoda ? Something else ?
Gitea does force us into the org/project hierarchy. So we have to have exactly two components in a project name separated by a /. We could create a catch-all org for projects. We've started using opendev/ for repos related to opendev itself, e.g.: https://opendev.org/opendev/base-jobs We could: 1) Use opendev/ for OpenDev itself and any other project 2) Move base-jobs to opendevorg/ and use opendev/ as a catch-all 3) Create some new catch-all org (did someone say stackforge?) 4) Put otherwise orgless projects in their own org (e.g., ailuropoda/ailuropoda) I have no strong opinions. Feedback welcome, and I'll bring it up in the next infra meeting.
3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ?
It would stop. I do think it should then be removed from the openstack/ org on GitHub, as that would be rather misleading otherwise. We can either delete it, which is simple, or, if the project wants to establish a new mirror location on GitHub, we could look into performing an org transfer in order to establish redirects. That is manual, time consuming, and would require complex identity verification steps, but possible.
4/ the reason why we created unofficial projects under openstack/ in the first place was that it was hard to rename projects afterwards when they actually became official. We have much less incoming openstack projects those days, so it might not be as much of a problem, but I was wondering if that was somehow simpler to do today ?
Sadly not yet. There is a plugin for Gerrit which is in development: https://gerrit.googlesource.com/plugins/rename-project/ We're running the wrong version of Gerrit, and it's development lags behind Gerrit master slightly. But someday we hope everything will align and we can use that. We have already automated the process of renaming projects in Gitea, so when we do rename projects in Gerrit (for this migration and any smaller renames in the future), we will have redirects in place on our mirror. -Jim
On 3/8/19 5:29 PM, James E. Blair wrote:
Thierry Carrez <thierry@openstack.org> writes:
I think that would be a great idea, removing a /lot/ of confusion. Four questions:
1/ how much consent do we need from the unofficial project itself before renaming it to something that does not use the OpenStack name? A lot of them are abandoned so it might be hard to get all of them to agree before cleaning things up...
My personal opinion is that OpenStack, represented by the TC in this case, owns the openstack/ namespace, and since the TC chose to let projects use it previously, can revoke that permission.
But I'll defer to the TC to decide how much authority it has. :)
I also have this opinion.
2/ what would, say, openstack/ailuropoda be renamed to ? https://opendev.org/ailuropoda ? or https://opendev.org/opendev/ailuropoda ? Something else ?
Gitea does force us into the org/project hierarchy. So we have to have exactly two components in a project name separated by a /.
We could create a catch-all org for projects. We've started using opendev/ for repos related to opendev itself, e.g.:
https://opendev.org/opendev/base-jobs
We could:
1) Use opendev/ for OpenDev itself and any other project 2) Move base-jobs to opendevorg/ and use opendev/ as a catch-all 3) Create some new catch-all org (did someone say stackforge?) 4) Put otherwise orgless projects in their own org (e.g., ailuropoda/ailuropoda)
I have no strong opinions. Feedback welcome, and I'll bring it up in the next infra meeting.
I am not a fan of 1 or 2 - I don't think the potential confusion of some sort of association between the opendev project and those projecs is worth it. 3 and 4 both seem fine to me - although I think I prefer stackforge/ as an alternative for any non-official project that does not positively identify an org it would like to be in.
3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ?
It would stop. I do think it should then be removed from the openstack/ org on GitHub, as that would be rather misleading otherwise. We can either delete it, which is simple, or, if the project wants to establish a new mirror location on GitHub, we could look into performing an org transfer in order to establish redirects. That is manual, time consuming, and would require complex identity verification steps, but possible.
4/ the reason why we created unofficial projects under openstack/ in the first place was that it was hard to rename projects afterwards when they actually became official. We have much less incoming openstack projects those days, so it might not be as much of a problem, but I was wondering if that was somehow simpler to do today ?
Sadly not yet. There is a plugin for Gerrit which is in development:
https://gerrit.googlesource.com/plugins/rename-project/
We're running the wrong version of Gerrit, and it's development lags behind Gerrit master slightly. But someday we hope everything will align and we can use that.
This is one of those places where someone finding the time to do some java dev to finish that rename-project plugin could be super helpful.
We have already automated the process of renaming projects in Gitea, so when we do rename projects in Gerrit (for this migration and any smaller renames in the future), we will have redirects in place on our mirror.
-Jim
James, Gitea looks great! My only wish is the search bar would work for the project names (octavia and openstack/octavia don't seem to work). Are we planning to make this transition after the Stein release is out? I am slightly worried about making git changes right at the end of the release where project teams are doing the final push to get the release out. Michael On Fri, Mar 8, 2019 at 6:36 AM Thierry Carrez <thierry@openstack.org> wrote:
James E. Blair wrote:
[...] Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
I think that would be a great idea, removing a /lot/ of confusion. Four questions:
1/ how much consent do we need from the unofficial project itself before renaming it to something that does not use the OpenStack name? A lot of them are abandoned so it might be hard to get all of them to agree before cleaning things up...
2/ what would, say, openstack/ailuropoda be renamed to ? https://opendev.org/ailuropoda ? or https://opendev.org/opendev/ailuropoda ? Something else ?
3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ?
4/ the reason why we created unofficial projects under openstack/ in the first place was that it was hard to rename projects afterwards when they actually became official. We have much less incoming openstack projects those days, so it might not be as much of a problem, but I was wondering if that was somehow simpler to do today ?
-- Thierry Carrez (ttx)
On 3/8/19 5:36 PM, Michael Johnson wrote:
James,
Gitea looks great! My only wish is the search bar would work for the project names (octavia and openstack/octavia don't seem to work).
Octvia works in the repo search for meh: https://opendev.org/explore/repos?q=octavia&tab= (from https://opendev.org/explore/repos) I agree, openstack/octavia as a search term did not work. Maybe that's an improvement we can make upstream. (the gitea upstream has thusfar been very receptive and responsive to patches)
Are we planning to make this transition after the Stein release is out? I am slightly worried about making git changes right at the end of the release where project teams are doing the final push to get the release out.
Michael
On Fri, Mar 8, 2019 at 6:36 AM Thierry Carrez <thierry@openstack.org> wrote:
James E. Blair wrote:
[...] Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
I think that would be a great idea, removing a /lot/ of confusion. Four questions:
1/ how much consent do we need from the unofficial project itself before renaming it to something that does not use the OpenStack name? A lot of them are abandoned so it might be hard to get all of them to agree before cleaning things up...
2/ what would, say, openstack/ailuropoda be renamed to ? https://opendev.org/ailuropoda ? or https://opendev.org/opendev/ailuropoda ? Something else ?
3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ?
4/ the reason why we created unofficial projects under openstack/ in the first place was that it was hard to rename projects afterwards when they actually became official. We have much less incoming openstack projects those days, so it might not be as much of a problem, but I was wondering if that was somehow simpler to do today ?
-- Thierry Carrez (ttx)
Michael Johnson <johnsomor@gmail.com> writes:
James,
Gitea looks great! My only wish is the search bar would work for the project names (octavia and openstack/octavia don't seem to work).
"octavia" seems to work for me: https://opendev.org/explore/repos?q=octavia&tab= Though it does look like it returns them in order of most-to-least-recently updated. I agree that "openstack/octavia" doesn't work as I would expect.
Are we planning to make this transition after the Stein release is out? I am slightly worried about making git changes right at the end of the release where project teams are doing the final push to get the release out.
That's one of the things we'll start talking about in next week's infra meeting. That sounds like a very reasonable thing for us to keep in mind. :) -Jim
On Fri, Mar 8, 2019 at 9:36 AM Thierry Carrez <thierry@openstack.org> wrote:
3/ What would happen to the automatic GitHub mirroring when we rename unofficial projects ? I suspect the mirroring would stop ? Would we automatically remove the no-longer-mirrored project from GitHub ?
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. "Free software needs free tools" [1] certainly ranks at the top of the presentations I have attended and I have the utmost respect for the four opens, the foundation's values and mission. Please do not consider that I have sold my soul to proprietary software vendors. A Fedora council blog post [2] has recently worded this better than I probably could: --- Ideally, we want everything to be on open source services (e.g. Taiga, Pagure, or GitLab). But, as a pragmatic matter, we recognize that GitHub has a huge network effect — there are millions of users and developers there, and millions of open source and free software projects hosted there, including software that’s fundamental to the Fedora operating system. --- Is there a way to make this work ? [1]: https://www.youtube.com/watch?v=U_nK6nP_RCY [2]: https://communityblog.fedoraproject.org/fedora-council-december-2018-hackfes... David Moreau Simard dmsimard = [irc, github, twitter]
On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote:
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. [...] Is there a way to make this work ? [...]
The idea is that you could run a Zuul job in the "post" pipeline which pushes the branch tip to a repository in a GitHub (or Bitbucket or whatever) remote URL of your choice. The job could include credentials for a service account you create with push rights for that remote. While the playbook containing the Zuul secret would need to be in your repository, the fundamental role to perform the git push is probably a good candidate for including in Zuul's standard library. You'd probably also want it to run in the "tag" pipeline to push a copy of any tag which triggers it. This ought to be a fairly trivial job and could be set up in advance of any changes in Gerrit. Are you perhaps interested in prototyping something along these lines? I expect it would be very useful. -- Jeremy Stanley
On 2019-03-10 17:03:27 +0000 (+0000), Jeremy Stanley wrote:
On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote:
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. [...] Is there a way to make this work ? [...]
The idea is that you could run a Zuul job in the "post" pipeline which pushes the branch tip to a repository in a GitHub (or Bitbucket or whatever) remote URL of your choice. The job could include credentials for a service account you create with push rights for that remote. While the playbook containing the Zuul secret would need to be in your repository, the fundamental role to perform the git push is probably a good candidate for including in Zuul's standard library. You'd probably also want it to run in the "tag" pipeline to push a copy of any tag which triggers it. [...]
I also meant to add (mostly for the sake of other readers as I expect it's obvious to you) that the job would be able to run on the Zuul executor and so would be effectively instantaneous, as it then doesn't wait for a job node assignment. -- Jeremy Stanley
Jeremy Stanley <fungi@yuggoth.org> writes:
On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote:
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. [...] Is there a way to make this work ? [...]
The idea is that you could run a Zuul job in the "post" pipeline which pushes the branch tip to a repository in a GitHub (or Bitbucket or whatever) remote URL of your choice. The job could include credentials for a service account you create with push rights for that remote. While the playbook containing the Zuul secret would need to be in your repository, the fundamental role to perform the git push is probably a good candidate for including in Zuul's standard library. You'd probably also want it to run in the "tag" pipeline to push a copy of any tag which triggers it.
Easier than that, actually. With the new pass-to-parent[1] feature, the job and playbook can be defined once in zuul-jobs, and the only item necessary in the repository would be the job invocation and secret. [1] https://zuul-ci.org/docs/zuul/user/config.html#attr-job.secrets.pass-to-pare... -Jim
On Sun, Mar 10, 2019 at 1:04 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote:
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. [...] Is there a way to make this work ? [...]
The idea is that you could run a Zuul job in the "post" pipeline which pushes the branch tip to a repository in a GitHub (or Bitbucket or whatever) remote URL of your choice. The job could include credentials for a service account you create with push rights for that remote. While the playbook containing the Zuul secret would need to be in your repository, the fundamental role to perform the git push is probably a good candidate for including in Zuul's standard library. You'd probably also want it to run in the "tag" pipeline to push a copy of any tag which triggers it.
This ought to be a fairly trivial job and could be set up in advance of any changes in Gerrit. Are you perhaps interested in prototyping something along these lines? I expect it would be very useful.
Thanks for the clarification Jeremy. I was under the impression that the challenge with GitHub was not a technical one. What I take away from this is that while GitHub will not be supported by OpenDev, individual projects can still choose to use it on their own. I'll look at creating roles/jobs around this workflow. David Moreau Simard dmsimard = [irc, github, twitter]
You do realize that by changing the naming structure of long existing projects you are going to break every single HTTP link out there that points at actual code, right? Why can't Openstack stay OpenStack inside of the the OpenDev environment? Or at least provide backwards compatible links? It is going to be as if OpenStack has just disappeared. On Thu, Mar 14, 2019 at 10:54 AM David Moreau Simard <dmsimard@redhat.com> wrote:
On Sun, Mar 10, 2019 at 1:04 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote:
ARA is an "unofficial" OpenStack project that would be part of this move and I would appreciate if ARA could remain on GitHub where the Ansible community is. [...] Is there a way to make this work ? [...]
The idea is that you could run a Zuul job in the "post" pipeline which pushes the branch tip to a repository in a GitHub (or Bitbucket or whatever) remote URL of your choice. The job could include credentials for a service account you create with push rights for that remote. While the playbook containing the Zuul secret would need to be in your repository, the fundamental role to perform the git push is probably a good candidate for including in Zuul's standard library. You'd probably also want it to run in the "tag" pipeline to push a copy of any tag which triggers it.
This ought to be a fairly trivial job and could be set up in advance of any changes in Gerrit. Are you perhaps interested in prototyping something along these lines? I expect it would be very useful.
Thanks for the clarification Jeremy.
I was under the impression that the challenge with GitHub was not a technical one.
What I take away from this is that while GitHub will not be supported by OpenDev, individual projects can still choose to use it on their own.
I'll look at creating roles/jobs around this workflow.
David Moreau Simard dmsimard = [irc, github, twitter]
On 3/14/19 3:25 PM, Adam Young wrote:
You do realize that by changing the naming structure of long existing projects you are going to break every single HTTP link out there that points at actual code, right?
Why can't Openstack stay OpenStack inside of the the OpenDev environment? Or at least provide backwards compatible links? It is going to be as if OpenStack has just disappeared.
Who said anything about doing this without providing backwards compatible links? There are totally going to be backwards compatible links. " When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org. "
On Thu, Mar 14, 2019 at 10:54 AM David Moreau Simard <dmsimard@redhat.com <mailto:dmsimard@redhat.com>> wrote:
On Sun, Mar 10, 2019 at 1:04 PM Jeremy Stanley <fungi@yuggoth.org <mailto:fungi@yuggoth.org>> wrote: > > On 2019-03-10 11:52:33 -0400 (-0400), David Moreau Simard wrote: > > ARA is an "unofficial" OpenStack project that would be part of this > > move and I would appreciate if ARA could remain on GitHub where the > > Ansible community is. > [...] > > Is there a way to make this work ? > [...] > > The idea is that you could run a Zuul job in the "post" pipeline > which pushes the branch tip to a repository in a GitHub (or > Bitbucket or whatever) remote URL of your choice. The job could > include credentials for a service account you create with push > rights for that remote. While the playbook containing the Zuul > secret would need to be in your repository, the fundamental role to > perform the git push is probably a good candidate for including in > Zuul's standard library. You'd probably also want it to run in the > "tag" pipeline to push a copy of any tag which triggers it. > > This ought to be a fairly trivial job and could be set up in advance > of any changes in Gerrit. Are you perhaps interested in prototyping > something along these lines? I expect it would be very useful.
Thanks for the clarification Jeremy.
I was under the impression that the challenge with GitHub was not a technical one.
What I take away from this is that while GitHub will not be supported by OpenDev, individual projects can still choose to use it on their own.
I'll look at creating roles/jobs around this workflow.
David Moreau Simard dmsimard = [irc, github, twitter]
corvus@inaugust.com (James E. Blair) writes:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
Working with the folks representing each of the affected OSF projects, we've scheduled the migration for Friday, April 19, 2019. This is shortly after the next OpenStack release. Please see [2] for further details about what this will involve. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.htm... -Jim
On Thu, Mar 07, 2019 at 01:45:55PM -0800, James E. Blair wrote:
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
I just want to check before I do anything rash .... Is it okay to land patches that move from http://git.openstack.org/cgit/.... to the equiv on https://opendev.org/ ? Aside from muscle memory issues I like the new urls :) Yours Tony.
On 2019-03-21 12:09:08 +1100 (+1100), Tony Breeds wrote: [...]
I just want to check before I do anything rash .... Is it okay to land patches that move from http://git.openstack.org/cgit/.... to the equiv on https://opendev.org/ ? [...]
Definitely don't try to change references in Zuul configuration yet, or paths to Zuul-provided Git repositories in jobs, as it won't work until the scheduled cut-over (and we'll be bypassing Gerrit to merge the corrections for those along with .gitreview file updates for every repository we host as a part of the maintenance itself). Beyond that, we're likely to be taking the Gitea service at opendev.org up and down some more between now and then, than we are after. So I'd caution against it personally. -- Jeremy Stanley
On Thu, Mar 21, 2019 at 02:46:19AM +0000, Jeremy Stanley wrote:
Definitely don't try to change references in Zuul configuration yet, or paths to Zuul-provided Git repositories in jobs, as it won't work until the scheduled cut-over (and we'll be bypassing Gerrit to merge the corrections for those along with .gitreview file updates for every repository we host as a part of the maintenance itself). Beyond that, we're likely to be taking the Gitea service at opendev.org up and down some more between now and then, than we are after. So I'd caution against it personally.
Good enough for me. I'll hold off. Thanks Jeremy Yours Tony.
On Thu, Mar 21, 2019, at 02:14, Tony Breeds wrote:
Aside from muscle memory issues I like the new urls :)
+1 Next to that, I believe this kind of conversation should be tagged with [all] as it impacts everyone, and matches my email filtering needs :D Anyway, thanks for this, it's truly great! Regards, Jean-Philippe (evrardjp)
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership. One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5]. This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well. Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly. [5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm... Thank you for your patience and feel free to reach out with any questions you might have. Clark
On Thu, Apr 11, 2019, at 3:21 PM, Clark Boylan wrote:
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership.
One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5].
This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well.
Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly.
[5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm...
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC. Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues. For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped. As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark
---- On Tue, 16 Apr 2019 19:13:06 -0500 Clark Boylan <cboylan@sapwetik.org> wrote ----
On Thu, Apr 11, 2019, at 3:21 PM, Clark Boylan wrote:
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership.
One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5].
This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well.
Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly.
[5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm...
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
Thanks Clark, Fungi for the list. With quick review, below are the two repo which I feel need a home somewhere. - gerrit-dash-creator - it thought it was under infra. - upstream-institute-virtual-environment - We use this in OUI trainings. I pinged this on #openstack-upstream-institute to find home. -gmann
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark
---- On Tue, 16 Apr 2019 21:10:18 -0500 Ghanshyam Mann <gmann@ghanshyammann.com> wrote ----
---- On Tue, 16 Apr 2019 19:13:06 -0500 Clark Boylan <cboylan@sapwetik.org> wrote ----
On Thu, Apr 11, 2019, at 3:21 PM, Clark Boylan wrote:
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership.
One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5].
This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well.
Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly.
[5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm...
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
Thanks Clark, Fungi for the list. With quick review, below are the two repo which I feel need a home somewhere.
- gerrit-dash-creator - it thought it was under infra. - upstream-institute-virtual-environment - We use this in OUI trainings. I pinged this on #openstack-upstream-institute to find home.
I found one more which need to be placed somewhere in openstack/ - microversion-parse - this lib is used by many projects for API microversion parsing. maybe cdent can suggest.
-gmann
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark
On Tue, 16 Apr 2019, Ghanshyam Mann wrote:
I found one more which need to be placed somewhere in openstack/
- microversion-parse - this lib is used by many projects for API microversion parsing. maybe cdent can suggest.
When microversion-parse was first put together it wasn't put under an official project for three reasons: * Make it accessible to anything outside the OpenStack world that might like to work with microversion (if ever such a thing cae to exist). * Make it crystal clear that the library was just a thing you install from PyPI, no big deal. * Couldn't decide anywhere to put it. We're essentially still in that boat, but what's changed, at least a bit, is that it's increasingly easy to think of things born in the OpenStack world as just things you can install from PyPI. All of which is a long way of saying I don't really have any good suggestions. The current core group is made up of members of the API-SIG but that group doesn't currently own any code-oriented repos. If it is acceptable for it to be openstack/microversion-parse then let's do that. If it can't, because it is not "official", then it's also fine for it to be in the 'x' namespace. The main signifier (to me) is the domain name, and with that changing anyway, the rest of it doesn't really signify. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent
---- On Wed, 17 Apr 2019 04:45:18 -0500 Chris Dent <cdent+os@anticdent.org> wrote ----
On Tue, 16 Apr 2019, Ghanshyam Mann wrote:
I found one more which need to be placed somewhere in openstack/
- microversion-parse - this lib is used by many projects for API microversion parsing. maybe cdent can suggest.
When microversion-parse was first put together it wasn't put under an official project for three reasons:
* Make it accessible to anything outside the OpenStack world that might like to work with microversion (if ever such a thing cae to exist).
* Make it crystal clear that the library was just a thing you install from PyPI, no big deal.
* Couldn't decide anywhere to put it.
We're essentially still in that boat, but what's changed, at least a bit, is that it's increasingly easy to think of things born in the OpenStack world as just things you can install from PyPI.
All of which is a long way of saying I don't really have any good suggestions.
The current core group is made up of members of the API-SIG but that group doesn't currently own any code-oriented repos.
If it is acceptable for it to be openstack/microversion-parse then let's do that. If it can't, because it is not "official", then it's also fine for it to be in the 'x' namespace. The main signifier (to me) is the domain name, and with that changing anyway, the rest of it doesn't really signify.
Thanks Chris for detail information. As it is very close and OpenStack-only-used lib, For long term maintenance, it will be good if it stay under openstack. and if we want to extend it with more common classes like APIVersionRequest thing[1] Moving to oslo can be one idea to discuss. If you would like to keep it under openstack/ till opendev-transition, you can add this in this ethercal[2] and after that, we can discuss to propose under some official project like oslo etc ? [1] https://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/api_ve... [2] https://ethercalc.openstack.org/opendev-transition -gmann
-- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent
On Wed, 17 Apr 2019, Ghanshyam Mann wrote:
If you would like to keep it under openstack/ till opendev-transition, you can add this in this ethercal[2] and after that, we can discuss to propose under some official project like oslo etc ?
I've added it to the ethercalc with a reference back to this discussion. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent
On 17/04/2019 04.10, Ghanshyam Mann wrote:
[...] Thanks Clark, Fungi for the list. With quick review, below are the two repo which I feel need a home somewhere.
- gerrit-dash-creator - it thought it was under infra.
It was never under governance, so is independent. Looks like I'm the only reviewer of it at the moment, if anybody wants to help and move it to another place, please speak up, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wed, Apr 17, 2019 at 9:16 AM Clark Boylan <cboylan@sapwetik.org> wrote:
On Thu, Apr 11, 2019, at 3:21 PM, Clark Boylan wrote:
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership.
One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5].
This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well.
Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly.
[5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm...
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
while tap-as-a-service is unofficial at this point, the intention is to make it a part of neutron sooner or later. i want to keep them under openstack/ if acceptable. openstack/tap-as-a-service -> x/tap-as-a-service openstack/tap-as-a-service-dashboard -> x/tap-as-a-service-dashboard openstack/tap-as-a-service-tempest-plugin -> x/tap-as-a-service-tempest-plugin
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark
On Wed, Apr 17, 2019 at 9:16 AM Clark Boylan <cboylan@sapwetik.org> wrote:
On Thu, Apr 11, 2019, at 3:21 PM, Clark Boylan wrote:
On Thu, Mar 7, 2019, at 1:46 PM, James E. Blair wrote:
Hi,
As discussed in November[1], the OpenStack project infrastructure is being rebranded as "OpenDev" to better support a wider community of projects.
We are nearly ready to perform the part of this transition with the largest impact: moving the authoritative git repositories for existing projects.
In this email, I'd like to introduce the new hosting system we are preparing, discuss the transition, and invite projects to work with us on the logistics of the change.
Gerrit ======
Gerrit is the core of our system and it will remain so in OpenDev. As part of this move, we will rename the gerrit server from review.openstack.org to review.opendev.org. As part of the transition, we will automatically merge appropriate changes to all branches of all repositories updating .gitreview and Zuul configuration files. Any further changes (README files, etc.) we expect to be made by individual project contributors.
Repository Browsing ===================
Currently our canonical *public* repository system is the cgit server at https://git.openstack.org/ (and git.airshipit.org, git.starlingx.io, and git.zuul-ci.org). This is a load balanced cluster of several servers which is designed to handle all the public git repository traffic, as it scales much better than Gerrit (and has a more friendly domain name). From a technical standpoint, it's excellent, but its usability could be improved.
Therefore, as part of this transition, we will replace the cgit servers with a new system based on Gitea. Gitea is a complete development collaboration system, but it's very flexible and will allow us to disable components which we aren't using. We will operate it in a read-only configuration where it will act as the public mirror for Gerrit. The advantages it has over the current system are:
* Shorter domain name in project URLs: https://git.openstack.org/openstack/nova vs https://opendev.org/openstack/nova * Clone and browsing URLs are the same (with cgit, the browsing URL has an extra path component) * More visually pleasing code browsing * Integrated code searching * Ability to highlight multiple lines in links
When we perform the transition we will install redirects from git.openstack.org (and the other git sites) to opendev.org, and will maintain those redirects for the foreseeable future. We will construct them so that even existing deep links to individual files in individual commits to cgit will redirect to the correct location on opendev.org.
This system is up and running now with a live mirror of data from Gerrit, and you can start testing it out today at https://opendev.org/
Please let us know if you encounter any problems.
If you would like to read more about the design of this system and the transition, see the infra-spec[2].
GitHub ======
Currently all OpenStack projects are replicated to GitHub. We do not plan on changing that during the transition, however, any projects outside of the openstack*/ namespaces will not automatically be replicated to GitHub, and we do not plan on adding that in the future. We do, however, support projects using Zuul to run post-merge jobs to push updates to GitHub or any other third-party mirrors with their own credentials. We will be happy to work with anyone interested in that to help set up jobs to do so.
We are adopting this approach so that individual projects can have more control over how they are represented in social media, and to give us more flexibility in supporting our own organizational namespaces on OpenDev without assuming they map directly to GitHub.
Eventually we plan on moving the OpenStack project to that system as well and retiring direct replication from Gerrit to GitHub completely. But we will defer that work until after this transition.
Logistics =========
We can prepare much of the system in advance (as we have for the hosting system on opendev.org), but the actual transition and renaming of the Gerrit server will need to happen at once during an outage window. We need to schedule that outage and begin preparing for it.
Since all of the project git URLs are going to change (to replace git.openstack.org with opendev.org and review.openstack.org with review.opendev.org), we can additionally take the opportunity to reorganize projects into different organizations.
For example, during the transition we will rename Zuul, and it's associated projects, from the "openstack-infra" org to "zuul". So their new names will be "zuul/zuul", "zuul/nodepool", etc.
This is an excellent time for the rest of the OpenStack Foundation pilot projects to do the same.
If the OpenStack project desires this, it would also be a good time to move unofficial projects out of the openstack/ namespace.
Therefore, we need your help:
Action Items ============
We need each of the following projects:
* OpenStack * Airship * StarlingX * Zuul
To nominate a single point of contact to work with us on the transition. It would be helpful for that person to attend the next (and possibly next several) openstack infra team meetings in IRC [3]. We will work with those people on scheduling the transition, as well as finalizing the list of projects which should be renamed as part of the transition.
If you manage an unofficial project and would like to take the opportunity to move or rename your project, please add it to this ethercalc[4].
[1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.... [3] http://eavesdrop.openstack.org/#Project_Infrastructure_Team_Meeting [4] https://ethercalc.openstack.org/opendev-transition
We've made good progress in preparing this change and are still on track to do this Friday April 19, 2019. Our project liasons have been drawing up lists of projects to rename during the outage. One big thing to keep in mind is unofficial OpenStack projects will no longer be in the "openstack" namespace. They will be placed in the 'x/' namespace instead which intends to indicate no endorsement or special ownership.
One side effect of this change (as noted in Jim's earlier email) is that we will stop replicating projects that move out of the openstack namespace. Projects that wish to be replicated to Github or anywhere else they like can do so following the steps that David Moreau-Simard put together for us here [5].
This transition is likely to be a bit bumpy particularly at the start. We'll be around after the transition to help fix unexpected errors and are likely to spend a fair bit of time at the PTG improving things as well.
Finally, to be extra clear, we intend to put http redirects in place so that all your old http(s) urls continue to work. Fungi has set this up for testing with details here [6] if you would like to ensure your urls redirect properly.
[5] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005007.htm... [6] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004921.htm...
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
i guess networking-l2gw-tempest-plugin should go to the same namespace with networking-l2gw.
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark
On Wed, Apr 17, 2019 at 12:12 AM Takashi Yamamoto <yamamoto@midokura.com> wrote:
[snip]
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment
On Wed, Apr 17, 2019 at 9:16 AM Clark Boylan <cboylan@sapwetik.org> wrote: please quickly review these planned renames for any obvious errors or issues.
i guess networking-l2gw-tempest-plugin should go to the same namespace with networking-l2gw.
+1, this should take care of it: https://review.openstack.org/#/c/653449/ // jim
On Tue, Apr 16, 2019, at 5:13 PM, Clark Boylan wrote:
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
Hello everyone! The Infra team, no, OpenDev Infra team, has completed the initial work to migrate to a more flexible git hosting platform. Gerrit is now hosted at review.opendev.org (with redirects from review.openstack.org in place). Our git mirroring has transitioned from git.openstack.org, git.airshipit.org, git.starlingx.io, and git.zuul-ci.org to http(s)://opendev.org. We have put in place redirects from these old domains to the new domain. If you see James Blair at the summit and appreciate these redirects: buy him a beverage. As part of this transition we've also moved git repos around. Airship, Zuul, OpenDev, StarlingX and others now have their own top level "orgs" which we hope cuts down on confusion over what is or isn't part of a certain project. You will likely want to update your git remotes to the new canonical locations (where ever you get redirected to using the old urls) in the near future. For unofficial projects that were hosted under openstack/ the OpenStack TC decided to move them out into a different org (namespace). The chosen namespace was x/ because it is short and doesn't convey any particular meaning. In time we can continue to use more meaningful namespaces, but for now I think we want to stabilize after the recent moves. The Zuul tenant configs report no errors (Jeremy Stanley gets the beverages for this); however, that does not mean all jobs will be happy. We will be around to help work people through job failures related to this migration. Please reach out and we'll go from there. On the infrastructure side of things we will also need to work to get our continuous deployment running again. This was a bit of an inception move for us as we do all our work through Gerrit and we had to take Gerrit down and "move" it. Finally thank you all for your patience today and thank you to everyone that helped make this possible. Clark
Thanks Clark. -----Original Message----- From: Clark Boylan <cboylan@sapwetik.org> Sent: Friday, April 19, 2019 11:09 PM To: openstack-discuss@lists.openstack.org Subject: Re: Migrating git repos to OpenDev [EXTERNAL EMAIL] On Tue, Apr 16, 2019, at 5:13 PM, Clark Boylan wrote:
The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC.
Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues.
For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped.
Hello everyone! The Infra team, no, OpenDev Infra team, has completed the initial work to migrate to a more flexible git hosting platform. Gerrit is now hosted at review.opendev.org (with redirects from review.openstack.org in place). Our git mirroring has transitioned from git.openstack.org, git.airshipit.org, git.starlingx.io, and git.zuul-ci.org to http(s)://opendev.org. We have put in place redirects from these old domains to the new domain. If you see James Blair at the summit and appreciate these redirects: buy him a beverage. As part of this transition we've also moved git repos around. Airship, Zuul, OpenDev, StarlingX and others now have their own top level "orgs" which we hope cuts down on confusion over what is or isn't part of a certain project. You will likely want to update your git remotes to the new canonical locations (where ever you get redirected to using the old urls) in the near future. For unofficial projects that were hosted under openstack/ the OpenStack TC decided to move them out into a different org (namespace). The chosen namespace was x/ because it is short and doesn't convey any particular meaning. In time we can continue to use more meaningful namespaces, but for now I think we want to stabilize after the recent moves. The Zuul tenant configs report no errors (Jeremy Stanley gets the beverages for this); however, that does not mean all jobs will be happy. We will be around to help work people through job failures related to this migration. Please reach out and we'll go from there. On the infrastructure side of things we will also need to work to get our continuous deployment running again. This was a bit of an inception move for us as we do all our work through Gerrit and we had to take Gerrit down and "move" it. Finally thank you all for your patience today and thank you to everyone that helped make this possible. Clark
"Clark Boylan" <cboylan@sapwetik.org> writes:
Hello everyone!
The Infra team, no, OpenDev Infra team, has completed the initial work to migrate to a more flexible git hosting platform. Gerrit is now hosted at review.opendev.org (with redirects from review.openstack.org in place). Our git mirroring has transitioned from git.openstack.org, git.airshipit.org, git.starlingx.io, and git.zuul-ci.org to http(s)://opendev.org. We have put in place redirects from these old domains to the new domain. If you see James Blair at the summit and appreciate these redirects: buy him a beverage.
So does that mean that old git:// URLs in remotes will need to be updated in local copies? For example, in a local working copy I have this output: $ git remote -v gerrit ssh://doug-hellmann@review.openstack.org:29418/openstack/releases.git (fetch) gerrit ssh://doug-hellmann@review.openstack.org:29418/openstack/releases.git (push) origin git://git.openstack.org/openstack/releases (fetch) origin git://git.openstack.org/openstack/releases (push) $ git remote update Fetching origin fatal: unable to connect to git.openstack.org: git.openstack.org[0: 23.253.125.17]: errno=No route to host git.openstack.org[1: 2001:4800:7817:103:be76:4eff:fe04:e3e3]: errno=Network is unreachable error: Could not fetch origin Fetching gerrit remote: Counting objects: 185, done remote: Finding sources: 100% (127/127) remote: Total 127 (delta 75), reused 103 (delta 75) Receiving objects: 100% (127/127), 54.07 KiB | 1.00 MiB/s, done. Resolving deltas: 100% (75/75), completed with 33 local objects.
From ssh://review.openstack.org:29418/openstack/releases 7f9656b69..b32f07138 master -> gerrit/master
So the gerrit remote works using review.openstack.org but the origin remote does not work using git.openstack.org. If I change the URL for the origin remote to https://opendev.org/openstack/releases it works fine. Before I do that in all of my sandboxes, do I need to, or are those old URLs expected to work? -- Doug
On 2019-04-21 20:50:16 -0400 (-0400), Doug Hellmann wrote: [...]
So does that mean that old git:// URLs in remotes will need to be updated in local copies? [...]
Yes, Gitea doesn't support traditional Git protocol, only Git over HTTP/HTTPS. And even if it had, there's no built-in redirect functionality with that protocol anyway.
If I change the URL for the origin remote to https://opendev.org/openstack/releases it works fine. Before I do that in all of my sandboxes, do I need to, or are those old URLs expected to work?
Simply switching the git:// to https:// (or http://) should work, courtesy of the redirect sites we've built for git.openstack.org and friends. -- Jeremy Stanley
Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2019-04-21 20:50:16 -0400 (-0400), Doug Hellmann wrote: [...]
So does that mean that old git:// URLs in remotes will need to be updated in local copies? [...]
Yes, Gitea doesn't support traditional Git protocol, only Git over HTTP/HTTPS. And even if it had, there's no built-in redirect functionality with that protocol anyway.
If I change the URL for the origin remote to https://opendev.org/openstack/releases it works fine. Before I do that in all of my sandboxes, do I need to, or are those old URLs expected to work?
Simply switching the git:// to https:// (or http://) should work, courtesy of the redirect sites we've built for git.openstack.org and friends.
One quick and easy way to achieve that is: git config --global url.https://git.openstack.org/.insteadof git://git.openstack.org/
On 2019-04-23 12:37:11 +0100 (+0100), Adam Spiers wrote:
Jeremy Stanley <fungi@yuggoth.org> wrote: [...]
Simply switching the git:// to https:// (or http://) should work, courtesy of the redirect sites we've built for git.openstack.org and friends.
One quick and easy way to achieve that is:
git config --global url.https://git.openstack.org/.insteadof git://git.openstack.org/
Great idea. I always forget about git's "insteadof" mapping ability. It's quite versatile. Thanks for pointing out that option! -- Jeremy Stanley
On Tue, Apr 23, 2019 at 12:37:11PM +0100, Adam Spiers wrote:
git config --global url.https://git.openstack.org/.insteadof git://git.openstack.org/
Wow I had no idea! I kinda feel like by shell script was wasted time :( Yours Tony.
On 2019-04-23 09:52:02 -0300 (-0300), Lucio Seki wrote:
Simply switching the git:// to https:// (or http://) should work, courtesy of the redirect sites we've built for git.openstack.org and friends.
For how long will this redirect work?
We haven't decided on a sunset date for the git.airshipit.org, git.openstack.org, git.starlingx.io and git.zuul-ci.org redirects to opendev.org, nor the review.openstack.org redirect to review.opendev.org. The maintenance cost for these is minimal, so I would fully expect it could be on the order of years. There's plenty of released software out there with references to these old hostnames, so we have a strong incentive to keep them around and not break users. -- Jeremy Stanley
On Sun, Apr 21, 2019 at 08:50:16PM -0400, Doug Hellmann wrote:
"Clark Boylan" <cboylan@sapwetik.org> writes:
Hello everyone!
The Infra team, no, OpenDev Infra team, has completed the initial work to migrate to a more flexible git hosting platform. Gerrit is now hosted at review.opendev.org (with redirects from review.openstack.org in place). Our git mirroring has transitioned from git.openstack.org, git.airshipit.org, git.starlingx.io, and git.zuul-ci.org to http(s)://opendev.org. We have put in place redirects from these old domains to the new domain. If you see James Blair at the summit and appreciate these redirects: buy him a beverage.
So does that mean that old git:// URLs in remotes will need to be updated in local copies? For example, in a local working copy I have this output:
Yup. I hit this also. I wrote: https://github.com/tbreeds/opendev-git-update with the help of OpenDev Infra. It will workout where the project landed if there was a namespace change, and switch to using https instead of git for origin urls. It avoids the need to re-clone repos. It also *tries* to do the right thing for current stable branches. It meets my needs but isn't quality software ;P Pull-requests welcome. It used stopped part way through so I really recommend grabbing the current master before you run it. Yours Tony.
participants (19)
-
Adam Spiers
-
Adam Young
-
Andreas Jaeger
-
Arkady.Kanevsky＠dell.com
-
Chris Dent
-
Clark Boylan
-
corvus＠inaugust.com
-
David Moreau Simard
-
Doug Hellmann
-
Ghanshyam Mann
-
Jean-Philippe Evrard
-
Jeremy Stanley
-
Jim Rollenhagen
-
Lucio Seki
-
Michael Johnson
-
Monty Taylor
-
Takashi Yamamoto
-
Thierry Carrez
-
Tony Breeds