All-
The OpenStack Networking team is happy to announce that the Quantum project
will be changing its name to Neutron. You'll soon see Neutron in lots of places
as we work to implement the name change within OpenStack.
mark
___
Mailing list: https://l
Will-
The metadata service in Folsom will only work when overlapping IP ranges are
disabled (see:
http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html).
For Grizzly, we have added metadata service for overlapping networks. This
feature is currently available in
Thomas-
You are not missing anything. The DHCP hostname is auto generated because Nova
does not currently provide this information to Quantum when creating the port
and Quantum does not have the ability to query the Nova API. Quantum and Nova
should not directly access the other component's d
I'm glad it works with the newer version. I was thinking that might be case.
I've filed a bug, so that we can document the minimum dnsmasq version.
mark
On Nov 30, 2012, at 6:14 PM, Robert van Leeuwen
wrote:
>>> What version of dnsmasq are you running?
>> dnsmasq-2.48-6.el6.x86_64
>
> Mark
Robert-
Yes the tag setting should be in the opts file. What version of dnsmasq are
you running? Also can you get a tcpdump of the DHCP traffic?
(tcpdump -vvv -n -i port 67 or port 68)
Thanks,
mark
On Nov 30, 2012, at 4:31 AM, Robert van Leeuwen
wrote:
> Hi,
>
> I'm having some troub
at 10:40 PM, Takaaki Suzuki wrote:
>> Hi Mark.
>>
>> Thank you for your comment.
>> I'll try again.
>>
>> So, I just want to make sure.
>> Is this function support in Quantum folsom release?
>>
>> Thanks!
>> Suzuki
>>
>&g
I think we've isolated the problem. Until we can get the patch posted, try
this workaround:
1) create the subnets
2) kill dnsmasq instance for the network
3) restart dhcp_agent
If this does not work, let me know,
mark
On Sep 4, 2012, at 6:47 PM, Takaaki Suzuki wrote:
> Thank you for investi
7 matches
Mail list logo
