Re: [Openstack-operators] Proposal for an 'Operations' project

Excerpts from Michael Chapman's message of 2014-11-06 12:20:52 +0100: Hi Operators! I felt like OpenStack didn't have enough projects, so here's another one. During the summit I feel like I'm repeatedly having the same conversations with different groups about bespoke approaches to

Re: [Openstack-operators] Proposal for an 'Operations' project

Excerpts from Jeremy Stanley's message of 2014-11-08 16:23:02 -0800: On 2014-11-08 04:08:08 -0500 (-0500), Fischer, Matt wrote: [...] Perhaps some of the code fits in some places as previously mentioned on the list, but the issue is that none of those projects really focus on operations.

Re: [Openstack-operators] Operations project: Packaging

Excerpts from Michael Chapman's message of 2014-11-17 22:16:28 -0800: Hi all, Packaging was one of the biggest points of interest in the Friday Paris meeting, and I'd like to use this thread to have a centralised discussion and/or argument regarding whether there is a packaging system that

Re: [Openstack-operators] Heat in production?

We (the TripleO developers) use Heat as part of TripleO to manage small (40 nodes) clouds for TripleO. This means that we're using Heat to manage our bare metal nodes which are in turn managed by nova+ironic. For the most part it is only used to bring up new nodes or change parameters (not

Re: [Openstack-operators] [Ceilometer] Real world experience with Ceilometer deployments - Feedback requested

Excerpts from George Shuklin's message of 2015-02-11 17:59:02 -0800: Ceilometer is in sad state. 1. Collector leaks memory. We ran it on same host with mongo, and it grab 29Gb out of 32, leaving mongo with less than gig memory available. I wonder how hard it would be to push Ceilometer down

Re: [Openstack-operators] How to handle updates of public images?

Excerpts from George Shuklin's message of 2015-02-05 05:09:51 -0800: Hello everyone. We are updating our public images regularly (to provide them to customers in up-to-date state). But there is a problem: If some instance starts from image it becomes 'used'. That means: * That image is

Re: [Openstack-operators] Packaging with fpm

Excerpts from Mathieu Gagné's message of 2015-03-04 08:31:45 -0800: Hi, I'm currently experimenting with fpm. I learned that fpm does not generate the files needed to upload your new package to an APT repository. Since the package type built by fpm is binary, that file would be the

Re: [Openstack-operators] Packaging with fpm

Excerpts from Mathieu Gagné's message of 2015-03-04 09:39:34 -0800: On 2015-03-04 12:18 PM, Clint Byrum wrote: Excerpts from Mathieu Gagné's message of 2015-03-04 08:31:45 -0800: I really like APT repositories and would like to continue using them for the time being. I'm impressed you

Re: [Openstack-operators] CMDB

I added information about Assimilation Monitoring to the etherpad. It's not strictly a CMDB, but it can be used for what CMDB's often are used for, and is worth noting in the discussion. Excerpts from Shane Gibson's message of 2015-05-07 08:27:01 -0700: At Symantec we use YiDB for CMDB data -

[Openstack-operators] [all] QPID incompatible with python 3 and untested in gate -- what to do?

Hello! There's been some recent progress on python3 compatibility for core libraries that OpenStack depends on[1], and this is likely to open the flood gates for even more python3 problems to be found and fixed. Recently a proposal was made to make oslo.messaging start to run python3 tests[2],

Re: [Openstack-operators] Keystone performance issue

Excerpts from Reza Bakhshayeshi's message of 2015-10-27 05:11:28 +0900: > Hi all, > > I've installed OpenStack Kilo (with help of official document) on a > physical HP server with following specs: > > 2 Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz each 12 physical core (totally > 48 threads) > and

