git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[tripleo][tripleo-ansible] Reigniting tripleo-ansible


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 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/20190610/af2f9459/attachment.html>