Open Stack

Hi Folks – Wanted to pass this along, ahead of our team meeting today.

The agenda for today’s meeting is:

·         Update from OpenStack Board Meeting – Carol, Shamail, Rocky, Arkady, others

·         User Story Repo Update – Rocky, Shamail

o   Status on Repo

o   Walk through on Posting User Stories

·         Timeline for Posting Stores – All

o   Define calendar for Posting Stories, Group Discussion on Consolidation, Group Discussion on Prioritization

o   Can we find a 2hr block of time next week for a call to Review User Stories and Discuss Consolidation?

·         Ops Meetup Planning

o   Review current Ops Meetup agenda (below)

o   Identify areas for PWG coverage and get volunteers

Logistics: There was discussion last week about adding a voice line as an option on top of IRC. The thinking is we’ll use the IRC (as usual), an etherpad to make it easier to track action items from meeting to meeting and voice to allow more efficient discussion and ideally allow us to cover topics in our weekly meeting. Here’s the info for today’s meeting
                Time: 19ː00 - 20ː00 UTC
                IRC: #openstack-meeting
                Etherpad: https://etherpad.openstack.org/p/8_3_2015_PWG
                Voice: Access: (888) 875-9370, Bridge: 3; Passcode: 1278598

Thanks
Carol

From: Tom Fifield [mailto:tom at openstack.org]
Sent: Monday, August 03, 2015 3:48 AM
To: OpenStack Operators
Subject: [Openstack-operators] Draft Agenda for PAO Ops Meetup (August 18, 19)

Hi all,

Registrations are going well for our meetup in Palo Alto. If you're on the fence, hopefully this discussion will get you quickly over the line so you don't miss out!

http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924

So, I've taken our suggestions and attempted to wrangle them into something that would fit in the space we have over 2 days.

As a reminder, we have two different kind of sessions - General Sessions, which are discussions for the operator community aimed to produce actions (eg best practices, feedback on badness), and Working groups focus on specific topics aiming to make concrete progress on tasks in that area.

As always, some stuff has been munged and mangled in an attempt to fit it in. For example, we'd expect to talk about Kolla more generally in the context of "Using Containers for Deployment", because there are some other ways to do that too. Similarly, we'd expect the "ops project" discussion to be rolled into the session on the user committee.

Anyway, take a look at the below and reply with your comments! Is anything missing? Something look like a terrible idea? Want to completely change the room layout? There's still a little bit of flexibility at this stage.


Tuesday

Med II

Med III

Salon A

Salon B

Bacchus

9:00 - 10:00

Registration

10:00 - 10:30

Introduction

10:30 - 11:15

Burning Issues

11:15 - 11:55

Hypervisor Tuning

11:55 - 12:05

Breakout Explain

12:05 - 13:30

Lunch

13:30 - 15:00

Large Deployments Team

Burning Issues

Logging WG

Upgrades WG

Ops Guide Fixing

15:00 - 15:30

Coffee

15:30 - 16:00

Breakout Reports

16:00 - 17:00

Using Containers for Deployment

17:00 - 18:00

Lightening Talks



Wednesday

Med II

Med III

Salon A

Salon B

Bacchus

9:00 - 09:45

CMDB: use cases

9:45 - 10:30

Deployment Tips - read only slaves? admin-only API servers?

10:30 - 11:15

What network model are you using? Are you happy?

11:15 - 11:30

Coffee

11:30 - 12:15

User Committee Discussion

12:15 - 12:20

Breakout Explain

12:20 - 13:30

Lunch

13:30 - 15:00

Tools and Monitoring

Product WG

Packaging

HPC Working Group

Ops Tags Team

15:00 - 15:30

Coffee

15:30 - 16:00

Breakout Reports

16:00 - 17:00

Feedback Session, Tokyo Planning



There will be a followup email shortly regarding moderators for the sessions - thanks to those who volunteered so far!


Regards,


Tom
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.openstack.org/pipermail/product-wg/attachments/20150803/60a3ce23/attachment.txt>