date:20121030

to run quantum-server, dhcp agent, ovs and linuxbridge agent, we need to 
specify the quantum.conf as one of the configure files.

Besides the RPC sections, some of other parts are useful too.
RPC parts are used for communication between quantum-server and dhcp 
agent, ovs agent or linux bridge agent.

On 10/30/2012 03:37 PM, Trinath Somanchi wrote:

Hi Stackers-

With respect to the Folsom Quantum Admin Manual 
(http://docs.openstack.org/trunk/openstack-network/admin/content/rpc_setup.html) 
, the RPC setup section.


The lines ,

[Important] Important

This /etc/quantum/quantum.conf file should be copied to and used on 
all hosts running quantum-server, quantum-dhcp-agent, 
quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below).




Specify that the quantum.conf should be copied to all Network Nodes if 
the Agents doesn't run in the Controller node.


Also in the same way, IF we have the DHCP/OVS agents running in the 
HOST nodes itself the same scenario works for it.



I'm thinking that, this configuration copy to  the HOST/NETWORK nodes 
is to support the RABBITMQ linking between the Controller and the 
NETWORK/HOST


nodes, in order to enable RPC based communication between the 
Controller and the Agents running in the Network/Host nodes.



Please correct my understanding briefed above.


Thanking you-




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



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


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

Re: [Openstack] new mailing list for bare-metal provisioning

2012-10-30 Thread Thierry Carrez

Mark T. Voelker wrote:
 Thus, I'd have missed those messages if I were only subscribed to
 the Quantum topic.

It was my understanding that messages that don't include a proper
topic end up being sent to everyone. So you can use topics to
actively ignore stuff that has been marked [Nova], rather than only
receive [baremetal] stuff.

 Personally I like to see everything so it doesn't much matter to
 me other than in how I set up my email filters, but I think perhaps
 this is one reason why we've had the discussion about more vs fewer
 mailing lists more than once.

I personally prefer to receive everything and do filtering client-side
too. Topics are just an additional option, I guess.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
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] RPC setup for Quantum

2012-10-30 Thread Trinath Somanchi

True said. I'm clear with this point.

But My doubt is that, for every HOST node, we need to have quantum.conf if
the HOST node has the DHCP-Agent and the OVS-Agent running in them.

Please help me in this regard.

-
Trinath

On Tue, Oct 30, 2012 at 1:58 PM, gong yong sheng gong...@linux.vnet.ibm.com
 wrote:

  to run quantum-server, dhcp agent, ovs and linuxbridge agent, we need to
 specify the quantum.conf as one of the configure files.
 Besides the RPC sections, some of other parts are useful too.
 RPC parts are used for communication between quantum-server and dhcp
 agent, ovs agent or linux bridge agent.

 On 10/30/2012 03:37 PM, Trinath Somanchi wrote:

 Hi Stackers-

  With respect to the Folsom Quantum Admin Manual (
 http://docs.openstack.org/trunk/openstack-network/admin/content/rpc_setup.html)
 , the RPC setup section.

  The lines ,

[image: [Important]] Important

 This /etc/quantum/quantum.conf file should be copied to and used on all
 hosts running quantum-server, quantum-dhcp-agent,
 quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below).



  Specify that the quantum.conf should be copied to all Network Nodes if
 the Agents doesn't run in the Controller node.

 Also in the same way, IF we have the DHCP/OVS agents running in the HOST
 nodes itself the same scenario works for it.


  I'm thinking that, this configuration copy to  the HOST/NETWORK nodes is
 to support the RABBITMQ linking between the Controller and the NETWORK/HOST

 nodes, in order to enable RPC based communication between the Controller
 and the Agents running in the Network/Host nodes.


  Please correct my understanding briefed above.


  Thanking you-



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



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





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

Re: [Openstack] [Openstack :: Folsom] Quantum DHCP Agent in Compute HOST


Hi,
In fact, we can split Quantum network Node into two categories:
one is for dhcp, which install ovs agent and dhcp agent. We can have one 
such kind of node
one is for l3 agent, we can deal with one external network on one l3 
agent. We can have many nodes of this kind.


Regards,

Yong Sheng Gong
On 10/30/2012 02:27 PM, balaji patnala wrote:

Hi Salvatore,
Just want to understand more on Network Node in the below given 
app_demo page.
As i see in the setup, it looks like there will be one Quantum Network 
Node for one Data centre setup. Please correct me if my assumptions 
are wrong.
This Quantum Network Node will have all the virtual routers, gateway 
which can be created with quantum-l3-agent plugin.
Also my assumption is that this quantum Network Node will serve all 
the Tenant virtual gateways and routers created using quantum.

Please give us some more information on this to understand the setup.
Also do we have any specific reason for having quantum Network Node 
instead of keeping these plugin on the Controller Node similar to 
earlier release like Essex.

Thanks in advance.
Regards,
Balaji

On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando 
sorla...@nicira.com mailto:sorla...@nicira.com wrote:


Hi Trinath,

Even if is perfectly reasonable to run the DHCP/L3 agents in the
controller node, the advice we give in the administration guide is
slightly different.
As suggested in [1], the only Quantum component running on the
controller node should be the API server.
The DHCP and L3 agents might run in a dedicated network node.
Please note you will need also the L2 agent running on that node.

Regards,
Salvatore

[1]

http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html

On 26 October 2012 10:50, Trinath Somanchi
trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com
wrote:

Hi Stackers-

I have found many installation and configuration manuals for
Openstack Folsom which state the installation and
configuration of Quantum-DHCP-Agent in the Controller machine.

But I have doubt here,

Can't we have the Quantum-DHCP/L3-Agent to be running in the
Compute NODE rather than in the controller.

How does the Installation and configuration change with this
type of Installation?

Please guide me on How to achieve the same.

Thanking you

-- 
Regards,

--
Trinath Somanchi,
+91 9866 235 130 tel:%2B91%209866%20235%20130


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



___
Mailing list: https://launchpad.net/~openstack
https://launchpad.net/%7Eopenstack
Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
https://launchpad.net/%7Eopenstack
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] RPC setup for Quantum



On 10/30/2012 04:53 PM, Trinath Somanchi wrote:

True said. I'm clear with this point.

But My doubt is that, for every HOST node, we need to have 
quantum.conf if the HOST node has the DHCP-Agent and the OVS-Agent 
running in them.


dhcp-agent and ovs-agent will need the quantum.conf as one of their 
configure files.

for example dhcp-agent --config-file quantum.conf --config-file dhcp.ini
So if the Host node has these agents running on them, we need to have 
quantum.conf on host node.
these agents will use the configuration in quantum.conf, such as logging 
settings, RPC settings.

Hope this explanation helps.



Please help me in this regard.

-
Trinath

On Tue, Oct 30, 2012 at 1:58 PM, gong yong sheng 
gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote:


to run quantum-server, dhcp agent, ovs and linuxbridge agent, we
need to specify the quantum.conf as one of the configure files.
Besides the RPC sections, some of other parts are useful too.
RPC parts are used for communication between quantum-server and
dhcp agent, ovs agent or linux bridge agent.

On 10/30/2012 03:37 PM, Trinath Somanchi wrote:

Hi Stackers-

With respect to the Folsom Quantum Admin Manual

(http://docs.openstack.org/trunk/openstack-network/admin/content/rpc_setup.html)
, the RPC setup section.

The lines ,

[Important] Important

This /etc/quantum/quantum.conf file should be copied to and used
on all hosts running quantum-server, quantum-dhcp-agent,
quantum-openvswitch-agent, or quantum-linuxbridge-agent (see below).



Specify that the quantum.conf should be copied to all Network
Nodes if the Agents doesn't run in the Controller node.

Also in the same way, IF we have the DHCP/OVS agents running in
the HOST nodes itself the same scenario works for it.


I'm thinking that, this configuration copy to  the HOST/NETWORK
nodes is to support the RABBITMQ linking between the Controller
and the NETWORK/HOST

nodes, in order to enable RPC based communication between the
Controller and the Agents running in the Network/Host nodes.


Please correct my understanding briefed above.


Thanking you-




-- 
Regards,

--
Trinath Somanchi,
+91 9866 235 130 tel:%2B91%209866%20235%20130



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





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



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

Re: [Openstack] Allocate specific floating IP to an instance

2012-10-30 Thread Emilien Macchi

Hello Sebastien,


What you can do today is to choose manually which floating IP you need to 
associate with a specific instance.
You need to run OpenStack Folsom + Quantum.

First, you need to create Floating IP pool(s) from Quantum CLI, and after that, 
the tenant is able to associate this IP to a private instance :
quantum floatingip-create ext_net
quantum floatingip-associate $FLOATING_ID $PORT_ID
More informations about Networking configuration with Quantum CLI here :
http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html


Cheers ;-)



Emilien Macchi

// eNovance Inc. http://enovance.com
// ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
// 10 rue de la Victoire 75009 Paris

- Mail original -

De: Sébastien Han han.sebast...@gmail.com
À: Openstack openstack@lists.launchpad.net
Envoyé: Lundi 29 Octobre 2012 17:25:47
Objet: [Openstack] Allocate specific floating IP to an instance

Hi Stacker,

I know OpenStack is not designed that way and I don't think it's
possible (or maybe I misses something :)) but I was wondering if there
is any simple workaround to choose a specific floating IP to allocate.
In other words, don't give me a random or N+1 next floating IP
available but let me decide which floating IP I want to assign to my
instance. It doesn't make sense in a public cloud but it does for a
corporate/private cloud. It would be nice to have :)

Thanks in advance.

Cheers!

___
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] Allocate specific floating IP to an instance

I'm fairly confident that quantum is not a requirement for this.

Nova's in-built networking supports exactly this since as long ago as I can
remember.

Thanks,
Kiall
On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com wrote:

 Hello Sebastien,


 What you can do today is to choose manually which floating IP you need to
 associate with a specific instance.
 You need to run OpenStack Folsom + Quantum.

 First, you need to create Floating IP pool(s) from Quantum CLI, and after
 that, the tenant is able to associate this IP to a private instance :

 quantum floatingip-create ext_net
 quantum floatingip-associate $FLOATING_ID $PORT_ID

 More informations about Networking configuration with Quantum CLI here :

 http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html


 Cheers ;-)


 Emilien Macchi
 
 // eNovance Inc.  http://enovance.com
 // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
 // 10 rue de la Victoire 75009 Paris

 --
 *De: *Sébastien Han han.sebast...@gmail.com
 *À: *Openstack openstack@lists.launchpad.net
 *Envoyé: *Lundi 29 Octobre 2012 17:25:47
 *Objet: *[Openstack] Allocate specific floating IP to an instance

 Hi Stacker,

 I know OpenStack is not designed that way and I don't think it's
 possible (or maybe I misses something :)) but I was wondering if there
 is any simple workaround to choose a specific floating IP to allocate.
 In other words, don't give me a random or N+1 next floating IP
 available but let me decide which floating IP I want to assign to my
 instance. It doesn't make sense in a public cloud but it does for a
 corporate/private cloud. It would be nice to have :)

 Thanks in advance.

 Cheers!

 ___
 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] Allocate specific floating IP to an instance

Bonjour Mr Macchi,

As you may already know I don't run Quantum but nova-network with Folsom.
However I should have mentioned it before :)

Any trick for nova-network?

Cheers!

On Tue, Oct 30, 2012 at 10:03 AM, Emilien Macchi emil...@enovance.com wrote:
 Hello Sebastien,


 What you can do today is to choose manually which floating IP you need to
 associate with a specific instance.
 You need to run OpenStack Folsom + Quantum.

 First, you need to create Floating IP pool(s) from Quantum CLI, and after
 that, the tenant is able to associate this IP to a private instance :

 quantum floatingip-create ext_net
 quantum floatingip-associate $FLOATING_ID $PORT_ID

 More informations about Networking configuration with Quantum CLI here :
 http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html


 Cheers ;-)


 Emilien Macchi
 
 // eNovance Inc.  http://enovance.com
 // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
 // 10 rue de la Victoire 75009 Paris

 
 De: Sébastien Han han.sebast...@gmail.com
 À: Openstack openstack@lists.launchpad.net
 Envoyé: Lundi 29 Octobre 2012 17:25:47
 Objet: [Openstack] Allocate specific floating IP to an instance


 Hi Stacker,

 I know OpenStack is not designed that way and I don't think it's
 possible (or maybe I misses something :)) but I was wondering if there
 is any simple workaround to choose a specific floating IP to allocate.
 In other words, don't give me a random or N+1 next floating IP
 available but let me decide which floating IP I want to assign to my
 instance. It doesn't make sense in a public cloud but it does for a
 corporate/private cloud. It would be nice to have :)

 Thanks in advance.

 Cheers!

 ___
 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] Allocate specific floating IP to an instance

@Kiall, if it does, tell us more about it please.


On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie wrote:
 I'm fairly confident that quantum is not a requirement for this.

 Nova's in-built networking supports exactly this since as long ago as I can
 remember.

 Thanks,
 Kiall

 On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com wrote:

 Hello Sebastien,


 What you can do today is to choose manually which floating IP you need to
 associate with a specific instance.
 You need to run OpenStack Folsom + Quantum.

 First, you need to create Floating IP pool(s) from Quantum CLI, and after
 that, the tenant is able to associate this IP to a private instance :

 quantum floatingip-create ext_net

 quantum floatingip-associate $FLOATING_ID $PORT_ID

 More informations about Networking configuration with Quantum CLI here :

 http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html


 Cheers ;-)


 Emilien Macchi
 
 // eNovance Inc.  http://enovance.com
 // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
 // 10 rue de la Victoire 75009 Paris

 
 De: Sébastien Han han.sebast...@gmail.com
 À: Openstack openstack@lists.launchpad.net
 Envoyé: Lundi 29 Octobre 2012 17:25:47
 Objet: [Openstack] Allocate specific floating IP to an instance

 Hi Stacker,

 I know OpenStack is not designed that way and I don't think it's
 possible (or maybe I misses something :)) but I was wondering if there
 is any simple workaround to choose a specific floating IP to allocate.
 In other words, don't give me a random or N+1 next floating IP
 available but let me decide which floating IP I want to assign to my
 instance. It doesn't make sense in a public cloud but it does for a
 corporate/private cloud. It would be nice to have :)

 Thanks in advance.

 Cheers!

 ___
 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] Allocate specific floating IP to an instance

