Open Stack

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 at 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 at 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-W4Dhc17Pf6VHm1oUzKLJYz0u9ORAJYafrIGooZQ/viewform?usp=sf_link
>>
>> 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 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 [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/20190619/9af2be66/attachment-0001.html>