Hi David, In principal, adding new services isn't a problem. On 23/09/14 14:49, david.meredith@stfc.ac.uk wrote:
1. name of service: com.schedmd.SlurmClient 2. high-level description of the service functionality: SLURM (Simple Linux Utility for Resource Management) is an open-source resource manager designed for Linux clusters of all sizes. Machine flagged this type is hosting software to submit jobs to SLURM. http://slurm.schedmd.com/
However, this one looks wrong. A service is normally distinguished by having an endpoint through which a client can interact with it. For this reason, Service objects are normally servers, not clients. What you describe sounds like client software for interacting with SLURM: i.e., the software installed on some machines that lets one submit jobs into a SURLM-managed batch system. Would this service describe a machine that a user can log into somehow (ssh?) and, once logged in, can submit jobs via SLURM client? If so, it sounds a bit like a EGI UI machine: how do we publish these currently?
1. name of service: eu.unity-idm.Unity 1. name of service: eu.unicore.UnicorePortal 1. name of service: eu.egi.egrant
These all looks reasonable ... Although I'm sure we can have the discussion about which level of granularity makes sense for Type --- or if it makes sense having Service.Type at all :-) Cheers, Paul.