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

[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 UTC, APAC: 
Thursday 2330 UTC3. Option 1 biweekly
Let me know your preference. I'm open to other suggestions.
If you are interested in joining the team, sign up here 
https://wiki.openstack.org/wiki/Documentation/OpsGuide#Team_Members. Things 
will begin to ramp with the Architecture Design Guide specs approved for 
Mitaka, and Ops Guide conversion and reorganisation specs in the works.  
Hopefully, there will an opportunity to discuss these changes at the Tokyo 
summit.

Thanks!
Darren

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

Re: [Openstack-operators] User Survey - Deadline Sept 25th

[Tom Fifield]

Copy and Paste Error Strikes Again!

The deadline is (as the subject says):  ***September 25 at 23:59 UTC***. 
That is next Friday - get on it :)


http://www.openstack.org/user-survey


Regards,

Tom

On 16/09/15 11:40, Tom Fifield wrote:

Hi all,

If you run OpenStack, build apps on it, or have customers with OpenStack
deployments, please take a few minutes to respond to the latest User
Survey or pass it along to your friends.

Since 2013, the user survey has provided significant insight into what
people are deploying and how they're using OpenStack. You can see the
most recent results in these SuperUser Articles: [1][2][3].

Please follow the link and instructions below to complete the User
Survey by ***Sep 25, 2015 at 23:00 UTC***. If you already completed the
survey, there's no need to start over. You can simply log back in to
update your Deployment Profile, as well as take the opportunity to
provide additional input. You need to do this to keep your past survey
responses active, but we hope you'll do it because we've made the survey
shorter and with more interesting questions ;)



Take the Survey ( http://www.openstack.org/user-survey )


All of the information you provide is confidential to the Foundation and
User Committee and will be aggregated anonymously unless you clearly
indicate we can publish your organization’s profile.

Remember you can hear directly from users and see the aggregate survey
findings by attending the next OpenStack Summit, October 27-30 in Tokyo
(http://www.openstack.org/summit).

Thank you again for your support.


-Tom


[1]
http://superuser.openstack.org/articles/user-survey-identifies-leading-industries-and-business-drivers-for-openstack-adoption

[2]
http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up

[3]
http://superuser.openstack.org/articles/openstack-application-developers-share-insights




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

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

[Shilla Saebi]

Darren,

Thanks for putting this together. I vote for Option 1 and 3.

On Tue, Sep 15, 2015 at 11:21 PM, darren chan 
wrote:

> 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 UTC, APAC: Thursday 2330 UTC
> 3. Option 1 biweekly
>
> Let me know your preference. I'm open to other suggestions.
>
> If you are interested in joining the team, sign up here
> https://wiki.openstack.org/wiki/Documentation/OpsGuide#Team_Members.
> Things will begin to ramp with the Architecture Design Guide specs approved
> for Mitaka, and Ops Guide conversion and reorganisation specs in the
> works.  Hopefully, there will an opportunity to discuss these changes at
> the Tokyo summit.
>
> Thanks!
>
> Darren
>
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] User Survey - Deadline Sept 25th

[Tom Fifield]

Hi all,

If you run OpenStack, build apps on it, or have customers with OpenStack 
deployments, please take a few minutes to respond to the latest User 
Survey or pass it along to your friends.


Since 2013, the user survey has provided significant insight into what 
people are deploying and how they're using OpenStack. You can see the 
most recent results in these SuperUser Articles: [1][2][3].


Please follow the link and instructions below to complete the User 
Survey by ***April 8, 2015 at 23:00 UTC***. If you already completed the 
survey, there's no need to start over. You can simply log back in to 
update your Deployment Profile, as well as take the opportunity to 
provide additional input. You need to do this to keep your past survey 
responses active, but we hope you'll do it because we've made the survey 
shorter and with more interesting questions ;)




