[Openstack] Nova API Extension Documentation

[Jake Dahn]

Hello all,

I would like to acquire some help from you all. As it is right now, there are a 
bunch of nova api extensions which contain 0 documentation on 
http://api.openstack.org - but instead have things scattered about the web.

I would love it if some of you would help contribute to the extension 
documentation effort, I have made up this etherpad which contains instructions 
on how to get rolling.

If you'd like to help, just get started - and if you have any questions i 
should be on irc as 'jakedahn'

Here is the etherpad: http://etherpad.openstack.org/nova-ext-docs

Thanks!
___
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] Looking for complete keystone endpoint-create example

[Luis Gervaso]

Hi,

You can use devstack, but you need to make one update. This is the way i do:

0. screen -x, and go to keystone

1. CTRL-C keystone proceess

Change keystone config:

FROM:

[catalog]
driver = keystone.catalog.backends.templated.TemplatedCatalog
template_file = /opt/stack/keystone/etc/default_catalog.templates

TO:

[catalog]
driver = keystone.catalog.backends.sql.Catalog

2. Restart your keystone process (arrow-up, to repeat the last command)

3. You can test keystone endpoints API

Regards

On Tue, Apr 3, 2012 at 5:13 AM, Lorin Hochstein wrote:

> All:
>
> I'm trying to fix the keystone docs in the "Openstack Install and Deploy
> Manual", which uses a database backend for the catalog instead of a
> template file. I cannot find a complete example that shows the
> "endpoint-create" for all of the relevant services. (DevStack uses the
> template file backend, not the database backend, so I can't use it for an
> example).
>
> In particular, do we have to create a separate endpoint for each tenant?
> Are endpointTemplates still around or are they gone now?
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO & CTO
mobile: (+34) 627983344
luis@ woorea.es
___
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] Looking for complete keystone endpoint-create example

[Yong Sheng Gong]

I think devstack is still using tempalte catalogdevstack/files/keystone.conf[catalog]driver = keystone.catalog.backends.templated.TemplatedCatalogtemplate_file = %KEYSTONE_DIR%/etc/default_catalog.templatesThese are my commands, you can add for other service:keystone service-create --name "Identity Service" --type identity keystone  endpoint-create --region RegionOne --service_id 1d2eb30e5674414884947a33b505d614 --publicurl http://localhost:5000/v2.0 --adminurl http://localhost:35357/v2.0 --internalurl http://localhost:5000/v2.0 keystone service-create --name "Image Service" --type glance keystone  endpoint-create --region RegionOne --service_id 8f2e683b8d8a4dbaa0c84afed1ceb848 --publicurl http://localhost:9292/v1 --adminurl http://localhost:9292/v1 --internalurl http://localhost:9292/v1 keystone
 service-create --name "compute Service" --type compute keystone  
endpoint-create --region RegionOne --service_id 
aca8502b8c5c4936bcf1ee510b34cb43 --publicurl http://localhost:\$\(compute_port\)s/v1.1/\$\(tenant_id\)s --adminurl http://localhost:\$\(compute_port\)s/v1.1/\$\(tenant_id\)s --internalurl http://localhost:\$\(compute_port\)s/v1.1/\$\(tenant_id\)s-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: "openstack@lists.launchpad.net (openstack@lists.launchpad.net)" From: Lorin Hochstein Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/03/2012 11:13AMSubject: [Openstack] Looking for complete keystone endpoint-create exampleAll:I'm trying to fix the keystone docs in the "Openstack Install and Deploy Manual", which uses a database backend for the catalog instead of a template file. I cannot find a complete example that shows the "endpoint-create" for all of the relevant services. (DevStack uses the template file backend, not the database backend, so I can't use it for an example). In particular, do we have to create a separate endpoint for each tenant? Are endpointTemplates still around or are they gone now?
Take care,Lorin--Lorin HochsteinLead Architect - Cloud ServicesNimbis Services, Inc.www.nimbisservices.com
___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

[Openstack] Looking for complete keystone endpoint-create example

[Lorin Hochstein]

All:

I'm trying to fix the keystone docs in the "Openstack Install and Deploy 
Manual", which uses a database backend for the catalog instead of a template 
file. I cannot find a complete example that shows the "endpoint-create" for all 
of the relevant services. (DevStack uses the template file backend, not the 
database backend, so I can't use it for an example). 

In particular, do we have to create a separate endpoint for each tenant? Are 
endpointTemplates still around or are they gone now?

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





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

[Openstack] ANN: new and better archives for OpenStack mailing lists

[Stefano Maffulli]

Did you have the feeling that traffic on the dev mailing list since
Diablo release? Well... it did!

New tool to search and retrieve messages to this and operators@ list
with some graphs on top:

http://openstack.markmail.org/

thanks Markmail and awesome Jason Hunter for the support.
stef


___
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] Limit flavors to specific hosts

[Lorin Hochstein]

Jan:

Here are two use cases from when I was at ISI. In both cases, we wanted access 
to a machine with customized hardware to improve performance of certain 
applications:

1. GPUs.  We wanted the users to be able to specify request a host that had GPU 
cards so they could run GPU-accelarated apps in their instances. 

2. Shared-memory machine. We had an SGI UV machine with specific performance 
characteristics, and sometimes we wanted to specifically launch instances on 
that machine, even if the instance could fit on one of the regular x86 boxes we 
had. So we had an extra spec with something like "system=uv".


Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





On Apr 2, 2012, at 9:23 PM, Jan Drake wrote:

> If I understand this correctly, the motivation is to be able to provide a 
> hint to schedulers on host-level appropriateness based on information 
> external to that found in the hyperviser.  
> 
> Right/Wrong/Close?
> 
> It would help to have a real-world example of where basic host resource  
> evalution for scheduling would cause a situation requiring the host-level 
> hard-coding of what is essentially a flavor-constraint.
> 
> I'll hold further thoughts for downstream.
> 
> 
> Jan
> 
> 
> On Apr 2, 2012, at 6:06 PM, Lorin Hochstein  wrote:
> 
>> Just created a blueprint for this:
>> 
>> https://blueprints.launchpad.net/nova/+spec/host-capabilities-api
>> 
>> 
>> Take care,
>> 
>> Lorin
>> --
>> Lorin Hochstein
>> Lead Architect - Cloud Services
>> Nimbis Services, Inc.
>> www.nimbisservices.com
>> 
>> 
>> 
>> 
>> 
>> On Apr 2, 2012, at 3:29 PM, Jay Pipes wrote:
>> 
>>> Can I add a feature request to the below thoughtstream? Can we make it so 
>>> that the management of these things can be done outside of config files? 
>>> i.e. via a REST API with some simple middleware exposing the particular 
>>> scheduler nodes' understanding of which capabilities/filters it is using to 
>>> apply its scheduling algorithm?
>>> 
>>> Making changes to configuration files works OK for simple uses and testing, 
>>> not so much for on-demand operations :) I say this after grumbling about 
>>> similar configuration obstacles with ratelimits.
>>> 
>>> Best,
>>> -jay
>>> 
>>> On 04/02/2012 02:37 PM, Chris Behrens wrote:
 I have some plans for being able to set arbitrary "capabilities" for
 hosts via nova.conf that you can use to build scheduler filters.
 
 Right now, there are capabilities, but I believe we're only creating
 these from hypervisor stats. You can filter on those today. What I'm
 planning on adding is a way to specify additional keyname/value pairs in
 nova.conf to supplement the capabilities we build from hypervisor stats.
 You could set things like this in your nova.conf:
 
 --host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something
 
 etc. Since capabilities are already passed to scheduler rules, you could
 add some basic filters that do:
 
 if 'instance_type_ids' in capabilities and instance_type.id not in
 capabilities['instance_type_ids']:
 return False
 
 Since host_capabilities are just arbitrary keyname/value pairs, you can
 pretty much add anything you want to --host_capabilities and then write
 some matching scheduler filter rules.
 
 That's the basic idea, anyway. The exact same behavior will apply to
 'cells' and the cells scheduler as well. (Except you'll have
 cells_capabilities= somewhere (prob nova.conf for the cells service).
 
 - Chris
 
 
 On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:
 
> Hi Folks,
> I’m looking for a capability to limit some flavours to some hosts. I
> want the mapping to be as flexible as possible, and work within a
> zone/cell (I don’t want to add zones just to get this mapping). For
> example I want to express something like:
> Host_1 supports flavours A, C
> Host_2 supports flavours A, B
> Host_3 supports flavours A, B, C
> Host_4 supports flavours D
> Ideally there would be some form of grouping to sets of flavours:
> Flavour_A is part of Flavour_Sets 1, 2, 3
> Flavour_B is part of Flavour_Sets 2, 3
> Flavour_C is part of Flavour_Sets 1, 3, 4
> Host_1 supports flavour Set 1
> Host_2 supports flavour Set 2
> Host_3 supports flavour Set 3
> Host_4 supports flavour Set 4
> >From the Essex design summit I thought that host aggregates was going to 
> >give this sort of capability, but having looked through the code that 
> >seems to be quite tightly coupled with specific hypervisor 
> >functionality, whereas this is purely a scheduler feature.
> I can see that I could define flavour group membership through the
> instanace_type_extra_specs, but not how to then associate these with
> specific hosts.
> I know I’m a tad behind some of the recent changes – so before
> sug

Re: [Openstack] (Chef) "knife openstack" with Essex RC1?

[Philipp Wollermann]

Hi,

I wrote a mail to Matt @ Opscode, who wrote that guide, some days ago inquiring 
about the state of the guide and his cookbooks repository.
He told me that it's out of date and shouldn't be used for newer versions of 
OpenStack - however there is much work going on for OpenStack Essex + Chef at 
https://github.com/rcbops/chef-cookbooks/tree/ubuntu-precise :) According to 
him, this repository will probably become the base for his own guide again, 
once he has time to work on it.

Best regards,
Philipp Wollermann

Infrastructure Engineer
CyberAgent, Inc. (Tokyo)
https://github.com/philwo


On 2012/04/03, at 1:31, Brian Parker wrote:

> Hi!
> 
> Has anyone tried following the instructions for "knife openstack" with Essex? 
>  We are trying these steps:
> 
> http://wiki.opscode.com/display/chef/OpenStack+Bootstrap+Fast+Start+Guide
> 
> When attempting "knife openstack flavor list", we are getting a "ERROR: 
> RuntimeError: Unable to parse service catalog." error because the service 
> catalog is empty in the response.
> 
> Thanks!
> 
> Brian
> ___
> 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] HELP: create VM failure

[Philipp Wollermann]

Hi Sam,

did you check /etc/nova/nova-compute.conf ?
Ubuntu has this special configuration file in which the libvirt_type is set 
again, overriding what you set in nova.conf.
I didn't notice that on my first install of OpenStack on Ubuntu, causing 
instance spawning to fail.

Best regards,
Philipp Wollermann

Infrastructure Engineer
CyberAgent, Inc. (Tokyo)
https://github.com/philwo


On 2012/04/02, at 8:35, Sam Su wrote:

> Hi Leander,
> 
> Thank you for you response.
> 
> I have double checked the value of libvirt_type in nova.conf, it is kvm, not 
> hvm. I search this problem in Google, it looks like a bug of libvirt before.
> https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/445253
> 
> I tried to change  libvirt_type=qemu and reboot system, nothing was changed.
> 
> Maybe this problem is because my Ubuntu server is installed in a VMWare VM. I 
> am planning to re-install Openstack in a physical machine.
> 
> 
> Thanks,
> Sam
> 
> 
> On Sun, Apr 1, 2012 at 3:04 PM, Leander Bessa  wrote:
> 
> Maybe you specified --libvirt_type=hvm instead of --libvirt_type=kvm in your 
> nova.conf file.
> 
> On Sun, Apr 1, 2012 at 8:44 PM, Sam Su  wrote:
> Hi, 
> 
> I am trying to deploy Openstack all-in-one environment (Nova, Glance, 
> Keystone, Dashboard ) from scratch in an Ubuntu 12.04 server, After installed 
> Nova,  I tried to create a VM with nova command but failed:
> 
> root@ubuntu:/etc/nova#  nova boot --flavor 1 --image 
> 8e7f9978-86b2-4c75-a0a8-44b0bb2a46e2 --key_name key1 VM2
> +-+--+
> |   Property  |Value |
> +-+--+
> | OS-DCF:diskConfig   | MANUAL   |
> | OS-EXT-SRV-ATTR:host| ubuntu   |
> | OS-EXT-SRV-ATTR:hypervisor_hostname | None |
> | OS-EXT-SRV-ATTR:instance_name   | instance-0002|
> | OS-EXT-STS:power_state  | 0|
> | OS-EXT-STS:task_state   | scheduling   |
> | OS-EXT-STS:vm_state | building |
> | accessIPv4  |  |
> | accessIPv6  |  |
> | adminPass   | Yj6mVrxaEiX6 |
> | config_drive|  |
> | created | 2012-04-01T19:25:54Z |
> | flavor  | m1.tiny  |
> | hostId  |  |
> | id  | c15be925-c4d8-4b76-b7c3-e94ebe513cf1 |
> | image   | Ubuntu 11.10 cloudimg amd64  |
> | key_name| key1 |
> | metadata| {}   |
> | name| VM2  |
> | progress| 0|
> | status  | BUILD|
> | tenant_id   | 2660dedf826c4510aff873c05d9d506b |
> | updated | 2012-04-01T19:25:54Z |
> | user_id | b42c715d94384aa6a66c56df44ac69b2 |
> +-+--+
> root@ubuntu:/etc/nova# nova show VM2
> +-+--+
> |   Property  |  
> Value   |
> +-+--+
> | OS-DCF:diskConfig   | MANUAL
>|
> | OS-EXT-SRV-ATTR:host| ubuntu
>|
> | OS-EXT-SRV-ATTR:hypervisor_hostname | None  
>|
> | OS-EXT-SRV-ATTR:instance_name   | instance-0002 
>|
> | OS-EXT-STS:power_state  | 0 
>|
> | OS-EXT-STS:task_state   | spawning  
>|
> | OS-EXT-STS:vm_state

Re: [Openstack] Limit flavors to specific hosts

[Jan Drake]

If I understand this correctly, the motivation is to be able to provide a hint 
to schedulers on host-level appropriateness based on information external to 
that found in the hyperviser. 

Right/Wrong/Close?

It would help to have a real-world example of where basic host resource  
evalution for scheduling would cause a situation requiring the host-level 
hard-coding of what is essentially a flavor-constraint.

I'll hold further thoughts for downstream.


Jan


On Apr 2, 2012, at 6:06 PM, Lorin Hochstein  wrote:

> Just created a blueprint for this:
> 
> https://blueprints.launchpad.net/nova/+spec/host-capabilities-api
> 
> 
> Take care,
> 
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
> 
> 
> 
> 
> 
> On Apr 2, 2012, at 3:29 PM, Jay Pipes wrote:
> 
>> Can I add a feature request to the below thoughtstream? Can we make it so 
>> that the management of these things can be done outside of config files? 
>> i.e. via a REST API with some simple middleware exposing the particular 
>> scheduler nodes' understanding of which capabilities/filters it is using to 
>> apply its scheduling algorithm?
>> 
>> Making changes to configuration files works OK for simple uses and testing, 
>> not so much for on-demand operations :) I say this after grumbling about 
>> similar configuration obstacles with ratelimits.
>> 
>> Best,
>> -jay
>> 
>> On 04/02/2012 02:37 PM, Chris Behrens wrote:
>>> I have some plans for being able to set arbitrary "capabilities" for
>>> hosts via nova.conf that you can use to build scheduler filters.
>>> 
>>> Right now, there are capabilities, but I believe we're only creating
>>> these from hypervisor stats. You can filter on those today. What I'm
>>> planning on adding is a way to specify additional keyname/value pairs in
>>> nova.conf to supplement the capabilities we build from hypervisor stats.
>>> You could set things like this in your nova.conf:
>>> 
>>> --host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something
>>> 
>>> etc. Since capabilities are already passed to scheduler rules, you could
>>> add some basic filters that do:
>>> 
>>> if 'instance_type_ids' in capabilities and instance_type.id not in
>>> capabilities['instance_type_ids']:
>>> return False
>>> 
>>> Since host_capabilities are just arbitrary keyname/value pairs, you can
>>> pretty much add anything you want to --host_capabilities and then write
>>> some matching scheduler filter rules.
>>> 
>>> That's the basic idea, anyway. The exact same behavior will apply to
>>> 'cells' and the cells scheduler as well. (Except you'll have
>>> cells_capabilities= somewhere (prob nova.conf for the cells service).
>>> 
>>> - Chris
>>> 
>>> 
>>> On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:
>>> 
 Hi Folks,
 I’m looking for a capability to limit some flavours to some hosts. I
 want the mapping to be as flexible as possible, and work within a
 zone/cell (I don’t want to add zones just to get this mapping). For
 example I want to express something like:
 Host_1 supports flavours A, C
 Host_2 supports flavours A, B
 Host_3 supports flavours A, B, C
 Host_4 supports flavours D
 Ideally there would be some form of grouping to sets of flavours:
 Flavour_A is part of Flavour_Sets 1, 2, 3
 Flavour_B is part of Flavour_Sets 2, 3
 Flavour_C is part of Flavour_Sets 1, 3, 4
 Host_1 supports flavour Set 1
 Host_2 supports flavour Set 2
 Host_3 supports flavour Set 3
 Host_4 supports flavour Set 4
 >From the Essex design summit I thought that host aggregates was going to 
 >give this sort of capability, but having looked through the code that 
 >seems to be quite tightly coupled with specific hypervisor functionality, 
 >whereas this is purely a scheduler feature.
 I can see that I could define flavour group membership through the
 instanace_type_extra_specs, but not how to then associate these with
 specific hosts.
 I know I’m a tad behind some of the recent changes – so before
 suggesting a design summit session on this I thought I’d ask - is
 there something that already does this type of mapping ?
 Cheers,
 Phil
 ___
 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

Re: [Openstack] Limit flavors to specific hosts

[Lorin Hochstein]

Just created a blueprint for this:

https://blueprints.launchpad.net/nova/+spec/host-capabilities-api


Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





On Apr 2, 2012, at 3:29 PM, Jay Pipes wrote:

> Can I add a feature request to the below thoughtstream? Can we make it so 
> that the management of these things can be done outside of config files? i.e. 
> via a REST API with some simple middleware exposing the particular scheduler 
> nodes' understanding of which capabilities/filters it is using to apply its 
> scheduling algorithm?
> 
> Making changes to configuration files works OK for simple uses and testing, 
> not so much for on-demand operations :) I say this after grumbling about 
> similar configuration obstacles with ratelimits.
> 
> Best,
> -jay
> 
> On 04/02/2012 02:37 PM, Chris Behrens wrote:
>> I have some plans for being able to set arbitrary "capabilities" for
>> hosts via nova.conf that you can use to build scheduler filters.
>> 
>> Right now, there are capabilities, but I believe we're only creating
>> these from hypervisor stats. You can filter on those today. What I'm
>> planning on adding is a way to specify additional keyname/value pairs in
>> nova.conf to supplement the capabilities we build from hypervisor stats.
>> You could set things like this in your nova.conf:
>> 
>> --host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something
>> 
>> etc. Since capabilities are already passed to scheduler rules, you could
>> add some basic filters that do:
>> 
>> if 'instance_type_ids' in capabilities and instance_type.id not in
>> capabilities['instance_type_ids']:
>> return False
>> 
>> Since host_capabilities are just arbitrary keyname/value pairs, you can
>> pretty much add anything you want to --host_capabilities and then write
>> some matching scheduler filter rules.
>> 
>> That's the basic idea, anyway. The exact same behavior will apply to
>> 'cells' and the cells scheduler as well. (Except you'll have
>> cells_capabilities= somewhere (prob nova.conf for the cells service).
>> 
>> - Chris
>> 
>> 
>> On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:
>> 
>>> Hi Folks,
>>> I’m looking for a capability to limit some flavours to some hosts. I
>>> want the mapping to be as flexible as possible, and work within a
>>> zone/cell (I don’t want to add zones just to get this mapping). For
>>> example I want to express something like:
>>> Host_1 supports flavours A, C
>>> Host_2 supports flavours A, B
>>> Host_3 supports flavours A, B, C
>>> Host_4 supports flavours D
>>> Ideally there would be some form of grouping to sets of flavours:
>>> Flavour_A is part of Flavour_Sets 1, 2, 3
>>> Flavour_B is part of Flavour_Sets 2, 3
>>> Flavour_C is part of Flavour_Sets 1, 3, 4
>>> Host_1 supports flavour Set 1
>>> Host_2 supports flavour Set 2
>>> Host_3 supports flavour Set 3
>>> Host_4 supports flavour Set 4
>>> >From the Essex design summit I thought that host aggregates was going to 
>>> >give this sort of capability, but having looked through the code that 
>>> >seems to be quite tightly coupled with specific hypervisor functionality, 
>>> >whereas this is purely a scheduler feature.
>>> I can see that I could define flavour group membership through the
>>> instanace_type_extra_specs, but not how to then associate these with
>>> specific hosts.
>>> I know I’m a tad behind some of the recent changes – so before
>>> suggesting a design summit session on this I thought I’d ask - is
>>> there something that already does this type of mapping ?
>>> Cheers,
>>> Phil
>>> ___
>>> 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

___
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] question about keystone and dashboard on RHEL6

[Xin Zhao]

On 4/2/2012 6:35 PM, Russell Bryant wrote:

On 04/02/2012 03:09 PM, Xin Zhao wrote:

Hello,

I am new to OpenStack and trying to install the diablo release on a
RHEL6 cluster. I follow instructions here:
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova

The instruction doesn't mention how to install and configure Keystone
and dashboard services, I wonder:

1) are these two services available for RHEL6, in diablo release?
2) do I need to go to the latest Essex release, and where the
instructions is?

The dashboard, horizon, is not included with the Diablo packages that
you find in EPEL6 right now.  When we update EPEL6 to Essex, which
should be within the next few weeks, horizon will be included as well.



How about keystone, the instructions here 
(http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova) doesn't
mention how to install and configure keystone, although it tells how to 
clean up keystone, which makes me think there is something

missing in the earlier sections of this instruction.

Xin

___
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] OpenStack Java SDK First Snapshot

[Stefano Maffulli]

Hi Luis,

thanks for this contribution. I know quite a few folks will be happy to
have a Java SDK to play around. 

On Mon, 2012-04-02 at 07:05 +0200, Luis Gervaso wrote:
> Actually, I want this to be temporal, I tried to release at Maven
> Central but I need some
> credentials from openstack.org community so if someone can help that's
> would be great!

> https://issues.sonatype.org/browse/OSSRH-3172
> 
I believe you'll need to talk to the Project Policy Board for this.
Using openstack.org for the Java SDK is a big deal: it may be
interpreted as an official project of OpenStack and for this it needs
approval from the board. 

I suggest you to write to openstack-...@lists.launchpad.net and cc me
(just to make sure that the message goes through, as launchpad gets
cranky sometimes).

Cheers,
stef



___
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] question about keystone and dashboard on RHEL6

[Russell Bryant]

On 04/02/2012 03:09 PM, Xin Zhao wrote:
> Hello,
> 
> I am new to OpenStack and trying to install the diablo release on a
> RHEL6 cluster. I follow instructions here:
> http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
> 
> The instruction doesn't mention how to install and configure Keystone
> and dashboard services, I wonder:
> 
> 1) are these two services available for RHEL6, in diablo release?
> 2) do I need to go to the latest Essex release, and where the
> instructions is?

The dashboard, horizon, is not included with the Diablo packages that
you find in EPEL6 right now.  When we update EPEL6 to Essex, which
should be within the next few weeks, horizon will be included as well.

-- 
Russell Bryant

___
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] Moving nova.rpc into openstack.common

[Chris Behrens]

Awesome, thanks :)

On Apr 2, 2012, at 3:46 PM, Russell Bryant wrote:

> I just threw up a patch a little while ago:
> 
> https://review.openstack.org/6119
> 
> -- 
> Russell Bryant
> 
> On 04/02/2012 06:37 PM, Chris Behrens wrote:
>> Seems like a sensible plan.  Carrot can go now.  I marked it deprecated so 
>> we can remove in folsom.  I can take care of this today, even.
>> 
>> On Apr 2, 2012, at 3:02 PM, Duncan McGreggor  wrote:
>> 
>>> +1
>>> 
>>> Thanks for exploring this, Russell!
>>> 
>>> Next step: getting a common REST API abstraction in place that all the
>>> projects can use... ;-)
>>> 
>>> d
>>> 
>>> On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant  wrote:
 Greetings,
 
 There was a thread on this list a little while ago about moving the
 notification drivers that are in nova and glance into openstack.common
 since they provide very similar functionality, but have implementations
 that have diverged over time.  Is anyone actively working on this?  If
 so, please let me know.
 
 For the message queue notifiers, nova uses nova.rpc to do the heavy
 lifting.  Glance has notifiers written against the messaging libs
 directly.  I think it makes sense to take the nova approach.  This would
 mean moving nova.rpc into openstack.common before the notifiers can get
 moved.
 
 I have started looking at moving nova.rpc to openstack.common.rpc.  My
 plan is:
 
 1) Write a series of patches that reduces coupling in nova.rpc on the
 rest of nova.
 
 2) Submit changes needed to support this decoupling to openstack.common.
 
 3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.
 
 While doing the above, I want to aim for the least amount of disruption
 to the rpc interface as is practical.
 
 While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
 marked as deprecated in Essex.  Is there any reason anyone would still
 use impl_carrot over impl_kombu?
 
 Thoughts?
 
 Thanks,
 
 --
 Russell Bryant
 
 ___
 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] Moving nova.rpc into openstack.common

