On 10/22/15, 5:18 AM, "Jastrzebski, Michal" <michal.jastrzeb...@intel.com> wrote:
>Hello, > >I have looked at this code and it seems pretty solid. I'm not sure if it >will be ready for governance as-is, there are few things I think have to >be addressed before (for example I'm not sure if ansible can be >dependency due to its license). Having said that I'd be happy to see it >in our codebase as it will help kolla's user experience a lot. > >So +1 from me, thanks guys for it! > >Let's discuss what has to be done to get it into openstack asap, and then >next steps. I'd like to volunteer to help you with that guys. > >Regard The process to add it is simple. If a majority of the core reviewers vote to accept the code, someone (you volunteered?) submits a project-config repo addition with an upstream of the proper git upstream repo to the target of kolla-pythonclient. I submit a change to the governance repo first to inform the TC and broader community we are including a new repository in our managed repo list. Regards -steve >s, >Michał > >> -----Original Message----- >> From: Paul Bourke [mailto:paul.bou...@oracle.com] >> Sent: Thursday, October 22, 2015 10:42 AM >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [kolla] Integrating kollacli as >>python-kollaclient >> >> Having used the cli for some time I can vouch for it being very useful, >>and >> usable. The guys have done a nice job of giving it an "OpenStack feel", >> mimicking the patterns used in openstackclient and the like. >> >> It should give users a more polished introduction to Kolla. >> >> +1 >> >> -Paul >> >> On 21/10/15 23:20, Steven Dake (stdake) wrote: >> > Hello Folks, >> > >> > >> > Oracle has developed a CLI tool for managing OpenStack Kolla clusters. >> > Several months ago at our midcycle, the topic was brought up an I >> > suggested to go ahead and get started on the work. We clearly didn't >> > spend enough time discussing how it should be integrated into the code >> > base or developed or even what its features should be, and that is my >>error. >> > >> > >> > What ended up happening is sort of a code dump, which is not ideal, >> > but I can only work so many 20 hour days ;) I didn't believe our >> > community had the bandwidth to deal with integrating a CLI directly >> > into the tree while we were focused on our major objective of >> > implementing Ansible deployment of OpenStack in Docker containers. >> > Possibly the wrong call, but it is what it is and it is my error, not >>Oracles. >> > >> > >> > The code can be cloned from: >> > >> > git clone git://oss.oracle.com/git/openstack-kollacli.git >> > >> > >> > The code as is is very high quality but will likely need to go through >> > alot of refactoring to ReST-ify it. There are two major authors of >> > the code, Borne Mace and Steve Noyes. >> > >> > >> > I'd like a majority vote from the core team as to whether we should >> > add this repository to our list of governed repositories in the >> > OpenStack Kolla governance repository here: >> > >> > >> > https://github.com/openstack/governance/blob/master/reference/projects >> > .yaml#L1509 >> > >> > >> > Consider this email a +1 vote from me. >> > >> > >> > A completely separate email thread and decision will be made by the >> > community about core team membership changes to handle maintenance of >> > the code. Assuming this code is voted into Kolla's governance, I plan >> > to propose Borne as a core reviewer, which will be open to core team >> > vote as a separate act with our 3 +1 votes no vetos within 1 week >> > period. We will address that assuming a majority vote of the code >> > merge wins. Steve can follow the normal processes for joining the >> > core team if he wishes (reviewing patches) - clearly his code >> > contributions are there. Borne already does some reviews, and >> > although he isn't a top reviewer, he does have some contribution in >> > this area making it into the top 10 for the Liberty cycle. >> > >> > >> > >> > Kolla CLI Features: >> > >> > * dynamic ansible inventory manipulation via the host, group and >> > service commands >> > * ssh key push via the host setup command >> > * ssh key validation via the host check command >> > * ansible deployment via the deploy command >> > * property viewing and modification with the property list, set and >> > clear commands >> > * cleanup of docker containers on a single, multiple or all hosts >>via >> > the host destroy command >> > * debug data collection via the dump command >> > * configuration of openstack passwords via the password command >> > * Lines of python = 2700 >> > * Lines of test case code = 1800 >> > * ~ 200 commits >> > >> > >> > >> > >> > >> ________________________________________________________________ >> ______ >> > ____ 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 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
