Open Stack

On Tue, Jun 11, 2019 at 12:12 PM Luke Short <ekultails at 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 at 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 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