March 2010 - occi-wg - lists.ogf.org

OCCI and CloudAudit at CloudConnect 2010
by shlomo.swidler＠gmail.com 21 Mar '10

21 Mar '10

I presented OCCI and CloudAudit at the CloudConnect event this week, on Wed. 17 March, the third day of the conference. The presentation is on SlideShare: http://www.slideshare.net/shl0m0/cloud-connect-occi-cloudaudit-standards-up… This was given as the first presentation of the day, in the session entitled "Where we are today: the state of the standards". I received very positive feedback on it; two people independently came up to me and said it was the best presentation they'd yet seen at the conference. The contentious standards panel that you may have heard about happened later in the day. Some links to various writeups about that: http://www.informationweek.com/blog/main/archives/2010/03/let_stormy_sess.h… http://doubleclix.wordpress.com/2010/03/17/the-art-of-cloud-standards/ Shlomo -- Shlomo Swidler Cloud Computing Consultant, Developer, Amazon EC2 Expert http://www.orchestratus.com/ http://www.shlomoswidler.com/

3 4

GSOC project proposal: OCCI on Nimbus
by Andre Merzky 19 Mar '10

19 Mar '10

Amongst a large number of interesting GSOC project proposals from te globus folx, there is also this one http://dev.globus.org/wiki/Google_Summer_of_Code_2010_Ideas#Expand_Nimbus_R… which seems to work towards an OCCI implementation for Nimbus. So, in case anybody here knows a good student who could pull this off, please forward that link. That implementation would w/o doubt benefit both OCCI and Globus/Nimbus. Best, Andre. -- Nothing is ever easy.

3 3

DCI Federation Protocol WG BoF at OGF28, Munich
by Alexander Papaspyrou 17 Mar '10

17 Mar '10

----- Apologies if you receive multiple copies of this message ----- All, on behalf of the D-Grid Initiative project "D-Grid Scheduler Interoperability" I would like to invite you to join a Birds-of-a-Feather session for a DCI Federation Protocol WG during the upcoming OGF in Munich. The overall topic is the chartering of the group for working on recommendations that allow the federated use of Distributed Computing Infrastructures across the borders of traditionally separate computing infrastructures. The session is currently scheduled for Wednesday, March 17, 10.30 a.m. Please note that, due to collisions with various other sessions and private meetings, this might be subject to change and rescheduled to Wednesday afternoon. A topic summary and session details can be found online at http://www.ogf.org/gf/event_schedule/index.php?id=2030 The agenda for the 90 minute session will be: - Walkthrough the project goals and status of DGSI and prospects for a standard - Collection of potential adopters - Formulation of a draft charter - AOB Feel free to contact me if you have any questions. For a very coarse overview, feel free to have a look at a presentation from the latest CloudScape conference on SlideShare (http://www.slideshare.net/alexanderpapaspyrou/federating-resource-exposure-…) Regards, -- Alexander Papaspyrou alexander.papaspyrou(a)tu-dortmund.de

1 1

Rich Wolski on Cloud APIs
by Alexis Richardson 12 Mar '10

12 Mar '10

http://www.eucalyptus.com/blog/2010/03/11/cloud-apis

1 0

First Draft of OCCI xml Scheme
by Gary Mazz 10 Mar '10

10 Mar '10

