[Openstack-operators] [Telco][NFV] Telco Working Group meetings suspended

[Steve Gordon]

Hi all,

As discussed at this week's meeting [1] all user stories have now been moved 
from telcowg-usecases to openstack-userstories and we will be suspending the 
Telco Working Group meetings moving forward. Participants are encouraged to 
attend one of the two weekly Product Working Group meeting times [2] to discuss 
and advocate for the relevant user stories going forward. Please also note that 
there is a product-wg mailing list [3] for discussion of same.

For those attending summit please note these collaboration sessions:

* OPNFV and OpenStack Collaboration BoF [4]
* Ops: NFV/Telco [5]

Thanks,

Steve

[1] 
http://eavesdrop.openstack.org/meetings/telcowg/2016/telcowg.2016-04-13-14.01.html
[2] http://eavesdrop.openstack.org/#OpenStack_Product_WG
[3] http://lists.openstack.org/pipermail/product-wg/
[4] 
https://www.openstack.org/summit/austin-2016/summit-schedule/events/7510?goback=1
[5] 
https://www.openstack.org/summit/austin-2016/summit-schedule/events/9522?goback=1


- Original Message -
> From: "Steve Gordon" 
> 
> - Original Message -
> > From: "Calum Loudon" 
> > 
> > Thanks Steve
> > 
> > I agree with moving to the PWG.
> > 
> > On that topic, do you know what's happened to some of the user stories we
> > proposed, specifically https://review.openstack.org/#/c/290060/ and
> > https://review.openstack.org/#/c/290347/?  Neither shows up in
> > https://review.openstack.org/#/q/status:open+project:openstack/openstack-user-stories
> 
> This query includes status:open, and those two reviews were merged already so
> they don't show up.
> 
> > but there is a https://review.openstack.org/#/c/290991/ which seems to be a
> > copy of https://review.openstack.org/#/c/290060/ with the template help
> > text
> > added back in and no mention of the original?
> 
> From Shamail's comment in 290991:
> 
> This change should be used to discuss and refine the concept. Can the
> user story owner please make a minor change to show ownership?
> 
> Basically they opened new reviews with a minor change to trigger further
> discussion. I'm not in love with this approach versus just discussing it on
> the original move request but it is the way it is being done for now. W.r.t.
> 290060 I believe you probably meant to include another link but I imagine
> the situation is the same.
> 
> -Steve

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

[Openstack-operators] [Neutron] Operator Pain Points

[Carl Baldwin]

I'm cross-posting this to the dev and operators mailing lists.

In the upcoming design summit in Austin, I'll be hosting a session [1]
to discuss how to prioritize operator pain points around Neutron, find
owners, and plan them for Newton.  In preparation for that discussion,
I have performed a preliminary search in Launchpad for existing
operator pain points.  I made a list of existing issues with the
following tags: "loadimpact", "ops", "troubleshooting", and
"usability".  This is a subset of standard tags used within the
Neutron project [2]:

I have posted that list to the etherpad for the session [3] grouped by
their importance as marked at the time I queried.

Please check the etherpad [3] to see if your pain points are
represented.  If they are not, please find the launchpad bug for your
issue, or create a new one if it does not exist.  Add the URL

I am looking forward to a well organized and productive discussion at
the summit and I'm eager to see you all there.

Carl Baldwin

[1] https://www.openstack.org/summit/austin-2016/summit-schedule/events/9103
[2] 
http://docs.openstack.org/developer/neutron/policies/bugs.html#proposing-new-tags
[3] https://etherpad.openstack.org/p/newton-neutron-pain-points

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

Re: [Openstack-operators] Draft Agenda for AUS Ops@Summit

[darren chan]

Hi Tom,
Thanks for organizing the schedule. Is possible to move the Ops: Docs or the 
Ops: Liberty upgrade session to a different timeslot ? I know a few people who 
would like to attend both sessions. 
Thanks!  
On Wednesday, 13 April 2016, 22:40, Tom Fifield  wrote:
 

 All,

just a quick note to say this is now on the official agenda:

https://www.openstack.org/summit/austin-2016/summit-schedule/#event_types=13,14,15


Don't forget to download your summit app - it has caching magic.


Regards,


Tom

