Open Stack

Thanks for your response. In the meantime, I created an additional
throw-away subnet(192.168/16) on each network. So on the 'main' neutron
port, I call the 'production' subnet.
On the other neutron port(s) in the bond group, I call the "throw-away"
subnet.
So now only one IP is allocated out of my production subnet, and the other
allocations from the 'throw-away' subnets are just ignored. Since the
bond/members take on the
IP/MAC of the 'proudction' neutron port.





On Mon, Jul 11, 2016 at 12:48 AM, Sam Stoelinga <sammiestoel at gmail.com>
wrote:

> If you're using PCI passhtrough with direct passthrough you shouldn't be
> hit by ARP spoofing protection so even though it assigns an IP you could in
> theory use any IP. If you need to allow a single IP to be allowed on
> multiple ports you can use allowed address pairs functionality. From what I
> understand you want to make sure it only assigns a single IP such that you
> aren't wasting an IP allocation?
>
> Looking at the Neutron API specs
> <http://developer.openstack.org/api-ref-networking-v2.html#createPort> it
> looks like only providing a network id and not a subnetid should work, but
> it still assigns an IP automatically.
> Using the CLI I tried to create a Neutron port without an IP but wasn't
> successful either. It seems to always assign an IP. For reference:
> neutron --debug port-create e33d8ee8-92e1-48e4-be5e-91573e731e27 --name
> test_net_only
> curl -g -i -X POST http://192.168.0.13:9696/v2.0/ports.json
> '{"port": {"network_id": "e33d8ee8-92e1-48e4-be5e-91573e731e27", "name":
> "test_net_only", "admin_state_up": true}}'
> RESP BODY: {"port": {"status": "DOWN", "binding:host_id": "",
> "allowed_address_pairs": [], "dns_assignment": [{"hostname":
> "host-192-168-111-12", "ip_address": "192.168.111.12", "fqdn":
> "host-192-168-111-12.openstacklocal."}], "device_owner": "",
> "binding:profile": {}, "port_security_enabled": true, "fixed_ips":
> [{"subnet_id": "fee4c6f2-d67e-43d5-b8a1-0f64c8775a39", "ip_address":
> "192.168.111.12"}], "id": "17926156-e7f8-4c00-bab8-8990d7df937c",
> "security_groups": ["62a33f63-bfae-4bd9-8662-507136d7598b"], "device_id":
> "", "name": "test_net_only", "admin_state_up": true, "network_id":
> "e33d8ee8-92e1-48e4-be5e-91573e731e27", "dns_name": "",
> "binding:vif_details": {}, "binding:vnic_type": "normal",
> "binding:vif_type": "unbound", "tenant_id":
> "4a79550e40794812b070db605728f734", "mac_address": "fa:16:3e:e8:2d:70"}}
>
> Maybe somebody else knows how to create a port without assigning a subnet
> / fixed IP address.
>
>
> On Fri, Jul 8, 2016 at 9:45 PM, Brent Troge <brenttroge2016 at gmail.com>
> wrote:
>
>> I want to create a bond within my guest VM and trying to understand how
>> to
>> create my neutron ports without allocating an IP for each VF created.
>> I just need one IP allocated instead of each VF(neutron port) being
>> allocated an IP.
>>
>> I do not see anything within the neutron port api which supports
>> something like: 'no-ip-allocation;
>>
>> I am expecting something like the below.. See my made up property under
>> 'sriov_port2'
>>
>> resources:
>>   sriov_port1:
>>     type: OS::Neutron::Port
>>     properties:
>>       network: { get_param: my_net }
>>       vnic_type: direct
>>   sriov_port2:
>>     type: OS::Neutron::Port
>>     properties:
>>       network: { get_param: my_net }
>>       vnic_type: direct
>>       fixed-ip: false
>>
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160711/3ea45c3c/attachment.html>