Dmitry Tantsur
5c5478d774
The current approach with separate ResourceDetail classes suffers from serious flows and is barely usable. For example for nodes: * get_node() returns complete Node objects * nodes() returns incomplete Node objects * nodes(details=True) returns NodeDetail objects, which are exactly like complete Node objects, except that you cannot do anything with them: updating, listing VIFs, etc. This is confusing and essentially requires the caller to issue a redundant get_node call after listing detailed nodes. This change consolidates everything into Node (Port, etc) objects and deprecates NodeDetail (PortDetail, etc). I would highly recommend the same approach taken for other ResourceDetail objects. Change-Id: Idedee2b394e2ed412a69880d4bc9315737e1c3ed
13 lines
517 B
YAML
13 lines
517 B
YAML
---
|
|
features:
|
|
- |
|
|
The objects returned by baremetal detailed listing functions
|
|
(``connection.baremetal.{nodes,ports,chassis,port_groups}``) are now
|
|
fully functional, e.g. can be directly updated or deleted.
|
|
deprecations:
|
|
- |
|
|
The following baremetal resource classes are no longer used and will be
|
|
removed in a future release: ``NodeDetail``, ``PortDetail``,
|
|
``ChassisDetail`` and ``PortGroupDetail``. The regular ``Node``, ``Port``,
|
|
``Chassis`` and ``PortGroup`` are now used instead.
|