Hi Sebastian,

The commands are nearly identical - just replace quantum with nova!

Although, it sounds like you already have floating IPs being allocated
randomly.

That could be one of two things - either you have
auto_assign_floatingip=True in your configuration, or you misunderstand the
difference between fixed and floating ips.

When you boot an instance, does it get a private or public IP? And - when
you ran the network-create command, what IP range did you use?

Kiall
On Oct 30, 2012 9:26 AM, Sébastien Han han.sebast...@gmail.com wrote:

 @Kiall, if it does, tell us more about it please.


 On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie
 wrote:
  I'm fairly confident that quantum is not a requirement for this.
 
  Nova's in-built networking supports exactly this since as long ago as I
 can
  remember.
 
  Thanks,
  Kiall
 
  On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com wrote:
 
  Hello Sebastien,
 
 
  What you can do today is to choose manually which floating IP you need
 to
  associate with a specific instance.
  You need to run OpenStack Folsom + Quantum.
 
  First, you need to create Floating IP pool(s) from Quantum CLI, and
 after
  that, the tenant is able to associate this IP to a private instance :
 
  quantum floatingip-create ext_net
 
  quantum floatingip-associate $FLOATING_ID $PORT_ID
 
  More informations about Networking configuration with Quantum CLI here :
 
 
 http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
 
 
  Cheers ;-)
 
 
  Emilien Macchi
  
  // eNovance Inc.  http://enovance.com
  // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
  // 10 rue de la Victoire 75009 Paris
 
  
  De: Sébastien Han han.sebast...@gmail.com
  À: Openstack openstack@lists.launchpad.net
  Envoyé: Lundi 29 Octobre 2012 17:25:47
  Objet: [Openstack] Allocate specific floating IP to an instance
 
  Hi Stacker,
 
  I know OpenStack is not designed that way and I don't think it's
  possible (or maybe I misses something :)) but I was wondering if there
  is any simple workaround to choose a specific floating IP to allocate.
  In other words, don't give me a random or N+1 next floating IP
  available but let me decide which floating IP I want to assign to my
  instance. It doesn't make sense in a public cloud but it does for a
  corporate/private cloud. It would be nice to have :)
 
  Thanks in advance.
 
  Cheers!
 
  ___
  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] about nova-schedule queues

2012-10-30 Thread 韦远科

hi all,

I read into the source code for nova-scheduler and found there actually
exists three msg queues, like
scheduler
scheduler.node70
scheduler_*fanout_bd738fedcdf344d9bb3cb580657f54e0*.

what's the functions for each queue and are there connections??


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] Allocate specific floating IP to an instance

Hi Kial,

Hold on...
You obviously didn't understand my question. So please don't try to
teach me anything. I can admit that the initial description of my
request was a bit unclear. So I'm gonna try to clarify it.

I use nova-network with the VLAN manager, so I have a network range
per projects (fixed ips), per VLAN. Each project uses a specific pool,
I use the floating IPs to expose instances to another private network
and I don't use the auto_assign_floating_ip parameter.

Now, when I perform a nova floating-ip-create my-pool this gives
me the first floating IP available of that pool. What I want to
know/achieve is to decide the floating IP address to create. Basically
this could lead to a command like:

# nova floating-ip-create my-pool floating-ip-that-I-want-create-from-a-pool

But as you can see below, it's not available from the CLI:

# nova help floating-ip-create
usage: nova floating-ip-create [floating-ip-pool]

Allocate a floating IP for the current tenant.

Positional arguments:
  floating-ip-pool  Name of Floating IP Pool. (Optional)

Then I'll associate this floating IP to one of my instances.

Let's try to raise the level of this discussion. Now if there is
something that I don't know, or something that I missed, feel free to
teach/correct me. I'm looking for a workaround, or code patch.
Something that doesn't require huge amount of work. Is that doable?

Anyone?

On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes ki...@managedit.ie wrote:
 Hi Sebastian,

 The commands are nearly identical - just replace quantum with nova!

 Although, it sounds like you already have floating IPs being allocated
 randomly.

 That could be one of two things - either you have
 auto_assign_floatingip=True in your configuration, or you misunderstand the
 difference between fixed and floating ips.

 When you boot an instance, does it get a private or public IP? And - when
 you ran the network-create command, what IP range did you use?

 Kiall

 On Oct 30, 2012 9:26 AM, Sébastien Han han.sebast...@gmail.com wrote:

 @Kiall, if it does, tell us more about it please.


 On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie
 wrote:
  I'm fairly confident that quantum is not a requirement for this.
 
  Nova's in-built networking supports exactly this since as long ago as I
  can
  remember.
 
  Thanks,
  Kiall
 
  On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com wrote:
 
  Hello Sebastien,
 
 
  What you can do today is to choose manually which floating IP you need
  to
  associate with a specific instance.
  You need to run OpenStack Folsom + Quantum.
 
  First, you need to create Floating IP pool(s) from Quantum CLI, and
  after
  that, the tenant is able to associate this IP to a private instance :
 
  quantum floatingip-create ext_net
 
  quantum floatingip-associate $FLOATING_ID $PORT_ID
 
  More informations about Networking configuration with Quantum CLI here
  :
 
 
  http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html
 
 
  Cheers ;-)
 
 
  Emilien Macchi
  
  // eNovance Inc.  http://enovance.com
  // ✉ emil...@enovance.com ☎ +33 (0)1 49 70 99 80
  // 10 rue de la Victoire 75009 Paris
 
  
  De: Sébastien Han han.sebast...@gmail.com
  À: Openstack openstack@lists.launchpad.net
  Envoyé: Lundi 29 Octobre 2012 17:25:47
  Objet: [Openstack] Allocate specific floating IP to an instance
 
  Hi Stacker,
 
  I know OpenStack is not designed that way and I don't think it's
  possible (or maybe I misses something :)) but I was wondering if there
  is any simple workaround to choose a specific floating IP to allocate.
  In other words, don't give me a random or N+1 next floating IP
  available but let me decide which floating IP I want to assign to my
  instance. It doesn't make sense in a public cloud but it does for a
  corporate/private cloud. It would be nice to have :)
 
  Thanks in advance.
 
  Cheers!
 
  ___
  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] about nova-schedule queues


Following is my understanding:
usage:
scheduler queue is used for compute api server. For example of nova 
boot, API server will send a msg to scheduler queue for a booting
scheduler_*fanout_ is used for service*s to report service 
capability. For example, nova compute **will use scheduler_fanout to 
publish its capabilities.


scheduler.{hostname} seemingly is not used now.
we can deploy many schedulers into a Openstack cloud. All the schedulers 
will listen on scheduler msg queue. AMQP server (rabbitmq) will adopt 
round robin way to
dispatch the msg to these schedulers. But since the capabilities are fan 
outed, all the schedulers can receive these capabilities.


On 10/30/2012 06:55 PM, 韦远科 wrote:

hi all,

I read into the source code for nova-scheduler and found there 
actually exists three msg queues, like

scheduler
scheduler.node70
scheduler_*fanout_bd738fedcdf344d9bb3cb580657f54e0*.

what's the functions for each queue and are there connections??


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


___
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] Allocate specific floating IP to an instance

Response inline.

Thanks,
Kiall

On Tue, Oct 30, 2012 at 11:04 AM, Sébastien Han han.sebast...@gmail.comwrote:

Hi Kial,

Hold on...
You obviously didn't understand my question. So please don't try to
teach me anything. I can admit that the initial description of my
request was a bit unclear. So I'm gonna try to clarify it.

I apologize, I certainly did not intend any insult.

I use nova-network with the VLAN manager, so I have a network range
per projects (fixed ips), per VLAN. Each project uses a specific pool,
I use the floating IPs to expose instances to another private network
and I don't use the auto_assign_floating_ip parameter.

Great - Sounds like a pretty standard setup.

Now, when I perform a nova floating-ip-create my-pool this gives
me the first floating IP available of that pool. What I want to
know/achieve is to decide the floating IP address to create. Basically
this could lead to a command like:

# nova floating-ip-create my-pool
floating-ip-that-I-want-create-from-a-pool

Ah - I understand now.

This is not supported by Nova Network (I can't say if it's supported with
Quantum).

But as you can see below, it's not available from the CLI:

# nova help floating-ip-create
usage: nova floating-ip-create [floating-ip-pool]

Allocate a floating IP for the current tenant.

Positional arguments:
floating-ip-pool Name of Floating IP Pool. (Optional)

Then I'll associate this floating IP to one of my instances.

Let's try to raise the level of this discussion. Now if there is
something that I don't know, or something that I missed, feel free to
teach/correct me.

Again - I apologize. No insult was intended.

I'm looking for a workaround, or code patch.
Something that doesn't require huge amount of work. Is that doable?

I believe it is doable without significant changes to the code.

By patching the code to allow an extra parameter to pass through from the
REST API call, all the way through to the DB's allocation method,
the allocation method could be made to choose a particular IP by altering
the SQL query executed.

Some pointers to the relevant parts of the code:

REST API:
https://github.com/openstack/nova/blob/stable/folsom/nova/api/openstack/compute/contrib/floating_ips.py#L162-180

Network Service API:
https://github.com/openstack/nova/blob/stable/folsom/nova/network/api.py#L177-188

Network Service Manager:
https://github.com/openstack/nova/blob/stable/folsom/nova/network/manager.py#L406-443

DB API:
*
https://github.com/openstack/nova/blob/stable/folsom/nova/db/api.py#L263-269
*

DB Implementation:
https://github.com/openstack/nova/blob/stable/folsom/nova/db/sqlalchemy/api.py#L700-718

I hope this helps!

Actually - It looked like it could be done fairly quickly, you can try this
(untested) patch: http://paste.ubuntu.com/1317723/plain/

Once applied, you should be able to supply an ip param as part of the
REST API call, and you will get that specific IP - if it is available. This
doesn't update the CLI, I've never looked at it's code so wouldn't know
where to start :)

Thanks,
Kiall

Anyone?

On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes ki...@managedit.ie
wrote:
Hi Sebastian,

The commands are nearly identical - just replace quantum with nova!

Although, it sounds like you already have floating IPs being allocated
randomly.

That could be one of two things - either you have
auto_assign_floatingip=True in your configuration, or you misunderstand
the
difference between fixed and floating ips.

When you boot an instance, does it get a private or public IP? And - when
you ran the network-create command, what IP range did you use?

Kiall

On Oct 30, 2012 9:26 AM, Sébastien Han han.sebast...@gmail.com
wrote:

@Kiall, if it does, tell us more about it please.

On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie
wrote:
I'm fairly confident that quantum is not a requirement for this.

Nova's in-built networking supports exactly this since as long ago as
I
can
remember.

Thanks,
Kiall

On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com
wrote:

Hello Sebastien,

What you can do today is to choose manually which floating IP you
need
to
associate with a specific instance.
You need to run OpenStack Folsom + Quantum.

First, you need to create Floating IP pool(s) from Quantum CLI, and
after
that, the tenant is able to associate this IP to a private instance :

quantum floatingip-create ext_net

quantum floatingip-associate $FLOATING_ID $PORT_ID

More informations about Networking configuration with Quantum CLI
here
:

http://docs.openstack.org/trunk/openstack-network/admin/content/demo_logical_network_config.html

Cheers ;-)

Emilien Macchi

// eNovance Inc. http://enovance.com
// ✉ emil...@enovance.com ☎

Re: [Openstack] about nova-schedule queues

2012-10-30 Thread Sandy Walsh

As with most services there are two queues, but the scheduler has one extra:

1. The general round-robin queue. Any worker of that class can process the 
event. But, only one worker will handle the event.
2. The specific worker queue. Used when I want an event to go to a specific 
worker, for example: I want Scheduler #2 to deal with this
3. The fan-out queue. For sending atomic, non-critical information to all 
workers. The compute nodes send periodic capacity updates to all schedulers on 
this channel.

Hope it helps!
-S


From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net 
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of 
韦远科 [weiyuanke...@gmail.com]
Sent: Tuesday, October 30, 2012 7:55 AM
To: openstack mail list
Subject: [Openstack] about nova-schedule queues

hi all,

I read into the source code for nova-scheduler and found there actually exists 
three msg queues, like
scheduler
scheduler.node70
scheduler_fanout_bd738fedcdf344d9bb3cb580657f54e0.

what's the functions for each queue and are there connections??


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] Allocate specific floating IP to an instance

P.S. - That patch is against the current stable/folsom branch.. It won't
apply to Grizzly cleanly..

Thanks,
Kiall

On Tue, Oct 30, 2012 at 11:46 AM, Kiall Mac Innes ki...@managedit.iewrote:

Response inline.

Thanks,
Kiall

On Tue, Oct 30, 2012 at 11:04 AM, Sébastien Han
han.sebast...@gmail.comwrote:

Hi Kial,

I apologize, I certainly did not intend any insult.

Great - Sounds like a pretty standard setup.

# nova floating-ip-create my-pool
floating-ip-that-I-want-create-from-a-pool

Ah - I understand now.

This is not supported by Nova Network (I can't say if it's supported with
Quantum).

But as you can see below, it's not available from the CLI:

# nova help floating-ip-create
usage: nova floating-ip-create [floating-ip-pool]

Allocate a floating IP for the current tenant.

Positional arguments:
floating-ip-pool Name of Floating IP Pool. (Optional)

Then I'll associate this floating IP to one of my instances.

Let's try to raise the level of this discussion. Now if there is
something that I don't know, or something that I missed, feel free to
teach/correct me.

Again - I apologize. No insult was intended.

I'm looking for a workaround, or code patch.
Something that doesn't require huge amount of work. Is that doable?

I believe it is doable without significant changes to the code.

Some pointers to the relevant parts of the code:

REST API:

https://github.com/openstack/nova/blob/stable/folsom/nova/api/openstack/compute/contrib/floating_ips.py#L162-180

Network Service API:

https://github.com/openstack/nova/blob/stable/folsom/nova/network/api.py#L177-188

Network Service Manager:

https://github.com/openstack/nova/blob/stable/folsom/nova/network/manager.py#L406-443

DB API:
*
https://github.com/openstack/nova/blob/stable/folsom/nova/db/api.py#L263-269
*

DB Implementation:

https://github.com/openstack/nova/blob/stable/folsom/nova/db/sqlalchemy/api.py#L700-718

I hope this helps!

Actually - It looked like it could be done fairly quickly, you can try
this (untested) patch: http://paste.ubuntu.com/1317723/plain/

Thanks,
Kiall

Anyone?

On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes ki...@managedit.ie
wrote:
Hi Sebastian,

The commands are nearly identical - just replace quantum with nova!

Although, it sounds like you already have floating IPs being allocated
randomly.

That could be one of two things - either you have
auto_assign_floatingip=True in your configuration, or you misunderstand
the
difference between fixed and floating ips.

When you boot an instance, does it get a private or public IP? And -
when
you ran the network-create command, what IP range did you use?

Kiall

On Oct 30, 2012 9:26 AM, Sébastien Han han.sebast...@gmail.com
wrote:

@Kiall, if it does, tell us more about it please.

On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie
wrote:
I'm fairly confident that quantum is not a requirement for this.

Nova's in-built networking supports exactly this since as long ago
as I
can
remember.

Thanks,
Kiall

On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com
wrote:

Hello Sebastien,

What you can do today is to choose manually which floating IP you
need
to
associate with a specific instance.
You need to run OpenStack Folsom + Quantum.

First, you need to create Floating IP pool(s) from Quantum CLI, and
after
that, the tenant is able to associate this IP to a private instance
:

quantum floatingip-create ext_net

quantum floatingip-associate $FLOATING_ID $PORT_ID

More informations about Networking configuration with Quantum CLI
here
:

[Openstack] Nova compute fails to start

2012-10-30 Thread Johannes Baltimore

Hello.

Whenever I try to start the compute module, it seems not to start at all.
I'm pasting the log entry for when I try to do it:

http://paste.ubuntu.com/1317755

If someone wants to help and needs to know anything else, just let me know.
Thanks in advance
___
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 compute fails to start

2012-10-30 Thread John Griffith

On Tue, Oct 30, 2012 at 6:02 AM, Johannes Baltimore johannes.b...@gmail.com
 wrote:

 Hello.

 Whenever I try to start the compute module, it seems not to start at all.
 I'm pasting the log entry for when I try to do it:

 http://paste.ubuntu.com/1317755

 If someone wants to help and needs to know anything else, just let me
 know. Thanks in advance

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

 Hi Johannes,

Looks like something amiss in nova.conf, do you have the following in your
nova.conf file:

`compute_driver=libvirt.LibvirtDriver`


John
___
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 compute fails to start

2012-10-30 Thread Johannes Baltimore

That was exactly what was missing. Thank you,good sir.

2012/10/30 John Griffith john.griff...@solidfire.com



 On Tue, Oct 30, 2012 at 6:02 AM, Johannes Baltimore 
 johannes.b...@gmail.com wrote:

 Hello.

 Whenever I try to start the compute module, it seems not to start at all.
 I'm pasting the log entry for when I try to do it:

 http://paste.ubuntu.com/1317755

 If someone wants to help and needs to know anything else, just let me
 know. Thanks in advance

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

 Hi Johannes,

 Looks like something amiss in nova.conf, do you have the following in your
 nova.conf file:

 `compute_driver=libvirt.LibvirtDriver`


 John

___
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] Domain Name Spaces

2012-10-30 Thread David Chadwick


On 27/10/2012 00:17, Henry Nash wrote:

So to pick up on a couple of the areas of contention:

a) Roles.  I agree that role names must stay globally unique.  One way
of thinking about this is that it is not actually keystone that is
creating the role name space it is the other services (Nova etc.) by
specifying roles in their policy files.  Until those services support
domain specific segmentation, then role names stay global.


I addressed this issue in my Federation design doc (in Appendix 2). Here 
is the text to save you having to look it up (note that an attribute is 
simply a generalisation of role and is needed in the broader authz 
context. Roles are too limiting.)


Attributes may be globally defined, e.g. visa attributes, or locally 
defined e.g. member of club X. Globally defined attributes are often 
specified in international standards and may be used in several 
different domains and federations. Their syntax and semantics are fixed, 
regardless of which Attribute Authority (AA) issues them. Local 
attributes are defined by their issuing attribute authority and usually 
are only valid in the domain or federation in which the AA is a member. 
For locally identifiable attributes the attribute authority (issuer) 
must be globally identifiable (in the federation). The attribute then 
becomes globally identifiable through hierarchical naming (AA.attribute).


Whilst in a non-federated world the service provider (e.g. Swift) can 
unilaterally define the roles it wants, in a federated world the 
attributes have to be mutually agreed between the issuer (AA) and the 
consumer (e.g. Swift).


To address this issue I proposed a role mapping (attribute mapping) 
service that is run by Keystone, and it maps between the role/attribute 
required by the service, and the actual attribute issued by the AA. For 
example, say Swift requires the role of Admin to be assigned to 
addministrators, whereas company X, the attribute authority, assigns the 
LDAP attribute title=OpenStack Cloud Administrator to its admin staff. 
Keystone will use its attribute mapping service to map between these values.




b) Will multi-domains make it more complicated in terms of authorisation
- e.g. will the users have to input a Domain Name into Horizon the whole
time?  The first thing I would say is that if the cloud administrator
has create multiple domains, then the keystone API should indeed require
the domain specification.


Again, in our federated design document we have the concept of a realm, 
which is similar to that of a domain, only in the federated case it 
indicates the place where the user will be authenticated and obtain 
(some of) his authz attributes from. The user can indicate the 
realm/domain name on the command line, but if it is missing, Keystone 
replies with a list of domains that it knows about and asks the user to 
choose one from the list.


 However, that should not mean it should be

laborious for a Horizon user.  In the case where a Cloud Provider has
created domains to encapsulate each of their customers - then if they
want to let those customer use horizon as the UI, then I would think
they want to be able to give each customer a unique URL which will point
to a Horizon that knows which domain to go to.


this is certainly a possibility.

regards

David

  Maybe the url contains

the Domain Name or ID in the path, and Horizon pulls this out of its own
url (assuming that's possible) and hence the user is never given an
option to chose a domain.  A Cloud Admin would use a non domain
qualified url to get to Horizon (basically as it is now) and hence be
able to see the different domains.  Likewise, in the case of where the
Cloud Provider has not chosen to create any individual domains (and is
just running the cloud in the default domain), then the  non domain
qualified url would be used to a Horizon that only showed one, default
domain and hence no choice is required.


Henry

On 26 Oct 2012, at 17:31, heckj wrote:


Bringing conversation for domains in Keystone to the broader mailing
lists.


On Oct 26, 2012, at 5:18 AM, Dolph Mathews dolph.math...@gmail.com
mailto:dolph.math...@gmail.com wrote:

I think this discussion would be great for both mailing lists.

-Dolph


On Fri, Oct 26, 2012 at 5:18 AM, Henry Nash henry.n...@mac.com
mailto:henry.n...@mac.com wrote:

Hi

Not sure where best to have this discussion - here, as a comment
to the v3api doc, or elsewhere - appreciate some guidance and
will transfer this to the right place

At the Summit we started a discussion on whether things like user
name, tenant name etc. should be globally unique or unique within
a domain.  I'd like to widen that discussion to try and a) agree
a direction, b) agree some changes to our current spec. Here's my
view as an opening gambit:

- When a Keystone instance is first started, there is only one,
default, Domain.  The Cloud Provider does not need to create any
new domains,

Re: [Openstack] [keystone] Re: Domain Name Spaces

2012-10-30 Thread David Chadwick


On 26/10/2012 17:31, heckj wrote:

Bringing conversation for domains in Keystone to the broader mailing lists.


On Oct 26, 2012, at 5:18 AM, Dolph Mathews dolph.math...@gmail.com
mailto:dolph.math...@gmail.com wrote:

I think this discussion would be great for both mailing lists.

-Dolph


On Fri, Oct 26, 2012 at 5:18 AM, Henry Nash henry.n...@mac.com
mailto:henry.n...@mac.com wrote:

Hi

Not sure where best to have this discussion - here, as a comment
to the v3api doc, or elsewhere - appreciate some guidance and will
transfer this to the right place

At the Summit we started a discussion on whether things like user
name, tenant name etc. should be globally unique or unique within
a domain.  I'd like to widen that discussion to try and a) agree a
direction, b) agree some changes to our current spec. Here's my
view as an opening gambit:

- When a Keystone instance is first started, there is only one,
default, Domain.  The Cloud Provider does not need to create any
new domains, all projects can exist in this default domain, as
will the users etc.  There is one, global, name space.  Clients
using the v2 API will work just fine.


+1


Very much what we were thinking for the initial implemenation and
rollout to make it backwards compatible with the V2 (non-domain) core API


- If the Cloud Provider wants to provide their customers with
regions they can administer themselves and be self-contained, then
they create a Domain for each customer.  It should be possible for
users/roles to be scoped to a Domain so that (effectively)
administrative duties can be delegated to some users in that
Domain.  So far so good - all this can be done with the v3 API.


Not clear on if you're referring to endpoint regions, or just
describing domain isolation?


I believe you're describing the key use cases behind the domains
mechanism to begin with - user and project partitioning to allow for
administration of those to be clearly owned and managed appropriately.



- We still have work to do to make sure items in other OS projects
that reference tenants (e.g. Images) can take a Domain or Project
ID, but we'll get to that soon enough


Everything will continue to work with projects, but once middleware
starts providing a DOMAIN_ID and DOMAIN_NAME to the underlying
service, it'll be up to them to take advantage of it. Images per
domain is an excellent example use case.



- However, Cloud Providers want to start enabling enterprise
customers to run more and more of the workloads in OpenStack
clouds - over and above, the smaller sized companies that are
doing this today.  For this to work, the encapsulation of a Domain
need, I think, to be able to be stricter - and this is where the
name space comes into play.  I think we need to allow for a Domain
to have its own namespace (i.e. users, roles, projects etc.) as an
option.  I see this as a first step to allowing each Domain to
have its own AuthZ/N service (.e.g external ldap owned and hosted
by the customer who will be using the Domain)

Implementation:

- A simplistic version would just allow a flag to specified on
Domain creation that said whether this a private or shared
Domain.  Shared would use the current global name space (and
probably be the default for compatibility reasons).


I like the direction of this -- need to digest implications :)


I like the idea conceptually - but let's be clear on the implications to
the end users:

Where we're starting is preserving a global name space for project names
and user names. Allowing a mix of segregated and global name spaces
imposes a burden of additional data being needed to uniquely place
authentication and authorization.

We've been keeping to 2 key pieces of info (username, password) to get
authenticated - and then (via CLI or Horizon dashboard) you can choose
from a list of protential projects and carry on. In most practical
circumstances, any user working primarily from the CLI is already
providing 3-4 pieces of information:

* username
* password
* tenant name
* auth_url


In fact these are all name/value pairs, so they can all be regarded as 
attribute names and values (or types and values in LDAP terminology).


The attribute names/types have to be globally unique. I think you have 
implicitly mandated this in Keystone by defining the names yourself, and 
by not allowing other names to be used. I presume that currently it 
would not be meaningful to pass a value of

* age
via the CLI. But it should be, since one might have an authz policy that 
bases its decision on the age of the user.


So how about considering a more generic interface where any attribute 
name and value can be passed, and the authz service will use these to 
see if they fit the policy or not.


regards

David



to access and use the cloud.

By allowing domains to be their own namespaces, we're adding

Re: [Openstack] [keystone] Domain Name Spaces

2012-10-30 Thread Adam Young


On 10/30/2012 06:43 AM, David Chadwick wrote:

On 27/10/2012 00:17, Henry Nash wrote:

So to pick up on a couple of the areas of contention:

a) Roles.  I agree that role names must stay globally unique. One way
of thinking about this is that it is not actually keystone that is
creating the role name space it is the other services (Nova etc.) by
specifying roles in their policy files.  Until those services support
domain specific segmentation, then role names stay global.


I addressed this issue in my Federation design doc (in Appendix 2). 
Here is the text to save you having to look it up (note that an 
attribute is simply a generalisation of role and is needed in the 
broader authz context. Roles are too limiting.)


Attributes may be globally defined, e.g. visa attributes, or locally 
defined e.g. member of club X. Globally defined attributes are often 
specified in international standards and may be used in several 
different domains and federations. Their syntax and semantics are 
fixed, regardless of which Attribute Authority (AA) issues them. Local 
attributes are defined by their issuing attribute authority and 
usually are only valid in the domain or federation in which the AA is 
a member. For locally identifiable attributes the attribute authority 
(issuer) must be globally identifiable (in the federation). The 
attribute then becomes globally identifiable through hierarchical 
naming (AA.attribute).


Whilst in a non-federated world the service provider (e.g. Swift) can 
unilaterally define the roles it wants, in a federated world the 
attributes have to be mutually agreed between the issuer (AA) and the 
consumer (e.g. Swift).


To address this issue I proposed a role mapping (attribute mapping) 
service that is run by Keystone, and it maps between the 
role/attribute required by the service, and the actual attribute 
issued by the AA. For example, say Swift requires the role of Admin to 
be assigned to addministrators, whereas company X, the attribute 
authority, assigns the LDAP attribute title=OpenStack Cloud 
Administrator to its admin staff. Keystone will use its attribute 
mapping service to map between these values.




b) Will multi-domains make it more complicated in terms of authorisation
- e.g. will the users have to input a Domain Name into Horizon the whole
time?  The first thing I would say is that if the cloud administrator
has create multiple domains, then the keystone API should indeed require
the domain specification.


Again, in our federated design document we have the concept of a 
realm, which is similar to that of a domain, only in the federated 
case it indicates the place where the user will be authenticated and 
obtain (some of) his authz attributes from. The user can indicate the 
realm/domain name on the command line, but if it is missing, Keystone 
replies with a list of domains that it knows about and asks the user 
to choose one from the list.


I think this is the Key point.  Domain/Realm means who accepts 
responsibility for the user.  And that responsibility needs to be 
unambiguous.




 However, that should not mean it should be

laborious for a Horizon user.  In the case where a Cloud Provider has
created domains to encapsulate each of their customers - then if they
want to let those customer use horizon as the UI, then I would think
they want to be able to give each customer a unique URL which will point
to a Horizon that knows which domain to go to.


this is certainly a possibility.

regards

David

  Maybe the url contains

the Domain Name or ID in the path, and Horizon pulls this out of its own
url (assuming that's possible) and hence the user is never given an
option to chose a domain.  A Cloud Admin would use a non domain
qualified url to get to Horizon (basically as it is now) and hence be
able to see the different domains.  Likewise, in the case of where the
Cloud Provider has not chosen to create any individual domains (and is
just running the cloud in the default domain), then the  non domain
qualified url would be used to a Horizon that only showed one, default
domain and hence no choice is required.


Henry

On 26 Oct 2012, at 17:31, heckj wrote:


Bringing conversation for domains in Keystone to the broader mailing
lists.


On Oct 26, 2012, at 5:18 AM, Dolph Mathews dolph.math...@gmail.com
mailto:dolph.math...@gmail.com wrote:

I think this discussion would be great for both mailing lists.

-Dolph


On Fri, Oct 26, 2012 at 5:18 AM, Henry Nash henry.n...@mac.com
mailto:henry.n...@mac.com wrote:

Hi

Not sure where best to have this discussion - here, as a comment
to the v3api doc, or elsewhere - appreciate some guidance and
will transfer this to the right place

At the Summit we started a discussion on whether things like user
name, tenant name etc. should be globally unique or unique within
a domain.  I'd like to widen that discussion to try and a) agree
a direction, b) agree some changes to our current spec.

Re: [Openstack] [keystone] Domain Name Spaces

2012-10-30 Thread David Chadwick


Hi Gabriel

there is something of an oxymoron in one of your statements below By 
design, authentication will fail if they don't specify a domain (since 
you won't exist in the global domain)


If the global domain is truly global then it should encompass all public 
and private (sub)domains. Otherwise it is not global.


It is quite easy to include private name spaces in a global name space 
by using hierarchical naming. Firstly ensure that domain names match the 
naming of the global name space. Secondly append the name of the private 
domain to that of the local name to turn the latter into a global name.


If you are familiar with Eduroam, the pan_European wireless 
authentication infrastructure, this is precisely what it does.


When I log in at Kent, I use my kent user id and password. When I log in 
to Eduroam from somewhere else in Europe (or even at kent) I use my kent 
user id and prepend @kent.ac.uk, and the infrastructure automatically 
routes my request and pw to the kent authentication server for 
validation (via Radius).


We should be considering this sort of federated feature (or something 
like it) for Keystone with domains


regards

David


On 30/10/2012 08:00, Henry Nash wrote:

Gabriel,

So I think you are right to ask that this is made clear and concrete -
I'll work with the core contributors of Keystone to make it so.

To your specific point:
- Let's call the initial Domain, the Global Domain, rather than the
default domain
- If the Cloud Provider doesn't explicitly create any domains, then
everything exists in the Global Domain.  There is no need to specify a
domain in any calls, since everything will default to the Global domain.
  The v2 API will work just fine (which knows nothing about domains)
- If they do create some domains, then they indicate (on creation)
whether each of these /share/ the namespace of the Global domain, or
have their own /private/ namespace.
- If all of these new domains were specified as /shared/ then all user
and tenant names are still globally unique.  A caller still does not
technically need to specify a domain, although scoping things down to a
domain (or of course project) is likely for most operations (just like
it is today)
- If, however, some of these new domains were specified as /private/
then any users who are part of a private domain must specify the domain
in order to authenticate.  By design, authentication will fail if they
don't specify a domain (since you won't exist in the global domain).
  Once a user in a private domain is authenticated, they are scoped to
that domain. [implementation: we need to work out whether the domainID
is encoded in the token - this is my assumption since this means the
Domain Name/ID is NOT required for subsequent requestsand
validation, by Keystone, can still be achieved ]
- It is perfectly possible (but of course up to the Cloud Provider) to
support a mixture of /shared/ and /private/ domains (representing
different customer types)but the point being that the Cloud Provider
will tell their customers how they should access they system (i.e.
provide them with any domain specification that may or may not be required).

Very keen to hear other concerns you may have.

Henry
On 27 Oct 2012, at 21:22, Gabriel Hurley wrote:


There are various options for how Horizon can handle the UX problems
associated with adding additional domains. Making it a part of the URL
is one which could be supported, but I’m not inclined to make that the
only method. The implementation details can be hashed out when we get
there.
I am more concerned about the experience for CLI/API users; adding
more parameters they have to pass is quite unfriendly. And I have to
say that Keystone’s track record for handling “default” options has
been quite poor (see “default tenant”). The mixed support for lookups
via ID vs. name is also a mess. There needs to be consistency around
what is unique and in what scope (which is where this thread started).
So far I haven’t heard a concrete answer on that.
For example, if tenants uniqueness is scoped to a domain, and lookups
via tenant name are possible, and there’s a default domain… well
haven’t you just painted yourself into a corner where tenant names in
the default domain must be unique while names in any other domain do
not? It’s these kinds of issues that need to really be thought through.
-Gabriel
*From:*openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net 
mailto:nebula@lists.launchpad.net]*On
Behalf Of*Adam Young
*Sent:*Friday, October 26, 2012 4:19 PM
*To:*Henry Nash
*Cc:*OpenStack Development Mailing List; openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net (openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net)
*Subject:*Re: [Openstack] [keystone] Domain Name Spaces
On 10/26/2012 07:17 PM, Henry Nash

[Openstack] OpenStack + BUILD State stuck for VM instances

2012-10-30 Thread Desta Haileselassie Hagos

Hi All,

The state for VM instances seem to get stuck on build state for a very long
time, and whenever I try to reboot I am having the following error.

ERROR: Cannot 'reboot' while instance is in vm_state building (HTTP 409)


Any help would be appreciated.


Desta
___
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] [Nova] Consistent API validation and error responses

2012-10-30 Thread Karajgi, Rohit

Hi,

Referring to the bug https://bugs.launchpad.net/nova/+bug/1072734, I would like 
to get some thoughts around our API validation approach.

Are we looking at enhancing the API validations in Grizzly, or Nova v3 spec to 
ensure that all validations are made consistently after the Nova API layer?
Currently, image and flavor uuids are validated upfront in the v2 API, however 
volume uuid validation does not happen at this stage.

Though I agree with Dan's thoughts on the performance hit, ensuring that 
validations are consistently made for images and volumes enhances usability.
Can we consider this change for v2 API?


Best Regards,
Rohit Karajgi | Lead Engineer | NTT Data Global Technology Services Private Ltd 
| w. +91.20.6604.1500 x 378 |  m. +91 992.242.9639 | 
rohit.kara...@nttdata.commailto:rohit.kara...@nttdata.com


__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] ERROR: Keypair data is invalid

2012-10-30 Thread DarkSinclair

Greetings all,

There looks to be a problem with specifying any key name containing a special 
character (except dash and/or underscore) within 'nova keypair-add'.   I am 
currently running Folsom on Ubuntu and noticed the archives at 
https://lists.launchpad.net/openstack/msg17626.html indicate the problem was 
present on Essex as well and never resolved.  I'm new to the project and only 
beginning but it looks like the following function in nova/compute/api.py may 
not be behaving properly to return an appropriate message (also if possible, 
could a list of safe characters in the return message be possible?), and 
instead reports Keypair data is invalid when clearly this is an issue with the 
desired naming of the key pair (the same public key is accepted fine when 'safe 
chars' (_-) only are used.

Any direction would be greatly appreciated.  If I should be posting this bug 
elsewhere, please let me know and I will happily do-so.

Thanks in advance,

def _validate_keypair_name(self, context, user_id, key_name):
  safechars = _- + string.digts + string.ascii_letters
  clean_value = .join(x for x in key_name if x in safe chars)
  if clean_value != key_name:
msg = _(Keypair name contains unsafe characters)
raise exception.InvalidKeypair(explanation=msg)
[…]

 The errors when trying to add anything defined outside of safechars:

# nova keypair-add --pub_key isinclair.id_rsa.pub isinclair_id_rsa
# nova keypair-add --pub_key isinclair.id_rsa.pub isinclair-id_rsa
#
# nova keypair-add --pub_key isinclair.id_rsa.pub isinclair.id_rsa
ERROR: Keypair data is invalid (HTTP 400) (Request-ID: 
req-4a30f245-af5a-4b2e-854d-a842380889cc)
# nova keypair-add --pub_key isinclair.id_rsa.pub isinclair@id_rsa
ERROR: Keypair data is invalid (HTTP 400) (Request-ID: 
req-dfec1608-e188-42e3-b922-3c1d49f4349a)
# nova keypair-add --pub_key isinclair.id_rsa.pub isinclair%id_rsa
ERROR: Keypair data is invalid (HTTP 400) (Request-ID: 
req-ac791522-4e05-4cb8-a6eb-487c65b9a3c5)
# nova keypair-add --pub_key isinclair.id_rsa.pub 'isinclair.id_rsa'
ERROR: Keypair data is invalid (HTTP 400) (Request-ID: 
req-401811b6-d7d0-4ce0-86a1-7cc47f904587)
 # nova keypair-add --pub_key isinclair.id_rsa.pub isinclair=id_rsa
ERROR: Keypair data is invalid (HTTP 400) (Request-ID: 
req-f01dc4b1-ea7f-4cc1-be9b-bc7dfc35ef56)
#
___
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] Quotas in folsom

2012-10-30 Thread Everett Toews

On 10/29/12 2:25 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:

It's also worth noting that I've finally been able to start working on
Boson, which may help with thatŠ
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.com


---

Is http://wiki.openstack.org/Boson still up to date? Is there a blueprint
for it?

Thanks,
Everett


___
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] Horizon developers guide

2012-10-30 Thread Srikanth Kumar Lingala

Hi,
To customize Openstack dashboard, any developer's guide available?

-- 

Srikanth.
___
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] Quotas in folsom

2012-10-30 Thread Kevin L. Mitchell

On Tue, 2012-10-30 at 10:19 -0500, Everett Toews wrote:
 Is http://wiki.openstack.org/Boson still up to date? Is there a blueprint
 for it?

There is not a blueprint for it, since it's a brand-new project, and I'm
just getting started on it.  I can point you at the code repository I
have for it, at https://github.com/klmitch/boson (I'll worry about going
into incubation later, after we have something that kinda works, but I'm
happy to accept pull requests…)  I'll likely hold off on blueprints
until it's time to start integrating it into the openstack projects…
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.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-dev] Horizon developers guide

2012-10-30 Thread Anne Gentle

For customizing by modifying panels and such, see
http://docs.openstack.org/developer/horizon/topics/customizing.html

To custom brand the dashboard, see
http://docs.openstack.org/trunk/openstack-compute/install/yum/content/dashboard-custom-brand.html

Anne

On Tue, Oct 30, 2012 at 10:30 AM, Srikanth Kumar Lingala
srikanthkumar.ling...@gmail.com wrote:
 Hi,
 To customize Openstack dashboard, any developer's guide available?

 --
 
 Srikanth.


 ___
 OpenStack-dev mailing list
 openstack-...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
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] Allocate specific floating IP to an instance

Thanks for the detail reply :-).

And many thanks for the patch, I'll give a try and let you know.

Cheers!


On Tue, Oct 30, 2012 at 12:47 PM, Kiall Mac Innes ki...@managedit.ie wrote:
 P.S. - That patch is against the current stable/folsom branch.. It won't
 apply to Grizzly cleanly..

 Thanks,
 Kiall



 On Tue, Oct 30, 2012 at 11:46 AM, Kiall Mac Innes ki...@managedit.ie
 wrote:

 Response inline.

 Thanks,
 Kiall


 On Tue, Oct 30, 2012 at 11:04 AM, Sébastien Han han.sebast...@gmail.com
 wrote:

 Hi Kial,

 Hold on...
 You obviously didn't understand my question. So please don't try to
 teach me anything. I can admit that the initial description of my
 request was a bit unclear. So I'm gonna try to clarify it.


 I apologize, I certainly did not intend any insult.



 I use nova-network with the VLAN manager, so I have a network range
 per projects (fixed ips), per VLAN. Each project uses a specific pool,
 I use the floating IPs to expose instances to another private network
 and I don't use the auto_assign_floating_ip parameter.


 Great - Sounds like a pretty standard setup.



 Now, when I perform a nova floating-ip-create my-pool this gives
 me the first floating IP available of that pool. What I want to
 know/achieve is to decide the floating IP address to create. Basically
 this could lead to a command like:

 # nova floating-ip-create my-pool
 floating-ip-that-I-want-create-from-a-pool


 Ah - I understand now.

 This is not supported by Nova Network (I can't say if it's supported with
 Quantum).



 But as you can see below, it's not available from the CLI:

 # nova help floating-ip-create
 usage: nova floating-ip-create [floating-ip-pool]

 Allocate a floating IP for the current tenant.

 Positional arguments:
   floating-ip-pool  Name of Floating IP Pool. (Optional)

 Then I'll associate this floating IP to one of my instances.

 Let's try to raise the level of this discussion. Now if there is
 something that I don't know, or something that I missed, feel free to
 teach/correct me.


 Again - I apologize. No insult was intended.


 I'm looking for a workaround, or code patch.
 Something that doesn't require huge amount of work. Is that doable?


 I believe it is doable without significant changes to the code.

 By patching the code to allow an extra parameter to pass through from the
 REST API call, all the way through to the DB's allocation method, the
 allocation method could be made to choose a particular IP by altering the
 SQL query executed.

 Some pointers to the relevant parts of the code:

 REST API:

 https://github.com/openstack/nova/blob/stable/folsom/nova/api/openstack/compute/contrib/floating_ips.py#L162-180

 Network Service API:

 https://github.com/openstack/nova/blob/stable/folsom/nova/network/api.py#L177-188

 Network Service Manager:

 https://github.com/openstack/nova/blob/stable/folsom/nova/network/manager.py#L406-443

 DB API:

 https://github.com/openstack/nova/blob/stable/folsom/nova/db/api.py#L263-269

 DB Implementation:

 https://github.com/openstack/nova/blob/stable/folsom/nova/db/sqlalchemy/api.py#L700-718

 I hope this helps!

 Actually - It looked like it could be done fairly quickly, you can try
 this (untested) patch: http://paste.ubuntu.com/1317723/plain/

 Once applied, you should be able to supply an ip param as part of the
 REST API call, and you will get that specific IP - if it is available. This
 doesn't update the CLI, I've never looked at it's code so wouldn't know
 where to start :)

 Thanks,
 Kiall


 Anyone?

 On Tue, Oct 30, 2012 at 11:03 AM, Kiall Mac Innes ki...@managedit.ie
 wrote:
  Hi Sebastian,
 
  The commands are nearly identical - just replace quantum with nova!
 
  Although, it sounds like you already have floating IPs being allocated
  randomly.
 
  That could be one of two things - either you have
  auto_assign_floatingip=True in your configuration, or you misunderstand
  the
  difference between fixed and floating ips.
 
  When you boot an instance, does it get a private or public IP? And -
  when
  you ran the network-create command, what IP range did you use?
 
  Kiall
 
  On Oct 30, 2012 9:26 AM, Sébastien Han han.sebast...@gmail.com
  wrote:
 
  @Kiall, if it does, tell us more about it please.
 
 
  On Tue, Oct 30, 2012 at 10:19 AM, Kiall Mac Innes ki...@managedit.ie
  wrote:
   I'm fairly confident that quantum is not a requirement for this.
  
   Nova's in-built networking supports exactly this since as long ago
   as I
   can
   remember.
  
   Thanks,
   Kiall
  
   On Oct 30, 2012 9:04 AM, Emilien Macchi emil...@enovance.com
   wrote:
  
   Hello Sebastien,
  
  
   What you can do today is to choose manually which floating IP you
   need
   to
   associate with a specific instance.
   You need to run OpenStack Folsom + Quantum.
  
   First, you need to create Floating IP pool(s) from Quantum CLI, and
   after
   that, the tenant is able to associate this IP to a private instance
   :
  
   quantum floatingip-create

[Openstack] Scheduler issues in folsom

2012-10-30 Thread Jonathan Proulx

Hi All,

I'm having what I consider serious issues with teh scheduler in
Folsom.  It seems to relate to the introdution of threading in the
scheduler.

For a number of local reason we prefer to have instances start on the
compute node with the least amount of free RAM that is still enough to
satisfy the request which is the reverse of the default policy of
scheduling on the system with the most free RAM.  I'm fairly certain
the smae behavior would be seen with that policy as well, and any
other policy that results in a best choice for scheduling the next
instance. 

We have work loads that start hundreds of instances or the same image
and there are plans on scaling this to thousands.  What I'm seeing is
somehting like this:

* user submits API request for 300 instances
* scheduler puts them all on one node
* retry schedule kicks in at some point for the 276 that don't fit
* those 276 are all scheduled on the next best node
* retry cycle repeats with the 252 that don't fit there

I'm not clear exactly where the RetryScheduler in serts itself (I
should probably read it) but the first compute node is very overloaded
handling start up request which results in a fair number of instances
entering ERROR state rather than rescheduling (so not all 276
actually make it to the next round) and the whole process it painfully
slow.  In the end we are lucky to see 50% of the requested instances
actually make it into Active state (and then only becasue we increased
scheduler_max_attempts).

Is that really how it's supposed to work?  With the introduction of
the RetryScheduler as a fix for the scheduling race condition I think
it is, but it is a pretty bad solution for me, unless I'm missing
something, am I?  wouln't be the first time... 

For now I'm working around this by using the ChanceScheduler
(compute_scheduler_driver=nova.scheduler.chance.ChanceScheduler) so
the scheduler threads don't pick a best node.  This is orders of
magnitude faster and consistantly successful in my tests.  It is not
ideal for us as we have a small minority of ciompute nodes with twice
the memory capacity of our standard nodes and would prefer to keep
those available for some of our extra large memory flavors and we'd
also liek to minimize memory fragmentation on the standard sized nodes
for similar reasons.

-Jon

___
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] new mailing list for bare-metal provisioning

2012-10-30 Thread Mark T. Voelker

 It was my understanding that messages that don't include a proper
 topic end up being sent to everyone. So you can use topics to

That depends on what the user sets under Do you want to receive
messages that do not match any topic filter?

At Your Service,

Mark T. Voelker
Systems Development Unit
+1 919 392-4326
mvoel...@cisco.com

On 10/30/2012 04:29 AM, Thierry Carrez wrote:
 Mark T. Voelker wrote:
 Thus, I'd have missed those messages if I were only subscribed to
 the Quantum topic.
 
 It was my understanding that messages that don't include a proper
 topic end up being sent to everyone. So you can use topics to
 actively ignore stuff that has been marked [Nova], rather than only
 receive [baremetal] stuff.
 
 Personally I like to see everything so it doesn't much matter to
 me other than in how I set up my email filters, but I think perhaps
 this is one reason why we've had the discussion about more vs fewer
 mailing lists more than once.
 
 I personally prefer to receive everything and do filtering client-side
 too. Topics are just an additional option, I guess.
 



signature.asc
Description: OpenPGP digital signature
___
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] Nova middleware for enabling CORS?

2012-10-30 Thread Renier Morales

Hello,

I'm wondering if someone has already created a nova paste filter/middleware for 
enabling Cross-Origin Resource Sharing (CORS), allowing a web page to access 
the openstack api from another domain. Any pointers out there?

Thanks,

-Renier


___
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 middleware for enabling CORS?

2012-10-30 Thread David Kranz


On 10/30/2012 12:43 PM, Renier Morales wrote:

Hello,

I'm wondering if someone has already created a nova paste 
filter/middleware for enabling Cross-Origin Resource Sharing (CORS), 
allowing a web page to access the openstack api from another domain. 
Any pointers out there?


Thanks,

-Renier




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
This https://review.openstack.org/#/c/6909/ was an attempt to add such 
middleware to swift. It is

generic CORS support but seems
to have been rejected in favor of putting CORS support in swift directly 
and checked in last week:

https://github.com/openstack/swift/commit/74b27d504d310c70533175759923c21df158daf9

 -David
___
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 middleware for enabling CORS?

2012-10-30 Thread javier cerviño

Hi Renier,

We're currently developing a JavaScript API for Nova, Keystone, and
Glance. To do so we also installed a CORS filter, developed by Adrian
Smith, (with small changes) in these components.

I can pass you the code and a short guideline to configure it if you want.

Cheers,
Javier.

On 30 October 2012 17:43, Renier Morales reni...@us.ibm.com wrote:
 Hello,

 I'm wondering if someone has already created a nova paste filter/middleware
 for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to
 access the openstack api from another domain. Any pointers out there?

 Thanks,

 -Renier



 ___
 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 middleware for enabling CORS?

2012-10-30 Thread Renier Morales

Javier,

Thank you. That sounds good. Actually I would only need to enable CORS on Nova, 
Keystone, and Glance. So if you have that and can share it, that would be 
perfect for me. Awesome actually :-)

Thanks,

-Renier


On Oct 30, 2012, at 1:08 PM, javier cerviño wrote:

 Hi Renier,
 
 We're currently developing a JavaScript API for Nova, Keystone, and
 Glance. To do so we also installed a CORS filter, developed by Adrian
 Smith, (with small changes) in these components.
 
 I can pass you the code and a short guideline to configure it if you want.
 
 Cheers,
 Javier.
 
 On 30 October 2012 17:43, Renier Morales reni...@us.ibm.com wrote:
 Hello,
 
 I'm wondering if someone has already created a nova paste filter/middleware
 for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to
 access the openstack api from another domain. Any pointers out there?
 
 Thanks,
 
-Renier
 
 
 
 ___
 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] Troubleshooting Swift 1.7.4 on mini servers

2012-10-30 Thread Rick Jones


On 10/29/2012 07:37 PM, Pete Zaitcev wrote:

On Mon, 29 Oct 2012 18:16:52 -0700
Nathan Trueblood nat...@truebloodllc.com wrote:


Definitely NOT a problem with the filesystem, but something is causing the
object-server to think there is a problem with the filesystem.


If you are willing to go all-out, you can probably catch the
error with strace, if it works on ARM.


Strace is your friend even if he is sometimes a bit on the chatty side. 
 It looks as though there is at least some support for ARM if 
http://packages.debian.org/search?keywords=strace is any indication.


rick jones


___
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] Trouble accessing list of servers via APi on arm.trystack.org

2012-10-30 Thread Zepp Warlock

Hello,

I could successfully log into the UI at http://arm.trystack.org/nova/

I also can get auth token by executing: curl -k -X 'POST' 
-v http://arm.trystack.org:5000/v2.0/tokens -d 
'{auth:{passwordCredentials:{username: user981443, password:***}, 
tenantId:}}' -H 'Content-type: application/json'

One of the issues is that I can't access any other APIs but 'tenants'
so 
curl -H 
X-Auth-Token:3954c19d157a446aa87d52cb674b5b6e http://arm.trystack.org:5000/v2.0/tenants
works fine but 
curl -H 
X-Auth-Token:3954c19d157a446aa87d52cb674b5b6e http://arm.trystack.org:5000/v2.0/servers

does not (I get 404 HTTP status code).

Am I calling a wrong API?

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] Nova middleware for enabling CORS?

2012-10-30 Thread Renier Morales

On Oct 30, 2012, at 1:08 PM, David Kranz wrote:

 On 10/30/2012 12:43 PM, Renier Morales wrote:
 Hello,
 
 I'm wondering if someone has already created a nova paste filter/middleware 
 for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to 
 access the openstack api from another domain. Any pointers out there?
 
 Thanks,
 
 -Renier
 
 
 This https://review.openstack.org/#/c/6909/ was an attempt to add such 
 middleware to swift. It is
 generic CORS support but seems
 to have been rejected in favor of putting CORS support in swift directly and 
 checked in last week:
 https://github.com/openstack/swift/commit/74b27d504d310c70533175759923c21df158daf9

Question for the list: this supports CORS in Swift. Should other services 
(nova, keystone, glance) do the same kind of intrinsic CORS enablement?
It's surprising that something like CORS, if done, would not be done in a more 
generic plug-in friendly that you could use across all services.

-Renier

___
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 middleware for enabling CORS?

2012-10-30 Thread heckj

Keystone doesn't (yet) support CORS  - there's an open blueprint for it, but no 
work has been applied there as yet

-joe

On Oct 30, 2012, at 10:57 AM, Renier Morales reni...@us.ibm.com wrote:
 On Oct 30, 2012, at 1:08 PM, David Kranz wrote:
 
 On 10/30/2012 12:43 PM, Renier Morales wrote:
 Hello,
 
 I'm wondering if someone has already created a nova paste filter/middleware 
 for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to 
 access the openstack api from another domain. Any pointers out there?
 
 Thanks,
 
-Renier
 
 
 This https://review.openstack.org/#/c/6909/ was an attempt to add such 
 middleware to swift. It is
 generic CORS support but seems
 to have been rejected in favor of putting CORS support in swift directly and 
 checked in last week:
 https://github.com/openstack/swift/commit/74b27d504d310c70533175759923c21df158daf9
 
 Question for the list: this supports CORS in Swift. Should other services 
 (nova, keystone, glance) do the same kind of intrinsic CORS enablement?
 It's surprising that something like CORS, if done, would not be done in a 
 more generic plug-in friendly that you could use across all services.
 
   -Renier
 
 ___
 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] Trouble accessing list of servers via APi on arm.trystack.org

2012-10-30 Thread Anne Gentle

Hi Zepp -

As far as I know, the ARM Trystack does not enable access to the
Compute API. So your results make sense - you can query the Identity
API but not the Compute API (nor any other OpenStack APIs).

Anne

On Tue, Oct 30, 2012 at 12:10 PM, Zepp Warlock zeppl...@yahoo.com wrote:
 Hello,

 I could successfully log into the UI at http://arm.trystack.org/nova/

 I also can get auth token by executing: curl -k -X 'POST' -v
 http://arm.trystack.org:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username: user981443,
 password:***}, tenantId:}}' -H 'Content-type: application/json'

 One of the issues is that I can't access any other APIs but 'tenants'
 so
 curl -H X-Auth-Token:3954c19d157a446aa87d52cb674b5b6e
 http://arm.trystack.org:5000/v2.0/tenants
 works fine but
 curl -H X-Auth-Token:3954c19d157a446aa87d52cb674b5b6e
 http://arm.trystack.org:5000/v2.0/servers
 does not (I get 404 HTTP status code).

 Am I calling a wrong API?

 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


___
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] Troubleshooting Swift 1.7.4 on mini servers

2012-10-30 Thread Nathan Trueblood

No disk errors in the kern.log.   The filesystem is fine.   I really think
this will turn out to be a bug or a timing (slowness) issue.

I will try some of the other recent suggestions, and failing those try to
track this down with strace.

Thx.

On Mon, Oct 29, 2012 at 7:02 PM, Alex Yang alex890...@gmail.com wrote:

 There are any error about disk in the kern.log?


 2012/10/30 Nathan Trueblood nat...@truebloodllc.com

 Still no further clues.   I re-created all the volumes I'm using for
 Swift.  Plenty of Inodes free:

  lab@data02:~$ df -i
 FilesystemInodes IUsed IFree IUse% Mounted on
 /dev/sda2   12214272 39290  121749821% /
 none  107979   4821074971% /dev
 none  107979   2681077111% /run
 none  107979 21079771% /run/lock
 none  107979 11079781% /run/shm
 /dev/sda1  4915223 491291% /boot
 /dev/sda4  13404640037 1340463631% /srv/node/sda4

 I successfully upload a small object to container cont1, then cont2.
 When I upload to cont3, I see the following in the object-server log
 (data02)

 This seems to be the problematic sequence:

 Data02 has ip 192.168.1.202
 Data03 has ip 192.168.1.203

 1. First the account server reports an HTTP 201 on the container from a
 different object server in a different zone.
 2. Then the object server reports a 404 trying to HEAD the new object.
 3. Then the object server reports a 507 trying to PUT the new object.

 From this point the operation eventually fails and the proxy reports a
 503.

 Oct 29 17:58:20 data02 account-server 192.168.1.203 - -
 [30/Oct/2012:00:58:20 +] PUT /sda4/116021/AUTH_system/cont3 201 -
 tx5a3ca6c845af41928e0ba6b7bc58d2da - - 0.0082 
 Oct 29 17:58:20 data02 object-server 192.168.1.111 - -
 [30/Oct/2012:00:58:20 +] HEAD
 /sda4/257613/AUTH_system/cont3/home/lab/bigfile3 404 - -
 tx5f21503ff12e45e39a80eb52f6757261 - 0.0011
 Oct 29 17:58:20 data02 object-server 192.168.1.111 - -
 [30/Oct/2012:00:58:20 +] PUT
 /sda4/257613/AUTH_system/cont3/home/lab/bigfile3 507 - -
 tx425494dc372740e28d043a07d3a08b9a - 0.0031

 In an earlier, successful transaction I noticed that between Steps 1 and
 2 above, there is a response from the container-server:

 Oct 29 17:57:59 data02 account-server 192.168.1.204 - -
 [30/Oct/2012:00:57:59 +] PUT /sda4/116021/AUTH_system/cont2 201 -
 txb10d75886bf14e4eba14fcc52d81c5d9 - - 0.0182 
 Oct 29 17:57:59 data02 container-server 192.168.1.111 - -
 [30/Oct/2012:00:57:59 +] PUT /sda4/122355/AUTH_system/cont2 201 -
 txb10d75886bf14e4eba14fcc52d81c5d9 - - 0.1554
 Oct 29 17:57:59 data02 object-server 192.168.1.111 - -
 [30/Oct/2012:00:57:59 +] HEAD
 /sda4/226151/AUTH_system/cont2/home/lab/bigfile3 404 - -
 tx1c514850530849d1bfbfa716d9039b87 - 0.0012
 Oct 29 17:57:59 data02 container-server 192.168.1.204 - -
 [30/Oct/2012:00:57:59 +] PUT
 /sda4/122355/AUTH_system/cont2/home/lab/bigfile3 201 -
 tx8130af5cae484e5f9c5a25541d1c87aa - - 0.0041
 Oct 29 17:57:59 data02 object-server 192.168.1.111 - -
 [30/Oct/2012:00:57:59 +] PUT
 /sda4/226151/AUTH_system/cont2/home/lab/bigfile3 201 - -
 tx8130af5cae484e5f9c5a25541d1c87aa - 0.1716


 So maybe the container server is failing to create the new container?
 Maybe a bug in auto-create of containers?

 Definitely NOT a problem with the filesystem, but something is causing
 the object-server to think there is a problem with the filesystem.

 I suspect a bug in one of the underlying libraries.

 Any further suggestions on how to troubleshoot?

 Thanks.   When I finally find the solution, I'll post my results.

 -N

 On Fri, Oct 26, 2012 at 11:21 PM, John Dickinson m...@not.mn wrote:

 A 507 is returned by the object servers in 2 situations: 1) the drives
 are full or 2) the drives have been unmounted because of disk error.

 It's highly likely that you simply have full drives. Remember that the
 usable space in your cluster is 1/N where N = replica count. As an example,
 with 3 replicas and 5 nodes with a single 1TB drive each, you only have
 about 1.6TB available for data.

 As Pete suggested in his response, how big are your drives, and what
 does `df` tell you?

 --John


 On Oct 26, 2012, at 5:26 PM, Nathan Trueblood nat...@truebloodllc.com
 wrote:

  Hey folks-
 
  I'm trying to figure out what's going wrong with my Swift deployment
 on a small cluster of mini servers.   I have a small test cluster (5
 storage nodes, 1 proxy) of mini-servers that are ARM-based.   The proxy is
 a regular, Intel-based server with plenty of RAM.   The
 object/account/container servers are relatively small, with 2GB of RAM per
 node.
 
  Everything starts up fine, but now I'm trying to troubleshoot a
 strange problem.   After I successfully upload a few test files, it seems
 like the storage system stops responding and the proxy gives me a 503 error.
 
  Here's the test sequence I run on my proxy:
 
  lab@proxy01:~/bin$ ./swiftcl.sh stat

Re: [Openstack] Nova middleware for enabling CORS?

2012-10-30 Thread John Dickinson

Since the CORS support in Swift allows the preflight OPTIONS response to be 
different on a per-container basis (which is correct in a multi-tenant system), 
the CORS support was added directly into Swift's proxy server rather than as 
middleware. In order to fulfill the OPTIONS request, container information 
needs to be read from the system, and the proxy server already has this 
information (probably in cache). Implementing the CORS support as middleware 
would require duplicating much of the code and framework that already exists in 
Swift's proxy server. CORS support in Swift was correctly implemented.

--John




On Oct 30, 2012, at 10:57 AM, Renier Morales reni...@us.ibm.com wrote:

 On Oct 30, 2012, at 1:08 PM, David Kranz wrote:
 
 On 10/30/2012 12:43 PM, Renier Morales wrote:
 Hello,
 
 I'm wondering if someone has already created a nova paste filter/middleware 
 for enabling Cross-Origin Resource Sharing (CORS), allowing a web page to 
 access the openstack api from another domain. Any pointers out there?
 
 Thanks,
 
-Renier
 
 
 This https://review.openstack.org/#/c/6909/ was an attempt to add such 
 middleware to swift. It is
 generic CORS support but seems
 to have been rejected in favor of putting CORS support in swift directly and 
 checked in last week:
 https://github.com/openstack/swift/commit/74b27d504d310c70533175759923c21df158daf9
 
 Question for the list: this supports CORS in Swift. Should other services 
 (nova, keystone, glance) do the same kind of intrinsic CORS enablement?
 It's surprising that something like CORS, if done, would not be done in a 
 more generic plug-in friendly that you could use across all services.
 
   -Renier
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



smime.p7s
Description: S/MIME cryptographic signature
___
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] Troubleshooting Swift 1.7.4 on mini servers

2012-10-30 Thread Nathan Trueblood

The filesystem is XFS, and I used the recommended mkfs and mount options
for Swift.

The file size seems to have no bearing on the issue, although I haven't
tried really tiny files.   Bigfile3 is only 200K.

I'll try disabling fallocate...

On Mon, Oct 29, 2012 at 7:37 PM, Pete Zaitcev zait...@redhat.com wrote:

 On Mon, 29 Oct 2012 18:16:52 -0700
 Nathan Trueblood nat...@truebloodllc.com wrote:

  Definitely NOT a problem with the filesystem, but something is causing
 the
  object-server to think there is a problem with the filesystem.

 If you are willing to go all-out, you can probably catch the
 error with strace, if it works on ARM. Failing that, find all places
 where 507 is generated and see if any exceptions are caught, by
 modifying the source, I'm afraid to say.

  I suspect a bug in one of the underlying libraries.

 That's a possibility. Or, it could be a kernel bug. You are using XFS,
 right? If it were something other than XFS or ext4, I would suspect
 ARM blowing over the 2GB barrier somewhere, since your object is
 called bigfile3. As it is, you have little option than to divide
 the layers until you identify the one that's broken.

 BTW, make sure to disable the fallocate, since we're at it.

 -- Pete

___
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] Domain Name Spaces

2012-10-30 Thread Dolph Mathews

+1; I think that's a great overview of where we're starting with domains in
Grizzly / identity api v3.

However, where we want to take domains in Grizzly+1 / identity-api v3.1 is
certainly ripe for discussion.

-Dolph


On Tue, Oct 30, 2012 at 10:19 AM, Yee, Guang guang@hp.com wrote:

 I agree with Adam.

 ** **

 +1 on Default Domain.

 ** **

 When we first introduced the Keystone Domains BP, things such as
 usability, flexibility, consistency, and backward compatibility played a
 critical role in our design. Domains are basically containers for users
 and projects (formerly tenants) for administrative purposes and are not
 visible to public/service APIs. Therefore, other OS services need not be
 domain-aware. 

 ** **

 Domains does not affect (public) API backward compatibility, as far as OS
 services are concerned. Therefore, the globally uniqueness requirement for
 users and projects remains.

 ** **

 If you have no need for domains, you don’t have to change anything.
 Default Domain is invisible to the V2 APIs.

 ** **

 If you are using domains and your user ID/names are globally unique, you
 don’t have to change anything.

 ** **

 If you are using domains and are integrating with an existing identity
 management system backend such as Active Directory, you can still achieve
 globally uniqueness by having domain name appended to username (i.e.
 jdoe@acme), or simply using user email as user name for authentication.
 And I am sure there are other solutions ways as well.

 ** **

 If you have a use case that has not been covered by the above, please let
 us know. Or please feel free to join us on the weekly Keystone meeting.***
 *

 ** **

 ** **

 Guang

 ** **

 ** **

 ** **

 *From:* openstack-bounces+guang.yee=hp@lists.launchpad.net [mailto:
 openstack-bounces+guang.yee=hp@lists.launchpad.net] *On Behalf Of *Adam
 Young
 *Sent:* Tuesday, October 30, 2012 6:34 AM
 *To:* openstack@lists.launchpad.net

 *Subject:* Re: [Openstack] [keystone] Domain Name Spaces

 ** **

 On 10/30/2012 04:00 AM, Henry Nash wrote:

 Gabriel, 

 ** **

 So I think you are right to ask that this is made clear and concrete -
 I'll work with the core contributors of Keystone to make it so.

 ** **

 To your specific point:

 - Let's call the initial Domain, the Global Domain, rather than the
 default domain

 No.  It is default.  It is not global.  The other domains do not nest
 inside this domain.  Calling it the Global domain is confusing.  I would
 accept: unnamed domain, or implicit domain,  but don't think either of
 those are an improvement to default.


 

 - If the Cloud Provider doesn't explicitly create any domains, then
 everything exists in the Global Domain.  There is no need to specify a
 domain in any calls, since everything will default to the Global domain.
  The v2 API will work just fine (which knows nothing about domains)

 That is correct

 

 - If they do create some domains, then they indicate (on creation) whether
 each of these *share* the namespace of the Global domain, or have their
 own *private* namespace.  

 No.  Domain are non-overlapping sets.

 

 - If all of these new domains were specified as *shared* then all user
 and tenant names are still globally unique.  A caller still does not
 technically need to specify a domain, although scoping things down to a
 domain (or of course project) is likely for most operations (just like it
 is today)

 I fail to see the benefit.

 

 - If, however, some of these new domains were specified as *private* then
 any users who are part of a private domain must specify the domain in order
 to authenticate.  By design, authentication will fail if they don't specify
 a domain (since you won't exist in the global domain).  Once a user in a
 private domain is authenticated, they are scoped to that domain.
 [implementation: we need to work out whether the domainID is encoded in the
 token - this is my assumption since this means the Domain Name/ID is NOT
 required for subsequent requestsand validation, by Keystone, can still
 be achieved ]

 We are reimplementing tokens/projects here.

 

 - It is perfectly possible (but of course up to the Cloud Provider) to
 support a mixture of *shared* and *private* domains (representing
 different customer types)but the point being that the Cloud Provider
 will tell their customers how they should access they system (i.e. provide
 them with any domain specification that may or may not be required).


 I think that this complicates things.  I would instead recommend that a
 provider either go with a single domain or explicit domaiuns, as mixing the
 two is wierd, but some installations will need to make their existing
 deployments work.

 I like the idea that the domain will be implicit from the hostname of the
 web front end, and also possibly of a Keystone endpoint.  This can be done
 with vhosts for

Re: [Openstack] Troubleshooting Swift 1.7.4 on mini servers

2012-10-30 Thread Pete Zaitcev

On Tue, 30 Oct 2012 11:07:55 -0700
Nathan Trueblood nat...@truebloodllc.com wrote:

 The file size seems to have no bearing on the issue, although I haven't
 tried really tiny files.   Bigfile3 is only 200K.

Okay. BTW, do not forget to use curl and issue the same PUT that proxy does,
see if it throws 507 repeateably. That could shortcut some of the testing.

-- Pete

___
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] sample_data.sh script to configure keystone

