Hi all,

I think it's probably a good idea to have a meeting in our scheduled slot 1400 UTC on Thurs 30th July.

I'll actually be in Beijing at the time, but I've planned to be there, but it something goes wrong, it would be great if someone could run the meeting. I think a good discussion topic is what you'd like to do for the mid-cycle ops event as we'll likely have a 90 minute in-person session.


Regards,


Tom

On 16/07/15 21:11, Tom Fifield wrote:
OK, if there isn't soon an outpouring of support for this meeting, I
think it's best cancelled :)


On 16/07/15 18:37, Maish Saidel-Keesing wrote:
I would prefer to defer today's meeting

On 07/16/15 11:17, Tom Fifield wrote:
Hi,

According to the logs from last week, which are sadly in yet another
directory: http://eavesdrop.openstack.org/meetings/_operator_tags/ , we
do have a meeting this week, but the only agenda item (Jamespage &
markbaker - thoughts on packaging) didn't pan out since markbaker wasn't
available.

Is there interest for a meeting, and any proposed topics? ops:ha?

Regards,


Tom



On 16/07/15 16:10, Maish Saidel-Keesing wrote:
Are we having a meeting today at 14:00 UTC?

On 06/29/15 07:39, Tom Fifield wrote:
Hi,

As noted last meeting, we didn't get even half way through out agenda,
so we will meet this week as well.

So, join us this Thursday Jul 2nd 1400 UTC in #openstack-meeting on
freenode
(http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150702T1400
)

To kick off with agenda item #4:
https://etherpad.openstack.org/p/ops-tags-June-2015

Previous meeting notes can be found at:
http://eavesdrop.openstack.org/meetings/ops_tags/2015/


Regards,


Tom




_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to