Bug 1367404

Summary:	[Docs][RFE][Director] Document composable services
Product:	Red Hat OpenStack	Reporter:	Carlos Camacho <ccamacho>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	lbopf, srevivo
Target Milestone:	---	Keywords:	Documentation, FutureFeature
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-14 02:57:28 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:
Bug Depends On:	1337778
Bug Blocks:

Description Carlos Camacho 2016-08-16 11:07:33 UTC

Documentation required for OSP10 composable services

The purpose of this bug it's to request the related downstream documentation for composable roles in OSP10. 

Requirements description:

We need to describe the process related to the decomposition of the current monolithic heat templates configuration for all the services deployed in the overcloud based on each specific role (Controller, Compute, Block Storage, Object Storage and Ceph Storage). Also to describe the process to add new services into this new architecture.

Related documentation:

Composable services introduction:
http://hardysteven.blogspot.com.es/2016/08/tripleo-composable-services-101.html

Description about current fixed roles architecture:
http://hardysteven.blogspot.com.es/2015/05/tripleo-heat-templates-part-1-roles-and.html

Current upstream documentation related to how to integrate current/new services:
http://tripleo.org/developer/tht_walkthrough/tht_walkthrough.html

Comment 2 Carlos Camacho 2016-08-16 13:39:48 UTC

How to test a composable service:

The first item that needs to checked it's to verify that the actual service it's enabled by default in the resource registry. For example, by verifying  in the following file “overcloud-resource-registry-puppet.yaml” that   OS::TripleO::Services::Horizon:  it's not pointing to OS::Heat::None.

Case pointing  to OS::Heat::None.
  In this case the service should be enabled by using an environment file inside the 'environments' folder.

Case pointing to a valid heat template.
  For example “puppet/services/horizon.yaml”, in which case this composable service will be deployed by default.

Note: It's important to check that this resource registry it's not overridden when deploying HA environments, in which case the heat template might be overridden in this environmental file “environments/puppet-pacemaker.yaml”

Comment 3 Lucy Bopf 2016-10-14 02:57:28 UTC

The requirements for this bug have now been covered in (related) bug 1367611. Closing this one as a duplicate to streamline tracking.

*** This bug has been marked as a duplicate of bug 1367611 ***