Hi, This is the first draft of the occi xml scheme. Its not the final version but, its about 100% of what occi defines. I'll be following up with the xml reference file. Notes: 1) This version of the scheme is based on assigning all occi resources xml elements and occi metadata to XML attributes. This creates a problem in XML scheme version 1.0. Defining the "id" attributes as unique and defining enumerated values for attributes is unsupported. 2)I'll move to the 1.1 version as soon as I figure out 1.1 constraints 3) Occi float values are currently defined as decimal, just to make parsing easier. cheers, gary <?xml version="1.0" encoding="utf-8"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="collection"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="compute"> <xs:complexType> <xs:attribute name="id" type="xs:string" use="required" /> <xs:attribute name="title" type="xs:string" use="optional" /> <xs:attribute name="summary" type="xs:string" use="optional" /> <xs:attribute name="cores" type="xs:positiveInteger" use="optional" /> <xs:attribute name="architecture" type="xs:string" use="optional" /> <xs:attribute name="hostname" type="xs:string" use="required" /> </xs:complexType> </xs:element> <xs:element maxOccurs="unbounded" name="network"> <xs:complexType> <xs:attribute name="id" type="xs:string" use="required" /> <xs:attribute name="allocation" type="xs:string" use="optional" /> <xs:attribute name="title" type="xs:string" use="optional" /> <xs:attribute name="summary" type="xs:string" use="optional" /> <xs:attribute name="address" type="xs:string" use="optional" /> <xs:attribute name="gateway" type="xs:string" use="optional" /> <xs:attribute name="vlan" type="xs:unsignedInteger" use="optional" /> <xs:attribute name="label" type="xs:string" use="optional" /> </xs:complexType> </xs:element> <xs:element maxOccurs="unbounded" name="memory"> <xs:complexType> <xs:attribute name="id" type="xs:string" use="required" /> <xs:attribute name="title" type="xs:string" use="optional" /> <xs:attribute name="summary" type="xs:string" use="optional" /> <xs:attribute name="size" type="xs:decimal" use="optional" /> </xs:complexType> </xs:element> <xs:element maxOccurs="unbounded" name="storage"> <xs:complexType> <xs:sequence minOccurs="0"> <xs:element name="link" type="xs:anyurl" /> </xs:sequence> <xs:attribute name="id" type="xs:string" use="required" /> <xs:attribute name="title" type="xs:string" use="optional" /> <xs:attribute name="summary" type="xs:string" use="optional" /> <xs:attribute name="size" type="xs:decimal" use="optional" /> <xs:attribute name="status" type="xs:string" use="optional" > </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="id" type="xs:string" use="required" /> <xs:attribute name="title" type="xs:string" use="optional" /> <xs:attribute name="summary" type="xs:string" use="optional" /> </xs:complexType> </xs:element> </xs:schema>

3 2

Re: [occi-wg] OCCI Editor Getting Started Guide (docs/README.txt)
by Sam Johnston 10 Mar '10

10 Mar '10

