Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 443676

Summary:	Support multiple deployment planners for Cloud Foundry
Product:	[ECD] Orion	Reporter:	Maciej Bendkowski <maciej.bendkowski>
Component:	Deployment	Assignee:	Maciej Bendkowski <maciej.bendkowski>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	6.0
Target Milestone:	7.0
Hardware:	PC
OS:	Linux
Whiteboard:

Description Maciej Bendkowski

2014-09-10 04:27:35 EDT

In order to provide seamless best-effort interactive deployments, we need an extendable server-side service for detecting various application types. It would follow that different application run-times should have dedicated wizards.

Comment 1 Maciej Bendkowski

2014-09-10 06:16:07 EDT

Part I: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=cff9dc835b46a46b2f14fb566c22bac57677aefc

A generic pluginable mechanism for different deployment planners was introduced. A deployment planner is a server side service which can deduce necessary deployment parameters and fill in defaults for a specific application run-times. Moreover, planners can define dedicated packaging processes for uploading application bits.

Comment 2 Maciej Bendkowski

2014-09-10 10:31:26 EDT

Part II: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=c97d1022b56901d76c399d9588969cd532d200e6

The packaging mechanism has been extracted to a separated service.

Comment 3 Maciej Bendkowski

2014-09-22 04:57:38 EDT

Part III: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=6968c774d03e3886e34f8922229efd70c46bd9f9

Introduced client-side plugins providing custom deployment wizards for generic and node.js applications.