Take the Survey ( http://www.openstack.org/user-survey )


All of the information you provide is confidential to the Foundation and 
User Committee and will be aggregated anonymously unless you clearly 
indicate we can publish your organization’s profile.


Remember you can hear directly from users and see the aggregate survey 
findings by attending the next OpenStack Summit, October 27-30 in Tokyo 
(http://www.openstack.org/summit).


Thank you again for your support.


-Tom


[1] 
http://superuser.openstack.org/articles/user-survey-identifies-leading-industries-and-business-drivers-for-openstack-adoption
[2] 
http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up
[3] 
http://superuser.openstack.org/articles/openstack-application-developers-share-insights


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

Re: [Openstack-operators] Tokyo Summit Ops Design Summit Tracks - Agenda Brainstorming

[Tom Fifield]

Last chance to provide your ideas for our design summit track.

So far we are lacking:
* Lightning talks
* Working Groups
* General Sessions

Starting next week we're going to prepare the draft agenda for 
circulation and discussion. So, get in now. What would you like to 
discuss with fellow ops and developers?



https://etherpad.openstack.org/p/TYO-ops-meetup


Regards,


Tom

On 08/09/15 17:10, Tom Fifield wrote:

Ping!

This is your chance to provide input on our design summit track for
Tokyo. Add your ideas on the etherpad below!


https://etherpad.openstack.org/p/TYO-ops-meetup


On 03/09/15 03:27, Tom Fifield wrote:

Hi all,

Thanks for those who made it to the recent meetup in Palo Alto. It was a
fantastic couple of days, and many are excited to get started on talking
about our ops track in the Tokyo design summit.


Recall that this is in addition to the operations and other conference
track's presentations. It's aimed at giving us a design-summit-style
place to congregate, swap best practices, ideas and give feedback.


As usual, we're working to act on the feedback from all past events to
make this one better than ever. One that we continue to work on is the
need to see action happen as a result of this event, so please - when
you are suggesting sessions in the below etherpad please try and phrase
them in a way that will probably result in things happening afterward.


**

Please propose session ideas on:

https://etherpad.openstack.org/p/TYO-ops-meetup

ensuring each session suggestion will have a result.

**


The room allocations are still being worked out, but the current
thinking is that we will interleave general sessions and working groups
across Tuesday and Wednesday, to allow for attendance from ops in the
cross-project sessions.


More as it comes, and as always, further information about ops meetups
and notes from the past can be found on the wiki @:

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

Finally, don't forget to register ASAP!
http://www.eventbrite.com/e/openstack-summit-october-2015-tokyo-tickets-17356780598



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



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

Re: [Openstack-operators] [tags] ease of upgrade

[Barrett, Carol L]

Michal/Grzegorz/Will – Can you pls work with Dave to make sure all of the 
Liberty improvements are included?

Dave: The Enterprise WG has been focused on rolling upgrades and developed 
tracker for our work from Kilo to Liberty to Mitaka. You can find the info 
here: 
https://docs.google.com/spreadsheets/d/1iT0XraW8ORGk2fb1bJMigE6wWdKK6YgrNB4ishPOc1M/edit#gid=1668081475.
 The Product WG has prioritized this user story and we are collaborating on 
continued implementation. We have weekly team meetings if you’d like to come in 
for a discussion on this tag, happy to add this to an agenda. The meetings are 
Tuesdays at 1500 UTC. You can find more info here: 
https://wiki.openstack.org/wiki/Enterprise_Working_Group, scroll down to the 
Deployment Team section.

Thanks
Carol


From: David Medberry [mailto:openst...@medberry.net]
Sent: Tuesday, September 15, 2015 8:40 AM
To: Tom Fifield
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] [tags] ease of upgrade

Sure, I can take a pass at this.

On Tue, Sep 15, 2015 at 2:11 AM, Tom Fifield 
> wrote:
Hi all,

One of our long mooted tags has been something that captures the ease of 
upgrade for a service.

We've got a lot of inherit knowledge about this stuff that would be great to 
capture, for example:

* Swift just eats upgrades up - whether you go for every point release, or do 
the N to N+1 jump, provided you read the release notes it's basically always a 
good time with Swift.
* Nova's upgrade_levels is pretty amazing, too. In recent versions you can run 
N+1 apis with a mix of N and N+1 compute nodes - quite convenient.
* Neutron in some configurations dumps all of the flows, you have to watch dhcp 
timeouts, how long services are offline etc, so a few little traps that keep it 
from being perfect.

If we could somehow make this into a tag, that'd be great. Anyone want to have 
a go?


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

Re: [Openstack-operators] [tags] ease of upgrade

[Matt Kassawara]

I think these sorts of general upgrade notes from the trenches should also
belong in the operations guide.

On Tue, Sep 15, 2015 at 2:11 AM, Tom Fifield  wrote:

> Hi all,
>
> One of our long mooted tags has been something that captures the ease of
> upgrade for a service.
>
> We've got a lot of inherit knowledge about this stuff that would be great
> to capture, for example:
>
> * Swift just eats upgrades up - whether you go for every point release, or
> do the N to N+1 jump, provided you read the release notes it's basically
> always a good time with Swift.
> * Nova's upgrade_levels is pretty amazing, too. In recent versions you can
> run N+1 apis with a mix of N and N+1 compute nodes - quite convenient.
> * Neutron in some configurations dumps all of the flows, you have to watch
> dhcp timeouts, how long services are offline etc, so a few little traps
> that keep it from being perfect.
>
> If we could somehow make this into a tag, that'd be great. Anyone want to
> have a go?
>
>
> 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