Good question so I'm copying the list (especially for the benefit of the newcomers). We maintain a Google Code repository at http://code.google.com/p/occi/ which includes a Mercurial (hg) repository at https://occi.googlecode.com/hg/ - this is in addition to the (currently fairly ordinary) marketing site at http://www.occi-wg.org/ and OGF's GridForge at http://forge.ogf.org/ The best way to get at up-to-the-second updates is to go to the Source tab, then Browse. There you'll find a "code" and "docs" directory (the purpose of which should be fairly obvious) and under docs you'll find 3 versions (DocBook XML, PDF and HTML) of each file. Click on e.g. occi-core.html<http://code.google.com/p/occi/source/browse/docs/occi-core.html>and on the right hand side you'll find a "View raw file" link (in this case occi-core.html <http://occi.googlecode.com/hg/docs/occi-core.html>). Note that sometimes the PDF and HTML renderings fall behind the DocBook XML renderings by a few hours/days but regenerating them is fairly straightforward, following the instructions in README.txt<http://occi.googlecode.com/hg/docs/README.txt> Hope this helps, Sam On Thu, Feb 18, 2010 at 6:23 PM, X wrote: > Dear Sam: > > Does your changes to occi docs are available online? > > Regards, > X > > On Thu, Feb 18, 2010 at 1:09 PM, Sam Johnston <samj(a)samj.net> wrote: > > Afternoon all, > > As you know I've been quieter than usual lately (I've been busy changing > > companies/countries) but now I have a little bit of time on my hands I've > > been fleshing out the OCCI spec. Much of the feedback we've received has > > been that it's too abstract (which you'll recall was by design following > the > > format wars of 2009) so I've added some examples to help people visualise > > what's going on. > > I've also added the following guide to the repository as README.txt so as > to > > make it as easy as possible for others to get involved in the editing of > the > > OCCI documents. I had a clash for the call this week but understand this > > issue was raised for the 17th time so hopefully this will put it to bed > and > > make it a lot easier for more of you to get involved - if you have any > > questions you know where to find me. > > Cheers, > > Sam > >> > >> Open Cloud Computing Interface (OCCI) > >> > >> Editor Getting Started Guide > >> > >> Overview > >> > >> ======== > >> > >> "DocBook is a semantic markup language for technical documentation. It > was > >> originally intended for writing technical documents related to computer > >> hardware and software but it can be used for any other sort of > >> documentation." > >> > >> It was selected for OCCI in order to allow us to maintain a single > source > >> and publish to multiple formats: > >> > >> * HyperText Markup Language (HTML) > >> > >> * Portable Document Format (PDF) > >> > >> * Plain Text (TXT) > >> > >> Getting Started > >> > >> =============== > >> > >> You will need the following to get started editing OCCI: > >> > >> * Mercurial (http://mercurial.selenic.com/) > >> > >> * XML Editor (XMLmind: http://www.xmlmind.com/xmleditor/download.shtml > ) > >> > >> 1. Download and install Mercurial and your preferred XML editor. > >> > >> 2. Get a local copy of the occi repository with this command: > >> > >> hg clone https://occi.googlecode.com/hg/ occi > >> > >> 3. Edit the DocBook source (Hint: TDG5 is a great resource both for > >> getting started and as a reference) > >> > >> Checking In > >> > >> =========== > >> > >> If you want to check in changes you'll likely need to create a ~/.hgrc > >> file something like this: > >> > >> [ui] > >> > >> username = John Citizen <john(a)example.com> > >> > >> [auth] > >> > >> occi.prefix = occi.googlecode.com/hg/ > >> > >> occi.username = john(a)example.com > >> > >> occi.password = LF3W8dKKJG5X7 > >> > >> occi.schemes = https > >> > >> You can now commit your changes (with a useful changelog entry please!) > >> using: > >> > >> hg ci > >> > >> hg push > >> > >> Rendering > >> > >> ========= > >> > >> You will need DocBook tools if you want to render the DocBook XML to > other > >> formats (which you should do each time you check in changes): > >> > >> * DocBook XSLT > >> (http://sourceforge.net/projects/docbook/files/docbook-xsl-ns/) > >> > >> * Apache FOP Binaries > >> (http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop) > >> > >> Under Mac OS X (using the default Makefile): > >> > >> 1. Extract docbook-xsl-ns into ~/Library/XML/XSL > >> > >> 2. Extract Apache FOP and copy build/fop.jar and lib/*.jar into > >> /Library/Java/Extensions > >> > >> Then whenever you make changes simply run "make" to generate new HTML > and > >> PDF versions. > >> > >> Resources > >> > >> ========= > >> > >> * Official Site (http://www.docbook.org/) > >> > >> * Wikipedia - DocBook (http://en.wikipedia.org/wiki/DocBook) > >> > >> * DocBook 5.0 - The Definitive Guide > >> (http://www.docbook.org/tdg5/en/html/docbook.html) > >> > >> * DocBook XSL: The Complete Guide > >> (http://www.sagehill.net/docbookxsl/index.html) > > > > > > _______________________________________________ > > occi-wg mailing list > > occi-wg(a)ogf.org > > http://www.ogf.org/mailman/listinfo/occi-wg > > > > > > > > -- > Regards, > X >

4 11

Reminder concall today in 2h and 20min
by Thijs Metsch 10 Mar '10

10 Mar '10

Hi, For the dial-in details have a look here: http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/Teleconferen… We'll discuss some organizational topics for next weeks OGF... 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

1 0

