Hi
I am busy redoing my foreman installation with katello and want to mirror my packages here.
I am currently running so never been an issue, but now that I intend to upgrade, I need to a proper answer
What exactly and from where do i install for grid EMI3 UMD3 UMD4 ?
I currently have EMI3, changed to UMD3 with torque(etc) disabled.
Input would be great.
Sean
The short answer is to look at the EGI Middleware page
I believe the correct answer is to start with the EGI repository http://repository.egi.eu/
There are two categories :
Once you know which stack to use, you need to know which components to install. Each site needs to respect the OLA, which defines what services you need to have certified at your site. I'm assuming you're going with the typical triple-threat : CE/accounting + SE + BDII
See the relevant product pages for these for how to configure them.
On a slightly disturbing note though - there is no CREAM CE for CentOS7, it seems. so... just check out the
repos before you go crazy.
I would like to suggest that we work on deployment code for the middleware - Puppet/Ansible stuff. Can your foreman use different provisioners ?
The question was more what to install than what to mirror, I can of course mirror everything ....
The lack of cream-ce is an issue, I would like to change as little as possible in the upgrade.
Ja the triple threat, ce, se x3, bdii, vobox, gums, perfsonar.
maybe split the ce into ce and head node.
I dont want cloud, I want it all running in docker, its far far simpler that way, networking might be more of an issue though.
If you are going to run everything in containers, you're going to need to change the installation and deployment quite a bit - but it's not very difficult. For CREAM, e.g. it's a mysql db and a tomcat- so you have to have two separate containers. Clearly not impossible, but could be done in a few days. The main issue is then configuration - the "old" way of doing this was writing the single YAIM file and then having yaim execute the string of scripts to create the config files. This is quite similar to how Ansible does it (tasks, templates, variables, etc), but still some work would be involved.
If you treat your CE as VM's instead of containers, you could first provision the containers, and then configure them. IE first do a docker run and then yaim -c inside the CE. You have options...
The point is that you don't have to decide on the base operating system of the platform, you can run the services inside containers on a different OS. E.g. base OS on the cluster is CEntOS7, but your CE is two containers that are FROM mysql/mysql for the db and FROM tomcat/tomcat for the CREAM service.
As for the others, a similar discussion holds. The main thing is to model the services in terms of their components and then provision them apporpriately...