Greetings, As mentioned at the previous tripleo meeting [1], we're going to revisit the current tripleo squads and the expectations for those squads at the tripleo meeting. Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci A reasonable update could include the following.. 1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph? 6. others?? The squads should reflect major current efforts by the TripleO team IMHO. For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews. Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention. Thanks all!!! [1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now. Gulio? Francesco? Alan? John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
On Tue, Feb 4, 2020 at 5:45 PM John Fulton <johfulto@redhat.com> wrote:
On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit
the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now.
Gulio? Francesco? Alan?
Agree here and I also updated the etherpad as well [1] w/ our current status and the open topics we still have on ceph side. Not sure if we want to use "Integration" since the topics couldn't be only ceph related but can involve other storage components. Giulio, Alan, wdyt?
John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
[1] https://etherpad.openstack.org/p/tripleo-integration-squad-status
-- Francesco Pantano GPG KEY: F41BD75C
On Tue, Feb 4, 2020 at 11:22 AM Francesco Pantano <fpantano@redhat.com> wrote:
On Tue, Feb 4, 2020 at 5:45 PM John Fulton <johfulto@redhat.com> wrote:
On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to
revisit the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now.
Gulio? Francesco? Alan?
Agree here and I also updated the etherpad as well [1] w/ our current status and the open topics we still have on ceph side. Not sure if we want to use "Integration" since the topics couldn't be only ceph related but can involve other storage components.
Giulio, Alan, wdyt?
"Ceph integration" makes the most sense to me, but I'm fine with just naming it "Ceph" as we all know what that means. Alan
John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
[1] https://etherpad.openstack.org/p/tripleo-integration-squad-status
-- Francesco Pantano GPG KEY: F41BD75C
Is there a need for Ironic integration one? From: Alan Bishop <abishop@redhat.com> Sent: Tuesday, February 4, 2020 2:20 PM To: Francesco Pantano Cc: John Fulton; Wesley Hayutin; OpenStack Discuss; Phil Weeks Subject: Re: [tripleo] rework of triple squads and the tripleo mtg. [EXTERNAL EMAIL] On Tue, Feb 4, 2020 at 11:22 AM Francesco Pantano <fpantano@redhat.com<mailto:fpantano@redhat.com>> wrote: On Tue, Feb 4, 2020 at 5:45 PM John Fulton <johfulto@redhat.com<mailto:johfulto@redhat.com>> wrote: On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com<mailto:whayutin@redhat.com>> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now. Gulio? Francesco? Alan? Agree here and I also updated the etherpad as well [1] w/ our current status and the open topics we still have on ceph side. Not sure if we want to use "Integration" since the topics couldn't be only ceph related but can involve other storage components. Giulio, Alan, wdyt? "Ceph integration" makes the most sense to me, but I'm fine with just naming it "Ceph" as we all know what that means. Alan John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
[1] https://etherpad.openstack.org/p/tripleo-integration-squad-status -- Francesco Pantano GPG KEY: F41BD75C
Top post... OK.. so I'm going to propose we experiment with the following and if we don't like it, we can change it. I'm breaking the squads into two groups, active squads and moderately active squads. *My expectation is that the active squads are posting at the very least reviews that need attention.* #topic Active Squad status ci #link https://hackmd.io/IhMCTNMBSF6xtqiEd9Z0Kw?both validations #link https://etherpad.openstack.org/p/tripleo-validations-squad-status ceph-integration #link https://etherpad.openstack.org/p/tripleo-integration-squad-status transformation #link https://etherpad.openstack.org/p/tripleo-ansible-agenda mistral-to-ansible #link https://etherpad.openstack.org/p/tripleo-mistral-to-ansible I've added ironic integration to moderately active as it's a new request. I have no expectations for the moderately active bunch :) #topic Moderately Active Squads Ironic-integration https://etherpad.openstack.org/p/tripleo-ironic-integration-squad-status upgrade #link https://etherpad.openstack.org/p/tripleo-upgrade-squad-status edge #link https://etherpad.openstack.org/p/tripleo-edge-squad-status networking #link https://etherpad.openstack.org/p/tripleo-networking-squad-status Let's see how this plays out.. Thanks all!! On Wed, Feb 5, 2020 at 9:58 AM <Arkady.Kanevsky@dell.com> wrote:
Is there a need for Ironic integration one?
*From:* Alan Bishop <abishop@redhat.com> *Sent:* Tuesday, February 4, 2020 2:20 PM *To:* Francesco Pantano *Cc:* John Fulton; Wesley Hayutin; OpenStack Discuss; Phil Weeks *Subject:* Re: [tripleo] rework of triple squads and the tripleo mtg.
[EXTERNAL EMAIL]
On Tue, Feb 4, 2020 at 11:22 AM Francesco Pantano <fpantano@redhat.com> wrote:
On Tue, Feb 4, 2020 at 5:45 PM John Fulton <johfulto@redhat.com> wrote:
On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit
the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now.
Gulio? Francesco? Alan?
Agree here and I also updated the etherpad as well [1] w/ our current status and the open topics we still have on ceph side. Not sure if we want to use "Integration" since the topics couldn't be only ceph related but can involve other storage components.
Giulio, Alan, wdyt?
"Ceph integration" makes the most sense to me, but I'm fine with just naming it "Ceph" as we all know what that means.
Alan
John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
[1] https://etherpad.openstack.org/p/tripleo-integration-squad-status
--
Francesco Pantano GPG KEY: F41BD75C
Late to the party, but still: what's the proposed goal of the ironic integration squad? On Wed, Feb 5, 2020 at 6:00 PM <Arkady.Kanevsky@dell.com> wrote:
Is there a need for Ironic integration one?
*From:* Alan Bishop <abishop@redhat.com> *Sent:* Tuesday, February 4, 2020 2:20 PM *To:* Francesco Pantano *Cc:* John Fulton; Wesley Hayutin; OpenStack Discuss; Phil Weeks *Subject:* Re: [tripleo] rework of triple squads and the tripleo mtg.
[EXTERNAL EMAIL]
On Tue, Feb 4, 2020 at 11:22 AM Francesco Pantano <fpantano@redhat.com> wrote:
On Tue, Feb 4, 2020 at 5:45 PM John Fulton <johfulto@redhat.com> wrote:
On Tue, Feb 4, 2020 at 11:13 AM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit
the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph?
I'm fine with "Ceph". The original intent of going from "Ceph Integration" to the more generic "Integration" was that it could include anyone using external-deploy-steps to deploy non-openstack projects with TripleO (k8s, skydive, etc). Though those things happened, we didn't really get anyone else to join the squad or update our etherpad so I'm fine with renaming it to Ceph. We're still active but our etherpad was getting old. I updated it just now.
Gulio? Francesco? Alan?
Agree here and I also updated the etherpad as well [1] w/ our current status and the open topics we still have on ceph side. Not sure if we want to use "Integration" since the topics couldn't be only ceph related but can involve other storage components.
Giulio, Alan, wdyt?
"Ceph integration" makes the most sense to me, but I'm fine with just naming it "Ceph" as we all know what that means.
Alan
John
6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
[1] https://etherpad.openstack.org/p/tripleo-integration-squad-status
--
Francesco Pantano GPG KEY: F41BD75C
On Tue, Feb 4, 2020 at 6:12 PM Wesley Hayutin <whayutin@redhat.com> wrote:
Greetings,
As mentioned at the previous tripleo meeting [1], we're going to revisit the current tripleo squads and the expectations for those squads at the tripleo meeting.
Currently we have the following squads.. 1. upgrades 2. edge 3. integration 4. validations 5. networking 6. transformation 7. ci
A reasonable update could include the following..
1. validations 2. transformation 3. mistral-to-ansible 4. CI 5. Ceph / Integration?? maybe just Ceph? 6. others??
The squads should reflect major current efforts by the TripleO team IMHO.
so I agree with the notion that current efforts are discussed/reported on/summarized etc during the tripleo weekly but I'd be careful about saying 'these are the only squads'. Something like upgrades for example is still very much ongoing (though as far as I understand this is now splintered into 3 subgroups, updates, upgrades and migrations) even if they aren't reporting during the meeting as a habit. Instead of just accepting this absence and saying there is no upgrades squad, instead lets try and get them to check in to the meeting more often. I think upgrades is a special case, perhaps the above also applies to the networking squad too. Otherwise agree with your new list, but as above I'd be careful not to exclude folks that *are* working on $tripleo_stuff but for _reasons_ (likely workload/pressure) aren't coming to the tripleo weekly. just my 2c thanks
For the meetings, I would propose we use this time and space to give context to current reviews in progress and solicit feedback. It's also a good time and space to discuss any upstream blockers for those reviews.
Let's give this one week for comments etc.. Next week we'll update the etherpad list and squads. The etherpad list will be a decent way to communicate which reviews need attention.
Thanks all!!!
[1] http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-01-07-14.0...
participants (7)
-
Alan Bishop
-
Arkady.Kanevsky＠dell.com
-
Dmitry Tantsur
-
Francesco Pantano
-
John Fulton
-
Marios Andreou
-
Wesley Hayutin