yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #72189
[Bug 1761823] [NEW] [RFE] Introduce /ip-address resource
Public bug reported:
This RFE is created according to the feedback of the neutron driver team
meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the port
that this address is/was associated with.
There are two major use cases:
* Provide a unified view for two types of IP address (fixed and floating). This facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
** Affects: neutron
Importance: Undecided
Status: New
** Description changed:
This RFE is created according to the feedback of the neutron driver team
meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the port
that this address is/was associated with.
There are two major use cases:
- * Provide a unified view for two type of IP address (fixed and floating).
+ * Provide a unified view for two types of IP address (fixed and floating). This facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1761823
Title:
[RFE] Introduce /ip-address resource
Status in neutron:
New
Bug description:
This RFE is created according to the feedback of the neutron driver
team meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including the data of the
port that this address is/was associated with.
There are two major use cases:
* Provide a unified view for two types of IP address (fixed and floating). This facilitates information lookup by an address of unknown type.
* Provide history of an address (i.e. which VM this address is/was associated with in a specific time).
[1]
http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-04-06-14.00.log.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1761823/+subscriptions
Follow ups