On 08/04/16 12:32, Tom Fifield wrote:
> OK, we've had moderator confirmation for many sessions, so I'm going to
> start putting this on the official agenda and setting up some etherpads :)
>
> Still haven't heard anyone interested in Ceph or Swift.
>
>
> Monday     Salon E (112)     Salon D (112)     MR406 (98)     MR409 (55)     
> MR410
> (38)     MR412 (38)
> 11:15 - 11:55     Logging: if you could get one thing fixed this cycle,
> what would it be?     Liberty upgrades - what worked, what didn't, what
> would we do differently next time     Docs: should the Ops Guide have a new
> revision?     Large Deployments Team     WG2     WG3
> 12:05 - 12:45     Taxonomy of Failures     Mitaka: Beyond the Release Notes
> Roadmap Feedback Request from Ops     Large Deployments Team     Ask
> OpenStack     WG3
> 12:45 - 2:00     Lunch
> 2:00 - 2:40     Deployment methods     Config Options     Future of op meetups
> organisation     OSOps     Scientific WG     WG6
> 2:50 - 3:30     Lightning Talks     Customer Onboarding best practices
> Session 12     OSOps     Scientific WG     Ops Tags Team
> 3:40 - 4:20     Lightning Talks     Inventory Management     Requests for
> Enhancement Process     WG 7     Logging     Ops Tags Team
> 4:20 - 4:40     Break
> 4:40 - 5:20     Containers on OpenStack     Ceph Integration     Session 18   
>   Ops
> Recognition - what is it, and where is it going?     NFV/Telco     WG12
> 5:30 - 6:10     Openstack in Containers     Swift Ops     Session 21     Ops
> Recognition - what is it, and where is it going?     NFV/Telco     WG12
> 6:00 - 7:30     Marketplace Booth Crawl Happy Hour!!
>
>     
>     
>     
>     
>     
>     
>
>     
>     
>     
>     
>     
>     
> Tuesday     Other Rooms     
>     
>     
>     
>     
> 11:15 - 11:55     Scientific WG     
>     
>     
>     
>     
>
>     
>     
>     
>     
>     
>     
> Wednesday     Other Rooms     Other Rooms     Other Rooms     
>     
>     
> 9:00 - 12:30     
>     
>     Ansible     
>     
>     
> 1:50 - 2:30     User Committee     Large Deployment Team     
>     Puppet     
>     
> 2:40 - 3:20     User Committee     
>     
>     Puppet     
>     
> 3:30 - 4:10     
>     
>     
>     
>     
>     
> 4:30 - 6:00     
>     
>     Ansible     Puppet     
>     
>
>     
>     
>     
>     
>     
>     
> Thursday     Other Rooms     Other Rooms     Other Rooms     
>     
>     
> 9:00 - 10:30     Ansible     
>     
>     
>     
>     
>
>     
>     
>     
>     
>     
>     
> 11:00 - 11:40     
>     
>     Chef     
>     
>     
> 11:50 - 12:30     Ansible     Puppet     Chef     
>     
>     
> 1:30 - 2:10     
>     
>     Chef     
>     
>     
>
>     
>     
>     
>     
>     
>     
>
>     
>     
>     
>     
>     
>     
> Friday     Salon E (112)     Salon C (Lunch)     Other Rooms     
>     
>     
> 09:00 - 12:30     Unstructured     
>     Ansible/Puppet     
>     
>     
> 12:45 - 1:50     
>     Feedback session / Awards     
>     
>     
>     
> 2:00 - 4:10     Unstructured     
>     
>     
>     
>     
> 4:20 - 4:40     Break     
>     
>     
>     
>     
> 4:40 - 5:20     Unstructured     
>     
>     
>     
>     
>
>
>
>
> On 05/04/16 10:20, Tom Fifield wrote:
>> Thanks to those who got back to me yesterday about conflicts.
>>
>> Today's update is a significant re-wrangling, so check it out below.
>>
>> I've started matching up moderators to slots based on your sign-ups on
>> the etherpads - check your email :)
>>
>> The sessions in Red (general sessions) don't have a moderator yet -
>> please let me know if you want to sign up for them.
>> https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide
>>
>> Similarly, if there is something missing you'd like to chat with
>> others about, we still have some empty slots.
>>
>>
>> Monday     Salon E (112)     Salon D (112)     MR406 (98)     MR409 (55)     
>> MR410
>> (38)     MR412 (38)
>> 11:15 - 11:55     Logging: if you could get one thing fixed this cycle,
>> what would it be?     Liberty upgrades - what worked, what didn't, what
>> would we do differently next time     Docs: should the Ops Guide have a
>> new revision?     Large Deployments Team     WG2     WG3
>> 12:05 - 12:45     Taxonomy of Failures     Mitaka: Beyond the Release
>> Notes     Roadmap Feedback Request from Ops     Large Deployments Team
>> WG2     WG3
>> 12:45 - 1:50     Lunch
>> 2:00 - 2:40     

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