[Russell Bryant]

I just threw up a patch a little while ago:

https://review.openstack.org/6119

-- 
Russell Bryant

On 04/02/2012 06:37 PM, Chris Behrens wrote:
> Seems like a sensible plan.  Carrot can go now.  I marked it deprecated so we 
> can remove in folsom.  I can take care of this today, even.
> 
> On Apr 2, 2012, at 3:02 PM, Duncan McGreggor  wrote:
> 
>> +1
>>
>> Thanks for exploring this, Russell!
>>
>> Next step: getting a common REST API abstraction in place that all the
>> projects can use... ;-)
>>
>> d
>>
>> On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant  wrote:
>>> Greetings,
>>>
>>> There was a thread on this list a little while ago about moving the
>>> notification drivers that are in nova and glance into openstack.common
>>> since they provide very similar functionality, but have implementations
>>> that have diverged over time.  Is anyone actively working on this?  If
>>> so, please let me know.
>>>
>>> For the message queue notifiers, nova uses nova.rpc to do the heavy
>>> lifting.  Glance has notifiers written against the messaging libs
>>> directly.  I think it makes sense to take the nova approach.  This would
>>> mean moving nova.rpc into openstack.common before the notifiers can get
>>> moved.
>>>
>>> I have started looking at moving nova.rpc to openstack.common.rpc.  My
>>> plan is:
>>>
>>> 1) Write a series of patches that reduces coupling in nova.rpc on the
>>> rest of nova.
>>>
>>> 2) Submit changes needed to support this decoupling to openstack.common.
>>>
>>> 3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.
>>>
>>> While doing the above, I want to aim for the least amount of disruption
>>> to the rpc interface as is practical.
>>>
>>> While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
>>> marked as deprecated in Essex.  Is there any reason anyone would still
>>> use impl_carrot over impl_kombu?
>>>
>>> Thoughts?
>>>
>>> Thanks,
>>>
>>> --
>>> Russell Bryant
>>>
>>> ___
>>> 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] Moving nova.rpc into openstack.common

[Chris Behrens]

Seems like a sensible plan.  Carrot can go now.  I marked it deprecated so we 
can remove in folsom.  I can take care of this today, even.

On Apr 2, 2012, at 3:02 PM, Duncan McGreggor  wrote:

> +1
> 
> Thanks for exploring this, Russell!
> 
> Next step: getting a common REST API abstraction in place that all the
> projects can use... ;-)
> 
> d
> 
> On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant  wrote:
>> Greetings,
>> 
>> There was a thread on this list a little while ago about moving the
>> notification drivers that are in nova and glance into openstack.common
>> since they provide very similar functionality, but have implementations
>> that have diverged over time.  Is anyone actively working on this?  If
>> so, please let me know.
>> 
>> For the message queue notifiers, nova uses nova.rpc to do the heavy
>> lifting.  Glance has notifiers written against the messaging libs
>> directly.  I think it makes sense to take the nova approach.  This would
>> mean moving nova.rpc into openstack.common before the notifiers can get
>> moved.
>> 
>> I have started looking at moving nova.rpc to openstack.common.rpc.  My
>> plan is:
>> 
>> 1) Write a series of patches that reduces coupling in nova.rpc on the
>> rest of nova.
>> 
>> 2) Submit changes needed to support this decoupling to openstack.common.
>> 
>> 3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.
>> 
>> While doing the above, I want to aim for the least amount of disruption
>> to the rpc interface as is practical.
>> 
>> While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
>> marked as deprecated in Essex.  Is there any reason anyone would still
>> use impl_carrot over impl_kombu?
>> 
>> Thoughts?
>> 
>> Thanks,
>> 
>> --
>> Russell Bryant
>> 
>> ___
>> 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] Swift tools with Keystone: swift-bench and swift-dispersion-*

[Chmouel Boudjnah]

There is a review on the go here:

https://review.openstack.org/#change,6088

which should address swift-dispertion to be able to connect to auth
version 2.0 servers.

Feel free to log a bug if there is other tools missing.

Chmouel.

On Mon, Apr 2, 2012 at 10:57 PM, Kevin Jackson
 wrote:
> Hello All,
> Is it possible to use Swift tools such as swift-bench and
> swift-dispersion-populate/report with Keystone?
> If so, how?  The examples refer to the SAIO configuration of authentication
> using tempauth on port 11000 but I can't find reference to what should run
> on port 11000 (I'm presuming this is the default for proxy-server or have I
> misread something?)...
>
> Cheers,
>
> Kev
> --
> Kevin Jackson
> @itarchitectkev
>
> ___
> 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

[Openstack] Issue with keystone-2012.1~rc1.tar.gz -- unable to authorize user

[Vijay]

Hello,
Installed keystone-2012.1~rc1.tar.gz. 
Following this url to configure:
http://docs.openstack.org/trunk/openstack-compute/install/content/setting-up-tenants-users-and-roles.html
 
When I tried to 
keystone --token 012345SECRET99TOKEN012345 --endpoint 
http://192.168.198.85:35357/v2.0 tenant-create --name openstackDemo 
--description "Default
Tenant" --enabled true
 
I am getting 
No handlers could be found for logger "keystoneclient.client"
Unable to authorize user

In the console log,
it says
 
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi]  
REQUEST BODY 
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] {"tenant": {"enabled": 
true, "name": "openstackDemo", "description": "Default Tenant"}}
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi]
2012-04-02 15:23:38    DEBUG [routes.middleware] Matched POST /tenants
2012-04-02 15:23:38    DEBUG [routes.middleware] Route path: '{path_info:.*}', 
defaults: {'controller': }
2012-04-02 15:23:38    DEBUG [routes.middleware] Match dict: {'controller': 
, 
'path_info': '/tenants'}
2012-04-02 15:23:38    DEBUG [routes.middleware] Matched POST /tenants
2012-04-02 15:23:38    DEBUG [routes.middleware] Route path: '/tenants', 
defaults: {'action': u'create_tenant', 'controller': 
}
2012-04-02 15:23:38    DEBUG [routes.middleware] Match dict: {'action': 
u'create_tenant', 'controller': }
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] arg_dict: {}
2012-04-02 15:23:38  WARNING [keystone.common.wsgi] The request you have made 
requires authentication.
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi]  
RESPONSE HEADERS 
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] Content-Type = 
application/json
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] Vary = X-Auth-Token
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] Content-Length = 116
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi]
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi]  
RESPONSE BODY 
2012-04-02 15:23:38    DEBUG [keystone.common.wsgi] {"error": {"message": "The 
request you have made requires authentication.", "code": 401, "title": "Not 
Authorized"}}
2012-04-02 15:23:38    DEBUG [eventlet.wsgi.server] 192.168.198.85 - - 
[02/Apr/2012 15:23:38] "POST /v2.0/tenants HTTP/1.1" 401 257 0.008317

 
Is this a bug or is something in my keystone.conf not set properly?
 
Any lead is appreciated.
Thanks,
-Vijay___
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] question about keystone and dashboard on RHEL6

[Yong Sheng Gong]

try this:http://wiki.openstack.org/NovaInstall/RHEL6Notes-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: openstack From: Xin Zhao Sent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/03/2012 03:09AMSubject: [Openstack] question about keystone and dashboard on RHEL6Hello,I am new to OpenStack and trying to install the diablo release on a RHEL6 cluster. I follow instructions here:http://fedoraproject.org/wiki/Getting_started_with_OpenStack_NovaThe instruction doesn't mention how to install and configure Keystone and dashboard services, I wonder:1) are these two services available for RHEL6, in diablo release?2) do I need to go to the latest Essex release, and where the instructions is?Thanks,Xin___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] Moving nova.rpc into openstack.common

[Duncan McGreggor]

+1

Thanks for exploring this, Russell!

Next step: getting a common REST API abstraction in place that all the
projects can use... ;-)

d

On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant  wrote:
> Greetings,
>
> There was a thread on this list a little while ago about moving the
> notification drivers that are in nova and glance into openstack.common
> since they provide very similar functionality, but have implementations
> that have diverged over time.  Is anyone actively working on this?  If
> so, please let me know.
>
> For the message queue notifiers, nova uses nova.rpc to do the heavy
> lifting.  Glance has notifiers written against the messaging libs
> directly.  I think it makes sense to take the nova approach.  This would
> mean moving nova.rpc into openstack.common before the notifiers can get
> moved.
>
> I have started looking at moving nova.rpc to openstack.common.rpc.  My
> plan is:
>
> 1) Write a series of patches that reduces coupling in nova.rpc on the
> rest of nova.
>
> 2) Submit changes needed to support this decoupling to openstack.common.
>
> 3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.
>
> While doing the above, I want to aim for the least amount of disruption
> to the rpc interface as is practical.
>
> While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
> marked as deprecated in Essex.  Is there any reason anyone would still
> use impl_carrot over impl_kombu?
>
> Thoughts?
>
> Thanks,
>
> --
> Russell Bryant
>
> ___
> 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] (Chef) "knife openstack" with Essex RC1?

[Brian Parker]

Well, I think we can see that the Knife-openstack/Fog versions used in that
wiki page are not (currently) compatible with Essex.  I hate to double
post, but I think I'll take my questions over to the Opscode mailing list.
 Sorry for the noise!

Brian

On Mon, Apr 2, 2012 at 11:31 AM, Brian Parker wrote:

> Hi!
>
> Has anyone tried following the instructions for "knife openstack" with
> Essex?  We are trying these steps:
>
> http://wiki.opscode.com/display/chef/OpenStack+Bootstrap+Fast+Start+Guide
>
> When attempting "knife openstack flavor list", we are getting a "ERROR:
> RuntimeError: Unable to parse service catalog." error because the service
> catalog is empty in the response.
>
> Thanks!
>
> Brian
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Swift tools with Keystone: swift-bench and swift-dispersion-*

[Kevin Jackson]

Hello All,
Is it possible to use Swift tools such as swift-bench and
swift-dispersion-populate/report with Keystone?
If so, how?  The examples refer to the SAIO configuration of authentication
using tempauth on port 11000 but I can't find reference to what should run
on port 11000 (I'm presuming this is the default for proxy-server or have I
misread something?)...

Cheers,

Kev
-- 
Kevin Jackson
@itarchitectkev
___
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] Moving nova.rpc into openstack.common

[Matt Dietz]

I started looking into moving the notification drivers as well, but punted
because of the reliance on multiple things, RPC included. For us, it's a
nice to have but not a need.

As for your plan, it seems sensible to me.

On 4/2/12 3:26 PM, "Russell Bryant"  wrote:

>Greetings,
>
>There was a thread on this list a little while ago about moving the
>notification drivers that are in nova and glance into openstack.common
>since they provide very similar functionality, but have implementations
>that have diverged over time.  Is anyone actively working on this?  If
>so, please let me know.
>
>For the message queue notifiers, nova uses nova.rpc to do the heavy
>lifting.  Glance has notifiers written against the messaging libs
>directly.  I think it makes sense to take the nova approach.  This would
>mean moving nova.rpc into openstack.common before the notifiers can get
>moved.
>
>I have started looking at moving nova.rpc to openstack.common.rpc.  My
>plan is:
>
>1) Write a series of patches that reduces coupling in nova.rpc on the
>rest of nova.
>
>2) Submit changes needed to support this decoupling to openstack.common.
>
>3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.
>
>While doing the above, I want to aim for the least amount of disruption
>to the rpc interface as is practical.
>
>While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
>marked as deprecated in Essex.  Is there any reason anyone would still
>use impl_carrot over impl_kombu?
>
>Thoughts?
>
>Thanks,
>
>-- 
>Russell Bryant
>
>___
>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] Limit flavors to specific hosts

