Re: [Openstack-operators] How to apply the bugfix for keystone pyldap (#1736241)

> From: David Young > mailto:dav...@funkypenguin.co.nz>> > Date: Friday, December 8, 2017 at 10:34 PM > To: > "openstack-operators@lists.openstack.org" > > mailto:openstack-operators@lists.openstack.org>> > Subject: [Openstack-operators] How to ap

Re: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

From: "Craft, Mike" Date: Thursday, March 2, 2017 at 7:50 PM To: "openstack-operators@lists.openstack.org" Subject: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage Hello, Did an upgrade from liberty to mitaka and we are experiencing an issue

Re: [Openstack-operators] OSA Newton Release Deployment in test environment

LXC will setup eth0 in the container which will NAT through the host to access the internet. Clearly there’s something wrong with that traffic path, so step through it like you would with any environment by validating that it is able to reach its gateway (host), then next hop, etc. From: Amit

Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues

at 1:56 PM To: Jesse Pretorius , "OpenStack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues Thank you Jesse. So should i set the parameter haproxy_ssl to false in the default folder of the haproxy_server role or some

Re: [Openstack-operators] feedback on pymysql

From: Matt Fischer As a part of our upgrades to Newton we are transitioning our services to use pymysql rather than the deprecated MySQL-Python [1]. I believe pymsql has been the default in devstack and the gate for sometime now and that MySQL-Python is essentially untested and not updated, h

Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues

From: Achi Hamza Date: Thursday, November 17, 2016 at 1:57 PM To: Jesse Pretorius , "OpenStack-operators@lists.openstack.org" Subject: Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues Thank you Jesse, but these iptables rules are just applied on the deploy

Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues

m shell -a "curl http://172.16.1.2:8181/os-releases/14.0.1/requirements_constraints.txt"; curl http://172.16.1.2:8181/os-releases/14.0.1/requirements_constraints.txt J From: Achi Hamza Date: Thursday, November 17, 2016 at 10:59 AM To: Jesse Pretorius Subject: Re: [Openstack-opera

Re: [Openstack-operators] [openstack-dev] [openstack-ansible] pip issues

Hi Achi, Can you list the files in /var/www/repo/os-release? ansible repo_all -m shell -a "find /var/www/repo/os-releases -type f" Thanks, Jesse IRC: odyssey4me From: Achi Hamza Date: Thursday, November 17, 2016 at 10:01 AM To: "OpenStack-operators@lists.openstack.org" , "openstack-...@lists

Re: [Openstack-operators] openstack-ansible - recovery of failed infrastructure host

Hi Ben, If you stand up a new infrastructure host with the same IP address and name in openstack_user_config then execute the setup-hosts, setup-infrastructure and setup-openstack plays it should put everything back in place for you without further intervention. Jesse IRC: odyssey4me On 10/24

Re: [Openstack-operators] Instances failing to launch when rbd backed (ansible Liberty setup)

Hi Grant/Chris, Can you verify whether there is a symlink from inside the venv to the location of the RBD python libs in the system packages? If there isn’t one then you should be able to re-execute the os-nova-install.yml playbook as it gets executed here: https://github.com/openstack/opensta

Re: [Openstack-operators] Moving from distro packages to containers (or virtualenvs...)

On 13 May 2016 at 19:59, Joshua Harlow wrote: > > So I guess its like the following (correct me if I am wrong): > > openstack-ansible > - > > 1. Sets up LXC containers from common base on deployment hosts (ansible > here to do this) > 2. Installs things into those containers (virt

Re: [Openstack-operators] [OpenStack-Ansible] Liberty to Mitaka upgrade?

On 20 April 2016 at 04:27, Dale Baley wrote: > Is there a document or guide for upgrading from Liberty to Mitaka yet? > Hi Dale, The active work to test and implement any plays to assist with upgrades has not yet been implemented for Liberty->Mitaka. We hope to do this work by Newton Milestone-

Re: [Openstack-operators] [OpenStack-Ansible] Liberty and Ubuntu 16.04

On 6 April 2016 at 13:50, Andreas Vallin wrote: > Hi > I am wondering if there will be possible to run Ubuntu 16.04 LTS with > Liberty and the openstack-ansible project? Are you planning to "support" > that? > Hi Andreas, Support for Ubuntu 16.04 LTS is work that will be done in the Newton cycl

[Openstack-operators] [OpenStack-Ansible] Mitaka release

tinuing work on Multi-OS enablement, adding support for Ubuntu 16.04 LTS, taking advantage of Ansible 2.x, revisiting the dynamic inventory with a view on how environments are deployed across regions and with Cells v2, and of course adding support for Liberty->Mitaka upgrades. -- Jesse Pretori

Re: [Openstack-operators] [openstack-ansible] Mid Cycle Sprint

Hi everyone, Thank you all for responding and giving your feedback. Given that the Ops Mid Cycle [1] is in the UK (15-16 Feb) and AnsibleFest [2] is also in the UK (18 Feb), and also that everyone seems ok with the UK as a location for the mid cycle then we shall have it in the UK! The Ops Mid C

[Openstack-operators] [openstack-ansible] Mid Cycle Sprint

provement (best practises, testing, how to develop a new role, etc) - Upgrade Framework [2] - Multi-OS Support [3] [1] https://etherpad.openstack.org/p/oa-install-docs [2] https://etherpad.openstack.org/p/openstack-ansible-upgrade-framework [3] https://etherpad.openstack.org/p/openstack-ansible-mu

Re: [Openstack-operators] Keystone audit logs with haproxy

On 25 November 2015 at 05:40, Ajay Kalambur (akalambu) wrote: > Hi > Have a deployment where keystone sits behind a ha proxy node. Now > authentication requests are made to a vip. Problem is when there is an > authentication failure we cannot track the remote ip that failed login as > all authent

Re: [Openstack-operators] Ansible-OpenStack:cannot ssh into the containers

On 24 November 2015 at 17:02, Achi Hamza wrote: > Hi, > > I am trying to deploy openstack using openstack-ansible project. I am > using Liberty release (tag *12.0.0*). > The problem i have is that Ansible is not able to SSH into the containers: > > *TASK: [Wait for ssh to be available] >

[Openstack-operators] [keystone] Request for Feedback: Online database migrations

] https://review.openstack.org/245186 -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Spec Review Time :)

On 20 November 2015 at 03:35, Tom Fifield wrote: > > > https://review.openstack.org/#/q/status:open+AND+project:openstack/nova-specs,n,z > > FYI, it's possible to use some regex in your query - for example this will give you all currently open specs in all specs repositories: https://review.ope

[Openstack-operators] [openstack-ansible] Documentation update planning

ase add to the etherpad [2], respond to this email and ideally be in the meeting. :) [1] https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting [2] https://etherpad.openstack.org/p/oa-install-docs -- Jesse Pretorius IRC:

