Ask Your Question

danwent's profile - activity

2017-12-03 11:52:56 -0500 received badge  Notable Question (source)
2017-06-25 21:04:43 -0500 received badge  Popular Question (source)
2013-04-19 18:32:19 -0500 answered a question VMs get DHCP server's address as a default gateway

yeah, i've seen this before.

My understand is that this happens on redhat/centos versions that have a version of dnsmasq that is older than what quantum is expecting. basically, the config we push to dnsmasq is not interpreted correctly, meaning dnsmasq does its default behavior of using its own IP as the gateway. i'll convert this to a bug, as we should either check the dnsmasq version and push the right config, or document the version requirements around dnsmasq better.

On Fri, Apr 19, 2013 at 10:35 AM, AnasASO < question227068@answers.launchpad.net > wrote:

New question #227068 on quantum: https://answers.launchpad.net/quantum/+question/227068 (https://answers.launchpad.net/quantum...)

I'm getting a weird behaviour. When I run a VM, it gets the address of DHCP server (dnsmasq) as the default gateway !!!! My install is as follow : - two physical nodes, each with two NICs (one for management network, and the other for Data network (VMs) ) - OS : CentOS 6.4 - L2 plugin : Linuxbridge - namespaces=False - dhcp-agent is running on the controller node (all openstack services : nova, glance, cinder, quantum-server, ...) - l3-agent is runnig on the compute node Because of the misconfigured gateway, I can't access to my VMs using floating IPs, till I change the default gateway myself(I can access the VMs using their fixed IPs) any idea what's wrong? if you need any additional information, you can ask. thanks in advance


You received this question notification because you are an answer contact for quantum.


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

2013-04-13 22:43:11 -0500 answered a question 'quantum floatingip-list' does not seem match 'quantum port-list'

there are two different types of port when you are talking about floating ips.

one is a "hidden port", visible only to admin users, that represents the IP allocation on the "external network" (i.e., the public IP for the floating IP).

the other is the "associated" port, which is the internal port (usually a VM VIF) that the floating IP is mapped to (i.e., the private IP for the floating IP). It is possible to allocate a floating IP that is unassociated with an internal port, but then to associate or disassociate on demand via the API.

dan

On Fri, Apr 12, 2013 at 10:16 PM, digitalwonk < question226594@answers.launchpad.net > wrote:

New question #226594 on quantum: https://answers.launchpad.net/quantum/+question/226594 (https://answers.launchpad.net/quantum...)

When I do a 'quantum floatingip-list', the number of ports assigned (10) is significantly less that the number of ports with floating ips shown in 'quantum port-list' (95). Is that expected?

Even if I exclude the ports that are assigned to tenant router gateways and vms, I still have some number of ports that I don't know where they come from (76 ports). I attempted to port-delete them, but I receive a "Port xxx has owner network:floatingip and therefore cannot be deleted directly via the port API." Where are these assigned or are these somehow orphan ports/ips?

If it matters, I'm still on folsom.

Thanks, Ed


You received this question notification because you are an answer contact for quantum.


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

2013-04-12 05:37:46 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

Sumit, this is because the order is actually the other way around. Think of it as being that nova contacts quantum to create ports, then when the nova virt layer is actually creating the VM, it looks at how many ports exist for instance X, and creates that many items in the XML. Since both ports are created with the same instance-id as the port's device_id, the underlying virt layer is tricked into thinking there are supposed to be two interfaces.

2013-04-11 15:23:43 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

Ok, could you possibly post the portions of the relevant nova-compute + quantum logs, along with a port-show for each of the duplicate ports (or some other way of us seeing the UUIDs of the duplicate ports, and the instance id of the vm)? thanks.

On Thu, Apr 11, 2013 at 12:36 AM, Sumit Naiksatam < question225158@answers.launchpad.net > wrote:

Question #225158 on quantum changed: https://answers.launchpad.net/quantum/+question/225158 (https://answers.launchpad.net/quantum...)

Sumit Naiksatam posted a new comment: Here is the nova log as we reproduced this: http://paste.openstack.org/show/35783/

