Re: [openstack-dev] [tc][kolla] Adding new deliverables

enstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables Michał Jastrzębski wrote: > So from my point of view, while I understand why project separation > makes sense in the long run, I will argue that at this moment i

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Michał Jastrzębski wrote: > So from my point of view, while I understand why project separation > makes sense in the long run, I will argue that at this moment it will > be hurtful for the project. Our community is still fairly integrated, > and I'd love to keep it this way a while longer. We

Re: [openstack-dev] [tc][kolla] Adding new deliverables

tt Houser (bhouser)" <bhou...@cisco.com>, "Steven Dake > (stdake)" <std...@cisco.com>, "OpenStack Development Mailing List (not > for usage questions)" <openstack-dev@lists.openstack.org> > > *Subject: *Re: [openstack-dev] [tc][kolla]

Re: [openstack-dev] [tc][kolla] Adding new deliverables

;Britt Houser (bhouser)" <bhou...@cisco.com>, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables To your point Steve, then I’d image that Kolla would hav

Re: [openstack-dev] [tc][kolla] Adding new deliverables

ent Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables To your point Steve, then I’d image that Kolla would have no objection to the introduction of other Openstack-namespace projects that provide alter

Re: [openstack-dev] [tc][kolla] Adding new deliverables

: "Britt Houser (bhouser)" <bhou...@cisco.com>, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables To your point Steve, then I’d image that Kolla would have no obje

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Regards >> -steve >> >> -Original Message----- >> From: Thierry Carrez <thie...@openstack.org> >> Organization: OpenStack >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" >> <openstack-dev@lists.openstack.o

Re: [openstack-dev] [tc][kolla] Adding new deliverables

iginal Message- >> From: Thierry Carrez <thie...@openstack.org> >> Organization: OpenStack >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> >> Date: Wednesday, January 11

Re: [openstack-dev] [tc][kolla] Adding new deliverables

k-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables Excerpts from Steven Dake (stdake)'s message of 2017-01-11 14:50:31 +: > Thierry, > > I am not a big fan of the separate gerrit teams we have instituted inside the Kolla project.

Re: [openstack-dev] [tc][kolla] Adding new deliverables

sounds wrong to me. >> >> I hope my position is clear ☺ If not, feel free to ask any follow-up >> questions. >> >> Regards >> -steve >> >> -Original Message- >> From: Thierry Carrez <thie...@openstack.org> >> Organization: Ope

Re: [openstack-dev] [tc][kolla] Adding new deliverables

v@lists.openstack.org> > Date: Wednesday, January 11, 2017 at 4:21 AM > To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables > > Michał Jastrzębski wrote: > &g

Re: [openstack-dev] [tc][kolla] Adding new deliverables

gt; Regards > -steve > > > -Original Message- > From: Thierry Carrez <thie...@openstack.org> > Organization: OpenStack > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Wednesd

Re: [openstack-dev] [tc][kolla] Adding new deliverables

<openstack-dev@lists.openstack.org> Date: Wednesday, January 11, 2017 at 4:21 AM To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables Michał Jastrzębski wrote: > I created CIVS poll with optio

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Thierry Carrez wrote: > [...] > The fact that you're having hard discussions in Kolla about "adding new > deliverables" produced by distinct groups of people indicates that you > may be using Kolla as an old-style "program" rather than as a single > team. Why not set them up as separate project

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Michał Jastrzębski wrote: > I created CIVS poll with options we discussed. Every core member should > get link to poll voting, if that's not the case, please let me know. Just a quick sidenote to explain how the "big-tent" model of governance plays in here... In the previous project structure

Re: [openstack-dev] [tc][kolla] Adding new deliverables

.org> > *Date: *Thursday, January 5, 2017 at 9:06 PM > > *To: *"OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > *Subject: *Re: [openstack-dev] [tc][kolla] Adding new deliverables > > > > I'll reply

Re: [openstack-dev] [tc][kolla] Adding new deliverables

<openstack-dev@lists.openstack.org> Date: Thursday, January 5, 2017 at 9:06 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables I'll reply to Britts comments, and

Re: [openstack-dev] [tc][kolla] Adding new deliverables

k Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > *Subject: *Re: [openstack-dev] [tc][kolla] Adding new deliverables > > > > Also coming from the perspective of a Kolla-Kubernetes contributor, I am > worried about the sc

Re: [openstack-dev] [tc][kolla] Adding new deliverables

t;OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, January 5, 2017 at 6:47 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Also coming from the perspective of a Kolla-Kubernetes contributor, I am worried about the scope that Kolla is extending itself to. Moving from a single repo to multiple repo's has made the situation much better, but by operating under a single umbrella I feel that we may potentially be

Re: [openstack-dev] [tc][kolla] Adding new deliverables

