Re: [Openstack] nova scheduler: AggregateMultiTenancyIsolation enhanced for domain level tenancy

Hi, I never thought about domains but it seems a great idea! If you want to extend it would be great. Remember that at the moment the "AggregateMultiTenancyIsolation" filter only guaranties that the nodes in the aggregate will run instances from the specified tenant. But it isn't exclusive… Ther

[Openstack] nova scheduler: AggregateMultiTenancyIsolation enhanced for domain level tenancy

Hi, I was poking around for a way to scope host aggregates at the domain level and moreover support the notion multiple tenant access. For example: * As an Cloud provider, I want to isolate aggregates/availability zones at the domain level (i.e. assign which domain can spawn instances on a gi

Re: [Openstack] Nova Scheduler issue

Oh don't worry. The nova-scheduler and other nova components will take care all of it. Just run the disable nova-compute command and run another instance. You'll see. On Thu, Jul 12, 2012 at 4:16 PM, Trinath Somanchi wrote: > Thanks for the reply. > > If I stop the Nova-Compute in Essex-1 machine

Re: [Openstack] Nova Scheduler issue

Thanks for the reply. If I stop the Nova-Compute in Essex-1 machine. then How will Controller and Nodes communicate via libvirt where in turn Nova-compute handles it.? On Thu, Jul 12, 2012 at 1:00 PM, Sébastien Han wrote: > $ sudo nova-manage service disable --host=ESSEX-1 --service nova-comput

Re: [Openstack] Nova Scheduler issue

$ sudo nova-manage service disable --host=ESSEX-1 --service nova-compute It's also good to read the documentation before asking questions. http://docs.openstack.org/essex/openstack-compute/admin/content/managing-the-cloud.html#d6e6254 Cheers. On Thu, Jul 12, 2012 at 9:14 AM, Christian Wittwer w

Re: [Openstack] Nova Scheduler issue

You can just stop nova-compute on the essex-1 node. 2012/7/12 Trinath Somanchi > Hi- > > I have installed Openstack on a Machine ESSEX-1 which is the controller > and Nova-Compute on another machine ESSEX-2 which acts as an agent/node. > > When ever I start an new instance, the VM instance is ge

[Openstack] Nova Scheduler issue

Hi- I have installed Openstack on a Machine ESSEX-1 which is the controller and Nova-Compute on another machine ESSEX-2 which acts as an agent/node. When ever I start an new instance, the VM instance is getting created in the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the agent/node

Re: [Openstack] Nova scheduler

To: Neelakantam Gaddam > Cc: openstack@lists.launchpad.net > Subject: Re: [Openstack] Nova scheduler > > you should use admin credentials ,then run instances by adding an > option --force_hosts=node1 to nova boot . > > 2012/6/19 Neelakantam Gaddam : > > Hi All, > > > > Nov

Re: [Openstack] Nova scheduler

@lists.launchpad.net] On Behalf Of heut2008 Sent: Tuesday, June 19, 2012 2:30 PM To: Neelakantam Gaddam Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Nova scheduler you should use admin credentials ,then run instances by adding an option --force_hosts=node1 to nova boot . 2012/6

Re: [Openstack] Nova scheduler

Even simpler yesThanks Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 19 juin 2012 à 11:00, heut2008 a écrit :you should use admin credentials  ,then run instances  by adding  anoption --force_hosts=node1  to nova boot  .2012/6/19 Neelakantam Gaddam :Hi All,Nova s

Re: [Openstack] Nova scheduler

Hi, you can find here the available filters : http://nova.openstack.org/devref/filter_scheduler.htmlHere are the ones you might look at : IsolatedHostsFilter JsonFilterDifferentHostFilter /SameHostFilter Razique Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 19 juin 2012 à 10:54, Neelak

Re: [Openstack] Nova scheduler

you should use admin credentials ,then run instances by adding an option --force_hosts=node1 to nova boot . 2012/6/19 Neelakantam Gaddam : > Hi All, > > Nova scheduler  decides the compute host for the VM instances to run based > on the selected scheduling algorithm. Is it possible to choose

[Openstack] Nova scheduler

Hi All, Nova scheduler decides the compute host for the VM instances to run based on the selected scheduling algorithm. Is it possible to choose a particular compute host for each request where a VM instance should run ? -- Thanks & Regards Neelakantam Gaddam __

Re: [Openstack] [nova-scheduler] Question

wrote: -To: openstack@lists.launchpad.netFrom: Leander Bessa Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 05/04/2012 09:01PMSubject: [Openstack] [nova-scheduler] QuestionHello,I have a question about nova-scheduler. I believe that, in order to have viable values

Re: [Openstack] [nova-scheduler] Question

Yes. By default, once in two minutes host's capabilities are refreshed in nova-scheduler. These capabilities are then used along with data from DB to form current host capabilities. After that, resources used by each instance on the host are subtracted from it. The result containing the actual amo

[Openstack] [nova-scheduler] Question

Hello, I have a question about nova-scheduler. I believe that, in order to have viable values supplied to the scheduler filters, it gathers the most recent state from each of the compute host. However, i've read through the documentation and haven't found any explicit statement which confirm my su