Bug 1466874 - [Intel OSP13] Discover and compose Intel RSD nodes
[Intel OSP13] Discover and compose Intel RSD nodes
Status: NEW
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo (Show other bugs)
13.0 (Queens)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: James Slagle
Arik Chernetsky
: FutureFeature
Depends On:
Blocks: epic-rsd 1419948 1422243
  Show dependency treegraph
 
Reported: 2017-06-30 11:38 EDT by Krish Raghuram
Modified: 2017-09-21 10:45 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Krish Raghuram 2017-06-30 11:38:59 EDT
Description of feature:
RSD platforms currently support the Redfish API, and are expected to soon support the Swordfish and Yang-to-Redfish APIs. Red Hat has already written a Redfish library (Sushy) to provide access from within OpenStack to the RSD platforms. Functionality is needed within OpenStack (eg. through the CLI), to view and manage the compute resources through the open APIs. Specifically:

-	discover and list compute resources
-	Allow composition of nodes 
-	Allow decomposition of nodes with erase and no erase option for data on drives

Version-Release number of selected component (if applicable):
OpenStack Client version (potentially) in OpenStack Queens release

2. Business Justification:
  a) Why is this feature needed?
     RSD is a new architecture that realizes an agile infrastructure where the hardware resources can be pooled according to application needs. It also enables a more easily scaled infrastructure, so CPU, memory, network and storage resources can be added as needed, without the need to do complete replacements of nodes
  b) What hardware does this enable?
   New platforms based on RSD architecture
  c) Is this hardware on-board in a system (eg, LOM) or an add-on card? 
  RSD nodes are disaggregated (CPU, memory, storage, accelerators etc.)
  d) Business impact? N/A
  
  e) Other business drivers: N/A

3. Primary contact at Partner, email, phone (chat)
   Priyank Durugkar - priyank.durugkar@intel.com

4. Expected results:
- DC admin installs the undercloud
- Admin then uses the CLI to discover compute resources
- Admin then composes a compute node on a RSD rack with the required resources
- TripleO then deploys the node into the overcloud
- Once a node is no longer needed, admin decomposes the node 

Additional info:
Comment 1 Red Hat Bugzilla Rules Engine 2017-06-30 11:39:05 EDT
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Comment 2 Nate Potter 2017-07-24 16:16:31 EDT
I'm working on enabling this starting with adding RSD functionality to the python-valenceclient using a custom extension of Sushy that allows for node composition logic. From there we can expose the work to OSC through a plugin.
Comment 3 Nate Potter 2017-08-03 14:02:57 EDT
Here is the code I wrote extending Sushy to be able to discover composed nodes via the RSD redfish API https://review.openstack.org/#/c/490253/. It was merged to the new rsd-lib project, which will be used by the python-rsdclient plugin for OSC.
Comment 4 Krish Raghuram 2017-09-21 10:45:38 EDT
This is high priority for Intel for Queens release. We've got all the code tested and merged into https://github.com/openstack/rsd-lib and https://github.com/openstack/python-rsdclient

Note You need to log in before you can comment on or make changes to this bug.