[Openstack-operators] [openstack-ansible] Fedora/CentOS/other Support

ne who's interested. If you're actually happy to volunteer to assist with the work, please feel free to add a note to that effect on the etherpad. [1] https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting [2] https://etherpad.openstack.org/p/openstack-ansibl

[Openstack-operators] [openstack-ansible] Mitaka Summit Summary

Hi everyone, I've put together some thoughts based on the Mitaka Summit from the OpenStack-Ansible point of view: http://odyssey4me.github.io/openstack/ansible/mitaka/summit/2015/11/17/mitaka-summit.html Please feel free to ping me with any feedback! Thanks, -- Jesse Pretorius IRC: odyss

[Openstack-operators] [openstack-ansible] Mitaka Summit Schedule

fully? We are very interested in gathering feedback from a broad group of OpenStack operators based on the above topics and would love to have your feedback! -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-oper

[Openstack-operators] [openstack-ansible] Mitaka Summit sessions

[1] https://review.openstack.org/#/q/project:openstack/openstack-ansible-specs+status:open,n,z -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-ansible] Release: Kilo 11.1.0

Hi everyone, The openstack-ansible community is pleased to announce our release of the Kilo 11.1.0 milestone. This release fixes 57 bugs and implements 4 major blueprints, including: * Keystone as a Federated Identity Provider * Keystone as a Federated Service Provider * Horizon Federation Singl