Crossposting to this list
by Thijs Metsch 08 Mar '10

08 Mar '10

Hi, Just a short reminder to you all: Email addresses which are not subscribed to this list are not allowed to post. So I have to manually approve them. So whenever you do some cross postings like to the clouddemo list and the OCCI list - some post might not come through if you don't use the same email addresses for both lists... 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

1 0

occi XML file - first cut
by Gary Mazz 08 Mar '10

08 Mar '10

Hi, This is the first draft of the xml reference document. This is just to give everyone an idea of what the occi xml document will look like. The URL names for the scheme are temporary for today, I'll have the url and address of the occi-pilot.org setup tomorrow. cheers, gary <?xml version="1.0" encoding="utf-8" ?> <OCCI xmlns="http://www.occi-pilot.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.occi-pilot.org occi-xml-01.xsd"> <collection id="VM1-6D5FB012-1ED6-4ce2-A466-19E862DB795B}" title="My VM1" summary="A test Vitrual Machine 1"> <compute id="VM1-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Mains" summary="Main CPUs" cores="" architecture="" hostname=""></compute> <compute id="VM1-F9B6EA5D-BFCE-43a8-B100-B72A0B841CD8" title="Spare" summary="Spared for Failover" cores="2" architecture="x86" hostname="Wally"></compute> <network id="VM1-AC3F20FA-AB76-4fb2-AE31-A81A9467588C" allocation="dhcp"></network> <network id="VM1-AC3F20FB-AB76-4fb2-AE32-A81A9467588C" title="Public" summary="Public" address="" gateway="" allocation="auto"></network> <network id="VM1-AC3F20FC-AB76-4fb2-AE32-A81A9467588C" title="Mgt" summary="Mgt" vlan="22" label="Management Segment" address="172.31.1.10" gateway="172.31.1.1" allocation="manual"></network> <network id="VM1-AC3F20FD-AB76-4fb2-AE32-A81A9467588C" title="Heartbeat" summary="" vlan="12" label="Hearbeat Segment" allocation="dhcp"></network> <memory id="VM1-AC3F20FD-AB76-4fb2-AE31-A81A9467588D" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <memory id="VM1-AC3F20FD-AB76-4fb2-AE31-A81A9467588E" title="Shared" summary="System Memory for Shared" size="1000000"></memory> <memory id="VM1-AC3F20FD-AB76-4fb2-AE31-A81A9467588F" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <storage id="VM1-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Disk1" summary="Main Disk" size="2000000000" status="offline"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM1</link> </storage> <storage id="VM1-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD9" title="Disk2" summary="Transaction Disk" size="2000000000" status="degraded"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM1</link> </storage> <storage id="VM1-E9B6EA5D-AFCD-43a8-B100-B72A0B841CDA" title="Spare" summary="Spared for Failover" size="2000000000" status="online"> <link>http://www.cdmi-pilot.com/demo/CDMI-SPARE-VM1</link> </storage> </collection> <collection id="VM2-6D5FB012-1ED6-4ce2-A466-19E862DB795B" title="My VM2" summary="A test Vitrual Machine 2"> <compute id="VM2-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Mains" summary="Main CPUs" cores="" architecture="" hostname=""></compute> <compute id="VM2-E9B6EA5D-BFCE-43a8-B100-B72A0B841CD8" title="Spare" summary="Spared for Failover" cores="2" architecture="x86" hostname="Wally"></compute> <network id="VM2-AC3F20FA-AB76-4fb2-AE31-A81A9467588C" allocation="dhcp"></network> <network id="VM2-AC3F20FB-AB76-4fb2-AE32-A81A9467588C" title="Public" summary="Public" address="" gateway="" allocation="auto"></network> <network id="VM2-AC3F20FC-AB76-4fb2-AE32-A81A9467588C" title="Mgt" summary="Mgt" vlan="22" label="Management Segment" address="172.31.1.10" gateway="172.31.1.1" allocation="manual"></network> <network id="VM2-AC3F20FD-AB76-4fb2-AE32-A81A9467588C" title="Heartbeat" summary="" vlan="12" label="Hearbeat Segment" allocation="dhcp"></network> <memory id="VM2-AC3F20FD-AB76-4fb2-AE31-A81A9467588D" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <memory id="VM2-AC3F20FD-AB76-4fb2-AE31-A81A9467588E" title="Shared" summary="System Memory for Shared" size="1000000"></memory> <memory id="VM2-AC3F20FD-AB76-4fb2-AE31-A81A9467588F" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <storage id="VM2-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Disk1" summary="Main Disk" size="2000000000" status="offline"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM2</link> </storage> <storage id="VM2-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD(" title="Disk2" summary="Transaction Disk" size="2000000000" status="degraded"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM2</link> </storage> <storage id="VM2-E9B6EA5D-AFCD-43a8-B100-B72A0B841CDA" title="Spare" summary="Spared for Failover" size="2000000000" status="online"> <link>http://www.cdmi-pilot.com/demo/CDMI-SPARE-VM2</link> </storage> </collection> <collection id="VM3-6D5FB012-1ED6-4ce2-A466-19E862DB795B}" title="My VM2" summary="A test Vitrual Machine 2"> <compute id="VM3-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Mains" summary="Main CPUs" cores="" architecture="" hostname=""></compute> <compute id="VM3-E9B6EA5D-BFCE-43a8-B100-B72A0B841CD8" title="Spare" summary="Spared for Failover" cores="2" architecture="x86" hostname="Wally"></compute> <network id="VM3-AC3F20FA-AB76-4fb2-AE31-A81A9467588C" allocation="dhcp"></network> <network id="VM3-AC3F20FB-AB76-4fb2-AE32-A81A9467588C" title="Public" summary="Public" address="" gateway="" allocation="auto"></network> <network id="VM3-AC3F20FC-AB76-4fb2-AE32-A81A9467588C" title="Mgt" summary="Mgt" vlan="22" label="Management Segment" address="172.31.1.10" gateway="172.31.1.1" allocation="manual"></network> <network id="VM3-AC3F20FD-AB76-4fb2-AE32-A81A9467588C" title="Heartbeat" summary="" vlan="12" label="Hearbeat Segment" allocation="dhcp"></network> <memory id="VM3-AC3F20FD-AB76-4fb2-AE31-A81A9467588D" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <memory id="VM3-AC3F20FD-AB76-4fb2-AE31-A81A9467588E" title="Shared" summary="System Memory for Shared" size="1000000"></memory> <memory id="VM3-AC3F20FD-AB76-4fb2-AE31-A81A9467588F" title="RamDisk" summary="System Memory for RamDisk" size="1000000"></memory> <storage id="VM3-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD8" title="Disk1" summary="Main Disk" size="2000000000" status="offline"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM3</link> </storage> <storage id="VM3-E9B6EA5D-AFCD-43a8-B100-B72A0B841CD9" title="Disk2" summary="Transaction Disk" size="2000000000" status="degraded"> <link>http://www.cdmi-pilot.com/demo/CDMI-DISK-2-VM3</link> </storage> <storage id="VM3-E9B6EA5D-AFCD-43a8-B100-B72A0B841CDA" title="Spare" summary="Spared for Failover" size="2000000000" status="online"> <link>http://www.cdmi-pilot.com/demo/CDMI-SPARE-VM3</link> </storage> </collection>

1 0

Cloud Computing Use Case White Paper – Asset management
by Drussell4881 05 Mar '10

05 Mar '10

Should Asset Management be part of the Service Level Agreement (SLA) discussion? Will Asset Management refer to existing standards ( HIPAA, SAS70), etc.) or will Asset Management redefine existing policies? Will SLAs be off the shelf or custom for each Cloud solution? What are your thoughts? We would like to hear your comments as part of the original post at http://su.pr/5OiUwk. Thanks Dave

1 0