[occi-wg] Anymore use cases which nede to be documented

Thijs Metsch Thijs.Metsch at Sun.COM
Thu Jul 30 08:59:42 CDT 2009


Hi Marcus,

Can you try again for some reasons many people on the wiki have not been
assigned the right roles/permissions. Might be an issue that 4 people
approved membership with a outdated interface *g*

-Thijs

On Thu, 2009-07-30 at 15:31 +0200, Marcus Hardt wrote:
> Quoting Thijs Metsch
> > Thanks...Are you member of the gridforge project? If so you should be
> > able to commit...
> 
> Well, yes I know; I'm a member of the project. The "svn co" command given 
> worked, but this commit failed:
> 
> [marcus at tuna:~/svn/occi/docs]$ svn ci --username marcus -m "Added Mutliple 
> Allocation use-case"
> svn: Commit failed (details follow):
> svn: Server sent unexpected return value (403 Forbidden) in response to 
> MKACTIVITY request for '/svn/repos/occi/!svn/act/9c1b5eea-2bbd-412d-
> b19e-6b7e2ac80bf5'
> 
> 
> I reproduced this, by check out into a different dir, using 
> 	svn checkout --username marcus http://forge.ogf.org/svn/repos/occi
> and committing again, using the above command (with and without --username 
> marcus).
> 
> What to do?
> 
> M.
> 
> > -Thijs
> >
> > On Thu, 2009-07-30 at 11:34 +0200, Marcus Hardt wrote:
> > > Hi, I tried to edit, but SVN didn't accpt my commit (403: Forbidden).
> > >
> > > Here's it as a patch.
> > > Index: occi-usecases.xml
> > > ===================================================================
> > > --- occi-usecases.xml   (revision 51)
> > > +++ occi-usecases.xml   (working copy)
> > > @@ -699,4 +699,30 @@
> > >        </listitem>
> > >      </itemizedlist>
> > >    </section>
> > > +  <section>
> > > +         <title>Multiple Allocation</title>
> > > +         <para>Allocate a whole cluster with one call.</para>
> > > +
> > > +          <bridgehead>Functional Requirements</bridgehead>
> > > +
> > > +         <itemizedlist>
> > > +                 <listitem>
> > > +                         <para>Definition of groups: There should be a
> > > way to define groups +                                 of computers. In
> > > the example of a cluster, there would be two +                          
> > >       groups: The Headnode and a couple of Workernodes.</para> +        
> > >         </listitem>
> > > +
> > > +                 <listitem>
> > > +                         <para>Information: For configuration of the
> > > members of the defined +                                 groups, there
> > > should be way (maybe a URL) to find out about +                         
> > >        all groups and their basic configurations. In the example, the + 
> > >                                Headnode would want to know IPs or
> > > Hostnames of all +                                 Workernodes. The
> > > workernodes will need to know this, as well +                           
> > >      _and_ they need to know, that the headnode is in a different +     
> > >                            group. </para>
> > > +                 </listitem>
> > > +
> > > +         </itemizedlist>
> > > +  </section>
> > > +
> > >  </article>
> > >
> > >
> > > Quoting Thijs Metsch
> > >
> > > > Hi,
> > > >
> > > > Thanks for the contribution! - You can add it to the document yourself
> > > > if you want , otherwise I'll do that later!
> > > >
> > > > Cheers,
> > > >
> > > > -Thijs
> > > >
> > > > On Thu, 2009-07-30 at 10:41 +0200, Marcus Hardt wrote:
> > > > > I've added the use case of allocating multiple machines. I've added
> > > > > it only to the wiki, not to any document and I wonder if this is
> > > > > enough.
> > > > >
> > > > > M.
> > > > >
> > > > > Quoting Michael Behrens
> > > > >
> > > > > > I' added a compute/task use case could that would also support the
> > > > > > installation of patches.  Let me know if that's okay.
> > > > > > Attached is a PDF of the content as well.  A main driver was to
> > > > > > also provide for applying patches and updates to the system.  I
> > > > > > think it makes some sense to be able to use the same interface for
> > > > > > that as well as tasks, etc.
> > > > > >
> > > > > > If it is not applicable at this time, it can be excluded, etc.
> > > > > >
> > > > > > Let me know how I can help with editing, etc.
> > > > > >
> > > > > > Thijs Metsch wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > Today I moved all the use cases we had in the wiki to the
> > > > > > > document:
> > > > > > >
> > > > > > > http://forge.ogf.org/sf/docman/do/downloadDocument/projects.occi
> > > > > > >-wg/ docm an.root.drafts/doc15732/2
> > > > > > >
> > > > > > > (Except the financial grid use case...)
> > > > > > >
> > > > > > > Those descriptions still need be refined in the wording and
> > > > > > > references to the sources need to be added - but this is just
> > > > > > > the start :-)
> > > > > > >
> > > > > > > The question is now: are there anymore use cases which need to
> > > > > > > be added? Any which need to be refined etc?
> > > > > > >
> > > > > > > Please reply until Tuesday next week...
> > > > > > >
> > > > > > > All the best,
> > > > > > >
> > > > > > > -Thijs
> 
> 
-- 
Thijs Metsch                        Tel: +49 (0)941 3075-122 (x60122)
http://blogs.sun.com/intheclouds
Software Engineer Grid Computing
Sun Microsystems GmbH
Dr.-Leo-Ritter-Str. 7               mailto:thijs.metsch at sun.com
D-93049 Regensburg                  http://www.sun.com




More information about the occi-wg mailing list