> The instance firewall should be configured to only allow DHCP
> responses from the IP it believes to be the correct DHCP server.
> Perhaps it has the wrong idea?
Ah yes - it probably does because of my unusual network "subrange" config.
It seems I'm not "missing something", so I've proposed a i
Justin Santa Barbara wrote >
> Yes, I do have a non-nova DHCP server. However, even if I didn't, and even
> if iptables allowed talking to 169.254 with the magic link-local, cloud-init
> still couldn't configure the IP address... :-(
If Linux assigned a 169.254 address to an Ethernet port t
2012/2/24 Justin Santa Barbara :
> I have contributed a patch (which has merged) which should allow you
> to stop editing the SQL: https://review.openstack.org/#change,3816
> With that, you should be able to pass the full range, with an
> additional argument specifying the subset that nova control
On Feb 23, 2012, at 5:42 PM, Justin Santa Barbara wrote:
>> If you're going to go the cloud-init route... you wouldn't need DHCP, right?
>> There should be iptables rules to allow you to talk to the metadata
>> service over 169.254.* (And linux should give you a default link-local
>> addres
> If you're going to go the cloud-init route... you wouldn't need DHCP, right?
> There should be iptables rules to allow you to talk to the metadata service
> over 169.254.* (And linux should give you a default link-local address that
> allows you to talk to the MD service magically)
>
> Do y
On Feb 23, 2012, at 3:55 PM, Justin Santa Barbara wrote:
> Thanks for chipping in.
>
> I have contributed a patch (which has merged) which should allow you
> to stop editing the SQL: https://review.openstack.org/#change,3816
> With that, you should be able to pass the full range, with an
> addi
Thanks for chipping in.
I have contributed a patch (which has merged) which should allow you
to stop editing the SQL: https://review.openstack.org/#change,3816
With that, you should be able to pass the full range, with an
additional argument specifying the subset that nova controls:
e.g.-fixed_ci
I'd assume FlatDHCPManager works much like FlatManager, but maybe I'm wrong. I
use FlatManager and I always end up having to modify the fixed_ips table
manually after running nova-manage because I think I'm trying to do something
similar as you. I have a /23... and I want to give nova a /25 ou
I'm trying to use OpenStack in what I think to be the typical
non-public-cloud deployment, and my experience is not what it
could/should be. I'm hoping someone can point me to the "right way",
or we can figure out what needs to change.
My wishlist:
* I want my instances to be on "my network" e.g.
9 matches
Mail list logo
