Bug 1466874
| Summary: | [Intel OSP13] Discover and compose Intel RSD nodes | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Krish Raghuram <krishnan.raghuram> |
| Component: | python-rsdclient | Assignee: | Ilya Etingof <ietingof> |
| Status: | CLOSED ERRATA | QA Contact: | Dan Yasny <dyasny> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 13.0 (Queens) | CC: | apevec, bfournie, emacchi, jjung, jschluet, krishnan.raghuram, lhh, lin.a.yang, markmc, mburns, mlammon, nathaniel.potter, paul.von.behren, pchavva, priyank.durugkar, racedoro, rhel-osp-director-maint, robert.h.armstrong, sclewis, srevivo |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, OtherQA, TechPreview, Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://github.com/openstack/python-rsdclient | ||
| Whiteboard: | |||
| Fixed In Version: | python-rsd-lib-0.1.1-0.20171222201255.d911e6e.el7ost python-rsdclient-0.1.1-0.20180110154722.f02d3fc.el7ost | Doc Type: | Technology Preview |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-27 13:31:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1514115, 1514119 | ||
| Bug Blocks: | 1412053, 1414581, 1419948, 1422243 | ||
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. 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. 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. 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 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. *** Bug 1466873 has been marked as a duplicate of this bug. *** *** Bug 1466880 has been marked as a duplicate of this bug. *** 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.) (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? (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. (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. Also check packaging guidelines at https://www.rdoproject.org/documentation/rdo-packaging/ then ask any questions after that on Freenode #rdo Based on: https://bugzilla.redhat.com/show_bug.cgi?id=1514115 (rsd-lib inclusion in RDO) https://bugzilla.redhat.com/show_bug.cgi?id=1514119 (python-rsdclient inclusion in RDO) The inclusion of both packages has been merged: https://review.rdoproject.org/r/#/c/10491/ https://review.rdoproject.org/r/#/c/10490/ So we assume the packages are ready in RDO. Moving to POST accordingly. I found and imported python-rsd-lib-0.1.1-0.20171222201255.d911e6e.el7ost but python-rsdclient I am not finding in RDO Trunk Master (DLRN) https://trunk.rdoproject.org/centos7-queens/current/ rdo git repo for rsdclient-distgit is empty and missing .spec The spec file was added for rsd-lib-distgit here -https://review.rdoproject.org/r/#/c/10619/ A spec file is also needed for rsdclient-distgit, its not apparent if a patch has been created, if not can you add it? NM, patch for spec file is here - https://review.rdoproject.org/r/#/c/10620/ and has an external tracker, it just needs to merge. Now two RDO package specs for rsd-lib-distgit and rsdclient-distgit have been merged. https://review.rdoproject.org/r/#/c/10620/ https://review.rdoproject.org/r/#/c/10619/ Thanks, moving this back to POST. The content for this fix is included in OSP 13 RC which is available on the Red Hat OpenStack Platform beta channels currently. Any efforts to verify that these bugs have been fixed would be appreciated. (In reply to Jon Schlueter from comment #35) > The content for this fix is included in OSP 13 RC which is available on the > Red Hat OpenStack Platform beta channels currently. Any efforts to verify > that these bugs have been fixed would be appreciated. By when do you need this to be tested? GA is scheduled for this week, if it's not verified by then by default bug will closed shipped advisory. If you want/need something different please respond as soon as possible. (In reply to Jon Schlueter from comment #37) > GA is scheduled for this week, if it's not verified by then by default bug > will closed shipped advisory. If you want/need something different please > respond as soon as possible. What is meant by "closed shipped advisory"? Will it not be "Tech Preview" for the feature? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086 |
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 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: