Open Stack

Thank you for for your answer.
Yes, openvswitch (ovsdb-server and ovs-vswitchd) is launched on both the computer and networker nodes (not the controller). 

On the computer node:
#ovs-vsctl show
ddb0b9e5-3112-40d9-8f40-e4619c957e06
    Bridge "br-eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "eth1"
            Interface "eth1"
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-eth1"
            Interface "int-br-eth1"
    ovs_version: "1.11.0"


On networker node:
#ovs-vsctl show
566dca7e-e1da-40fc-93cb-3f077cd7b7e2
    Bridge br-int
        Port "int-br-eth2"
            Interface "int-br-eth2"
        Port br-int
            Interface br-int
                type: internal
        Port "tap4a791b41-d8"
            tag: 1
            Interface "tap4a791b41-d8"
    Bridge br-ex
        Port "tapa48e20db-cc"
            Interface "tapa48e20db-cc"
        Port "eth1"
            Interface "eth1"
        Port br-ex
            Interface br-ex
                type: internal
    Bridge "br-eth2"
        Port "phy-br-eth2"
            Interface "phy-br-eth2"
        Port "eth2"
            Interface "eth2"
        Port "br-eth2"
            Interface "br-eth2"
                type: internal
    ovs_version: "1.11.0"

libvirt is running on the computer node, no logs in log file...

I'm trying to do the use case "Provider router with private networks" of the guide. 
On the networker:
 - eth1 is connected to external network
 - eth0 is the "management network"
 - eth2 is the "data network"
On the computer:
 - eth0 is the "management network"
 - eth1 is the 'data network"

Thanks again
Anne-Claire

>
>-----Message d'origine-----
>De : Diop Samba [mailto:samba.diop at nagra.com] 
>Envoyé : jeudi 23 janvier 2014 12:54
>À : Gerard, Anne-Claire; openstack at lists.openstack.org
>Objet : RE: Unable to launch a vm
>
>Hello,
>
>You did not  mention that openvswitch is running.
>You should have following services running :
>
>On network and compute node :
>
>Openvswitch which runs :
>	ovsdb-server
>	ovs-vswitchd
>
>To verify that everything is you should have something like this:
># ovs-vsctl show
>0e781dce-6f12-4a47-994a-55b77a8263cb
>    Bridge br-int
>        Port "tap04d164cc-64"
>            tag: 32
>            Interface "tap04d164cc-64"
>                type: internal
>    Bridge br-ex
>        Port br-ex
>            Interface br-ex
>                type: internal
>        Port phy-br-ex
>            Interface phy-br-ex
>        Port "eth1"
>            Interface "eth1"
>    ovs_version: "1.11.0"
> #
>
>Make sure that libvirtd is running and check the logs.
>
>
>Good luck.
>Samba.
>
>
>
>
>> -----Original Message-----
>> From: Gerard, Anne-Claire [mailto:anne-claire.gerard at capgemini.com]
>> Sent: jeudi 23 janvier 2014 12:04
>> To: openstack at lists.openstack.org
>> Subject: [Openstack] Unable to launch a vm
>> 
>> Hi all,
>> 
>> I have followed the guide "OpenStack Installation Guide for Red Hat 
>> Enterprise Linux, CentOS, and Fedora  - havana" and I am trying to 
>> launch an instance.
>> 
>> The configuration has three nodes with CentOs 6.5, one controller 
>> node, one networker node and one compute node.
>> The controller node hosts the following services:
>>  - glance
>>  - rabbitmq
>>  - keystone
>>  - nova-scheduler
>>  - nova-api
>>  - nova-cert
>>  - nova-consoleauth
>>  - neutron server
>> The networker node hosts the following services:
>>  - neutron-openvswith-agent
>>  - neutron-dhcp-agent
>>  - neutron-l3-agent
>>  - neutron-metadata-agent
>> The computer node hosts the following services:
>>  - neutron-openvswitch-agent
>>  - libvirt
>>  - nova-compute
>> 
>> I am using nova without the conductor, I wasn't able to make it work 
>> (suspicious log in compute.log on compute node:
>> WARNING nova.conductor.api [req-554e681f-2705-4503-b6f0-2d1db62d6e6d
>> None None] Timed out waiting for nova-conductor. Is it running? Or did 
>> this service start before nova-conductor?
>> ). So, I have configured nova with the use_local=true configuration 
>> option in nova.conf files.
>> 
>> When trying to boot an instance, the VM is stuck in scheduling and 
>> nothing happens.
>> To launch the instance, I am running the command nova boot --flavor 1 
>> -- key_name mykey --image 4a784fde-cb0c-4cc6-af59-507748aa9247 -- 
>> security_group default test
>> 
>> I have been trying to track what is happening mainly by investigating the logs.
>> So far, what I have understood is:
>>   - request is being received by nova-api on controller node
>>   - nova-api sends a message through rabbitmq to the scheduler
>>   - nova-scheduler determines the host on which the vm should be 
>> launched (computer node)
>>   - nova-scheduler sends a message through rabbitmq with routing key 
>> compute.computer and that's it. In rabbitmq I have seen the message 
>> compute.computer but I have no idea who consumes it.
>> There is no error in the different logs and there is no log at all for 
>> neutron services on networker node nor for nova-compute on computer node.
>> 
>> Can anyone tell me what is the problem?
>> 
>> Thanks,
>> Anne-Claire
>> This message contains information that may be privileged or 
>> confidential and is the property of the Capgemini Group. It is 
>> intended only for the person to whom it is addressed. If you are not 
>> the intended recipient, you are not authorized to read, print, retain, 
>> copy, disseminate, distribute, or use this message or any part 
>> thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
>> 
>> 
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe : 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.