Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

Ahh.. Ok, when I read "InterOp Challenge" that sounded like an event and not a tool. Since it is a tool, then it totally makes sense, and it could be used to evaluate a platform which I would agree with you may not necessarily be an operator tool, but could be something they would use. I just

Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

Hi Katherine.. The OsOps Working Group meets on the Odd Wednesday's at 1900 UTC in #openstack-meetings-4. You can find out more here - http://eavesdrop.openstack.org/#OpenStack_OSOps/Monitoring_and_Tools_Working_Group Thanks Joe On Wed, Aug 31, 2016 at 5:07 PM, Catherine Cuong Diep

Re: [Openstack-operators] Designate service

A bit late replying, but we're deploying something similar to production (using Mitaka but the initial work was done with Liberty) this month. (It's been working great in our sandbox) We posted it on GitHub: https://github.com/cybera/cybera-designate-handler There's several other great examples

Re: [Openstack-operators] Delete cinder service

Just be careful with LIMIT x on your servers if you have replicated mysql databases. At least under older versions of mysql this can lead to broken replication as the results of the query performed on the master and on the slave are not guaranteed to be the same.

[Openstack-operators] [recognition] AUC Recognition WG Meeting Reminder (09/01)

Hi everyone, The AUC recognition WG will be meeting on September 1st, 2016 at 1900 UTC. The details can be found on our wiki page[1]. See you there! *Agenda* * Review feedback from Ops Meetup ** https://etherpad.openstack.org/p/NYC-ops-AUC * Develop plan to close out WG in next 2-3 weeks [1]

Re: [Openstack-operators] Converged infrastructure

I proposed a talk for the Summit which unfortunately did not make it. We overprovision compute nodes with memory enough for Ceph to run and we isolate an N number of cores dedicated for the OSD processes. That way, there is no competition between VMs and OSDs. We run all SSD and it has been

Re: [Openstack-operators] Delete cinder service

On 9/1/16, 9:51 AM, "Nick Jones" wrote: On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote: > On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote: > :I've used direct database update to achive this in Mitaka: > :use cinder;

Re: [Openstack-operators] Delete cinder service

On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote: On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote: :I've used direct database update to achive this in Mitaka: :use cinder; :update services set deleted = '1' where ; I belive the official way is: cinder-manage service

Re: [Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

Jonathan D. Proulx wrote: On Thu, Sep 01, 2016 at 01:50:40PM +0200, Ihar Hrachyshka wrote: :ml2_conf.ini is to be loaded by neutron-server only. The agent should :not load it, instead relying on openvswitch_agent.ini file for :anything agent specific. If for some reason

Re: [Openstack-operators] Delete cinder service

Hello William, if you changed the cinder host name you need also to reflect this change in the database for the existing volumes. in mysql you have to do something like: update volumes set host='newhostname#DEFAULT' where host = 'oldhostname#DEFAULT'; update volumes set host='newhostname' where

Re: [Openstack-operators] Delete cinder service

On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote: :I've used direct database update to achive this in Mitaka: :use cinder; :update services set deleted = '1' where ; I belive the official way is: cinder-manage service remove Which probably more or less does the same thing...

Re: [Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

On Thu, Sep 01, 2016 at 01:50:40PM +0200, Ihar Hrachyshka wrote: :ml2_conf.ini is to be loaded by neutron-server only. The agent should :not load it, instead relying on openvswitch_agent.ini file for :anything agent specific. If for some reason puppet does put agent :configuration options into

Re: [Openstack-operators] Delete cinder service

I've used direct database update to achive this in Mitaka: use cinder; update services set deleted = '1' where ; So far I didn't encounter any negative consequences of this method. 2016-09-01 16:06 GMT+03:00 William Josefsson : > Hi, > > I changed a hostname on my

[Openstack-operators] [Massively distributed] Description proposal

Dear all, Following intensive discussions on the dev mailing list, we've just started to write a description of the Massively Distributed WG: https://etherpad.openstack.org/p/massively-distributed_WG_description I strongly encourage every person that is interested by Multi-site

[Openstack-operators] Delete cinder service

Hi, I changed a hostname on my cinder node, and now I can see two entries in 'cinder service-list'. How do I delete the old entry, there is no 'cinder service-delete'? In meantime, I have disabled the old service. Google mention cinder-manage, but I don't have that tool available on my server

Re: [Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

Jonathan D. Proulx wrote: Hi All, I'm woking on testing my jump from Kilo->Mitaka Using puppet on ubuntu 14.04 with cloud archive packages. Puppet seems to be writing the ml2/ovs configs into /etc/neutron/plugins/ml2/ml2_conf.ini which is where the previously were, so

Re: [Openstack-operators] [kolla] question of default users for operators

Blair, I wanted to get back to you with what we ended up with in Kolla Newton, as well as our z streams of Liberty and Mitaka. We decided not to create a default user as a result of this thread. We did decide to create a member role to match the defaults shipped in horizon's configuration