Re: [Openstack] [openstack-dev] Nova PTL candidacy

2012-09-06 Thread Sateesh Chodapuneedi 
+1 for Vish

Regards,
Sateesh


This e-mail message is for the sole use of the intended recipient(s) and may 
contain confidential and/or privileged information. Any unauthorized review, 
use, disclosure, or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message. 



-Original Message-
From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net 
[mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] 
On Behalf Of Rafi Khardalian
Sent: Thursday, September 06, 2012 11:58 PM
To: openstack@lists.launchpad.net (openstack@lists.launchpad.net); OpenStack 
Development Mailing List
Subject: Re: [Openstack] [openstack-dev] Nova PTL candidacy

On Wed, Sep 5, 2012 at 12:19 AM, Michael Still
michael.st...@canonical.com wrote:
 On 09/05/2012 06:03 AM, Matt Joyce wrote:
 Vish is also a pretty cool guy and doesn't afraid of anything.

 Vish does a great job -- many hours a day of code review and mentoring,
 puts up with criticism much more calmly than I think many would, and is
 a pleasure to work with.

+1 -- Completely agree.

---
Rafi Khardalian
Vice President, Operations | Metacloud, Inc.
Email: r...@metacloud.com | Tel: 855-638-2256, Ext. 2662

___
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 VMware support improvements

2012-02-23 Thread Sateesh Chodapuneedi 
 Also, on http://nova.openstack.org/vmwareapi_readme.html it mentions 
 nova.network.vmwareapi_net for vlan networking support, but it doesn't 
 appear to actually exist in the code - am I missing something?
You are correct, vmwareapi_net.py is removed sometime back when hypervisor 
driver api (xenapi or vmwareapi) specific network interface drivers are 
introduced and new flags  (xenapi_vif_driver for xenapi  vmware_vif_driver 
for vmwareapi. I have reported a bug (https://bugs.launchpad.net/bugs/939480) 
and proposed the updated documentation for upstream merge.

Regards,
Sateesh


This e-mail message is for the sole use of the intended recipient(s) and may 
contain confidential and/or privileged information. Any unauthorized review, 
use, disclosure, or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message. 



-Original Message-
From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net 
[mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] 
On Behalf Of Graham Hagger
Sent: Thursday, February 23, 2012 6:57 AM
To: Ewan Mellor
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Nova VMware support improvements

Right now I'd mostly like to know what the reasoning was behind making the 
driver only pick the first available local datastore, rather than making it 
configurable?  Also, on http://nova.openstack.org/vmwareapi_readme.html it 
mentions nova.network.vmwareapi_net for vlan networking support, but it doesn't 
appear to actually exist in the code - am I missing something?

At present I'm just evaluating OpenStack, but support for configurable vmware 
storage options is one of the first things I'd look to add if it gets picked up.

Right now my Python foo is somewhat lacking, but I'll happily contribute what I 
can when the need arises.

Thanks,

Graham

On Wed, Feb 22, 2012 at 2:03 AM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:

 It's generally working OK; we (Citrix) did a bit of work on it a couple of 
 months ago.  It's not going to get much attention in the near future though, 
 so if you're keen to keep it up to date you'd be more than welcome to get 
 involved.



 Cheers,



 Ewan.



 From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net 
 [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] 
 On Behalf Of Graham Hagger
 Sent: Monday, February 20, 2012 11:01 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Nova VMware support improvements



 Greetings all,



 Is anyone actively working to improve the VMware support within Nova, and is 
 there any kind of roadmap for enhancements?



 I can find general information about the direction of the project, but 
 nothing specific to VMware right now.



 Many thanks,



 Graham

___
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] Four compute-node, everytime the 1st and 2nd are choosen

2011-11-10 Thread Sateesh Chodapuneedi 
The flag (of type list) you can use is --least_cost_functions
Multiple algorithms can be specified, the default one is 
compute_fill_first_cost_fn which gives priority to the compute host 
(XenServer/ESX etc.) with more free RAM.

Regards,
Sateesh


This e-mail message is for the sole use of the intended recipient(s) and may 
contain confidential and/or privileged information. Any unauthorized review, 
use, disclosure, or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.


From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net 
[mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] 
On Behalf Of Razique Mahroua
Sent: Thursday, November 10, 2011 4:12 PM
To: Jorge Luiz Correa
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Four compute-node, everytime the 1st and 2nd are 
choosen

+1 :)

