Bug 1466874 - [Intel OSP13] Discover and compose Intel RSD nodes [NEEDINFO]
[Intel OSP13] Discover and compose Intel RSD nodes
Status: NEW
Product: Red Hat OpenStack
Classification: Red Hat
Component: distribution (Show other bugs)
13.0 (Queens)
x86_64 Linux
medium Severity high
: Upstream M2
: 13.0 (Queens)
Assigned To: Jon Schlueter
Udi Shkalim
https://github.com/openstack/python-r...
: FutureFeature, OtherQA, Triaged
: 1466880 (view as bug list)
Depends On:
Blocks: 1412053 epic-rsd 1419948 1422243
  Show dependency treegraph
 
Reported: 2017-06-30 11:38 EDT by Krish Raghuram
Modified: 2017-11-01 11:51 EDT (History)
16 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: ---
krishnan.raghuram: needinfo? (nathaniel.potter)


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
Comment 6 Ramon Acedo 2017-10-19 06:36:33 EDT
Hi Krish, our understanding is this functionality will be included in the python-rsdclient you are working on. 

Adding python-rsdclient to RDO as a package first and then to OSP will make composing and listing the RSD nodes possible. 

We intend to do this for OSP 13 as requested. This BZ can be a placeholder to track the progress and to later test it in OSP when available by the Intel team with OSP.

Including it for OSP 13, pending the usual reviewing of dependencies, security, legal, etc.

BZ will need a new component for python-rsdclient, for now it's under python-openstackclient.
Comment 7 Ramon Acedo 2017-10-20 06:13:58 EDT
*** Bug 1466873 has been marked as a duplicate of this bug. ***
Comment 8 Ramon Acedo 2017-10-20 06:15:42 EDT
*** Bug 1466880 has been marked as a duplicate of this bug. ***
Comment 12 Jon Schlueter 2017-10-23 11:00:32 EDT
Also is there work for getting python-rsdclient packaged and available in RDO by upstream Milestone 2 for Queens cycle?  (if not already stated packaging and package review in RDO/fedora needs to be underway soon.)
Comment 15 Krish Raghuram 2017-10-23 13:29:28 EDT
(In reply to Jon Schlueter from comment #12)
> Also is there work for getting python-rsdclient packaged and available in
> RDO by upstream Milestone 2 for Queens cycle?  (if not already stated
> packaging and package review in RDO/fedora needs to be underway soon.)

Nate Potter on our team is investigating this, as we don't have experience packaging stuff into RDO. Would Milestone 2 be the Dec.4 deadline that I've heard being mentioned?
Comment 16 Jon Schlueter 2017-10-23 23:13:37 EDT
(In reply to Krish Raghuram from comment #15)
> (In reply to Jon Schlueter from comment #12)
> > Also is there work for getting python-rsdclient packaged and available in
> > RDO by upstream Milestone 2 for Queens cycle?  (if not already stated
> > packaging and package review in RDO/fedora needs to be underway soon.)
> 
> Nate Potter on our team is investigating this, as we don't have experience
> packaging stuff into RDO. Would Milestone 2 be the Dec.4 deadline that I've
> heard being mentioned?

Yes Dec 4-8 this Queens Milestone 2 [1]  and we should have all packages available in RDO before then.

[1] https://releases.openstack.org/queens/schedule.html


First step is work with RDO guys to get .spec created and reviewed for these packages, get Review BZ's filed for RDO, and reviews well underway.

Alan Pevec and others can help coordinate getting this process rolling.
Comment 17 Mike Burns 2017-10-24 07:57:50 EDT
(In reply to Krish Raghuram from comment #15)
> (In reply to Jon Schlueter from comment #12)
> > Also is there work for getting python-rsdclient packaged and available in
> > RDO by upstream Milestone 2 for Queens cycle?  (if not already stated
> > packaging and package review in RDO/fedora needs to be underway soon.)
> 
> Nate Potter on our team is investigating this, as we don't have experience
> packaging stuff into RDO. Would Milestone 2 be the Dec.4 deadline that I've
> heard being mentioned?

http://rdoproject.org/documentation/add-packages/ talks about how to add packages.

Dec 4 is when we need the package in RDO for us to get it into OSP 13.  

If you need assistance, people on #rdo on Freenode are generally pretty helpful.
Comment 18 Alan Pevec 2017-10-24 08:00:02 EDT
Also check packaging guidelines at https://www.rdoproject.org/documentation/rdo-packaging/ then ask any questions after that on Freenode #rdo

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