Re: [Openstack] Nova scheduler

[heut2008]

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 a particular
> compute host for each request where a VM instance should run  ?
>
> --
> Thanks & Regards
> Neelakantam Gaddam
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova scheduler

[Razique Mahroua]

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, Neelakantam Gaddam a écrit :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 & RegardsNeelakantam Gaddam
___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova scheduler

[Razique Mahroua]

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 scheduler  decides the compute host for the VM instances to run basedon the selected scheduling algorithm. Is it possible to choose a particularcompute host for each request where a VM instance should run  ?--Thanks & RegardsNeelakantam Gaddam___Mailing list: https://launchpad.net/~openstackPost to     : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova scheduler

[Vaze, Mandar]

When I tried this on post-essex release code, I got :
error: unrecognized arguments: --force_hosts=

Try --hint force_hosts= instead

-Mandar

-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=nttdata@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/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 a 
> particular compute host for each request where a VM instance should run  ?
>
> --
> Thanks & Regards
> Neelakantam Gaddam
>
> ___
> Mailing list: https://launchpad.net/~openstack Post to     : 
> openstack@lists.launchpad.net Unsubscribe : 
> https://launchpad.net/~openstack More help   : 
> https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova scheduler

[Neelakantam Gaddam]

Hi Mandar,

Thanks for your help.

This command is working for me.

Regards
Neelakantam

On Wed, Jun 20, 2012 at 11:37 AM, Vaze, Mandar wrote:

> When I tried this on post-essex release code, I got :
>error: unrecognized arguments: --force_hosts=
>
> Try --hint force_hosts= instead
>
> -Mandar
>
> -Original Message-
> From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net[mailto:
> openstack-bounces+mandar.vaze=nttdata@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/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 a
> > particular compute host for each request where a VM instance should run
> ?
> >
> > --
> > Thanks & Regards
> > Neelakantam Gaddam
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack Post to :
> > openstack@lists.launchpad.net Unsubscribe :
> > https://launchpad.net/~openstack More help   :
> > https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> __
> Disclaimer:This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data.  If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding
>



-- 
Thanks & Regards
Neelakantam Gaddam
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [nova-scheduler] Question

[Yuriy Taraday]

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 amounts for free resources is then passed to
filters and cost functions.

Kind regards, Yuriy.


On Fri, May 4, 2012 at 5:01 PM, Leander Bessa  wrote:
> 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
> suspicious.
>
> Long story short, is this the behavior of nova-scheduler?
>
> Regards,
>
> Leander
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [nova-scheduler] Question

[Yong Sheng Gong]

hi,see my blog post: https://www.ibm.com/developerworks/mydeveloperworks/blogs/e93514d3-c4f0-4aa0-8844-497f370090f5/entry/openstack_nova_scheduler_and_its_algorithm27?lang=enyou will have a good understand of the nova scheduler.enjoy it.-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net 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 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 suspicious.
Long story short, is this the behavior of nova-scheduler?Regards,Leander
___Mailing list: https://launchpad.net/~openstackPost to     : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova Scheduler issue

[Christian Wittwer]

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 getting created in
> the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the agent/node.
>
> Please kindly help me on how to restrict/instruct the controller to create
> the VM instances only on the Agent/Nodes only.
>
> Thanking you for the help.
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova Scheduler issue

[Sébastien Han]

$ 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 wrote:

> 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 getting created in
>> the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the agent/node.
>>
>> Please kindly help me on how to restrict/instruct the controller to
>> create the VM instances only on the Agent/Nodes only.
>>
>> Thanking you for the help.
>>
>>
>> --
>> Regards,
>> --
>> Trinath Somanchi,
>> +91 9866 235 130
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova Scheduler issue

[Trinath Somanchi]

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-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 wrote:
>
>> 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 getting created in
>>> the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the agent/node.
>>>
>>> Please kindly help me on how to restrict/instruct the controller to
>>> create the VM instances only on the Agent/Nodes only.
>>>
>>> Thanking you for the help.
>>>
>>>
>>> --
>>> Regards,
>>> --
>>> Trinath Somanchi,
>>> +91 9866 235 130
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Nova Scheduler issue

[Nguyen Son Tung]

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. 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-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 
>> wrote:
>>>
>>> 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 getting created in
 the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the 
 agent/node.

 Please kindly help me on how to restrict/instruct the controller to
 create the VM instances only on the Agent/Nodes only.

 Thanking you for the help.


 --
 Regards,
 --
 Trinath Somanchi,
 +91 9866 235 130


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Nguyen Son Tung
Cellphone: 0942312007
Skype: neophilo

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[Belmiro Moreira]

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…
There is a blueprint to extend it: 
https://blueprints.launchpad.net/nova/+spec/multi-tenancy-isolation-only-aggregates
At CERN we already implemented this blueprint and we also support of multiple 
tenants in the same aggregate. We use this filter to have dedicated resources 
for some tenants.

I didn't upload the code yet… in my TODO list 
but also waiting for the blueprint approval.

cheers,
Belmiro


On May 3, 2013, at 8:21 PM, boden  wrote:

> 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 given 
> aggregate/az)
> * As an Cloud provider, I want to isolate aggregates/availability zones at 
> the domain level and permit multiple domains or projects access (i.e. same as 
> previous UC but permit a set of domains access to the aggregate/az)
> 
> I came across the AggregateMultiTenancyIsolation scheduler filter and it 
> appears it might be fairly simple to enhance this filter to:
> (a) support domains in addition to tenants/project (i.e. filter_domain_id in 
> aggregate metadata)
> (b) support multiple domains/projects access (i.e. allow a comma list or 
> array or domains/tenants on the aggregate metadata)
> 
> Anyone else see a need for this?
> 
> Disclaimer: nova n00b here, so my above assertions may be off target.
> 
> Thx
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp