Re: [Openstack] Openstack grizzly rc1 packages availability for Debian

[Emilien Macchi]

Hi,

You can find more informations about the packages here :

http://qa.debian.org/developer.php?login=openstack-de...@lists.alioth.debian.org

And join us on #debian-openstack (OFTC) !


Regards,

Emilien Macchi

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

On 03/22/2013 02:03 PM, Mohammed Amine SAYA wrote:
 Hi All,
 
 I ran into quantum dhcp issue described in bug 1135948 and I also learned
 that it has been fixed in quantum grizzly-rc1. Does somebody know something
 about grizzly-rc1 package availability for DEBIAN ?
 
 Thanks for your help,
 Amine.
 
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 



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

Re: [Openstack] Horizon

[Emilien Macchi]

Hi Viktor,


* If you have used keystone-data.sh script, the password should be 
password.
* Horizon does not use novarc neither MySQL. It only uses OpenStack APIs.
* Django log files can by found on /var/log/apache2/error.log  access.log


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


- Original Message -

From: Viktor Viking viktor.viking...@gmail.com
To: openstack@lists.launchpad.net
Sent: Wednesday, February 6, 2013 1:47:02 PM
Subject: [Openstack] Horizon



Hi,


After a successful installation of Folsom, I'm trying to use Dashboard. I've 
had no success login in.


If I just type a random user/passwd string, I get a message: Invalid username 
or password.


If I type admin:secret (a correct user:password combination), the login page 
reloads and nothing happens.


Some info on my setup:


I followed this guide for Folsom installation:


http://docs.openstack.org/folsom/basic-install/content/basic-install-folsom.pdf



My novarc file:



export OS_TENANT_NAME=admin
export OS_USERNAME=admin
export OS_PASSWORD=secret
export OS_AUTH_URL= http://localhost:5000/v2.0/ 
export SERVICE_ENDPOINT= http://localhost:35357/v2.0 
export SERVICE_TOKEN=secret


Keystone.log doesn't show anything out of the ordinary.



mysql select id,name from user;
+--+-+
| id | name |
+--+-+
| 6294f0f5e16d49b9992c211e9cac6855 | admin |
| 88f6d25dec6f40f1a9cddf2b20aad4b2 | cinder |
| 4c0f5a439a3d44368e8d4af395049ff2 | demo |
| c7ee8554321d4fe2bba341a99ee98dc9 | glance |
| 520ddc424a30447aa47992400382a167 | nova |
| 6e44c5aa1edc4fe5919286ecdda196a0 | quantum |
| f4a54be5b3154f85bc4df89a61c5360d | swift |
| 6dfec4512b7f4eaa9dc214d7232244fd | viktor |
+--+-+



mysql select * from tenant;
+--+++
| id | name | extra |
+--+++
| 779c87a9c37f4f63b0fc0aab236a5e1e | demo | {enabled: true, description: 
null} |
| 8d4286a5249e43e9aa56864357737884 | invisible_to_admin | {enabled: true, 
description: null} |
| cf03bbe4daaf4579bd005a4e64da3334 | MYTENANT | {enabled: true, 
description: null} |
| f822dc409d684062b003ba99efa12672 | admin | {enabled: true, description: 
null} |
+--+++


I realize dashboard doesn't use a database anymore as it did in Essex. Is that 
right? BTW, where can I find django log files?


Any tips about what is going wrong?


Thank you,
Viktor
___
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] [Documentation] Installation and configuration for testing-sized systems

[Emilien Macchi]

Hi Stackers,


For your information, a new documentation is now available [1] :
Installation and configuration for testing-sized systems.
The purpose of this work is to explain how to install a 3 nodes
(controller + network + compute) setup from Ubuntu Packages (Folsom),
and understand how to configure services together.

Feel free to report any suggestion or bug [2].

This work replaces the Folsom Deployment Guide I
wrote 3 months ago [3], reviewed by many people in the Community.

[1] http://docs.openstack.org/folsom/basic-install/content/
[2] https://bugs.launchpad.net/openstack-manuals
[3] https://github.com/EmilienM/openstack-folsom-guide


Regards,

-- 
Emilien Macchi

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






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

Re: [Openstack] Windows 2012 Server

[Emilien Macchi]

Hi,

I've installed the Windows 2012 Datacenter Edition in our Testing Cloud
running Folsom and it's working very well : I can RDP the VM, and also
use VNC inside the dashboard.

I've created the image using VirtIO driver both for storage and network.
The Disk Format is RAW and the Container Format is OVF.
In my testing setup, I use FlatDHCP and the VM gets the network and can
ping outside. We use also KVM for the Hypervisor.


I confirm everything can work with Folsom packages.


Regards,


Emilien Macchi

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

On 12/18/2012 10:16 PM, Brian Haley wrote:
 On 12/18/2012 01:41 PM, Joe Warren-Meeks wrote:
 Hi guys,

 I've created a windows 2012 image and uploaded it ok. Pretty much following 
 this
 example:

 http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-a-windows-image.html

 When I go to launch an instance, it works ok and nova list and nova show look
 healthy.

 If I VNC to it as soon as it starts to boot, I get to see the BIOS and then 
 the
 new Windows logo, but then the screen goes black and nothing seems to happen.
 Sending ctrl-alt-del elicits no response and it doesn't look like the network
 has DHCP'ed either.

 Has anyone else seen this and if so, any idea what I can do to fix it?
 
 When you say it hasn't DHCP'ed, do you mean you never see the request from the
 VM on the bridge when you run tdpcump?
 
 -Brian
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 



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

Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !

[Emilien Macchi]

Hi,I suggest you reading my script [1] which helps to create virtual networking in Folsom with OVS Plugin for you use case.[1] https://github.com/EmilienM/openstack-folsom-guide/blob/master/scripts/quantum-networking.shRegards,Emilien Macchi// eNovance Inc.   http://enovance.com// ✉ emil...@enovance.com   ☎ +33 (0)1 49 70 99 80// 10 rue de la Victoire 75009 ParisDe: "Skible OpenStack" skible.openst...@gmail.comÀ: "gong yong sheng" gong...@linux.vnet.ibm.comCc: openstack@lists.launchpad.netEnvoyé: Lundi 12 Novembre 2012 06:12:15Objet: Re: [Openstack] how to configure l3_agent when you have Per-tenant Routers !




Thank you for responding back but i
  think when you configure the l3 agent to use one router the other
  tenant won't be able to connect to internet because their routers
  are not configured !
  i repeat : i wish to have a router for each of my tenants and they
  all connect to the internet
  Le 12/11/2012 01:31, gong yong sheng a écrit:



  There is a router_id in l3_agent.ini,
You can create a router for a tenant and then start a l3 agent
for it.
On 11/11/2012 01:34 AM, Skible OpenStack wrote:
  
  



  https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst
  
  i have set my namespace in l3 agent and dhcp agent to true.
  set external network id to my external network id in the l3
  agent file
  
  do i need to run multiple l3 agents to have the per tenant
  router usecase ?
  
  Le 10/11/2012 18:29, Razique Mahroua a écrit:



  Hey there,
  which guide did you followed ?
  
 Nuage  Co - Razique
  Mahroua
razique.mahr...@gmail.com
  
   


  Le 10 nov. 2012 à 17:57, Skible OpenStack skible.openst...@gmail.com


a écrit :
  
  Hello,

I am having trouble configuring my l3 agent when i have
a quantum router for each of my tenants. None of my VMs
seem to be internet accessible !
However, It seems that i can only use one router and set
the router_id in the l3_agent to allow VMs access to
internet !

please help

___
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/~openstackPost to   : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help  : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[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] Quantum OVS Agent as service

[Emilien Macchi]

Hi,

You are running a (very) old version of my guide.

Try to read it again or follow official documentation available.


Regards



Emilien Macchi

// eNovance Inc. http://enovance.com
// ✉ emil...@enovance.com
// 10 rue de la Victoire 75009 Paris

- Mail original -

De: Srikanth Kumar Lingala srikanthkumar.ling...@gmail.com
À: Dan Wendlandt d...@nicira.com
Cc: openstack@lists.launchpad.net
Envoyé: Jeudi 18 Octobre 2012 07:10:53
Objet: Re: [Openstack] Quantum OVS Agent as service

Hi Dan,
I am following Folsom Installation guide provided by Emilien Macchi. In that 
document it is mentioned to create a bridge 'br-int' attached to 'eth1' through 
ovs. And also it suggests to assign this ' br-int ' bridge as ' 
integration_bridge ' and ' br-eth1 ' as ' bridge_mappings ' in 
'/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini' like the following:



integration_bridge = br-int
bridge_mappings = default:br-eth1


Please clarify me, is it necessary to enable 'bridge_mappings' field.


Regards,
Srikanth.

On Wed, Oct 17, 2012 at 10:13 PM, Dan Wendlandt  d...@nicira.com  wrote:


It sounds like your config file is saying that you have an OVS bridge
named br-eth1, but it looks like you do not.

Did you intend to do this, or is this a config copied from somewhere else? 

If you actually intended to use VLANs that send traffic out eth1, you
can do the following:

# create bridge
ovs-vsctl add-br br-eth1

# add eth1 as a port on this bridge
ovs-vsctl add-port br-eth1 eth1

dan



On Wed, Oct 17, 2012 at 1:53 AM, Srikanth Kumar Lingala
 srikanthkumar.ling...@gmail.com  wrote:
 Hi all,
 If we run Quantum OVS Agent as a service ... 'service
 quantum-plugin-openvswitch-agent start', it is unable to start the agent. It
 is throwing the following error to '/var/log/quantum/agent-ovs.log'

 Stderr: 'Device br-eth1 does not exist.\n'
 2012-10-16 12:48:10 ERROR
 [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Bridge br-eth1 for 
 physical network default does not exist

 if we run the agent manually like the following command, it is able to
 start:

 /usr/bin/quantum-openvswitch-agent --
 --config-file=/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
 --log-file=/var/log/quantum/agent-ovs.log
 --config-file=/etc/quantum/quantum.conf

 Please suggest.
 --
 
 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




--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~




___
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] Creating networks with same subnet across Tenants

[Emilien Macchi]

Hi,

Please consider the limitations when using namespaces in Folsom release [1].


Regards,

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



Emilien Macchi

// eNovance Inc. http://enovance.com
// ✉ emil...@enovance.com
// 10 rue de la Victoire 75009 Paris

- Mail original -

De: gong yong sheng gong...@linux.vnet.ibm.com
À: Srikanth Kumar Lingala srikanthkumar.ling...@gmail.com
Cc: openstack-...@lists.openstack.org, openstack@lists.launchpad.net
Envoyé: Vendredi 12 Octobre 2012 16:05:06
Objet: Re: [Openstack] Creating networks with same subnet across Tenants


Try to define allow_overlapping_ips = True
On 10/12/2012 09:37 PM, Srikanth Kumar Lingala wrote:


Hi all,
Is it possible to create two networks with same subnet across two different 
tenants?
I tried this with latest quantum, but got the following error:
Invalid input for operation: Requested subnet with cidr: 25.25.0.0/24 for 
network: 7263582f-cb57-47a2-86cf-97a4ab40de52 overlaps with another subnet. 



I think it is quite possible case across multiple tenants.
Please clarify. --

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



___
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] A simple guide to install OpenStack Folsom

[Emilien Macchi]

Hi,

Great job !

I suggest some things :

- glance add command is deprecated, please use glance image-create.
- no need to modify ownership for nova.
- typo here : /etc/cinder/api-paste.init (it's a INI file)
- for Quantum, you are using the use case in which only one tenant can reach 
external network, I don't suggest this use case for many deployments. You can 
have a look to my script [1] for enabling all tenants access to external 
network.



Regards


- Mail original -

De: Skible OpenStack skible.openst...@gmail.com
À: Alan Pevec ape...@gmail.com
Cc: openstack@lists.launchpad.net
Envoyé: Mercredi 10 Octobre 2012 11:27:15
Objet: Re: [Openstack] A simple guide to install OpenStack Folsom

Le 10/10/2012 11:23, Alan Pevec a écrit :
 On Wed, Oct 10, 2012 at 11:10 AM, Skible OpenStack
 skible.openst...@gmail.com wrote:
 I am counting on our your feedback to enhance my work and contribute it to
 the OpenStack Eco System.
 I wonder about 
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/tree/master/Scripts
 which say:
 # Mainly inspired by
 https://github.com/openstack/keystone/blob/master/tools/sample_data.sh

 Why not submit that as an improvement to Keystone?
 I'd like to propose consolidation of all keystone initialization
 scripts around (Keyston's sample_data.sh, Devstack's keystone_data.sh,
 scripts like yours) and move to Lorin's YAML config (see
 https://lists.launchpad.net/openstack/msg17204.html)
 I'm just not sure yet if additional dependency on YAML is worth it.

 Cheers,
 Alan
Hi Alan,

That's a very good idea. I personally prefer scripting over YAML since
it is simpler and easier to use.
devstack's script is way fat to me, it adds things i don't need so i had
put it on a diet to come out with a much simpler and easier script.

I will see how i can submit my work to keystone people.

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

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

Re: [Openstack] Help about Quantum Conf

[Emilien Macchi]

Hi,I suggest you to read the official documentation [1] which helps to install and configure Quantum + OVS for many use cases.I think you should use 3 NICs for your controller node : eth0 for management network, eth1 for VMs traffic (used by OVS), and eth2 for public network (i.e. Internet). For compute nodes, I suggest using 2 NIC : eth0 for management network and eth1 for VMs traffic.[1] http://docs.openstack.org/trunk/openstack-network/admin/content/demo_installions.htmlRegards--Emilien MacchiOpenStack EngineerEMAIL : emilien.mac...@enovance.com –SKYPE :enovance-emilien.macchiWEB :www.enovance.comDe: "Bilel Msekni" ski...@hotmail.frÀ: openstack@lists.launchpad.net, "emilien openstack" emilien.openst...@gmail.comEnvoyé: Mardi 9 Octobre 2012 09:29:30Objet: [Openstack] Help about Quantum Conf





Hi,

I have finished installing OpenStack Folsom but i am encountring a
small issue about configuring Quantum.
I would like to start the simplest scenario Flat
  Network but i dont know how to configure my bridges (br-int,
br-ex and br-tun)

i have two NICs on each node ( primary eth0 and secondary eth1)

If someone can show me the way, i will be very grateful since i will
be writing a guide about it for future users.

Thanks.


___Mailing list: https://launchpad.net/~openstackPost to   : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help  : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Launch instance on a second compute node

[Emilien Macchi]

Hi,


Can you provide nova-compute.log from second compute node ?


Thank's,


Regards


On Sat, Oct 6, 2012 at 5:06 PM, Afef MDHAFFAR afef.mdhaf...@gmail.comwrote:

 Hi all,

 I am trying to add a second compute node. I use Ubuntu 12.04 with XCP.
 nova-manage service list show that the second node is working and
 correctly added to the cloud:
 -
 nova-manage service list
 2012-10-06 14:53:50 DEBUG nova.utils
 [req-e73cab5f-b984-48dc-aee7-98298a9a5dc9 None None] backend module
 'nova.db.sqlalchemy.api' from '/opt/stack/nova/nova/db/sqlalchemy/api.pyc'
 from (pid=2588) __get_backend /opt/stack/nova/nova/utils.py:502
 Binary   Host Zone
 Status State Updated_At
 nova-compute DevStackOSDomU   nova
 enabled:-)   2012-10-06 14:53:49
 nova-network DevStackOSDomU   nova
 enabled:-)   2012-10-06 14:53:49
 nova-compute DevStackOSDomU   nova
 enabledXXX   2012-10-04 12:57:37
 nova-certDevStackOSDomU   nova
 enabled:-)   2012-10-06 14:53:47
 nova-scheduler   DevStackOSDomU   nova
 enabled:-)   2012-10-06 14:53:47
 nova-consoleauth DevStackOSDomU   nova
 enabled:-)   2012-10-06 14:53:42
 nova-network DevStackOSDomU1  nova
 enabled:-)   2012-10-06 14:53:57
 nova-compute DevStackOSDomU1  nova
 enabled:-)   2012-10-06 14:53:57
 ---

 However, I am still not able to launch an instance on the second compute
 node, even if I clearly specify the compute node in the nova boot command 
 (nova
 boot --image 1 --flavor 2 --key_name test --hint force_hosts=
 DevStackOSDomU1  my-first-server).

 Any idea how to solve this porblem?

 Thank you,
 Afef



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




-- 
*Emilien Macchi
*
OpenStack Engineer



http://www.enovance.com
 *EMAIL :* emil...@enovance.com – *SKYPE : *enovance-emilien.macchi
*WEB : *www.enovance.com
eNovance_petit.pngeNoCloud_petit.png___
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] Installing Folsom on Ubuntu 12.04

[Emilien Macchi]

Hi,

Have you tried 'apt-get update' before checking the repository ?

Keystone should be 2012.2~rc1-0ubuntu1~cloud0 in Cloud Archive [1]


Regards


[1]
http://ubuntu-cloud.archive.canonical.com/dists/precise-updates/folsom/main/binary-amd64/Packages