[Tom Fifield]

On 12/04/16 22:12, Clayton O'Neill wrote:

On Tue, Apr 12, 2016 at 9:09 AM, Sean M. Collins  wrote:

Joseph Bajin wrote:

Maybe I'm wrong about this, maybe all the entries from the etherpads are
read by projects and fed into their pipelines.


They might, but they also might not. There are more etherpads created
than there is human capacity to process. Same thing with bugs and RFEs.
Just making them isn't sufficient.

My point is: Kris had success, I believe, because they went to the
Neutron midcycle and participated directly in the development process.
Neutron developers were informed of their need, consensus was built, and
the work got done.


This sort of story is exactly why I think we should have the Ops
Mid-Cycle colocated with the new Design Summit replacement.  I agree
with you that it’s likely the most of the information that’s gathered
in the ether pads isn’t looked at, or isn’t in actionable form.  As an
operator it’s hard for me to justify nearly a month of travel for two
summits a year, two Ops mid-cycles a year *and* the Design Summit
replacements twice a year.


Hi Clayton,

Please allow me to clarify some things, because this opinion might be 
based on a misconception regarding the proposed event split :)


The developer-centric event is designed to provide a place where 
developers can be neck-deep in python code, working on the technical 
"how" of implementation without interruption. Unless you're an active 
coder, working on the code base of a particular project, it's not the 
place to participate in the development process.



Today, the "what" and "why" discussions of the development process that 
the majority of ops can more actively participate in are happening at 
the individual project mid-cycles. This is what Kris participated in. 
However, due to the proposed event split's release cycle changes these 
discussions will move to the summit.



Regards,


Tom




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

Re: [Openstack-operators] Neutron firewall blocking GRE

[Kevin Benton]

Do you have a security groups allow rule for GRE? If so, do you have
the nf_conntrack_proto_gre module loaded on your compute nodes? If not, the
security groups iptables filtering will end up dropping the GRE packets.

On Fri, Apr 15, 2016 at 1:38 AM, Cory Hawkless  wrote:

> Does anyone know if there is any reason I’m having trouble getting GRE
> traffic into my instances?
>
> I have a router out on the internet an I’m trying to build a GRE tunnel
> into an instance to link a site office to my Openstack network, but looking
> at packet dumps from inside the VM I can’t see any GRE packets making it in
> at all?
>
>
>
> Regards,
>
> Cory
>
> ___
> 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

[Openstack-operators] Neutron firewall blocking GRE

[Cory Hawkless]

Does anyone know if there is any reason I'm having trouble getting GRE traffic 
into my instances?
I have a router out on the internet an I'm trying to build a GRE tunnel into an 
instance to link a site office to my Openstack network, but looking at packet 
dumps from inside the VM I can't see any GRE packets making it in at all?

Regards,
Cory
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] keystone authentication on public interface

[Van Leeuwen, Robert]

>
>Hello folks,
>
>I was wondering if you let me know if enabling keystone to listen on public 
>interface for ports 5000 and 35357 is considered as a normal practice. Example 
>if a customer wants to authenticate not via horizon or some other proxy but 
>setting up OS_AUTH_URL=http://blah  variable to be able to run OpenStack 
>commands in cli.

I think this depends a bit on your user base.
Personally I see horizon more of a getting-started thing for people who are not 
extremely technical and maybe want one or two instances which never change.

You really need the API’s if you want to automate deployments (e.g. Using 
Terraform).
If you have e.g. OPS teams using it they will probably want APIs

Depending on your user base (private/public cloud) you choose to expose the 
APIs on private/public IP space.
Since there are some pretty big OpenStack clouds facing the internet, eg 
backspace, I think the APIs are battle-tested.

