Description of problem: Rack-scale nodes need to be deployed into an OpenStack cloud through a TripleO plug-in or interface. This will require an interface into the Valence software layer Version-Release number of selected component (if applicable): TripleO version that is part of OpenStack Pike release How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Deployment of a cloud (compute, network, storage) from a shared pool of disaggregated rack resources (CPU, memory, NIC, local storage) Additional info:
See https://review.openstack.org/#/c/341966/
*** Bug 1411503 has been marked as a duplicate of this bug. ***
Additional info for reference: Standalone WebUI development in Valence: https://blueprints.launchpad.net/openstack-valence/+spec/web-ui-interface Valence also provides an API that can be used by deployment tools to do what it's own GUI does - that is the focus of this BZ Primary contact at Partner, email, phone (chat) Nate Potter nathaniel.potter (IRC: ntpttr)
If Valence can have a Redfish interface for Ironic then integration with TripleO might be automatic (to be reassessed once the Ironic Redfish driver is finished).
(In reply to Ramon Acedo from comment #4) > If Valence can have a Redfish interface for Ironic then integration with > TripleO might be automatic (to be reassessed once the Ironic Redfish driver > is finished). Ramon, you're probably right about this. When I had raised this bugzilla, the Valence community was working the older approach of having everything go through Valence. Now with Valence registering the nodes with Ironic, it may be possible for TripleO to install the undercloud, see the registered RSD nodes after Valence has registered them with Ironic, and then deploy the overcloud onto those nodes. For an already-running overcloud, TripleO can see the new nodes and extend the cloud to them. Let's test this taskflow out after the Valence-Ironic-Redfish path is tested and working
(In reply to Ramon Acedo from comment #4) > If Valence can have a Redfish interface for Ironic then integration with > TripleO might be automatic (to be reassessed once the Ironic Redfish driver > is finished). I recommend closing this BZ and focusing attention on the new BZ# 1489201, which requests TripleO support (maybe only testing is required) for the new implementation of RSD node composition and registration through OpenStack Client