Bug 1397204

Summary:	[Intel-OSP12] TripleO interface to Valence Rack Scale Controller to deploy nodes
Product:	Red Hat OpenStack	Reporter:	Krish Raghuram <krishnan.raghuram>
Component:	openstack-tripleo	Assignee:	James Slagle <jslagle>
Status:	CLOSED WONTFIX	QA Contact:	Arik Chernetsky <achernet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	jdonohue, krishnan.raghuram, lin.a.yang, malini.k.bhandaru, mburns, nathaniel.potter, racedoro, rhel-osp-director-maint, robert.h.armstrong
Target Milestone:	Upstream M1	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
URL:	https://wiki.openstack.org/wiki/Valence
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-05 15:20:34 UTC	Type:	Feature Request
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:
Bug Blocks:	1414581, 1419948, 1422243

Description Krish Raghuram 2016-11-21 21:59:28 UTC

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:

Comment 1 Krish Raghuram 2016-11-21 22:13:24 UTC

See https://review.openstack.org/#/c/341966/

Comment 2 Krish Raghuram 2017-01-13 17:11:22 UTC

*** Bug 1411503 has been marked as a duplicate of this bug. ***

Comment 3 Krish Raghuram 2017-01-13 17:15:17 UTC

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)

Comment 4 Ramon Acedo 2017-03-02 17:37:36 UTC

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).

Comment 5 Krish Raghuram 2017-03-02 20:09:23 UTC

(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

Comment 7 Krish Raghuram 2017-09-21 14:43:17 UTC

(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