clarify that IP on port does not need to be part of allocation pool

[dan wendlandt]

See discussion here, particularly the chunk of text gary calls out that should be rewritten: https://bugs.launchpad.net/bugs/1077292

[Tom Fifield (fifieldt)]

Gary Kotton (garyk) wrote on 2012-11-12: #4

Hi,
It says "When IP addresses are associated to a port, this also implies the port is associated with a subnet, as the IP address was taken from the allocation pool for a specific subnet. " My understanding is that the IP address must be taken from the allocation pool if it is defined.
Thanks
Gary

dan wendlandt (danwent) wrote on 2012-11-12: #5

Sounds like we have some conflicting text, but the intent as I understood it was that allocation_pools referred to what IPs might be automatically allocated when the creator of a port did not specify any specific fixed_ips. However, any unallocated IP in the subnet could be specified explicitly when creating a port, even if it was not in the allocation_pool. This allowed one to retain a particular subset of the subnet IPs for static allocation.

Salvatore Orlando (salvatore-orlando) wrote on 2012-11-12: #6

The allocation pool, to my understanding, was created for automatic allocation, ie: for those cases where the IP is no explicitly specified. I think there's nothing wrong with out-of-pool explicit allocation.

We might think about allowing the policy engine to restrict this capability to some specific users, but that is probably another story.

[Tom Fifield (fifieldt)]

Hi Salvatore,

did you still want to work on this one?

[Tom Fifield (fifieldt)]

de-assigning, to give someone else a go. If this was done in error - please re-assign.

[Andreas Jaeger (jaegerandi)]

David, are you still working on this?

[David F. Flanders (dff-melb)]

Nope, sorry, please do take it over. Best, Flanders

On 20 December 2013 20:56, Andreas Jaeger <email address hidden>wrote:

> David, are you still working on this?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1078013
>
> Title:
> clarify that IP on port does not need to be part of allocation pool
>
> Status in OpenStack Manuals:
> Triaged
>
> Bug description:
> See discussion here, particularly the chunk of text gary calls out
> that should be rewritten: https://bugs.launchpad.net/bugs/1077292
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1078013/+subscriptions
>

--
Research Community Manager | ITS Research Dept | University of Melbourne
Office phone: [phone] | Mobile (SMS): 040 128 3375 | Twitter:
@DFFlanders
Research Community Events:
http://research-it-services-unimelb.eventbrite.com.au/
Research IT Services Blog: http://blogs.unimelb.edu.au/researchservices/
Flanders' personal blog: dfflanders.wordpress.com/about/

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/89384
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=df8fe30fe5803758ee56dbc29fa969d7d94c6a95
Submitter: Jenkins
Branch: master

commit df8fe30fe5803758ee56dbc29fa969d7d94c6a95
Author: Anne Gentle <email address hidden>
Date: Mon Apr 21 12:14:50 2014 -0500

    Users can create ports for IPs outside of allocation_pool

    - Indicated that the pool of allocated IPs is set by their cloud provider
    - User would actually see the bug when deleting a port, but we don't
    document that procedure.
    - To close the bug, will also update the Networking API 2.0 doc

    Change-Id: I94fafd62a7f9b66dfcf2392186801d6a1e935cd6
    Partial-bug: 1078013

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/89385
Committed: https://git.openstack.org/cgit/openstack/netconn-api/commit/?id=8a1dc1230d8c7818e8acc34d41cbd7b9a35da1c6
Submitter: Jenkins
Branch: master

commit 8a1dc1230d8c7818e8acc34d41cbd7b9a35da1c6
Author: Anne Gentle <email address hidden>
Date: Mon Apr 21 12:21:53 2014 -0500

    Indicates that port definition can have specific unallocated IPs

    Change-Id: I2eb27e4d697c69f039b0f082b31926eb916cb3d2
    Closes-bug: 1078013