2012-10-30 Thread Ahmed Al-Mehdi

Hello,

The latest version of the OpenStack Install guide (Oct 10, 2012) mentions the 
bash script sample_data.sh to configure keystone.  I find such a script (and 
the python script mentioned in earlier versions of the doc) very helpful, 
especially for someone who understands the individual manual commands, but 
would much prefer a script.  However, the bash script does not perform the same 
manual steps mentioned in the manual.  Is there any plans to update the bash 
script?

Regards,
Ahmed.

___
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] sample_data.sh script to configure keystone

2012-10-30 Thread heckj

Ahmed,

We'd welcome an update to the script - some have talked about variations they 
have that use YAML, etc. As long as it's simple, and can be used from devstack 
to do a holistic test and verification, we'll happily take patches to the 
script in Keystone. Please suggest them using the gerrit/code review process!

-joe


On Oct 30, 2012, at 11:52 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:
 Hello,
 
 The latest version of the OpenStack Install guide (Oct 10, 2012) mentions the 
 bash script sample_data.sh to configure keystone.  I find such a script 
 (and the python script mentioned in earlier versions of the doc) very 
 helpful, especially for someone who understands the individual manual 
 commands, but would much prefer a script.  However, the bash script does not 
 perform the same manual steps mentioned in the manual.  Is there any plans to 
 update the bash script?
 
 Regards,
 Ahmed.
 
 ___
 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] sample_data.sh script to configure keystone

2012-10-30 Thread Ahmed Al-Mehdi

Joe,

Once I get familiar with using devstack, I will recommend some update to the 
bash script.  It would be really nice/helpful if the script mimicked the manual 
steps at the least, and as you mentioned, can be used from devstack.  Currently 
the install manual has three sections to configure keystone – manual steps, 
bash script (sample_data.sh), and manual steps mentioned in Appendix B, which 
are all different.

Regards,
Ahmed.


From: heckj he...@mac.commailto:he...@mac.com
Date: Tuesday, October 30, 2012 12:19 PM
To: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] sample_data.sh script to configure keystone

Ahmed,

We'd welcome an update to the script - some have talked about variations they 
have that use YAML, etc. As long as it's simple, and can be used from devstack 
to do a holistic test and verification, we'll happily take patches to the 
script in Keystone. Please suggest them using the gerrit/code review process!

-joe


On Oct 30, 2012, at 11:52 AM, Ahmed Al-Mehdi 
ah...@coraid.commailto:ah...@coraid.com wrote:
Hello,

The latest version of the OpenStack Install guide (Oct 10, 2012) mentions the 
bash script sample_data.sh to configure keystone.  I find such a script (and 
the python script mentioned in earlier versions of the doc) very helpful, 
especially for someone who understands the individual manual commands, but 
would much prefer a script.  However, the bash script does not perform the same 
manual steps mentioned in the manual.  Is there any plans to update the bash 
script?

Regards,
Ahmed.

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

___
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] Troubleshooting Swift 1.7.4 on mini servers

2012-10-30 Thread Nathan Trueblood

Ok, if I was giving out t-shirts for finding this issue then the prize
would go to Pete.   Thank you

Disabling fallocate did the trick.   I was slowly working my way through
all the object-server config options and hadn't gotten to that one yet.
Turning features on and off by brute force is admittedly lame, but
sometimes that's all you have.

I also turned off all the other things I was doing to try to slow down the
mini-servers, but disabling fallocate was all that was necessary.   Here is
my config:

[DEFAULT]
bind_ip = 192.168.1.202
workers = 1
disable_fallocate = true

[pipeline:main]
pipeline = object-server

[app:object-server]
use = egg:swift#object

[object-replicator]

[object-updater]

[object-auditor]

A few more details...

My servers are running Ubuntu 12.04 LTS.   A straight-up apt-get of all the
pre-requisites did NOT produce a working Swift deployment on Arm.
Although  all the dependencies would deploy fine and the Swift services
would start up, the proxy-server could not communicate with the storage
nodes.

So I also had to get older, Armel versions of the python-greenlet and
python-eventlet.

https://launchpad.net/ubuntu/precise/armel/python-greenlet/0.3.1-1ubuntu5.1
https://launchpad.net/ubuntu/precise/armel/python-eventlet/0.9.16-1ubuntu4.1

Once I deployed those older libraries for Armel, then my Swift cluster
worked (except for the fallocate issue).

Thanks for everyone's help.

-N

On Tue, Oct 30, 2012 at 11:07 AM, Nathan Trueblood
nat...@truebloodllc.comwrote:

 The filesystem is XFS, and I used the recommended mkfs and mount options
 for Swift.

 The file size seems to have no bearing on the issue, although I haven't
 tried really tiny files.   Bigfile3 is only 200K.

 I'll try disabling fallocate...


 On Mon, Oct 29, 2012 at 7:37 PM, Pete Zaitcev zait...@redhat.com wrote:

 On Mon, 29 Oct 2012 18:16:52 -0700
 Nathan Trueblood nat...@truebloodllc.com wrote:

  Definitely NOT a problem with the filesystem, but something is causing
 the
  object-server to think there is a problem with the filesystem.

 If you are willing to go all-out, you can probably catch the
 error with strace, if it works on ARM. Failing that, find all places
 where 507 is generated and see if any exceptions are caught, by
 modifying the source, I'm afraid to say.

  I suspect a bug in one of the underlying libraries.

 That's a possibility. Or, it could be a kernel bug. You are using XFS,
 right? If it were something other than XFS or ext4, I would suspect
 ARM blowing over the 2GB barrier somewhere, since your object is
 called bigfile3. As it is, you have little option than to divide
 the layers until you identify the one that's broken.

 BTW, make sure to disable the fallocate, since we're at it.

 -- Pete



___
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] Scheduler issues in folsom

2012-10-30 Thread Vishvananda Ishaya

The retry scheduler is NOT meant to be a workaround for this. It sounds like
the ram filter is not working properly somehow. Have you changed the setting
for ram_allocation_ratio? It defaults to 1.5 allowing overallocation, but in
your case you may want 1.0.

I would be using the following two config options to achieve what you want:
compute_fill_first_cost_fn_weight=1.0
ram_allocation_ratio=1.0

If you are using the settings above, then the scheduler should be using up the
resources on the node it schedules to until it fills up the available ram and
then moving on to the next node. If this is not occurring then you have 
uncovered
some sort of bug.

Vish
On Oct 30, 2012, at 9:21 AM, Jonathan Proulx j...@csail.mit.edu wrote:

 Hi All,
 
 I'm having what I consider serious issues with teh scheduler in
 Folsom.  It seems to relate to the introdution of threading in the
 scheduler.
 
 For a number of local reason we prefer to have instances start on the
 compute node with the least amount of free RAM that is still enough to
 satisfy the request which is the reverse of the default policy of
 scheduling on the system with the most free RAM.  I'm fairly certain
 the smae behavior would be seen with that policy as well, and any
 other policy that results in a best choice for scheduling the next
 instance. 
 
 We have work loads that start hundreds of instances or the same image
 and there are plans on scaling this to thousands.  What I'm seeing is
 somehting like this:
 
 * user submits API request for 300 instances
 * scheduler puts them all on one node
 * retry schedule kicks in at some point for the 276 that don't fit
 * those 276 are all scheduled on the next best node
 * retry cycle repeats with the 252 that don't fit there
 
 I'm not clear exactly where the RetryScheduler in serts itself (I
 should probably read it) but the first compute node is very overloaded
 handling start up request which results in a fair number of instances
 entering ERROR state rather than rescheduling (so not all 276
 actually make it to the next round) and the whole process it painfully
 slow.  In the end we are lucky to see 50% of the requested instances
 actually make it into Active state (and then only becasue we increased
 scheduler_max_attempts).
 
 Is that really how it's supposed to work?  With the introduction of
 the RetryScheduler as a fix for the scheduling race condition I think
 it is, but it is a pretty bad solution for me, unless I'm missing
 something, am I?  wouln't be the first time... 
 
 For now I'm working around this by using the ChanceScheduler
 (compute_scheduler_driver=nova.scheduler.chance.ChanceScheduler) so
 the scheduler threads don't pick a best node.  This is orders of
 magnitude faster and consistantly successful in my tests.  It is not
 ideal for us as we have a small minority of ciompute nodes with twice
 the memory capacity of our standard nodes and would prefer to keep
 those available for some of our extra large memory flavors and we'd
 also liek to minimize memory fragmentation on the standard sized nodes
 for similar reasons.
 
 -Jon
 
 ___
 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] Openstack

2012-10-30 Thread Joe Warren-Meeks

Hi guys,

Can someone point me in the direction of a guide to get Openstack
working with two nodes, one as controller and the second as a compute
node, please?

I've tried the CSS corp PDF and the hastexo one, but I can't get them
to work. All I get are virts booting straight into error.

I want a controller node to run all keystone, glance and nova db
functions then a compute node to run the virtuals with vlans bridging
using 8021q. I've tried so many permutations and configs. I can't
believe I'm doing something that outrageous, but I've hacked away at
this for hours and hours with no joy.

Is there any chance that nova-compute gets confuse by seeing
lost+found in the /var/lib/nova/instances directory? I have that
mounted as iscsi.

Cheers..

 -- joe.

___
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

2012-10-30 Thread Curtis C.

On Tue, Oct 30, 2012 at 4:56 PM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
 Hi guys,

 Can someone point me in the direction of a guide to get Openstack
 working with two nodes, one as controller and the second as a compute
 node, please?

 I've tried the CSS corp PDF and the hastexo one, but I can't get them
 to work. All I get are virts booting straight into error.

 I want a controller node to run all keystone, glance and nova db
 functions then a compute node to run the virtuals with vlans bridging
 using 8021q. I've tried so many permutations and configs. I can't
 believe I'm doing something that outrageous, but I've hacked away at
 this for hours and hours with no joy.

Is virtualization turned on in the BIOS?

I think nova show ID will show an error message if the instance fails to boot.

Thanks,
Curtis.


 Is there any chance that nova-compute gets confuse by seeing
 lost+found in the /var/lib/nova/instances directory? I have that
 mounted as iscsi.

 Cheers..

  -- joe.

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



-- 
Twitter: @serverascode
Blog: serverascode.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] about nova-schedule queues

2012-10-30 Thread 韦远科

thanks gong and sandy for your brief and clear explanation.  really helps

-
韦远科
中国科学院 计算机网络信息中心
北京市海淀区中关村南四街四号 349信箱(100190)

Yuanke Wei (Wei)
Computer Network Information Center,Chinese Academy of Sciences
4 Zhongguancun Nansijie, Haidian District, Beijing 100190, China
P.O. Box 349
gtalk: weiyuanke...@gmail.com
msn: weiyuanke...@hotmail.com



On Tue, Oct 30, 2012 at 7:43 PM, gong yong sheng gong...@linux.vnet.ibm.com
 wrote:

  Following is my understanding:
 usage:
 scheduler queue is used for compute api server. For example of nova boot,
 API server will send a msg to scheduler queue for a booting
 scheduler_*fanout_ is used for services to report service capability.
 For example, nova compute *will use scheduler_fanout to publish its
 capabilities.

 scheduler.{hostname} seemingly is not used now.
 we can deploy many schedulers into a Openstack cloud. All the schedulers
 will listen on scheduler msg queue. AMQP server (rabbitmq) will adopt round
 robin way to
 dispatch the msg to these schedulers. But since the capabilities are fan
 outed, all the schedulers can receive these capabilities.


 On 10/30/2012 06:55 PM, 韦远科 wrote:

 hi all,

  I read into the source code for nova-scheduler and found there actually
 exists three msg queues, like
 scheduler
 scheduler.node70
 scheduler_*fanout_bd738fedcdf344d9bb3cb580657f54e0*.

  what's the functions for each queue and are there connections??


  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



___
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] Scheduler issues in folsom

2012-10-30 Thread Huang Zhiteng

On Wed, Oct 31, 2012 at 6:55 AM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
 The retry scheduler is NOT meant to be a workaround for this. It sounds like
 the ram filter is not working properly somehow. Have you changed the setting
 for ram_allocation_ratio? It defaults to 1.5 allowing overallocation, but in
 your case you may want 1.0.

 I would be using the following two config options to achieve what you want:
 compute_fill_first_cost_fn_weight=1.0
 ram_allocation_ratio=1.0
I'd suggest the same ratio too.  But besides memory overcommitment, I
suspect this issue is also related to how KVM do memory allocation (it
doesn't do actual allocation of the entire memory for guest when
booting). I've seen compute node reported more memory than it should
have (e.g. 4G node has two 1GB instances running but still report 3GB
free memory) because libvirt driver calculates free memory simply
based on /proc/meminfo, which doesn't reflect how many memory guests
are intended to use.

 If you are using the settings above, then the scheduler should be using up the
 resources on the node it schedules to until it fills up the available ram and
 then moving on to the next node. If this is not occurring then you have 
 uncovered
 some sort of bug.

 Vish
 On Oct 30, 2012, at 9:21 AM, Jonathan Proulx j...@csail.mit.edu wrote:

 Hi All,

 I'm having what I consider serious issues with teh scheduler in
 Folsom.  It seems to relate to the introdution of threading in the
 scheduler.

 For a number of local reason we prefer to have instances start on the
 compute node with the least amount of free RAM that is still enough to
 satisfy the request which is the reverse of the default policy of
 scheduling on the system with the most free RAM.  I'm fairly certain
 the smae behavior would be seen with that policy as well, and any
 other policy that results in a best choice for scheduling the next
 instance.

 We have work loads that start hundreds of instances or the same image
 and there are plans on scaling this to thousands.  What I'm seeing is
 somehting like this:

 * user submits API request for 300 instances
 * scheduler puts them all on one node
 * retry schedule kicks in at some point for the 276 that don't fit
 * those 276 are all scheduled on the next best node
 * retry cycle repeats with the 252 that don't fit there

 I'm not clear exactly where the RetryScheduler in serts itself (I
 should probably read it) but the first compute node is very overloaded
 handling start up request which results in a fair number of instances
 entering ERROR state rather than rescheduling (so not all 276
 actually make it to the next round) and the whole process it painfully
 slow.  In the end we are lucky to see 50% of the requested instances
 actually make it into Active state (and then only becasue we increased
 scheduler_max_attempts).

 Is that really how it's supposed to work?  With the introduction of
 the RetryScheduler as a fix for the scheduling race condition I think
 it is, but it is a pretty bad solution for me, unless I'm missing
 something, am I?  wouln't be the first time...

 For now I'm working around this by using the ChanceScheduler
 (compute_scheduler_driver=nova.scheduler.chance.ChanceScheduler) so
 the scheduler threads don't pick a best node.  This is orders of
 magnitude faster and consistantly successful in my tests.  It is not
 ideal for us as we have a small minority of ciompute nodes with twice
 the memory capacity of our standard nodes and would prefer to keep
 those available for some of our extra large memory flavors and we'd
 also liek to minimize memory fragmentation on the standard sized nodes
 for similar reasons.

 -Jon

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


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



-- 
Regards
Huang Zhiteng

___
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] Scheduler issues in folsom

2012-10-30 Thread Vishvananda Ishaya


On Oct 30, 2012, at 7:01 PM, Huang Zhiteng winsto...@gmail.com wrote:

 I'd suggest the same ratio too.  But besides memory overcommitment, I
 suspect this issue is also related to how KVM do memory allocation (it
 doesn't do actual allocation of the entire memory for guest when
 booting). I've seen compute node reported more memory than it should
 have (e.g. 4G node has two 1GB instances running but still report 3GB
 free memory) because libvirt driver calculates free memory simply
 based on /proc/meminfo, which doesn't reflect how many memory guests
 are intended to use.

Ah interesting, if this is true then this is a bug we should try to fix.
I was under the impression that it allocated all of the memory unless
you were using virtio_balloon, but I haven't verified.

Vish

___
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] Scheduler issues in folsom

2012-10-30 Thread Huang Zhiteng

On Wed, Oct 31, 2012 at 10:07 AM, Vishvananda Ishaya
vishvana...@gmail.com wrote:

 On Oct 30, 2012, at 7:01 PM, Huang Zhiteng winsto...@gmail.com wrote:

 I'd suggest the same ratio too.  But besides memory overcommitment, I
 suspect this issue is also related to how KVM do memory allocation (it
 doesn't do actual allocation of the entire memory for guest when
 booting). I've seen compute node reported more memory than it should
 have (e.g. 4G node has two 1GB instances running but still report 3GB
 free memory) because libvirt driver calculates free memory simply
 based on /proc/meminfo, which doesn't reflect how many memory guests
 are intended to use.

 Ah interesting, if this is true then this is a bug we should try to fix.
 I was under the impression that it allocated all of the memory unless
 you were using virtio_balloon, but I haven't verified.
I'm pretty sure about this.  Can anyone from RedHat confirm this is
how KVM works?

 Vish



-- 
Regards
Huang Zhiteng

___
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 :: Folsom] Quantum Network Node setup

2012-10-30 Thread balaji patnala

Hi Yong,

Thanks for information.
I think you mean to say that these Quantum Network Node is not per Tenant
basis and it can serve all the Tenants of DC setup.

Just want to understand what will be the advantages we are thinking of by
doing so.

Regards,
Balaji
On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com
 wrote:

  Hi,
 In fact, we can split Quantum network Node into two categories:
 one is for dhcp, which install ovs agent and dhcp agent. We can have one
 such kind of node
 one is for l3 agent, we can deal with one external network on one l3
 agent. We can have many nodes of this kind.

 Regards,

 Yong Sheng Gong

 On 10/30/2012 02:27 PM, balaji patnala wrote:

 Hi Salvatore,

 Just want to understand more on Network Node in the below given app_demo
 page.

 As i see in the setup, it looks like there will be one Quantum Network
 Node for one Data centre setup. Please correct me if my assumptions are
 wrong.

 This Quantum Network Node will have all the virtual routers, gateway which
 can be created with quantum-l3-agent plugin.

 Also my assumption is that this quantum Network Node will serve all the
 Tenant virtual gateways and routers created using quantum.

 Please give us some more information on this to understand the setup.

 Also do we have any specific reason for having quantum Network Node
 instead of keeping these plugin on the Controller Node similar to earlier
 release like Essex.

 Thanks in advance.

 Regards,
 Balaji

 On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote:

 Hi Trinath,

 Even if is perfectly reasonable to run the DHCP/L3 agents in the
 controller node, the advice we give in the administration guide is slightly
 different.
 As suggested in [1], the only Quantum component running on the controller
 node should be the API server.
 The DHCP and L3 agents might run in a dedicated network node. Please
 note you will need also the L2 agent running on that node.

 Regards,
 Salvatore

 [1]
 http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html

  On 26 October 2012 10:50, Trinath Somanchi 
 trinath.soman...@gmail.comwrote:

  Hi Stackers-

 I have found many installation and configuration manuals for Openstack
 Folsom which state the installation and configuration of Quantum-DHCP-Agent
 in the Controller machine.

 But I have doubt here,

 Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute
 NODE rather than in the controller.

 How does the Installation and configuration change with this type of
 Installation?

 Please guide me on How to achieve the same.

 Thanking you

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


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



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




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



___
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-ubuntu-testing-notifications] Build Fixed: precise_folsom_keystone_stable #67

Title: precise_folsom_keystone_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_stable/67/Project:precise_folsom_keystone_stableDate of build:Tue, 30 Oct 2012 09:03:18 -0400Build duration:4 min 59 secBuild cause:Started by user Adam GandelmanBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFixed bug 1068851. Refreshed new crypto for the SSL tests.by gporraseditexamples/ssl/certs/keystone.pemeditexamples/ssl/private/keystonekey.pemaddexamples/ssl/gen_pki.sheditexamples/ssl/certs/ca.pemeditexamples/ssl/private/cakey.pemeditexamples/ssl/certs/middleware.pemreplacing PKI token detection from content length to content prefix. (bug 1060389)by heckjeditkeystone/service.pyeditkeystone/token/backends/sql.pyeditkeystone/middleware/auth_token.pyeditkeystone/common/cms.pyConsole Output[...truncated 5517 lines...]Checking signature on .changesGood signature on /tmp/tmp5tiU4x/keystone_2012.2.1+git201210300903~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp5tiU4x/keystone_2012.2.1+git201210300903~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading keystone_2012.2.1+git201210300903~precise-0ubuntu1.dsc: done.  Uploading keystone_2012.2.1+git201210300903~precise.orig.tar.gz: done.  Uploading keystone_2012.2.1+git201210300903~precise-0ubuntu1.debian.tar.gz: done.  Uploading keystone_2012.2.1+git201210300903~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'keystone_2012.2.1+git201210300903~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/k/keystone/keystone-doc_2012.2+git201209252030~precise-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/keystone_2012.2+git201209252030~precise-0ubuntu1_all.debdeleting and forgetting pool/main/k/keystone/python-keystone_2012.2+git201209252030~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/keystone/precise-folsom']Pushed up to revision 140.2 tags updated.INFO:root:Storing current commit for next build: 094c49424e72373b134384174749887e51fd847aINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-folsom-proposed /tmp/tmp5tiU4x/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmp5tiU4x/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-folsom --forcedch -b -D precise --newversion 2012.2.1+git201210300903~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [094c494] replacing PKI token detection from content length to content prefix. (bug 1060389)dch -a [3cd343b] Fixed bug 1068851. Refreshed new crypto for the SSL tests.dch -a [2f9807e] Set defaultbranch in .gitreview to stable/folsomdch -a [b0bbd8a] Bump next version to 2012.2.1dch -a [8154492] utf-8 encode user keys in memcache (bug 1056373)debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2.1+git201210300903~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A keystone_2012.2.1+git201210300903~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-stable-testing keystone_2012.2.1+git201210300903~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom keystone_2012.2.1+git201210300903~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/keystone/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_deploy #344

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/344/Project:precise_folsom_deployDate of build:Tue, 30 Oct 2012 09:08:01 -0400Build duration:18 secBuild cause:Started by user Adam GandelmanBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole OutputStarted by user Adam GandelmanBuilding on master in workspace /var/lib/jenkins/jobs/precise_folsom_deploy/workspaceNo emails were triggered.[workspace] $ /bin/bash -x /tmp/hudson3654476686199480878.sh+ export RELEASE=folsom+ RELEASE=folsom+ export DISTRO=precise+ DISTRO=precise+ /var/lib/jenkins/tools/juju-deployer/deployer.py -T -S -dDEBUG: Calling 'juju status'...DEBUG: Destroying service: mysqlDEBUG: Calling juju, attempt 1: juju destroy-service mysqlDEBUG: Cleaning cached charms from ZK.DEBUG: Removing charms set(['cs_3a_precise_2f_mysql-9'])DEBUG: Terminating machine: 32DEBUG: Calling juju, attempt 1: juju terminate-machine 32DEBUG: Terminating machine: 34DEBUG: Calling juju, attempt 1: juju terminate-machine 34DEBUG: Terminating machine: 35DEBUG: Calling juju, attempt 1: juju terminate-machine 35DEBUG: Terminating machine: 36DEBUG: Calling juju, attempt 1: juju terminate-machine 36DEBUG: Terminating machine: 33DEBUG: Calling juju, attempt 1: juju terminate-machine 33DEBUG: Terminating machine: 25DEBUG: Calling juju, attempt 1: juju terminate-machine 25DEBUG: Terminating machine: 26DEBUG: Calling juju, attempt 1: juju terminate-machine 26DEBUG: Terminating machine: 27DEBUG: Calling juju, attempt 1: juju terminate-machine 27DEBUG: Terminating machine: 28DEBUG: Calling juju, attempt 1: juju terminate-machine 28DEBUG: Terminating machine: 29DEBUG: Calling juju, attempt 1: juju terminate-machine 29DEBUG: Terminating machine: 30DEBUG: Calling juju, attempt 1: juju terminate-machine 30DEBUG: Terminating machine: 31DEBUG: Calling juju, attempt 1: juju terminate-machine 31- Destroying services- Destroying machines+ /var/lib/jenkins/tools/jenkins-scripts/flush_cached_charms.sh+ /var/lib/jenkins/tools/jenkins-scripts/set_deploy_release.sh precisesudo: cobbler: command not foundCurrent distro: sudo: cobbler: command not found+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #345

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/345/Project:precise_folsom_deployDate of build:Tue, 30 Oct 2012 09:10:00 -0400Build duration:1.3 secBuild cause:Started by user Adam GandelmanBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole OutputStarted by user Adam GandelmanBuilding on master in workspace /var/lib/jenkins/jobs/precise_folsom_deploy/workspaceNo emails were triggered.[workspace] $ /bin/bash -x /tmp/hudson3138613568076321521.sh+ export RELEASE=folsom+ RELEASE=folsom+ export DISTRO=precise+ DISTRO=precise+ /var/lib/jenkins/tools/juju-deployer/deployer.py -T -S -dDEBUG: Calling 'juju status'...DEBUG: No services destroy- Destroying machines+ /var/lib/jenkins/tools/jenkins-scripts/flush_cached_charms.sh+ /var/lib/jenkins/tools/jenkins-scripts/set_deploy_release.sh precisesudo: cobbler: command not foundCurrent distro: sudo: cobbler: command not found+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_essex_glance_stable #28

Title: precise_essex_glance_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_glance_stable/28/Project:precise_essex_glance_stableDate of build:Tue, 30 Oct 2012 09:01:58 -0400Build duration:15 minBuild cause:Started by user Adam GandelmanBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 4338 lines...]gpg: Signature made Tue Oct 30 09:03:28 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Tue Oct 30 09:03:28 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpPKao7D/glance_2012.1.3+git201210300902~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpPKao7D/glance_2012.1.3+git201210300902~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2012.1.3+git201210300902~precise-0ubuntu1.dsc: done.  Uploading glance_2012.1.3+git201210300902~precise.orig.tar.gz: done.  Uploading glance_2012.1.3+git201210300902~precise-0ubuntu1.debian.tar.gz: done.  Uploading glance_2012.1.3+git201210300902~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptExporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-client_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2012.1.3+git201208240612~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2012.1.3+git201208240612~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 165.INFO:root:Storing current commit for next build: 120fcf4a4ccecf70e1a9e859b2ad64df695a9929INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-essex-proposed /tmp/tmpPKao7D/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpPKao7D/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/precise-essex-stable --forcedch -b -D precise --newversion 2012.1.3+git201210300902~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2012.1.3+git201210300902~precise-0ubuntu1_source.changessbuild -d precise-essex -n -A glance_2012.1.3+git201210300902~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/essex-stable-testing glance_2012.1.3+git201210300902~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-essex glance_2012.1.3+git201210300902~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/precise-essex-stableEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #347