Dear all,

Reviewing the cloud part of the proposed draft I think we should also change a bit the references to the hypervisors as these are not normally exposed at all to the users and even irrelevant for most cases. Instead the CloucComputingManager should be what is described now as the Cloud Middleware.

In the "Conceptual Model of the Cloud Computing Service" it is stated:
* An Hypervisor, usual name for Virtual Machine Manager, is a piece of computer software, firmware or hardware that creates, runs and manages Virtual Machine
* A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers (namely Infrastructure as a Service feature), but also storage (Storage as a Service) and other rich services (Platform as a Service, etc…).

I would turn this into:
* A Cloud Middleware is a piece of computer software that leverages on hypervisor virtualization capabilities to provide Virtual Machines on-demand to final users. The Cloud Middleware may provide not only virtual servers, but also storage and other rich services (e.g. Platform as a Service).

And then in the CloudComputingManager:
Current text:

The CloudComputingManager class is a specialization of the Manager class for the computational capability (Virtual Machines) manager. The CloudComputingManager is responsible for the local control of resources. The CloudComputingManager layer is not exposed directly to external clients or to the Virtual Machines themselves.


The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines. A Compute Service will usually have only one Compute Manager, but MAY have more. The class provides aggregated information on controlled resources, hypervisors limits and also describes local storage extents accessible to the Virtual Machines.


I propose to just remove the "The Virtual Machine manager is usually referred as Hypervisor, thus a piece of software, firmware or hardware which creates, runs and manages Virtual Machines." sentence.


Any other references to hypervisor should be updated.


Regards,

Enol


On Thu, 31 May 2018 at 16:31 Alessandro Paolini <alessandro.paolini@egi.eu> wrote:
Dear all,

over the last months it was discussed with the cloud providers the necessary network attributes to publish in the BDII and we arrived to a good compromise.
So we would like to discuss with you the latest changes to the draft before getting the approval for implementing the new schema in production.


I still need to update the figures, which for the moment you can find here: 

Here is the list of the latest classes and attributes added/modified:

Classes:
ComputingShareAcceleratorInfo
ComputingManagerAcceleratorInfo
AcceleratorEnvironment
CloudComputingShareAcceleratorInfo
CloudComputingManagerAcceleratorInfo
CloudComputingImageAcceleratorInfo
CloudComputingImageNetworkTraffic
CloudComputingInstanceAcceleratorInfo


Attributes:
GLUE2EndpointAuthentication
GLUE2ComputingEndpointAuthentication
GLUE2CloudComputingEndpointAuthentication
GLUE2CloudComputingShareDefaultNetwokType
GLUE2CloudComputingSharePublicNetwokName
GLUE2CloudComputingShareProjectID
GLUE2CloudComputingVirtualAcceleratorComputeCapability
GLUE2CloudComputingVirtualAcceleratorVirtualizationType
GLUE2CloudComputingImageContextualizationName
GLUE2CloudComputingImageContextualizationVersion
GLUE2CloudComputingImageDescription
GLUE2CloudComputingImageVersion


Storage attributes:
StorageShareNumberOfFiles (requested by ATLAS)



Best regards,
Alessandro

--
Dr. Alessandro Paolini
Operations Officer - EGI Foundation
Science Park 140
1098 XG Amsterdam
The Netherlands
skype: alessandro.paolini.egi
*********************************
"I believe in the power of laughter and tears"
    "as an antidote to hatred and terror"
          "A day without laughter"
             "is a wasted day" >>> Charlie Chaplin