Re: [openstack-dev] [openstack-tc][deb-packaging] Updated proposal for OpenStack deb packages
On 07/24/2015 11:07 AM, Thierry Carrez wrote: Igor Yozhikov wrote: Hello again to everyone, resending this letter due to typo in the topic of the previous letter, apologize for this. * Introductory words:* I want to present renewed proposal for packaging of OpenStack components for deb based Linux distributions. In case of stackforge retirement, I believe that new repositories for deb specs should appears under the //openstack// name-space instead of //stackforge//. This and further steps was also advised by dhellmann, anteaya and angdraug at #openstack-meeting irc channel during/after TechnicalCommittee meeting http://paste.openstack.org/show/399927/ yesterday 21 of Jul 2015. Also it would be great to discuss all of this during next TC meeting July 28th. Igor, The following was proposed to the TC, but needs a revision to match what you propose here: https://review.openstack.org/#/c/185187/ Would you mind updating the proposed change there ? That way we could discuss it at the TC next week... Done. Please note that package repository names are based on actual source package names in Debian. For example, /openstack/openstack-trove and not just trove, which refers to a Java library in Debian. Thomas P.S: I'd also would like to add that I've seen people bike-shedding around the name openstack-pkg-tools. The rename of this tool is *not* open for discussion (it would be too much work). Yes, it's Debian specific, but maybe it wont at some point, as there are tools that may be interesting for RPM guys. Even if we never do that, this (Debian native) package is prefixed by deb- like every other Git repository, so there's no way to be confused. Finally, this has *nothing* to do with the actual TC discussion, so let's discuss this issue *separately*, shall we? __ 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
Re: [openstack-dev] [openstack-tc][deb-packaging] Updated proposal for OpenStack deb packages
Igor Yozhikov wrote: Hello again to everyone, resending this letter due to typo in the topic of the previous letter, apologize for this. * Introductory words:* I want to present renewed proposal for packaging of OpenStack components for deb based Linux distributions. In case of stackforge retirement, I believe that new repositories for deb specs should appears under the //openstack// name-space instead of //stackforge//. This and further steps was also advised by dhellmann, anteaya and angdraug at #openstack-meeting irc channel during/after TechnicalCommittee meeting http://paste.openstack.org/show/399927/ yesterday 21 of Jul 2015. Also it would be great to discuss all of this during next TC meeting July 28th. Igor, The following was proposed to the TC, but needs a revision to match what you propose here: https://review.openstack.org/#/c/185187/ Would you mind updating the proposed change there ? That way we could discuss it at the TC next week... -- Thierry Carrez (ttx) __ 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
Re: [openstack-dev] [openstack-tc][deb-packaging] Updated proposal for OpenStack deb packages
Hi, I replied previously, but it looks like I messed up the formatting :). Designate is missing from this list - we are currently packaged by both Ubuntu and Debian. We have 2 repos that would need packaging - openstack/designate openstack/designate-dashboard Thanks, Graham On 22/07/15 15:12, Igor Yozhikov wrote: Hello again to everyone, resending this letter due to typo in the topic of the previous letter, apologize for this. * Introductory words:* I want to present renewed proposal for packaging of OpenStack components for deb based Linux distributions. In case of stackforge retirement, I believe that new repositories for deb specs should appears under the //openstack// name-space instead of //stackforge//. This and further steps was also advised by dhellmann, anteaya and angdraug at #openstack-meeting irc channel during/after TechnicalCommittee meeting http://paste.openstack.org/show/399927/ yesterday 21 of Jul 2015. Also it would be great to discuss all of this during next TC meeting July 28th. Link on previous letter http://lists.openstack.org/pipermail/openstack-dev/2015-July/069377.html *Renewed proposal:* During the Liberty summit in Vancouver, the idea to maintain OpenStack packages for Debian and Ubuntu on upstream infra sparked. As part of the OpenStack and Debian community we still want to push for it. In case of stackforge retirement it will be awesome to be able to work directly under the //openstack// name-space. Mostly, it is server packages for Debian which we want to see maintained there. All of the dependencies (including Oslo libraries and python-*client) will continue to be maintained using git.debian.org http://git.debian.org, as a shared effort between Debian and Ubuntu. Purpose: * One centralized place at github.com http://github.com//openstack// to maintain package build manifests/specs for main OpenStack projects. * //openstack//* already has gerrit where could be attached additional gates for building and testing OpenStack packages for deb based Linux distributions. * All changes related to the ways of how one or another OpenStack project should be installed would be represented or proposed to one place. So not only famous package maintainers can work on build manifests for packages, but also the entire community interested in packaging of OpenStack projects. Also this place could become as main base for packages for all deb based Linux distributions like Debian and Ubuntu. * Package build manifests could be reviewed or adjusted not only by package maintainers, but also by python developers, that are writing OpenStack code and that's could be very valuable due to possible changes in configuration, paths and so on. Projects list: Here I propose list of OpenStack projects, it consists of about 25 of projects which of course would be changed with time due to possible birth of new projects. Project name Possible github.com/openstack http://github.com/openstack repository ceilometer http://github.com/openstack/deb-ceilometer ceilometermiddleware http://github.com/openstack/deb-ceilometermiddleware cinder http://github.com/openstack/deb-cinder glance http://github.com/openstack/deb-glance glance_store http://github.com/openstack/deb-glance_store heat http://github.com/openstack/deb-heat horizon http://github.com/openstack/deb-horizon ironic http://github.com/openstack/deb-ironic keystone http://github.com/openstack/deb-keystone keystonemiddleware http://github.com/openstack/deb-keystonemiddleware mistral http://github.com/openstack/deb-mistral mistral-dashboard http://github.com/openstack/deb-mistral-dashboard murano http://github.com/openstack/deb-murano murano-dashboard http://github.com/openstack/deb-murano-dashboard neutron http://github.com/openstack/deb-neutron neutron-fwaas http://github.com/openstack/deb-neutron-fwaas neutron-lbaas http://github.com/openstack/deb-neutron-lbaas neutron-vpnaas http://github.com/openstack/deb-neutron-vpnaas nova http://github.com/openstack/deb-nova rally http://github.com/openstack/deb-rally sahara http://github.com/openstack/deb-sahara sahara-dashboard http://github.com/openstack/deb-sahara-dashboard swift http://github.com/openstack/deb-swift tempest http://github.com/openstack/deb-tempest trove http://github.com/openstack/deb-trove Thanks, Igor Yozhikov Senior Deployment Engineer at Mirantis http://www.mirantis.com skype: igor.yozhikov cellular: +7 901 5331200 slack: iyozhikov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
