Fedcloud-tf:WorkGroups:Scenario3

Main

Roadmap and Innovation

Technology

For Users

For Resource Providers

Media

Workbenches:

Open issues

Scenario 1 VM Management

Scenario 2 Data Management

Scenario 3 Information Systems

Scenario 4 Accounting

Scenario 5 Monitoring

Scenario 6 Notification

Scenario 7 Federated AAI

Scenario 8 VM Image Management

Scenario 9 Brokering

Scenario 10 Contextualisation

Scenario 11 Security

Scenario 3: Integrating information from multiple resource providers

Leader: David Wallom, OeRC

Scenario collaborators

Role	Institution	Name
Scenario leader	OeRC	David Wallom
Collaborator	OeRC	Matteo Turilli
Collaborator	EGI.eu	Peter Solagna
Collaborator	INFN	Elisabetta Ronchieri

Information that should be published by a cloud service

The following are the information identified during the TF F2F meeting:

Please add more points edit/comments the list

1. What is the name of the resource and what type of interface can I use to manage instances on the resource?
   1. What is the endpoint I should contact to interact with the cloud management interface? (E.g. the url of the web-service/portal)
2. What are the AuthN and AuthZ rules that operate on your cloud?
3. What instances are already installed on the resource and am I allowed to upload my own instances?
4. If I am able to upload instances what format of instances does the resource accept?
5. Is there a data interface available and if so what is it?
6. What is the overall size of the resource?
7. Are instance templates defined that limit the choice of instance scales I am able to run?
8. What type of virtual network can I establish on the resource?
9. Does the resource support cloud scalability through managed bursting to another external provider?

The following are questions on the dynamic information;

1. I have a virtual instance that requires X,Y,Z resources, does your cloud have A>X, B>Y,C>Z resource available?
2. My instance is short lived is its utilisation of resources going to be captured in the information system such that overprovisioning will/will not occur?
3. What is the charging scheme and how much will using your cloud cost?

How to render those information in GLUE2

Note: BDII service speaks only GLUE2. The Cloud information need to be squeezed in the current set of GLUE2 Entities. If the schema is extended to include Cloud-specific entities, it needs to be officially approved by OGF and implemented in the various glue-schema glue-validator components deployed with the BDII.

Use the currently available GLUE2.0 entities

Currently the GLUE2 includes two main conceptual models for Computing Elements and Storage Elements. These elements should be used to model the Cloud capabilities remaining compliant to the current GLUE2.0 schema.

Capabilities for cloud services

Note: bold capabilities are new, not already in GLUE2 specification. Adding new capabilities do not requires an extension of the GLUE2 schema.
Please: add new high level capabilities if you feel that something is missing. These capabilities are used in the following entities.

Capability	Description
cloud.VMmanagement	This is the standard capability that every cloud service should publish if it allows to instantiate/suspend/delete virtual machines
cloud.virtualImagesUpload	This is the capability that allows users to upload their own virtual images through the cloud interface
security.authentication/security.authorization	I would leave those capability, given that every cloud provider has authentication

Computing Service entity description

• This Service is used to describe the computing resource itself, decoupling from the Grid endpoint.
• Attributes that need to be provided by the resource providers are in bold

Attribute	Type	Multiplicity	Description
Creation time	..	..	..
Validity	..	..	..
ID	..	..	..
Name	String	1	Human readable name. It could be used to fill the information: "what is the name of the resource"
OtherInfo	String	n	Placeholder to add information that does not fit into any other attribute. Cloud information that cannot be mapped in other attributes could be added here.
Capability	Capability_t	n	This attribute lists the capabilities available for this service, currently the type Capability_t does not include specific cloud capabilities. Being an open enum type it can be extended with additional capabilities. Currently some of the already available capabilities are: security.accounting, security.authentication or information.logging. We could consider to add capabilities like "cloud.vm.uploadImage" to add the information in the quesiton: "am I allowed to upload my own instances?". To identify cloud services there would be the need to add a new capability, common to all the cloud services regardless of their specific capabilities, like: "cloud.managementSystem" (nb: stupid example). Resource providers, in this design stage, could provide just descriptions of the capabilities they would like to publish. I (Peter) will try to group them proposing some labels for the different capabilities.
Type	ServiceType_t	1	Type of service in a reverse namespace model, e.g.: org.glite.lb or org.glite.wms. It could be org.opennebula, org.stratuslab or com.cloudsigma

