Re: [Openstack-operators] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

2016-11-22 Thread darren chan
No problem :) I simplified the spec to be more realistic about what we can achieve for Ocata. https://review.openstack.org/#/c/394261/ On Friday, 18 November 2016, 23:53, Steve Martinelli wrote: On Thu, Nov 17, 2016 at 11:04 PM, darren chan wrote: Good timing, I was about to send

Re: [Openstack-operators] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

2016-11-17 Thread darren chan
Good timing, I was about to send a follow-up email about this spec. I agree, this content needs to be more visible, which is why the spec proposed to move upgrade notes to the Upgrades chapter in the Operations Guide. However, it seems like the general consensus is to keep content in project repo

[Openstack-operators] [OpenStack-docs] [OpenStack-dev] [docs] Project upgrade notes

2016-11-07 Thread darren chan
Hi everyone, There was an operations community discussion during the Ocata summit to include upgrade notes from the developer documentation in the Operations Guide. The spec can be reviewed here:  https://review.openstack.org/#/c/394261/ Feedback and comments are appreciated! Thanks, Darren  

[Openstack-operators] Ops/Arch Guides specialty team meeting time

2016-09-18 Thread darren chan
Hi everyone, The Ops/Arch Guides specialty team meeting time has changed to biweekly on Monday 2100 UTC in IRC #openstackmeeting3.  Tomorrow we will discuss the docs session at the ops midcycle (https://etherpad.openstack.org/p/NYC-ops-Documentation) and the direction of the Ops Guide. Feel fre

[Openstack-operators] [OpenStack-operators] [OpenStack-docs] [ops-guide] [arch-guide] reorganization

2016-05-08 Thread darren chan
Hi everyone,  In the ops-guide session at the Austin OpenStack Summit, we discussed reorganising content by task instead of persona, to make information easier to find, and reduce content overlap and duplication between guides. To achieve this, we are defining a list of tasks for cloud archit

[Openstack-operators] [OpenStack-operators][OpenStack-docs][ops-guide] [arch-guide] reorganization

2016-05-08 Thread darren chan
Hi everyone,  In the ops-guide session at the Austin OpenStack Summit, we discussed reorganising content by task instead of persona, to make information easier to find, and reduce content overlap and duplication between guides. To achieve this, we are defining a list of tasks for cloud architect

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

2016-04-15 Thread 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 not

Re: [Openstack-operators] Draft Agenda for MAN Ops Meetup (Feb 15, 16)

2016-02-01 Thread darren chan
I've spoken with Alexandra Settle, and she can moderate a session about Operations Guide improvements. On Thursday, 21 January 2016, 5:03, Tom Fifield wrote: Hi all, Matt, Nick and myself took some time to take our suggestions from the etherpad and attempted to wrangle them into som

Re: [Openstack-operators] Arch guide virtual doc swarm

2015-11-24 Thread darren chan
In addition, an etherpad is available  https://etherpad.openstack.org/p/arch-guide-reorg with the current structure and proposed structure. Have a look and add any changes you would like to see.  Thanks, Darren On Wednesday, 25 November 2015, 0:43, Shilla Saebi wrote: Hello Operators

[Openstack-operators] [ops-guide] meeting

2015-11-19 Thread darren chan
Just a reminder the ops guide meeting will start in 5 minutes in #openstack-meeting-3. Thanks! Darren___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [ops-guide] Ops/Arch Guide specialty team meeting time

2015-09-15 Thread darren chan
Hi everyone, Currently our weekly meeting is held on Thursday 1500 UTC, with fairly poor attendance. Here are some options to cater for different timezones: 1. Every Thursday 2130 UTC (to suit US and APAC timezones)2. Every Thursday at alternating times to cater for timezones - US: Thursday 1400