August 2009 - occi-wg - lists.ogf.org

APIs for search in Clouds
by Mehdi Sheikhalishahi 28 Aug '09

28 Aug '09

Dearr OCCI Standard, In the future, on the internet we will have a huge number of IaaS cloud providers for different purposes. It would be great if they can provide enough information about their capabilities and features such as which kind of hypervisors they support, how much capacity for different resources (compute, storage, network) they can offer, how much it costs for usage and these sort of things. This is like search on the Web but with more precise information and standards. I don't know which kind of Information System for search would be most suitable for search based on the Web with search engines or based on the current Grid Systems. Anyway, I think providing some APIs for this would be useful. What's your ideas? -- Best Regards, Mehdi Sheikhalishahi

3 2

Name of the Top Level OCCI logical container
by Gary Mazz 27 Aug '09

27 Aug '09

Hi, As we are seeing editorial changes occuring to the OCCI standard document. I noticed we don't have a name for the top level occi container. Today, it is referred to as "common attributes". Although I'm a fan of generic naming conventions, I was hoping for something a little more descriptive. Suggestions welcome. -gary

1 0

Reminder: weekly OCCI concall tomorrow at 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST
by Thijs Metsch 26 Aug '09

26 Aug '09

Hi folks, With last weeks concall not taking place we have a lot to discuss tomorrow. So next concall will take place tomorrow (Wednesday August 26, 2009) at 07:00 PDT, 10:00 EDT, 15:00 BST, 16:00 CEST. You can find the conference bridge details further down here... The Agenda is currently set to: - API specification status We will define action items for the upcoming week and discuss those action items from now on every week. Current action items include: * update the document according to the attributes discussing thread * update the document with new wordings sent to the list. We still need volunteers to do so but we'll disciss that domorrow. - Durability property for storage - SNIA/OCCI There is a whitepaper about SNIA/OGF OCCI. It can be found here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Concall20090… - OCCI/OVF demo? Craig asked if we could do something like this. So please join the call tomorrow. It is very crucial that we keep on track an deliver our specification document very soon. All the best, -Thijs Passcode: Participant: 9032568 Dial in numbers: Country Toll Numbers Freephone/Toll Free Number ARGENTINA 0800-777-0463 AUSTRALIA ADELAIDE: 61-8-8121-4868 1-800-249-288 AUSTRALIA BRISBANE: 61-7-3102-0970 1-800-249-288 AUSTRALIA CANBERRA: 61-2-6100-1970 1-800-249-288 AUSTRALIA MELBOURNE: 61-3-9010-7739 1-800-249-288 AUSTRALIA PERTH: 61-8-9467-5249 1-800-249-288 AUSTRALIA SYDNEY: 61-2-8205-8125 1-800-249-288 AUSTRIA 43-1-92-86-506 0800-005-029 BELGIUM 32-1-150-0314 0800-4-8680 BRAZIL 0800-7610674 CHILE 1230-020-2867 CHINA* 86-400-810-4766 10800-712-1433 10800-120-1433 COLOMBIA 01800-9-156430 CZECH REPUBLIC 420-2-25-98-56-54 800-700-173 DENMARK 45-7014-0280 8088-6132 ESTONIA 800-011-1089 FINLAND Land Line: 106-33-146 0-800-1-10100 FINLAND Mobile: 09-106-33-146 0-800-1-10100 FRANCE LYON: 33-4-26-69-12-81 080-563-9647 FRANCE MARSEILLE: 33-4-86-06-00-81 080-563-9647 FRANCE PARIS: 33-1-70-70-74-20 080-563-9647 GERMANY 49-69-2222-2566 0800-000-3441 GREECE 30-80-1-100-0683 00800-12-6973 HONG KONG 852-2286-5731 800-930-705 HUNGARY 06-800-18013 INDIA 000-800-852-1266 INDONESIA 001-803-011-3787 IRELAND 353-1-247-5253 1800-932-145 ISRAEL 1-80-9214916 ITALY 39-02-3600-3642 800-986-570 JAPAN OSAKA: 81-6-7739-4769 0034-800-400828 JAPAN TOKYO: 81-3-5539-5189 0034-800-400828 LATVIA 8000-3025 LUXEMBOURG 352-27-000-1360 MALAYSIA 1-800-80-2812 MEXICO 001-866-627-0574 NETHERLANDS 31-20-718-8533 0800-020-1392 NEW ZEALAND 64-9-970-4769 0800-449-823 NORWAY 47-21-59-00-59 800-15414 PANAMA 011-001-800-5072129 PERU 0800-53733 PHILIPPINES 63-2-858-3715 POLAND 00-800-1212021 PORTUGAL 8008-14061 RUSSIA 8-10-8002-9683011 SINGAPORE 65-6883-9228 800-120-4662 SLOVAK REPUBLIC 421-2-322-422-21 SOUTH AFRICA 080-09-80416 SOUTH KOREA 82-2-6744-1081 00798-14800-6860 SPAIN 34-91-414-62-98 800-099-810 SWEDEN 46-8-505-78-524 0200-890-106 SWITZERLAND 41-44-580-4389 0800-001-523 TAIWAN 886-2-2795-7377 00801-137-766 THAILAND 001-800-1206-65656 UNITED KINGDOM BIRMINGHAM: 44-121-210-9021 0808-238-6025 UNITED KINGDOM GLASGOW: 44-141-202-3221 0808-238-6025 UNITED KINGDOM LEEDS: 44-113-301-2121 0808-238-6025 UNITED KINGDOM LONDON: 44-20-7075-3246 0808-238-6025 UNITED KINGDOM MANCHESTER: 44-161-601-1421 0808-238-6025 URUGUAY 000-413-598-3415 USA 1-203-418-3122 866-692-3163 VENEZUELA 0800-1-00-3733 -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

