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

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: Cloud Demo call tomorrow
by Mark A. Carlson 03 Mar '10

03 Mar '10

Note: future notices will just go to cloud-demo(a)googlegroups.com What: Cloud Demo coordination planning When: Wednesdays: 8amPT/9amMT/11amET Where: 866-545-5227 code 6300276# Agenda: Status updates: SNIA, OCCI, others? Hosting location ideas? Staging location ideas? Venue planning for first demo - http://www.ogf.org/OGF29/ ? Timeline for first demo Google Group for Cloud Demo http://groups.google.com/group/cloud-demo

3 3

Re: [occi-wg] Demo Topology and conceptual architecture
by Krishna Sankar 24 Feb '10

24 Feb '10

Thanks. I think the logical flow is : Client invokes OCCI which in turn invokes CDMI which in turn invokes the storage layer. The client interface definitely is OCCI and we could do optimization so that the CDMI layer is transparently embedded. Updating existing VM with more storage is a good use case. I will add that. Also will update the slides with a simple logical call flow ... based on the CDMI OCCI paper ... Cheers <k/> On Feb 20, 2010, at Sat Feb 20, 10, Michael Behrens wrote: > Reviewed the great slides.... > > I'll work with Gary on the interfaces that I'll code to for the JavaFX client that I'm working on. It will be simple at first, etc. > Also, assuming that same client would invoke CDMI, I'll also need to determine which interfaces to invoke to allocate storage. Actually, I'm a little confused as to whether or not the OCCI layer would invoke CDMI or if the client would do so directly - probably both. > > Use case clarification: Is the intent of the Consumer Storage to illustrate cloud to cloud data migration? > A third use-case might involve updating a cloud VM with additional new storage. > > > > Krishna wrote: >> All, >> As per today's discussion, Mark and I collaborated on a preliminary >> topology and demo architecture diagram. I have uploaded the file. >> Let us discuss and get to some concurrence via e-mail; that way next >> week we can firm up the topology and move on to infrastructure setup >> and software development. >> >> Cheers >> <k/> >> _______________________________________________ >> occi-wg mailing list >> occi-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/occi-wg >> >> >> > > > -- > Michael Behrens > R2AD, LLC > (571) 594-3008 (cell) > (703) 714-0442 (land) > >

3 5

today's minutes in text
by Hope Hines 24 Feb '10

24 Feb '10

All, Attached are today's meeting minutes in text. Hope Olocity Corporation 1767 Denver West BLVD Suite A Golden, CO 80401 WK: 719-359-8898 Cell: 719-330-4685 www.olocity.com <mailto:Kurt.Krems@Olocity.com> Hope.Hines(a)olocity.com logo_email

1 0

Meeting Minutes
by Hope Hines 24 Feb '10

24 Feb '10

All, Please find attached for your review today's meeting minutes. Hope Olocity Corporation 1767 Denver West BLVD Suite A Golden, CO 80401 WK: 719-359-8898 Cell: 719-330-4685 www.olocity.com <mailto:Kurt.Krems@Olocity.com> Hope.Hines(a)olocity.com logo_email

1 0

Demo call today
by Mark A. Carlson 24 Feb '10

24 Feb '10

You can join the webex at snia.webex.com, Cloud TWG password: cloud2010 Usual dialin number -- mark

2 1

connection to forge failed
by michele.orru＠cnaf.infn.it 24 Feb '10

24 Feb '10

Why there are such problems when trying to get the following http://forge.ogf.org/sf/go/doc15732 Error: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /sf/go/doc15732. Reason: Error reading from remote server Michele Orru INFN-CNAF ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

3 4

OCCI reference document
by gary mazzaferro 23 Feb '10

23 Feb '10

Hi, I've been working on the details of the occi reference document. The current specification is a little weak in some critical areas and need to be worked out. Challenges with server-side parsers have varying degrees of xhtml5 compatibility. I should have a few examples by the end of the week. Tomorrow and Wed. are travel days for me. If I can get the reference documents completed by wed. (tonight) I'll post them. I'm not sure if I can make the wed. call, I'll be in eastern time zone. If we could reschedule for Thursday, it would be great :) -gary

2 1

Fwd: Re: [Fwd: Simplified OCCI VM lifecycle diagram]
by Sam Johnston 22 Feb '10

22 Feb '10

Copying list... ---------- Forwarded message ---------- From: "Sam Johnston" <samj(a)samj.net> Date: 21 Feb 2010 22:09 Subject: Re: [occi-wg] [Fwd: Simplified OCCI VM lifecycle diagram] To: "Gary Mazz" <garymazzaferro(a)gmail.com> Gary, The problem with state diagrams is that if your implementation doesn't fit the mould then you can't use OCCI. For example, you can't stop a resource with rackspacecloud, only destroy it. Something like this is probably useful as an informative rather than normative reference. Sam > > On 21 Feb 2010 21:35, "Gary Mazz" <garymazzaferro(a)gmail.com> wrote: > > Hi, > > As per the week... _______________________________________________ occi-wg mailing list occi-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/occi-wg

4 5

[Fwd: Simplified OCCI VM lifecycle diagram]
by Gary Mazz 21 Feb '10

21 Feb '10

Hi, As per the weekly occi meeting last Wed, I'm resending the simplified occi lifecycle diagram. This was initially sent to the mailing list last september. -gary -------- Original Message -------- Subject: Simplified OCCI VM lifecycle diagram Date: Thu, 03 Sep 2009 08:27:54 -0600 From: Gary Mazz <garymazzaferro(a)gmail.com> To: occi-wg(a)ogf.org <occi-wg(a)ogf.org> Hi, I put together a simplified version of the OCCI life cycle (state) diagram. I'll be using this as an overview and for discussion purposes. I'll provide a description in a couple of days. -gary

1 0