Regarding how & ports:
I would terminate everything on port 443 (so people do not have to mess with 
firewalls) and offload SSL to a load-balancer.
You can do host-header inspection on the loadbalancer so e.g. 
keystone.example.com goes to your keystone server on port 5000 and 
keystone-admin.example.com goes to port 35357 (if you chose to expose it)

Cheers,
Robert van Leeuwen
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Maintenance

[Juvonen, Tomi (Nokia - FI/Espoo)]

Thanks, this is great.

Br,
Tomi

> -Original Message-
> From: EXT Tom Fifield [mailto:t...@openstack.org]
> Sent: Friday, April 15, 2016 9:33 AM
> To: Juvonen, Tomi (Nokia - FI/Espoo) ; openstack-
> operat...@lists.openstack.org
> Subject: Re: [Openstack-operators] Maintenance
> 
> OK, you're on the agenda!
> 
> 
> Hilton Austin - MR 406
> Monday, April 25, 2:50pm-3:30pm
> https://www.openstack.org/summit/austin-2016/summit-schedule/events/9516
> 
> Moderators guide is at:
> 
> https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide
> 
> Etherpad for your session:
> 
> https://etherpad.openstack.org/p/AUS-ops-Nova-maint
> 
> Regards,
> 
> 
> Tom
> 
> 
> 
> 
> 
> On 14/04/16 18:45, Juvonen, Tomi (Nokia - FI/Espoo) wrote:
> > Hi Tom,
> >
> > Yes, it would be good to have a discussion session and I could be a
> moderator.
> >
> > Br,
> > Tomi
> >
> >> -Original Message-
> >> From: EXT Tom Fifield [mailto:t...@openstack.org]
> >> Sent: Thursday, April 14, 2016 1:16 PM
> >> To: openstack-operators@lists.openstack.org
> >> Subject: Re: [Openstack-operators] Maintenance
> >>
> >> Hi Tomi,
> >>
> >> This seems like a pretty important topic.
> >>
> >> In addition to this thread, would you consider moderating an ops summit
> >> discussion in Austin to gather more about how ops run maintenance on
> >> their nova installs?
> >>
> >> Regards,
> >>
> >>
> >> Tom
> >>
> >> On 14/04/16 17:14, Juvonen, Tomi (Nokia - FI/Espoo) wrote:
> >>> Hi Ops,
> >>> I am working in OPNFV Doctor project that has the Telco perspective
> >>> about host maintenance related requirements to OpenStack. Already
> talked
> >>> some in dev mailing list and Nova team, but would like to have operator
> >>> perspective and interest for maintenance related changes. Not sure
> where
> >>> this will lead, but even a new OpenStack project to fulfil the
> >>> requirements. This will be somehow also close to fault monitoring
> >>> systems as these NFV related flows are very similar and also monitoring
> >>> needs to be aware of the maintenance. I will also be in Austin together
> >>> with other OPNFV Doctor people, if to discuss something there.
> >>> Here is link to OPNFV Doctor requirements:
> >>> _http://artifacts.opnfv.org/doctor/docs/requirements/02-
> >> use_cases.html#nvfi-maintenance_
> >>> 
> >>> _http://artifacts.opnfv.org/doctor/docs/requirements/03-
> >> architecture.html#nfvi-maintenance_
> >>>  >> architecture.html>
> >>> _http://artifacts.opnfv.org/doctor/docs/requirements/05-
> >> implementation.html#nfvi-maintenance_
> >>>  >> implementation.html>
> >>> Here is what I could transfer as use cases, but would ask feedback to
> >>> get more:
> >>> As admin I want to set maintenance period for certain host.
> >>> As admin I want to know when host is ready to actions to be done by
> admin
> >>> during the maintenance. Meaning physical resources are emptied.
> >>> As owner of a server I want to prepare for maintenance to minimize
> >> downtime,
> >>> keep capacity on needed level and switch HA service to server not
> >>> affected by
> >>> maintenance.
> >>> As owner of a server I want to know when my servers will be down
> because
> >> of
> >>> host maintenance as it might be servers are not moved to another host.
> >>> As owner of a server I want to know if host is to be totally removed,
> so
> >>> instead of keeping my servers on host during maintenance, I want to
> move
> >>> them
> >>> to somewhere else.
> >>> As owner of a server I want to send acknowledgement to be ready for
> host
> >>> maintenance and I want to state if servers are to be moved or kept on
> >> host.
> >>> Removal and creating of server is in owner's control already.
> Optionally
> >>> server
> >>> Configuration data could hold information about automatic actions to be
> >>> done
> >>> when host is going down unexpectedly or in controlled manner. Also
> >>> actions at
> >>> the same if down permanently or only temporarily. Still this needs
> >>> acknowledgement from server owner as he needs time for application
> level
> >>> controlled HA service switchover.
> >>> Br,
> >>> Tomi
> >>>
> >>>
> >>> ___
> >>> 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

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

Re: [Openstack-operators] Maintenance

[Tom Fifield]

OK, you're on the agenda!


Hilton Austin - MR 406
Monday, April 25, 2:50pm-3:30pm
https://www.openstack.org/summit/austin-2016/summit-schedule/events/9516

Moderators guide is at:

https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide

Etherpad for your session:

https://etherpad.openstack.org/p/AUS-ops-Nova-maint

Regards,


Tom





On 14/04/16 18:45, Juvonen, Tomi (Nokia - FI/Espoo) wrote:

Hi Tom,

Yes, it would be good to have a discussion session and I could be a moderator.

Br,
Tomi


-Original Message-
From: EXT Tom Fifield [mailto:t...@openstack.org]
Sent: Thursday, April 14, 2016 1:16 PM
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] Maintenance

Hi Tomi,

This seems like a pretty important topic.

In addition to this thread, would you consider moderating an ops summit
discussion in Austin to gather more about how ops run maintenance on
their nova installs?

Regards,


Tom

On 14/04/16 17:14, Juvonen, Tomi (Nokia - FI/Espoo) wrote:

Hi Ops,
I am working in OPNFV Doctor project that has the Telco perspective
about host maintenance related requirements to OpenStack. Already talked
some in dev mailing list and Nova team, but would like to have operator
perspective and interest for maintenance related changes. Not sure where
this will lead, but even a new OpenStack project to fulfil the
requirements. This will be somehow also close to fault monitoring
systems as these NFV related flows are very similar and also monitoring
needs to be aware of the maintenance. I will also be in Austin together
with other OPNFV Doctor people, if to discuss something there.
Here is link to OPNFV Doctor requirements:
_http://artifacts.opnfv.org/doctor/docs/requirements/02-

use_cases.html#nvfi-maintenance_


_http://artifacts.opnfv.org/doctor/docs/requirements/03-

architecture.html#nfvi-maintenance_



_http://artifacts.opnfv.org/doctor/docs/requirements/05-

implementation.html#nfvi-maintenance_



Here is what I could transfer as use cases, but would ask feedback to
get more:
As admin I want to set maintenance period for certain host.
As admin I want to know when host is ready to actions to be done by admin
during the maintenance. Meaning physical resources are emptied.
As owner of a server I want to prepare for maintenance to minimize

downtime,

keep capacity on needed level and switch HA service to server not
affected by
maintenance.
As owner of a server I want to know when my servers will be down because

of

host maintenance as it might be servers are not moved to another host.
As owner of a server I want to know if host is to be totally removed, so
instead of keeping my servers on host during maintenance, I want to move
them
to somewhere else.
As owner of a server I want to send acknowledgement to be ready for host
maintenance and I want to state if servers are to be moved or kept on

host.

Removal and creating of server is in owner's control already. Optionally
server
Configuration data could hold information about automatic actions to be
done
when host is going down unexpectedly or in controlled manner. Also
actions at
the same if down permanently or only temporarily. Still this needs
acknowledgement from server owner as he needs time for application level
controlled HA service switchover.
Br,
Tomi


___
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



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

Re: [Openstack-operators] Draft Agenda for AUS Ops@Summit

[Tom Fifield]

Hi all,

We still have no moderators for the following sessions:
* Mitaka: Beyond the Release Notes
* Swift Ops

Information about what it means to be a moderator is available here:

 https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide


If no moderators sign up to lead these sessions, they will be cancelled.



Regards,


Tom


On 13/04/16 20:28, Tom Fifield wrote:

All,

just a quick note to say this is now on the official agenda:

https://www.openstack.org/summit/austin-2016/summit-schedule/#event_types=13,14,15



Don't forget to download your summit app - it has caching magic.


Regards,


Tom

On 08/04/16 12:32, Tom Fifield wrote:

