[Openstack-operators] [LDT] Scheduling of 'plan the week' at the summit

The Large Deployment Team meeting for ‘Plan the Week’ (https://www.openstack.org/summit/boston-2017/summit-schedule/events/18404/large-deployment-team-planning-the-week) seems to be on Wednesday at 11h00 and the Recapping the week is the next slot at 11h50

[Openstack-operators] Last Opportunity: OpenStack Days East 2017

Dear Potential Sponsors of OpenStack Days East 2017: This is the *last* Opportunity to Engage and Educate at OpenStack Days East as a Sponsor for 2017! The all *volunteer* organizing committee has been working hard to create a robust agenda for OpenStack Days

[Openstack-operators] [puppet] Deprecating Postgresql support

Greetings, We didn't see anyone using Postgresql when deploying Puppet OpenStack: - no feedback on ML or IRC - no bug report in Launchpad Postgresql support (or call it how you want) is also removed upstream in OpenStack. We will deprecate the class that used to deploy Postgresql in Pike and

Re: [Openstack-operators] [puppet] Deprecating Postgresql support

On Thu, Apr 27, 2017 at 7:38 AM, Emilien Macchi wrote: > Greetings, > > We didn't see anyone using Postgresql when deploying Puppet OpenStack: > - no feedback on ML or IRC > - no bug report in Launchpad > > Postgresql support (or call it how you want) is also removed upstream

Re: [Openstack-operators] [scientific] Lightning talks on Scientific OpenStack

Hi George - Sorry for the slow response. The consensus was for 8 minutes maximum. That should be plenty for a lightning talk, and enables us to fit one more in. Best wishes, Stig > On 27 Apr 2017, at 20:29, George Mihaiescu wrote: > > Hi Stig, it will be 10 minutes

Re: [Openstack-operators] [puppet] Deprecating Postgresql support

On 4/27/2017 8:54 AM, Emilien Macchi wrote: [adding mailing-lists again] On Thu, Apr 27, 2017 at 9:31 AM, Benedikt Trefzer wrote: Hi Emilien On 27.04.2017 13:38, Emilien Macchi wrote: Greetings, We didn't see anyone using Postgresql when deploying Puppet OpenStack: - no

Re: [Openstack-operators] looking for feedback on proposals to improve logging

Hi, I have been working on the concept of fault management blueprint to increase cloud resiliency. As part of this proposal, info such as logs, KPIs, health checks and so on are critical since we are engaging in deep data analysis and machine learning. >> >> To ease the data analysis process

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

On 4/27/2017 4:52 PM, Eric Fried wrote: Y'all- TL;DR: Does glance ever really need/use multiple endpoint URLs? I'm working on bp use-service-catalog-for-endpoints[1], which intends to deprecate disparate conf options in various groups, and centralize acquisition of service

Re: [Openstack-operators] [scientific] Lightning talks on Scientific OpenStack

Hi Stig, it will be 10 minutes sessions like in Barcelona? Thanks, George > On Apr 26, 2017, at 03:31, Stig Telfer wrote: > > Hi All - > > We have planned a session of lightning talks at the Boston summit to discuss > topics specific for OpenStack and research

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

We make extensive use of the [glance]/api_servers list. We configure that on hypervisors to direct them to Glance servers which are more “local” network-wise (in order to reduce network traffic across security zones/firewalls/etc.) This way nova-compute can fail over in case one of the

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

We at Nectar are in the same boat as Mike. Our use-case is a little bit more about geo-distributed operations though - our Cells are in different States around the country, so the local glance-apis are particularly important for caching popular images close to the nova-computes. We consider these