en en en en en eu en en en en en en en en en en en en pt pt en en en en ceb en pt pt hu hu en en en en fr en en en en en en en en en en en en en en en en en pt nb en en en en en gu en en pt nl en en en en it sv en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en hu en en en en en en en en en en en vi en en en en en en en en pt en en en en en en ru en en en en en en en id en en en en en en en en en en en en en en en en en en en en en pt zh en en gu en it nl en it sv en en pt en en en en pt en en en en en en en en fr en en en en en en en hu en en en en en en en vi en en pt en en pt en en pt en ru en en en en it en id en en pt en en en en en en en en en en en en en en en en ur en en en en en en en en en en en en en en en en en en en en en en en en en en en en
| The majority of the sites use VM for services but were reluctant wrt the scenarion where the site downloads a service image from a central repository. The main reason is that local images are very customized. Indeed, the big effort is spend in the customization of the images and not on the VM deployment. For that reason, they prefer to deploy an image they've built and control. Nevertheless, if images are available, there is some willingness in giving it a try.
| Images of the most basic services could be tested: site-bdii, UI, WNs or glite-Cluster.
Revision as of 17:35, 20 March 2012
1 Question 1: Deployment of platforms
2 Question 2: Deployment of virtual images
Please reply to both Question 1 and Question 2.
DEADLINE for reply: 20 March 2012
Back to the operations survey main page.
Question 1: Deployment of platforms
Grid software is being provided for multiple OS platforms. For example, the number of supported platforms will increase with EMI 2.0 (Spring 2012): in EMI 2.0 it is expected that all products will be released for sl6, and a subset also for Debian.
EGI operations need to review the list of early adopter sites, to make sure that staged rollout resources are allocated for testing of software on the platforms of interest.
All Resource infrastructure Providers are requested to consult with their site managers to define their priorities. Please define your deployment priorities of sl6 and Debian for 2012 for products released by EMI (ARC, dCache, gLite, UNICORE) and IGE (Globus) by replying to questions in the following table.
Are you insterested in installing some EGI and/or IGE components on Debian-based distributions? If so, which components? in how many sites?
Specify if you are interested in installation of EGI and/or IGE components on other platforms and if so, which components in how many sites
dCache, DPM, and EMI WN (4 sites)
EMI UI (10 sites)
We (4 sites) are interested in SL6 versions of all components.
We (4 sites) are interested in a Debian/Ubuntu based WN/UI
UIIP have developed UNICORE distribution for Windows and we are ready to maintain this and further develop.
No plans for upgrade to SL6 in 2012.
No plans to deploy services on Debian.
We use CentOS distribution on all sites. The top priority for us is to have official support for CentOS.
No plans for upgrade to SL6 in 2012.
Yes, all major services are running on SL* machines, SL6 is interested.
Yes, there is interest in a Debian based WN. Server support for Debian would be welcomed, however, without better information we don't have concrete plan.
All 10 clusters but one are already SL6 based, ARC is currently installed from the NorduGrid repo. DPM and SAM Nagios are on SL5 until they can be migrated.
No plans for Debian, except for clients.
we are interested in all EMI components for SL6. As we already have most components running at SL.
Migration from SL5 to SL6 for all components planned when stable releases arrive (1 site)
ARC InfoSys (1 site)
ARC CE, ARC clients (2 sites), Redhat Linux 5.6, Suse Linux 11
All sites are interested in having ALL local middleware components (CREAM, SEs (DPM, STORM, DCACHE), APEL, SITE-BDII, UI, WNs, GLEXEC, ARGUS and LRMS_UTILS) supported in SL6. There is some special emphasis on clients (UIs and WNs) so that is where the support work should start.
The sites which manage core services also want core services supported in SL6 with special emphasis on WMS, TopBDII, VOMS and LFC
Only one site show interest in having middleware components supported in Debian/Ubuntu
CentOS seems better supported than SL (reacts faster to new kernel releases, security issues). Some sites have some services deployed in CentOS5.
Mark this as "good to have".
Plan to run some WNs on SL6 in 2012 at one site. When installing new services / releases of other services we will consider SL6.
There is high interest in gLite components on Sl6, WN and UI with high priority (survey sent to all Italian sites (54), 22 responses received.)
there is low interest in gLite components on debian (four site), starting from WN and UI (survey sent to all Italian sites (54), 22 responses received.)
there is low interest in gLite components on other platform (one site): the platform is SUSE (survey sent to all Italian sites (54), 22 responses received.)
No plans for upgrade to SL6 in 2012
We are interested in SL6 versions of all components
There is interest in a Debian/Ubuntu based WN/UI
All biggest sites (5) are interested in SL6 versions of gLite components. For UNICORE components all sites express interest in SL6 version (seems nothing SL-specific is needed than just CentOS 6).
We are interested in SL6 versions of all components (all sites).
There is an interest for Debian/Ubuntu based UI (large number of Grid users).
Upgrade from SL5 to SL6 likely on one site
Ubuntu in use at one site
4 sites currently use Centos5
CREAM-CE, DCACHE, WN, GLEXEC, DPM servers/clients, site-bdii, glite-UI, ARC CE/ARC client. With lower priority ARGUS, VOBOX, NAGIOS, APEL, CLUSTER.
YES. Components needed: ARC client and A-REX server. GridFTP server.
DPM disk servers on Solaris. We have some, but the support is not assured.
All major services and sites are configured on SL and we are interested with the components on SL6: CreamCE, DPM server/disk,WN, site-bdii, gLite-UI. The other services like VOMS, WMS, LFC_mysql, Nagios, top-BDII with lower priority.
We are interested in SL6 versions of all components of EMI (ARC A-REX, dCache, CREAM CE, gLExec, WMS, Nagios, WN, UI, DPM, StoRM).
Some sites are insterested in Debian/Ubuntu based WN/UI.
CentOS 5 & 6 (~10 sites), Ubuntu Server (1 site) and Fedora (3 sites).
Question 2: Deployment of virtual images
EGI SA2 is deploying a new Market Place based on StratusLab. The new Market Place will include different Virtual Machines with different middleware services ready to be used, verified and tested by SA2 team. Is your NGI willing to use the new service to download and use pre-installed VMs from the marketplace?
If you replied yes, in which service images are you interested in? eg. User Interfaces (emi-UI), Storage, Job Submission (WMS), Compute Elements (Cream/unicore/arc), etc.
Not at this stage, but we will investigate it further.
CREAM CE, WN, UI, DPM
The majority of the sites use VM for services but were reluctant wrt the scenario where the site downloads a service image from a central repository. The main reason is that local images are very customized. Indeed, the big effort is spent in the customization of the images and not on the VM deployment. For that reason, they prefer to deploy an image they've built and control. Nevertheless, if images are available, there is some willingness to give it a try. So, the answers is NES.
Images of the most basic services could be tested: site-bdii, UI, WNs or glite-Cluster.
there is interest/curiosity on VM but...
the provided images should be locally managed by a different cloud infrastructure (i.e. we would use the marketplace but not install the StratusLab stack).