There are some interesting points in this topic. I agree entirely with Sam Yaple. It does not make sense to me to have kolla-ansible and kolla-kubernetes cores involved with the introduction of a new deliverable under the kolla umbrella. A new deliverable (read: project, really) should not rely

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Michał Jastrzębski's message of 2017-01-05 11:45:49 -0800: > I think total separation of projects would require much larger > discussion in community. Currently we agreed on having kolla-ansible > and kolla-k8s to be deliverables under kolla umbrella from historical > reasons. Also I

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 7:42 PM, Doug Hellmann wrote: > Excerpts from Sam Yaple's message of 2017-01-05 18:22:54 +: > > On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann > wrote: > > > > > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 7:45 PM, Michał Jastrzębski wrote: > I think total separation of projects would require much larger > discussion in community. Currently we agreed on having kolla-ansible > and kolla-k8s to be deliverables under kolla umbrella from historical > reasons.

Re: [openstack-dev] [tc][kolla] Adding new deliverables

I think total separation of projects would require much larger discussion in community. Currently we agreed on having kolla-ansible and kolla-k8s to be deliverables under kolla umbrella from historical reasons. Also I don't agree that there is "little or no overlap" in teams, in fact there is ton

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 18:22:54 +: > On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann wrote: > > > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > > > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley > > wrote:

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 6:12 PM, Doug Hellmann wrote: > Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley > wrote: > > > > > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > > >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Excerpts from Sam Yaple's message of 2017-01-05 17:02:35 +: > On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley wrote: > > > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > > [...] > > > I do feel this is slightly different than whats described. Since it is > > not >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 5:56 PM, Alex Schultz wrote: > On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski > wrote: > > Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, > > there is no reason in my mind for kolla-ansible/k8s core team to

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Oh you misunderstood good sir;) kolla-puppet is similar to tripleo - it's would set up whole OpenStack using kolla containers deployed by puppet manifests. I agree, if it would only install kolla - that should go to openstack puppet, but kolla is a deployment tool. On 5 January 2017 at 09:56,

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski wrote: > Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, > there is no reason in my mind for kolla-ansible/k8s core team to vote > on accepting new deliverable. I think this should be lightweight and > easy,

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, there is no reason in my mind for kolla-ansible/k8s core team to vote on accepting new deliverable. I think this should be lightweight and easy, we should allow experimentation (after all, kolla itself went through few fail

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 4:54 PM, Jeremy Stanley wrote: > On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: > [...] > > I do feel this is slightly different than whats described. Since it is > not > > unrelated services, but rather, for lack of a better word, competing > >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> >> Date: Wednesday, January 4, 2017 at 3:38 PM >> To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org> >> Subject

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On 2017-01-05 16:46:36 + (+), Sam Yaple wrote: [...] > I do feel this is slightly different than whats described. Since it is not > unrelated services, but rather, for lack of a better word, competing > services. To my knowledge infra doesn't have several service doing the same > job with

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 4:34 PM, Jeremy Stanley wrote: > On 2017-01-05 15:58:45 + (+), Sam Yaple wrote: > > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt > > (or kolla-puppet, or kolla-chef) is silly since the projects are > unrelated. >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

ay. > > > > > > Regards > > > -steve > > > > > > -Original Message- > > > From: Michał Jastrzębski <inc...@gmail.com> > > > Reply-To: "OpenStack Development Mailing List (not for usage > questions)" < >

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On 2017-01-05 15:58:45 + (+), Sam Yaple wrote: > Involving kolla-ansible and kolla-kubernetes in a decision about kolla-salt > (or kolla-puppet, or kolla-chef) is silly since the projects are unrelated. > That would be like involving glance when cinder has a new service because > they both

Re: [openstack-dev] [tc][kolla] Adding new deliverables

gt; > Regards > > -steve > > > > -Original Message- > > From: Michał Jastrzębski <inc...@gmail.com> > > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > > openstack-dev@lists.openstack.org> > > Date: Wedne

Re: [openstack-dev] [tc][kolla] Adding new deliverables

or usage questions)" < > openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [tc][kolla] Adding new deliverables > > Hello, > > New deliverable to Kolla was proposed, and we found ourselves in a bit > of an impasse regarding process of accepting new d

Re: [openstack-dev] [tc][kolla] Adding new deliverables

ary 4, 2017 at 3:38 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [tc][kolla] Adding new deliverables Hello, New deliverable to Kolla was proposed, and we found ourselves in a bit of an impa

Re: [openstack-dev] [tc][kolla] Adding new deliverables

As the person purposing kolla-salt, I would like to weigh in. I like the idea of option 2, I certainly feel the PTL should always be involved in these things. I would also agree with the pre-1.0 as dev/experimental so as to not be tightly bound by rules for more stable and long term projects

[openstack-dev] [tc][kolla] Adding new deliverables

Hello, New deliverable to Kolla was proposed, and we found ourselves in a bit of an impasse regarding process of accepting new deliverables. Kolla community grew a lot since we were singular project, and now we have 3 deliverables already (kolla, kolla-ansible and kolla-kubernetes). 4th one was