On Tue, Oct 2, 2012 at 12:06 AM, Ahmed Al-Mehdi ah...@coraid.com wrote:

 Hello,

 I am attempting to do a fresh install of OpenStack / Folsom release on
 Ubuntu 12.04 following the doc - Install and Deploy Manual – Red Hat
 Ubuntu (Folsom version).  I added a new file to /etc/apt/sources.list.d,
 folsom.list:


 root@bodega:/etc/apt/sources.list.d# cat folsom.list
 deb http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-updates/folsom 
 main
 root@bodega:/etc/apt/sources.list.d#

 When I check with aptitude as to what version of keystone will be
 installed, it seems Essex will be installed.

 root@bodega:/etc/apt/sources.list.d# aptitude show keystone
 Package: keystone
 State: not installed
 Version: *2012.1*+stable~20120824-a16a0ab9-0ubuntu2.2
 Priority: extra
 Section: python
 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com

 My understanding is version *2012.1* is Essex?  I must be missing
 something or doing something real silly, any help would be very appreciated.

 Thank you,
 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




-- 
*Emilien Macchi
*
System Engineer (Intern)



http://www.enovance.com

 *EMAIL :* emil...@enovance.com n.marc...@enovance.com – *SKYPE : *
enovance-emilien.macchi
*WEB : *www.enovance.com
eNoCloud_petit.pngeNovance_petit.png___
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] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04

[Emilien Macchi]

Hi Shake,

On Sat, Sep 8, 2012 at 6:08 AM, Shake Chen shake.c...@gmail.com wrote:

 Thanks for the greate document and script.

 I have read the document and have some question,

 queston 1


 If eth1 is connected to a Switch, it should be in tagged mode.

 my question is
 If the eth1 not connected to Switch,  it wolud work?


You need at least one physical network, let's say phynet1 which correspond
to a virtual bridge br-eth1.

You should connect at least one interface (eth1) on this bridge to be sure
that your virtual TAP will be able to communicate with the network.

Robert Kukura has written an excellent documentation [1] about how to
implement Open-vSwitch into Quantum.


 queston 2

 Enable IP forwarding :

 my question is
 In Essex, seem no need Enable IP forwarding ,

  just because we use quantum, so we need setting Enable IP forwarding,
 right?


In Essex, you should enable IP forwarding where you run nova-network with
the goal that VMs can ping outside.

In Folsom, you will find a L3 agent [2].


[1] http://wiki.openstack.org/ConfigureOpenvswitch
[2] http://wiki.openstack.org/quantum-l3


Regards,
-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Issue with compute service on Hyper-V Node

[Emilien Macchi]

Hi,

I'm playing with Hyper-V support [1] to run a compute node on a Windows
node.

My environment :

- 1 controller on Ubuntu 12.04 with OpenStack Essex (a clean install).

- 1 compute node with Windows 2012 / Hyper-V / Python 2.7 (32 bits)

Here is my nova.conf : http://paste.openstack.org/show/vt6bZ35GoY6pBosq8rVV/
and the error I have when I try to start nova-compute with net start
openstack-compute : http://paste.openstack.org/show/agNpu90ZOFisJn05sXUQ/
I can see : Exception: Unknown connection type None while there is
connection_type=hyperv in my nova.conf.

I've followed step by step the PDF, and downloaded the last version of
installer.


Any idea ?

[1] http://wiki.openstack.org/Hyper-V


Regards
-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Issue with compute service on Hyper-V Node

[Emilien Macchi]

I finally found by myself.

The nova.conf file needs to be put in nova\bin as it is written in the Wiki.

I think you should modify the PDF documentation to avoid misunderstanding.


Great job by the way !


On Sat, Sep 8, 2012 at 5:02 PM, Emilien Macchi
emilien.mac...@stackops.comwrote:

 Hi,

 I'm playing with Hyper-V support [1] to run a compute node on a Windows
 node.

 My environment :

 - 1 controller on Ubuntu 12.04 with OpenStack Essex (a clean install).

 - 1 compute node with Windows 2012 / Hyper-V / Python 2.7 (32 bits)

 Here is my nova.conf :
 http://paste.openstack.org/show/vt6bZ35GoY6pBosq8rVV/
 and the error I have when I try to start nova-compute with net start
 openstack-compute : http://paste.openstack.org/show/agNpu90ZOFisJn05sXUQ/
 I can see : Exception: Unknown connection type None while there is
 connection_type=hyperv in my nova.conf.

 I've followed step by step the PDF, and downloaded the last version of
 installer.


 Any idea ?

 [1] http://wiki.openstack.org/Hyper-V


 Regards
 --
 Emilien Macchi
 *System Engineer*
 *www.stackops.com

 | *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
 * http://www.stackops.com
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination, distribution, copying or
 use of this message or any attachments, for any purpose, is strictly
 prohibited by law.




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L

[Openstack] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04

[Emilien Macchi]

Hi Stackers,

This week, I've been moving forward with Folsom testing.
It seems that I'm not alone in wanting to see what will provide Folsom and
what will be the changes for Deployment. I also decided to start a guide
(with some scripts) [1] which helps anyone who wants to deploy Folsom
Testing Packages [1] into Ubuntu 12.04.

Keep in mind my work is still under development, but please fill free to
report any problem.
At this moment, Networking with Quantum is not working since I've some
packaging issues but it should be fixed very soon.

Of course, this doc is really far to be ready for full deployment, but it
will evolute in the future and I hope everyone will enjoy with it.

Thank's to the developers for the great job which has been done, and good
testing !

[1] https://github.com/EmilienM/openstack-folsom-guide
[2]
https://launchpad.net/~openstack-ubuntu-testing/+archive/folsom-trunk-testing


Regards,
-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Unable to start Horizon after successfully installation through devstack.

[Emilien Macchi]

Hi,

Did you try :

apt-get -y install python-django
wget
http://mirror.ovh.net/ubuntu//pool/main/p/python-django-openstack-auth/python-openstack-auth_1.0.1-0ubuntu6_all.deb
dpkg -i python-openstack-auth*.deb
apt-get -y install apache2 libapache2-mod-wsgi openstack-dashboard
memcached python-memcache
service apache2 restart

I run Horizon from Folsom Testing packages, and it's working quite well (I
have some bugs to solve, but the dashboard is working).


Regards

On Thu, Sep 6, 2012 at 11:29 AM, hitesh wadekar hitesh.wade...@gmail.comwrote:

 Hi Razique,

 There is no horizon vhost into /etc/apache2/horizon

 It seems compressor config issue.

 I found this - https://bugs.launchpad.net/horizon/+bug/1036571, but
 still issue has not been resolved.

 Thanks,
 Hitesh


 On Thu, Sep 6, 2012 at 1:06 PM, Razique Mahroua razique.mahr...@gmail.com
  wrote:

 Hi,
 check the Apache error logs, maybe a module is missing ?
 (the horizon vhost is into /etc/apache2/conf.d/horizon I think)


 *Nuage  Co - Razique Mahroua** *
 razique.mahr...@gmail.com


 Le 6 sept. 2012 à 07:26, hitesh wadekar hitesh.wade...@gmail.com a
 écrit :

 Hello Folks,

 Recently I tried with DevStack installation. It has successfully
 installed, even success message has been appeared at cmd. However, when I
 checked it in the browser I got this issue.
 Internal Server Error

 The server encountered an internal error or misconfiguration and was
 unable to complete your request.

 Also, when I checked it with DevStack Horizon screen. It has been stucked
 at  - UncompressableFileError: 'horizon/js/horizon.js' isn't accessible
 via COMPRESS_URL ('/static/') and can't be compressed.

 Any idea about it?

 Cheer,

 Hitesh






 ___
 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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
NUAGECO-LOGO-Fblan_petit.jpg___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Essex Quantum+OVS Doubt

[Emilien Macchi]

Hi,

You can read this excellent and full documentation :

http://wiki.openstack.org/ConfigureOpenvswitch


-Emilien



On Tue, Sep 4, 2012 at 12:49 PM, Trinath Somanchi 
trinath.soman...@gmail.com wrote:

 Hi-

 With respect to Quantum-ovs-plugin-agent, which will be running in the
 compute node, I have the following doubts.

 The core and expected functionality, is that,,

 [1] the port is tagged with a 'tag'.
 [2] deletion of flows.

 Is my understanding CORRECT? If not what more tasks are performed by this
 AGENT.?

 Please help me in this regard.

 --
 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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Quantum DHCP support.

[Emilien Macchi]

Hi,

You can find more informations here :

http://wiki.openstack.org/QuantumDevstack

and here :

devstack.org


-Emilien



On Tue, Sep 4, 2012 at 11:43 AM, Trinath Somanchi 
trinath.soman...@gmail.com wrote:

 Hi Suzuki-

 I'm interested in the kind of setup your running with. Can u guide with
 some inputs on bringing up the Devstack_QuantumV2 +OVS setup.

 Thanking you.

 -
 TNS


 On Tue, Sep 4, 2012 at 2:33 PM, Takaaki Suzuki suz...@midokura.comwrote:

 Hi

 Currently, I see that DHCP instance is created per network, at least
 from looking at the Dnsmasq implementation.

 I'm curious to know how a DHCP instance can provide services to a VM
 attached to a port on a network that has multiple subnets.

 It doesn't seem possible to me that a VM can get two IP addresses on
 an interface from this DHCP server. Is this feature supported in
 Quantum?

 I ran a quick test using Devstack + QuantumV2 + OVS plugin.  I created
 one network called test04, and two subnets for tor the network,
 192.168.10.0/24 and 192.168.30.0/24.
 With Dnsmasq running as the DHCP server, I launched a VM, and as
 suspected, it did not receive any IP address.  I checked the Dnsmasq
 log and it looked like it did receive DHCPDISCOVER message but it did
 not offer anything back.

 I would love to know there is actually a way to get this to work, or
 if I'm missing some critical steps here.

 Thanks!
 Suzuki

 ___
 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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] the Dashboard bug of Folsom in ubuntu 12.04

[Emilien Macchi]

Shake,

Did you figure out a solution to this bug ?



Regards

On Mon, Aug 27, 2012 at 11:54 AM, Shake Chen shake.c...@gmail.com wrote:

 HI

 I try to install the Folsom in ubuntu 12.04,  the step is like Essex.

 I have add the PPA of folsom

 but when I try to install Dashbaord, meet the problem

 root@node07:~# apt-get install openstack-dashboard
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 Some packages could not be installed. This may mean that you have
 requested an impossible situation or if you are using the unstable
 distribution that some required packages have not yet been created
 or been moved out of Incoming.
 The following information may help to resolve the situation:

 The following packages have unmet dependencies:
  openstack-dashboard : Depends: python-django-horizon but it is not going
 to be installed
 E: Unable to correct problems, you have held broken packages.


 seem ubuntu package的bug？ right？


 --
 Shake Chen



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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] A few posts on H/A OpenStack

[Emilien Macchi]

Hi,

Thank's for the articles, that's very interesting.

With other stackers (Sebastien Han [1]  Martin Loschwitz [2]), we are
working also on other Resources Agents for bringing all OpenSack services
in HA. You can have a look here :

https://github.com/madkiss/openstack-resource-agents


Regards

[1] www.sebastien-han.fr
[2] http://www.hastexo.com/blogs/martin




On Sat, Sep 1, 2012 at 9:29 AM, Eugene Kirpichov ekirpic...@gmail.comwrote:

 Thanks! Indeed I put only the tag networking into planet, will fix...



 31.08.2012, в 21:20, Atul Jha atul@csscorp.com написал(а):

  Eugene,
 
  snip
  Hi,
 
  Thought the community could be interested. We (Mirantis) recently
  published a few posts about building H/A OpenStack.
 
  http://www.mirantis.com/blog/intro-to-openstack-in-production/ - Intro
  http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/ -
  MySQL and RabbitMQ
 
 http://www.mirantis.com/blog/software-high-availability-load-balancing-openstack-cloud-api-servic/
  - API services
 
  Comments very welcome.
 
  /snip
 
  Nice, informative blog.
  I am not sure if i missed anything but why i don`t see these blogs in
 openstack planet feed? (http://planet.openstack.org/)
 
  Am i missing something? Putting it on planet will have more impact as we
 really don`t know if everyone who wants to know about HA is on the
 mailing-list and has not missed your announcement mail. In another words
 you don`t have to take effort in making announcement in mailing list for
 every new blog published. :)
 
 
  Cheers!!
 
  Atul Jha aka koolhead17
  http://www.csscorp.com/common/email-disclaimer.php

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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Billing in Openstack

[Emilien Macchi]

Hi,

You should read Ceilometer Project [1] and try it into DevStack directly in
editing localrc before to run devstack and add :

enable_service ceilometer-acompute,ceilometer-acentral, ceilometer-collector

Enjoy !


[1] http://wiki.openstack.org/EfficientMetering



Regards,


-Emilien


On Thu, Aug 30, 2012 at 12:21 PM, Rajesh Avula avula.rajes...@gmail.comwrote:

 Greetings...!!

 I would like to generate billing of used resources (CPU, RAM, Disk) in
 openstack. Below are the details of my setup (Please ask me for more
 details if require regarding setup)

 Mainly I have used 2 system to make my setup, below are the details...

 1. *On First Laptop *(Dell - Latitude, with 4 GB RAM, Intel Core i5 vpro
 Processor, 500 GB Hard disk) I have installed a *virtual machine with
 CentOS (6.2)* on *Xenserver (6.0.2)* and on that *virtual machine I
 installed openstack* by following below links and some other links from
 google

 https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
 http://wiki.openstack.org/XenServer

 2. *On Second Laptop* (same as above configuration) I have installed 
 *openfiler
 and made NFS and iSCSI targets* for glance, swift, and for instances.

 3. For network I am using BELKIN wireless adapter 5 port L2-switch)

 I am able to launch Instances from AMI's, instances are getting IP
 addresses, able to create volumes and attaching to the instances.

 All I need is, Is there any possibility in openstack where I can define
 the values / prices for the resources so that users will get the bills
 accordingly ?

 Below are the packages installed in my setup for dashboard
 python-django-horizon-2012.1.1-1.el6.noarch
 openstack-dashboard-2012.1.1-1.el6.noarch

 Is there any other packages should be installed to get billing option on
 dashboard?
 Any specific configuration required ?

 Please let me know how to get billing information of the used / using
 resources.


 --
 Thanks  Regards,
 Rajesh Avula
 09831138115
 07259024701.

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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] [Netstack] [Quantum] Using VirtIO Driver with KVM

[Emilien Macchi]

Thank you for the bug Yaguang !

You've been faster than me ;)


Regards


On Wed, Aug 8, 2012 at 4:16 AM, heut2008 heut2...@gmail.com wrote:

 I have file  a bug https://bugs.launchpad.net/nova/+bug/1034216
 and  upload a patch https://review.openstack.org/#/c/11008/

 2012/8/8 Dan Wendlandt d...@nicira.com

  Hi Emilien,

 I know of customers using virtio with Quantum, but I think they may have
 modified the template directly, as you mention below.

 This code in nova changed quite a bit from Essex - Folsom.  Looking at
 nova/virt/libvirt/vif.py, I noticed that whoever added the
 libvirt_use_virtio_for_bridges flag did not add it to the
 LibvirtOpenVswitchDriver class.  Based on the XML you show below, my guess
 would be that if you add the following lines prior to the return statement
 of the plug() method of that class, you would get the right XML:

 if FLAGS.libvirt_use_virtio_for_bridges:
   conf.model = virtio

 That said, I haven't tested it.

 Can you file a bug on this in nova?  Thanks,

 Dan


 On Tue, Aug 7, 2012 at 2:57 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi Stackers,


 I'm talking with Sebastien 
 Hanhttp://www.sebastien-han.fr/blog/2012/07/19/make-the-network-of-your-vms-fly-with-virtio-driverabout
  VirtIO Driver for network interfaces.

 We have two setup :

 1) Ubuntu 12.04 / Essex / KVM
network_manager=*nova.network*.manager.*VlanManager*
libvirt_use_virtio_for_bridges=true

 2) Ubuntu 12.04 / Essex / KVM
network_manager=nova.network.quantum.manager.QuantumManager

 linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
libvirt_use_virtio_for_bridges=true

 What we have seen :

 - VMs booting from first setup have VirtIO driver for networking
 (Gigabit ready). Here is the libvirt.xml for network part :

 interface type='bridge'
 (...)
 model type='virtio'/
 (...)
 /interface

 - VMs booting from second setup (with Quantum) don't use VirtIO driver
 (No gigabit). Here is the libvirt.xml for network part :

 interface type='ethernet'
 target dev='tapx' /
 mac address='' /
 script path='' /
  /interface

 The only one way I found to use VirtIO driver with Quantum to modify
 /usr/share/pyshared/nova/virt/libvirt.xml.template file and add :

 model type='virtio'/
 (after line 125)

 So you must have something like this :
 interface type='ethernet'
 target dev='${nic.name}' /
 mac address='${nic.mac_address}' /
 script path='${nic.script}' /
 model type='virtio'/
 /interface

 And restart LibVirt service :
 service libvirt-bin restart


 What do you think about that ? Should we modify the template to get
 Gigabit capacity or is there something wrong in my configuration ?


 Best regards

 --
 Emilien Macchi
 *System Engineer*
 *www.stackops.com

 | *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
 * http://www.stackops.com
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination

[Openstack] [Quantum] Using VirtIO Driver with KVM

[Emilien Macchi]

Hi Stackers,


I'm talking with Sebastien
Hanhttp://www.sebastien-han.fr/blog/2012/07/19/make-the-network-of-your-vms-fly-with-virtio-driverabout
VirtIO Driver for network interfaces.

We have two setup :

1) Ubuntu 12.04 / Essex / KVM
   network_manager=*nova.network*.manager.*VlanManager*
   libvirt_use_virtio_for_bridges=true

2) Ubuntu 12.04 / Essex / KVM
   network_manager=nova.network.quantum.manager.QuantumManager
   linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
   libvirt_use_virtio_for_bridges=true

What we have seen :

- VMs booting from first setup have VirtIO driver for networking (Gigabit
ready). Here is the libvirt.xml for network part :

interface type='bridge'
(...)
model type='virtio'/
(...)
/interface

- VMs booting from second setup (with Quantum) don't use VirtIO driver (No
gigabit). Here is the libvirt.xml for network part :

interface type='ethernet'
target dev='tapx' /
mac address='' /
script path='' /
 /interface

The only one way I found to use VirtIO driver with Quantum to modify
/usr/share/pyshared/nova/virt/libvirt.xml.template file and add :

model type='virtio'/
(after line 125)

So you must have something like this :
interface type='ethernet'
target dev='${nic.name}' /
mac address='${nic.mac_address}' /
script path='${nic.script}' /
model type='virtio'/
/interface

And restart LibVirt service :
service libvirt-bin restart


What do you think about that ? Should we modify the template to get Gigabit
capacity or is there something wrong in my configuration ?


Best regards

-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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][Nova] Question regarding multiple network interfaces

[Emilien Macchi]

Hi,

If you run VlanManager [1] you have actually two important flags :

Private Switch :

vlan_interface=ethX


Public Switch :

public_interface=ethX

[1]
http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-vlan-networking.html


Regards




On Tue, Aug 7, 2012 at 11:50 PM, Leander Bessa Beernaert 
leande...@gmail.com wrote:

 Is there a flag in the nova.conf file or is this something that needs to
 be done on the operating system?


 On Tue, Aug 7, 2012 at 8:26 PM, Sébastien Han han.sebast...@gmail.comwrote:

 Hi,

 If eth0 is connected to the public switch and if eth1 is connected to
 the private switch you can enable the ipv4 forwarding on the compute
 node. Thanks to this the VMs will have access to the outside world and
 the packet will be routed from eth1 to eth0 :).

 Cheers!

 On Tue, Aug 7, 2012 at 5:18 PM, Leander Bessa Beernaert
 leande...@gmail.com wrote:
  Hello,
 
  I have a question regarding the use of two network interfaces.
 According to
  the official documentation, one of the interfaces is used for public
 access
  and the other for internal access (inter-vm communication). What i'd
 like to
  know is how does an instance connect to the outside world (internet
 access)?
  Is it done through the switch connected to the private interface or the
  public interface?
 
  --
  Cumprimentos / Regards,
  Leander
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 




 --
 Cumprimentos / Regards,
 Leander

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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com

| *emilien.mac...@stackops.com**  *|* skype:emilien.macchi*
* http://www.stackops.com
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Testing NOVA-OVS-Quantum setup

[Emilien Macchi]

My bad, here the good link :

https://github.com/EmilienM/doc-openstack/issues/new


Regards


On Mon, Jul 16, 2012 at 6:55 AM, Trinath Somanchi 
trinath.soman...@gmail.com wrote:

 Hi Emilien-

 The link given by you throwing an error. 404 page not found.


 https://github.com/EmilienM/doc-openstack/issues/add



 On Sat, Jul 14, 2012 at 2:15 AM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 That's actually an issue with Packaging and I met in April during Essex
 Release.

 My document does not explain in details how to manage Quantum, but this
 is a document which allow to get something working in dual node.

 Of course, maybe I did some errors and the best way for me to correct it
 asap is to write here :

 https://github.com/EmilienM/doc-openstack/issues/add


 Good luck,


 Regards



 On Fri, Jul 13, 2012 at 7:31 PM, Dan Wendlandt d...@nicira.com wrote:

 Hi Trinath,

 I suspect that /etc/quantum should be created when you run the following
 line from Emilien's document:

 apt-get install -y quantum-server quantum-plugin-openvswitch
 python-keystone
 python-keystoneclient openvswitch-datapath-source

 If /etc/quantum was not created, perhaps its an issue with the packaging.

 Dan


 On Thu, Jul 12, 2012 at 11:00 PM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi -

 Thanks a lot for the reply.

 Following the document (
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for
 installing the OVS and Quantum Agent in Compute nodes.

 *Open-vSwitch  Quantum-agent*
 apt-get install openvswitch-switch quantum-openvswitch-agent
 modprobe openvswitch_mod
 echo openvswitch_mod/etc/modules

 Trinath After following the above steps, I'm unable to find below
 specified editable file. in /etc there no directory with quantum.


 Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change
 the SQL connection to :
 sql_connection = mysql://
 ovs_quantum:password@10.68.1.40:3306/ovs_quantum


 Please guide me understand the same,



 On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.comwrote:

 Hi Trinath,

 Yes, you need to install openvswitch and the quantum-agent on the nova
 compute nodes as well.

 Aaron


 On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi-

 With respect to your document, on Openstack - OVS and Quantum,

 I'm unable to understand the setup of OVS and Quantum in
 ESSEX-2/Compute-node machine.

 In the Document,
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No:
 17/19,

 In the section Open-vSwitch  Quantum-agent, Do we need to install
 OVS and Quantum in the Compute-nodes too..??





 .




 On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi,

 I wrote a documentation about installation of Essex with Quantum,
 OVS in multi-node architecture.

 You can read it here :

 https://github.com/EmilienM/doc-openstack



 Regards




 On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote:

 Trinath,

 I found the following Quantun admin guide was useful for that
 purpose:


 http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w

 Thanks,

 Joseph

 
 (w) 703-248-6160
 (f) 703-812-3712
 3811 N. Fairfax Drive Suite 200
 Arlington, VA, 22203, USA
 http://www.east.isi.edu/~jsuh

 - Original Message -
 From: Trinath Somanchi trinath.soman...@gmail.com
 To: openstack@lists.launchpad.net
 Sent: Wednesday, June 20, 2012 7:04:21 AM
 Subject: [Openstack] Testing NOVA-OVS-Quantum setup


 Hi-


 I have installed configured NOVA-OVS-Quantum based setup using the
 guide provided by openstack and OVS.


 I have a instance up and running.


 I'm new to Openstack.


 Can you any one help me out on the testing/validating on is
 instance up with OVS and Quantum.


 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




 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com**
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten 
 asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su

Re: [Openstack] Testing NOVA-OVS-Quantum setup

[Emilien Macchi]

Hi,

*Quantum-Server :*

Can be a VM, or installed also on nova-controller node.


*Quantum-Agent :*

Should be run on each compute node, and ALSO the nova-network node (to
create virtual gateway).
If you run nova-network on nova-controller node, you'll need also
Quantum-Agent.



Regards

On Mon, Jul 16, 2012 at 11:37 AM, Trinath Somanchi 
trinath.soman...@gmail.com wrote:

 Hi-


 Got a doubt in configuring Quantum in Controller and Node.

 In Controller, we have Quantum-Server and Quantum-Agent.
 In Node we have only Quantum-Agent.

 Why do we need Quantum-Agent in the Controller side?

 Please kindly help me understand this...

 --
 trinath


 On Mon, Jul 16, 2012 at 2:14 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 My bad, here the good link :

 https://github.com/EmilienM/doc-openstack/issues/new


 Regards



 On Mon, Jul 16, 2012 at 6:55 AM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi Emilien-

 The link given by you throwing an error. 404 page not found.


 https://github.com/EmilienM/doc-openstack/issues/add



 On Sat, Jul 14, 2012 at 2:15 AM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 That's actually an issue with Packaging and I met in April during Essex
 Release.

 My document does not explain in details how to manage Quantum, but this
 is a document which allow to get something working in dual node.

 Of course, maybe I did some errors and the best way for me to correct
 it asap is to write here :

 https://github.com/EmilienM/doc-openstack/issues/add


 Good luck,


 Regards



 On Fri, Jul 13, 2012 at 7:31 PM, Dan Wendlandt d...@nicira.com wrote:

 Hi Trinath,

 I suspect that /etc/quantum should be created when you run the
 following line from Emilien's document:

 apt-get install -y quantum-server quantum-plugin-openvswitch
 python-keystone
 python-keystoneclient openvswitch-datapath-source

 If /etc/quantum was not created, perhaps its an issue with the
 packaging.

 Dan


 On Thu, Jul 12, 2012 at 11:00 PM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi -

 Thanks a lot for the reply.

 Following the document (
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for
 installing the OVS and Quantum Agent in Compute nodes.

 *Open-vSwitch  Quantum-agent*
 apt-get install openvswitch-switch quantum-openvswitch-agent
 modprobe openvswitch_mod
 echo openvswitch_mod/etc/modules

 Trinath After following the above steps, I'm unable to find below
 specified editable file. in /etc there no directory with quantum.


 Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and
 change the SQL connection to :
 sql_connection = mysql://
 ovs_quantum:password@10.68.1.40:3306/ovs_quantum


 Please guide me understand the same,



 On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.comwrote:

 Hi Trinath,

 Yes, you need to install openvswitch and the quantum-agent on the
 nova compute nodes as well.

 Aaron


 On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi-

 With respect to your document, on Openstack - OVS and Quantum,

 I'm unable to understand the setup of OVS and Quantum in
 ESSEX-2/Compute-node machine.

 In the Document,
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No:
 17/19,

 In the section Open-vSwitch  Quantum-agent, Do we need to install
 OVS and Quantum in the Compute-nodes too..??





 .




 On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi,

 I wrote a documentation about installation of Essex with Quantum,
 OVS in multi-node architecture.

 You can read it here :

 https://github.com/EmilienM/doc-openstack



 Regards




 On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote:

 Trinath,

 I found the following Quantun admin guide was useful for that
 purpose:


 http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w

 Thanks,

 Joseph

 
 (w) 703-248-6160
 (f) 703-812-3712
 3811 N. Fairfax Drive Suite 200
 Arlington, VA, 22203, USA
 http://www.east.isi.edu/~jsuh

 - Original Message -
 From: Trinath Somanchi trinath.soman...@gmail.com
 To: openstack@lists.launchpad.net
 Sent: Wednesday, June 20, 2012 7:04:21 AM
 Subject: [Openstack] Testing NOVA-OVS-Quantum setup


 Hi-


 I have installed configured NOVA-OVS-Quantum based setup using
 the guide provided by openstack and OVS.


 I have a instance up and running.


 I'm new to Openstack.


 Can you any one help me out on the testing/validating on is
 instance up with OVS and Quantum.


 Thanking you..


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

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack

[Openstack] [Folsom Testing Packages] Feedback

[Emilien Macchi]

Thank's to Adam Gandelman for the last e-mail about *Folsom Testing Packages
* in *Ubuntu* [1].

I would like to share here my feedback and also the Issues I have today
with that :


   - Glance Packaging [2] : Conflict between two packages.
   - Glance Endpoint does not work with API V2 but works with API V1. If I
   comment */etc/glance/glance-api-paste.ini* the part about V2, everything
   works. Maybe it's my bad, I need to understand more what's wrong. Anyway, I
   did not have this issue with Essex.
   - Horizon does not work [3]


[1] http://www.mail-archive.com/openstack@lists.launchpad.net/msg14298.html
[2] https://bugs.launchpad.net/python-glanceclient/+bug/1024281
[3] https://bugs.launchpad.net/horizon/+bug/1024326


Let me know if you have any idea.


Regards

-- 
Emilien Macchi
*System Engineer*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Testing NOVA-OVS-Quantum setup

[Emilien Macchi]

That's actually an issue with Packaging and I met in April during Essex
Release.

My document does not explain in details how to manage Quantum, but this is
a document which allow to get something working in dual node.

Of course, maybe I did some errors and the best way for me to correct it
asap is to write here :

https://github.com/EmilienM/doc-openstack/issues/add


Good luck,


Regards


On Fri, Jul 13, 2012 at 7:31 PM, Dan Wendlandt d...@nicira.com wrote:

 Hi Trinath,

 I suspect that /etc/quantum should be created when you run the following
 line from Emilien's document:

 apt-get install -y quantum-server quantum-plugin-openvswitch
 python-keystone
 python-keystoneclient openvswitch-datapath-source

 If /etc/quantum was not created, perhaps its an issue with the packaging.

 Dan


 On Thu, Jul 12, 2012 at 11:00 PM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi -

 Thanks a lot for the reply.

 Following the document (
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing
 the OVS and Quantum Agent in Compute nodes.

 *Open-vSwitch  Quantum-agent*
 apt-get install openvswitch-switch quantum-openvswitch-agent
 modprobe openvswitch_mod
 echo openvswitch_mod/etc/modules

 Trinath After following the above steps, I'm unable to find below
 specified editable file. in /etc there no directory with quantum.


 Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change
 the SQL connection to :
 sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum
 


 Please guide me understand the same,



 On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote:

 Hi Trinath,

 Yes, you need to install openvswitch and the quantum-agent on the nova
 compute nodes as well.

 Aaron


 On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi 
 trinath.soman...@gmail.com wrote:

 Hi-

 With respect to your document, on Openstack - OVS and Quantum,

 I'm unable to understand the setup of OVS and Quantum in
 ESSEX-2/Compute-node machine.

 In the Document,
 https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No:
 17/19,

 In the section Open-vSwitch  Quantum-agent, Do we need to install OVS
 and Quantum in the Compute-nodes too..??





 .




 On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi,

 I wrote a documentation about installation of Essex with Quantum, OVS
 in multi-node architecture.

 You can read it here :

 https://github.com/EmilienM/doc-openstack



 Regards




 On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote:

 Trinath,

 I found the following Quantun admin guide was useful for that purpose:


 http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w

 Thanks,

 Joseph

 
 (w) 703-248-6160
 (f) 703-812-3712
 3811 N. Fairfax Drive Suite 200
 Arlington, VA, 22203, USA
 http://www.east.isi.edu/~jsuh

 - Original Message -
 From: Trinath Somanchi trinath.soman...@gmail.com
 To: openstack@lists.launchpad.net
 Sent: Wednesday, June 20, 2012 7:04:21 AM
 Subject: [Openstack] Testing NOVA-OVS-Quantum setup


 Hi-


 I have installed configured NOVA-OVS-Quantum based setup using the
 guide provided by openstack and OVS.


 I have a instance up and running.


 I'm new to Openstack.


 Can you any one help me out on the testing/validating on is instance
 up with OVS and Quantum.


 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




 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com**
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten 
 asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales 
 circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y

Re: [Openstack] [Folsom Testing Packages] Feedback

[Emilien Macchi]

My bad. I know for the future now.

Thank's and sorry for the mistake.


Regards


On Fri, Jul 13, 2012 at 7:19 PM, Adam Gandelman ad...@canonical.com wrote:

  On 07/13/2012 05:50 AM, Emilien Macchi wrote:

 Thank's to Adam Gandelman for the last e-mail about *Folsom Testing
 Packages* in *Ubuntu* [1].

 I would like to share here my feedback and also the Issues I have today
 with that :


- Glance Packaging [2] : Conflict between two packages.
 - Glance Endpoint does not work with API V2 but works with API V1. If
I comment */etc/glance/glance-api-paste.ini* the part about V2,
everything works. Maybe it's my bad, I need to understand more what's
wrong. Anyway, I did not have this issue with Essex.
- Horizon does not work [3]


 [1]
 http://www.mail-archive.com/openstack@lists.launchpad.net/msg14298.html
 [2] https://bugs.launchpad.net/python-glanceclient/+bug/1024281
 [3] https://bugs.launchpad.net/horizon/+bug/1024326


 Let me know if you have any idea.


 Regards


 Thanks Emilien, this is exacly the kind of testing I was hoping to get!
 In the future, please target bugs against the Ubuntu distro package rather
 than the upstream project.  Thanks again, hope to have those fixed for you
 soon.

 Adam





  Emilien Macchi
 *System Engineer*
 *www.stackops.com* | emilien.mac...@stackops.com**
  *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination, distribution, copying or
 use of this message or any attachments, for any purpose, is strictly
 prohibited by law.



 ___
 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




-- 
Emilien Macchi
*System Engineer*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique

Re: [Openstack] dashboard connecting problem with keystone

[Emilien Macchi]

Hi,

I have already got this issue.

You need to be sure that nova-volume is working and also the endpoint in
Keystone is working on the right port and the good API version (should be
v1).


Regards



On Thu, Jun 21, 2012 at 3:20 PM, sarath zacharia
sarathzacha...@gmail.comwrote:

 Hai,

   I upgraded the new openstack version to essex. And all service
 are running . When I logging to the dashboard it shows error like

 Error: Unable to retrieve usage information.


 Is it because of any keystone configuration with the nova and glance .and
 any default_catalog.templates file path settings in keystone.conf

  and I got error from the apache2 log file

 [Thu Jun 21 18:40:38 2012] [error]
 [Thu Jun 21 18:40:38 2012] [error]
 ERROR:horizon.dashboards.nova.instances_and_volumes.views:ClientException
 in volume index
 [Thu Jun 21 18:40:38 2012] [error] Traceback (most recent call last):
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/horizon/dashboards/nova/instances_and_volumes/
 views.py, line 69, in get_volumes_data
 [Thu Jun 21 18:40:38 2012] [error] volumes = api.volume_list(self.request)
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/horizon/api/nova.py, line 475, in
 volume_list
 [Thu Jun 21 18:40:38 2012] [error] return
 cinderclient(request).volumes.list()
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/novaclient/v1_1/volumes.py, line 79,
 in list
 [Thu Jun 21 18:40:38 2012] [error] return self._list(/volumes/detail,
 volumes)
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/novaclient/base.py, line 71, in _list
 [Thu Jun 21 18:40:38 2012] [error] resp, body = self.api.client.get(url)
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/novaclient/client.py, line 136, in get
 [Thu Jun 21 18:40:38 2012] [error] return self._cs_request(url, 'GET',
 **kwargs)
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/novaclient/client.py, line 124, in
 _cs_request
 [Thu Jun 21 18:40:38 2012] [error] **kwargs)
 [Thu Jun 21 18:40:38 2012] [error] File
 /usr/lib/python2.7/dist-packages/novaclient/client.py, line 107, in
 request
 [Thu Jun 21 18:40:38 2012] [error] raise exceptions.from_response(resp,
 body)
 [Thu Jun 21 18:40:38 2012] [error] BadRequest: Malformed request url (HTTP
 400)

 --
 with regards

 Sarath Zacharia

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




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law

Re: [Openstack] Testing NOVA-OVS-Quantum setup

[Emilien Macchi]

Hi,

I wrote a documentation about installation of Essex with Quantum, OVS in
multi-node architecture.

You can read it here :

https://github.com/EmilienM/doc-openstack



Regards



On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote:

 Trinath,

 I found the following Quantun admin guide was useful for that purpose:


 http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w

 Thanks,

 Joseph

 
 (w) 703-248-6160
 (f) 703-812-3712
 3811 N. Fairfax Drive Suite 200
 Arlington, VA, 22203, USA
 http://www.east.isi.edu/~jsuh

 - Original Message -
 From: Trinath Somanchi trinath.soman...@gmail.com
 To: openstack@lists.launchpad.net
 Sent: Wednesday, June 20, 2012 7:04:21 AM
 Subject: [Openstack] Testing NOVA-OVS-Quantum setup


 Hi-


 I have installed configured NOVA-OVS-Quantum based setup using the guide
 provided by openstack and OVS.


 I have a instance up and running.


 I'm new to Openstack.


 Can you any one help me out on the testing/validating on is instance up
 with OVS and Quantum.


 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




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] instance cannot access outside network

[Emilien Macchi]

 you in advance .

 ** **

 *David(**李跃洲**)*

 *E-MAIL: yuezhou...@hisoft.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




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Essex - Quantum - OVS - Multi-Node Architecture - Working Partially !

[Emilien Macchi]

Hi Stackers,

I'm working now with a Multi-Node Architecture which is working partially
with Essex - Quantum - OVS. My VMs have now the network but I did some
hacks for that and I need more help.

Can you have a look to my questions ?

https://answers.launchpad.net/quantum/+question/199823


Thank you,

Regards

-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Can't manage volumes snapshots with python-novaclient

[Emilien Macchi]

Hi,


I have a bug with python-novaclient / Ubuntu 12.04 / Essex
(2012.1-0ubuntu2.1 version for OpenStack packages).

My nova.conf : http://paste.openstack.org/show/18372/


Issue :

- When I go to the dashboard, from my project tab I can't go to Instances
 Volumes and Images  Snapshots. Here the debug :
http://paste.openstack.org/show/18363/

- nova volume-list fails : http://paste.openstack.org/show/18368/


Any idea ?

Regards

-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Can't manage volumes snapshots with python-novaclient

[Emilien Macchi]

I found the solution. My Volume Endpoint was in v1.1, and it should be v1.


Status : fixed.


Regards


On Wed, Jun 6, 2012 at 7:42 PM, Kiall Mac Innes ki...@managedit.ie wrote:

 Have you checked the server logs? Both of the logs you pasted are from the
 client side.. (Horizon and the nova command both use python-novaclient to
 speak to nova-api - where the real error will be logged)

 Thanks,
 Kiall


 On Wed, Jun 6, 2012 at 5:35 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi,


 I have a bug with python-novaclient / Ubuntu 12.04 / Essex
 (2012.1-0ubuntu2.1 version for OpenStack packages).

 My nova.conf : http://paste.openstack.org/show/18372/


 Issue :

 - When I go to the dashboard, from my project tab I can't go to
 Instances  Volumes and Images  Snapshots. Here the debug :
 http://paste.openstack.org/show/18363/

 - nova volume-list fails : http://paste.openstack.org/show/18368/


 Any idea ?

 Regards

 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com**
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination, distribution, copying or
 use of this message or any attachments, for any purpose, is strictly
 prohibited by law.


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





-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception

Re: [Openstack] [Openstack-operators] Quantum+Openvswitch: possible network configurations

[Emilien Macchi]

Hi Igor,

How did you progress in your dual node ?

I'm interesting about that :-)


Regards


On Sat, Jun 2, 2012 at 6:03 PM, Igor Laskovy igor.lask...@gmail.com wrote:

 Hello all from sunny Kiev!

 I have lab with two nodes (controller and compute) and
 Quantum+Openvswitch setup.
 With which options in nova.conf I can configure just simply putting my
 instances into one network without providing any gw/nats, without
 setting any ip subnets and dhcp activities for this network?
 Just putting virtual nics in the bridge, mark it with some vlan
 id/xvlan label and run traffic away through one of the network card of
 physical host.

 --
 Igor Laskovy
 Kiev, Ukraine
 ___
 Openstack-operators mailing list
 openstack-operat...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] search on the mailing list

[Emilien Macchi]

Hi Massimo,

You can have a look here :

http://openstack.markmail.org


Good luck !


Regards


On Fri, Jun 1, 2012 at 10:05 AM, Massimo Canonico m...@di.unipmn.it wrote:

 Hi,
 I'm having a problem deleting my running instance and I would like to
 search on the mailing list in order to figure out if someone had already
 had this problem (i'm quite sure).

 So I went to 
 https://lists.launchpad.net/**openstack/https://lists.launchpad.net/openstack/with
  my credentials, but I did not find any search button.

 Am I wrong?

 M

 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com**
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] After nova-network setup, I loose Internet access

[Emilien Macchi]

Thanks Vish  Chris,

You helped me to understand what is wrong.

I add fixed_range=*10.0.0.0/16* and now all is right.

Solved !


Thank's again.


Regards



On Thu, May 31, 2012 at 1:15 AM, Chris Wright chr...@sous-sol.org wrote:

 * Emilien Macchi (emilien.mac...@stackops.com) wrote:
  But I haven't created any network yet, and my nova.conf on nova-network
  node is the default file.
 
  Do you think the problem comes from nova.conf ?

 Indirectly, yes.  The default fixed_range is 10.0.0.0/8 (which will cause
 a
 NAT rule to be added for that range).  You can add fixed_range to your
 nova.conf and change it to something that doesn't conflict.

 thanks,
 -chris




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] After nova-network setup, I loose Internet access

[Emilien Macchi]

Hi Stackers,


I'm working on a multi-node architecture with Ubuntu 12.04 / Openstack
Essex from Ubuntu packages :

1 controller (with Rabbit-MQ, MySQL, Nova-API, Nova-Schedule), 1 network
(nova-network), 1 compute (nova-compute with KVM).

When I setup a fresh nova-network node, I do (and nothing else after
upgrade) :

*apt-get install nova-network*

After this command, I loose Internet access, but can reach the server from
my LAN.

Here you can find my iptables-save
http://paste.openstack.org/show/18222/result.

My routing table :

Destination Gateway Genmask Flags Metric RefUse
Iface
*default 10.15.100.4 0.0.0.0 UG10000
eth0*
10.15.0.0   *   255.255.0.0 U 0  00 eth0


Where *10.15.100.4* is my gateway.


Any idea ?


Regards

-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] After nova-network setup, I loose Internet access

[Emilien Macchi]

Hi,

I've just discovered where exactly it's broken : the default NAT rules.

When I flush NAT rules with *iptables -t nat -F*, I have Internet access.

What do you think about that ?

The fact is I use Ubuntu packages, with default configuration, so need I to
change something, or is it normal ?

Am I alone to have this problem ?



Regards



On Wed, May 30, 2012 at 3:30 PM, Sébastien Han han.sebast...@gmail.comwrote:

 Hi,

 Which tests did you perform in order to recover your internet connectivity?
 It might seem stupid but did you check your /etc/resolv.conf, try to
 desinstall/reinstall nova-network, flush the iptables?

 Tell us more about the recovery tests you've already done, after this we
 will be able go further :)

 Cheers!


 On Wed, May 30, 2012 at 2:03 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi Stackers,


 I'm working on a multi-node architecture with Ubuntu 12.04 / Openstack
 Essex from Ubuntu packages :

 1 controller (with Rabbit-MQ, MySQL, Nova-API, Nova-Schedule), 1 network
 (nova-network), 1 compute (nova-compute with KVM).

 When I setup a fresh nova-network node, I do (and nothing else after
 upgrade) :

 *apt-get install nova-network*

 After this command, I loose Internet access, but can reach the server
 from my LAN.

 Here you can find my 
 iptables-savehttp://paste.openstack.org/show/18222/result.

 My routing table :

 Destination Gateway Genmask Flags Metric RefUse
 Iface
 *default 10.15.100.4 0.0.0.0 UG10000
 eth0*
 10.15.0.0   *   255.255.0.0 U 0  00
 eth0


 Where *10.15.100.4* is my gateway.


 Any idea ?


 Regards

 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination, distribution, copying or
 use of this message or any attachments, for any purpose, is strictly
 prohibited by law.


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





-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva

Re: [Openstack] After nova-network setup, I loose Internet access

[Emilien Macchi]

But I haven't created any network yet, and my nova.conf on nova-network
node is the default file.

Do you think the problem comes from nova.conf ?




On Wed, May 30, 2012 at 11:12 PM, Vishvananda Ishaya v...@kokkocloud.comwrote:

 It is probably because your fixed range for instances conflicts with the
 range used for your host.

 You might have to update your config to use a different/smaller fixed
 range in your conf and when running the network create command.

 Vish

 On May 30, 2012, at 7:12 AM, Emilien Macchi wrote:

 Hi,

 I've just discovered where exactly it's broken : the default NAT rules.

 When I flush NAT rules with *iptables -t nat -F*, I have Internet
 access.

 What do you think about that ?

 The fact is I use Ubuntu packages, with default configuration, so need I
 to change something, or is it normal ?

 Am I alone to have this problem ?



 Regards



 On Wed, May 30, 2012 at 3:30 PM, Sébastien Han han.sebast...@gmail.comwrote:

 Hi,

 Which tests did you perform in order to recover your internet
 connectivity?
 It might seem stupid but did you check your /etc/resolv.conf, try to
 desinstall/reinstall nova-network, flush the iptables?

 Tell us more about the recovery tests you've already done, after this we
 will be able go further :)

 Cheers!


 On Wed, May 30, 2012 at 2:03 PM, Emilien Macchi 
 emilien.mac...@stackops.com wrote:

 Hi Stackers,


 I'm working on a multi-node architecture with Ubuntu 12.04 / Openstack
 Essex from Ubuntu packages :

 1 controller (with Rabbit-MQ, MySQL, Nova-API, Nova-Schedule), 1 network
 (nova-network), 1 compute (nova-compute with KVM).

 When I setup a fresh nova-network node, I do (and nothing else after
 upgrade) :

 *apt-get install nova-network*

 After this command, I loose Internet access, but can reach the server
 from my LAN.

 Here you can find my 
 iptables-savehttp://paste.openstack.org/show/18222/result.

 My routing table :

 Destination Gateway Genmask Flags Metric RefUse
 Iface
 *default 10.15.100.4 0.0.0.0 UG1000
 0 eth0*
 10.15.0.0   *   255.255.0.0 U 0  00
 eth0


 Where *10.15.100.4* is my gateway.


 Any idea ?


 Regards

 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de este mensaje, que el correo
 electrónico y las comunicaciones por medio de Internet no permiten asegurar
 ni garantizar la confidencialidad de los mensajes transmitidos, así como
 tampoco su integridad o su correcta recepción, por lo que STACKOPS
 TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
 Si no consintiese en la utilización del correo electrónico o de las
 comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
 conocimiento de manera inmediata. Este mensaje va dirigido, de manera
 exclusiva, a su destinatario y contiene información confidencial y sujeta
 al secreto profesional, cuya divulgación no está permitida por la ley. En
 caso de haber recibido este mensaje por error, le rogamos que, de forma
 inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
 atención y proceda a su eliminación, así como a la de cualquier documento
 adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
 utilización de este mensaje, o de cualquier documento adjunto al mismo,
 cualquiera que fuera su finalidad, están prohibidas por la ley.

 * PRIVILEGED AND CONFIDENTIAL 
 We hereby inform you, as addressee of this message, that e-mail and
 Internet do not guarantee the confidentiality, nor the completeness or
 proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
 does not assume any liability for those circumstances. Should you not agree
 to the use of e-mail or to communications via Internet, you are kindly
 requested to notify us immediately. This message is intended exclusively
 for the person to whom it is addressed and contains privileged and
 confidential information protected from disclosure by law. If you are not
 the addressee indicated in this message, you should immediately delete it
 and any attachments and notify the sender by reply e-mail. In such case,
 you are hereby notified that any dissemination, distribution, copying or
 use of this message or any attachments, for any purpose, is strictly
 prohibited by law.


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





 --
 Emilien Macchi
 *SysAdmin (Intern)*
 *www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
 *

 *

  ADVERTENCIA LEGAL 
 Le informamos, como destinatario de

[Openstack] Instances don't get an IP from DHCP (Quantum, OVS, multi-node computes)

[Emilien Macchi]

Hi,

Since 2 weeks, I've been looking for a solution with a Quantum + OVS issue.

The situation :

2 servers :

Essex-1 - Eth0 : 10.68.1.40 - ETH1 : connected to br-int OVS bridge
- Glance, Nova-*, Keystone, Horizon, Quantum-Server, KVM, OVS,
Quantum-Agent
- nova.conf :
https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf

Essex-2 - Eth0 : 10.68.1.45 - ETH1 : connected to br-int OVS bridge
- nova-compute, KVM, Quantum-Agent
- nova.conf :
https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf

I've followed http://openvswitch.org/openstack/documentation/ and
http://docs.openstack.org/trunk/openstack-network/admin/content/

I've created th network with :
nova-manage network create --label=mysql
--fixed_range_v4=192.168.113.0/24--project_id=d2f0dc48a8944c6e96cb88c772376f06
--bridge=br-int
--bridge_interface=eth1

What's not working :
- When I create an instance from dashboard, the VM does not get an IP from
DHCP server (hosted on ESSEX-1).
You can see the logs here : http://paste.openstack.org/show/17997/

What I did to investigate :
- dhcpdump -i br-int : I can see DHCPDISCOVER on both servers (without
answers)
- ps -ef | grep dnsmasq :
nobody 6564 1 0 14:12 ? 00:00:00 /usr/sbin/dnsmasq --strict-order
--bind-interfaces --conf-file= --domain=novalocal
--pid-file=/var/lib/nova/networks/nova-gw-0f427a46-3f.pid
--listen-address=192.168.113.1 --except-interface=lo
--dhcp-range=192.168.113.2,static,120s --dhcp-lease-max=256
--dhcp-hostsfile=/var/lib/nova/networks/nova-gw-0f427a46-3f.conf
--dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 6565 6564 0 14:12 ? 00:00:00 /usr/sbin/dnsmasq --strict-order
--bind-interfaces --conf-file= --domain=novalocal
--pid-file=/var/lib/nova/networks/nova-gw-0f427a46-3f.pid
--listen-address=192.168.113.1 --except-interface=lo
--dhcp-range=192.168.113.2,static,120s --dhcp-lease-max=256
--dhcp-hostsfile=/var/lib/nova/networks/nova-gw-0f427a46-3f.conf
--dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root 16536 6192 0 14:40 pts/14 00:00:00 grep --color=auto dnsm

Is my nova.conf correct ?
What's wrong with my configuration ?
Is there a problem with DNSMASQ ?

I would apreciate any idea !

Regards

-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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 Essex - Guide for Ubuntu 12.04

[Emilien Macchi]

Hi,

On Fri, May 18, 2012 at 7:13 PM, Yi Sun beyo...@gmail.com wrote:

  On 05/18/2012 03:44 AM, Emilien Macchi wrote:

 Yi,

 On Fri, May 18, 2012 at 7:47 AM, Yi Sun beyo...@gmail.com wrote:

 Emilien,
 I'm using your document to setup an environment, so far I have two
 issues, hope you could help out.
 1. the Linux bridge driver is install/loaded during the install process.
 I tried to remove it by add it into modprobe blacklist, but it is still
 installed after reboot.


 We don't care about it, we use OVS bridging.

 In the INSTALL.Linux file that comes with OVS source code, it has
 following comments:

 **
  The Open vSwitch datapath requires bridging support
   (CONFIG_BRIDGE) to be built as a kernel module.  (This is common
   in kernels provided by Linux distributions.)  The bridge module
   must not be loaded or in use.  If the bridge module is running
   (check with lsmod | grep bridge), you must remove it (rmmod
   bridge) before starting the datapath.

 
 Anyway, I have find out how to remove bridge and stp. Just use following
 commands:

 # virsh net-destroy default
 # virsh net-autostart --disable default

 Ok. Thank's for information.





   2. I can start quantum-server manually without any problem, but it will
 fall if it is auto started during system boot up.


You should modify the init script with
--*logfile*=/var/log/quantum/quantum-server.log
flag.

Regards




 Do you have logs files ?

   Do you know how to turn on the log for quantum-server? I did not find
 anything in /var/log/quantum.

 Thx
 Yi




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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]create network project_id

[Emilien Macchi]

Hi William,

Do you use Quantum in your infrastructude ?

Do you have logs files to show use ?


Regards


On Wed, May 16, 2012 at 5:00 AM, William Herry 
william.herry.ch...@gmail.com wrote:

 Hi

 how can I create a network for *specified* project, I use --project_id
 option when create network, seems not work,
 do i miss something:

 any one can help?

 thanks


 --

 ===
 William Herry

 williamherrych...@gmail.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




-- 
Emilien Macchi
*SysAdmin (Intern)*
*www.stackops.com* | emilien.mac...@stackops.com** | skype:memilien69
*

*

 ADVERTENCIA LEGAL 
Le informamos, como destinatario de este mensaje, que el correo electrónico
y las comunicaciones por medio de Internet no permiten asegurar ni
garantizar la confidencialidad de los mensajes transmitidos, así como
tampoco su integridad o su correcta recepción, por lo que STACKOPS
TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias.
Si no consintiese en la utilización del correo electrónico o de las
comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro
conocimiento de manera inmediata. Este mensaje va dirigido, de manera
exclusiva, a su destinatario y contiene información confidencial y sujeta
al secreto profesional, cuya divulgación no está permitida por la ley. En
caso de haber recibido este mensaje por error, le rogamos que, de forma
inmediata, nos lo comunique mediante correo electrónico remitido a nuestra
atención y proceda a su eliminación, así como a la de cualquier documento
adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o
utilización de este mensaje, o de cualquier documento adjunto al mismo,
cualquiera que fuera su finalidad, están prohibidas por la ley.

* PRIVILEGED AND CONFIDENTIAL 
We hereby inform you, as addressee of this message, that e-mail and
Internet do not guarantee the confidentiality, nor the completeness or
proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L.
does not assume any liability for those circumstances. Should you not agree
to the use of e-mail or to communications via Internet, you are kindly
requested to notify us immediately. This message is intended exclusively
for the person to whom it is addressed and contains privileged and
confidential information protected from disclosure by law. If you are not
the addressee indicated in this message, you should immediately delete it
and any attachments and notify the sender by reply e-mail. In such case,
you are hereby notified that any dissemination, distribution, copying or
use of this message or any attachments, for any purpose, is strictly
prohibited by law.
___
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] Install Your Own OpenStack Cloud - Essex Edition

[Emilien Macchi]

Eric,


Have you made worked OVS with Quantum in multi-mode yet ?



Emilien




Le mardi 08 mai 2012 à 09:46 +0200, Eric Dodemont a écrit :

 Emilien,
 
 In a next version, I will include: 
 
 - Quantum (I just mention it in this version);
 - LXC (experimental);
 - a study case;
 - instance migration, etc.
 
 Eric  
 
 On 07/05/12 14:59, Emilien Macchi wrote: 
 
  Nice work Eric,
  
  
  But you don't speak about Quantum. Is it on schedule ?
  
  
  
  Regards
  
  
  Le lundi 07 mai 2012 à 14:23 +0200, Eric Dodemont a écrit : 
  
   I have written a 50 pages document: Install Your Own OpenStack Cloud - 
   Essex Edition.
   
   The PDF file can be downloaded here: http://tiny.cc/qstxdw
   
   In the document, I describe in detail the installation, configuration 
   and use of my OpenStack cloud. I try to not use scripts to show clearly 
   all the steps to follow.
   
   Installation is made on two physical servers and explanations are given 
   to add more compute nodes.
   
   I added a lot of information, especially about the VLAN networking mode.
   
   Software Versions:
   
   - Operating System: Linux Ubuntu Server version 12.04 (Precise), 64 bits.
   - Cloud Computing: OpenStack version 2012.1 (Essex) including Nova, 
   Glance, Keystone, and Horizon.
   
   Best regards,
   
   Eric
   
   ___
   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] Quantum - Keystone integration in stable/essex broken?

[Emilien Macchi]

Hi,


That's right, Keystone  Quantum are not yet ready to wok together.

I met the same problem when I tested it a couple of weeks ago and the
authentification via Keystone didn't work as well.

People from dev confirmed me that it's not completely supported for
Essex.




Regards




Emilien



Le mardi 08 mai 2012 à 07:34 +, Gurjar, Unmesh a écrit :
 Hi,
 
  
 
 I am using stable/essex release and have enabled Quantum with Keystone
 authentication. I had to update the authN filter to use the
 ‘keystone.middleware.auth_token:filter_factory’ (instead of the
 default 'keystone.middleware.quantum_auth_token:filter_factory').
 However, seems like enabling Keystone with Quantum is not completely
 supported (since the nova-manage network creation fails with
 authentication error). Looks like the Quantum Manager in Nova does not
 support Keystone authentication. 
 
  
 
 Can someone please confirm whether enabling Quantum with Keystone is
 completely supported.
 
  
 
 Another observation is that the Nova Quantum client
 (https://github.com/openstack/nova/blob/stable/essex/nova/network/quantum/client.py)
  is using the Quantum API version 1.1, however, the CURRENT version in 
 Quantum API 
 (https://github.com/openstack/quantum/blob/stable/essex/quantum/api/versions.py)
  is 1.0 (version 1.1 is PROPOSED). Shouldn't Nova Quantum client (of 
 stable/essex) be using version 1.0 instead?
 
  
 
  
 
 Thanks  Regards,
 
 Unmesh Gurjar | Lead Engineer |Vertex Software Private Ltd. | w.
 +91.20.6604.1500 x 379 | m. +91.982.324.7631 |
 unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas
 
  
 
 
 
 
 __
 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


___
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] Install Your Own OpenStack Cloud - Essex Edition

[Emilien Macchi]

Nice work Eric,


But you don't speak about Quantum. Is it on schedule ?



Regards


Le lundi 07 mai 2012 à 14:23 +0200, Eric Dodemont a écrit :

 I have written a 50 pages document: Install Your Own OpenStack Cloud - 
 Essex Edition.
 
 The PDF file can be downloaded here: http://tiny.cc/qstxdw
 
 In the document, I describe in detail the installation, configuration 
 and use of my OpenStack cloud. I try to not use scripts to show clearly 
 all the steps to follow.
 
 Installation is made on two physical servers and explanations are given 
 to add more compute nodes.
 
 I added a lot of information, especially about the VLAN networking mode.
 
 Software Versions:
 
 - Operating System: Linux Ubuntu Server version 12.04 (Precise), 64 bits.
 - Cloud Computing: OpenStack version 2012.1 (Essex) including Nova, 
 Glance, Keystone, and Horizon.
 
 Best regards,
 
 Eric
 
 ___
 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] Instance IP assignment problem

[Emilien Macchi]

I think this documentation explains better like me :


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

Quantum is in incubation with Essex, so it's use Nova as a client of
Quantum. In the future, Quantum could be able to manage floating / fixed
ips by itself.



Regards



Le jeudi 03 mai 2012 à 17:06 -0500, Salman Malik a écrit : 

 Hmm... I didn't know the difference. 
 So does it works like this: one can use the floating_range
 flag/fixed_range in nova. conf for putting instances in this global
 network by default ? and then one could create quantum network for
 each project and may use fixed/floating flags with this network to
 define private and public networks ?
 
 
 
 
 __
 
 Date: Thu, 3 May 2012 23:36:36 +0200
 Subject: Re: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: soh...@cs.toronto.edu; ahal...@griddynamics.com;
 openstack@lists.launchpad.net
 
 With Quantum !
 
 
 Le jeudi 3 mai 2012, Salman Malik salma...@live.com a écrit :
  I see. So where do you use private IP's in your setup ?
 
  Thanks,
  Salman
 
 
  
  Subject: RE: [Openstack] Instance IP assignment problem
  From: emilien.openst...@gmail.com
  To: salma...@live.com
  CC: soh...@cs.toronto.edu; ahal...@griddynamics.com;
 openstack@lists.launchpad.net
  Date: Thu, 3 May 2012 17:02:23 +0200
 
  Hi Salman,
 
  Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit :
 
  Hi Emilien,
 
  In your configuration you have the following flags:
 
  --flat_network_bridge=br100
 
  I'm going to try to change it in both servers.
 
  --floating_range=10.68.5.0/24
 
  That's actually my public pool, sot it's not my fixed pool
 (privates IPs).
 
  After my tests, I will let you know of course.
 
 
  Thanks,
 
 
 
  Regards
 
 
  Can you please tell me why you need br100 when you are using br-int
 with OVS ? Secondly, you seem to use floating_range flag as the second
 flag. I assume that it is the pool of addresses that your instances
 will get IP from, right? It may be worthwhile to modify it to
 fixed_range because Bilal suggested here that this config worked for
 him.
 
  Let us know.
 
  Thanks,
  Salman
 
 
 
  
  Date: Thu, 3 May 2012 08:29:42 -0400
  Subject: Re: [Openstack] Instance IP assignment problem
  From: soh...@cs.toronto.edu
  To: emilien.openst...@gmail.com
  CC: ahal...@griddynamics.com; openstack@lists.launchpad.net;
 salma...@live.com
 
  Oops accidently hit send on my phone.
 
 
  I had a similar problem before. My problem was that the nic driver
 on the compute instance (your Essex 2) was dropping vlan tags, and
 then, openvswitch wasn't delivering packets. You can check it using
 tcpdump -e -vvv.
 
  BTW, if you are using virtualbox to run openstack, make sure you are
 not using vbox intel drivers. Use pcnet fast instead.
 
  OVS splinter may also be useful.
 
  Hope that helps.
 
  Cheers
 
  Soheil
 
  On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote:
 
  I had a similar problem before. My problem was that the nic driver
 on the compute instance (your Essex 2) was dropping vlan tags, and
 then, openvswitch wasn
 
  can you find dhcp requests by using tcpdump for example ?
 
  sorry for off-topic but there may be many reasons of such issue
 with dhcp. last one for me was old dhcp client(Ubuntu) and udp
 checksum error. I have essex on centos and was trying ubuntu vm. 
 
  On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
  All seems alright but not working yet.
 
 
  http://paste.openstack.org/show/14791/
 
 
 
  I have executed on both servers :
 
  ovs-vsctl add-port br-int eth1
 
 
  Need I do something else ?
 
  How t


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

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

Thank's for your link, but I'm not sure to have to use it now.


I have one server with all nova services and another with nova-compute
only.


Anyway, I'm going to post a new e-mail about my problem.


Regards


Le vendredi 04 mai 2012 à 13:14 +, Vaze, Mandar a écrit :
 Please also see this : https://review.openstack.org/#/c/6829/
 
  
 
 When nova-network is on remote host,  dhcp requests need to go to
 remote server. I’ve proposed a fix above.
 
  
 
 -Mandar
 
  
 
 
 From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
 [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net]
 On Behalf Of Emilien Macchi
 Sent: Thursday, May 03, 2012 2:19 PM
 To: Bilel Msekni
 Cc: salma...@live.com; openstack@lists.launchpad.net
 Subject: Re: [Openstack] Instance IP assignment problem
 
 
 
  
 
 All seems alright but not working yet.
 
 
 http://paste.openstack.org/show/14791/
 
 
 
 I have executed on both servers :
 
 ovs-vsctl add-port br-int eth1
 
 
 Need I do something else ?
 
 How the DHCP is working in this case ?
 
 
 
 
 
 
 Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : 
 
 Then the problem isn't in the instance but in the nova-network
 service , please check if it is working well  
 
 
 as well as give us the output log when you attempt to create a
 new instance.
 
  
 
 

 __
 
 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: ski...@hotmail.fr
 CC: salma...@live.com; openstack@lists.launchpad.net
 Date: Thu, 3 May 2012 10:21:37 +0200
 
 Fixed IP
 
 
 
 Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : 
 
 Fixed IP or Floating IP ?
 
 
 
 

 __
 
 
 
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 Date: Thu, 3 May 2012 09:55:31 +0200
 CC: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Instance IP assignment problem
 
 Hi,
 
 
 As I told you, I have also a problem for instance IP
 assignement.
 
 
 My architecture :
 
 I use Quantum with OVS plugin on 2 servers Essex-1  Essex-2.
 Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent
  nova-compute only.
 
 You can see more details here.
 
 My configurations files are here and in my documentation.
 
 
 
 Problem Description :
 
 When an instance is created in ESSEX-1, all is working
 (network).
 
 But when the VM is started on ESSEX-2, it does not get an IP
 address. (log file)
 
 I'm sure the problem comes from OVS connection with ESSEX-1.
 
 
 Do I need to configure something like a trunk or a tunnel
 between Essex-1  Essex-2 ?
 
 I miss something in my configuration, if you have any idea...
 
 
 Regards
 
 
 Emilien
 
 
 Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : 
 
 It may help if you can share the log of your launched instance
 as well. There is a possibility that we both are having the
 same issue.
 Netstack developers can give a definitive answer to this, but
 it would be interesting to learn what goes wrong with a
 launched instance.
 
 Salman
 
 
 
 
 

 __
 
 
 
 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:26:26 +0200
 
 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : 
 
 Regarding L3 gateway, I believe its not necessary to have one
 (as the VM hasn't obtained an IP right now, so it can't talk
 to anything outside its net), but I am not sure.
 Regarding your problem, do you see any DHCP responses from the
 DHCP server ? I am asking this because I was having a similar
 problem earlier where I was getting assigned an IP address no
 in my desired fixed_network and I believe that was cause by
 another interfering DHCP server that was replying

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

With this article, I understand I'm not alone to have this problem.


I'm going to try the solution, and If it's working, I will update my
documentation on Essex.



Regards



Le vendredi 04 mai 2012 à 13:10 +, Vaze, Mandar a écrit :
 Emilien,
 
  
 
 Please see https://answers.launchpad.net/quantum/+question/194111
 
  
 
 Nova-compute and nova-network on two different machines seems to be
 the key here.
 
 Solution is proposed in the above thread.
 
  
 
 Hope that helps.
 
  
 
 -Mandar
 
  
 
 
 From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
 [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net]
 On Behalf Of Emilien Macchi
 Sent: Thursday, May 03, 2012 1:26 PM
 To: Salman Malik
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Instance IP assignment problem
 
 
 
  
 
 Hi,
 
 
 As I told you, I have also a problem for instance IP assignement.
 
 
 My architecture :
 
 I use Quantum with OVS plugin on 2 servers Essex-1  Essex-2. Essex-1
 runs all services and Essex-2 runs OVS, Quantum-agent  nova-compute
 only.
 
 You can see more details here.
 
 My configurations files are here and in my documentation.
 
 
 
 Problem Description :
 
 When an instance is created in ESSEX-1, all is working (network).
 
 But when the VM is started on ESSEX-2, it does not get an IP address.
 (log file)
 
 I'm sure the problem comes from OVS connection with ESSEX-1.
 
 
 Do I need to configure something like a trunk or a tunnel between
 Essex-1  Essex-2 ?
 
 I miss something in my configuration, if you have any idea...
 
 
 Regards
 
 
 Emilien
 
 
 Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : 
 
 It may help if you can share the log of your launched instance as
 well. There is a possibility that we both are having the same issue.
 Netstack developers can give a definitive answer to this, but it would
 be interesting to learn what goes wrong with a launched instance.
 
 Salman
 
 
 
 
  
 
 

 __
 
 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:26:26 +0200
 
 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : 
 
 Regarding L3 gateway, I believe its not necessary to have one
 (as the VM hasn't obtained an IP right now, so it can't talk
 to anything outside its net), but I am not sure.
 Regarding your problem, do you see any DHCP responses from the
 DHCP server ? I am asking this because I was having a similar
 problem earlier where I was getting assigned an IP address no
 in my desired fixed_network and I believe that was cause by
 another interfering DHCP server that was replying to discover
 messages before the nova-network could.
 
 Here my nova.conf and I don't have any interfering DHCP
 server :
 
 
 https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf
 
 
 Thanks
 
 Salman
 
 
 
 
 

 __
 
 
 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:06:01 +0200
 
 Hi Salman,
 
 
 I'm thinking about a networking issue. Where is your L3
 gateway in this architecture ? Maybe do you need an ip helper
 tool to redirect DHCP broadcast ?
 
 
 What do you think about my problem (follow up to my last
 e-mail) ?
 
 
 Thanks
 
 
 Emilien
 
 Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : 
 
 Hi,
 
 Here is the error log: http://pastebin.com/KrNZDrvD
 and nova.conf: http://pastebin.com/Fvd6dSZs
 
 Emilien, I am trying to get an understanding of how different
 Quantum plugins work with OpenStack. Ryu plugin is
 particularly interesting as it uses an OpenFlow controller to
 configure Vswitches.
 
 The problem I am faced with is  (I think ) that I already have
 a private network and Quantum should assign IP addresses to
 instances using DHCP. But instances send out discover message
 on laucnh but never find a DHCP server (although there are 2
 dnsmasqs running

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

Hi,


As I told you, I have also a problem for instance IP assignement.


My architecture :

I use Quantum with OVS plugin on 2 servers Essex-1  Essex-2. Essex-1
runs all services and Essex-2 runs OVS, Quantum-agent  nova-compute
only.

You can see more details here.

My configurations files are here and in my documentation.



Problem Description :

When an instance is created in ESSEX-1, all is working (network).

But when the VM is started on ESSEX-2, it does not get an IP address.
(log file)

I'm sure the problem comes from OVS connection with ESSEX-1.


Do I need to configure something like a trunk or a tunnel between
Essex-1  Essex-2 ?

I miss something in my configuration, if you have any idea...


Regards


Emilien


Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit :
 It may help if you can share the log of your launched instance as
 well. There is a possibility that we both are having the same issue. 
 Netstack developers can give a definitive answer to this, but it would
 be interesting to learn what goes wrong with a launched instance.
 
 Salman
 
 
 
 
 
 
 __
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:26:26 +0200
 
 Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit : 
 
 Regarding L3 gateway, I believe its not necessary to have one
 (as the VM hasn't obtained an IP right now, so it can't talk
 to anything outside its net), but I am not sure.
 Regarding your problem, do you see any DHCP responses from the
 DHCP server ? I am asking this because I was having a similar
 problem earlier where I was getting assigned an IP address no
 in my desired fixed_network and I believe that was cause by
 another interfering DHCP server that was replying to discover
 messages before the nova-network could. 
 
 
 Here my nova.conf and I don't have any interfering DHCP server :
 
 https://github.com/EmilienM/doc-openstack/blob/master/Configuration%
 20Files/Essex-1/nova.conf
 
 
 Thanks
 
 
 Salman
 
 
 
 
 __
 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:06:01 +0200
 
 Hi Salman,
 
 
 I'm thinking about a networking issue. Where is your L3
 gateway in this architecture ? Maybe do you need an ip helper
 tool to redirect DHCP broadcast ?
 
 
 What do you think about my problem (follow up to my last
 e-mail) ?
 
 
 Thanks
 
 
 Emilien
 
 Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : 
 
 Hi,
 
 Here is the error log: http://pastebin.com/KrNZDrvD
 and nova.conf: http://pastebin.com/Fvd6dSZs
 
 Emilien, I am trying to get an understanding of how
 different Quantum plugins work with OpenStack. Ryu
 plugin is particularly interesting as it uses an
 OpenFlow controller to configure Vswitches.
 
 The problem I am faced with is  (I think ) that I
 already have a private network and Quantum should
 assign IP addresses to instances using DHCP. But
 instances send out discover message on laucnh but
 never find a DHCP server (although there are 2
 dnsmasqs running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 __
 
 
 Date: Tue, 1 May 2012 20:43:44 +0200
 Subject: Re: [Openstack] Instance IP assignment
 problem
 From: jorge.delac...@stackops.com
 To: emilien.openst...@gmail.com
 CC: openstack@lists.launchpad.net; salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all the files, errors and
 conf in pastebin or something like that? 
 I have troubles to open in phone :)
 Thank you
 El 01/05/2012 20:39, Emilien Macchi
 emilien.openst...@gmail.com escribió:
 
 Hi

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

 should assign IP addresses to
 instances using DHCP. But instances send out
 discover message on laucnh but never find a
 DHCP server (although there are 2 dnsmasqs
 running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 __
 
 
 
 Date: Tue, 1 May 2012 20:43:44 +0200
 Subject: Re: [Openstack] Instance IP
 assignment problem
 From: jorge.delac...@stackops.com
 To: emilien.openst...@gmail.com
 CC: openstack@lists.launchpad.net;
 salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all the files, errors
 and conf in pastebin or something like that? 
 I have troubles to open in phone :)
 Thank you
 El 01/05/2012 20:39, Emilien Macchi
 emilien.openst...@gmail.com escribió:
 
 Hi,
 
 
 I have a similar problem when I create
 a network per project_id with Quantum.
 
 
 My VMs don't get IP and I can't
 understand why today.
 
 But when I create a private network
 for all projects, VMs get an IP and
 all is working well.
 Do you have the same problem ?
 
 
 Salman, I'm interesting about your
 nova.conf. I can see you are using
 Ryu ?
 Can you tell me more about your use
 case or architecture ?
 
 
 Thanks
 
 
 Le mardi 01 mai 2012 à 12:28 -0500,
 Salman Malik a écrit : 
 
 Hi Jorge,
 
 Thanks for looking into the
 post.
 I have made changes to the
 nova.conf file so that I only
 use 10.0.0.x network (but the
 problem is still the same).
 For this configuration, I
 assume that it will give out
 IPs to instances starting from
 10.0.0.11. And just to inform
 you, my eth1 is configured to
 be 10.0.0.10 (which is a VM
 itself, and eth1 is configured
 as a host-only network with no
 DHCP) and this interface is
 plugged in the integration
 bridge used by quantum
 plugins.
 
 Thanks,
 Salman
 
 PS: Error log of a launched
 instance is also attached

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

: [Openstack] Instance IP
 assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com;
 openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:06:01 +0200
 
 Hi Salman,
 
 
 I'm thinking about a networking issue. Where
 is your L3 gateway in this architecture ?
 Maybe do you need an ip helper tool to
 redirect DHCP broadcast ?
 
 
 What do you think about my problem (follow up
 to my last e-mail) ?
 
 
 Thanks
 
 
 Emilien
 
 Le mardi 01 mai 2012 à 14:00 -0500, Salman
 Malik a écrit : 
 
 Hi,
 
 Here is the error log:
 http://pastebin.com/KrNZDrvD
 and nova.conf:
 http://pastebin.com/Fvd6dSZs
 
 Emilien, I am trying to get an
 understanding of how different Quantum
 plugins work with OpenStack. Ryu
 plugin is particularly interesting as
 it uses an OpenFlow controller to
 configure Vswitches.
 
 The problem I am faced with is  (I
 think ) that I already have a private
 network and Quantum should assign IP
 addresses to instances using DHCP. But
 instances send out discover message on
 laucnh but never find a DHCP server
 (although there are 2 dnsmasqs
 running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 __
 
 
 
 
 Date: Tue, 1 May 2012 20:43:44 +0200
 Subject: Re: [Openstack] Instance IP
 assignment problem
 From: jorge.delac...@stackops.com
 To: emilien.openst...@gmail.com
 CC: openstack@lists.launchpad.net;
 salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all the
 files, errors and conf in pastebin or
 something like that? 
 I have troubles to open in phone :)
 Thank you
 El 01/05/2012 20:39, Emilien Macchi
 emilien.openst...@gmail.com
 escribió:
 
 Hi,
 
 
 I have a similar problem when
 I create a network per
 project_id with Quantum.
 
 
 My VMs don't get IP and I
 can't understand why today.
 
 But when I create a private
 network for all projects, VMs
 get an IP and all is working
 well.
 Do you have the same

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

 already have
 a private network and Quantum
 should assign IP addresses to
 instances using DHCP. But
 instances send out discover
 message on laucnh but never
 find a DHCP server (although
 there are 2 dnsmasqs
 running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 __
 
 
 
 
 
 Date: Tue, 1 May 2012 20:43:44
 +0200
 Subject: Re: [Openstack]
 Instance IP assignment problem
 From:
 jorge.delac...@stackops.com
 To:
 emilien.openst...@gmail.com
 CC:
 openstack@lists.launchpad.net;
 salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all
 the files, errors and conf in
 pastebin or something like
 that? 
 I have troubles to open in
 phone :)
 Thank you
 El 01/05/2012 20:39, Emilien
 Macchi
 emilien.openst...@gmail.com
 escribió:
 
 Hi,
 
 
 I have a similar
 problem when I create
 a network per
 project_id with
 Quantum.
 
 
 My VMs don't get IP
 and I can't understand
 why today.
 
 But when I create a
 private network for
 all projects, VMs get
 an IP and all is
 working well.
 Do you have the same
 problem ?
 
 
 Salman, I'm
 interesting about your
 nova.conf. I can see
 you are using Ryu ?
 Can you tell me more
 about your use case
 or architecture ?
 
 
 Thanks
 
 
 Le mardi 01 mai 2012 à
 12:28 -0500, Salman

Re: [Openstack] Openstack Essex - Guide for Ubuntu 12.04

[Emilien Macchi]

Hi Shake,

Le jeudi 03 mai 2012 à 16:56 +0800, Shake Chen a écrit :

 I have some question about document. please correct me if wrong.
 
 1: nova-api
 
 I found you install nova-api in both machine. but in nova.conf
 
 --nova_url=http://10.68.1.40:8774/v1.1/
 
 whether really need install nova-api in compute node.


So can I delete nova-api from nova compute node (ESSEX-2) ?



 2: nova-network
 
 I found  install nova-network in both machine. but nova.conf not set
 
 --multi-host=T
 
 also the the machine nova.conf 
 --routing_source_ip=10.68.1.40



That's a mistake from me. I just copy/paste the files and change some
parameters.

Please tell me what I can drop from nova.conf of Essex-2.

N.B: I don't want to use multi-host because I'm using Quantum, and it's
not compatible yet for multi hosts.

Tell me if I say wrong !


Thank you for your feedback,

After your response, I'm going to correct it and update my Git.


Regards


Emilien



 
 
 
 
 
 
 
 
 On Wed, May 2, 2012 at 5:30 PM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 HI Edgar,
 
 
 Thank's !
 
 
 Yes,as you can read in the doc, it will evoluate in the
 future.
 
 Maybe someone will do it before me, the documentation is under
 a free license, so feel free to add some features !
 
 
 Best regards
 
 
 
 Le mardi 01 mai 2012 à 23:52 -0700, Edgar Magana (eperdomo) a
 écrit : 
 
  Hi Emilien,
  
   
  
  Good document in general, any plans to add swift here?
  
   
  
  Thanks,
  
   
  
  Edgar Magana
  
   
  
  From: openstack-bounces
  +eperdomo=cisco@lists.launchpad.net
  [mailto:openstack-bounces
  +eperdomo=cisco@lists.launchpad.net] On Behalf Of
  Emilien Macchi
  Sent: Monday, April 30, 2012 12:42 AM
  To: openstack@lists.launchpad.net
  Subject: [Openstack] Openstack Essex - Guide for Ubuntu
  12.04
  
  
   
  
  Hi,
  
  I release my first documentation on OpenStack Essex for
  Ubuntu 12.04.
  
  I've been working for three weeks with StackOps for my
  internship, and my work is focused ont Quantum (Networking
  as a service in OpenStack).
  
  
  It was quite difficult to have a working infrastructure
  because Quantum is only in incubation for Essex release.
  That's why I publish a documentation in which anyone can
  test this fabulous software.
  
  You can find this documentation in attachment and here with
  all configuration files  scripts.
  
  
  Please let me know if I did some mistakes, and of course I
  will do by best tocorrect it.
  
  
  Best regards
  
  
  
  
  
  
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

I ran a 'dhcpdump' on ESSEX-2 and I can see DHCP request, but no
response from ESSEX-1 DNSMASQ process...

I continue to investigate...





Le jeudi 03 mai 2012 à 13:31 +0400, Anton Haldin a écrit :

 can you find dhcp requests by using tcpdump for example ?
 
 
 
 sorry for off-topic but there may be many reasons of such issue with
 dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum
 error. I have essex on centos and was trying ubuntu vm. 
 
 
 On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 All seems alright but not working yet.
 
 
 http://paste.openstack.org/show/14791/
 
 
 
 I have executed on both servers :
 
 ovs-vsctl add-port br-int eth1
 
 
 Need I do something else ?
 
 How the DHCP is working in this case ?
 
 
 
 
 
 
 Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : 
 
  Then the problem isn't in the instance but in the
  nova-network service , please check if it is working well 
  as well as give us the output log when you attempt to create
  a new instance.
  
  
  
  
  
  Subject: RE: [Openstack] Instance IP assignment problem
  From: emilien.openst...@gmail.com
  To: ski...@hotmail.fr
  CC: salma...@live.com; openstack@lists.launchpad.net
  Date: Thu, 3 May 2012 10:21:37 +0200
  
  Fixed IP
  
  
  
  Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : 
  
  Fixed IP or Floating IP ?
  
  
  
  
  
  
  From: emilien.openst...@gmail.com
  To: salma...@live.com
  Date: Thu, 3 May 2012 09:55:31 +0200
  CC: openstack@lists.launchpad.net
  Subject: Re: [Openstack] Instance IP assignment
  problem
  
  Hi,
  
  
  As I told you, I have also a problem for instance IP
  assignement.
  
  
  My architecture :
  
  I use Quantum with OVS plugin on 2 servers Essex-1 
  Essex-2. Essex-1 runs all services and Essex-2 runs
  OVS, Quantum-agent  nova-compute only.
  
  You can see more details here.
  
  My configurations files are here and in my
  documentation.
  
  
  
  Problem Description :
  
  When an instance is created in ESSEX-1, all is
  working (network).
  
  But when the VM is started on ESSEX-2, it does not
  get an IP address. (log file)
  
  I'm sure the problem comes from OVS connection with
  ESSEX-1.
  
  
  Do I need to configure something like a trunk or a
  tunnel between Essex-1  Essex-2 ?
  
  I miss something in my configuration, if you have
  any idea...
  
  
  Regards
  
  
  Emilien
  
  
  Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a
  écrit : 
  
  It may help if you can share the log of your
  launched instance as well. There is a
  possibility that we both are having the same
  issue. 
  Netstack developers can give a definitive
  answer to this, but it would be interesting
  to learn what goes wrong with a launched
  instance.
  
  Salman
  
  
  
  
  
  
  
  
  Subject: RE: [Openstack] Instance IP
  assignment problem
  From: emilien.openst...@gmail.com
  To: salma...@live.com

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

I share my OVS configuration with you :


root@essex-1:~# ovs-vsctl show
03583d51-03b8-4061-a147-1d892447bee2
Bridge br-int
Port tap21d51768-3c
tag: 12
Interface tap21d51768-3c
Port br-int
Interface br-int
type: internal
Port gw-2850687f-68
tag: 12
Interface gw-2850687f-68
type: internal
Port eth1
Interface eth1
ovs_version: 1.4.0+build0


root@essex-2:~# ovs-vsctl show
3defede8-df1c-4a99-9928-850d9f665194
Bridge br-int
Port br-int
Interface br-int
type: internal
Port tapa8899517-37
tag: 12
Interface tapa8899517-37
Port eth1
Interface eth1
ovs_version: 1.4.0+build0





Le jeudi 03 mai 2012 à 13:31 +0400, Anton Haldin a écrit :

 can you find dhcp requests by using tcpdump for example ?
 
 
 
 sorry for off-topic but there may be many reasons of such issue with
 dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum
 error. I have essex on centos and was trying ubuntu vm. 
 
 
 On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 All seems alright but not working yet.
 
 
 http://paste.openstack.org/show/14791/
 
 
 
 I have executed on both servers :
 
 ovs-vsctl add-port br-int eth1
 
 
 Need I do something else ?
 
 How the DHCP is working in this case ?
 
 
 
 
 
 
 Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit : 
 
  Then the problem isn't in the instance but in the
  nova-network service , please check if it is working well 
  as well as give us the output log when you attempt to create
  a new instance.
  
  
  
  
  
  Subject: RE: [Openstack] Instance IP assignment problem
  From: emilien.openst...@gmail.com
  To: ski...@hotmail.fr
  CC: salma...@live.com; openstack@lists.launchpad.net
  Date: Thu, 3 May 2012 10:21:37 +0200
  
  Fixed IP
  
  
  
  Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : 
  
  Fixed IP or Floating IP ?
  
  
  
  
  
  
  From: emilien.openst...@gmail.com
  To: salma...@live.com
  Date: Thu, 3 May 2012 09:55:31 +0200
  CC: openstack@lists.launchpad.net
  Subject: Re: [Openstack] Instance IP assignment
  problem
  
  Hi,
  
  
  As I told you, I have also a problem for instance IP
  assignement.
  
  
  My architecture :
  
  I use Quantum with OVS plugin on 2 servers Essex-1 
  Essex-2. Essex-1 runs all services and Essex-2 runs
  OVS, Quantum-agent  nova-compute only.
  
  You can see more details here.
  
  My configurations files are here and in my
  documentation.
  
  
  
  Problem Description :
  
  When an instance is created in ESSEX-1, all is
  working (network).
  
  But when the VM is started on ESSEX-2, it does not
  get an IP address. (log file)
  
  I'm sure the problem comes from OVS connection with
  ESSEX-1.
  
  
  Do I need to configure something like a trunk or a
  tunnel between Essex-1  Essex-2 ?
  
  I miss something in my configuration, if you have
  any idea...
  
  
  Regards
  
  
  Emilien
  
  
  Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a
  écrit : 
  
  It may help if you can share the log of your
  launched instance as well. There is a
  possibility that we both are having the same
  issue. 
  Netstack developers can give a definitive
  answer

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

 
 
 
 
 __
 
 
 
 
 
 
 Date: Tue, 1 May 2012
 20:43:44 +0200
 Subject: Re:
 [Openstack] Instance
 IP assignment problem
 From:
 jorge.delac...@stackops.com
 To:
 emilien.openst...@gmail.com
 CC:
 
 openstack@lists.launchpad.net; salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you
 upload all the files,
 errors and conf in
 pastebin or something
 like that? 
 I have troubles to
 open in phone :)
 Thank you
 El 01/05/2012 20:39,
 Emilien Macchi
 emilien.openst...@gmail.com 
 escribió:
 
 Hi,
 
 
 I have a
 similar
 problem when I
 create a
 network per
 project_id
 with Quantum.
 
 
 My VMs don't
 get IP and I
 can't
 understand why
 today.
 
 But when I
 create a
 private
 network for
 all projects,
 VMs get an IP
 and all is
 working well.
 Do you have
 the same
 problem ?
 
 
 Salman, I'm
 interesting
 about your
 nova.conf. I
 can see you
 are using
 Ryu ?
 Can you tell
 me more about
 your use
 case or
 architecture

Re: [Openstack] Can't get fix ip via dhcp and can't accociate Floating ip using quantum

[Emilien Macchi]

Hi,

I know this problem.

You should :

- Delete the network with nova-manage network delete
--uuid=XXX (you can find the UUID with nova-manage network
quantum_list

- Clean the ovs_quantum database to check if the network has been
deleted

-Clean the nova database and purge all fixed_ips, networks


I remember after that, my problems was solved.


I hope that's works now for you ;-) - Let me now !



Regards


Le jeudi 03 mai 2012 à 17:58 +0800, livemoon a écrit :

 I use quantum as my nova-network in ubuntu 12.04LTS, there are two
 problem:
 
 
 
 1: it can show fix ip, but in vm, the network interfaces have no ips.
 Using dhclient eth0 does not make sense. Using ifconfig eth0 inet
 xxx netmask xxx can work.
 
 
 2: when I accociate floating ip to a vm , it show error, the
 nova-network log is below:
 
 
 2012-05-03 17:51:18 DEBUG nova.rpc.amqp
 [req-f0a4fffa-d6fa-4ab6-9985-1bc4e248edf7
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc]
 unpacked context: {'user_id': u'538eac0210274847a183a988f57fbd59',
 'roles': [u'Member'], 'timestamp': '2012-05-03T09:51:18.403089',
 'auth_token': 'SANITIZED', 'remote_address': u'127.0.0.1',
 'is_admin': False, 'request_id':
 u'req-f0a4fffa-d6fa-4ab6-9985-1bc4e248edf7', 'project_id':
 u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from
 (pid=3791)
 _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
 2012-05-03 17:51:18 DEBUG nova.rpc.amqp [-] received
 {u'_context_roles': [u'Member'], u'_msg_id':
 u'c4056c388c26498b83a3909d33e6d4ce', u'_context_read_deleted': u'no',
 u'_context_request_id': u'req-ec319cc9-245d-4808-991b-a00b417b923e',
 u'args': {u'id': u'1'}, u'_context_auth_token': 'SANITIZED',
 u'_context_is_admin': False, u'_context_project_id':
 u'57eb0d7989c7457aa3818998fbf9a4dc', u'_context_timestamp':
 u'2012-05-03T09:51:18.787337', u'_context_user_id':
 u'538eac0210274847a183a988f57fbd59', u'method': u'get_floating_ip',
 u'_context_remote_address': u'127.0.0.1'} from (pid=3791)
 _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
 2012-05-03 17:51:18 DEBUG nova.rpc.amqp
 [req-ec319cc9-245d-4808-991b-a00b417b923e
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc]
 unpacked context: {'user_id': u'538eac0210274847a183a988f57fbd59',
 'roles': [u'Member'], 'timestamp': '2012-05-03T09:51:18.787337',
 'auth_token': 'SANITIZED', 'remote_address': u'127.0.0.1',
 'is_admin': False, 'request_id':
 u'req-ec319cc9-245d-4808-991b-a00b417b923e', 'project_id':
 u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from
 (pid=3791)
 _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
 2012-05-03 17:51:18 DEBUG nova.rpc.amqp [-] received
 {u'_context_roles': [u'Member', u'admin'], u'_msg_id':
 u'248d0e0cbff14809978e1b0333621772', u'_context_read_deleted': u'no',
 u'_context_request_id': u'req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1',
 u'args': {u'instance_id': 5, u'instance_uuid':
 u'57f9432f-2177-4635-9692-645ed5a5f2f7', u'host': u'cloud',
 u'project_id': u'57eb0d7989c7457aa3818998fbf9a4dc', u'rxtx_factor':
 1.0}, u'_context_auth_token': 'SANITIZED', u'_context_is_admin':
 True, u'_context_project_id': u'57eb0d7989c7457aa3818998fbf9a4dc',
 u'_context_timestamp': u'2012-05-03T09:51:18.825231',
 u'_context_user_id': u'538eac0210274847a183a988f57fbd59', u'method':
 u'get_instance_nw_info', u'_context_remote_address': u'127.0.0.1'}
 from (pid=3791)
 _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
 2012-05-03 17:51:18 DEBUG nova.rpc.amqp
 [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc]
 unpacked context: {'user_id': u'538eac0210274847a183a988f57fbd59',
 'roles': [u'Member', u'admin'], 'timestamp':
 '2012-05-03T09:51:18.825231', 'auth_token': 'SANITIZED',
 'remote_address': u'127.0.0.1', 'is_admin': True, 'request_id':
 u'req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1', 'project_id':
 u'57eb0d7989c7457aa3818998fbf9a4dc', 'read_deleted': u'no'} from
 (pid=3791)
 _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
 2012-05-03 17:51:18 DEBUG nova.utils
 [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc]
 Attempting to grab semaphore get_dhcp for method _get_dhcp_ip...
 from (pid=3791)
 inner /usr/lib/python2.7/dist-packages/nova/utils.py:927
 2012-05-03 17:51:18 DEBUG nova.utils
 [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc] Got
 semaphore get_dhcp for method _get_dhcp_ip... from (pid=3791)
 inner /usr/lib/python2.7/dist-packages/nova/utils.py:931
 2012-05-03 17:51:18 DEBUG nova.utils
 [req-ac208065-fc2e-4c3b-8fd5-d3661ca33ce1
 538eac0210274847a183a988f57fbd59 57eb0d7989c7457aa3818998fbf9a4dc]
 Attempting to grab semaphore get_dhcp for method _get_dhcp_ip...
 from (pid=3791)
 inner /usr/lib/python2.7/dist-packages/nova/utils.py:927
 2012-05-03 17:51:18 DEBUG nova.utils
 

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

Hi Salman,

Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit :
 Hi Emilien,
 
 In your configuration you have the following flags:
 
 --flat_network_bridge=br100

I'm going to try to change it in both servers.

 --floating_range=10.68.5.0/24

That's actually my public pool, sot it's not my fixed pool (privates
IPs).

After my tests, I will let you know of course.


Thanks,



Regards


 
 Can you please tell me why you need br100 when you are using br-int
 with OVS ? Secondly, you seem to use floating_range flag as the second
 flag. I assume that it is the pool of addresses that your instances
 will get IP from, right? It may be worthwhile to modify it to
 fixed_range because Bilal suggested here that this config worked for
 him. 
 
 Let us know.
 
 Thanks,
 Salman
 
 
 
 
 
 
 __
 Date: Thu, 3 May 2012 08:29:42 -0400
 Subject: Re: [Openstack] Instance IP assignment problem
 From: soh...@cs.toronto.edu
 To: emilien.openst...@gmail.com
 CC: ahal...@griddynamics.com; openstack@lists.launchpad.net;
 salma...@live.com
 
 
 Oops accidently hit send on my phone.
 
 
 I had a similar problem before. My problem was that the nic driver on
 the compute instance (your Essex 2) was dropping vlan tags, and then,
 openvswitch wasn't delivering packets. You can check it using tcpdump
 -e -vvv.
 
 
 
 BTW, if you are using virtualbox to run openstack, make sure you are
 not using vbox intel drivers. Use pcnet fast instead.
 
 
 OVS splinter may also be useful.
 
 
 Hope that helps.
 
 
 Cheers
 Soheil
 
 On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote:
 
 I had a similar problem before. My problem was that the nic
 driver on the compute instance (your Essex 2) was dropping
 vlan tags, and then, openvswitch wasn
 
 can you find dhcp requests by using tcpdump for
 example ?
 
 
 
 sorry for off-topic but there may be many reasons of
 such issue with dhcp. last one for me was old dhcp
 client(Ubuntu) and udp checksum error. I have essex on
 centos and was trying ubuntu vm. 
 
 
 On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 All seems alright but not working yet.
 
 
 http://paste.openstack.org/show/14791/
 
 
 
 I have executed on both servers :
 
 ovs-vsctl add-port br-int eth1
 
 
 Need I do something else ?
 
 How the DHCP is working in this case ?
 
 
 
 
 
 
 Le jeudi 03 mai 2012 à 09:29 +0100, Bilel
 Msekni a écrit : 
 
 Then the problem isn't in the instance
 but in the nova-network service ,
 please check if it is working well 
 as well as give us the output log when
 you attempt to create a new instance.
 
 
 
 __
 
 Subject: RE: [Openstack] Instance IP
 assignment problem
 From: emilien.openst...@gmail.com
 To: ski...@hotmail.fr
 CC: salma...@live.com;
 openstack@lists.launchpad.net
 Date: Thu, 3 May 2012 10:21:37 +0200
 
 Fixed IP
 
 
 
 Le jeudi 03 mai 2012 à 09:15 +0100,
 Bilel Msekni a écrit : 
 
 Fixed IP or Floating IP

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

With Quantum !


Le jeudi 3 mai 2012, Salman Malik salma...@live.com a écrit :
 I see. So where do you use private IP's in your setup ?

 Thanks,
 Salman


 
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: soh...@cs.toronto.edu; ahal...@griddynamics.com;
openstack@lists.launchpad.net
 Date: Thu, 3 May 2012 17:02:23 +0200

 Hi Salman,

 Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit :

 Hi Emilien,

 In your configuration you have the following flags:

 --flat_network_bridge=br100

 I'm going to try to change it in both servers.

 --floating_range=10.68.5.0/24

 That's actually my public pool, sot it's not my fixed pool (privates
IPs).

 After my tests, I will let you know of course.


 Thanks,



 Regards


 Can you please tell me why you need br100 when you are using br-int with
OVS ? Secondly, you seem to use floating_range flag as the second flag. I
assume that it is the pool of addresses that your instances will get IP
from, right? It may be worthwhile to modify it to fixed_range because Bilal
suggested here that this config worked for him.

 Let us know.

 Thanks,
 Salman



 
 Date: Thu, 3 May 2012 08:29:42 -0400
 Subject: Re: [Openstack] Instance IP assignment problem
 From: soh...@cs.toronto.edu
 To: emilien.openst...@gmail.com
 CC: ahal...@griddynamics.com; openstack@lists.launchpad.net;
salma...@live.com

 Oops accidently hit send on my phone.


 I had a similar problem before. My problem was that the nic driver on the
compute instance (your Essex 2) was dropping vlan tags, and then,
openvswitch wasn't delivering packets. You can check it using tcpdump -e
-vvv.

 BTW, if you are using virtualbox to run openstack, make sure you are not
using vbox intel drivers. Use pcnet fast instead.

 OVS splinter may also be useful.

 Hope that helps.

 Cheers

 Soheil

 On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote:

 I had a similar problem before. My problem was that the nic driver on the
compute instance (your Essex 2) was dropping vlan tags, and then,
openvswitch wasn

 can you find dhcp requests by using tcpdump for example ?

 sorry for off-topic but there may be many reasons of such issue with
dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum error. I
have essex on centos and was trying ubuntu vm.

 On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi 
emilien.openst...@gmail.com wrote:

 All seems alright but not working yet.


 http://paste.openstack.org/show/14791/



 I have executed on both servers :

 ovs-vsctl add-port br-int eth1


 Need I do something else ?

 How t
___
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 Essex - Guide for Ubuntu 12.04

[Emilien Macchi]

HI Edgar,


Thank's !


Yes,as you can read in the doc, it will evoluate in the future.

Maybe someone will do it before me, the documentation is under a free
license, so feel free to add some features !


Best regards



Le mardi 01 mai 2012 à 23:52 -0700, Edgar Magana (eperdomo) a écrit :
 Hi Emilien,
 
  
 
 Good document in general, any plans to add swift here?
 
  
 
 Thanks,
 
  
 
 Edgar Magana
 
  
 
 
 From: openstack-bounces+eperdomo=cisco@lists.launchpad.net
 [mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On
 Behalf Of Emilien Macchi
 Sent: Monday, April 30, 2012 12:42 AM
 To: openstack@lists.launchpad.net
 Subject: [Openstack] Openstack Essex - Guide for Ubuntu 12.04
 
 
 
  
 
 Hi,
 
 I release my first documentation on OpenStack Essex for Ubuntu 12.04.
 
 I've been working for three weeks with StackOps for my internship, and
 my work is focused ont Quantum (Networking as a service in OpenStack).
 
 
 It was quite difficult to have a working infrastructure because
 Quantum is only in incubation for Essex release. That's why I
 publish a documentation in which anyone can test this fabulous
 software.
 
 You can find this documentation in attachment and here with all
 configuration files  scripts.
 
 
 Please let me know if I did some mistakes, and of course I will do by
 best tocorrect it.
 
 
 Best regards
 
 -- 
 Emilien Macchi
 Phone : +33 685 117 748
 Skype : memilien69
 Twitter : EmilienMacchi
 Website : http://my1.fr 
 
 
 
  
 
 

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

Re: [Openstack] Instance IP assignment problem

[Emilien Macchi]

Hi,


I have a similar problem when I create a network per project_id with
Quantum.


My VMs don't get IP and I can't understand why today.

But when I create a private network for all projects, VMs get an IP and
all is working well.
Do you have the same problem ?


Salman, I'm interesting about your nova.conf. I can see you are using
Ryu ?
Can you tell me more about your use case or architecture ?


Thanks


Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit :
 Hi Jorge,
 
 Thanks for looking into the post.
 I have made changes to the nova.conf file so that I only use 10.0.0.x
 network (but the problem is still the same). For this configuration, I
 assume that it will give out IPs to instances starting from 10.0.0.11.
 And just to inform you, my eth1 is configured to be 10.0.0.10 (which
 is a VM itself, and eth1 is configured as a host-only network with no
 DHCP) and this interface is plugged in the integration bridge used by
 quantum plugins.
 
 Thanks,
 Salman
 
 PS: Error log of a launched instance is also attached.
 
 
 
 
 
 
 __
 Date: Tue, 1 May 2012 19:03:49 +0200
 Subject: Re: [Openstack] Instance IP assignment problem
 From: jorge.delac...@stackops.com
 To: salma...@live.com
 CC: openstack@lists.launchpad.net
 
 Im not really sure but you are using range for your environment
 10.0.3.x and 10.0.0.x for fixed.
 Can you attach a nova network conf?
 Regards
 
 El 01/05/2012 18:56, Salman Malik salma...@live.com escribió:
 
 Hi Guys,
 
 Can anyone provide any insight to the following question:
 https://answers.launchpad.net/nova/+question/195439
 
 Thanks,
 Salman
 
 
 
 ___
 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] Instance IP assignment problem

[Emilien Macchi]

Hi Salman,


I'm thinking about a networking issue. Where is your L3 gateway in this
architecture ? Maybe do you need an ip helper tool to redirect DHCP
broadcast ?


What do you think about my problem (follow up to my last e-mail) ?


Thanks


Emilien

Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit :
 Hi,
 
 Here is the error log: http://pastebin.com/KrNZDrvD
 and nova.conf: http://pastebin.com/Fvd6dSZs
 
 Emilien, I am trying to get an understanding of how different Quantum
 plugins work with OpenStack. Ryu plugin is particularly interesting as
 it uses an OpenFlow controller to configure Vswitches.
 
 The problem I am faced with is  (I think ) that I already have a
 private network and Quantum should assign IP addresses to instances
 using DHCP. But instances send out discover message on laucnh but
 never find a DHCP server (although there are 2 dnsmasqs running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 
 
 __
 Date: Tue, 1 May 2012 20:43:44 +0200
 Subject: Re: [Openstack] Instance IP assignment problem
 From: jorge.delac...@stackops.com
 To: emilien.openst...@gmail.com
 CC: openstack@lists.launchpad.net; salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all the files, errors and conf in pastebin or
 something like that? 
 I have troubles to open in phone :)
 Thank you
 
 El 01/05/2012 20:39, Emilien Macchi emilien.openst...@gmail.com
 escribió:
 
 Hi,
 
 
 I have a similar problem when I create a network per
 project_id with Quantum.
 
 
 My VMs don't get IP and I can't understand why today.
 
 But when I create a private network for all projects, VMs get
 an IP and all is working well.
 Do you have the same problem ?
 
 
 Salman, I'm interesting about your nova.conf. I can see you
 are using Ryu ?
 Can you tell me more about your use case or architecture ?
 
 
 Thanks
 
 
 Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit : 
 
 Hi Jorge,
 
 Thanks for looking into the post.
 I have made changes to the nova.conf file so that I
 only use 10.0.0.x network (but the problem is still
 the same). For this configuration, I assume that it
 will give out IPs to instances starting from
 10.0.0.11. And just to inform you, my eth1 is
 configured to be 10.0.0.10 (which is a VM itself, and
 eth1 is configured as a host-only network with no
 DHCP) and this interface is plugged in the integration
 bridge used by quantum plugins.
 
 Thanks,
 Salman
 
 PS: Error log of a launched instance is also attached.
 
 
 
 
 __
 
 Date: Tue, 1 May 2012 19:03:49 +0200
 Subject: Re: [Openstack] Instance IP assignment
 problem
 From: jorge.delac...@stackops.com
 To: salma...@live.com
 CC: openstack@lists.launchpad.net
 
 Im not really sure but you are using range for your
 environment 10.0.3.x and 10.0.0.x for fixed.
 Can you attach a nova network conf?
 Regards
 El 01/05/2012 18:56, Salman Malik
 salma...@live.com escribió:
 
 Hi Guys,
 
 Can anyone provide any insight to the
 following question:
 https://answers.launchpad.net/nova/+question/195439
 
 Thanks,
 Salman
 
 
 ___
 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] Instance IP assignment problem

[Emilien Macchi]

Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit :
 Regarding L3 gateway, I believe its not necessary to have one (as the
 VM hasn't obtained an IP right now, so it can't talk to anything
 outside its net), but I am not sure.
 Regarding your problem, do you see any DHCP responses from the DHCP
 server ? I am asking this because I was having a similar problem
 earlier where I was getting assigned an IP address no in my desired
 fixed_network and I believe that was cause by another interfering DHCP
 server that was replying to discover messages before the nova-network
 could. 
 

Here my nova.conf and I don't have any interfering DHCP server :

https://github.com/EmilienM/doc-openstack/blob/master/Configuration%
20Files/Essex-1/nova.conf


Thanks


 Salman
 
 
 
 
 
 
 __
 Subject: RE: [Openstack] Instance IP assignment problem
 From: emilien.openst...@gmail.com
 To: salma...@live.com
 CC: jorge.delac...@stackops.com; openstack@lists.launchpad.net
 Date: Tue, 1 May 2012 21:06:01 +0200
 
 Hi Salman,
 
 
 I'm thinking about a networking issue. Where is your L3 gateway in
 this architecture ? Maybe do you need an ip helper tool to redirect
 DHCP broadcast ?
 
 
 What do you think about my problem (follow up to my last e-mail) ?
 
 
 Thanks
 
 
 Emilien
 
 Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit : 
 
 Hi,
 
 Here is the error log: http://pastebin.com/KrNZDrvD
 and nova.conf: http://pastebin.com/Fvd6dSZs
 
 Emilien, I am trying to get an understanding of how different
 Quantum plugins work with OpenStack. Ryu plugin is
 particularly interesting as it uses an OpenFlow controller to
 configure Vswitches.
 
 The problem I am faced with is  (I think ) that I already have
 a private network and Quantum should assign IP addresses to
 instances using DHCP. But instances send out discover message
 on laucnh but never find a DHCP server (although there are 2
 dnsmasqs running). 
 
 Any ideas?
 
 Thanks,
 Salman
 
 
 
 
 __
 
 Date: Tue, 1 May 2012 20:43:44 +0200
 Subject: Re: [Openstack] Instance IP assignment problem
 From: jorge.delac...@stackops.com
 To: emilien.openst...@gmail.com
 CC: openstack@lists.launchpad.net; salma...@live.com
 
 Hi Emilien and Salman,
 Please, could you upload all the files, errors and conf in
 pastebin or something like that? 
 I have troubles to open in phone :)
 Thank you
 El 01/05/2012 20:39, Emilien Macchi
 emilien.openst...@gmail.com escribió:
 
 Hi,
 
 
 I have a similar problem when I create a network per
 project_id with Quantum.
 
 
 My VMs don't get IP and I can't understand why today.
 
 But when I create a private network for all projects,
 VMs get an IP and all is working well.
 Do you have the same problem ?
 
 
 Salman, I'm interesting about your nova.conf. I can
 see you are using Ryu ?
 Can you tell me more about your use case or
 architecture ?
 
 
 Thanks
 
 
 Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a
 écrit : 
 
 Hi Jorge,
 
 Thanks for looking into the post.
 I have made changes to the nova.conf file so
 that I only use 10.0.0.x network (but the
 problem is still the same). For this
 configuration, I assume that it will give out
 IPs to instances starting from 10.0.0.11. And
 just to inform you, my eth1 is configured to
 be 10.0.0.10 (which is a VM itself, and eth1
 is configured as a host-only network with no
 DHCP) and this interface is plugged in the
 integration bridge used by quantum plugins.
 
 Thanks,
 Salman
 
 PS: Error log of a launched instance is also
 attached

Re: [Openstack] Openstack Essex - Guide for Ubuntu 12.04

[Emilien Macchi]

Loïc,

Le lundi 30 avril 2012 à 13:46 +0200, Loic Dachary a écrit :


 Emilien, in order for people to improve your document you should add the 
 sources of the document to https://github.com/EmilienM/doc-openstack . 
 Otherwise it needs to be copied over and you'll have a hard time 
 incorporating pull requests.


Sorry, I forget to publish it. It's online now.



Regards,


Emilien
___
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] Quantum deployment on Essex

[Emilien Macchi]

Hi livemoon,


 3. Then I use nova-manage network create to create network,
 but the database ova_quantum is empty, I have defined it in
 ovs_quantum_plugin.ini


If your database is empty, it's because the connection between
quantum-server and the database is not working. Check your
ovs_quantum_plugin.ini if you have the good sql_connection parameter.
And restart the service.


 I don't know whether quantum and openvswitch work well together in my
 system. Can you give me any help?


I can help you. I'm very close to release a complete documentation in
which I explain from scratch how to install Essex (with Quantum of
course).


I have to fix some errors, and I release it before monday afternoon.


Best regards


-- 
Emilien Macchi
Phone : +33 685 117 748
Skype : memilien69
Twitter : EmilienMacchi
Website : http://my1.fr
___
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] Quantum Integration Part 3

[Emilien Macchi]

Hi Dan,


Le vendredi 27 avril 2012 à 08:28 -0700, Dan Wendlandt a écrit :



 
 Which mode are you running OVS in?  VLAN or tunneled?  If you are
 using VLAN-mode (default) you need to add some physical interface to
 br-int, so that VLANs are trunked to the physical network.  Is it
 possible that eth1 was also the interface you were using for IP
 communication on the box?  That definitely won't work with OVS or the
 linux bridge.  I'll improve the docs around that to make this more
 clear.  
 


I'm using default mode : VLAN.


 
 
 
 Can you ping me with the error messages (can be offlist)?  I still
 don't understand what you misconfigured, or how you fixed it.  


I actually had an issue when I executed : ovs-vsctl add-port br-int eth1

I checked on the log and could see that Quantum-Agent didn't start.
After inverstigation, it's seem that it was looking for a free physical
interface to bridge. I released eth1 and all worked very good.


 
 
 Great to hear.  As I mentioned in a previous post, Horizon + Quantum
 isn't complete.  You won't be able to create networks using Horizon,
 or boot VMs while specifying a particular set of vNICs.  If you're
 interested in helping this work move forward more quickly, I'm happy
 to put you in touch with the right people.  
 


Of course I am !

I'm writing a documentation to install OpenStack Essex from scratch with
Ubuntu 12.04 with Quantum  OVS. I will to release it soon :-)


Regards


-- 
Emilien Macchi
Phone : +33 685 117 748
Skype : memilien69
Twitter : EmilienMacchi
Website : http://my1.fr
___
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] Quantum Integration Part 3

[Emilien Macchi]

Hi Dan,

Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit :


 Are you able to access the VM via VNC?  If you statically configure
 the IP does it work?  What happens if you run dhcpc manually? 


With a Debian image, I connect to the VM with VNC from dashboard,
configure /etc/network/interfaces manually, ifup eth0, but I can't ping
anything.

Maybe the problem come from my OVS configuration ?

I've created a bridge br-int, and attached eth1 on each server to this
bridge (is it an error from me ?).


Here you can find my nova-network.log :
http://paste.openstack.org/show/13951/

My ovs-vswitchd.log of my nova-compute :
http://paste.openstack.org/show/13952/

My nova-compute.log : http://paste.openstack.org/show/13954/

My Quantum-server.log : http://paste.openstack.org/show/13961/

And finally, the log file of the instance :
http://paste.openstack.org/show/13960/


The errors you can read is in ovs-vwitchd.log with eth1, and on the
quantum-server.log, it's talking about no route for the network.


I continue to investigate today, and please contact me if anyone has an
idea.



Best regards



 
 
 I would look in the nova-network logs and see if you see an errors
 related to DHCP.  
  
 
 - Horizon with Quantum : I can't integrate Quantum in the
 dashboard even with
 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
 
 
 Essex Horizon does not support Quantum.  Its actually not just a
 Horizon thing, it has to do with how the Nova + Quantum integration
 works.  Each Quantum network has to be associated with appropriate
 IPAM subnet, meaning the existing .  For now, you need to create
 networks using nova-manage.  If you want VMs to get the default set of
 NICs, you can then boot them with Horizon.  If you want to specify
 what networks vNICs are plugged into, this is only supported via the
 nova boot command with the --nic option.  I'll flush this out in more
 detail in the Quantum Admin Guide. 
  
 Dan
 
 
 
 
 
 
 
 
 
 -- 
 ~~~
 Dan Wendlandt 
 
 Nicira, Inc: www.nicira.com
 
 twitter: danwendlandt
 ~~~
 
 
 
 

___
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] Quantum Integration Part 3

[Emilien Macchi]

Hi again,


After inverstigation, it finally works.


I have the network on my instances in using Quantum.


The fact was I've follow official OVS documentation, and you should not
follow this direction :

ovs-vsctl add-port br-int eth1


If you see on the logs file of OVS, you can see that the bridge will not
work properly... that's why my instances did not get the network.

I've tried ovs-vsctl del-port br-int eth1, restart all the services
and now, all is working.


I have now a dual-node with : Nova-*, Glance, Quantum (without
authentification), Keystone, and Horizon (without Quantum UI yet).

Next steps : QoS, UI, Isolation testing, and documentation :-)



I will continue to post about Quantum when I will advance in the
project.


 Best regards



Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit :
 Hi Emilien,
 
 
 On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 
 For example, Quantum does not work with Keystone : When
 nova-network send an API call to Quantum-server, the token is
 missing in the HTTP HEADER. I've disabled Keystone at this
 time.
 
 
 
 That is correct.  In the Quantum Admin Guide, it explains some work
 that was done to support Keystone Authn, but notes that this is all
 experimental, as the Quantum API does not support Authz.  This is
 because the only person that calls Quantum in Essex is Nova itself.
  Troy Toman's team is working on Quantum Authz for Folsom, so the API
 can be exposed directly to tenants.  
  
 
 
 - What is working at this time :
 
 - Quantum-Server with MySQL
 - Quantum-Agent (with OVS) on each nova-compute node
 - OVS bridge with eth1
 -  nova-network seems working with Quantum
 
 - What is not working (yet !) :
 
 - When I create an instance (from dashboard or with Nova
 CLI), the network is created with Quantum, an private IP is
 attributed to the instance, but when I check the instance log
 file, the network interface doesn't get an IP adress. Here the
 log : http://paste.openstack.org/show/13821
 
 
 Are you able to access the VM via VNC?  If you statically configure
 the IP does it work?  What happens if you run dhcpc manually? 
 
 
 I would look in the nova-network logs and see if you see an errors
 related to DHCP.  
  
 
 - Horizon with Quantum : I can't integrate Quantum in the
 dashboard even with
 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
 
 
 Essex Horizon does not support Quantum.  Its actually not just a
 Horizon thing, it has to do with how the Nova + Quantum integration
 works.  Each Quantum network has to be associated with appropriate
 IPAM subnet, meaning the existing .  For now, you need to create
 networks using nova-manage.  If you want VMs to get the default set of
 NICs, you can then boot them with Horizon.  If you want to specify
 what networks vNICs are plugged into, this is only supported via the
 nova boot command with the --nic option.  I'll flush this out in more
 detail in the Quantum Admin Guide. 
  
 Dan
 
 
 
 
 
 
 
 
 
 -- 
 ~~~
 Dan Wendlandt 
 
 Nicira, Inc: www.nicira.com
 
 twitter: danwendlandt
 ~~~
 
 
 
 

-- 
Emilien Macchi
Phone : +33 685 117 748
Skype : memilien69
Twitter : EmilienMacchi
Website : http://my1.fr
___
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] Quantum Integration Part 3

[Emilien Macchi]

Hi,


As I can see, nobody has replied to my last e-mail since yesterday, but
I'm sure you want to know the situation.

You can see my architecture :
https://lists.launchpad.net/openstack/pdfD4HBwoSR2Y.pdf

I've finally installed Quantum-server on essex-1 and solved a lot of
smalls issues.

For example, Quantum does not work with Keystone : When nova-network
send an API call to Quantum-server, the token is missing in the HTTP
HEADER. I've disabled Keystone at this time.


- What is working at this time :

- Quantum-Server with MySQL
- Quantum-Agent (with OVS) on each nova-compute node
- OVS bridge with eth1
-  nova-network seems working with Quantum

- What is not working (yet !) :

- When I create an instance (from dashboard or with Nova CLI), the
network is created with Quantum, an private IP is attributed to the
instance, but when I check the instance log file, the network interface
doesn't get an IP adress. Here the log :
http://paste.openstack.org/show/13821
- Horizon with Quantum : I can't integrate Quantum in the dashboard
even with
http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html



Here my nova.conf :

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=10.X.X.40
--ec2_host=10.X.X.40
--rabbit_host=10.X.X.40
--cc_host=10.X.X.40
--nova_url=http://10.X.X.40:8774/v1.1/
--routing_source_ip=10.X.X.40
--glance_api_servers=10.X.X.40:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.68
--sql_connection=mysql://nova:X@10.X.X.40/nova
--ec2_url=http://10.X.X.40:8773/services/Cloud
--keystone_ec2_url=http://10.X.X.40:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--novnc_enable=true
--novncproxy_base_url=http://10.X.X.40:6080/vnc_auto.html
--vncserver_proxyclient_address=10.X.X.40
--vncserver_listen=10.X.X.40

#Quantum :
--network_manager=nova.network.quantum.manager.QuantumManager
--linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
--quantum_use_dhcp=True

--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=192.168.68.0/24
--floating_range=10.X.X.50/24
--network_size=256
--flat_network_dhcp_start=192.168.68.129
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose

And my nova-compute.conf :

--libvirt_type=kvm
--libvirt_ovs_bridge=br-int
--libvirt_vif_type=ethernet
--libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver


For OpenvSwitch, I have followed
http://openvswitch.org/openstack/documentation/

For Quantum :
http://docs.openstack.org/incubation/openstack-network/admin/content/
with some tips.

I use Ubuntu 12.04 up to date with OpenStack Essex.



I can feel that I'm really close to have the network on my VM...


If someone as an idea or can see a mistake... I'm looking forward to
read you.



Best regards


-- 
Emilien Macchi
Phone : +33 685 117 748
Skype : memilien69
Twitter : EmilienMacchi
Website : http://my1.fr
___
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] Quantum Integration Part 3

[Emilien Macchi]

Hi Dan,


Thank you for your quick answer.


I really was looking forward to hear you about my mail.


I have VNC access from the dashboard, and tomorrow I will follow your
tip about manual configuration.



I will let you know about the result.



For the dashboard, I want to try in order to have something graphical in
my report, and I know people loves graphics stuff :-)

But I totally understant that I need to use the Nova CLI, and that's I'm
doing.



Regards



Le mercredi 25 avril 2012 à 10:54 -0700, Dan Wendlandt a écrit :
 Hi Emilien,
 
 
 On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi
 emilien.openst...@gmail.com wrote:
 
 
 For example, Quantum does not work with Keystone : When
 nova-network send an API call to Quantum-server, the token is
 missing in the HTTP HEADER. I've disabled Keystone at this
 time.
 
 
 
 That is correct.  In the Quantum Admin Guide, it explains some work
 that was done to support Keystone Authn, but notes that this is all
 experimental, as the Quantum API does not support Authz.  This is
 because the only person that calls Quantum in Essex is Nova itself.
  Troy Toman's team is working on Quantum Authz for Folsom, so the API
 can be exposed directly to tenants.  
  
 
 
 - What is working at this time :
 
 - Quantum-Server with MySQL
 - Quantum-Agent (with OVS) on each nova-compute node
 - OVS bridge with eth1
 -  nova-network seems working with Quantum
 
 - What is not working (yet !) :
 
 - When I create an instance (from dashboard or with Nova
 CLI), the network is created with Quantum, an private IP is
 attributed to the instance, but when I check the instance log
 file, the network interface doesn't get an IP adress. Here the
 log : http://paste.openstack.org/show/13821
 
 
 Are you able to access the VM via VNC?  If you statically configure
 the IP does it work?  What happens if you run dhcpc manually? 
 
 
 I would look in the nova-network logs and see if you see an errors
 related to DHCP.  
  
 
 - Horizon with Quantum : I can't integrate Quantum in the
 dashboard even with
 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/build-and-configure-openstack-dashboard.html
 
 
 Essex Horizon does not support Quantum.  Its actually not just a
 Horizon thing, it has to do with how the Nova + Quantum integration
 works.  Each Quantum network has to be associated with appropriate
 IPAM subnet, meaning the existing .  For now, you need to create
 networks using nova-manage.  If you want VMs to get the default set of
 NICs, you can then boot them with Horizon.  If you want to specify
 what networks vNICs are plugged into, this is only supported via the
 nova boot command with the --nic option.  I'll flush this out in more
 detail in the Quantum Admin Guide. 
  
 Dan
 
 
 
 
 
 
 
 
 
 -- 
 ~~~
 Dan Wendlandt 
 
 Nicira, Inc: www.nicira.com
 
 twitter: danwendlandt
 ~~~
 
 
 
 

-- 
Emilien Macchi
Phone : +33 685 117 748
Skype : memilien69
Twitter : EmilienMacchi
Website : http://my1.fr
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp