Open Stack

Please do not submit a duplicated CL as I have already submitted the first
one:
https://review.openstack.org/#/c/241410/
<https://review.openstack.org/#/c/241410/>The second CL to revert the
retirement of stack forge/compass-install was not successful because the
repo now is read only. Please refer to my earlier email.

Thanks,
Xicheng
On Tuesday, November 3, 2015, Weidong.Shao <weidong.shao at huawei.com
<javascript:_e(%7B%7D,'cvml','weidong.shao at huawei.com');>> wrote:

> Will send out a CL by tomorrow morning. I am on travel now.
> On compass-monit, yes, it is to be deprecated as it has been.
>
> Thanks again for your help,
> Weidong
>
> -----Original Message-----
> From: Anita Kuno [mailto:anteaya at anteaya.info]
> Sent: Tuesday, November 03, 2015 11:45 AM
> To: Weidong Shao; Weidong.Shao; mordred at inaugust.com;
> openstack-infra at lists.openstack.org
> Subject: Re: about move of stackforge - compass-install
>
> On 10/21/2015 01:22 AM, Weidong Shao wrote:
> > Anita, Thanks for the detailed info!
> >
> > Weidong
>
> We still don't have patches up for moving this repo. We need them please.
>
> Also please reply with a clear intention that either compass-monit stays
> where it is, retired in stackforge, or it is also moved at the same time as
> compass-install. We don't want to have to do this a second time for
> compass-monit.
>
> Thank you,
> Anita.
>
> >
> > On Tue, Oct 20, 2015 at 6:40 PM Anita Kuno <anteaya at anteaya.info> wrote:
> >
> >> On 10/20/2015 07:11 PM, Weidong.Shao wrote:
> >>> Anita, Monty, and the infra-team:
> >>>
> >>> When I filled out the wiki regarding moving vs deprecating Compass
> >> related repos, I made a mistake on compass-install.
> >>> Now, is it still possible to make compass-install to openstack? We
> >>> need
> >> this for the installation of Compass.
> >>>
> >>> Thanks,
> >>> Weidong
> >>>
> >>>
> >>
> >> Somehow this didn't get posted to the openstack-infra mailing list,
> >> but I will reply including that list and hopefully it will post
> successfully.
> >>
> >> Okay so this also happened to networking-bigswitch so the patches
> >> that were offered to fix this were as follows:
> >>
> >> Someone on the infra team will have to manually change the gerrit
> >> permissions on the repo before a patch to compass-install following
> >> this pattern can merge:
> >> https://review.openstack.org/#/c/237720/
> >>
> >> This patch reverts the removal of contents for the repo:
> >> https://review.openstack.org/#/c/237741/
> >>
> >> This patch will allow the project to be moved to the openstack/
> >> namespace as active projects are no longer in stackforge:
> >> https://review.openstack.org/#/c/237753/ This patch is also linked
> here:
> >>
> >> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Pr
> >> oject_Renames
> >>
> >> In future should posts to the mailing list state activity is
> >> happening to repos, please read the posts. Further if you receive an
> >> email about your repo please read the email. If you are uncertain
> >> about the information contained in the email and what it portends for
> >> your repo, please ask. You can ask by sending an email to the
> >> openstack-infra mailing list or by asking in the #openstack-infra irc
> channel on freenode.
> >>
> >> The mass rename was a lot of work, changing repos that have been
> >> retired is also a lot of work. The repo won't be moved from the
> >> stackforge namespace until after we return from summit and then
> >> decide on another gerrit downtime window to fix this.
> >>
> >> Thank you,
> >> Anita.
> >>
> >
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20151103/2baf5ac7/attachment.html>