[occi-wg] OCCI MC - State Machine Diagram

Thijs Metsch Thijs.Metsch at Sun.COM
Mon Apr 20 02:57:56 CDT 2009


Ah sorry, my fault - than it was only that the picture was not
updated...Was missing the entry-points :-)

-Thijs

On Mon, 2009-04-20 at 09:50 +0200, Sam Johnston wrote:
> On Mon, Apr 20, 2009 at 9:31 AM, Thijs Metsch <Thijs.Metsch at sun.com>
> wrote:
>         
>         Hi,
>         
>         Can you upload those files to the wiki?
> 
> Sure, they're already hanging off this page:
> 
> http://forge.ogf.org/sf/wiki/do/viewPage/projects.occi-wg/wiki/StateModel
> 
> Sam
>  
>         On Sun, 2009-04-19 at 13:10 +0200, Sam Johnston wrote:
>         > On Sun, Apr 19, 2009 at 12:16 PM, Ignacio Martin Llorente
>         > <llorente at dacya.ucm.es> wrote:
>         >
>         >         I am not sure what is the state of this discussion,
>         but I
>         >         would like to support the addition of ENTRY and EXIT
>         points to
>         >         the diagram.
>         >
>         > Done. Attached, along with OmniGraffle source.
>         >
>         >         Moreover, if we do not assume that the submitted VMs
>         have to
>         >         run immediately or not at all,  I would like to
>         suggest that
>         >         we need a "Pending" state in the diagram. The new
>         submitted
>         >         VMs remain in this state until there are resources
>         available.
>         >         That could be the "DEFINED" state or the DMTF
>         "INITIAL" state.
>         >
>         > "Pending" is ambiguous. "Resuming" is pending, so is
>         "suspending".
>         > There's various takes on "defined" and "initial" too... for
>         example if
>         > you were to implement something like the Q-Layer^WSun Cloud
>         API web
>         > interface on top of OCCI then you would likely start by
>         creating and
>         > linking a bunch of objects, none of which would be useful
>         until
>         > associated with actual resources - it would be like a
>         shell/skeleton.
>         >
>         > Perhaps this is something worth taking into consideration,
>         though as
>         > I'd rather not impose too much on implementors it probably
>         belongs in
>         > the registry.
>         >
>         > Sam
>         >
>         
>         
>  
>         > _______________________________________________
>         > occi-wg mailing list
>         > occi-wg at ogf.org
>         > http://www.ogf.org/mailman/listinfo/occi-wg
>         --
>         
>         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
>         
>         
>         _______________________________________________
>         occi-wg mailing list
>         occi-wg at ogf.org
>         http://www.ogf.org/mailman/listinfo/occi-wg
>         
> 
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/occi-wg
-- 
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