Re: [Openstack-operators] [os-ansible-deployment][openstack-ansible] Release review/bug list for tomorrow's meeting

On 29 July 2015 at 22:04, Jesse Pretorius wrote: > The following reviews are in-flight and are important for the upcoming > releases, and therefore there is a need for more reviews and in some cases > backports once the master patches have landed: > https://review.openstack.org/#

Re: [Openstack-operators] [openstack-dev] [openstack-ansible] [os-ansible-deployment] Kilo -> Liberty Upgrade Problems

I'm adding openstack-operators too as this is a discussion that I think it would be useful to have their input for. On 30 July 2015 at 19:18, Ian Cordasco wrote: > Hey all, > > As you may have seen elsewhere on openstack-dev, OpenStack is changing the > versioning for the service projects. This

[Openstack-operators] [os-ansible-deployment][openstack-ansible] Release review/bug list for tomorrow's meeting

it or not in time for the release. We’ll discuss everything in the list in the meeting and decide on the best course of action. -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http

Re: [Openstack-operators] OSAD for RHEL

On 9 July 2015 at 05:54, John Dewey wrote: > IMO - registering the systems with subscription manager or pointing to in > house yum repos should be included as part of system bootstrapping, and not > a part of OSAD. OSAD should simply install the specific packages for the > alternate distro. > A

[Openstack-operators] [os-ansible-deployment] Feedback on Keystone Federation Spec

ck-ansible/+spec/keystone-sp-adfs-idp -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Collaborative Logstash filter development

f IRC discussion to figure out how best to organise this and to identify next steps? -- Jesse Pretorius IRC: odyssey4me ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/open

Re: [Openstack-operators] 100% CPU and hangs if syslog is restarted

On 28 May 2015 at 22:45, Nick Jones wrote: > > On 28 May 2015, at 19:10, Tim Bell wrote: > > Using UDP is a great workaround but it does not feel like a fix... can't > the daemons realise that the syslog socket is not alive and reconnect. > Given it affects most of the OpenStack projects, a fix i

Re: [Openstack-operators] OpenSource ELK configurations

On 27 May 2015 at 20:58, Joe Gordon wrote: > > On Wed, May 27, 2015 at 12:27 PM, Joseph Bajin > wrote: > >> I think those from the Infra Project are a great start, but I do think >> they are missing a lot. >> > > I am sure they are, and we would love contributions to make them better. > The filt

Re: [Openstack-operators] Specifying multiple tenants for aggregate_multitenancy_isolation_filter

On 28 January 2015 at 06:19, Tim Bell wrote: > +1 for commas. Configuration files with JSON is OK but commas for CLIs. > +1 for commas from an operator perspective ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lis

Re: [Openstack-operators] Migrating instances according to load on host

The closest thing I've seen to that has been the IBM Resource Scheduler (closed source) and this: https://github.com/BMDan/OpenStack-Hypervisor-Balance I've not tried it myself. There have been discussions around doing this, but I've not seen code submissions yet. On Tue, 16 Dec 2014 at 20:19 Sł

Re: [Openstack-operators] OpenStack Storage Backend: Sheepdog, Ceph, or GlusterFS

On 6 November 2014 13:01, Hossein Zabolzadeh wrote: > Thanks for your opinion. But I am looking for the real difference > between them... > - Which one is better support in openstack? > - Which one provides better unified storage backend for all openstack > storage controllers(cinder, swift and g

Re: [Openstack-operators] Architecture Opinions

2014 15:06, Jesse Pretorius wrote: > I would recommend ensuring that: > > 1) ceph-mon's and ceph-osd's are not hosted on the same server - they both > demand plenty of cpu cycles > The ceph-mon will generally not use much CPU. If a whole chassis is lost, you'll see it

Re: [Openstack-operators] Architecture Opinions

On 29 September 2014 23:28, Erik McCormick wrote: > The architecture I intended to deploy was this: > > 2 HAProxy nodes to load balance active / active APIs and Horizon > 2 HAProxy nodes to load balance a Galera Mysql cluster > 2 Control nodes with all API services > 3 Galera / MySQL nodes > 3 Mo