[Ed_Conzel]

+1

-Original Message-
From: openstack-bounces+ed_conzel=dell@lists.launchpad.net 
[mailto:openstack-bounces+ed_conzel=dell@lists.launchpad.net] On Behalf Of 
Jay Pipes
Sent: Monday, April 02, 2012 2:29 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Limit flavors to specific hosts

Can I add a feature request to the below thoughtstream? Can we make it so that 
the management of these things can be done outside of config files? i.e. via a 
REST API with some simple middleware exposing the particular scheduler nodes' 
understanding of which capabilities/filters it is using to apply its scheduling 
algorithm?

Making changes to configuration files works OK for simple uses and testing, not 
so much for on-demand operations :) I say this after grumbling about similar 
configuration obstacles with ratelimits.

Best,
-jay

On 04/02/2012 02:37 PM, Chris Behrens wrote:
> I have some plans for being able to set arbitrary "capabilities" for 
> hosts via nova.conf that you can use to build scheduler filters.
>
> Right now, there are capabilities, but I believe we're only creating 
> these from hypervisor stats. You can filter on those today. What I'm 
> planning on adding is a way to specify additional keyname/value pairs 
> in nova.conf to supplement the capabilities we build from hypervisor stats.
> You could set things like this in your nova.conf:
>
> --host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something
>
> etc. Since capabilities are already passed to scheduler rules, you 
> could add some basic filters that do:
>
> if 'instance_type_ids' in capabilities and instance_type.id not in
> capabilities['instance_type_ids']:
> return False
>
> Since host_capabilities are just arbitrary keyname/value pairs, you 
> can pretty much add anything you want to --host_capabilities and then 
> write some matching scheduler filter rules.
>
> That's the basic idea, anyway. The exact same behavior will apply to 
> 'cells' and the cells scheduler as well. (Except you'll have 
> cells_capabilities= somewhere (prob nova.conf for the cells service).
>
> - Chris
>
>
> On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:
>
>> Hi Folks,
>> I'm looking for a capability to limit some flavours to some hosts. I 
>> want the mapping to be as flexible as possible, and work within a 
>> zone/cell (I don't want to add zones just to get this mapping). For 
>> example I want to express something like:
>> Host_1 supports flavours A, C
>> Host_2 supports flavours A, B
>> Host_3 supports flavours A, B, C
>> Host_4 supports flavours D
>> Ideally there would be some form of grouping to sets of flavours:
>> Flavour_A is part of Flavour_Sets 1, 2, 3 Flavour_B is part of 
>> Flavour_Sets 2, 3 Flavour_C is part of Flavour_Sets 1, 3, 4
>> Host_1 supports flavour Set 1
>> Host_2 supports flavour Set 2
>> Host_3 supports flavour Set 3
>> Host_4 supports flavour Set 4
>> >From the Essex design summit I thought that host aggregates was going to 
>> >give this sort of capability, but having looked through the code that seems 
>> >to be quite tightly coupled with specific hypervisor functionality, whereas 
>> >this is purely a scheduler feature.
>> I can see that I could define flavour group membership through the 
>> instanace_type_extra_specs, but not how to then associate these with 
>> specific hosts.
>> I know I'm a tad behind some of the recent changes - so before 
>> suggesting a design summit session on this I thought I'd ask - is 
>> there something that already does this type of mapping ?
>> Cheers,
>> Phil
>> ___
>> 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

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

[Openstack] Moving nova.rpc into openstack.common

[Russell Bryant]

Greetings,

There was a thread on this list a little while ago about moving the
notification drivers that are in nova and glance into openstack.common
since they provide very similar functionality, but have implementations
that have diverged over time.  Is anyone actively working on this?  If
so, please let me know.

For the message queue notifiers, nova uses nova.rpc to do the heavy
lifting.  Glance has notifiers written against the messaging libs
directly.  I think it makes sense to take the nova approach.  This would
mean moving nova.rpc into openstack.common before the notifiers can get
moved.

I have started looking at moving nova.rpc to openstack.common.rpc.  My
plan is:

1) Write a series of patches that reduces coupling in nova.rpc on the
rest of nova.

2) Submit changes needed to support this decoupling to openstack.common.

3) Once nova.rpc is sufficiently decoupled, move it to openstack.common.

While doing the above, I want to aim for the least amount of disruption
to the rpc interface as is practical.

While we're at it, is it time to drop nova.rpc.impl_carrot?  It is
marked as deprecated in Essex.  Is there any reason anyone would still
use impl_carrot over impl_kombu?

Thoughts?

Thanks,

-- 
Russell Bryant

___
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] Limit flavors to specific hosts

[Jay Pipes]

Can I add a feature request to the below thoughtstream? Can we make it 
so that the management of these things can be done outside of config 
files? i.e. via a REST API with some simple middleware exposing the 
particular scheduler nodes' understanding of which capabilities/filters 
it is using to apply its scheduling algorithm?


Making changes to configuration files works OK for simple uses and 
testing, not so much for on-demand operations :) I say this after 
grumbling about similar configuration obstacles with ratelimits.


Best,
-jay

On 04/02/2012 02:37 PM, Chris Behrens wrote:

I have some plans for being able to set arbitrary "capabilities" for
hosts via nova.conf that you can use to build scheduler filters.

Right now, there are capabilities, but I believe we're only creating
these from hypervisor stats. You can filter on those today. What I'm
planning on adding is a way to specify additional keyname/value pairs in
nova.conf to supplement the capabilities we build from hypervisor stats.
You could set things like this in your nova.conf:

--host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something

etc. Since capabilities are already passed to scheduler rules, you could
add some basic filters that do:

if 'instance_type_ids' in capabilities and instance_type.id not in
capabilities['instance_type_ids']:
return False

Since host_capabilities are just arbitrary keyname/value pairs, you can
pretty much add anything you want to --host_capabilities and then write
some matching scheduler filter rules.

That's the basic idea, anyway. The exact same behavior will apply to
'cells' and the cells scheduler as well. (Except you'll have
cells_capabilities= somewhere (prob nova.conf for the cells service).

- Chris


On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:


Hi Folks,
I’m looking for a capability to limit some flavours to some hosts. I
want the mapping to be as flexible as possible, and work within a
zone/cell (I don’t want to add zones just to get this mapping). For
example I want to express something like:
Host_1 supports flavours A, C
Host_2 supports flavours A, B
Host_3 supports flavours A, B, C
Host_4 supports flavours D
Ideally there would be some form of grouping to sets of flavours:
Flavour_A is part of Flavour_Sets 1, 2, 3
Flavour_B is part of Flavour_Sets 2, 3
Flavour_C is part of Flavour_Sets 1, 3, 4
Host_1 supports flavour Set 1
Host_2 supports flavour Set 2
Host_3 supports flavour Set 3
Host_4 supports flavour Set 4
>From the Essex design summit I thought that host aggregates was going to give 
this sort of capability, but having looked through the code that seems to be quite 
tightly coupled with specific hypervisor functionality, whereas this is purely a 
scheduler feature.
I can see that I could define flavour group membership through the
instanace_type_extra_specs, but not how to then associate these with
specific hosts.
I know I’m a tad behind some of the recent changes – so before
suggesting a design summit session on this I thought I’d ask - is
there something that already does this type of mapping ?
Cheers,
Phil
___
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

[Openstack] question about keystone and dashboard on RHEL6

[Xin Zhao]

Hello,

I am new to OpenStack and trying to install the diablo release on a 
RHEL6 cluster. I follow instructions here:

http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova

The instruction doesn't mention how to install and configure Keystone 
and dashboard services, I wonder:


1) are these two services available for RHEL6, in diablo release?
2) do I need to go to the latest Essex release, and where the 
instructions is?


Thanks,
Xin

___
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] Limit flavors to specific hosts

[Lorin Hochstein]

Phil:

I don't know of a way to do this in Essex. However, when I was working at ISI, 
we added a configuration option called "extra_node_capabilities" that allows 
you to specify the capabilities of a particular host in the 
/etc/nova/nova.conf, and these capabilities are checked against the 
extra_specs. 

See the following lines of code in ISI's repo:

https://github.com/usc-isi/nova/blob/hpc-trunk/nova/virt/libvirt/connection.py#L163
https://github.com/usc-isi/nova/blob/hpc-trunk/nova/virt/libvirt/connection.py#L2669

I don't know how much reporting of capabilities has changed from diablo to 
essex, though, so no clue if that code would still work if ported to the 
current trunk.

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





On Apr 2, 2012, at 1:36 PM, Day, Phil wrote:

> Hi Folks,
>  
> I’m looking for a capability to limit some flavours to some hosts.  I want 
> the mapping to be as flexible as possible, and work within a zone/cell  (I 
> don’t want to add zones just to get this mapping).For example I want to 
> express something like:
>  
> Host_1 supports flavours A, C
> Host_2 supports flavours A, B
> Host_3 supports flavours A, B, C
> Host_4 supports flavours D
>  
> Ideally there would be some form of grouping to sets of flavours:
>  
> Flavour_A  is part of Flavour_Sets 1, 2, 3
> Flavour_B is part of Flavour_Sets 2, 3
> Flavour_C is part of Flavour_Sets 1, 3, 4
>  
> Host_1 supports flavour Set 1
> Host_2 supports flavour Set 2
> Host_3 supports flavour Set 3
> Host_4 supports flavour Set 4
>  
>  
> From the Essex design summit I thought that host aggregates was going to give 
> this sort of capability, but having looked through the code that seems to be 
> quite tightly coupled with specific hypervisor functionality, whereas this is 
> purely a scheduler feature.
>  
> I can see that I could define flavour group membership through the 
> instanace_type_extra_specs, but not how to then associate these with specific 
> hosts. 
>  
> I know I’m a tad behind some of the recent changes – so before suggesting a 
> design summit session on this I thought I’d ask - is there something that 
> already does this type of mapping ?
>  
> Cheers,
> Phil
>  
>  
>  
> ___
> 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] Limit flavors to specific hosts

[Chris Behrens]

I have some plans for being able to set arbitrary "capabilities" for hosts via 
nova.conf that you can use to build scheduler filters.

Right now, there are capabilities, but I believe we're only creating these from 
hypervisor stats.  You can filter on those today.  What I'm planning on adding 
is a way to specify additional keyname/value pairs in nova.conf to supplement 
the capabilities we build from hypervisor stats.  You could set things like 
this in your nova.conf:

--host_capabilities=instance_type_ids=1,2,3;keyX;keyY=something

etc.  Since capabilities are already passed to scheduler rules, you could add 
some basic filters that do:

if 'instance_type_ids' in capabilities and instance_type.id not in 
capabilities['instance_type_ids']:
return False

Since host_capabilities are just arbitrary keyname/value pairs, you can pretty 
much add anything you want to --host_capabilities and then write some matching 
scheduler filter rules.

That's the basic idea, anyway.   The exact same behavior will apply to 'cells' 
and the cells scheduler as well.  (Except you'll have cells_capabilities=  
somewhere (prob nova.conf for the cells service).

- Chris


On Apr 2, 2012, at 10:36 AM, Day, Phil wrote:

Hi Folks,

I’m looking for a capability to limit some flavours to some hosts.  I want the 
mapping to be as flexible as possible, and work within a zone/cell  (I don’t 
want to add zones just to get this mapping).For example I want to express 
something like:

Host_1 supports flavours A, C
Host_2 supports flavours A, B
Host_3 supports flavours A, B, C
Host_4 supports flavours D

Ideally there would be some form of grouping to sets of flavours:

Flavour_A  is part of Flavour_Sets 1, 2, 3
Flavour_B is part of Flavour_Sets 2, 3
Flavour_C is part of Flavour_Sets 1, 3, 4

Host_1 supports flavour Set 1
Host_2 supports flavour Set 2
Host_3 supports flavour Set 3
Host_4 supports flavour Set 4


>From the Essex design summit I thought that host aggregates was going to give 
>this sort of capability, but having looked through the code that seems to be 
>quite tightly coupled with specific hypervisor functionality, whereas this is 
>purely a scheduler feature.

I can see that I could define flavour group membership through the 
instanace_type_extra_specs, but not how to then associate these with specific 
hosts.

I know I’m a tad behind some of the recent changes – so before suggesting a 
design summit session on this I thought I’d ask - is there something that 
already does this type of mapping ?

Cheers,
Phil



___
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

[Openstack] Limit flavors to specific hosts

[Day, Phil]

Hi Folks,

I'm looking for a capability to limit some flavours to some hosts.  I want the 
mapping to be as flexible as possible, and work within a zone/cell  (I don't 
want to add zones just to get this mapping).For example I want to express 
something like:

Host_1 supports flavours A, C
Host_2 supports flavours A, B
Host_3 supports flavours A, B, C
Host_4 supports flavours D

Ideally there would be some form of grouping to sets of flavours:

Flavour_A  is part of Flavour_Sets 1, 2, 3
Flavour_B is part of Flavour_Sets 2, 3
Flavour_C is part of Flavour_Sets 1, 3, 4

Host_1 supports flavour Set 1
Host_2 supports flavour Set 2
Host_3 supports flavour Set 3
Host_4 supports flavour Set 4


>From the Essex design summit I thought that host aggregates was going to give 
>this sort of capability, but having looked through the code that seems to be 
>quite tightly coupled with specific hypervisor functionality, whereas this is 
>purely a scheduler feature.

I can see that I could define flavour group membership through the 
instanace_type_extra_specs, but not how to then associate these with specific 
hosts.

I know I'm a tad behind some of the recent changes - so before suggesting a 
design summit session on this I thought I'd ask - is there something that 
already does this type of mapping ?

Cheers,
Phil



___
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] Documenting public sites with VM images

