Dmitry Tantsur 5c5478d774 Change approach to detailed listings of baremetal resources ... 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		2018-11-23 09:14:37 +01:00
..
__init__.py	Rework config and rest layers	2017-11-15 11:46:50 -06:00
test_chassis.py	Change approach to detailed listings of baremetal resources	2018-11-23 09:14:37 +01:00
test_driver.py	Use discovery instead of config to create proxies	2018-10-06 07:44:29 -05:00
test_node.py	Change approach to detailed listings of baremetal resources	2018-11-23 09:14:37 +01:00
test_port.py	Change approach to detailed listings of baremetal resources	2018-11-23 09:14:37 +01:00
test_port_group.py	Change approach to detailed listings of baremetal resources	2018-11-23 09:14:37 +01:00
test_proxy.py	Change approach to detailed listings of baremetal resources	2018-11-23 09:14:37 +01:00