[rhos-list] EXTERNAL: Re: Questions about Quantum.

[Minton, Rich]

Gary,

I was hoping you could shed some light on what I'm seeing.  I was doing some comparison between my controller/compute node and another compute node - using "nova-manage config list". I noticed some configuration entries that look like they are leftovers from Nova Network. When I created our Openstack cluster originally I used packstack to start and then converted from Nova Network to Quantum. Is it possible that some of these leftover config entries are causing conflicts with Quantum Networking? Some of the questionable entries are:

network_manager = nova.network.manager.FlatDHCPManager
network_topic = network
dhcpbridge = /usr/bin/nova-dhcpbridge
num_networks = 1
dhcpbridge_flagfile = ['/usr/share/nova/nova-dist.conf', '/etc/nova/nova.conf']
instance_dns_manager = nova.network.dns_driver.DNSDriver
auto_assign_floating_ip = False
routing_source_ip = 10.255.254.36
networks_path = /var/lib/nova/networks
floating_range = 4.4.4.0/24
flat_network_dns = 8.8.4.4
floating_ip_dns_manager = nova.network.dns_driver.DNSDriver
public_interface = eth0
network_size = 256
fixed_range = 10.0.0.0/8
default_floating_pool = nova

I also saw some entries from Nova Volume but I'll leave that for another time.

Thank you,
Rick

From: Gary Kotton [mailto:gkotton at redhat.com]
Sent: Wednesday, May 08, 2013 10:02 AM
To: Minton, Rich
Cc: rhos-list at redhat.com
Subject: EXTERNAL: Re: [rhos-list] Questions about Quantum.

On 05/08/2013 04:19 PM, Minton, Rich wrote:
We are running into difficulty implementing RHEL Openstack using Quantum Networking and need to verify the level of Quantum Support provided by RHEL.

Sorry to hear that. Hopefully we will be able to help out.



Which of the RHEL Openstack Folsum Quantum implementations are supported (FLAT, FLAT DHCP, VLAN, GRE)?

GRE is not supported. This is due to the fact that there are some missing parts from the current kernel.


Which of those implementations support the Openstack Metadata Service?

In Folsom a VM can only access the metadata service if the L3 agent is running.

In Grizzly this can be done via the L3 agent or the DHCP agent (there may be cases where one would not want to run the L3 agent).

Please note that due to the fact that there is no namespace support in RHEL this support does not work when there are networks with overlapping IP ranges.



Can Metadata be supported without using the Quantum L3 agent, such as in the FLAT/FLATDHCP models?

Only with Grizzly.



Which Openstack Quantum Use Cases are supported?
                Single Flat Network
                Multiple Flat Network
                Mixed Flat and Private
                Provider Router with Private Networks
                Per-tenant Routers with Private Networks

I think all of the above.




Thanks for the help.
Rick

Richard Minton
LMICC Systems Administrator
4000 Geerdes Blvd, 13D31
King of Prussia, PA 19406
Phone: 610-354-5482





_______________________________________________

rhos-list mailing list

rhos-list at redhat.com<mailto:rhos-list at redhat.com>

https://www.redhat.com/mailman/listinfo/rhos-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhos-list/attachments/20130509/28e84ec7/attachment.htm>