Open Stack

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 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.).
>
> Sincerely,
>
> 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.
>>
>> David
>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190612/e36d508c/attachment.html>