[Christian Berendt]

Hi Lorin.

On 04/02/2012 05:11 PM, Lorin Hochstein wrote:
> I'm working on a doc update on where to download VM images that work
> with OpenStack . So far, I've got
> sections on CirrOS (Scott Moser's test image), Ubuntu and Fedora. Are
> there any other projects out there that have downloadable images that we
> can point users to?

Images build with http://susestudio.com/ are usable with OpenStack, too.

It's an easy way to build appliances for OpenSUSE and SLES 11 (SUSE
Linux Enterprise Server). You've to register there (for free) using an
OpenID to download or build images, but I think that's not that bad and
that it's still a public site.

As an example I built an OpenSUSE 12.1 (JeOS) image in appr. 2 minutes.

http://susestudio.com/a/YRUrwO/testing-instance-for-openstack-opensuse-121

HTH, Christian.

-- 
Christian Berendt
Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

___
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] multiple floating ip pools

[Vishvananda Ishaya]

Not yet. The extensions aren't in the api docs yet. Trying to address that
this week.
On Apr 2, 2012 8:40 AM, "Lorin Hochstein"  wrote:

> Vish:
>
> Are floating IP pools (--pool) documented anywhere? I did a quick look but
> couldn't find it in the main docs.
>
> Take care,
>
> Lorin
>
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
>
>
>
> On Mar 30, 2012, at 2:18 PM, Vishvananda Ishaya wrote:
>
> Floating ip pools allow you to specify a different ip range and bind
> interface for sets of ips, so it will work for segregation purposes.
>
> There isn't policy acl on which pool the ip comes from but it could be
> added. The policy wrapping in the network layer is very basic right now.
>  The underlying objects aren't passed in so we can't set policies based on
> (for example) pool name.  If/when the policy wrapping is improved to
> include more information that is a possibility.
>
> Vish
>
> On Mar 30, 2012, at 6:23 AM, Kevin Jackson wrote:
>
> I'm also interested in providing multiple floating IP pools.  Is this
> something that is achievable or conceived?
>
> My use case is as follows:
>
> Each tenant gets its own private VLAN and address space, so
> intercommunication between each tenant is able to be segregated.
> On assignment of public floating IPs though this segregation breaks down.
>
> To put this into context, I'd like to be able to have, say, a "Production"
> tenant and a "Development" tenant.  Inter-communication between the two
> should be prohibited.
> As soon as I assign a floating IP address, this model breaks down.
>
> I noticed that nova-manage floating create has a  ' --pool=
> Optional pool ' option.  How is this used?  Does this help solve my problem?
>
> Cheers,
>
> Kev
>
>
> On 6 February 2012 18:46, Xu (Simon) Chen  wrote:
>
>> Hi all,
>>
>> I am running devstack and got a dev instance of OpenStack running.
>>
>> I am happy to see the concept of multiple floating IP pools, and the
>> per-floating-ip interface in the trunk, which I consider a very good basis
>> for my blueprint proposal here:
>>
>> https://blueprints.launchpad.net/nova/+spec/multi-network-without-multi-nic
>>
>> I have a quick question. Is there a plan (or maybe it's already there)
>> for access control whether a project is allowed to take floating IPs from a
>> pool?
>>
>> Thanks!
>> -Simon
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Kevin Jackson
> @itarchitectkev
>  ___
> 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] OpenStack Community Newsletter –March 30, 2012

[Stefano Maffulli]

On Mon, 2012-04-02 at 10:53 -0400, Eoghan Glynn wrote:
> Assuming you're using git-log to generate these stats, you might
> want to throw the --find-copies-harder option into the mix, to
> avoid skewing the stats on minor re-orgs of the codebase directory
> structure.

I'll look into this with the folks that developed the tool I'm using
(cvsanaly, FYI). Thank you,
stef


___
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] Documenting public sites with VM images

[Anne Gentle]

Rackspace Cloud Builders has a nice list at
https://github.com/rackerjoe/oz-image-build of pre-built images.

It would be nice to update the docs with info about that oz-image-build
tool also.

Anne

On Mon, Apr 2, 2012 at 10:11 AM, Lorin Hochstein
wrote:

> All:
>
> I'm working on a doc update on where to download VM images that work with
> OpenStack . So far, I've got sections
> on CirrOS (Scott Moser's test image), Ubuntu and Fedora. Are there any
> other projects out there that have downloadable images that we can point
> users to?
>
>  Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
>
>
>
>
>
> ___
> 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

[Openstack] (Chef) "knife openstack" with Essex RC1?

[Brian Parker]

Hi!

Has anyone tried following the instructions for "knife openstack" with
Essex?  We are trying these steps:

http://wiki.opscode.com/display/chef/OpenStack+Bootstrap+Fast+Start+Guide

When attempting "knife openstack flavor list", we are getting a "ERROR:
RuntimeError: Unable to parse service catalog." error because the service
catalog is empty in the response.

Thanks!

Brian
___
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] multiple floating ip pools

[Jay Pipes]

On 04/02/2012 11:40 AM, Lorin Hochstein wrote:

Vish:

Are floating IP pools (--pool) documented anywhere? I did a quick look
but couldn't find it in the main docs.


Unfortunately, they are tucked away in the developer reference guide 
right now:


http://nova.openstack.org/api_ext/ext_floating_ips.html
http://nova.openstack.org/api_ext/ext_floating_ip_dns.html

best,
-jay

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

[Openstack] [Openstac RC1] Error with nova-list

[Leander Bessa]

Hello,

I'm trying to setup openstack rc1 with the packages supplied by ubuntu
12.04.
When i execute "nova list" i get the following traceback:

(nova): TRACE: Traceback (most recent call last):
>
> (nova): TRACE:   File "/usr/bin/nova-api", line 51, in 
>
> (nova): TRACE: servers.append(service.WSGIService(api))
>
> (nova): TRACE:   File "/usr/lib/python2.7/dist-packages/nova/service.py",
>> line 326, in __init__
>
> (nova): TRACE: self.app = self.loader.load_app(name)
>
> (nova): TRACE:   File "/usr/lib/python2.7/dist-packages/nova/wsgi.py",
>> line 388, in load_app
>
> (nova): TRACE: return deploy.loadapp("config:%s" % self.config_path,
>> name=name)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 247, in
>> loadapp
>
> (nova): TRACE: return loadobj(APP, uri, name=name, **kw)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 272, in
>> loadobj
>
> (nova): TRACE: return context.create()
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 710, in
>> create
>
> (nova): TRACE: return self.object_type.invoke(self)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 144, in
>> invoke
>
> (nova): TRACE: **context.local_conf)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/util.py", line 56, in
>> fix_call
>
> (nova): TRACE: val = callable(*args, **kw)
>
> (nova): TRACE:   File "/usr/lib/python2.7/dist-packages/paste/urlmap.py",
>> line 25, in urlmap_factory
>
> (nova): TRACE: app = loader.get_app(app_name, global_conf=global_conf)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 350, in
>> get_app
>
> (nova): TRACE: name=name, global_conf=global_conf).create()
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 362, in
>> app_context
>
> (nova): TRACE: APP, name=name, global_conf=global_conf)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 450, in
>> get_context
>
> (nova): TRACE: global_additions=global_additions)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 559, in
>> _pipeline_app_context
>
> (nova): TRACE: APP, pipeline[-1], global_conf)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 458, in
>> get_context
>
> (nova): TRACE: section)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 517, in
>> _context_from_explicit
>
> (nova): TRACE: value = import_string(found_expr)
>
> (nova): TRACE:   File
>> "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 22, in
>> import_string
>
> (nova): TRACE: return pkg_resources.EntryPoint.parse("x=" +
>> s).load(False)
>
> (nova): TRACE:   File "/usr/lib/python2.7/dist-packages/pkg_resources.py",
>> line 1989, in load
>
> (nova): TRACE: entry = __import__(self.module_name,
>> globals(),globals(), ['__name__'])
>
> (nova): TRACE: ImportError: No module named metadatarequesthandler
>
> (nova): TRACE:
>
>
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

Re: [Openstack] multiple floating ip pools

[Lorin Hochstein]

Vish:

Are floating IP pools (--pool) documented anywhere? I did a quick look but 
couldn't find it in the main docs. 

Take care,

Lorin


Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com




On Mar 30, 2012, at 2:18 PM, Vishvananda Ishaya wrote:

> Floating ip pools allow you to specify a different ip range and bind 
> interface for sets of ips, so it will work for segregation purposes.
> 
> There isn't policy acl on which pool the ip comes from but it could be added. 
> The policy wrapping in the network layer is very basic right now.  The 
> underlying objects aren't passed in so we can't set policies based on (for 
> example) pool name.  If/when the policy wrapping is improved to include more 
> information that is a possibility.
> 
> Vish
> 
> On Mar 30, 2012, at 6:23 AM, Kevin Jackson wrote:
> 
>> I'm also interested in providing multiple floating IP pools.  Is this 
>> something that is achievable or conceived?
>> 
>> My use case is as follows:
>> 
>> Each tenant gets its own private VLAN and address space, so 
>> intercommunication between each tenant is able to be segregated.
>> On assignment of public floating IPs though this segregation breaks down.
>> 
>> To put this into context, I'd like to be able to have, say, a "Production" 
>> tenant and a "Development" tenant.  Inter-communication between the two 
>> should be prohibited.
>> As soon as I assign a floating IP address, this model breaks down.
>> 
>> I noticed that nova-manage floating create has a  ' --pool= 
>> Optional pool ' option.  How is this used?  Does this help solve my problem?
>> 
>> Cheers,
>> 
>> Kev
>> 
>> 
>> On 6 February 2012 18:46, Xu (Simon) Chen  wrote:
>> Hi all,
>> 
>> I am running devstack and got a dev instance of OpenStack running. 
>> 
>> I am happy to see the concept of multiple floating IP pools, and the 
>> per-floating-ip interface in the trunk, which I consider a very good basis 
>> for my blueprint proposal here:
>> https://blueprints.launchpad.net/nova/+spec/multi-network-without-multi-nic
>> 
>> I have a quick question. Is there a plan (or maybe it's already there) for 
>> access control whether a project is allowed to take floating IPs from a pool?
>> 
>> Thanks!
>> -Simon
>> 
>> 
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
>> 
>> 
>> 
>> -- 
>> Kevin Jackson
>> @itarchitectkev
>> ___
>> 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

[Openstack] Melange RC2 now available

[Troy Toman]

The RC2 release for Melange is now available. You can find it at:

https://launchpad.net/melange/essex/essex-rc2

We fixed two issues between RC1 and RC2 that prevented IP blocks from being 
deleted properly and eased the transition for existing Melange DBs that were 
using Nova ID instead of UUID.

Troy

___
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] Dashboard VNC Console failed to connect to server

[Anthony Young]

>
>
> I have just a question, the novnc works on wich browsers? I've tried on
> firefox 10.0.2 and didn't worked.
>


Here is an approximate supported version list:
https://github.com/kanaka/noVNC/wiki/Browser-support.  I'm not sure about
that exact version of FF, though I know that certain versions use websocket
emulation and require Adobe Flash to be installed.  I tried the most recent
version of FF on Windows and OSX and it seemed ok.  I also tried 3.6 and it
worked fine.



> With chrome and IE I can connect to my instances, but can't use the
> keyboard.
>
>
Can you send a screenshot and pastie the instance console log?  While it is
possible that there is still an issue with the vnc connection, it is also
possible that your instances did not boot far enough to reach an
interactive state.



