Reminder: Cloud Demo Call Today
What: Cloud Demo coordination planning When: Wednesdays: 8amPT/9amMT/11amET Where: Audio conference information: Toll Free: (866) 682-4770 International: +1 (408) 774-4073 Conference Code: 1212488 Security Code: 1212 (note new number going forward...) Agenda: Updated status of demo What work is complete? What can clients do so far? What work is still left to do? Google Group for Cloud Demo http://groups.google.com/group/cloud-demo
After today¹s discussion, Mark asked me to capture the sequence. Here is 1st Cut:
1. Client -> CDMI : Create container - create object. Metadata to include [type = export, Display Name, Canonical Name, Mount Point, Security Tokens] 2. CDMI -> creates container, object and prepares the export as mount point 3. Client -> OCCI : XML or JSON call with [Display Name, Canonical Name, Mount Point, Security Tokens] 4. OCCI Layer : Mounts the mount point and displays the [Display Name]
OCCI Layer can try this without CDMI just by stubbing the Client->OCCI call with XML/JSON. That way we can develop the pieces in parallel.
After this is working, we can try OCCI to CDMI direct route
Cheers <k/> P.S : As discussed today, we have many of these pieces working incl parts of OCCI, CDMI(Capability,Container,Object), the computer hardware infrastructure (at SNIA) and the Client code.
Thanks Krishna. I was thinking of how to convey the information that is not available through CDMI to the implementation of OCCI and was thinking of a special file system (not CDMI exported, but always available) that was exported from the CDMI system to the OCCI system. On this filesystem would be one or more files where CDMI puts the information needed by OCCI to do the mounts, etc. When the Client makes the call in 3), the OCCI implementation would re-query the file and get the information needed. i.e "write-only" by CDMI and "read-only" from OCCI. Thoughts? -- mark On 5/12/10 3:43 PM, Krishna Sankar wrote:
After today's discussion, Mark asked me to capture the sequence. Here is 1st Cut:
1. Client -> CDMI : Create container - create object. Metadata to include [type = export, Display Name, Canonical Name, Mount Point, Security Tokens] 2. CDMI -> creates container, object and prepares the export as mount point 3. Client -> OCCI : XML or JSON call with [Display Name, Canonical Name, Mount Point, Security Tokens] 4. OCCI Layer : Mounts the mount point and displays the [Display Name]
OCCI Layer can try this without CDMI just by stubbing the Client->OCCI call with XML/JSON. That way we can develop the pieces in parallel.
After this is working, we can try OCCI to CDMI direct route
Cheers <k/> P.S : As discussed today, we have many of these pieces working incl parts of OCCI, CDMI(Capability,Container,Object), the computer hardware infrastructure (at SNIA) and the Client code.
Good idea. OOB communication we should make it a JSON file which could have the CDMI metadata that way we have a standard vocabulary. If that is the case, why not it be the container metadata queried by a GET ? Gary, would JSON over HTTP from a well known URL work as communication mechanism ? Cheers <k/> On 5/12/10 Wed May 12, 10, "Mark Carlson" <mark.carlson@oracle.com> wrote:
Thanks Krishna.
I was thinking of how to convey the information that is not available through CDMI to the implementation of OCCI and was thinking of a special file system (not CDMI exported, but always available) that was exported from the CDMI system to the OCCI system. On this filesystem would be one or more files where CDMI puts the information needed by OCCI to do the mounts, etc. When the Client makes the call in 3), the OCCI implementation would re-query the file and get the information needed. i.e "write-only" by CDMI and "read-only" from OCCI.
Thoughts?
-- mark
On 5/12/10 3:43 PM, Krishna Sankar wrote:
Cloud Demo 1st Cut Choreography
After today¹s discussion, Mark asked me to capture the sequence. Here is 1st Cut:
1. Client -> CDMI : Create container - create object. Metadata to include [type = export, Display Name, Canonical Name, Mount Point, Security Tokens] 2. CDMI -> creates container, object and prepares the export as mount point 3. Client -> OCCI : XML or JSON call with [Display Name, Canonical Name, Mount Point, Security Tokens] 4. OCCI Layer : Mounts the mount point and displays the [Display Name] 5.
OCCI Layer can try this without CDMI just by stubbing the Client->OCCI call with XML/JSON. That way we can develop the pieces in parallel.
After this is working, we can try OCCI to CDMI direct route
Cheers <k/> P.S : As discussed today, we have many of these pieces working incl parts of OCCI, CDMI(Capability,Container,Object), the computer hardware infrastructure (at SNIA) and the Client code.
Thats way too complicated and gets in the way of too many things. The info should be passed to occi via the client. If the CDMI config changes, the client needs to update the occi server. -g On Wed, May 12, 2010 at 4:25 PM, Mark Carlson <mark.carlson@oracle.com>wrote:
Thanks Krishna.
I was thinking of how to convey the information that is not available through CDMI to the implementation of OCCI and was thinking of a special file system (not CDMI exported, but always available) that was exported from the CDMI system to the OCCI system. On this filesystem would be one or more files where CDMI puts the information needed by OCCI to do the mounts, etc. When the Client makes the call in 3), the OCCI implementation would re-query the file and get the information needed. i.e "write-only" by CDMI and "read-only" from OCCI.
Thoughts?
-- mark
On 5/12/10 3:43 PM, Krishna Sankar wrote:
After today’s discussion, Mark asked me to capture the sequence. Here is 1st Cut:
1. Client -> CDMI : Create container - create object. Metadata to include [type = export, Display Name, Canonical Name, Mount Point, Security Tokens] 2. CDMI -> creates container, object and prepares the export as mount point 3. Client -> OCCI : XML or JSON call with [Display Name, Canonical Name, Mount Point, Security Tokens] 4. OCCI Layer : Mounts the mount point and displays the [Display Name]
OCCI Layer can try this without CDMI just by stubbing the Client->OCCI call with XML/JSON. That way we can develop the pieces in parallel.
After this is working, we can try OCCI to CDMI direct route
Cheers <k/> P.S : As discussed today, we have many of these pieces working incl parts of OCCI, CDMI(Capability,Container,Object), the computer hardware infrastructure (at SNIA) and the Client code.
Krish, I notice that PathResource was modified. What changed in this file? Thanks Scott On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com> wrote:
Have checked in code which has one update – now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com> wrote:
Have checked in code which has one update – now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
Exception code ! Have checked in an update that works. Cheers <k/> On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com> wrote:
Have checked in code which has one update now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
That compiles. Thanks On Sun, May 16, 2010 at 10:31 AM, Krishna Sankar <ksankar42@gmail.com>wrote:
Exception code ! Have checked in an update that works. Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com> wrote:
Have checked in code which has one update – now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
Good. Let me know if you need any help. Am on-line working on CDMI MIME IETF RFC. Cheers <k/> On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote:
That compiles. Thanks
On Sun, May 16, 2010 at 10:31 AM, Krishna Sankar <ksankar42@gmail.com> wrote:
Exception code ! Have checked in an update that works. Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com <http://scottjaybaker@gmail.com> > wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com <http://ksankar42@gmail.com> > wrote:
Have checked in code which has one update now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
try this in your toJson: g.useDefaultPrettyPrinter(); On Sun, May 16, 2010 at 10:52 AM, Krishna Sankar <ksankar42@gmail.com>wrote:
Good. Let me know if you need any help. Am on-line working on CDMI MIME IETF RFC.
Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote:
That compiles. Thanks
On Sun, May 16, 2010 at 10:31 AM, Krishna Sankar <ksankar42@gmail.com> wrote:
Exception code ! Have checked in an update that works. Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com < http://scottjaybaker@gmail.com> > wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com < http://ksankar42@gmail.com> > wrote:
Have checked in code which has one update – now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
These object metadata files need to have a standard prefix ( let's use .cdmi_) so I can filter them out when listing Container Children ( they show up in directory listings ). On Sun, May 16, 2010 at 3:48 PM, Scott Baker <scottjaybaker@gmail.com>wrote:
try this in your toJson:
g.useDefaultPrettyPrinter();
On Sun, May 16, 2010 at 10:52 AM, Krishna Sankar <ksankar42@gmail.com>wrote:
Good. Let me know if you need any help. Am on-line working on CDMI MIME IETF RFC.
Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote:
That compiles. Thanks
On Sun, May 16, 2010 at 10:31 AM, Krishna Sankar <ksankar42@gmail.com> wrote:
Exception code ! Have checked in an update that works. Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com < http://scottjaybaker@gmail.com> > wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com < http://ksankar42@gmail.com> > wrote:
Have checked in code which has one update – now it creates a . file with the metadata associated with an object. The file name is .<obj file>.
Cheers <k/>
These object metadata files need to have a standard prefix ( let's use .cdmi_) so I can filter them out when listing Container Children ( they show up in directory listings ).
On Sun, May 16, 2010 at 3:48 PM, Scott Baker <scottjaybaker@gmail.com> wrote:
try this in your toJson:
g.useDefaultPrettyPrinter();
On Sun, May 16, 2010 at 10:52 AM, Krishna Sankar <ksankar42@gmail.com> wrote:
Good. Let me know if you need any help. Am on-line working on CDMI MIME IETF RFC.
Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com <http://scottjaybaker@gmail.com> > wrote:
That compiles. Thanks
On Sun, May 16, 2010 at 10:31 AM, Krishna Sankar <ksankar42@gmail.com <http://ksankar42@gmail.com> > wrote:
Exception code ! Have checked in an update that works. Cheers <k/>
On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com <http://scottjaybaker@gmail.com> <http://scottjaybaker@gmail.com> > wrote:
Krish, Something has changed with your checkins and the build will not compile. Is there something you forgot to checkin? Scott
On Wed, May 12, 2010 at 7:08 PM, Krishna Sankar <ksankar42@gmail.com <http://ksankar42@gmail.com> <http://ksankar42@gmail.com> > wrote:
Have checked in code which has one update now it creates a . file with the
Done and committed ... On 5/16/10 Sun May 16, 10, "Scott Baker" <scottjaybaker@gmail.com> wrote: metadata associated with an object. The file name is .<obj file>. Cheers <k/>
FYI - Started coding the CDMI root level JavaFX parser...I'm able to connect and read the values from the CDMI server at this point and should be able to make more progress during the week. Mark - thanks for the assistance on Friday. I should be able to pass the object ID to OCCI. I'll need to test the OCCI interface later in the week. Laters.
participants (5)
-
gary mazzaferro -
Krishna Sankar -
Mark Carlson -
Michael Behrens -
Scott Baker