Re: [Openstack-operators] Openstack release compatibility

Hello, OpenStack-Ansible Mitaka deploys Linux Bridge by default. This would still happen, but as said, it's not too big of a deal too. Best regards, Jean-Philippe (evrardjp) On 6 November 2017 at 08:10, Kevin Benton wrote: > The Neutron OVS agent should not cause interrupts

Re: [Openstack-operators] Upstream LTS Releases

The 1 year release cycle makes a lot of sense to me too. +1 Saverio ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Upstream LTS Releases

On Fri, Nov 10, 2017 at 2:51 PM, John Dickinson wrote: > What I heard from ops in the room is that they want (to start) one release a > year who's branch isn't deleted after a year. What if that's exactly what we > did? I propose that OpenStack only do one release a year instead of

Re: [Openstack-operators] Upstream LTS Releases

"I propose that OpenStack only do one release a year instead of two.” I am all too happy to chime in and second (or third, or fourth) this notion. It is extremely challenging for many kinds of organizations (government, industry) to keep pace with the two releases per year model. I think it

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

I missed this session but the discussion strikes a chord as this is something I've been saying on my user survey every 6 months. On 11 November 2017 at 09:51, John Dickinson wrote: > What I heard from ops in the room is that they want (to start) one release a > year who's branch

Re: [Openstack-operators] Upstream LTS Releases

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 very > productive session about how to go about keeping a selection of past > releases available and maintained for a longer period of time (LTS). > > There was

Re: [Openstack-operators] [puppet] keystone.conf and 'federation/trusted_dashboard' (multi valued)

On Fri, Nov 10, 2017 at 12:45 PM, Red Cricket wrote: > Hi, > > I am using https://github.com/openstack/puppet-keystone (stable/newton > branch) and we would like to implement a design that uses federation openid. > > As part of this design I need to add these lines to

[Openstack-operators] [puppet] keystone.conf and 'federation/trusted_dashboard' (multi valued)

Hi, I am using https://github.com/openstack/puppet-keystone (stable/newton branch) and we would like to implement a design that uses federation openid. As part of this design I need to add these lines to the keystone.conf file: [federation] ... trusted_dashboard =

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

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 > > wrote: > > > Hello Ops folks, > > > > > > This morning at the Sydney Summit

[Openstack-operators] OpenStack Shared Storage Problem

Hi everyone, we have a little problem with our openstack installation using shared storage with ocfs2 over iSCSI with multipath, as OpenStack version we are running Mitaka and Ubuntu 16.04.3. We have totally 10 compute nodes. We have 2 shared storage volumes which one of the is used by compute