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

Bug 339020

Summary: Software provisioning across nodes in the cloud
Product: z_Archived Reporter: Gunnar Wagenknecht <gunnar>
Component: gyrexAssignee: Gunnar Wagenknecht <gunnar>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 339081    
Bug Blocks:    

Description Gunnar Wagenknecht CLA 2011-03-05 15:54:13 EST
We need a way to provision software across nodes in the cloud. Ideally individual nodes would provision software themselves depending on tasks/roles they need to fulfill. This bug acts as a placeholder and collects thoughts/ideas that lead to an initial implementation for 1.0.

For an initial implementation the following should be sufficient.

- all nodes should use the same set of repos
- the set of repos might vary depending on the data center a node is located in (we would use node tags + filters for this)

- we need a list of IUs that should be installed on each node
- such a IU would be a feature (p2 term seems to be root IU), the Gyrex server itself would be a product IU
- again the list could use node tags + filter to limit installability of IUs to specific nodes

- on each node a job would run and ensure that all IUs are installed that should be installed
- such a job might wait for specific signals in order to implement a controlled roll-out which can be stopped in case of problems

To not confuse with p2 we should not stress terms such as "profile".
Comment 1 Gunnar Wagenknecht CLA 2011-03-05 15:54:43 EST
Need to look what we can do for M6.
Comment 2 Gunnar Wagenknecht CLA 2011-05-16 16:13:55 EDT
This has been implemented for M6 and tweaked further for M7 including a nice RAP based Admin UI.