← Back to team overview

openstack team mailing list archive

Re: Quantum Integration Part 3

 

All fixed up, let me know if you have any other issues. Thanks Jim Blair
for the help.

Anne

On Fri, Apr 27, 2012 at 10:57 AM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:

> Ah, the Jenkins job copies to "incubated" and it should be "incubation" -
> fixing now.
> Anne
>
>
> On Fri, Apr 27, 2012 at 10:30 AM, Dan Wendlandt <dan@xxxxxxxxxx> wrote:
>
>> Hi Alan,
>>
>> That's a good question.  I had assumed that my recent commits to
>> https://www.github.com/openstack/openstack-manuals would
>> automatically propagate to
>> http://docs.openstack.org/incubation/openstack-network/admin/content/index.html, but that doesn't seem to have happened for the latest commits.
>>
>> Anne Gentle, can you help out here?  Thanks!
>>
>> Dan
>>
>> On Thu, Apr 26, 2012 at 3:30 PM, Alan Kavanagh <
>> alan.kavanagh@xxxxxxxxxxxx> wrote:
>>
>>> **
>>> Hi Dan
>>>
>>> When will the revised Quantum Admin Guide be posted?
>>>
>>> Alan
>>>
>>>  ------------------------------
>>> *From:* openstack-bounces+alan.kavanagh=ericsson.com@xxxxxxxxxxxxxxxxxxx[mailto:
>>> openstack-bounces+alan.kavanagh=ericsson.com@xxxxxxxxxxxxxxxxxxx] *On
>>> Behalf Of *Dan Wendlandt
>>> *Sent:* April-25-12 1:55 PM
>>> *To:* Emilien Macchi
>>> *Cc:* openstack@xxxxxxxxxxxxxxxxxxx
>>> *Subject:* Re: [Openstack] Quantum Integration Part 3
>>>
>>>  Hi Emilien,
>>>
>>> On Wed, Apr 25, 2012 at 9:13 AM, Emilien Macchi <
>>> emilien.openstack@xxxxxxxxx> 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
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>>
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com
>> twitter: danwendlandt
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>

References