One thing I forgot to mention is that going forward, I think a good approach for us to take would be to do something similar to what Salvatore is proposing, but do it across the board. What I mean is that we should abstract the existing entities a little bit and then add entities that are more specialized/concrete. This would allow us to include specialized information in the schema and also provide entities with names that others understand at a glance (if I have to explain what a ComputingActivity/Manager/Service/Share is one more time... :-P). It'll also allow us do any little cleanup changes we've come across in the current schema. A few quick examples about how this could be done: current ComputingShare: * create ClusterQueue entity that is a specialization of ComputingShare * create CloudAvailabilityZone entity that is a specialization of ComputingShare? * create CloudTenant entity that is a specialization of ComputingShare (and other entities) * change attribute names containing 'Jobs' to 'Activities' * move 'MappingQueue', '*Slots', '*WaitingTime' to ClusterQueue entity current ComputingActivity: * create ClusterJob specialization * create GridJob specialization (e.g. a job managed by a grid resource manager/scheduler) * create CloudInstance specialization * move Local* attributes to GridJob * move WaitingPosition to ClusterJob and GridJob * delete ComputingManager* * move ProxyExpirationTime to GridJob current ExecutionEnvironment: * create ClusterNode specialization (also used for physical nodes in clouds) * create CloudFlavor specialization * remove VirtualMachine attribute * move TotalInstances, UnavailableInstances to ClusterNode I think this will be relatively straightforward to do for the computing and storage entities. I guess what I'm proposing/asking is if we are talking about making nontrivial changes to the schema, why don't we just start work on GLUE 3.0? Warren ________________________________________ From: Warren Smith Sent: Wednesday, March 26, 2014 12:49 PM To: OGF GLUE Working Group Subject: glue2 cloud examples Hi all, I put some examples of how I'm representing an IaaS cloud using GLUE 2 into https://github.com/OGF-GLUE/JSON/tree/master/examples. Look for the files ending in openstack.json and the file images.json. I use a few extensions, but not very many. My approach is: Instance/Virtual Machine - ComputingActivity Physical Node - ExecutionEnvironment Virtual Machine Image - ApplicationEnvironment/Handle I haven't done anything with storage at this point, but my approach would be to handle an object or image store the same as a shared/parallel file system. I also haven't done anything related to describing virtual networks - GLUE 2 doesn't have much support for describing networks in general. VLANs, overlay networks, etc. are used outside of cloud environments as well as in cloud environments, so I don't know if there would be any need for separate entities/schemas for cloud vs non-cloud environments. Warren