3 4

Documents to mention in our use cases and requirements document
by Thijs Metsch 26 Aug '09

26 Aug '09

Hi guys, Is their any other document other than this one http://groups.google.com/group/cloud-computing-use-cases/browse_thread/thre… which we should/could mention in our use-case and requirements document? Also do we want to add the cloud API features matrix and comparison to our document? Keep in mind that we than have to do a more detailed investigation which will take time... Cheers, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

2 1

Re: [occi-wg] OCCI API Document Recommendations
by Gary Mazz 20 Aug '09

20 Aug '09

I sent this out a few days ago, but it never hit the reflector. I should have realized, I wasn't flamed... :) -gary Hi, I've been looking at the API document over the past couple of days and have some ideas I would like to float by the api team that may help it along its path to completion. I don't have a bunch of time, apologies for the terseness. I would just like to get them down so we can mull them about. -gary Overall strategy: Split the document into 4 parts: 1) a FAQ 2) the walkthough (which an Atom version is already in a white paper of sorts) 3) The core API document which included front matter; the description of the IaaS model components and a description and organization of datum (taxonomy); state diagram & states; the APIs based on CRUD operations including verbs and associated data; and completion codes 4) Mapping to the different API formats, ie, Atom, JSON, text and whatever else someone would want. The mapping document includes mapping of data to XML, CRUD verbs to HTTP operations and mapping of completion codes. This also included the methodology for connection, authentication, implementation specific data formats and representations. Details 1) Section 2: Move to White paper 2) Section 3: Move to FAQ 3) Section 4.3.1. Atom XML: Move to Atom Mapping specification 4) Section 4.3.2. Plain Text: Move to Plain Text Mapping specification 5) Section 4.3.3. JSON: Move to JSON Mapping specification 6) Section 4.5. References: Move to front matter "Normative References" 7) Section 4.6.1. IANA Considerations: Move to Appendix 8) Section 4.6.1. 6. OCCI Registries: Remove HTTP numerations and shift them to the appropriate mapping specification 9) New Appendix for Conformance : Extensions defined in sections 4.4 and 5.2 implies ans states level of conformance. A list of operations and data supported for levels of conformance needs to be defined. 10) Much of the operations are written around HTTP atom. This needs to be more generic. Definitions Required (in alphabetical order): Asynchronous operation Atom XML Average rate of progress Categories checksum CIDR notation Clock Clock speed Cloud Cloud infrastructure compute CPU CPU Architecture CPU core Current rate of progress Date device device persistence dmz DNS DNS hostname Drive Drive size ECC etag Finish time Float FQDN gateway gateway address Gbit/s gigahertz hostname HTTP HTTP header Human readable label identifier immutable resource infrastructure Integer IPv4 Address JSON Link Link target Linking megabytes memory model netmask netmask address network network address noun operation persistence persistent, Plain Text RAM Related resources reliable Remaining time representation representation resource restart scheme Server start Start time state State machine status message stop storage String Sub-collection Summary Tag Tag based VLAN Task schedule Task sub-type Task type Task(s) term Time Timeout Token transient, unique identifier Unit(s) updated URI URL UUID virtual machine VLAN VLAN ID Work completed Work completed Work remaining

1 0

Concall yesterday
by Thijs Metsch 20 Aug '09

20 Aug '09

Hi guys, Sorry for the messed up concall yesterday. I figured that with our Wiki down some of you didn't have the access code. Only Mark and I where on the call yesterday so we postponed the topics to next week. Again sorry for the inconvenience, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch at sun.com D-93049 Regensburg http://www.sun.com

2 1

Reminder: concall tomorrow (19.08.2009) at 4pm CET
by Thijs Metsch 18 Aug '09

18 Aug '09

Hi, our weekly concal will take place tormorrow at 4pm CET. For your timezone and the conference bridge information have a look here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… The current agenda can be found in our wiki - you can add the topics you would like to discuss there as well: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Concall20090… All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 1

Re: [occi-wg] OCCI specification document
by Richard Davies 18 Aug '09

18 Aug '09

Hi all, Some brief comments after reading through the current (23 July) draft specification. Cheers, Richard. 2.3 Operations As described, Create is form-encoded, Retrieve is in application/occi+X, Update is in application/occi+X, Delete doesn't need a format, and Requests are form-encoded. I'd like us to also support application/occi+X for Create and Requests so that it's possible to write a client which only knows about a single format rather than having to implement at least two (form + one occi+X). 5. Nouns and attributes You'll need to make storage.size a Float, like compute.memory.size to allow drives below 1 GB (e.g. CD images). Alternatively (and better in my view), you could turn all of Floats into integers and describe them in the basic units - bytes, hertz, etc. Compute and storage resources need better status and support for being transient or persistent (a cloud could support both models, so needs to be told which a given resource will be, since the semantics are different when a server shuts down). I'd suggest: - Compute: add a 'status', which is 'active', 'stopped', etc. (maybe 5.2.1 state machine handles this? But the section is empty). - Compute: add a 'compute.type'? which is Enum(transient, persistent). - Storage: add a 'status' which is 'mounted', 'inactive', etc. (again, does 5.2.1 handle this?) - Storage: reliability isn't the same as transient/persistent. A persistent storage is one which isn't destroyed when the compute shuts down. It could still be on RAID, local disk, SAN, etc. So split out 'storage.type'? which is Enum(transient, persistent) from storage.reliability For networks, I feel there's missing content: - There is no mechanism described for static IPs on the public internet - The network.ipv4 is almost enough to run a DHCP server, but not quite. You'd really need name servers too. What is the hostname attribute in table 7? Is this just an example? I don't really see it as a common attribute, so that networks and storage have a hostname... I definitely feel that the compute.memory.speed, compute.memory.reliability and storage.reliability are less important than the other attributes described. 4.4.3 Links I'd like to see a little more detail here on how I specify the interface by which compute is linked to storage or network. (e.g. eth0, eth1, sda, sdb, etc). Presumably this will end up in the link[i].rel field? Will we specify canonical interface names for OCCI or allow each cloud to chose its own (eth0 vs. Local Area Network, sda vs hda, etc.)? How will a compute resource specify which of many linked storage resources it should boot from? 4.2 Collections "Operations that return multiple resources are rendered ..." shall we write "Operations which COULD return multiple resources..." to make it clear that Atom is always returned, even if there is a single result? Or should we explicitly say that single results are NOT returned as Atom.

4 5

OCCI specification document
by Thijs Metsch 18 Aug '09

18 Aug '09

Hi @all, The current version of the OCCI specification can be found here: http://forge.ogf.org/sf/go/doc15731?nav=1 Please have a look with a special look on the attributes defined in the document? Are any missing? Are there to much? What about the naming? We will be working on the document in the next days to push it further to get it done for OGF27. So more details and information to come. For now comments and ideas about the attributes are more then welcome! All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

5 8

Some notes on work done in the background
by Thijs Metsch 14 Aug '09

14 Aug '09

Hi, Most of you might know that the wiki on http://www.cloud-standards.org tries to give an overview of all Cloud standards. Especially with a focus on collaboration! There is also a diagram showing the positioning of all the cloud standards: http://cloud-standards.org/wiki/index.php?title=Cloud_standards_positioning It is a first short but looking promising. Next to that talks with the Cloud group inside of SNIA are going on - we are probably going to have a whitepaper describing the how OCCI and SNIA can work together. There if not much going on on the DMTF front currently. OGF itself is heavily engaged in pushing OCCI and other topics. For example several guys are currently at the CloudWorld (You might have seen the email from Joel about it - there is a OCCI one pager btw). Next to that OGF talks to many other organizations and goverments about Cloud Standards and howto collaborate. Finally OCCI itself is represented pretty good as well: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Presentations I just wanted to give you all an update of what is going on in the background. Of cause we are also working on our specification so stay tuned. All the best, -Thijs -- Thijs Metsch Tel: +49 (0)941 3075-122 (x60122) http://blogs.sun.com/intheclouds http://www.twitter.com/befreax Software Engineer Cloud, Grid and Virtualization Sun Microsystems GmbH Dr.-Leo-Ritter-Str. 7 mailto:thijs.metsch@sun.com D-93049 Regensburg http://www.sun.com

1 0