Re: [Openstack] Quantum DHCP support.
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 On Wed, Sep 5, 2012 at 8:12 AM, Mark McClain wrote: > 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 investigate this problem. >> >>> 1. Can you send me the results of ps aux |grep dnsmasq >> nobody 12592 0.0 0.0 28812 1084 ?SSep03 0:00 >> dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces >> --interface=tapbd10a19b-a6 --except-interface=lo >> --domain=openstacklocal >> --pid-file=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/pid >> --dhcp-hostsfile=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/host >> --dhcp-optsfile=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/opts >> --leasefile-ro --dhcp-range=set:tag0,192.168.10.0,static,120s >> >>> 2. Can you also please send the ifconfig. The tap devices for also ip >>> address. Can you please send me ip addr. (my gut feeling is that we do not >>> configure 192.168.30.2 but rather 192.168.10.2. >> >> - ifconfig >> tap0118eb34-42 Link encap:Ethernet HWaddr de:fe:b2:24:cc:0f >> inet6 addr: fe80::dcfe:b2ff:fe24:cc0f/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:33 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:33 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:4770 (4.7 KB) TX bytes:4770 (4.7 KB) >> >> tap0e74b599-a1 Link encap:Ethernet HWaddr 36:42:91:96:44:14 >> inet6 addr: fe80::3442:91ff:fe96:4414/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:7129 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:7140 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:1763458 (1.7 MB) TX bytes:1699484 (1.6 MB) >> >> tap0fb10fc2-62 Link encap:Ethernet HWaddr 92:bf:8b:95:b2:7b >> inet6 addr: fe80::90bf:8bff:fe95:b27b/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:27 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:4302 (4.3 KB) TX bytes:3804 (3.8 KB) >> >> tap38bea316-b0 Link encap:Ethernet HWaddr fa:68:38:20:63:60 >> inet6 addr: fe80::f868:38ff:fe20:6360/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:7091 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:7009 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:500 >> RX bytes:1761232 (1.7 MB) TX bytes:1692872 (1.6 MB) >> >> - ipaddr >> 1: lo: mtu 16436 qdisc noqueue state UNKNOWN >>link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>inet 127.0.0.1/8 scope host lo >>inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: eth0: mtu 1500 qdisc mq state UP qlen >> 1000 >>link/ether d4:ae:52:67:54:a0 brd ff:ff:ff:ff:ff:ff >>inet *.*.*.*/* brd 192.168.100.255 scope global eth0 >>inet6 fe80::d6ae:52ff:fe67:54a0/64 scope link >> valid_lft forever preferred_lft forever >> 3: eth1: mtu 1500 qdisc noop state DOWN qlen 1000 >>link/ether d4:ae:52:67:54:a1 brd ff:ff:ff:ff:ff:ff >> 4: eth2: mtu 1500 qdisc noop state DOWN qlen 1000 >>link/ether 00:1b:21:d8:ef:38 brd ff:ff:ff:ff:ff:ff >> 5: eth3: mtu 1500 qdisc noop state DOWN qlen 1000 >>link/ether 00:1b:21:d8:ef:39 brd ff:ff:ff:ff:ff:ff >> 6: virbr0: mtu 1500 qdisc noqueue >> state DOWN >>link/ether 9e:9f:7d:e9:66:f9 brd ff:ff:ff:ff:ff:ff >>inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 >> 18: tap8f8a93a5-68: mtu 1500 qdisc pfifo_fast >> state DOWN qlen 500 >>link/ether 3a:2c:83:b2:a6:1f brd ff:ff:ff:ff:ff:ff >> 19: tap4002a239-42: mtu 1500 qdisc pfifo_fast >> state DOWN qlen 500 >>link/ether 16:f5:da:f9:ad:a7 brd ff:ff:ff:ff:ff:ff >> 21: tap1be70123-2e: mtu 1500 qdisc pfifo_fast >> state DOWN qlen 500 >>link/ether 52:4d:f8:0c:5e:8c
Re: [Openstack] Quantum DHCP support.
6 fe80::3442:91ff:fe96:4414/64 scope link
valid_lft forever preferred_lft forever
109: tap38bea316-b0: mtu 1500 qdisc
pfifo_fast state UP qlen 500
link/ether fa:68:38:20:63:60 brd ff:ff:ff:ff:ff:ff
inet6 fe80::f868:38ff:fe20:6360/64 scope link
valid_lft forever preferred_lft forever
110: tap0118eb34-42: mtu 1500 qdisc
pfifo_fast state UP qlen 500
link/ether de:fe:b2:24:cc:0f brd ff:ff:ff:ff:ff:ff
inet6 fe80::dcfe:b2ff:fe24:cc0f/64 scope link
valid_lft forever preferred_lft forever
111: tap0fb10fc2-62: mtu 1500 qdisc
pfifo_fast state UP qlen 500
link/ether 92:bf:8b:95:b2:7b brd ff:ff:ff:ff:ff:ff
inet6 fe80::90bf:8bff:fe95:b27b/64 scope link
valid_lft forever preferred_lft forever
115: br-tun: mtu 1500 qdisc noop state DOWN
link/ether 5a:86:d9:8f:14:42 brd ff:ff:ff:ff:ff:ff
Hope this help.
Thanks!
Suzuki
On Tue, Sep 4, 2012 at 8:22 PM, Gary Kotton wrote:
> Hi,
> Just a few more questions:
> 1. Can you send me the results of ps aux |grep dnsmasq
> 2. Can you also please send the ifconfig. The tap devices for also ip
> address. Can you please send me ip addr. (my gut feeling is that we do not
> configure 192.168.30.2 but rather 192.168.10.2.
> Thanks
> Gary
>
>
> On 09/04/2012 12:56 PM, Takaaki Suzuki wrote:
>>>
>>> Can you also please provide sudo ovs-vsctl show?
>>
>> sure.
>>
>> midokura16:~/devstack# ovs-vsctl show
>> d699f1f2-792c-4eb9-8306-32a622316389
>> Bridge br-tun
>> Port br-tun
>> Interface br-tun
>> type: internal
>> Port patch-int
>> Interface patch-int
>> type: patch
>> options: {peer=patch-tun}
>> Bridge br-int
>> Port "tapee78cf13-65"
>> tag: 4
>> Interface "tapee78cf13-65"
>> type: internal
>> Port "tap0e74b599-a1"
>> tag: 3
>> Interface "tap0e74b599-a1"
>> Port "tapc2df9bdf-da"
>> tag: 1
>> Interface "tapc2df9bdf-da"
>> type: internal
>> Port "tapda44c6f5-b4"
>> tag: 3
>> Interface "tapda44c6f5-b4"
>> type: internal
>> Port br-int
>> Interface br-int
>> type: internal
>> Port patch-tun
>> Interface patch-tun
>> type: patch
>> options: {peer=patch-int}
>> Port "tap0fb10fc2-62"
>> tag: 2
>> Interface "tap0fb10fc2-62"
>> Port "tap0118eb34-42"
>> tag: 2
>> Interface "tap0118eb34-42"
>> Port "tapbd10a19b-a6"
>> tag: 2
>> Interface "tapbd10a19b-a6"
>> type: internal
>> Port "tap38bea316-b0"
>> tag: 3
>> Interface "tap38bea316-b0"
>> ovs_version: "1.6.1"
>>
>> Thanks!
>> Suzuki
>>
>> On Tue, Sep 4, 2012 at 6:52 PM, Gary Kotton wrote:
>>>
>>> On 09/04/2012 12:48 PM, Takaaki Suzuki wrote:
>>>>
>>>> Hi Gary
>>>>
>>>> Thank you for your support.
>>>> I share with you information.
>>>
>>>
>>> Can you also please provide sudo ovs-vsctl show?
>>>
>>> Thanks
>>> Gary
>>>
>>>>> 1. can you please do quantum port-list?
>>>>
>>>> quantum --os_token f095d7163a564456b60bf47b078537a7 --os_url
>>>> http://localhost:9696/ port-list
>>>>
>>>> - VM port
>>>> admin_state_up : True
>>>> device_id : d6f9eb16-fb54-4c6c-8c1f-dd7859696910
>>>> device_owner:
>>>> fixed_ips :{"subnet_id":
>>>> "2c6e941e-cf21-40c9-8f1a-37db0e2e9a46", "ip_address": "192.168.30.3"}
>>>> id : 0118eb34-424f-460e-8e12-42ecffb2dad8
>>>> mac_address: fa:16:3e:0d:e6:31
>>>> name:
>>>> network_id: 069f4cfc-3f97-4018-b08e-4a4868f3ca94
>>>> status : ACTIVE
>>>> tenant_id :cf67ba5e70e346b9a080fb349b5e1125
>>>>
>>>> - DHCP agent port
>>>> admin_state_up : True
>>>> device_id :
&g
Re: [Openstack] Quantum DHCP support.
> Can you also please provide sudo ovs-vsctl show?
sure.
midokura16:~/devstack# ovs-vsctl show
d699f1f2-792c-4eb9-8306-32a622316389
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-int
Port "tapee78cf13-65"
tag: 4
Interface "tapee78cf13-65"
type: internal
Port "tap0e74b599-a1"
tag: 3
Interface "tap0e74b599-a1"
Port "tapc2df9bdf-da"
tag: 1
Interface "tapc2df9bdf-da"
type: internal
Port "tapda44c6f5-b4"
tag: 3
Interface "tapda44c6f5-b4"
type: internal
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "tap0fb10fc2-62"
tag: 2
Interface "tap0fb10fc2-62"
Port "tap0118eb34-42"
tag: 2
Interface "tap0118eb34-42"
Port "tapbd10a19b-a6"
tag: 2
Interface "tapbd10a19b-a6"
type: internal
Port "tap38bea316-b0"
tag: 3
Interface "tap38bea316-b0"
ovs_version: "1.6.1"
Thanks!
Suzuki
On Tue, Sep 4, 2012 at 6:52 PM, Gary Kotton wrote:
> On 09/04/2012 12:48 PM, Takaaki Suzuki wrote:
>>
>> Hi Gary
>>
>> Thank you for your support.
>> I share with you information.
>
>
> Can you also please provide sudo ovs-vsctl show?
>
> Thanks
> Gary
>
>>
>>> 1. can you please do quantum port-list?
>>
>> quantum --os_token f095d7163a564456b60bf47b078537a7 --os_url
>> http://localhost:9696/ port-list
>>
>> - VM port
>> admin_state_up : True
>> device_id : d6f9eb16-fb54-4c6c-8c1f-dd7859696910
>> device_owner:
>> fixed_ips :{"subnet_id":
>> "2c6e941e-cf21-40c9-8f1a-37db0e2e9a46", "ip_address": "192.168.30.3"}
>> id : 0118eb34-424f-460e-8e12-42ecffb2dad8
>> mac_address: fa:16:3e:0d:e6:31
>> name:
>> network_id: 069f4cfc-3f97-4018-b08e-4a4868f3ca94
>> status : ACTIVE
>> tenant_id :cf67ba5e70e346b9a080fb349b5e1125
>>
>> - DHCP agent port
>> admin_state_up : True
>> device_id :
>>
>> dhcp72aca792-f411-52a0-a641-defa1b398574-069f4cfc-3f97-4018-b08e-4a4868f3ca94
>> device_owner: network:dhcp
>> fixed_ips : {"subnet_id":
>> "bf07d0cd-7abb-4bf0-83a2-dfc1f3c21f8e", "ip_address": "192.168.10.2"},
>> {"subnet_id": "2c6e941e-cf21-40c9-8f1a-37db0e2e9a46", "ip_address":
>> "192.168.30.2"}
>> id : bd10a19b-a679-4b65-b36b-7beffcdae1ba
>> mac_address: fa:16:3e:6c:f0:b5
>> name: DHCP Agent
>> network_id: 069f4cfc-3f97-4018-b08e-4a4868f3ca94
>> status : ACTIVE
>> tenant_id :cf67ba5e70e346b9a080fb349b5e1125
>>
>>
>>> 2. Is the DHCP agent running (q-dhcp in stackrc)?
>>
>> Yes, DHCP agent running. I added "enable_service q-dhcp".
>>
>>> 3. How did you launch the VM's? Did you use nova boot --nic
>>> net-id=quantum
>>> network ID?
>>
>> I use Horizon for Quantum V2 (https://github.com/amotoki/horizon).
>>
>>> 4. Can you please check that the host files has the MAC address and IP
>>> address of your VM - this is under /opt/stack/data/dhcp//..
>>
>> midokura16:/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94# cat
>> host
>> fa:16:3e:0d:e6:31,192-168-30-3.openstacklocal,192.168.30.3
>> fa:16:3e:6c:f0:b5,192-168-10-2.openstacklocal,192.168.10.2
>> fa:16:3e:6c:f0:b5,192-168-30-2.openstacklocal,192.168.30.2
>>
>> - dnsmasq syslog when launch VM.
>> dnsmasq-dhcp[12592]: DHCPDISCOVER(tapbd10a19b-a6) fa:16:3e:0d:e6:31 no
>> address available
>> dnsmasq-dhcp[12592]: last message repeated 2 times
>> dnsmasq-dhcp[12592]: DHCPDISCOVER(tapbd10a19b-a6) fa:16:3e:15:62:6a no
>> address available
>> dnsmasq-dhcp[12592]: last message repeated 2 times
>>
>> - sudo ip netns exec 069f4cfc-3f97-4018-b08e-4a4868f3ca94 ip link
>> 104: tapbd10a19b-a6: mtu
>> 15
Re: [Openstack] Quantum DHCP support.
Hi TNS I use this information. (http://wiki.openstack.org/QuantumDevstack). You can get devstack plus quantum v2 setup. Thanks! Suzuki On Tue, Sep 4, 2012 at 6:43 PM, Trinath Somanchi 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 wrote: >> >> 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
Re: [Openstack] Quantum DHCP support.
Hi Gary
Thank you for your support.
I share with you information.
> 1. can you please do quantum port-list?
quantum --os_token f095d7163a564456b60bf47b078537a7 --os_url
http://localhost:9696/ port-list
- VM port
admin_state_up : True
device_id : d6f9eb16-fb54-4c6c-8c1f-dd7859696910
device_owner:
fixed_ips :{"subnet_id":
"2c6e941e-cf21-40c9-8f1a-37db0e2e9a46", "ip_address": "192.168.30.3"}
id : 0118eb34-424f-460e-8e12-42ecffb2dad8
mac_address: fa:16:3e:0d:e6:31
name:
network_id: 069f4cfc-3f97-4018-b08e-4a4868f3ca94
status : ACTIVE
tenant_id :cf67ba5e70e346b9a080fb349b5e1125
- DHCP agent port
admin_state_up : True
device_id :
dhcp72aca792-f411-52a0-a641-defa1b398574-069f4cfc-3f97-4018-b08e-4a4868f3ca94
device_owner: network:dhcp
fixed_ips : {"subnet_id":
"bf07d0cd-7abb-4bf0-83a2-dfc1f3c21f8e", "ip_address": "192.168.10.2"},
{"subnet_id": "2c6e941e-cf21-40c9-8f1a-37db0e2e9a46", "ip_address":
"192.168.30.2"}
id : bd10a19b-a679-4b65-b36b-7beffcdae1ba
mac_address: fa:16:3e:6c:f0:b5
name: DHCP Agent
network_id: 069f4cfc-3f97-4018-b08e-4a4868f3ca94
status : ACTIVE
tenant_id :cf67ba5e70e346b9a080fb349b5e1125
> 2. Is the DHCP agent running (q-dhcp in stackrc)?
Yes, DHCP agent running. I added "enable_service q-dhcp".
> 3. How did you launch the VM's? Did you use nova boot --nic net-id=quantum
> network ID?
I use Horizon for Quantum V2 (https://github.com/amotoki/horizon).
> 4. Can you please check that the host files has the MAC address and IP
> address of your VM - this is under /opt/stack/data/dhcp//..
midokura16:/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94# cat host
fa:16:3e:0d:e6:31,192-168-30-3.openstacklocal,192.168.30.3
fa:16:3e:6c:f0:b5,192-168-10-2.openstacklocal,192.168.10.2
fa:16:3e:6c:f0:b5,192-168-30-2.openstacklocal,192.168.30.2
- dnsmasq syslog when launch VM.
dnsmasq-dhcp[12592]: DHCPDISCOVER(tapbd10a19b-a6) fa:16:3e:0d:e6:31 no
address available
dnsmasq-dhcp[12592]: last message repeated 2 times
dnsmasq-dhcp[12592]: DHCPDISCOVER(tapbd10a19b-a6) fa:16:3e:15:62:6a no
address available
dnsmasq-dhcp[12592]: last message repeated 2 times
- sudo ip netns exec 069f4cfc-3f97-4018-b08e-4a4868f3ca94 ip link
104: tapbd10a19b-a6: mtu
1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:6c:f0:b5 brd ff:ff:ff:ff:ff:ff
- sudo ip netns exec 069f4cfc-3f97-4018-b08e-4a4868f3ca94 ip route
192.168.10.0/24 dev tapbd10a19b-a6 proto kernel scope link src 192.168.10.2
192.168.30.0/24 dev tapbd10a19b-a6 proto kernel scope link src 192.168.30.2
- quantum-dhcp agent spawn dnsmasq for test04 network
dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces
--interface=tapbd10a19b-a6 --except-interface=lo
--domain=openstacklocal
--pid-file=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/pid
--dhcp-hostsfile=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/host
--dhcp-optsfile=/opt/stack/data/dhcp/069f4cfc-3f97-4018-b08e-4a4868f3ca94/opts
--leasefile-ro --dhcp-range=set:tag0,192.168.10.0,static,120s
Hope that helped.
Thanks!
Suzuki
On Tue, Sep 4, 2012 at 6:13 PM, Gary Kotton wrote:
> On 09/04/2012 12:03 PM, Takaaki Suzuki wrote:
>>
>> 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.
>
> When a Quantum port is allocated an IP address is selected from one of the
> subnets configured on the network (unless the user has requested more than
> one IP address). The DHCP agent will learn this IP address and update the
> hosts file.
>
> Can you please provide the following information:
> 1. can you please do quantum port-list?
> 2. Is the DHCP agent running (q-dhcp in stackrc)?
> 3. How did you launch the VM's? Did you use nova boot --nic net-id=quantum
> network ID?
> 4. Can you please check that the host files has the MAC address and IP
> address of your VM - this is under /opt/stack/data/dhcp//..
>
> Thanks
> Gary
>>
>> With Dnsmasq running as the DHCP server, I
[Openstack] Quantum DHCP support.
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
Re: [Openstack] Question for Quantum V2 subnet
Hi
Thank you for your comment.
I see. dual stack network need ipv4 and bunch of ipv6 prefix
(link-local, global, temporary global..) on one network.
>> The reason for this is because you can have multiple subnets on the same
>> L2 bcast domain. You can use ip aliasing in order to use multiple subnets on
>> one virtual nic. For example ifconfig eth0:1 a.b.c.d/24; ifconfig eth0:2
>> d.e.f.g/24
This means, It seems like vlan tagging?
Thanks!
Suzuki
On Tue, Aug 14, 2012 at 12:50 PM, Dan Wendlandt wrote:
> In a dual stack deployment there may be a v4 and a v6 subnet on the same
> network.
>
> There's also the case that a service provider has a notion of a public
> network, which is represented by a UUID. After a period of time, they may
> run out of IPs in one subnet, and want to assign another subnet as well,
> without forcing tenants to have to start using a new identifier for the
> public network. Of course, the provider would be responsible for creating
> L3 connectivity between the two subnets.
>
> Others can chime in, but those where the two cases that I remember.
>
> Dan
>
>
> On Mon, Aug 13, 2012 at 8:31 PM, Aaron Rosen wrote:
>>
>> The reason for this is because you can have multiple subnets on the same
>> L2 bcast domain. You can use ip aliasing in order to use multiple subnets on
>> one virtual nic. For example ifconfig eth0:1 a.b.c.d/24; ifconfig eth0:2
>> d.e.f.g/24
>>
>> Aaron
>>
>>
>> On Mon, Aug 13, 2012 at 7:52 PM, Takaaki Suzuki
>> wrote:
>>>
>>> Hi all.
>>>
>>> I have one question. I prepared devstack with Qauntum V2.
>>> Now I can create Subnet for Network.
>>> And I can add multiple Subnet for one Network. VM can use multiple
>>> subnet for one virtual NIC?
>>> Why quantum v2 can create multiple subnet for one Network?
>>>
>>> quantum --os_token 1b73ace152c440ea939c2329fd115e56 --os_url
>>> http://localhost:9696/ net-list
>>>
>>> ++--+---++--+--+
>>> | admin_state_up | id | name |
>>> status | subnets | tenant_id
>>> |
>>>
>>> ++--+---++--+--+
>>> | True | d7a8106c-7ca6-4302-a065-6a87c859ed9c | test
>>> | ACTIVE | 474ea30c-9337-4f48-854c-9f572538a44c |
>>> 4fb66e3355304be5a6f3340d7067b369 |
>>> | |
>>>|| |
>>> 52ffda8c-61aa-465b-ae62-1ef57e9bed85 |
>>> |
>>> | |
>>>|| |
>>> 9a659285-c6b1-4e6f-b3f0-c3e37341e0be |
>>>|
>>>
>>> quantum --os_token 1b73ace152c440ea939c2329fd115e56 --os_url
>>> http://localhost:9696/ subnet-list
>>>
>>> +--+--+---+--+++--+--+
>>> | allocation_pools | cidr
>>>| gateway_ip| id | ip_version
>>> | name | network_id | tenant_id
>>> |
>>>
>>> +--+--+---+--+++--+--+
>>> | {"start": "192.168.100.2", "end": "192.168.100.254"} |
>>> 192.168.100.0/24 | 192.168.100.1 |
>>> 474ea30c-9337-4f48-854c-9f572538a44c | 4 | test01 |
>>> d7a8106c-7ca6-4302-a065-6a87c859ed9c |
>>> 4fb66e3355304be5a6f3340d7067b369 |
>>> | {"start": "192.168.210.2", "end": "192.168.210.254"} |
>>> 192.168.210.0/24 | 192.168.210.1 |
>>> 52ffda8c-61aa-465b-ae62-1ef57e9bed85 | 4 | test03 |
>>> d7a8106c-7ca6-4302-a065-6a87c859ed9c |
>>> 4fb66e3355304be5a6f3340d7067b369 |
>>> | {"start": "192.168.200.2", "end": "192.168.200.254"} |
>>> 192.168.200.0/24 | 192.168.200.1 |
>>> 9a659285-c6b1-4e6f-b3f0-c3e37341e0be |
[Openstack] Question for Quantum V2 subnet
Hi all.
I have one question. I prepared devstack with Qauntum V2.
Now I can create Subnet for Network.
And I can add multiple Subnet for one Network. VM can use multiple
subnet for one virtual NIC?
Why quantum v2 can create multiple subnet for one Network?
quantum --os_token 1b73ace152c440ea939c2329fd115e56 --os_url
http://localhost:9696/ net-list
++--+---++--+--+
| admin_state_up | id | name |
status | subnets | tenant_id
|
++--+---++--+--+
| True | d7a8106c-7ca6-4302-a065-6a87c859ed9c | test
| ACTIVE | 474ea30c-9337-4f48-854c-9f572538a44c |
4fb66e3355304be5a6f3340d7067b369 |
| |
|| |
52ffda8c-61aa-465b-ae62-1ef57e9bed85 |
|
| |
|| |
9a659285-c6b1-4e6f-b3f0-c3e37341e0be |
|
quantum --os_token 1b73ace152c440ea939c2329fd115e56 --os_url
http://localhost:9696/ subnet-list
+--+--+---+--+++--+--+
| allocation_pools | cidr
| gateway_ip| id | ip_version
| name | network_id | tenant_id
|
+--+--+---+--+++--+--+
| {"start": "192.168.100.2", "end": "192.168.100.254"} |
192.168.100.0/24 | 192.168.100.1 |
474ea30c-9337-4f48-854c-9f572538a44c | 4 | test01 |
d7a8106c-7ca6-4302-a065-6a87c859ed9c |
4fb66e3355304be5a6f3340d7067b369 |
| {"start": "192.168.210.2", "end": "192.168.210.254"} |
192.168.210.0/24 | 192.168.210.1 |
52ffda8c-61aa-465b-ae62-1ef57e9bed85 | 4 | test03 |
d7a8106c-7ca6-4302-a065-6a87c859ed9c |
4fb66e3355304be5a6f3340d7067b369 |
| {"start": "192.168.200.2", "end": "192.168.200.254"} |
192.168.200.0/24 | 192.168.200.1 |
9a659285-c6b1-4e6f-b3f0-c3e37341e0be | 4 | test02 |
d7a8106c-7ca6-4302-a065-6a87c859ed9c |
4fb66e3355304be5a6f3340d7067b369 |
+--+--+---+--+++--+--+
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
Re: [Openstack] Live Migration with libvirtError
Hi
Probably, before We had same problem.
Could you check libvirt log and resolve your host domain and nova.conf
vncserver_listen part?
(vncserver_listen=0.0.0.0)
Thanks!
Suzuki
On Thu, Aug 9, 2012 at 6:27 PM, Leander Bessa Beernaert
wrote:
> Hello,
>
> I'm no expert on the subject, but i think you should just use "mount -t nfs
> 172.18.32.7:/ /var/lib/nova/instances" instead of "mount -t nfs
> 172.18.32.7:/var/lib/nova/instances /var/lib/nova/instances". Also from the
> stack trace it seems your libvirtd is not running.
>
> On Thu, Aug 9, 2012 at 7:55 AM, 王鹏 wrote:
>>
>> HI everyone,
>> when I test live migration use NFS ,that's my sitting according to
>>
>> http://docs.openstack.org/essex/openstack-compute/admin/content/configuring-live-migrations.html
>>
>> 1.add this line /var/lib/nova/instances *(rw,sync,fsid=0,no_root_squash)
>> in /etc/exports
>> 2.mount -t nfs 172.18.32.7:/var/lib/nova/instances /var/lib/nova/instances
>> at compute
>> and change some setting in libvirt.conf and libvird-bin.conf add a option
>> -l
>> 3.restart service
>>
>> then I create instance in compute node ,find error
>> that's my nova-compute.log as follow:
>> 2012-08-09 13:13:03 ERROR nova.manager [-] Error during
>> ComputeManager.update_available_resource: Failed to connect socket to
>> '/var/run/libvirt/libvirt-sock': No such file or directory
>> 2012-08-09 13:13:03 TRACE nova.manager Traceback (most recent call last):
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/manager.py", line 155, in
>> periodic_tasks
>> 2012-08-09 13:13:03 TRACE nova.manager task(self, context)
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2409, in
>> update_available_resource
>> 2012-08-09 13:13:03 TRACE nova.manager
>> self.driver.update_available_resource(context, self.host)
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 1936, in update_available_resource
>> 2012-08-09 13:13:03 TRACE nova.manager 'vcpus_used': self.get_vcpu_used(),
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 1742, in get_vcpu_used
>> 2012-08-09 13:13:03 TRACE nova.manager for dom_id in
>> self._conn.listDomainsID():
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 298, in _get_connection
>> 2012-08-09 13:13:03 TRACE nova.manager self.read_only)
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
>> 341, in _connect
>> 2012-08-09 13:13:03 TRACE nova.manager return libvirt.openAuth(uri, auth,
>> 0)
>> 2012-08-09 13:13:03 TRACE nova.manager File
>> "/usr/lib/python2.7/dist-packages/libvirt.py", line 102, in openAuth
>> 2012-08-09 13:13:03 TRACE nova.manager if ret is None:raise
>> libvirtError('virConnectOpenAuth() failed')
>> 2012-08-09 13:13:03 TRACE nova.manager libvirtError: Failed to connect
>> socket to '/var/run/libvirt/libvirt-sock': No such file or directory
>> 2012-08-09 13:13:03 TRACE nova.manager
>>
>> what's /var/run/libvirt/libvirt-sock'?
>> why this error?
>>
>>
>> ___
>> 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
>
___
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 launch VM with XCP plus OpenStack Essex release version
Hi John. Thank you for your support again :) > Also, what sort of VM are you trying to launch? Is it a three part image with > external kernel? Yes, I use this VM images. ttylinux-uec-amd64-12.1_2.6.35-22_1 - ttylinux-uec-amd64-12.1_2.6.35-22_1.img - ttylinux-uec-amd64-12.1_2.6.35-22_1-initrd - ttylinux-uec-amd64-12.1_2.6.35-22_1-loader cirros-0.3.0-x86_64-uec - cirros-0.3.0-x86_64-blank.img - cirros-0.3.0-x86_64-initrd - cirros-0.3.0-x86_64-vmlinuz I'll check use EXT3 local SR and "kpartx" command. Thanks! Suzuki On Mon, Jun 11, 2012 at 7:03 PM, John Garbutt wrote: > It is not well documented (I promise to work on that soon), but you should > use an EXT3 local SR, not LVM. It is certainly worth moving to EXT3, just to > rule a few things out. > > I see you are using the Ubuntu XCP packages. This is a version of XenAPI I > have not yet started doing much QA on, but I did get a VM started OK when > using EXT3. However, I used to get LVM working for the basics with earlier > versions of xenapi, so I am shocked that is totally broken on the latest. > > Also, what sort of VM are you trying to launch? Is it a three part image with > external kernel? > > If you want to get going with XenAPI and OpenStack quickly, I would recommend > DevStack and XenServer 6.0.2 (free download) or XCP 1.5 Beta. That is the > combination I am testing today. Hoping to test Ubuntu XCP and OpenStack in > the next few weeks. > > Thanks, > John > > PS: > I think the problem you are hitting is because there was a recent change in > XCP/XenAPI where mounting the VDI into dom0 no longer automatically exposes > the partitions of that disk to the Dom0 Kernel, so you need to use kpartx (or > similar) to mount to appropriate partition. I can see you are hit this > because the device returned is "/dev/sm//" rather than > "/dev/sda1" or something like that. I got normal VMs working OK despite this, > but have not yet gone through all the XenAPI plugins to ensure all the issues > are fixed. > >> -Original Message- >> From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net >> [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] >> On Behalf Of Takaaki Suzuki >> Sent: 11 June 2012 04:07 >> To: openstack@lists.launchpad.net >> Cc: dev; Ryu Ishimoto >> Subject: [Openstack] Can't launch VM with XCP plus OpenStack Essex release >> version >> >> Hi all. >> >> I need your support again. >> We had this parted error with XCP plus OpenStack Essex release version. >> Nova can't launch VM with XCP with OpenStack. I use SR with Local LVM. >> Did you get parted command error? If you have any idea. >> Please let me know. >> >> -- >> nova-compute log: >> -- >> 2012-06-11 11:42:49 DEBUG nova.compute.manager >> [req-85e34ab4-885c-4006-ac22-47b0323b9e21 >> 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] >> [instance: ae09a885-ab5c-4b10-9582-73423932e40c] Deallocati ng network for >> instance from (pid=3057) _deallocate_network >> /usr/lib/python2.7/dist-packages/nova/compute/manager.py:616 >> 2012-06-11 11:42:49 DEBUG nova.rpc.amqp >> [req-85e34ab4-885c-4006-ac22-47b0323b9e21 >> 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] >> Making asynchronous cast on network... from (pid=3057) cast /usr/l >> ib/python2.7/dist-packages/nova/rpc/amqp.py:346 >> 2012-06-11 11:42:49 ERROR nova.rpc.amqp >> [req-85e34ab4-885c-4006-ac22-47b0323b9e21 >> 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] >> Exception during message handling >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp Traceback (most recent call last): >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp File >> "/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py", line 252, in >> _process_data >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp rval = >> node_func(context=ctxt, **node_args) >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp File >> "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp return f(*args, **kw) >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp File >> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 177, in >> decorated_function >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp sys.exc_info()) >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp File >> "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ >> 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() >
[Openstack] Can't launch VM with XCP plus OpenStack Essex release version
Hi all. I need your support again. We had this parted error with XCP plus OpenStack Essex release version. Nova can't launch VM with XCP with OpenStack. I use SR with Local LVM. Did you get parted command error? If you have any idea. Please let me know. -- nova-compute log: -- 2012-06-11 11:42:49 DEBUG nova.compute.manager [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] [instance: ae09a885-ab5c-4b10-9582-73423932e40c] Deallocati ng network for instance from (pid=3057) _deallocate_network /usr/lib/python2.7/dist-packages/nova/compute/manager.py:616 2012-06-11 11:42:49 DEBUG nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Making asynchronous cast on network... from (pid=3057) cast /usr/l ib/python2.7/dist-packages/nova/rpc/amqp.py:346 2012-06-11 11:42:49 ERROR nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Exception during message handling 2012-06-11 11:42:49 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/rpc/amqp.py", line 252, in _process_data 2012-06-11 11:42:49 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped 2012-06-11 11:42:49 TRACE nova.rpc.amqp return f(*args, **kw) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 177, in decorated_function 2012-06-11 11:42:49 TRACE nova.rpc.amqp sys.exc_info()) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 171, in decorated_function 2012-06-11 11:42:49 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 651, in run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp do_run_instance() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/utils.py", line 945, in inner 2012-06-11 11:42:49 TRACE nova.rpc.amqp retval = f(*args, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 650, in do_run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._run_instance(context, instance_uuid, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 451, in _run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._set_instance_error_state(context, instance_uuid) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 432, in _run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._deallocate_network(context, instance) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 429, in _run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp injected_files, admin_password) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 592, in _spawn 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._legacy_nw_info(network_info), block_device_info) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 184, in spawn 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._vmops.spawn(context, instance, image_meta, network_info) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/vmops.py", line 359, in spawn 2012-06-11 11:42:49 TRACE nova.rpc.amqp undo_mgr.rollback_and_reraise(msg=msg) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/utils.py", line 1714, in rollback_and_reraise 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._rollback() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/vmops.py", line 346, in spawn 2012-06-11 11:42:49 TRACE nova.rpc.amqp vdis = crea
[Openstack] XCP with DevStack
Hi all. I need your knowledge. :) I prepared XCP plus OpenvSwitch with Ubuntu precise on own environment. And I want to prepare DevStack for XCP(Ubuntu). https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md I don't understand localrc network settings part. The script launched DevStackOSDomU. after that network settings part failed. If you know any other DevStack/OpenStack for XCP installation or configuration document. Please let me know. Thanks! -- Midokura Japan 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