Razique Mahroua
razique.mahr...@gmail.commailto:razique.mahr...@gmail.com

[cid:image002.jpg@01CC9FD5.EC50CAF0]

Le 10 nov. 2011 à 11:27, Jorge Luiz Correa a écrit :


Is there a flag in nova.conf that permits we configure that? In documentation 
we can see that exists some algorithms used by scheduler. But, I don't know how 
to choose that one best fit our requirements.

Thanks!
:)
On Wed, Nov 9, 2011 at 1:36 PM, Ed Leafe 
ed.le...@rackspace.commailto:ed.le...@rackspace.com wrote:
On Nov 9, 2011, at 7:51 AM, Razique Mahroua wrote:

 I use the default scheduler, in fact, I've never tunned it really.
 The hypervisors all run KVM

   This is where the flag is defined in 
nova.scheduler.least_cost.pyhttp://nova.scheduler.least_cost.py/:

 32 FLAGS = flags.FLAGS
 33 flags.DEFINE_list('least_cost_functions',
 34 ['nova.scheduler.least_cost.compute_fill_first_cost_fn'],
 35 'Which cost functions the LeastCostScheduler should use.')

   Since the default weighting function is 'compute_fill_first_cost_fn', 
which, as its name suggests, chooses hosts so as to fill up one host as much as 
possible before selecting another, the pattern you're seeing is expected. If 
you change that flag to 'nova.scheduler.noop_cost_fn', you should see the hosts 
selected randomly. The idea is that you can create your own weighting functions 
that will select potential hosts in a way that best fits your needs.


-- Ed Leafe


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



--
- MSc. Correa, J.L.
___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

inline: image001.gifinline: image002.jpg___
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] Fwd: Four compute-node, everytime the 1st and 2nd are choosen

2011-11-09 Thread Sateesh Chodapuneedi 
Hi Razique,

Which scheduler are you using?
And what is the underlying hypervisor?

Regards,
Sateesh


This e-mail message is for the sole use of the intended recipient(s) and may 
contain confidential and/or privileged information. Any unauthorized review, 
use, disclosure, or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.


From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net 
[mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] 
On Behalf Of Razique Mahroua
Sent: Wednesday, November 09, 2011 3:22 PM
To: openstack (openstack@lists.launchpad.net)
Subject: [Openstack] Fwd: Four compute-node, everytime the 1st and 2nd are 
choosen

I confirm that issue,
since I've disabled the nova-compute service on the first 3 nodes, and when I 
spawn a new instance, now it goes to the last one, so the scheduler would have 
been able to choose them I've now a disbalanced farm :

Host 1 : High load (11 instances)
Host2 : Middel load (9 instance)
Host 3 : null load (0 instances)
Host 4 : null load (1 instance)

I use nova 2011.2 (Cactus stable)

Thanks

Début du message réexpédié :


De : Razique Mahroua 
razique.mahr...@gmail.commailto:razique.mahr...@gmail.com
Objet : Four compute-node, everytime the 1st and 2nd are choosen
Date : 9 novembre 2011 10:39:17 HNEC
À : openstack 
(openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

Hl all,
I've four compute-nodes, around 20 instances runing.
I've four nodes registered to nova-scheduler (nova-manage shows them)
but everytime I spawn a new instance, the 3rd an 4th node are never choosen for 
the instances.
the ressources are the same on the nodes (around 24gb of ram), they are idle, 
and available.
Can I force the scheduler to use them for an instance ?
Thanks
Razique - doc team -

inline: image001.gif___
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] instance N nics

2011-09-28 Thread Sateesh Chodapuneedi 
Yes, multiple nics are support for instance, but depends on the hypervisor 
underneath.
AFAIK, XenServer and ESX does support.

Regards,
Sateesh


This e-mail message is for the sole use of the intended recipient(s) and may 
contain confidential and/or privileged information. Any unauthorized review, 
use, disclosure, or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.


From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net 
[mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] 
On Behalf Of darkfower
Sent: Wednesday, September 28, 2011 2:13 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] instance N nics

Hi,


now instance support N nics ?
inline: image001.gif___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp