Re: [OpenStack-Infra] How to take over a project? (tap-as-a-service)
thank you! On Sat, Jun 23, 2018 at 5:01 AM, Anil Rao wrote: > Hi, > > Sorry for the delay in getting to this … > > I have [finally] changed the maintainer from Anil Rao to Yamamoto Takashi. > > I think this should do the trick. > > Regards, > Anil > > On Wed, May 30, 2018 at 10:52 PM, Takashi Yamamoto > wrote: >> >> hi, >> >> i want to take over tap-as-a-service project. >> >> originally the project had two leaders. but one of them (vinay) has not >> been >> responding these days. another (anil) recently told us he might not work >> on it anymore. this email has cc: to them. >> >> i think gerrit is ok as i'm already a member of tap-as-a-service-core >> group. >> >> however, for launchpad, i'm not sure who can change the permissions. >> can the infra team help? >> the LP project is this one: https://launchpad.net/tap-as-a-service >> >> thank you. > > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] How to take over a project? (tap-as-a-service)
hi, i want to take over tap-as-a-service project. originally the project had two leaders. but one of them (vinay) has not been responding these days. another (anil) recently told us he might not work on it anymore. this email has cc: to them. i think gerrit is ok as i'm already a member of tap-as-a-service-core group. however, for launchpad, i'm not sure who can change the permissions. can the infra team help? the LP project is this one: https://launchpad.net/tap-as-a-service thank you. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] tag/branch removal request for networking-midonet
hi, sorry for dropping the ball so long. On Fri, Apr 15, 2016 at 1:46 AM, Clark Boylan wrote: > On Wed, Apr 13, 2016, at 11:05 PM, Takashi Yamamoto wrote: >> hi, >> >> please remove tags and branches on networking-midonet repository, >> listed in "Bug Description" in the following bugs. >> https://bugs.launchpad.net/networking-midonet/+bug/1552036 >> https://bugs.launchpad.net/networking-midonet/+bug/1569797 > > Tag deletion isn't typically supported because deleting tags on our > Gerrit server does not remove the tags from any downstream repos. As I > understand it the PBR 1.9.1 release addressed the issues with these tags > and PBR. Can you confirm that this is working now and if so close the > tag deletion bug as wontfix or invalid? done. > > For the branch deletions did you want to make tags for the tips of those > branches so that they are not lost on garbage collection? no. such tags are not necessary. please just remove these branches. thank you. > > Clark ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
On Wed, Feb 1, 2017 at 9:51 AM, Takashi Yamamoto wrote: > hi, > >>> That's great to hear Yamamoto. Since you are already a neutron-core I assume >>> you are already intimate with the work required to strengthen the VPNaaS >>> project. I have added you to [4] and you can lean on me for any changes that >>> needs reviewing. > > i wrote a scenario test. > https://review.openstack.org/#/c/424459/ > while it's working well with midonet, it seems failing with strongswan driver. > is there any possibly related known issues with strongswan? https://bugs.launchpad.net/neutron/+bug/1660899 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
hi, >> That's great to hear Yamamoto. Since you are already a neutron-core I assume >> you are already intimate with the work required to strengthen the VPNaaS >> project. I have added you to [4] and you can lean on me for any changes that >> needs reviewing. i wrote a scenario test. https://review.openstack.org/#/c/424459/ while it's working well with midonet, it seems failing with strongswan driver. is there any possibly related known issues with strongswan? ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
hi, On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > Hi > > As of today, the project neutron-vpnaas is no longer part of the neutron > governance. This was a decision reached after the project saw a dramatic > drop in active development over a prolonged period of time. > > What does this mean in practice? > > From a visibility point of view, release notes and documentation will no > longer appear on openstack.org as of Ocata going forward. > No more releases will be published by the neutron release team. > The neutron team will stop proposing fixes for the upstream CI, if not > solely on a voluntary basis (e.g. I still felt like proposing [2]). > > How does it affect you, the user or the deployer? > > You can continue to use vpnaas and its CLI via the python-neutronclient and > expect it to work with neutron up until the newton > release/python-neutronclient 6.0.0. After this point, if you want a release > that works for Ocata or newer, you need to proactively request a release > [5], and reach out to a member of the neutron release team [3] for approval. i want to make an ocata release. (and more importantly the stable branch, for the benefit of consuming subprojects) for the purpose, the next step would be ocata-3, right? > Assuming that the vpnaas CI is green, you can expect to have a working > vpnaas system upon release of its package in the foreseeable future. > Outstanding bugs and new bug reports will be rejected on the basis of lack > of engineering resources interested in helping out in the typical OpenStack > review workflow. > Since we are freezing the development of the neutron CLI in favor of the > openstack unified client (OSC), the lack of a plan to make the VPN commands > available in the OSC CLI means that at some point in the future the neutron > client CLI support for vpnaas may be dropped (though I don't expect this to > happen any time soon). > > Can this be reversed? > > If you are interested in reversing this decision, now it is time to step up. > That said, we won't be reversing the decision for Ocata. There is quite a > curve to ramp up to make neutron-vpnaas worthy of being classified as a > neutron stadium project, and that means addressing all the gaps identified > in [6]. If you are interested, please reach out, and I will work with you to > add your account to [4], so that you can drive the neutron-vpnaas agenda > going forward. > > Please do not hesitate to reach out to ask questions and/or clarifications. > > Cheers, > Armando > > [1] https://review.openstack.org/#/c/392010/ > [2] https://review.openstack.org/#/c/397924/ > [3] https://review.openstack.org/#/admin/groups/150,members > [4] https://review.openstack.org/#/admin/groups/502,members > [5] https://github.com/openstack/releases > [6] > http://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-vpnaas.html > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
On Thu, Dec 1, 2016 at 1:02 AM, Armando M. wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: >> > Hi >> > >> > As of today, the project neutron-vpnaas is no longer part of the neutron >> > governance. This was a decision reached after the project saw a dramatic >> > drop in active development over a prolonged period of time. >> > >> > What does this mean in practice? >> > >> > From a visibility point of view, release notes and documentation will no >> > longer appear on openstack.org as of Ocata going forward. >> > No more releases will be published by the neutron release team. >> > The neutron team will stop proposing fixes for the upstream CI, if not >> > solely on a voluntary basis (e.g. I still felt like proposing [2]). >> > >> > How does it affect you, the user or the deployer? >> > >> > You can continue to use vpnaas and its CLI via the python-neutronclient >> > and >> > expect it to work with neutron up until the newton >> > release/python-neutronclient 6.0.0. After this point, if you want a >> > release >> > that works for Ocata or newer, you need to proactively request a release >> > [5], and reach out to a member of the neutron release team [3] for >> > approval. >> > Assuming that the vpnaas CI is green, you can expect to have a working >> > vpnaas system upon release of its package in the foreseeable future. >> > Outstanding bugs and new bug reports will be rejected on the basis of >> > lack >> > of engineering resources interested in helping out in the typical >> > OpenStack >> > review workflow. >> > Since we are freezing the development of the neutron CLI in favor of the >> > openstack unified client (OSC), the lack of a plan to make the VPN >> > commands >> > available in the OSC CLI means that at some point in the future the >> > neutron >> > client CLI support for vpnaas may be dropped (though I don't expect this >> > to >> > happen any time soon). >> > >> > Can this be reversed? >> > >> > If you are interested in reversing this decision, now it is time to step >> > up. >> > That said, we won't be reversing the decision for Ocata. There is quite >> > a >> > curve to ramp up to make neutron-vpnaas worthy of being classified as a >> > neutron stadium project, and that means addressing all the gaps >> > identified >> > in [6]. If you are interested, please reach out, and I will work with >> > you to >> > add your account to [4], so that you can drive the neutron-vpnaas agenda >> > going forward. >> > >> > Please do not hesitate to reach out to ask questions and/or >> > clarifications. >> >> hi, >> >> i'm interested in working on the project. >> well, at least on the parts which is used by networking-midonet. > > > That's great to hear Yamamoto. Since you are already a neutron-core I assume > you are already intimate with the work required to strengthen the VPNaaS > project. I have added you to [4] and you can lean on me for any changes that > needs reviewing. these fixes for gate jobs need review: https://review.openstack.org/#/c/410511/ https://review.openstack.org/#/c/410530/ https://review.openstack.org/#/c/419396/ > >> >> >> > >> > Cheers, >> > Armando >> > >> > [1] https://review.openstack.org/#/c/392010/ >> > [2] https://review.openstack.org/#/c/397924/ >> > [3] https://review.openstack.org/#/admin/groups/150,members >> > [4] https://review.openstack.org/#/admin/groups/502,members >> > [5] https://github.com/openstack/releases >> > [6] >> > >> > http://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-vpnaas.html >> > >> > >> > __ >> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
On Thu, Dec 1, 2016 at 1:02 AM, Armando M. wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: >> > Hi >> > >> > As of today, the project neutron-vpnaas is no longer part of the neutron >> > governance. This was a decision reached after the project saw a dramatic >> > drop in active development over a prolonged period of time. >> > >> > What does this mean in practice? >> > >> > From a visibility point of view, release notes and documentation will no >> > longer appear on openstack.org as of Ocata going forward. >> > No more releases will be published by the neutron release team. >> > The neutron team will stop proposing fixes for the upstream CI, if not >> > solely on a voluntary basis (e.g. I still felt like proposing [2]). >> > >> > How does it affect you, the user or the deployer? >> > >> > You can continue to use vpnaas and its CLI via the python-neutronclient >> > and >> > expect it to work with neutron up until the newton >> > release/python-neutronclient 6.0.0. After this point, if you want a >> > release >> > that works for Ocata or newer, you need to proactively request a release >> > [5], and reach out to a member of the neutron release team [3] for >> > approval. >> > Assuming that the vpnaas CI is green, you can expect to have a working >> > vpnaas system upon release of its package in the foreseeable future. >> > Outstanding bugs and new bug reports will be rejected on the basis of >> > lack >> > of engineering resources interested in helping out in the typical >> > OpenStack >> > review workflow. >> > Since we are freezing the development of the neutron CLI in favor of the >> > openstack unified client (OSC), the lack of a plan to make the VPN >> > commands >> > available in the OSC CLI means that at some point in the future the >> > neutron >> > client CLI support for vpnaas may be dropped (though I don't expect this >> > to >> > happen any time soon). >> > >> > Can this be reversed? >> > >> > If you are interested in reversing this decision, now it is time to step >> > up. >> > That said, we won't be reversing the decision for Ocata. There is quite >> > a >> > curve to ramp up to make neutron-vpnaas worthy of being classified as a >> > neutron stadium project, and that means addressing all the gaps >> > identified >> > in [6]. If you are interested, please reach out, and I will work with >> > you to >> > add your account to [4], so that you can drive the neutron-vpnaas agenda >> > going forward. >> > >> > Please do not hesitate to reach out to ask questions and/or >> > clarifications. >> >> hi, >> >> i'm interested in working on the project. >> well, at least on the parts which is used by networking-midonet. > > > That's great to hear Yamamoto. Since you are already a neutron-core I assume > you are already intimate with the work required to strengthen the VPNaaS > project. I have added you to [4] and you can lean on me for any changes that > needs reviewing. thank you. > >> >> >> > >> > Cheers, >> > Armando >> > >> > [1] https://review.openstack.org/#/c/392010/ >> > [2] https://review.openstack.org/#/c/397924/ >> > [3] https://review.openstack.org/#/admin/groups/150,members >> > [4] https://review.openstack.org/#/admin/groups/502,members >> > [5] https://github.com/openstack/releases >> > [6] >> > >> > http://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-vpnaas.html >> > >> > >> > __ >> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance
On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: > Hi > > As of today, the project neutron-vpnaas is no longer part of the neutron > governance. This was a decision reached after the project saw a dramatic > drop in active development over a prolonged period of time. > > What does this mean in practice? > > From a visibility point of view, release notes and documentation will no > longer appear on openstack.org as of Ocata going forward. > No more releases will be published by the neutron release team. > The neutron team will stop proposing fixes for the upstream CI, if not > solely on a voluntary basis (e.g. I still felt like proposing [2]). > > How does it affect you, the user or the deployer? > > You can continue to use vpnaas and its CLI via the python-neutronclient and > expect it to work with neutron up until the newton > release/python-neutronclient 6.0.0. After this point, if you want a release > that works for Ocata or newer, you need to proactively request a release > [5], and reach out to a member of the neutron release team [3] for approval. > Assuming that the vpnaas CI is green, you can expect to have a working > vpnaas system upon release of its package in the foreseeable future. > Outstanding bugs and new bug reports will be rejected on the basis of lack > of engineering resources interested in helping out in the typical OpenStack > review workflow. > Since we are freezing the development of the neutron CLI in favor of the > openstack unified client (OSC), the lack of a plan to make the VPN commands > available in the OSC CLI means that at some point in the future the neutron > client CLI support for vpnaas may be dropped (though I don't expect this to > happen any time soon). > > Can this be reversed? > > If you are interested in reversing this decision, now it is time to step up. > That said, we won't be reversing the decision for Ocata. There is quite a > curve to ramp up to make neutron-vpnaas worthy of being classified as a > neutron stadium project, and that means addressing all the gaps identified > in [6]. If you are interested, please reach out, and I will work with you to > add your account to [4], so that you can drive the neutron-vpnaas agenda > going forward. > > Please do not hesitate to reach out to ask questions and/or clarifications. hi, i'm interested in working on the project. well, at least on the parts which is used by networking-midonet. > > Cheers, > Armando > > [1] https://review.openstack.org/#/c/392010/ > [2] https://review.openstack.org/#/c/397924/ > [3] https://review.openstack.org/#/admin/groups/150,members > [4] https://review.openstack.org/#/admin/groups/502,members > [5] https://github.com/openstack/releases > [6] > http://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-vpnaas.html > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] tag/branch removal request for networking-midonet
hi, please remove tags and branches on networking-midonet repository, listed in "Bug Description" in the following bugs. https://bugs.launchpad.net/networking-midonet/+bug/1552036 https://bugs.launchpad.net/networking-midonet/+bug/1569797 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] removal of EOL branches for networking-midonet
On Fri, Feb 5, 2016 at 2:13 AM, Clark Boylan wrote: > On Wed, Feb 3, 2016, at 09:16 AM, Takashi Yamamoto wrote: >> hi, >> >> please retire icehouse and juno branches on networking-midonet repo. >> >> the corresponding eol tags are already in place. >> http://git.openstack.org/cgit/openstack/networking-midonet/tag/?h=icehouse-eol >> http://git.openstack.org/cgit/openstack/networking-midonet/tag/?h=juno-eol >> >> a relevant project-config patch: https://review.openstack.org/#/c/272005/ >> > The stable/icehouse and stable/juno branches on networking-midonet have > been deleted. > > Clark thank you! ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] removal of EOL branches for networking-midonet
hi, please retire icehouse and juno branches on networking-midonet repo. the corresponding eol tags are already in place. http://git.openstack.org/cgit/openstack/networking-midonet/tag/?h=icehouse-eol http://git.openstack.org/cgit/openstack/networking-midonet/tag/?h=juno-eol a relevant project-config patch: https://review.openstack.org/#/c/272005/ ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