Sorry Dan, I could not add any additional log statements in this run, but I am looking at the setup.


You received this question notification because you are an answer contact for quantum.


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

2013-04-03 00:20:27 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

Thanks for the update Sumit.

Not sure if you saw my comments above, but it might be good to insert some logging statements into the nova code that talks to quantum, otherwise i'm not sure that we'll have much more information to go on than the info already posted in the question. The quantum logs would be useful as well.

Dan

On Tue, Apr 2, 2013 at 4:06 PM, Sumit Naiksatam < question225158@answers.launchpad.net > wrote:

Question #225158 on quantum changed: https://answers.launchpad.net/quantum/+question/225158 (https://answers.launchpad.net/quantum...)

Sumit Naiksatam posted a new comment: This happened again today, however the automation run got wiped out after the test failure (on account of the dual IPs). We have changed the automation script so that this does not happen the next time. Will investigate once we reproduce this again and have live system. Sorry, I am not providing too much additional information, but I just wanted to report back.


You received this question notification because you are an answer contact for quantum.


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

2013-04-02 19:04:06 -0500 answered a question How to create a Floating IP pool and how to associate one of the floating IP's from the pool to a port on a VM

http://docs.openstack.org/trunk/openstack-network/admin/content/l3_workflow.html (http://docs.openstack.org/trunk/opens...)

On Tue, Apr 2, 2013 at 11:06 AM, Ritesh Shetty < question225720@answers.launchpad.net > wrote:

New question #225720 on quantum: https://answers.launchpad.net/quantum/+question/225720 (https://answers.launchpad.net/quantum...)

How to create a Floating IP pool and how to associate one of the floating IP's from the pool to a port on a VM


You received this question notification because you are an answer contact for quantum.


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

2013-03-27 21:04:16 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

