[tripleo][tripleo-ansible] Reigniting tripleo-ansible
ekultails at gmail.com
Fri Jun 14 16:14:59 UTC 2019
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.
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!
On Wed, Jun 12, 2019 at 9:43 AM Kevin Carter <kecarter at 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 . When folks
> get a chance, I'd greatly appreciate folks have a look at these reviews.
>  - 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 at 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.).
>> Luke Short, RHCE
>> Software Engineer, OpenStack Deployment Framework
>> Red Hat, Inc.
>> On Wed, Jun 5, 2019 at 8:53 AM David Peacock <dpeacock at redhat.com> wrote:
>>> On Tue, Jun 4, 2019 at 7:53 PM Kevin Carter <kecarter at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss