openstack team mailing list archive

[tra26@xxxxxxxxxxxxx]

Alright so the proposed patch (on the abandoned review) doesn't fix the
problem either, so I guess I take a look at Grizzly.

If I were to want to test this out is Grizzly is the best option to just
grab the code from git and deploy it that way or is there a snapshot that
passes the tests? Basically we need to evaluate if Grizzly fixes the
problem or if we need to abandon trying to use openstack entirely.

-Trevor

> Salvatore,
>
> Thanks for your reply, ok that makes sense. I tried to create the network
> without a subnet and as the bug
> (https://bugs.launchpad.net/nova/+bug/1039665) lists it brings it up with
> no vif. I will just put a shim in or something and see if that solves my
> problem (assign a random ip) since this has not been fixed in folsom and
> the review died.
>
>
> Thanks,
>
> Trevor
>
>> Hi Trevor,
>>
>> sorry for the delay in the response.
>> It seems you want a L2-only network.
>> In theory, all you should do to achieve this is to not create a subnet
>> on your network.
>> Disabling DHCP on the subnet won't make any difference, since the
>> --enable-dhcp option only controls the IP address delivery mechanism,
>> not whether IPAM should be performed or not. However if you don't use
>> DHCP (and you do not have in place any other IP injection mechanism),
>> neither nova or quantum will configure IPs on your instances, and you
>> should be able to use your own allocation system, even if the IP
>> information reported from nova are then likely to differ from the
>> actual configuration.
>>
>> Unfortunately, I seem to recall an issue in nova where the VIF was not
>> created at all if an instance was created on a network without a
>> subnet; however, I'm not informed on the current status of this issue.
>>
>> On 8 February 2013 15:14,  <tra26@xxxxxxxxxxxxx> wrote:
>>> Anyone?
>>>
>>>
>>> Thanks,
>>>
>>> -Trevor
>>>> Again, is there a better place to ask these types of questions?
>>>>
>>>> I am trying to get a provider network working where I have full
>>>> control
>>>> of
>>>> the ip allocations. What I need is to be able to have 2 (or more
>>>> public
>>>> ip
>>>> addresses, or really to our private network). I know this can't be
>>>> done
>>>> with floating ips, so that is why I am looking to patch it into my
>>>> network
>>>> and just manually configure the ips. (probably also having a flat vm
>>>> network as well).
>>>>
>>>> I've got a provider network configured as so, with no dhcp on the
>>>> subnet:
>>>> +---------------------------+--------------------------------------+
>>>> | Field                     | Value                                |
>>>> +---------------------------+--------------------------------------+
>>>> | admin_state_up            | True                                 |
>>>> | id                        | f1c2fb46-72a3-410c-b06a-518c56659d62 |
>>>> | name                      | provider                             |
>>>> | provider:network_type     | flat                                 |
>>>> | provider:physical_network | prinet                               |
>>>> | provider:segmentation_id  |                                      |
>>>> | router:external           | True                                 |
>>>> | shared                    | True                                 |
>>>> | status                    | ACTIVE                               |
>>>> | subnets                   | c68bb08b-483f-49a5-be08-b690e84c4f17 |
>>>> | tenant_id                 | 35cd7af3118248bcb0ada0080afa3403     |
>>>> +---------------------------+--------------------------------------+
>>>>
>>>> +------------------+------------------------------------------------------+
>>>> | Field            | Value
>>>> |
>>>> +------------------+------------------------------------------------------+
>>>> | allocation_pools | {"start": "192.168.224.2", "end":
>>>> "192.168.224.254"}
>>>> |
>>>> | cidr             | 192.168.224.0/24
>>>> |
>>>> | dns_nameservers  |
>>>> |
>>>> | enable_dhcp      | False
>>>> |
>>>> | gateway_ip       | 192.168.224.1
>>>> |
>>>> | host_routes      |
>>>> |
>>>> | id               | c68bb08b-483f-49a5-be08-b690e84c4f17
>>>> |
>>>> | ip_version       | 4
>>>> |
>>>> | name             |
>>>> |
>>>> | network_id       | f1c2fb46-72a3-410c-b06a-518c56659d62
>>>> |
>>>> | tenant_id        | 35cd7af3118248bcb0ada0080afa3403
>>>> |
>>>> +------------------+------------------------------------------------------+
>>>>
>>>>
>>>> nova is assigning an ip to the port regardless of there being no dhcp
>>>> and
>>>> therefore the port does not allow me to configure it. Using a
>>>> different
>>>> ip
>>>> results in the iptables rules rejecting the packets.
>>>>
>>>> Anyone know how to fix this or get around this? Please?
>>>>
>>>> -Trevor
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>