Sumit, if you are able to see this predictably, can you insert some additional logging calls to understand the flow that leads to these duplicate ports? For example, are both calls made within the same call to allocate_for_instance (e.g., is the the nets array somehow containing the same network twice?). Or is this the result of multiple calls to allocate_for_instance? Logging a msg with the instance-id when we enter allocate_for_instance, then having a log message indicating the quantum port ids allocated for the instance-id would be valuable (I would argue that latter should be something we actually push to nova for inclusion, as it seems appropriate at the INFO or DEBUG level.

2013-03-27 16:55:25 -0500 answered a question Is there a way to convert a nova-network install over to quantum?

Hi Ryan,

Unfortunately, there's not automated way to do this. I know garyk has talked about working on something along these lines in the future.

Its also worth pointing out that the functional equivalent to nova multi-host will only be available in havana for quantum, though grizzly quantum is able to spread load across multiple network nodes for processing l3

dan

On Wed, Mar 27, 2013 at 8:26 AM, Ryan Wallner < question225282@answers.launchpad.net > wrote:

New question #225282 on quantum: https://answers.launchpad.net/quantum/+question/225282 (https://answers.launchpad.net/quantum...)

I am using Rackspace Opencenter to install a Folsom based OpenStack deployment for various reasons, what I would like to do is translate this install over to use quantum instead of the flatDHCP multi_host mode network that it defaults to. I was wondering if someone had done this before and or knew if it there was a tried and true way of doing so, or is it "take a look at the docs and uninstall/reconfigure what is needed"

Thanks


You received this question notification because you are an answer contact for quantum.


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

2013-03-26 04:31:13 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

during the portion of the log where you are deleting vms, i see two quantum exceptions, but they are "port not found" errors, that seem correlated to nova instance not found errors, and aren't the port-ids mentioned above, so I doubt it is related.

2013-03-26 03:58:04.965 ERROR nova.network.quantumv2.api [req-b6fe4986-507d-4735-a504-adbf4386b5bc c9ae6c830b3b4d40925e5fe23f671893 ebacbc9c99f84607920b2ac749608623] Failed to delete quantum port 03347623-a4c8-473f-bde6-845d19c0009c 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api Traceback (most recent call last): 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/nova/network/quantumv2/api.py", line 309, in deallocate_for_instance 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api quantumv2.get_client(context).delete_port(port['id']) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 102, in with_params 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api ret = self.function(instance, args, *kwargs) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 236, in delete_port 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api return self.delete(self.port_path % (port)) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 521, in delete 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api headers=headers, params=params) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 510, in retry_request 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api headers=headers, params=params) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 455, in do_request 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api self._handle_fault_response(status_code, replybody) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 436, in _handle_fault_response 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api exception_handler_v20(status_code, des_error_body) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 75, in exception_handler_v20 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api raise exceptions.QuantumClientException(message=error_dict) 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api QuantumClientException: Port 03347623-a4c8-473f-bde6-845d19c0009c could not be found on network None 2013-03-26 03:58:04.965 1290 TRACE nova.network.quantumv2.api

2013-03-26 03:06:40 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

To me, this says output says that 108 and 109 are actually on different ports.

Can you do a quantum show-port <port-uuid> for both fo the ports below? In particular, I want to confirm that they have the same device_id.

From the looks of it, this looks to be an issue in Nova, as quantum itself has not actually allocated multiple ips to a port. Rather, pending the output i've requested above, it seems like nova created two ports for an instance, rather than one.

Looking through your logs, there are an extremely high number of exceptions and tracebacks in your nova log. I wonder if any of those failures caused an instance to be respawned, without the quantum port for the initial creation being cleaned up.

Unfortunately, the nova-compute log seems filled with tracebacks unrelated to quantum, so its hard to isolate a possible cause of the issue you're seeing above. It seems like you have some database schema sync issues at the least. I'd suggest cleaning up these issues and seeing if you can still repro this.

Dan

On Mon, Mar 25, 2013 at 7:31 PM, shu, xinxin < question225158@answers.launchpad.net > wrote:

Question #225158 on quantum changed: https://answers.launchpad.net/quantum/+question/225158 (https://answers.launchpad.net/quantum...)

shu, xinxin posted a new comment: i list ports of the instance which has two fixed ips, below is output:

+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------------+ | id | name | mac_address | fixed_ips |

+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------------+ | 1b93218d-2eb2-4064-b70c-d6562724fc47 | | fa:16:3e:10:7d:8c | {"subnet_id": "24be33c7-64f9-4695-811d-33eeb4ad75da", "ip_address": "172.16.100.108"} | | fc44d25d-574e-4c09-a6fa-74cd522b0e3c | | fa:16:3e:66:e2:60 | {"subnet_id": "24be33c7-64f9-4695-811d-33eeb4ad75da", "ip_address": "172.16.100.109"} |

+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------------+

i list all networks interfaces in this vm, only find an interface with fixed ip 172.16.100.108

here is the link of nova-compute log,"http://paste.openstack.org/show/34579/"

the id of this instance is 9aa82a35-c9f1-4f44-a108-d14e74eec231


You received this question notification because you are an answer contact for quantum.


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

2013-03-26 01:29:34 -0500 answered a question instance get more than one fixed ip(grizzly-g3)

the multiple IPs for a VM seems like a bug, assuming you made the same request for all VMs (which it sounds like you did).

Can you provide the output of quantum port-list (to confirm that there is also one port that has multiple IPs, not that nova is somehow associating multiple ports with the instance).

If there is a port with two IPs, can you try to reproduce this with verbose=True and debug=True, and post the log somewhere?

If not, then I'd be interesting in seeing the nova-compute log for the host running the VM with multiple IPs. Its possible that something strange is happening on the nova side to result in multiple ports being associated with a single VM.

2013-03-21 20:12:01 -0500 answered a question does post /networks require a network name as in API doc?

create a bug for this. https://bugs.launchpad.net/openstack-api-site/+bug/1158494 (https://bugs.launchpad.net/openstack-...)

thanks

2013-03-19 19:55:30 -0500 answered a question quantum single flat network, but cannot ping instances

it seems likely that the quantum-ovs-cleanup script is not being run on reboot.

you could try running it manually, and then restarting the dhcp agent.

2013-03-12 18:31:09 -0500 answered a question instance creation fails due to quantum internal server error

you'll want to include the quantum server log from when this error happened, as that is what will actually have a meaningful error message.

On Tue, Mar 12, 2013 at 10:45 AM, Sandeep Raman < question224072@answers.launchpad.net > wrote:

Question #224072 on quantum changed: https://answers.launchpad.net/quantum/+question/224072 (https://answers.launchpad.net/quantum...)

Description changed to: Precise Grizzly - single node install Quantum plugin - linuxbridge

Instance creation errors as http://paste.openstack.org/show/33454/ - It is excerpt from the nova-compute log QuantumClientException: Request Failed: internal server error while processing your request

Using nova boot to create instances. Previous attempts to launch instances were successful. All the quantum service is running.

Any one seen this before and any pointers how to solve this?


You received this question notification because you are an answer contact for quantum.


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

2013-03-12 16:48:41 -0500 answered a question Will Grizzly give one the ability to create a layer 3 agent from the dashboard?

the grizzly dashboard gives you the ability to create "routers" from the GUI. "l3-agents" are just one way of implementing routers.

2013-03-05 17:26:20 -0500 answered a question Adding a second external network using gre, second network does not route?

you can run multiple agents per node, assuming you are running with namespaces enabled.

On Tue, Mar 5, 2013 at 9:11 AM, digitalwonk < question223386@answers.launchpad.net > wrote:

Question #223386 on quantum changed: https://answers.launchpad.net/quantum/+question/223386 (https://answers.launchpad.net/quantum...)

Status: Answered => Open

digitalwonk is still having a problem: Thanks for the response Yong.

The l3 log currently report the following error message repeatedly:

2013-03-04 14:14:56 ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 171, in daemon_loop self.do_single_loop() File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 202, in do_single_loop target_ex_net_id = self._fetch_external_net_id() File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 185, in _fetch_external_net_id raise Exception("must configure 'gateway_external_network_id' if " Exception: must configure 'gateway_external_network_id' if Quantum has more than one external network.

So, if I have two separate external subnets, is there no way to have both of them being used on the same network node? Or would I need to somehow setup a separate quantum network node?

If I have to specify only one gateway_external_network_id, then why would anyone have more than external networks?

Thank you, Edwin


You received this question notification because you are an answer contact for quantum.


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

2013-03-04 01:20:53 -0500 answered a question quantum plugin floating_ip api error

to be honest, i'm not sure. I'd suggest using the 'quantum' client utility along with the --debug flag, so you can see the exact request and response. I'm not very familiar with horizon + quantum.

2013-03-03 17:14:33 -0500 answered a question quantum plugin floating_ip api error

this is a 404 error, as the url "/project/" is not something exposed via the quantum API.

2013-03-03 02:37:08 -0500 answered a question provider network vlan tag numbers

no, this is expected behavior. the VLAN that exists on br-int will be mapped to the correct vlan when the packet is sent out a particular external bridge. This is done for two reasons:

1) its possible that the same vlan ID is being used on two different bridges 2) vlans are used within br-int even when tunneling is used for communcation between hosts.

2013-02-26 17:39:17 -0500 answered a question Cannot ping instance after creating vm (using quantum networking)

I think step #3 was a mistake.

3) quantum net-create ext_net --shared --router:external=True

Should be:

3) quantum net-create ext_net --router:external=True

I.e., the network should be be shared.

Shared allows VMs to plug directly in, whereas we want ext_net to purely be external (but not shared).

When a VM is booted and no --nic is provided, it will be connected to all networks it sees, namely those that are owned by the tenant booting the VM, as well as all shared networks. This is why your VM has a NIC on ext_net when it shouldn't. The VM has no floating IPs.

Also, the reason you likely can't reach your VM via SSH on the internal IP may be security groups.

2013-02-18 17:50:39 -0500 answered a question Ubuntu 12.10 Openvswitch-plugin-agent version

have you rebooted after installing the new openvswitch kernel module? your kernel may still be running the old kernel module, since apt-get does not swap it out.

dan

On Mon, Feb 18, 2013 at 5:45 AM, Adel question222196@answers.launchpad.netwrote:

New question #222196 on quantum: https://answers.launchpad.net/quantum/+question/222196 (https://answers.launchpad.net/quantum...)

Hello,

Does any one knows about the good versions to use with ;

  • Ubuntu : 12.10
  • OpenStack : Folsom ==> quantum-plugin-agent : 1.4.3
  • Openvswitch : 1.4.3 ?

After havinng the problem bellow :

# File : /var/log/quantum/openvswitch-agent.log
# ERROR MSG : gre tunnels between virtual switches which is not

supported ....etc

I installed "openvswitch-datapath-dkms" and the errros are gone.

But :

1) ping of my vm is KO 2) The GRE Tunnels is not created automatically (both on the net-work and the compute nodes)

After creating the tunnels mannualy between the Network-Node & the Compute-Node

1) The ping of the first VM is still KO.

 2) when I ping the floating IP of my VM : 192.168.1.131   and using

tcpdump, i see that

    As a result :
    The Network-node, ask to the compute via the good GRE tunnel

(manualy created) who is the 10.5.5.2 witch is the private IP of the VM concerned (witch means for me the the l3-agent works fine). But no answer from the compute while the bridges are not crrectly added by the plugin-agent ....

So, does any one knows the versions and packages to implement with Ubuntu 12.10, openstack : folsom (openvswitch + GRE) ?

Thanks a lot for your help !


You received this question notification because you are an answer contact for quantum.


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

2013-02-14 17:00:15 -0500 answered a question In tenant network interconnection

My guess would be that you are also using security groups, which drop pings by default. If you allow ICMP for the security groups that both of the VMs are in, I think you will be able to ping the VMs as well. Router interfaces don't have security groups, and hence the pings work right away.

2013-02-12 20:55:18 -0500 answered a question Nat redirection

not currently, as quantum does not expose arbitrary NAT rules. Its likely something we'll be considering as part of the Havana release.

2013-02-12 19:33:08 -0500 answered a question using quantum CLI with publicURL

That's a good question Jack... thanks for raising it.

It looks like nova default to the publicURL, which would seem to make more sense.

I'll turn this into a bug for python-quantumclient and let that subteam respond in more detail.

2013-02-01 03:19:19 -0500 answered a question Should we use the copyright 2012-2013 or 2013 inside this year new developed quantum source code header?

i usually see the years listed, either separately as a range, but you'd have to ask a lawyer to know if it matters.

i think the general model is that we should encourage people to make sure the copyright date on any file they tweak is updated.

2013-01-31 21:19:55 -0500 answered a question Howto setup quantum for floating IPs similar to the way nova-network did it?

Hi Nick,

Unfortunately, as we describe in the limitations section ( http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html (http://docs.openstack.org/trunk/opens...) ), a deployment model similar to nova's --multi_host flag is not supported in quantum folsom.

There is work targeted for grizzly-3 that will support co-locating a router on the compute host along with a VM, see: - https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler (https://blueprints.launchpad.net/quan...) - https://docs.google.com/a/nicira.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit (https://docs.google.com/a/nicira.com/...)

2013-01-31 00:38:49 -0500 answered a question quantum router cannot ping default gateway

my guess would be that the OVS kernel module is not loaded.

easiest thing to do would be to reboot your box and make sure that ovs-dpctl show does not return an error.

2013-01-08 21:26:15 -0500 answered a question VLAN and GRE provider networks at the same time with OVS plugin

Good point Bob, I was wrong about the default.

dan

On Tue, Jan 8, 2013 at 1:11 PM, Robert Kukura < question218658@answers.launchpad.net > wrote:

Question #218658 on quantum changed: https://answers.launchpad.net/quantum/+question/218658 (https://answers.launchpad.net/quantum...)

Robert Kukura posted a new comment: Looks to me like it should work as well.

One note is that "tenant_network_type = vlan" will cause tenant networks to be allocated as vlans. If you change this to "tenant_network_type = gre" then they will be gre networks. In either case, you can allocate provider vlan and gre networks.

Also, I noticed that your ranges of vlan tags on the two physical networks don't overlap. Note that you can re-use the same vlan tags on distinct physical networks for distinct virtual networks (assuming the physical networks aren't the same network).

-Bob


You received this question notification because you are an answer contact for quantum.


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

2013-01-08 18:55:31 -0500 answered a question VLAN and GRE provider networks at the same time with OVS plugin

this should work. by default, i think you would get tunneled networks, but would be able to use the provider networks extension to create networks that map to physical vlans.

On Tue, Jan 8, 2013 at 10:11 AM, Miguel Lavalle < question218658@answers.launchpad.net > wrote:

New question #218658 on quantum: https://answers.launchpad.net/quantum/+question/218658 (https://answers.launchpad.net/quantum...)

HI,

With the OVS plug-in, can I have vlan and gre provider networks at the same time? If the answer is yes, would the following entries in ovs_quantum_plugin.ini be a good example of how to configure them:

tenant_network_type = vlan network_vlan_ranges = physnet1:1000:2999,physnet2:3000:3999 bridge_mappings = physnet1:br-eth1,physnet2:br-eth2

enable_tunneling = True tunnel_id_ranges = 1:1000 tunnel_bridge = br-tun local_ip = 10.0.0.3

Thanks


You received this question notification because you are an answer contact for quantum.


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

2013-01-08 17:39:42 -0500 answered a question One quantum subnet IP range on two different networks.

yes, this is possible if you set the following value in quantum.conf

allow_overlapping_ips = True

On Tue, Jan 8, 2013 at 6:15 AM, Asif question218633@answers.launchpad.netwrote:

New question #218633 on quantum: https://answers.launchpad.net/quantum/+question/218633 (https://answers.launchpad.net/quantum...)

Hi All, Is it possible to have same IP range on two subnets(subnets belonging to two different networks)? Since networks are isolated with VLANs we should be able to share same IP range across different subnets.

thanks Asif


You received this question notification because you are an answer contact for quantum.


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

2013-01-07 18:48:11 -0500 answered a question does dhcp-agent work in the same manner with KVM and Xen?

yes, though you should run the dhcp agent itself on a platform that supports it (e.g., Ubuntu, Fedora). The VMs that receive these requests can be running on KVM or XenServer/XCP

2012-12-21 02:17:53 -0500 answered a question No such table error in quantum server.log

i would simply stop quantum-server, drop the ovs_quantum database from mysql, and the start quantum-server

obviously this will destroy all existing networks + ports, but i'm assuming you're in a test setup.

2012-12-18 00:26:48 -0500 answered a question Floating IPs seem disconnected

thanks for the detailed report. this looks like a bug, as you should see the floating IPs as additional ips on the interface qg-a62da873-41 in the following output in you log:

root@knet-hj29:/var/log/quantum# ip netns exec qrouter-6e6f6f2d-45bd-40c1-b877-38df17c7394c ifconfig lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:672 (672.0 B) TX bytes:672 (672.0 B)

qg-a62da873-41 Link encap:Ethernet HWaddr fa:16:3e:c1:44:a9
inet addr:192.168.10.151 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fec1:44a9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15243 errors:0 dropped:0 overruns:0 frame:0 TX packets:759 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2261925 (2.2 MB) TX bytes:65187 (65.1 KB)

qr-b0755118-69 Link encap:Ethernet HWaddr fa:16:3e:86:47:f3
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe86:47f3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:695 errors:0 dropped:0 overruns:0 frame:0 TX packets:2692 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:75616 (75.6 KB) TX bytes:268972 (268.9 KB)

Can you see if there are errors in the log for the quantum-l3-agent?

2012-12-11 17:47:32 -0500 answered a question Gateway addresses for subnets are one off.

the gateway IP address of a subnet will default to being the first IP in the subnet (e.g., the .1 address for a subnet that has a range from .0-.255)

however, you can override this default if you choose, as for example, some people prefer the gateway IP to be another address (e.g., .the last IP in a range, such as .254)

2012-12-07 17:23:41 -0500 answered a question Multicast IP in Quantum

multicast should work for communication on the same L2 quantum network. Its possible however, that libvirt does some filtering that I am not aware of though

2012-12-07 09:07:55 -0500 answered a question Multicast IP in Quantum

multi-cast across logical L3 elements is not currently supported in quantum (or nova, I believe).

2012-12-06 22:42:43 -0500 answered a question OpenVSwitch flows missing on newly created setup

ah, my initial response was assuming you had followed the directions at: http://docs.openstack.org/trunk/openstack-network/admin/content/openvswitch_plugin.html (http://docs.openstack.org/trunk/opens...) if you were using tunneling, as these networks would automatically be created with type GRE, rather than local.

2012-12-06 21:44:16 -0500 answered a question OpenVSwitch flows missing on newly created setup

no, that's unlikely to be the cause.

are you sure the quantum-openvswitch-agents are running in the second setup? are you sure there are VMs up on running on the hosts? can you run "ovs-vsctl show" on the not-working setup.

2012-12-06 18:21:45 -0500 answered a question No such table error in quantum server.log

I wonder if you first ran quantum with a plugin that did NOT support the quantum "router" extension, then restarted with a plugin that did support it. I'm guessing it is the externalnetworks table that is not found, and that is specific to a plugin that has the "router" extension. Did you switch the plugin you were using?

2012-12-06 18:02:51 -0500 answered a question Quantum-server doesn't start

are you using RHEL? It may be related to this: https://lists.launchpad.net/openstack/msg02565.html (https://lists.launchpad.net/openstack...)

2012-12-04 06:41:52 -0500 answered a question Developing + Debugging Quantum via Devstack

the error you are getting from devstack is likely because stack.sh was run by someone other than the current user you are using to run screen -x stack.

you can either rerun stack.sh as the right user, su to the user that ran stack.sh, or chmod the /dev/pts/X file to something to make it readable by the current users (for example, if this is a dev box where you are not worried about security between multiple users, you could do "chmod 777 /dev/pts/1".

2012-12-03 22:58:36 -0500 answered a question Developing + Debugging Quantum via Devstack

you can access screen windows running each of the openstack services by running: screen -x stack

the quantum service windows all have names starting with "q-"

for most changes, you should just be able to control-c and then restart the services to pick up changes you made in /opt/stack/quantum

if you make more fundamental changes (e.g., to the database) or want to start with a clean setup, just run:

./unstack.sh ./stack.sh

2012-11-29 17:54:43 -0500 answered a question 3 nodes are involved: controller, network gateway, compute node. New instances are not communicating at all, no ip addresses.

changing the libvirt_vif_driver in that way basically makes it so that nova security groups are not applied. so it may have been that you could not communicate due to the fact that nova security groups were blocking the traffic.

2012-11-28 19:14:10 -0500 answered a question Floating IP and 'system' ports

that's a good point. we're talking about something similar on the security groups thread, so I think limiting it to compute:* ports (or explicitly excluding network:* ports) would be best.

2012-11-26 16:50:23 -0500 answered a question Unable to retrive the network list

here is the other reference to it... apparently his was double-filed: https://bugs.launchpad.net/openstack-manuals/+bug/1083064 (https://bugs.launchpad.net/openstack-...)

2012-11-26 16:49:09 -0500 answered a question Unable to retrive the network list

quantum is not running here, but horizon is trying to talk to quantum.

my guess is that the documentation you are following needs to either:

1) tell you to install and run the quantum service 2) tell you to configure horizon such that quantum is disabled.

I think I saw another issue who filed a similar problem.

2012-11-26 04:16:49 -0500 answered a question Can't ping gateway of tenant router....

are you running the quantum-ovs-agent on both the compute and the controller node?

if you are using tunnel mode, I would expect to see a tunnel port in your ovs-vsctl output.

2012-11-22 17:31:23 -0500 answered a question Quantum-server doesn't start

my guess would be that you have an old version of the python paste deploy library.

how did you upgrade/install quantum?

it may be enough just to use pip to update dependencies using the tool/pip-requires file by running the following within the quantum directory

sudo pip install -r tools/pip-requires