Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new "transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
We're excited to get this effort rolling again and would love to work with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
[0] - https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new "transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
+1
We're excited to get this effort rolling again and would love to work with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
Most definitely in. We've had great success working with the TripleO team on integrating the Tempest role and on the OSA side, we'd be more than happy to help try and converge our roles to maintain them together.
If there's any meetings or anything that will be scheduled, I'd be happy to attend.
[0] - https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
On Mon, Jun 3, 2019 at 12:08 PM Mohammed Naser mnaser@vexxhost.com wrote:
On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it
left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded
Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new
"transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
+1
We're excited to get this effort rolling again and would love to work
with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
Most definitely in. We've had great success working with the TripleO team on integrating the Tempest role and on the OSA side, we'd be more than happy to help try and converge our roles to maintain them together.
++
If there's any meetings or anything that will be scheduled, I'd be happy to attend.
its still very early but I expect to begin regular meetings (even if they're just impromptu IRC conversations to begin with) to work out what needs to be done and where we can begin collaborating with other folks. As soon as we have more I'll be sure to reach out here and on IRC.
[0] - https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
I am really happy to hear about that as this could be much more effective than having an uncontrollable number of roles scattered across lots of repositories which usually do not play very nice with each other.
I hope that testing these roles using molecule (official ansible testing platform) is also part of this plan.
Cheers Sorin
On 3 Jun 2019, at 18:42, Kevin Carter kecarter@redhat.com wrote:
On Mon, Jun 3, 2019 at 12:08 PM Mohammed Naser <mnaser@vexxhost.com mailto:mnaser@vexxhost.com> wrote: On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter <kecarter@redhat.com mailto:kecarter@redhat.com> wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new "transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
+1
We're excited to get this effort rolling again and would love to work with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
Most definitely in. We've had great success working with the TripleO team on integrating the Tempest role and on the OSA side, we'd be more than happy to help try and converge our roles to maintain them together.
++
If there's any meetings or anything that will be scheduled, I'd be happy to attend.
its still very early but I expect to begin regular meetings (even if they're just impromptu IRC conversations to begin with) to work out what needs to be done and where we can begin collaborating with other folks. As soon as we have more I'll be sure to reach out here and on IRC.
[0] - https://review.opendev.org/662763 https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com mailto:mnaser@vexxhost.com W. http://vexxhost.com http://vexxhost.com/
Hey Sorin,
I'm glad to see you are excited as we are about this effort! Since you are one of the core developers of Molecule, I was hoping to get some of your insight on the work we have started in that regard. I have a few patches up for adding in Molecule tests to tripleo-common. At a later point in time, we can discuss the transition of moving all of the Ansible content into the tripleo-ansible repository.
https://review.opendev.org/#/c/662803/ https://review.opendev.org/#/c/662577/
The first is to add the common files that will be used across most, if not all, of the Molecule tests in this repository. The second patch is where I actually implement Molecule tests and symlinks to those common files in the first patch. I wanted to get your thoughts on a few things.
1. How would we hook in the Molecule tests into tox so that it will be tested by CI? Do you have an example of this already being done? I believe from previous discussions you have already added a few Molecule tests to a TripleO repository before. Kevin also had a good ideal of creating an isolated Zuul job so that can be something we can investigate as well. 2. How should we handle the actual tests? In the second patch, I used the playbook.yaml to write the test in a playbook format (the actual test happens during the post_tasks phase). I have always done Molecule testing this way to keep things simple. However, would you recommend that we use the Python testinfra library instead to make sure that certain things exist?
Thanks for any input you may have!
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Mon, Jun 3, 2019 at 2:29 PM Sorin Sbarnea ssbarnea@redhat.com wrote:
I am really happy to hear about that as this could be much more effective than having an uncontrollable number of roles scattered across lots of repositories which usually do not play very nice with each other.
I hope that testing these roles using molecule (official ansible testing platform) is also part of this plan.
Cheers Sorin
On 3 Jun 2019, at 18:42, Kevin Carter kecarter@redhat.com wrote:
On Mon, Jun 3, 2019 at 12:08 PM Mohammed Naser mnaser@vexxhost.com wrote:
On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where
it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded
Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new
"transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
+1
We're excited to get this effort rolling again and would love to work
with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
Most definitely in. We've had great success working with the TripleO team on integrating the Tempest role and on the OSA side, we'd be more than happy to help try and converge our roles to maintain them together.
++
If there's any meetings or anything that will be scheduled, I'd be happy to attend.
its still very early but I expect to begin regular meetings (even if they're just impromptu IRC conversations to begin with) to work out what needs to be done and where we can begin collaborating with other folks. As soon as we have more I'll be sure to reach out here and on IRC.
[0] - https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
On Mon, Jun 3, 2019 at 1:51 PM Kevin Carter kecarter@redhat.com wrote:
On Mon, Jun 3, 2019 at 12:08 PM Mohammed Naser mnaser@vexxhost.com wrote:
On Mon, Jun 3, 2019 at 12:55 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new "transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
+1
We're excited to get this effort rolling again and would love to work with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
Most definitely in. We've had great success working with the TripleO team on integrating the Tempest role and on the OSA side, we'd be more than happy to help try and converge our roles to maintain them together.
++
If there's any meetings or anything that will be scheduled, I'd be happy to attend.
its still very early but I expect to begin regular meetings (even if they're just impromptu IRC conversations to begin with) to work out what needs to be done and where we can begin collaborating with other folks. As soon as we have more I'll be sure to reach out here and on IRC.
Organizing a squad and starting with IRC meetings sounds good to me, and I'll be participating in the work. Thanks for kicking off the conversation!
On Mon, Jun 3, 2019 at 12:52 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
Count me in.
On Tue, Jun 4, 2019 at 10:08 AM David Peacock dpeacock@redhat.com wrote:
On Mon, Jun 3, 2019 at 12:52 PM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
Count me in.
+1
In doing a brief audit of the `tripleo-ansible` landscape it seems like we have many repositories [0] with little to no activity (most being simple role shells) [1].
While these repositories seem well intentioned, I'm not really sure we need them. All of these roles fall under the `tripleo-ansible` acls and, in my opinion, are at odds with the initial stated goal:
... co-locating all of the Ansible tasks/roles/libraries/plugins
throughout the code base into a single purpose-built repository ...
While I can see a place for some of these roles and could rationalize building independent, reusable, repositories I don't think we're anywhere near ready for that at this time. I also believe that when where we're ready to begin building independent role repositories we should do so collaboratively; working with the likes of Infra, OpenStack-Ansible, Kolla, Airship, and anyone else who wants to contribute.
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
[0] - https://opendev.org/openstack/project-config/src/commit/a12c6b531f58aaf9c838... [1] - https://review.opendev.org/#/q/project:%255Eopenstack/ansible-role-tripleo.*...
Kevin Carter IRC: cloudnull
On Mon, Jun 3, 2019 at 11:27 AM Kevin Carter kecarter@redhat.com wrote:
Hello Stackers,
I wanted to follow up on this post from last year, pick up from where it left off, and bring together a squad to get things moving.
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133801.html
The effort to convert tripleo Puppet and heat templates with embedded Ansible to a more consumable set of playbooks and roles is in full effect. As we're working through this effort we believe co-locating all of the Ansible tasks/roles/libraries/plugins throughout the code base into a single purpose-built repository will assist us in streamlining and simplifying. Structurally, at this time, most of tripleo will remain the same. However, the inclusion of tripleo-Ansible will allow us to create more focused solutions which are independently testable, much easier understand, and simple to include into the current heat template deployment methodologies. While a straight port of the existing Ansible tasks will not be entirely possible, the goal of this ongoing effort will be zero impact on our existing workflow and solutions.
To reigniting this effort, I've put up a review to create a new "transformation" squad[0] geared toward building the structure around tripleo-ansible[1] and converting our current solutions into roles/playbooks/libraries/plugins. Initially, we'll be focused on our existing code base; however, long term, I believe it makes sense for this squad to work across projects to breakdown deployment barriers for folks using similar technologies.
We're excited to get this effort rolling again and would love to work with anyone and everyone throughout the community. If folks are interested in this effort, please let us know.
[0] - https://review.opendev.org/662763 [1] - https://opendev.org/openstack/tripleo-ansible --
Kevin Carter IRC: cloudnull
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
With the now merged structural changes it is time to organize an official meeting to get things moving.
So without further ado: * When should we schedule our meetings (day, hour, frequency)? * Should the meeting take place in the main #tripleo channel or in one of the dedicated meeting rooms (openstack-meeting-{1,2,3,4}, etc)? * How long should our meetings last? * Any volunteers to chair meetings?
To capture some of our thoughts, questions, hopes, dreams, and aspirations I've created an etherpad which I'd like interested folks to throw ideas at: [ https://etherpad.openstack.org/p/tripleo-ansible-agenda ]. I'd like to see if we can get a confirmed list of folks who want to meet and, potentially, a generally good timezone. I'd also like to see if we can nail down some ideas for a plan of attack. While I have ideas and would be happy to talk at length about them (I wrote a few things down in the etherpad), I don't want to be the only voice given I'm new to the TripleO community (I could be, and likely I am, missing a lot of context).
Assuming we can get something flowing, I'd like to shoot for an official meeting sometime next week (the week of 17 June, 2019). In the meantime, I'll look forward to chatting with folks in the #tripleo channel.
--
Kevin Carter IRC: cloudnull
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
Hey Kevin/all,
I propose we have the meeting at 14:00 UTC weekly on Thursdays for about 30 minutes. This is similar to the normal #tripleo meeting except instead of Tuesday it is on Thursday. I believe this time will accommodate the most amount of people. Let's keep it on #tripleo instead of the OpenStack meeting rooms to avoid the concerns others have had about missing information from the TripleO community. Everyone will be kept in the loop and the IRC logs will be easy to find since it's consolidated on TripleO. I would be happy to help lead the meetings and I have also added some thoughts to the Etherpad.
How does everyone feel about having our first meeting on June 20th?
Sincerely, Luke Short
On Mon, Jun 10, 2019 at 5:02 PM Kevin Carter kecarter@redhat.com wrote:
With the now merged structural changes it is time to organize an official meeting to get things moving.
So without further ado:
- When should we schedule our meetings (day, hour, frequency)?
- Should the meeting take place in the main #tripleo channel or in one of
the dedicated meeting rooms (openstack-meeting-{1,2,3,4}, etc)?
- How long should our meetings last?
- Any volunteers to chair meetings?
To capture some of our thoughts, questions, hopes, dreams, and aspirations I've created an etherpad which I'd like interested folks to throw ideas at: [ https://etherpad.openstack.org/p/tripleo-ansible-agenda ]. I'd like to see if we can get a confirmed list of folks who want to meet and, potentially, a generally good timezone. I'd also like to see if we can nail down some ideas for a plan of attack. While I have ideas and would be happy to talk at length about them (I wrote a few things down in the etherpad), I don't want to be the only voice given I'm new to the TripleO community (I could be, and likely I am, missing a lot of context).
Assuming we can get something flowing, I'd like to shoot for an official meeting sometime next week (the week of 17 June, 2019). In the meantime, I'll look forward to chatting with folks in the #tripleo channel.
--
Kevin Carter IRC: cloudnull
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
On Tue, Jun 11, 2019 at 12:12 PM Luke Short ekultails@gmail.com wrote:
Hey Kevin/all,
I propose we have the meeting at 14:00 UTC weekly on Thursdays for about 30 minutes. This is similar to the normal #tripleo meeting except instead of Tuesday it is on Thursday. I believe this time will accommodate the most amount of people. Let's keep it on #tripleo instead of the OpenStack meeting rooms to avoid the concerns others have had about missing information from the TripleO community. Everyone will be kept in the loop and the IRC logs will be easy to find since it's consolidated on TripleO. I would be happy to help lead the meetings and I have also added some thoughts to the Etherpad.
How does everyone feel about having our first meeting on June 20th?
I've updated line 12 Etherpad with possible days/times including the one you suggested (FWIW I have a recurring conflict at that time). Maybe people who are interested can update the etherpad and we announce the winning date at the end of the week?
https://etherpad.openstack.org/p/tripleo-ansible-agenda
John
Sincerely, Luke Short
On Mon, Jun 10, 2019 at 5:02 PM Kevin Carter kecarter@redhat.com wrote:
With the now merged structural changes it is time to organize an official meeting to get things moving.
So without further ado:
- When should we schedule our meetings (day, hour, frequency)?
- Should the meeting take place in the main #tripleo channel or in one of the dedicated meeting rooms (openstack-meeting-{1,2,3,4}, etc)?
- How long should our meetings last?
- Any volunteers to chair meetings?
To capture some of our thoughts, questions, hopes, dreams, and aspirations I've created an etherpad which I'd like interested folks to throw ideas at: [ https://etherpad.openstack.org/p/tripleo-ansible-agenda ]. I'd like to see if we can get a confirmed list of folks who want to meet and, potentially, a generally good timezone. I'd also like to see if we can nail down some ideas for a plan of attack. While I have ideas and would be happy to talk at length about them (I wrote a few things down in the etherpad), I don't want to be the only voice given I'm new to the TripleO community (I could be, and likely I am, missing a lot of context).
Assuming we can get something flowing, I'd like to shoot for an official meeting sometime next week (the week of 17 June, 2019). In the meantime, I'll look forward to chatting with folks in the #tripleo channel.
--
Kevin Carter IRC: cloudnull
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
I've submitted reviews under the topic "retire-role" to truncate all of the ansible-role-tripleo-* repos, that set can be seen here [0]. When folks get a chance, I'd greatly appreciate folks have a look at these reviews.
[0] - https://review.opendev.org/#/q/topic:retire-role+status:open
--
Kevin Carter IRC: kecarter
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
Hey folks,
Since we have not gotten a lot of feedback on the times to meet-up, I have created a Google Forms survey to help us figure it out. When you get a chance, please answer this simple 1-question survey.
https://docs.google.com/forms/d/e/1FAIpQLSfHkN_T7T-W4Dhc17Pf6VHm1oUzKLJYz0u9...
Try to complete this by end-of-day Tuesday so we have an idea of when we should meet on this upcoming Thursday. Thanks for your help!
Sincerely, Luke Short
On Wed, Jun 12, 2019 at 9:43 AM Kevin Carter kecarter@redhat.com wrote:
I've submitted reviews under the topic "retire-role" to truncate all of the ansible-role-tripleo-* repos, that set can be seen here [0]. When folks get a chance, I'd greatly appreciate folks have a look at these reviews.
[0] - https://review.opendev.org/#/q/topic:retire-role+status:open
--
Kevin Carter IRC: kecarter
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
Hey folks,
The meeting time results are in! For transparency, these are the full results:
- 6 anonymous responses. Each person could vote for multiple times that best fit their schedule. - 13:00 UTC = 3 - 14:00 UTC = 3 - 15:00 UTC = 2 - 16:00 UTC = 1
Since we had a tie for UTC 13 and 14, I am referring to our Etherpad https://etherpad.openstack.org/p/tripleo-ansible-agenda for the tie breaker. The most votes were for 14:00 UTC. I look forward to meeting with everyone during that time on IRC via the #tripleo channel tomorrow!
Sincerely, Luke Short
On Fri, Jun 14, 2019 at 12:14 PM Luke Short ekultails@gmail.com wrote:
Hey folks,
Since we have not gotten a lot of feedback on the times to meet-up, I have created a Google Forms survey to help us figure it out. When you get a chance, please answer this simple 1-question survey.
https://docs.google.com/forms/d/e/1FAIpQLSfHkN_T7T-W4Dhc17Pf6VHm1oUzKLJYz0u9...
Try to complete this by end-of-day Tuesday so we have an idea of when we should meet on this upcoming Thursday. Thanks for your help!
Sincerely, Luke Short
On Wed, Jun 12, 2019 at 9:43 AM Kevin Carter kecarter@redhat.com wrote:
I've submitted reviews under the topic "retire-role" to truncate all of the ansible-role-tripleo-* repos, that set can be seen here [0]. When folks get a chance, I'd greatly appreciate folks have a look at these reviews.
[0] - https://review.opendev.org/#/q/topic:retire-role+status:open
--
Kevin Carter IRC: kecarter
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
As it turns out the edge squad has a regularly scheduled meeting on Thursday's at 14:00 UTC. So to ensure we're not creating conflict we'll select the runner up time slot and shoot to have our meetings on Thursday's at 13:00 UTC.
I've updated the wiki with our new squad [0] and linked to our running etherpad [1]. I hope this time slot works for most everyone and I look forward to meeting with you all soon.
[0] https://wiki.openstack.org/wiki/Meetings/TripleO#Squads [1] https://etherpad.openstack.org/p/tripleo-ansible-agenda
--
Kevin Carter IRC: cloudnull
On Wed, Jun 19, 2019 at 8:35 AM Luke Short ekultails@gmail.com wrote:
Hey folks,
The meeting time results are in! For transparency, these are the full results:
- 6 anonymous responses. Each person could vote for multiple times
that best fit their schedule. - 13:00 UTC = 3 - 14:00 UTC = 3 - 15:00 UTC = 2 - 16:00 UTC = 1
Since we had a tie for UTC 13 and 14, I am referring to our Etherpad https://etherpad.openstack.org/p/tripleo-ansible-agenda for the tie breaker. The most votes were for 14:00 UTC. I look forward to meeting with everyone during that time on IRC via the #tripleo channel tomorrow!
Sincerely, Luke Short
On Fri, Jun 14, 2019 at 12:14 PM Luke Short ekultails@gmail.com wrote:
Hey folks,
Since we have not gotten a lot of feedback on the times to meet-up, I have created a Google Forms survey to help us figure it out. When you get a chance, please answer this simple 1-question survey.
https://docs.google.com/forms/d/e/1FAIpQLSfHkN_T7T-W4Dhc17Pf6VHm1oUzKLJYz0u9...
Try to complete this by end-of-day Tuesday so we have an idea of when we should meet on this upcoming Thursday. Thanks for your help!
Sincerely, Luke Short
On Wed, Jun 12, 2019 at 9:43 AM Kevin Carter kecarter@redhat.com wrote:
I've submitted reviews under the topic "retire-role" to truncate all of the ansible-role-tripleo-* repos, that set can be seen here [0]. When folks get a chance, I'd greatly appreciate folks have a look at these reviews.
[0] - https://review.opendev.org/#/q/topic:retire-role+status:open
--
Kevin Carter IRC: kecarter
On Wed, Jun 5, 2019 at 11:27 AM Luke Short lshort@redhat.com wrote:
Hey everyone,
For the upcoming work on focusing on more Ansible automation and testing, I have created a dedicated #tripleo-transformation channel for our new squad. Feel free to join if you are interested in joining and helping out!
+1 to removing repositories we don't use, especially if they have no working code. I'd like to see the consolidation of TripleO specific things into the tripleo-ansible repository and then using upstream Ansible roles for all of the different services (nova, glance, cinder, etc.).
Sincerely,
Luke Short, RHCE Software Engineer, OpenStack Deployment Framework Red Hat, Inc.
On Wed, Jun 5, 2019 at 8:53 AM David Peacock dpeacock@redhat.com wrote:
On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter kecarter@redhat.com wrote:
So the questions at hand are: what, if anything, should we do with these repositories? Should we retire them or just ignore them? Is there anyone using any of the roles?
My initial reaction was to suggest we just ignore them, but on second thought I'm wondering if there is anything negative if we leave them lying around. Unless we're going to benefit from them in the future if we start actively working in these repos, they represent obfuscation and debt, so it might be best to retire / dispose of them.
David
participants (8)
-
David Peacock
-
James Slagle
-
John Fulton
-
Kevin Carter
-
Luke Short
-
Luke Short
-
Mohammed Naser
-
Sorin Sbarnea