> --
> Date: Fri, 30 Mar 2012 12:23:08 -0700
>
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: guib...@hotmail.com
> CC: openstack@lists.launchpad.net
>
>
> On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk 
>  wrote:
>
> I installed the nova-consoleauth service and that resolved the problem of
> 404 not found. Now I'm getting a cannot connect to the server
> 127.0.0.1:6080. The IP 127.0.0.1 is strange, because on my nova.conf file
> I have the following flags:
>
>
> The 127.0.0.1 means that your flag is not taking effect.
>
> If you are using essex you need:
>
> --novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
>
> In https://review.openstack.org/6002 I explain that there are
> configuration options that have changed for essex, this is one of them.
>  Let me know if there is any way I can improve that explanation.
>
> Is this a 1 machine deploy? Given that vncproxy_url (again that is an
> outdated flag) references the same ip as the compute host, your configs
> would only work for all-in-one.
>
> A
>
>
> --vncserver_listen=192.168.100.142
> --vncserver_proxyclient_address=192.168.100.142
> --vncproxy_url=http://192.168.100.142:6080
> --vnc_console_proxy_url=http://192.168.100.142:6080
>
> My problem could be because of the localhost IP? I've already tried the
> port 6081, but with no success.
>
> --
> From: luciantho...@hotmail.com
> To: sleepsonthefl...@gmail.com
> Date: Fri, 30 Mar 2012 16:30:05 +
> CC: openstack@lists.launchpad.net
>
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
>
>  Anthony, I tried to add this flags there and do some more things but I
> didn't have sucess yet.
>
> I made a question in launchpad with all my network configurations and my
> log. Can you see that please?
>
> Thank you.
>
> https://answers.launchpad.net/nova/+question/192153
>
>
> *Lucian Thomaz*
>
>
> --
> Date: Thu, 29 Mar 2012 12:28:24 -0700
> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
> From: sleepsonthefl...@gmail.com
> To: luciantho...@hotmail.com
> CC: openstack@lists.launchpad.net
>
> Here are several flags that you must set on your compute host for a multi
> host deploy:
>
>
>- :option:`--vncserver_listen`  -
>defaults to 127.0.0.1 This is the address that vncservers will bind, and
>should be overridden in production deployments as a private address.
>Applies to libvirt only. For multi-host libvirt deployments this should be
>set to a host management ip on the same network as the proxies.
>- 
> :option:`--vncserver_proxyclient_address`
>  -
>defaults to 127.0.0.1 This is the address of the compute host that nova
>will instruct proxies to use when connecting to instance vncservers. For
>all-in-one xen server domU deployments this can be set to 169.254.0.1. For
>multi-host xen server domU deployments this can be set to a dom0 management
>ip on the same network as the proxies. For multi-host libvirt deployments
>this can be set to a host management ip on the same network as the proxies.
>- :option:`--novncproxy_base_url=[base url for client 
> connections]` -
>this is the public base url to which clients will connect. "?token=abc"
>will be added to this url for the purposes of auth. When using the system
>as described in this document, an appropriate value is "
>http://$SERVICE_HOST:6080/vnc_auto.html"; where SERVICE_HOST is a
>public hostname.
>
> Suppose you have 2 servers, APISERVER and COMPUTESERVER:
>
> APISERVER:
> public hostname = my.server.com
> management ip = 192.168.1.1
> public ip = 172.24.4.1
>
> COMPUTESERVER:
> management ip = 192.168.1.2
>
> Your nova.conf con COMPUTESERVER would need the following flags:
>
> novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or
> novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html
> vncserver_proxyclient_address=192.168.1.2
> vncserver_listen=192

Re: [Openstack] nova-manage required or deprecated for essex?

[John Garbutt]

I thought live-migration can happen through the nova CLI now (that is quite new 
I think).

However, there are also some commands for the XenServer storage migration 
volume driver that can only be done using nova-manage. I assume the intention 
is to add nova api extensions at some point, so that could be considered 
deprecated (Renuka should be able to confirm)

Cheers,
John

From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
Behalf Of Anne Gentle
Sent: 02 April 2012 15:29
To: Lorin Hochstein
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Subject: Re: [Openstack] nova-manage required or deprecated for essex?

Woops, meant to paste in a reference to 
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-01-31.log

"team meeting on January 31"

derp. :)

Anne
On Mon, Apr 2, 2012 at 9:21 AM, Anne Gentle 
mailto:a...@openstack.org>> wrote:
Hi Lorin -
My understanding is nova-manage image is not available any longer, but based on 
the team meeting on , we are not planning to remove it from docs since it's 
just too much work in the timed release timeframe for Essex.

For certain nova-manage image is not available, that's the point behind doc bug 
https://bugs.launchpad.net/openstack-manuals/+bug/957618

For Essex, the docs (and admins) still need to use nova-manage commands for:
-network creation
-migrating from deprecated auth to Keystone
-quick status checks on running services (nova-manage service list)
-database sync (migration)
-live migration seems to be using it a bit

Most other admin tasks can be accomplished in other ways and aren't documented 
with nova-manage commands.

Let me know if this list of nova-manage commands sounds accurate - Vish, Joe 
Heck, Brian Waldon?
Thanks,
Anne
On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein 
mailto:lo...@nimbisservices.com>> wrote:
Is nova-manage deprecated in essex, or are there some commands that still 
require nova-manage? I'd like to update the docs accordingly.

Yaguang Tang in this bug 
 said "nova-manage 
will be deprecated". But I couldn't tell from the context if he was referring 
specifically to "nova-manage image", or to nova-manage in general.

Right now, the docs have about 100 mentions of nova-manage:

[(master) docbkx]$ find . -name '*.xml' | xargs grep "nova-manage"| wc -l
  98



Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





___
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] dev ref doc for filter_scheduler

[Jay Pipes]

On 04/02/2012 01:06 AM, 彭勇 wrote:

distributed_scheduler  is renamed to filter_scheduler. and doc is here:

doc/source/devref/filter_scheduler.rst

the developer guide is still point to distributed_scheduler:

http://nova.openstack.org/devref/index.html
http://nova.openstack.org/devref/distributed_scheduler.html

any one can update it?


Yep, as mentioned on IRC, just log a bug about this and you can edit the 
doc files above and submit to Gerrit for review.


Best,
-jay

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

[Openstack] Documenting public sites with VM images

[Lorin Hochstein]

All:

I'm working on a doc update on where to download VM images that work with 
OpenStack . So far, I've got sections on 
CirrOS (Scott Moser's test image), Ubuntu and Fedora. Are there any other 
projects out there that have downloadable images that we can point users to?

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





___
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] [OpenStack] Xen Hypervisor

[John Garbutt]

Just double checking, but about the other machine you have put on the same 
network as your VMs, is the interface configured in the same subnet as the VMs?

Also, Just to be clear, not sure anyone has ever tried the sort of setup you 
are wanting (Single interface, with no VLANs). I have seen many setups using a 
single interface and VLANs, and many setups using different physical 
interfaces, and some combinations of the two, but I haven't seen anyone try 
collapsing everything onto a single physical interface. It might not work due 
to the way nova network in flatDHCP works (i.e. adds a DHCP server onto your 
network).

Just checking, but you are using FlatDHCP networking, I presume?

If you haven't assigned a floating ip and you are using some kind of flat 
networking, the public network configuration should be largely unimportant.

I think you want these settings:
flat_networking_bridge=xenbr0
flat_interface=eth0

What is the state of your VM, does it seem to have the correct IP address from 
the nova network DHCP?

I think you are close with your flags now, but I can't be specific with the 
help without more information:

* a list of your flags in nova.conf

* networking info (ifconfig or otherwise) from both Dom0 and DomU (with 
compute running) and the VM

* networking config from XenServer (networks, DomU VIFs and VM VIFs)

* a copy (in text form) of the network related tables in your DB (or 
all the values from your "nova-manage network create" and related calls)

More general advice is:

To make sure all the new network settings get applied, I would recommend:

* stop all nova services

* reset your nova DB

o   delete the old DB

o   Create the DB, do DB migration again, etc.

o   Add in your network again, (please tell us what values you use for that)

* start all nova services

It might be worth adding a second VIF on the same network, calling that eth1 in 
the Nova domU and then using that as the flat_interface. Normally it is not 
recommended that you configure an IP address on the interface that nova-network 
uses for the guest networking. Not sure what you are trying will work.

Thanks,
John

From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net 
[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On 
Behalf Of Alexandre Leites
Sent: 02 April 2012 14:53
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [OpenStack] Xen Hypervisor

I tried the last thing about changing public interface to eth0... but it still 
doesn't work. I still with erro of can't ping anything outside of VM (created 
by nova on xen).
> From: todd.desh...@xen.org
> Date: Mon, 2 Apr 2012 09:15:52 -0400
> Subject: Re: [Openstack] [OpenStack] Xen Hypervisor
> To: alex_...@live.com
> CC: openstack@lists.launchpad.net
>
> On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites 
> mailto:alex_...@live.com>> wrote:
> > Ok, anyway i tested it and didn't worked. Any other solution?
> >
>
> You should be more specific.
>
> You should explain the specific flags you tried and then post the
> relevant logs files.
>
> Thanks,
> Todd
>
>
> --
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://blog.xen.org/
> http://wiki.xen.org/
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Doc review request for keystone install

[Lorin Hochstein]

All:

I proposed a change in the OpenStack Install and Deploy manual 
  to fix bug 
https://bugs.launchpad.net/openstack-manuals/+bug/968679.

However, I'm not a keystone expert, and would appreciate it if somebody 
familiar with installing keystone could take a look and do a sanity check. I 
based my changes on 
http://www.hastexo.com/resources/docs/installing-openstack-essex-4-ubuntu-1204-precise-pangolin/step-3-install-and-configur.

Also, it's unclear to me whether the official recommended practice is to 
manually create the service catalog entries so they are stored in the  database 
backend (as was originally documented and seems to be the default Ubuntu 
package setup) or to use the templated catalog file (as suggested by that blog 
entry and used by devstack).

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com





___
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] OpenStack Community Newsletter –March 30, 2012

[Eoghan Glynn]

> COMMUNITY STATISTICS
> 
> 
> 
> • Activity on the main branch of OpenStack repositories, lines of
> code added and removed per developer during week 7 of 2012 (from
> Mon Mar 19 00:00:00 UTC 2012 to Mon March 26 00:00:00 UTC 2012)


Hi Stefano,

Assuming you're using git-log to generate these stats, you might
want to throw the --find-copies-harder option into the mix, to
avoid skewing the stats on minor re-orgs of the codebase directory
structure.

Cheers,
Eoghan

___
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] [OpenStack] Xen Hypervisor

[Alexandre Leites]

Sorry, i mean i tried to change public interface to xenbr0... 

From: alex_...@live.com
To: openstack@lists.launchpad.net
Date: Mon, 2 Apr 2012 13:53:23 +
Subject: Re: [Openstack] [OpenStack] Xen Hypervisor





I tried the last thing about changing public interface to eth0... but it still 
doesn't work. I still with erro of can't ping anything outside of VM (created 
by nova on xen).

> From: todd.desh...@xen.org
> Date: Mon, 2 Apr 2012 09:15:52 -0400
> Subject: Re: [Openstack] [OpenStack] Xen Hypervisor
> To: alex_...@live.com
> CC: openstack@lists.launchpad.net
> 
> On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites  wrote:
> > Ok, anyway i tested it and didn't worked. Any other solution?
> >
> 
> You should be more specific.
> 
> You should explain the specific flags you tried and then post the
> relevant logs files.
> 
> Thanks,
> Todd
> 
> 
> -- 
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://blog.xen.org/
> http://wiki.xen.org/
  

___
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-manage required or deprecated for essex?

[Anne Gentle]

Woops, meant to paste in a reference to
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-01-31.log

"team meeting on January 31"

derp. :)

Anne

On Mon, Apr 2, 2012 at 9:21 AM, Anne Gentle  wrote:

