[Openstack-operators] Expected behavior of disabled nova service

Hi everyone, I have a setup with 2 controllers and 2 compute nodes. For testing purposes, I want to make sure that when I send a request for launching a new instance, it's being processed by a particular scheduler. For this I have several options: 1) ssh to controller with scheduler I don't

[Openstack-operators] centos 7 newton nova-cmpute errot

Hello All, My openstack newton installation worked fine until today. Now I am not able to start nova compute on compute nodes the following errors appear in nova-compute.log: 2017-05-08 12:38:46.890 21922 INFO oslo.privsep.daemon [req-706bded2-801b-479f-af25-41f2d7a44d83 - - - - -] Running pr

Re: [Openstack-operators] [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively Distributed Cloud Sessions during the summit

Hello, In behalf of the User Community I would like to understand if this is considering officially to request to create the Working Group. I could have missed another email request the inclusion but if not, I would like to discuss the goals and objective from the WG. The User Committee will be

Re: [Openstack-operators] [openstack-dev][heat]desire your feedback and join! And welcome on board!

. 2017-05-04 12:08 GMT+08:00 Rico Lin : > Hi all, > > Boston Summit is near, and we need your help and feedback! We really hope > to improve your orchestration experiences, > so *if you're a User, Operator, or Developer,* please join us on > *`Large Orchestration Stacks >

Re: [Openstack-operators] [openstack-dev] [MassivelyDistributed] Fog / Edge / Massively Distributed Cloud Sessions during the summit

Dear Edgar, As indicated into the WG chairs' session pad [1], the WG was previously entitled ``Massively Distributed Cloud''. The description appears on the WG wiki page [2] (and I sent an email to the user ML a few months ago to ask for the official creation [3]). After exchanging with the

Re: [Openstack-operators] [nova] Anyone using the scheduler trusted filter?

Le 05/05/2017 17:22, Mike Perez a écrit : > Hey all, > > This filter has been experimental since its existence: May 28, 2012 [1]. There > are still no third-party tests to prove if this code is functional. I would > like to understand how many people are using it, and how well it's working for >

Re: [Openstack-operators] Expected behavior of disabled nova service

As I understand it, the behaviour *should* be that any active nova-conductor or nova-scheduler could possibly process any outstanding work item pulled from the RPC queue. I don't think that nova-conductor and nova-scheduler need to be co-located. I think you might have found a bug though...I'