Bug 919482

Summary:	Feature request to add application deployment to the REST API
Product:	[Other] RHQ Project	Reporter:	Kurt Stam <kurt.stam>
Component:	REST	Assignee:	Heiko W. Rupp <hrupp>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	mlipchuk
Target Milestone:	---
Target Release:	RHQ 4.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-03 14:43:25 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:

Description Kurt Stam 2013-03-08 15:42:44 UTC

One of the things the Overlord project governs is the lifecyle of a deployable artifact. In one of the Governance Workflow we guide an artifact through different runtime environments (dev/qa/stage/prod). We'd like to integrate with RHQ so you can do the actual deployment for us. We'd know the 'group' let's say the PROD4 server farm; and we'd hand you an war archive (zip), or RHQ bundle. I think there can be two scenarios:

1. You deploy it immediately
2. You add it to a staging repository and an admin will approve to do the actual deployment. (I think you already have this?)

We'd like to use the REST API, but it currently does not support this. Hence this feature request.

Comment 1 Heiko W. Rupp 2013-03-08 16:16:31 UTC

Hi Kurt,

thanks.

Currently we have two mechanisms for this:

1) deploy a .war to a single resource (which in case of as7 can be a whole server-group)
2) deploy a so called bundle (that can contain a .war file ) to a group of resources.

Directly deploying a .war to a group of (arbitrary) resources is not possible - if you use the rest-api,
you can retrieve the resources of a group and then deploy to them in a loop.

As you mention SOA-P *6* I think you may be thinking of 1) ?

Comment 2 Kurt Stam 2013-03-08 18:48:26 UTC

Thanks Heiko,

I understand the domain model of as7 can be used to deploy to an entire group; and I have to support that even when users do not use RHQ.

I would like for RHQ to abstract the physical nodes for me. I want to use it as the provision system in this case, where I only know of a logical name, let's say PROD4, which then on your side maps to a group of servers of any type (not just AS7). Don't you have  RHQ you have the concept of 'groups'. Your workaround, like you said, to query RHQ for this info and then deploy to each one is fine with me. Are you supporting deployments already using REST?

Comment 3 Maor 2013-03-11 09:55:19 UTC

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

Comment 4 Heiko W. Rupp 2013-03-22 16:46:20 UTC

A first implementation has been committed to master as  ed813bd93929d

You can have a look at an example of such a deploy here:

http://git.fedorahosted.org/cgit/rhq/rhq.git/tree/modules/integration-tests/rest-api/src/test/java/org/rhq/modules/integrationTests/restApi/ContentTest.java#n145

method is org.rhq.modules.integrationTests.restApi.ContentTest#testCreatePackageBasedResource

Comment 5 Heiko W. Rupp 2013-09-03 14:43:25 UTC

Bulk closing of issues in old RHQ releases that are in production for a while now.

Please open a new issue when running into an issue.