OK, we've had moderator confirmation for many sessions, so I'm going to
start putting this on the official agenda and setting up some
etherpads :)

Still haven't heard anyone interested in Ceph or Swift.


Monday Salon E (112) Salon D (112) MR406 (98) MR409
(55) MR410
(38) MR412 (38)
11:15 - 11:55 Logging: if you could get one thing fixed this cycle,
what would it be? Liberty upgrades - what worked, what didn't, what
would we do differently next time Docs: should the Ops Guide have
a new
revision? Large Deployments Team WG2 WG3
12:05 - 12:45 Taxonomy of Failures Mitaka: Beyond the Release
Notes
Roadmap Feedback Request from Ops Large Deployments Team Ask
OpenStack WG3
12:45 - 2:00 Lunch
2:00 - 2:40 Deployment methods Config Options Future of op
meetups
organisation OSOps Scientific WG WG6
2:50 - 3:30 Lightning Talks Customer Onboarding best practices
Session 12 OSOps Scientific WG Ops Tags Team
3:40 - 4:20 Lightning Talks Inventory Management Requests for
Enhancement Process WG 7 Logging Ops Tags Team
4:20 - 4:40 Break
4:40 - 5:20 Containers on OpenStack Ceph Integration
Session 18 Ops
Recognition - what is it, and where is it going? NFV/Telco WG12
5:30 - 6:10 Openstack in Containers Swift Ops Session
21 Ops
Recognition - what is it, and where is it going? NFV/Telco WG12
6:00 - 7:30 Marketplace Booth Crawl Happy Hour!!














Tuesday Other Rooms




11:15 - 11:55 Scientific WG











Wednesday Other Rooms Other Rooms Other Rooms


9:00 - 12:30

Ansible


1:50 - 2:30 User Committee Large Deployment Team
Puppet

2:40 - 3:20 User Committee

Puppet

3:30 - 4:10





4:30 - 6:00

Ansible Puppet








Thursday Other Rooms Other Rooms Other Rooms


9:00 - 10:30 Ansible











11:00 - 11:40

Chef


11:50 - 12:30 Ansible Puppet Chef


1:30 - 2:10

Chef
















Friday Salon E (112) Salon C (Lunch) Other Rooms


09:00 - 12:30 Unstructured
Ansible/Puppet


12:45 - 1:50
Feedback session / Awards



2:00 - 4:10 Unstructured




4:20 - 4:40 Break




4:40 - 5:20 Unstructured








On 05/04/16 10:20, Tom Fifield wrote:

Thanks to those who got back to me yesterday about conflicts.

Today's update is a significant re-wrangling, so check it out below.

I've started matching up moderators to slots based on your sign-ups on
the etherpads - check your email :)

The sessions in Red (general sessions) don't have a moderator yet -
please let me know if you want to sign up for them.
https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide

Similarly, if there is something missing you'd like to chat with
others about, we still have some empty slots.


Monday Salon E (112) Salon D (112) MR406 (98) MR409
(55) MR410
(38) MR412 (38)
11:15 - 11:55 Logging: if you could get one thing fixed this cycle,
what would it be? Liberty upgrades - what worked, what didn't, what
would we do differently next time Docs: should the Ops Guide have a
new revision? Large Deployments Team WG2 WG3
12:05 - 12:45 Taxonomy of Failures Mitaka: Beyond the Release
Notes Roadmap Feedback Request from Ops Large Deployments Team
WG2 WG3
12:45 - 1:50 Lunch
2:00 - 2:40 Deployment methods Config Options Future of
op meetups
organisation OSOps Scientific WG WG6
2:50 - 3:30 Lightning Talks Customer Onboarding best practices
Session 12 OSOps Scientific WG Ops Tags Team
3:40 - 4:20 Lightning Talks Inventory Management Requests
for
Enhancement Process WG 7 Logging Ops Tags Team
4:20 - 4:40 Break
4:40 - 5:20 Containers on OpenStack Ceph Integration
Session 18
Ops Recognition - what is it, and where is it going?
NFV/Telco WG12
5:30 - 6:10 Openstack in Containers Swift Ops Session
21 Ops
Recognition - what is it, and where is it going? NFV/Telco WG12
6:10 - 7:30 Marketplace Booth Crawl Happy Hour!!














Tuesday Other Rooms




11:15 - 11:55 Scientific WG











Wednesday