Chris Laco

Yes. I guess "lots of choices" is my complaint. knife-vagrant is dead at this point because of the gem vs omnibus vagrant, json conflicts, etc, so I can't just weasel->vagrant...

@spheromak The workflow issue I have is, I'm on OSX. I do Vagrant. Some co workers, and Jenkins, don't. So trying to find a sane simple way to go from...

@spheromak So, here's the gap for me. I may be off my rocker, but the first thing I do after installing chef server is make it the first node I...

@jameswthorne Can you tell me a little about this environment? I just did a fresh install of v4.2.2 on Ubuntu, and I looks like it is being monitoring in my...

@jameswthorne Is the RPC SE Lab also using the single controller role setup? I doing the full ha-controller1/2 that i is the official way, and it is there. I suspect...

Specifically... ha-controller1/2 roles have `"role[nova-api-metadata]"`, but single-controller nor single-network-node doesn't, so the monitoring wouldn't trigger a drop of the conf.d monit files if it doesn't see the nova-api-metadata in the...

@jameswthorne Ok, I want to say that everything is expected given the code/commit messages. The recommend install is to use hacontroller1 instead of single-controller. On Ubuntu, there is indeed a...

Do you have a chef-client run output you can post? In the code, the change notification for that file is subscribed to by the neutron service for non-https configurations: https://github.com/rcbops-cookbooks/nova-network/blob/3c1cad909cf2589d12756bca6cd518729bc8d41f/recipes/neutron-server.rb#L114

@willkelly Can you drop your [sanitized] env json in here to test with? Also, I assume this is the normal run lists (hacontroller1, hacontroller2, single-compute)?

@pellaeon I assume this a case where you have single-network-node on a machine separate from single-controller?