Hi Tushar, sorry for the delay and THANK YOU - this is a great reference.
Greetings -Sascha- Am 24.01.2014 23:01, schrieb Patil, Tushar: > Hi Sascha, > > Following URL gives you an easy overview of all configuration options > available in OpenStack compute service. > http://docs.openstack.org/havana/config-reference/content/list-of-compute-config-options.html > > > Thanks and Best Regards, > Tushar Patil. > >> -----Original Message----- >> From: Sascha Vogt [mailto:[email protected]] >> Sent: Friday, January 24, 2014 6:54 AM >> To: David Wittman >> Cc: [email protected] >> Subject: Re: [Openstack] Havana / nova-network - Multi-Node setup, dnsmasq >> uses >> the same IP on multiple nodes >> >> Hi David, >> >> thanks alot, that was it :) >> >> I find it very hard, to get a list of all supported options in nova.conf >> (and the other >> confs as well) and what they mean. Is there an easy overview of all of >> them??? >> >> Greetings >> -Sascha- >> >> Am 24.01.2014 15:47, schrieb David Wittman: >>> It sounds like you may have `share_dhcp_address` set to True in your >>> nova.conf: >>> >>> https://github.com/openstack/nova/blob/master/etc/nova/nova.conf.sampl >>> e#L1231-L1235 >>> >>> Dave >>> >>> >>> On Fri, Jan 24, 2014 at 7:22 AM, Sascha Vogt <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi all, >>> >>> I have a Multi-Node, Single-NIC setup. All machines only have a single >>> NIC. I created a virtual network (using gretap tunnels - aka >>> layer2-over-layer3 tunnel) to connect all machines and have one br-int >>> bridge which all VMs are attached to. >>> >>> nova-network runs on all machines and correctly binds dnsmasq to the >>> hosts bridge itself, though I noticed that each host-bridge gets the .1 >>> IP. This seems to work, because dnsmasq is configured by nova-network to >>> only answer to DHCP requests the specific instance has a MAC address >>> for, though I find it a bit irritating. >>> >>> I try to give a picture of it: >>> >>> controller >>> - br-int (dnsmasq with .1 address) >>> - gretap tunnel to compute-1 (using the static IPs of eth0) >>> - gretap tunnel to compute-2 (using the static IPs of eth0) >>> - vnet1-n (instances running on this host) >>> - eth0 (routes between external network and br-int, NAT / ip >>> forwarding active, static IP used also for OpenStack >>> managing) >>> >>> compute-1 >>> - br-int (dnsmasq with .1 address) >>> - gretap tunnel to controller (using the static IPs of eth0) >>> - vnet1-n (instances running on this host) >>> - eth0 (OpenStack managing) >>> >>> compute-2 >>> - br-int (dnsmasq with .1 address) >>> - gretap tunnel to controller (using the static IPs of eth0) >>> - vnet1-n (instances running on this host) >>> - eth0 (OpenStack managing) >>> >>> I'm using the FlatDHCPManager, and if you substitue eth0/the-switch in >>> this picture >>> http://www.mirantis.com/wp-content/uploads/2012/07/flat-dhcp-networking- >> diagrams-4.png >>> with the gretap tunnels I basically have that topology. In that picture >>> the dnsmasqs/br100 have different IPs. How did they get that? ;) >>> >>> Greetings >>> -Sascha- >> >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : [email protected] >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > ______________________________________________________________________ > Disclaimer:This email and any attachments are sent in strictest confidence > for the sole use of the addressee and may contain legally privileged, > confidential, and proprietary data. If you are not the intended recipient, > please advise the sender by replying promptly to this email and then delete > and destroy this email and any attachments without any further use, copying > or forwarding > _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