There are, then, a number of more attributes (static and dynamic) that could be used by cloud services, like: StatusInfo,TotalJobs, RunningJobs etc etc. Please note that Location is a GLUE2 entity that can be linked to the Service entity, this could answer to the "Where is located the cloud facility?" question.

ComputingEndpoint description

Every ComputingService has associated one or more Computing Endpoint. The endpoint is used to create, control am monitor computational activities.

• Resource providers should provide the information to create one endpoint for each interface they're exposing for the cloud service.

Attribute	Type	Multiplicity	Description
CreationTime	..	..	I will skip the most general, attributes like OtherInfo and Capability(described above).
URL	URI	1	Network location of the endpoint.
Capability	Capability_t	0..n	It's the same field of the Service entity. Some capability could be interface-specific. I would replicate all the general capability also for this instance.
Technology	EndpointTechnology_t	1	Examples are "webservice" and "corba". We could add "webportal" or something like this to clarify that the endpoint refers to a web application.
InterFaceName	InterFaceName_t	1 (mandatory)	The interface in the cloud case could be OCCI, EC2, jclouds or "webinterface". This can answer to the question: "what type of interface can I use to manage instances on the resource?"
InterfaceVersion	..	..	No description needed.
Supported profile	URI	*	We can define, here, a set of profiles for the authN/authZ of the users, like uri:sec:x509.

ExecutionEnvironment

The ExecutionEnvironment class describes the hardware and operating system environment in which a job will run. It could be used to describe the VM images already available in the Cloud service.

Attribute	Type	Multiplicity	Description
Platform	Platform_t	1	The platform atchitecture, can be: amd64,i386,itanum,powerpc,sparc
TotalInstances/used instances	-	-	These attributes are not relevant in a cloud environment, where the execution environment are deployed dynamically.
PhysicalCPUs	UInt32	0..1	The physical CPUs are not relevant - I would say- in a virtualised environment.
LogicalCPUs	UInt32	0..1	This attribute could be used to express the maximum number of cores that is possible to instantiate in a single VM of this type (likely it will be common to all the execution environments of the same cloud service).
MainMemorySize	UInt64	1	Max physical memory that is possible to instantiate on a single VM.
OSFamily OSName OSVersion	(*)	1	Attributes which define the operating system available. There will be an execution environment for every virtual machine available in the cloud service. We should define some placeholders to create an ExecutionEnvironment stub to describe the max cores/memory for the virtual machines uploaded by a user.

Deploy a new set of entities

This is the next step: define cloud specific GLUE entities to extend the GLUE2 schema in order to publish the cloud services in a standard way.

Technical implementation

For a first demo the best technical choice is to go for openldap, which is available in almost all the *nix machines in the world. On top of that, openldap is the server used by the gLite BDIIs, therefore it would be easy to use the same configuration files set-up used for the GRIS or the GIIS.

• Use the GLUE20.schema in the slapd.conf file to enable all the GLUE2.0 entities.

Resource providers to be published for the demo

RP Name	RP contact name	Resource Centre name to be published (was Site Name)	Country	Capabilities to be published (specify the endpoints supporting the capabilities!)	Other info to publish	VM Manager	V.Images available (OSFamily,OSName,OSVersion)
CESNET	Miroslav Ruda	CESNET Cloud	Czech Republic	cloud.managementSystem, cloud.vm.uploadImage		XEN	1.) Linux, OpenSUSE, 11.4 2.) Linux, Debian, 6.0.3
KTH	Zeeshan Ali Shah	KTH-PDC Cloud	Sweden	cloud.managementSystem, cloud.vm.customimage, cloud.data.cdmi
GWDG	Piotr Kasprzak	GWDG Cloud	Germany	cloud.managementSystem, cloud.vm.uploadImage		KVM	1.) Linux, Scientific Linux, 6.1 2.) Linux, Ubuntu, 11.10
CYFRONET	Jan Meizner	CYFRONET Cloud	Poland	cloud.managementSystem, cloud.vm.uploadImage		KVM
CESGA	Alvaro Simon	CESGA Cloud	Spain	cloud.managementSystem, cloud.vm.customimage		KVM	SL5