Re: [Openstack-operators] [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

Excerpts from James King's message of 2015-11-09 08:47:08 -0800: > disclaimer: I’ve never worked in a software auditing department or on in a > company with one > > What about risk-averse organizations with strict policy compliance > guidelines? Can we expect them to audit a new distribution of

Re: [Openstack-operators] [nova] FYI, local conductor mode is deprecated, pending removal in N

Excerpts from Joshua Harlow's message of 2015-11-12 10:35:21 -0800: > Mike Dorman wrote: > > We do have a backlog story to investigate this more deeply, we just have > > not had the time to do it yet. For us, it’s been easier/faster to add more > > hardware to conductor to get over the hump

Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

Excerpts from Tony Breeds's message of 2015-11-05 22:15:18 -0800: > Hello all, > > I'll start by acknowledging that this is a big and complex issue and I > do not claim to be across all the view points, nor do I claim to be > particularly persuasive ;P > In the future, also consider not making

Re: [Openstack-operators] [openstack-dev] Scheduler proposal

Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: > Forgive the top-post. > > Cross-posting to openstack-operators for their feedback as well. > > Ed the work seems very promising, and I am interested to see how this > evolves. > > With my operator hat on I have one

Re: [Openstack-operators] [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

Excerpts from Dina Belova's message of 2015-09-22 05:57:19 -0700: > Hey, OpenStackers! > > I'm writing to propose to organise new informal team to work specifically > on the OpenStack performance issues. This will be a sub team in already > existing Large Deployments Team, and I suppose it will

Re: [Openstack-operators] Service Catalog TNG urls

Excerpts from Xav Paice's message of 2015-12-05 13:26:23 -0800: > > > > > > >> SecurityAuditing/Accounting: > > >> Having a separate internal API (for the OpenStack services) from the > > >> Public API (for humans and remote automation), allows the operator to > > >> apply a strict firewall in

Re: [Openstack-operators] Service Catalog TNG urls

Excerpts from Xav Paice's message of 2015-12-06 14:09:58 -0800: > On 7 December 2015 at 05:38, Clint Byrum <cl...@fewbar.com> wrote: > > > Excerpts from Xav Paice's message of 2015-12-05 13:26:23 -0800: > > > > > > > > I respect that this is what

Re: [Openstack-operators] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Excerpts from Dina Belova's message of 2015-12-04 01:46:06 -0800: > Dear performance folks, > > There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays > ) to > 16:00 UTC (also Tuesdays >

Re: [Openstack-operators] Service Catalog TNG urls

Excerpts from Dan Sneddon's message of 2015-12-03 09:43:59 -0800: > On 12/03/2015 06:14 AM, Sean Dague wrote: > > For folks that don't know, we've got an effort under way to look at some > > of what's happened with the service catalog, how it's organically grown, > > and do some pruning and tuning

Re: [Openstack-operators] DIB in container vs VM

Excerpts from Abel Lopez's message of 2015-12-01 16:16:08 -0800: > Hey everyone, > I've been running diskimage-builder just fine for over a year inside various > VMs, but now, I'm having to run it inside a docker container. > I'm curious if anyone has experience with making the 'ubuntu latest'

Re: [Openstack-operators] Keystone token HA

Excerpts from Ajay Kalambur (akalambu)'s message of 2015-12-17 22:48:24 -0800: > Hi > If we deploy Keystone using memcached as token backend we see that bringing > down 1 of 3 memcache servers results in some tokens getting invalidated. Does > memcached not support replication of tokens > So if

Re: [Openstack-operators] Too many connections

Excerpts from Kris G. Lindgren's message of 2016-05-30 15:33:49 +: > You are most likely running db pools with a number of worker processes. If > you look at the MySQL connections most of them will be idle. If that's the > case set the db pool timeout lower. Lower the pool size down.

Re: [Openstack-operators] New networking solution for Cloud Native apps....

Excerpts from Chris Marino's message of 2016-02-01 06:08:34 -0800: > Hello everyone, just wanted to let you know that today we opened up the > repos for the new open source networking project we’ve been working on. > It’s called Romana and the project site is romana.io. > > Thought you would be

Re: [Openstack-operators] I have an installation question and possible bug

Excerpts from Christopher Hull's message of 2016-01-25 09:11:59 -0800: > Hello all; > > I'm an experienced developer and I work at Cisco. Chances are I've covered > the basics here,but just in case, check me. > I've followed the Kilo install instructions to the letter so far as I can > tell. I

Re: [Openstack-operators] Liberty RabbitMQ and ZeroMQ

Excerpts from William Josefsson's message of 2016-08-14 15:39:06 +0800: > Hi everyone, > > I see advice in replacing RabbitMQ with ZeroMQ. I've been running 2 > clusters Liberty/CentOS7 with RabbitMQ now for while. The larger > cluster consists of 3x Controllers and 4x Compute nodes. RabbitMQ is

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

Excerpts from Daniel P. Berrange's message of 2017-02-21 10:40:02 +: > On Mon, Feb 20, 2017 at 02:36:15PM -0500, Clint Byrum wrote: > > What exactly is the security concern of the metadata service? Perhaps > > those concerns can be addressed directly? > > >

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

What exactly is the security concern of the metadata service? Perhaps those concerns can be addressed directly? I ask because anything that requires special software on the guest is a non-starter IMO. virtio is a Linux thing, so what does this do for users of Windows? FreeBSD? etc. Excerpts

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

Excerpts from Jeremy Stanley's message of 2017-02-20 20:08:00 +: > On 2017-02-20 14:36:15 -0500 (-0500), Clint Byrum wrote: > > What exactly is the security concern of the metadata service? Perhaps > > those concerns can be addressed directly? > [...] > > A few I'm aw

Re: [Openstack-operators] Openstack team size vs's deployment size

Excerpts from gustavo panizzo (gfa)'s message of 2016-09-09 22:07:49 +0800: > On Thu, Sep 08, 2016 at 03:52:42PM +, Kris G. Lindgren wrote: > > I completely agree about the general rule of thumb. I am only looking at > > the team that specifically supports openstack. For us frontend support

Re: [Openstack-operators] Openstack team size vs's deployment size

Excerpts from Mathieu Gagné's message of 2016-09-12 17:55:34 -0400: > On Fri, Sep 9, 2016 at 6:41 PM, Mathieu Gagné wrote: > > On Wed, Sep 7, 2016 at 6:59 PM, Kris G. Lindgren > > wrote: > >> > >> I was hoping to poll other operators to see what their

Re: [Openstack-operators] [EXTERNAL] Re: Tenant/Project naming restrictions

Sounds like a bug in the API documentation: http://developer.openstack.org/api-ref/identity/v3/?expanded=create-project-detail "name bodystring The name of the project, which must be unique within the owning domain. A project can have the same name as its domain." Unfortunately, IMO

Re: [Openstack-operators] SDN for hybridcloud, does it *really* exist?

Excerpts from Jonathan Proulx's message of 2016-10-03 11:16:03 -0400: > On Sat, Oct 01, 2016 at 02:39:38PM -0700, Clint Byrum wrote: > > :I know it's hard to believe, but this world was foretold long ago and > :what you want requires no special equipment or changes to OpenSt

Re: [Openstack-operators] SDN for hybridcloud, does it *really* exist?

Excerpts from Jonathan Proulx's message of 2016-10-03 13:52:42 -0400: > > So my sense from responses so far: > > No one is doing unified SDN solutions across clouds and no one really > wants to. > > Consensus is just treat each network island like another remote DC and > use normal VPN type

Re: [Openstack-operators] SDN for hybridcloud, does it *really* exist?

Excerpts from Jonathan Proulx's message of 2016-09-30 10:15:26 -0400: > > Starting to think refactoring my SDN world (currently just neutron > ml2/ovs inside OpenStack) in preparation for maybe finally lighting up > that second Region I've been threatening for the past year... > > Networking is

Re: [Openstack-operators] [openstack-operators][ceph][nova] How do you handle Nova on Ceph?

Excerpts from Adam Kijak's message of 2016-10-12 12:23:41 +: > > > > From: Xav Paice > > Sent: Monday, October 10, 2016 8:41 PM > > To: openstack-operators@lists.openstack.org > > Subject: Re: [Openstack-operators]

Re: [Openstack-operators] How do you even test for that?

Excerpts from Jonathan Proulx's message of 2016-10-17 14:49:13 -0400: > Hi All, > > Just on the other side of a Kilo->Mitaka upgrade (with a very brief > transit through Liberty in the middle). > > As usual I've caught a few problems in production that I have no idea > how I could possibly have

Re: [Openstack-operators] Ops@Barcelona - Updates

Excerpts from Tom Fifield's message of 2016-10-17 12:58:27 +0800: > Hi all, > > There have been some schedule updates for the Ops design summit sessions: > > https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops+Summit%3A > > > > New Sessions added: > * Ops

Re: [Openstack-operators] Using novaclient, glanceclient, etc, from python

You may find the 'shade' library a straight forward choice: http://docs.openstack.org/infra/shade/ Excerpts from George Shuklin's message of 2016-11-17 20:17:08 +0200: > Hello. > > I can't find proper documentation about how to use openstack clients > from inside python application. All I can

Re: [Openstack-operators] Ironic with top-rack switches management

Excerpts from George Shuklin's message of 2016-12-26 00:22:38 +0200: > Hello everyone. > > > Did someone actually made Ironic running with ToR (top rack switches) > under neutron in production? Which switch verdor/plugin (and OS version) > do you use? Do you have some switch configuration with

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

ves. The user does not care in this case. How does, e.g., WHMCS do it? > That is a stock software that you can use to provide VPS over OpenStack. > Tomas from Homeatcloud > > -----Original Message- > From: Clint Byrum [mailto:cl...@fewbar.com] > Sent: Thursday, October 05, 2017 6:

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

use rebuild when reverting with snapshots. Keeping the same IP and > hostname avoids some issues with Active Directory and Kerberos. > > Tim > > -Original Message----- > From: Clint Byrum <cl...@fewbar.com> > Date: Tuesday, 3 October 2017 at 19:17 > To: opensta

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

Excerpts from Chris Friesen's message of 2017-10-04 09:15:28 -0600: > On 10/03/2017 11:12 AM, Clint Byrum wrote: > > > My personal opinion is that rebuild is an anti-pattern for cloud, and > > should be frozen and deprecated. It does nothing but complicate Nova > >

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

offer floating IPs, yet. > > Also, we use the user_data to bootstrap some actions in new instances > (puppet, ...). > > Considering all the use-cases for rebuild it would be great if the user_data > can be updated at rebuild time. > > > > On Wed, Oct 4, 2017 a

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

Excerpts from Belmiro Moreira's message of 2017-10-04 17:33:40 +0200: > In our cloud rebuild is the only way for a user to keep the same IP. > Unfortunately, we don't offer floating IPs, yet. > Also, we use the user_data to bootstrap some actions in new instances > (puppet, ...). > Considering all

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

Excerpts from Matt Riedemann's message of 2017-10-03 10:53:44 -0500: > We plan on deprecating personality files from the compute API in a new > microversion. The spec for that is here: > > https://review.openstack.org/#/c/509013/ > > Today you can pass new personality files to inject during

Re: [Openstack-operators] Upstream LTS Releases

Excerpts from Doug Hellmann's message of 2017-11-11 12:19:56 -0500: > Excerpts from John Dickinson's message of 2017-11-10 14:51:08 -0800: > > On 7 Nov 2017, at 15:28, Erik McCormick wrote: > > > > > Hello Ops folks, > > > > > > This morning at the Sydney Summit we had a very well attended and

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

Excerpts from Doug Hellmann's message of 2017-11-10 13:11:45 -0500: > Excerpts from Clint Byrum's message of 2017-11-08 23:15:15 -0800: > > Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: > > > On Tue, Nov 7, 2017 at 3:28 PM, Erik McCormick > > >

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: > On Tue, Nov 7, 2017 at 3:28 PM, Erik McCormick > wrote: > > Hello Ops folks, > > > > This morning at the Sydney Summit we had a very well attended and very > > productive session about how to go

Re: [Openstack-operators] Mixed service version CI testing

Excerpts from Matt Riedemann's message of 2017-12-19 09:58:34 -0600: > During discussion in the TC channel today [1], we got talking about how > there is a perception that you must upgrade all of the services together > for anything to work, at least the 'core' services like >

[Openstack-operators] Live-migration experiences?

Hello! At GoDaddy, we're about to start experimenting with live migration. While setting it up, we've found a number of options that seem attractive/useful, but we're wondering if anyone has data/anecdotes about specific configurations of live migration. Your time in reading them is