> Hi Lorin -
> My understanding is nova-manage image is not available any longer, but
> based on the team meeting on , we are not planning to remove it from docs
> since it's just too much work in the timed release timeframe for Essex.
>
> For certain nova-manage image is not available, that's the point behind
> doc bug https://bugs.launchpad.net/openstack-manuals/+bug/957618
>
> For Essex, the docs (and admins) still need to use nova-manage commands
> for:
> -network creation
> -migrating from deprecated auth to Keystone
> -quick status checks on running services (nova-manage service list)
> -database sync (migration)
> -live migration seems to be using it a bit
>
> Most other admin tasks can be accomplished in other ways and aren't
> documented with nova-manage commands.
>
> Let me know if this list of nova-manage commands sounds accurate - Vish,
> Joe Heck, Brian Waldon?
> Thanks,
> Anne
>
> On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein 
> wrote:
>
>> Is nova-manage deprecated in essex, or are there some commands that still
>> require nova-manage? I'd like to update the docs accordingly.
>>
>> Yaguang Tang in this bug <
>> https://bugs.launchpad.net/openstack-manuals/+bug/957618> said "nova-manage
>> will be deprecated". But I couldn't tell from the context if he was
>> referring specifically to "nova-manage image", or to nova-manage in general.
>>
>> Right now, the docs have about 100 mentions of nova-manage:
>>
>> [(master) docbkx]$ find . -name '*.xml' | xargs grep "nova-manage"| wc -l
>>   98
>>
>>
>>
>> Take care,
>>
>> Lorin
>> --
>> Lorin Hochstein
>> Lead Architect - Cloud Services
>> Nimbis Services, Inc.
>> www.nimbisservices.com
>>
>>
>>
>>
>>
>>
>> ___
>> 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-manage required or deprecated for essex?

[Anne Gentle]

Hi Lorin -
My understanding is nova-manage image is not available any longer, but
based on the team meeting on , we are not planning to remove it from docs
since it's just too much work in the timed release timeframe for Essex.

For certain nova-manage image is not available, that's the point behind doc
bug https://bugs.launchpad.net/openstack-manuals/+bug/957618

For Essex, the docs (and admins) still need to use nova-manage commands for:
-network creation
-migrating from deprecated auth to Keystone
-quick status checks on running services (nova-manage service list)
-database sync (migration)
-live migration seems to be using it a bit

Most other admin tasks can be accomplished in other ways and aren't
documented with nova-manage commands.

Let me know if this list of nova-manage commands sounds accurate - Vish,
Joe Heck, Brian Waldon?
Thanks,
Anne

On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein wrote:

> Is nova-manage deprecated in essex, or are there some commands that still
> require nova-manage? I'd like to update the docs accordingly.
>
> Yaguang Tang in this bug <
> https://bugs.launchpad.net/openstack-manuals/+bug/957618> said "nova-manage
> will be deprecated". But I couldn't tell from the context if he was
> referring specifically to "nova-manage image", or to nova-manage in general.
>
> Right now, the docs have about 100 mentions of nova-manage:
>
> [(master) docbkx]$ find . -name '*.xml' | xargs grep "nova-manage"| wc -l
>   98
>
>
>
> Take care,
>
> Lorin
> --
> Lorin Hochstein
> Lead Architect - Cloud Services
> Nimbis Services, Inc.
> www.nimbisservices.com
>
>
>
>
>
>
> ___
> 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] Dashboard VNC Console failed to connect to server

[Guilherme Birk]

Anthony, It's working now. Thanks for your support. I'll take a look at the 
outdated flags at my config.
I have just a question, the novnc works on wich browsers? I've tried on firefox 
10.0.2 and didn't worked. With chrome and IE I can connect to my instances, but 
can't use the keyboard.

Date: Fri, 30 Mar 2012 12:23:08 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server
From: sleepsonthefl...@gmail.com
To: guib...@hotmail.com
CC: openstack@lists.launchpad.net

On Fri, Mar 30, 2012 at 11:29 AM, Guilherme Birk  wrote:


I installed the nova-consoleauth service and that resolved the problem of 404 
not found. Now I'm getting a cannot connect to the server127.0.0.1:6080. The IP 
127.0.0.1 is strange, because on my nova.conf file I have the following flags:

The 127.0.0.1 means that your flag is not taking effect.

If you are using essex you need:

--novncproxy_base_url=http://192.168.100.142:6080/vnc_auto.html
In https://review.openstack.org/6002 I explain that there are configuration 
options that have changed for essex, this is one of them.  Let me know if there 
is any way I can improve that explanation.

Is this a 1 machine deploy? Given that vncproxy_url (again that is an outdated 
flag) references the same ip as the compute host, your configs would only work 
for all-in-one.

A



--vncserver_listen=192.168.100.142
--vncserver_proxyclient_address=192.168.100.142
--vncproxy_url=http://192.168.100.142:6080

--vnc_console_proxy_url=http://192.168.100.142:6080

My problem could be because of the localhost IP? I've already tried the port 
6081, but with no success.


From: luciantho...@hotmail.com
To: sleepsonthefl...@gmail.com

Date: Fri, 30 Mar 2012 16:30:05 +
CC: openstack@lists.launchpad.net
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server








Anthony, I tried to add this flags there and do some more things but I didn't 
have sucess yet.


I made a question in launchpad with all my network configurations and my log. 
Can you see that please?

Thank you.

https://answers.launchpad.net/nova/+question/192153



Lucian Thomaz


Date: Thu, 29 Mar 2012 12:28:24 -0700
Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server

From: sleepsonthefl...@gmail.com
To: luciantho...@hotmail.com
CC: openstack@lists.launchpad.net


Here are several flags that you must set on your compute host for a multi host 
deploy:



:option:`--vncserver_listen` - defaults to 127.0.0.1 This is the address that 
vncservers will bind, and should be overridden in production deployments as a 
private address. Applies to libvirt only. For multi-host libvirt deployments 
this should be set to a host management ip on the same network as the proxies.


:option:`--vncserver_proxyclient_address` - defaults to 127.0.0.1 This is the 
address of the compute host that nova will instruct proxies to use when 
connecting to instance vncservers. For all-in-one xen server domU deployments 
this can be set to 169.254.0.1. For multi-host xen server domU deployments this 
can be set to a dom0 management ip on the same network as the proxies. For 
multi-host libvirt deployments this can be set to a host management ip on the 
same network as the proxies.


:option:`--novncproxy_base_url=[base url for client connections]` - this is the 
public base url to which clients will connect. "?token=abc" will be added to 
this url for the purposes of auth. When using the system as described in this 
document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html"; 
where SERVICE_HOST is a public hostname.

Suppose you have 2 servers, APISERVER and COMPUTESERVER:
APISERVER:public hostname = my.server.commanagement ip = 192.168.1.1

public ip = 172.24.4.1
COMPUTESERVER:management ip = 192.168.1.2
Your nova.conf con COMPUTESERVER would need the following flags:


novncproxy_base_url=http://my.server.com:6080/vnc_auto.html or 
novncproxy_base_url=http://172.24.4.1:6080/vnc_auto.html

vncserver_proxyclient_address=192.168.1.2vncserver_listen=192.168.1.2


Note that novncproxy_base_url references a public ip or hostname (so clients 
can connect), while the other flags use private ips.


For more 
info:https://github.com/openstack/nova/blob/master/doc/source/runnova/vncconsole.rst



On Thu, Mar 29, 2012 at 11:07 AM, Lucian Thomaz  
wrote:






Hey guys,
I'm using Dashboard with a nova-compute installed in another machine, but when 
I try access VNC Console I get the error "failed to connect to server".


Here is the log -> http://pastebin.com/5DZMfiNE


Anyone already saw this trouble?



Lucian Thomaz 
  

___

Mailing list: https://launchpad.net/~openstack

Post to : openstack@lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



  

___
Mai

Re: [Openstack] [OpenStack] Xen Hypervisor

[Alexandre Leites]

I tried the last thing about changing public interface to eth0... but it still 
doesn't work. I still with erro of can't ping anything outside of VM (created 
by nova on xen).

> From: todd.desh...@xen.org
> Date: Mon, 2 Apr 2012 09:15:52 -0400
> Subject: Re: [Openstack] [OpenStack] Xen Hypervisor
> To: alex_...@live.com
> CC: openstack@lists.launchpad.net
> 
> On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites  wrote:
> > Ok, anyway i tested it and didn't worked. Any other solution?
> >
> 
> You should be more specific.
> 
> You should explain the specific flags you tried and then post the
> relevant logs files.
> 
> Thanks,
> Todd
> 
> 
> -- 
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://blog.xen.org/
> http://wiki.xen.org/
  ___
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] [OpenStack] Xen Hypervisor

[Todd Deshane]

On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites  wrote:
> Ok, anyway i tested it and didn't worked. Any other solution?
>

You should be more specific.

You should explain the specific flags you tried and then post the
relevant logs files.

Thanks,
Todd


-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://blog.xen.org/
http://wiki.xen.org/

___
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] [OpenStack] Xen Hypervisor

[Alexandre Leites]

Ok, anyway i tested it and didn't worked. Any other solution?

Subject: Re: [Openstack] [OpenStack] Xen Hypervisor
From: vishvana...@gmail.com
Date: Thu, 29 Mar 2012 13:30:32 -0700
CC: salvatore.orla...@eu.citrix.com; alex_...@live.com; 
ewan.mel...@eu.citrix.com; openstack@lists.launchpad.net; todd.desh...@xen.org
To: john.garb...@citrix.com

Public interface is the interface used for adding floating (natted) ips.  If 
this is generally eth0 in the domU then ignore my previous message.
Vish
On Mar 29, 2012, at 11:20 AM, John Garbutt wrote:The public interface, I 
thought was the interface of the DomU running the service, and it attached its 
own bridges inside the DomU? I have tried to describe all this 
here:http://wiki.openstack.org/XenServer/NetworkingFlags Would be cool if 
people can check that for me, and I can push it into the manuals. Cheers,John 
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] 
Sent: 29 March 2012 19:15
To: John Garbutt
Cc: Salvatore Orlando; Alexandre Leites; Ewan Mellor; 
openstack@lists.launchpad.net; todd.desh...@xen.org
Subject: Re: [Openstack] [OpenStack] Xen Hypervisor  On Mar 29, 2012, at 7:40 
AM, John Garbutt wrote:

If you want all your traffic going through a single nic (Management, Instance, 
Public), it might be possible using these settings: public_interface=eth0 I 
don't think this will work unless the implementation is very different in xen.  
xenbr0 will be bridged into eth0, so you actually want to be adding ips to the 
bridge not the raw eth device.  I would suggest public_interface=xenbr0 Xen 
experts, please correct me if I'm wrong.

flat_interface=eth0flat_network_bridge=xenbr0
  ___
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] [Keystone] keystone filter and server

[Kiall Mac Innes]

Inline..

Thanks,
Kiall


On Mon, Apr 2, 2012 at 11:42 AM, Deepak Garg wrote:

> > The only disadvantage of having it in python-keystone over
> > a python-keystone-middleware package is a few extra .py files on disk..
> > Personally, I don't see that as an issue..
> [Deepak] A few extra files but you are installing keystone client
> unnecessarily


Humm - you're right about about. python-keystone depends on
python-keystoneclient for some reason.

I wonder if that is a packaging bug, or if there is a legitimate reason for
the depends.


>  >> It might be better to include it in a new python-keystone-middleware
> >> package, but not python-openstack-common..
> >> python-openstack-common is this
> >> code: https://github.com/openstack/openstack-common. These are
> libraries
> >> that are service independent, eg config libs,
> [Deepak] Isn't it service independent ? All the services are using it,
> so they might as well borrow it from openstack-common
>

It's optionally used by many services, but is a piece of the keystone
project.. It should IMO belong in a keystone named package.. But, you are
right, its could go in openstack-common from a install perspective, but
from a development+packaging perspective, allowing for this would be more
hassle that it's worth.


> The reason I have suggested to include it in openstack-common because
> I think it is installed in all the nodes as all the services are
> dependent on openstack-common. I am not sure if we will run into
> maintenance issues.


I'm not sure what extra maintenance issues there may be over the already
installed set of python-{nova,glance,swift} packages?

Being overly simplistic, `apt-get` should be all you need to maintain the
package. Additionally, Once keystone becomes the only auth system for
OpenStack, I would assume the packages will have the middleware listed as a
hard dependency to make even easier..

Thanks,
Kiall
___
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] [Keystone] keystone filter and server

[Deepak Garg]

Please find my answers in-line


>
> The only disadvantage of having it in python-keystone over
> a python-keystone-middleware package is a few extra .py files on disk..
> Personally, I don't see that as an issue..
[Deepak] A few extra files but you are installing keystone client unnecessarily


>> It might be better to include it in a new python-keystone-middleware
>> package, but not python-openstack-common..
>> python-openstack-common is this
>> code: https://github.com/openstack/openstack-common. These are libraries
>> that are service independent, eg config libs,
[Deepak] Isn't it service independent ? All the services are using it,
so they might as well borrow it from openstack-common

