Re: [Openstack-operators] RabbitMQ 3.6.x experience?

On Tue, Jan 10, 2017 at 4:08 PM, Sam Morrison wrote: > > > On 10 Jan 2017, at 11:04 pm, Tomáš Vondra wrote: > > > > The version is 3.6.2, but the issue that I believe is relevant is still > not fixed: > >

Re: [Openstack-operators] RabbitMQ 3.6.x experience?

> On 10 Jan 2017, at 11:04 pm, Tomáš Vondra wrote: > > The version is 3.6.2, but the issue that I believe is relevant is still not > fixed: > https://github.com/rabbitmq/rabbitmq-management/issues/41 > Tomas > Yeah we found this version unusable, 3.6.5 hasn’t had any

Re: [Openstack-operators] [openstack-dev] [nova] [placement] Which service is using port 8778?

We use virtual hosts, haproxy runs on our VIP at port 80 and port 443 (SSL) (with keepalived to make sure it’s always running) and we use `use_backend` to send to the appropriate backend, more information here:

Re: [Openstack-operators] [openstack-dev] [nova] [placement] Which service is using port 8778?

On Tue, Jan 10, 2017 at 6:00 AM, Andy McCrae wrote: > Sorry to resurrect a few weeks old thread, but I had a few questions. > >> >> Yes, we should stop with the magic ports. Part of the reason of >> switching over to apache was to alleviate all of that. >> >> -Sean

Re: [Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

We’ve had a wonderful experience with Molecule and testing roles with it, I really think it’s one of the best tools out there. It’s also useful for testing, `molecule converge` and you have a full dev env that you can reconverge till you get to the state you want. > On Jan 10, 2017, at 2:15

Re: [Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

On a similar note, if you’re looking to test Ansible roles, have a look at molecule. https://molecule.readthedocs.io On January 10, 2017 at 7:42:02 AM, Stig Telfer (stig.openst...@telfer.org) wrote: Hi All - We’ve just published the sources and a detailed writeup for some new tools for

[Openstack-operators] minutes for openstack operators meetups team meeting 2017-1-10

Meeting ended Tue Jan 10 16:00:54 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 11:00 AM Minutes: http://eavesdrop.openstack.org/meetings/ops_meetups_team/2017/ops_meetups_team.2017-01-10-15.02.html 11:01 AM Minutes (text):

[Openstack-operators] Ansible-driven management of Dell server BIOS and RAID config

Hi All - We’ve just published the sources and a detailed writeup for some new tools for Ansible-driven management of Dell iDRAC BIOS and RAID configuration: https://www.stackhpc.com/ansible-drac.html The code’s up on Github and Ansible Galaxy. It should fit neatly into any infrastructure

[Openstack-operators] Mitaka to Newton Provider network issues

Hi All, We are currently on the process of upgrading from Mitaka to Newton, and on the upgraded compute nodes we lost all connectivity on provider networks. After digging through the ovs and ovs agent, we found that if we have only ONE provider network configured everything works as

Re: [Openstack-operators] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz wrote: > Hey everyone, > > We're going to be running a small midcycle/sprint on January 11-12, > 2017 in #puppet-openstack on freenode. We will be reviewing the work > items for Ocata and doing some bug triage. Feel free to add

[Openstack-operators] [scientific][scientific-wg] Reminder: Scientific WG meeting Tuesday 2100 UTC

Greetings all - We have a Scientific WG IRC meeting on Tuesday at 2100 UTC on channel #openstack-meeting. The agenda is available here[1] and full IRC meeting details are here[2]. This week we’d like get our calendars out and talk about upcoming events for 2017, in particular anything that

Re: [Openstack-operators] [User-committee] User Survey: Pre-launch check

Hi Heidi, In the Answers for "Which OpenStack Network (Neutron) drivers are you using?" (box E80), I think you should delete "Modular Layer 2 Plugin (ML2)". ML2 is an implementation option (and the strongly recommended one) for the vendors (including me) who provide networking drivers; it is not