Support other redfish resource similar to standard redfish system resource

[Lin Yang]

Current Sushy already supports operation for standard redfish ComputerSystem resource. However, some other redfish resources based on ComputerSystem have the same interface API but with a different name, like ComposedNode in RSD, http://www.intel.com/content/www/us/en/architecture-and-technology/rack-scale-design/pod-manager-api-specification.html page 37.

The behavior of ComposedNode is exactly the same as ComputerSystem, but the path name is /redfish/v1/Nodes. It will be more flexible to allow user to specify the resource path than limit it to '/redfish/v1/Systems', so user can use Sushy to operate all kinds of resource with the same interface as ComputerSystems.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/447162

[deray (debayan-ray)]

The document as specified in the description portion describes Node as another resource in addition to System (page 9 - RSAServiceRoot) as opposed to substituting System altogether. Hence, do you see it as a possible scenario to propose this change? Isn't it better to have a separate resource from code side to represent /redfish/v1/Nodes ? I can also understand that the schema properties of these 2 resources (Systems and Nodes) could be very similar.. but what if there is any single mismatch or deviation? The whole new designing ball game may pop up then, like :class:`Node` inheriting from :class:`System` and overwriting suitable properties (just for example purpose)

[OpenStack Infra (hudson-openstack)]

Change abandoned by Lin Yang (<email address hidden>) on branch: master
Review: https://review.openstack.org/447162
Reason: No needed anymore after patch https://review.openstack.org/#/c/448539/

[deray (debayan-ray)]

Hi Lin, Just wondering if this bug can be used an associative one for addition of other resources apart from ``ComposedNode``, like Managers, SessionService etc. I need a bug to be associated with this patch: https://review.openstack.org/#/c/441236 . The topic of this bug seems apt. Could you add "support for addition of Manager resource" to this bug description? In the meanwhile I am associating this with the patch. Let me also know if you want me to submit a fresh bug (rfe) for Manager resource instead. Thanks in advance.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/441236
Committed: https://git.openstack.org/cgit/openstack/sushy/commit/?id=bdce45aa43a52d6fc6dc78204592ac3e9b5b43e9
Submitter: Jenkins
Branch: master

commit bdce45aa43a52d6fc6dc78204592ac3e9b5b43e9
Author: Debayan Ray <email address hidden>
Date: Fri Mar 3 12:48:22 2017 -0500

    Add manager resource

    This patch adds the Manager/ManagerCollection resource. Manager
    resource will provide information about remote access controls like
    serial console, command shell, graphical console etc. It will also
    serve as the gateway to virtual media, ethernet interfaces (NICs)
    information.
    'ResetActionField' moved to a new file, "resources/common.py",
    to be reused both by system and manager resource. Necessary changes
    are also made to the usage documentation page pertaining to Manager
    resource.

    Partial-Bug: #1673886
    Change-Id: I1d1b9b3f13002e654e4dc62d0558f5a2afbd8662