The reason I have suggested to include it in openstack-common because
I think it is installed in all the nodes as all the services are
dependent on openstack-common. I am not sure if we will run into
maintenance issues.


Deepak


>> Thanks,
>> Kiall
>>
>>
>>
>> On Mon, Apr 2, 2012 at 9:49 AM, Deepak Garg 
>> wrote:
>>>
>>> Thanks for the answers. It helps a lot.
>>> But wouldn't it be better to include it in openstack-common which I
>>> think is installed in all nodes.
>>>
>>>
>>> Thanks,
>>> Deepak
>>>
>>>
>>> On Mon, Apr 2, 2012 at 2:15 PM, Kiall Mac Innes 
>>> wrote:
>>> > Ubuntu includes this in python-keystone, so it can be installed without
>>> > having keystone actually running.
>>> >
>>> > Thanks,
>>> > Kiall
>>> >
>>> > Sent from my phone.
>>> >
>>> > On Apr 2, 2012 9:04 a.m., "Chmouel Boudjnah" 
>>> > wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> On Mon, Apr 2, 2012 at 4:17 AM, Deepak Garg
>>> >> 
>>> >> wrote:
>>> >> > a. All the projects are using  middleware.auth_token.py from the
>>> >> > keystone repo for basic token auth,  but if we now say that the
>>> >> > filter_factory needs to be set to "keystone.middleware.auth_token",
>>> >> > does that mean that keystone should to be installed on the same
>>> >> > machine as that service ?
>>> >> > b. If yes, does this also mean that keystone server should be
>>> >> > running
>>> >> > on all nodes ?
>>> >>
>>> >> It  needs only the file auth_token.py and nothing else from keystone.
>>> >> For dependencies on the server you'll need to have python-webob
>>> >> installed and python-memcache/python-iso8601 if you use memcache
>>> >> caching.
>>> >>
>>> >> Hopefully packagers would create a sub-package from keystone source
>>> >> with only auth_token in there easy to install on the hosts that need
>>> >> it.
>>> >>
>>> >> Chmouel.
>>> >>
>>> >> ___
>>> >> Mailing list: https://launchpad.net/~openstack
>>> >> Post to     : openstack@lists.launchpad.net
>>> >> Unsubscribe : https://launchpad.net/~openstack
>>> >> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>> --
>>>
>>> Deepak Garg,
>>> Data Center and Cloud Div.
>>> Citrix R&D, India
>>> Skype-id: deepakgarg.iit
>>
>>
>



-- 

Deepak Garg,
Data Center and Cloud Div.
Citrix R&D, India
Skype-id: deepakgarg.iit

___
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] [Keystone] keystone filter and server

[Kiall Mac Innes]

Heh - Hit send too early ;)

The only disadvantage of having it in python-keystone over
a python-keystone-middleware package is a few extra .py files on disk..

Personally, I don't see that as an issue..

Thanks,
Kiall


On Mon, Apr 2, 2012 at 10:00 AM, Kiall Mac Innes  wrote:

> IMHO, No.
>
> It might be better to include it in a new python-keystone-middleware
> package, but not python-openstack-common..
>
> python-openstack-common is this code:
> https://github.com/openstack/openstack-common. These are libraries that
> are service independent, eg config libs,
>
>
>
> Thanks,
> Kiall
>
>
>
> On Mon, Apr 2, 2012 at 9:49 AM, Deepak Garg wrote:
>
>> Thanks for the answers. It helps a lot.
>> But wouldn't it be better to include it in openstack-common which I
>> think is installed in all nodes.
>>
>>
>> Thanks,
>> Deepak
>>
>>
>> On Mon, Apr 2, 2012 at 2:15 PM, Kiall Mac Innes 
>> wrote:
>> > Ubuntu includes this in python-keystone, so it can be installed without
>> > having keystone actually running.
>> >
>> > Thanks,
>> > Kiall
>> >
>> > Sent from my phone.
>> >
>> > On Apr 2, 2012 9:04 a.m., "Chmouel Boudjnah" 
>> wrote:
>> >>
>> >> Hi,
>> >>
>> >> On Mon, Apr 2, 2012 at 4:17 AM, Deepak Garg > >
>> >> wrote:
>> >> > a. All the projects are using  middleware.auth_token.py from the
>> >> > keystone repo for basic token auth,  but if we now say that the
>> >> > filter_factory needs to be set to "keystone.middleware.auth_token",
>> >> > does that mean that keystone should to be installed on the same
>> >> > machine as that service ?
>> >> > b. If yes, does this also mean that keystone server should be running
>> >> > on all nodes ?
>> >>
>> >> It  needs only the file auth_token.py and nothing else from keystone.
>> >> For dependencies on the server you'll need to have python-webob
>> >> installed and python-memcache/python-iso8601 if you use memcache
>> >> caching.
>> >>
>> >> Hopefully packagers would create a sub-package from keystone source
>> >> with only auth_token in there easy to install on the hosts that need
>> >> it.
>> >>
>> >> Chmouel.
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~openstack
>> >> Post to : openstack@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~openstack
>> >> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>>
>> Deepak Garg,
>> Data Center and Cloud Div.
>> Citrix R&D, India
>> Skype-id: deepakgarg.iit
>>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Swift] Is there any limitation for arranging Rings. Failed to do operation in this case

[Kuo Hugo]

Hi folks  ,

I'm facing an issue . Before fill in a bug ,  I have to clarify something
about arrange rings

:My Case:

There're three zones in this test , The replica as below
Objects  2 replicas
Account 3 replicas
Container 3 replicas

With this setup , I can check the status of an Account . Also Account's DB
has three replicas in each Zone properly.
Once I try to upload an object , it hangs. Even using curl to put the
object , the result is same.

After monitor the storage disks , I saw three empty temp files were created
. And no more actions . All logs without any error.

Does any one try to setup rings like this ?  Is this make sense .

Should it be filled into a bug?


Cheers
-- 
+Hugo Kuo+
tonyt...@gmail.com
+ 886 935004793
___
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] [Keystone] keystone filter and server

[Deepak Garg]

Thanks for the answers. It helps a lot.
But wouldn't it be better to include it in openstack-common which I
think is installed in all nodes.


Thanks,
Deepak


On Mon, Apr 2, 2012 at 2:15 PM, Kiall Mac Innes  wrote:
> Ubuntu includes this in python-keystone, so it can be installed without
> having keystone actually running.
>
> Thanks,
> Kiall
>
> Sent from my phone.
>
> On Apr 2, 2012 9:04 a.m., "Chmouel Boudjnah"  wrote:
>>
>> Hi,
>>
>> On Mon, Apr 2, 2012 at 4:17 AM, Deepak Garg 
>> wrote:
>> > a. All the projects are using  middleware.auth_token.py from the
>> > keystone repo for basic token auth,  but if we now say that the
>> > filter_factory needs to be set to "keystone.middleware.auth_token",
>> > does that mean that keystone should to be installed on the same
>> > machine as that service ?
>> > b. If yes, does this also mean that keystone server should be running
>> > on all nodes ?
>>
>> It  needs only the file auth_token.py and nothing else from keystone.
>> For dependencies on the server you'll need to have python-webob
>> installed and python-memcache/python-iso8601 if you use memcache
>> caching.
>>
>> Hopefully packagers would create a sub-package from keystone source
>> with only auth_token in there easy to install on the hosts that need
>> it.
>>
>> Chmouel.
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp



-- 

Deepak Garg,
Data Center and Cloud Div.
Citrix R&D, India
Skype-id: deepakgarg.iit

___
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] [Keystone] keystone filter and server

[Kiall Mac Innes]

Ubuntu includes this in python-keystone, so it can be installed without
having keystone actually running.

Thanks,
Kiall

Sent from my phone.
On Apr 2, 2012 9:04 a.m., "Chmouel Boudjnah"  wrote:

> Hi,
>
> On Mon, Apr 2, 2012 at 4:17 AM, Deepak Garg 
> wrote:
> > a. All the projects are using  middleware.auth_token.py from the
> > keystone repo for basic token auth,  but if we now say that the
> > filter_factory needs to be set to "keystone.middleware.auth_token",
> > does that mean that keystone should to be installed on the same
> > machine as that service ?
> > b. If yes, does this also mean that keystone server should be running
> > on all nodes ?
>
> It  needs only the file auth_token.py and nothing else from keystone.
> For dependencies on the server you'll need to have python-webob
> installed and python-memcache/python-iso8601 if you use memcache
> caching.
>
> Hopefully packagers would create a sub-package from keystone source
> with only auth_token in there easy to install on the hosts that need
> it.
>
> Chmouel.
>
> ___
> 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] [Keystone] keystone filter and server

[Chmouel Boudjnah]

Hi,

On Mon, Apr 2, 2012 at 4:17 AM, Deepak Garg  wrote:
> a. All the projects are using  middleware.auth_token.py from the
> keystone repo for basic token auth,  but if we now say that the
> filter_factory needs to be set to "keystone.middleware.auth_token",
> does that mean that keystone should to be installed on the same
> machine as that service ?
> b. If yes, does this also mean that keystone server should be running
> on all nodes ?

It  needs only the file auth_token.py and nothing else from keystone.
For dependencies on the server you'll need to have python-webob
installed and python-memcache/python-iso8601 if you use memcache
caching.

Hopefully packagers would create a sub-package from keystone source
with only auth_token in there easy to install on the hosts that need
it.

Chmouel.

___
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] HELP: create VM failure

[Razique Mahroua]

Hello,looks like you are trying to run an image with an architecture the hypervisors doesn't support.What kind of cpu is on the hv ?
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com

Le 2 avr. 2012 à 00:04, Leander Bessa a écrit :Maybe you specified --libvirt_type=hvm instead of --libvirt_type=kvm in your nova.conf file.On Sun, Apr 1, 2012 at 8:44 PM, Sam Su  wrote:
Hi, I am trying to deploy Openstack all-in-one environment (Nova, Glance, Keystone, Dashboard ) from scratch in an Ubuntu 12.04 server, After installed Nova,  I tried to create a VM with nova command but failed:

root@ubuntu:/etc/nova#  nova boot --flavor 1 --image 8e7f9978-86b2-4c75-a0a8-44b0bb2a46e2 --key_name key1 VM2+-+--+

|               Property              |                Value                 |+-+--+| OS-DCF:diskConfig                   | MANUAL                               |

| OS-EXT-SRV-ATTR:host                | ubuntu                               || OS-EXT-SRV-ATTR:hypervisor_hostname | None                                 || OS-EXT-SRV-ATTR:instance_name       | instance-0002                    |

| OS-EXT-STS:power_state              | 0                                    || OS-EXT-STS:task_state               | scheduling                           || OS-EXT-STS:vm_state                 | building                             |

| accessIPv4                          |                                      || accessIPv6                          |                                      || adminPass                           | Yj6mVrxaEiX6                         |

| config_drive                        |                                      || created                             | 2012-04-01T19:25:54Z                 || flavor                              | m1.tiny                              |

| hostId                              |                                      || id                                  | c15be925-c4d8-4b76-b7c3-e94ebe513cf1 || image                               | Ubuntu 11.10 cloudimg amd64          |

| key_name                            | key1                                 || metadata                            | {}                                   || name                                | VM2                                  |

| progress                            | 0                                    || status                              | BUILD                                || tenant_id                           | 2660dedf826c4510aff873c05d9d506b     |

| updated                             | 2012-04-01T19:25:54Z                 || user_id                             | b42c715d94384aa6a66c56df44ac69b2     |+-+--+

root@ubuntu:/etc/nova# nova show VM2+-+--+|               Property              |                                      Value                                       |

+-+--+| OS-DCF:diskConfig                   | MANUAL                                                                           |

| OS-EXT-SRV-ATTR:host                | ubuntu                                                                           || OS-EXT-SRV-ATTR:hypervisor_hostname | None                                                                             |

| OS-EXT-SRV-ATTR:instance_name       | instance-0002                                                                || OS-EXT-STS:power_state              | 0                                                                                |

| OS-EXT-STS:task_state               | spawning                                                                         || OS-EXT-STS:vm_state                 | error                                                                            |

| accessIPv4                          |                                                                                  || accessIPv6                          |                                                                                  |

| config_drive                        |                                                                                  || created                             | 2012-04-01T19:25:54Z                                                             |

| fault                               | {u'message': u'libvirtError', u'code': 500, u'created': u'2012-04-01T19:25:57Z'} || flavor                              | m1.tiny                                                                          |

| hostId                              | 05c193a7baf099665d8bd6cb4964e738b