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/02-use_cases.html>
_http://artifacts.opnfv.org/doctor/docs/requirements/03-
architecture.html#nfvi-maintenance_
<http://artifacts.opnfv.org/doctor/docs/requirements/03-
architecture.html>
_http://artifacts.opnfv.org/doctor/docs/requirements/05-
implementation.html#nfvi-maintenance_
<http://artifacts.opnfv.org/doctor/docs/requirements/05-
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
