Re: [occi-wg] A new paper related to OCCI Platfom
Congrats! Andy Edmonds Æ Senior Researcher, ICCLab Institute of Information Technology Zürich University of Applied Sciences blog.zhaw.ch/icclab, keybase.io/dizz On 1 February 2018 at 14:04, Philippe Merle <philippe.merle@inria.fr> wrote:
Hi,
We are pleased to announce that our recent paper "Model-Driven Configuration Management of Cloud Applications with OCCI" was accepted at the 8th International Conference on Cloud Computing and Services Science (CLOSER'18).
Title: Model-Driven Configuration Management of Cloud Applications with OCCI
Abstract: To tackle the cloud-provider lock-in, the Open Grid Forum (OGF) is developing the Open Cloud Computing Interface (OCCI), a standardized interface for managing any kind of cloud resources. Besides the OCCI Core model, which defines the basic modeling elements for cloud resources, the OGF also defines extensions that reflect the requirements of different cloud service levels, such as IaaS and PaaS. However, so far the OCCI PaaS extension is very coarse grained and lacks of supporting use cases and implementations. Especially, it does not define how the components of the application itself can be managed. In this paper, we present a model-driven framework that extends the OCCI PaaS extension and is able to use different configuration management tools to manage the whole lifecycle of cloud applications. We demonstrate the feasibility of the approach by presenting four different use cases and prototypical implementations for three different configuration management tools.
The camera-ready version is available at https://hal.inria.fr/hal-01678945/document.
For more information, have a look at https://hal.inria.fr/hal-01678945.
Best regards Philippe Merle
-- Philippe Merle Inria researcher http://chercheurs.lille.inria.fr/~pmerle/
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Hi Philippe et al., I have spent some time looking over the document that you linked below. I agree with Andy that congratulations are in order. In this paper, you have identified and proposed workable solutions for several areas in which the OCCI Platform model as currently published was just a starting point, and have gone further by implementing and making available tools through the OCCIware project. From an OGF and community point of view, the natural question would seem to be whether some of these concepts can be formalized through a revision or new derivative document to replace the existing one (https://www.ogf.org/documents/GFD.227.pdf) that can serve as a basis for further enhancing the OCCI specification set. There could be other documents in he set that need updating or revision based on practical experience. A related question would be whether meetings of the OCCI-WG, virtual or real, would be useful to explore your work and these concepts in more detail, as well as other practical results from the OCCIware project and other implementations. I note in passing that all of the current OCCi v1.2 documents are still in a proposed recommendation (P-REC) state, and that to advance from this to the full recommendation (REC) state, what is needed is agreement from within the working group that this is desired, plus at least two implementations for each specification and passage of an amount of time that is now smaller than the age of these documents. It would be a service to the community to clean up any current problems within this generation of specifications and get them to advance to the stage of full RECs. (Note that this does not preclude a future version that goes beyond the current state.) Alan On Feb 1, 2018, at 7:16 AM, Andy Edmonds <edmo@zhaw.ch<mailto:edmo@zhaw.ch>> wrote: Congrats! Andy Edmonds Æ Senior Researcher, ICCLab Institute of Information Technology Zürich University of Applied Sciences blog.zhaw.ch/icclab<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.zhaw.ch%2Ficclab&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=jwgh7dTuyfVTuJEPgIG2VeZvWR1pHTT%2FSQKNuKdl1%2BM%3D&reserved=0>, keybase.io/dizz<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkeybase.io%2Fdizz&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=EMxxWJv3EaHklH7pQLBtmA4GwHugOV95poFcbNvluHk%3D&reserved=0> On 1 February 2018 at 14:04, Philippe Merle <philippe.merle@inria.fr<mailto:philippe.merle@inria.fr>> wrote: Hi, We are pleased to announce that our recent paper "Model-Driven Configuration Management of Cloud Applications with OCCI" was accepted at the 8th International Conference on Cloud Computing and Services Science (CLOSER'18). Title: Model-Driven Configuration Management of Cloud Applications with OCCI Abstract: To tackle the cloud-provider lock-in, the Open Grid Forum (OGF) is developing the Open Cloud Computing Interface (OCCI), a standardized interface for managing any kind of cloud resources. Besides the OCCI Core model, which defines the basic modeling elements for cloud resources, the OGF also defines extensions that reflect the requirements of different cloud service levels, such as IaaS and PaaS. However, so far the OCCI PaaS extension is very coarse grained and lacks of supporting use cases and implementations. Especially, it does not define how the components of the application itself can be managed. In this paper, we present a model-driven framework that extends the OCCI PaaS extension and is able to use different configuration management tools to manage the whole lifecycle of cloud applications. We demonstrate the feasibility of the approach by presenting four different use cases and prototypical implementations for three different configuration management tools. The camera-ready version is available at https://hal.inria.fr/hal-01678945/document<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhal.inria.fr%2Fhal-01678945%2Fdocument&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=cNuUYMBMVmjC4tdLE%2BJMdRSS%2BKe4616edbcsjw97PdM%3D&reserved=0>. For more information, have a look at https://hal.inria.fr/hal-01678945<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhal.inria.fr%2Fhal-01678945&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=po3rU2LTOzDD2bYzMAtKdnM0CDFMFU891neziGh8X8Q%3D&reserved=0>. Best regards Philippe Merle -- Philippe Merle Inria researcher http://chercheurs.lille.inria.fr/~pmerle/<https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fchercheurs.lille.inria.fr%2F~pmerle%2F&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=fKTmBRgqipS7%2BboZtdvKeJBGzLb98pWKhCegAkOA%2F8I%3D&reserved=0> _______________________________________________ occi-wg mailing list occi-wg@ogf.org<mailto:occi-wg@ogf.org> https://www.ogf.org/mailman/listinfo/occi-wg<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Focci-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=9GGF5rJVfBdkTKGRgZZ4d1iT9kCdvYHlMA5tRHxF4s4%3D&reserved=0> _______________________________________________ occi-wg mailing list occi-wg@ogf.org<mailto:occi-wg@ogf.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Focci-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=9GGF5rJVfBdkTKGRgZZ4d1iT9kCdvYHlMA5tRHxF4s4%3D&reserved=0
Le 01/02/2018 à 20:01, Sill, Alan wrote:
From an OGF and community point of view, the natural question would seem to be whether some of these concepts can be formalized through a revision or new derivative document to replace the existing one (https://www.ogf.org/documents/GFD.227.pdf) that can serve as a basis for further enhancing the OCCI specification set. There could be other documents in he set that need updating or revision based on practical experience.
Hi, We already proposed such an evolution in 2017 : see below, mail exchange btw Boris Parak, Thijs Metsch, Philippe Merle and I, initiated on the occi-wg mailing list. The return was positive... then nothing happened, so we gave up proposing evolutions (because we were somewhat convinced the current release of OCCI Platform would be the last one !) Attached, the latest OCCI Platform we produced (and below, the full mail exchange). Regards, Pierre-Yves Gibello - Linagora -------- Message transféré -------- Sujet : Re: [occiware] [occi-wg] Evolution proposal in "OCCI Platform" specification Date : Tue, 4 Apr 2017 12:27:10 +0200 De : Philippe Merle <philippe.merle@inria.fr> Répondre à : Philippe Merle <philippe.merle@inria.fr> Organisation : Inria Pour : occi-wg@ogf.org, occiware@ow2.org <occiware@ow2.org> Hi Pierre-Yves, Add an appendix section named "Change Log" at the end of the OCCI Plaform document. You could take inspiration from the "Change Log" section at the end of the OCCI Core document. A+ Philippe Le 04/04/2017 à 10:26, Pierre-Yves Gibello a écrit :
Hi,
What do you mean by "errata" ? There is no mistake in any released doc, my document is an evolution proposal.
Regards, Pierre-Yves Gibello - OCCIWare project
Le 31/03/2017 à 17:10, Metsch, Thijs a écrit :
Hi,
Thanks for the contribution - looks good. Can you maybe write a little Errata text and include that in the doc as well?
Cheers,
-Thijs
-----Original Message----- From: occi-wg [mailto:occi-wg-bounces@ogf.org] On Behalf Of Pierre-Yves Gibello Sent: Monday, March 27, 2017 10:58 AM To: Boris Parak <xparak@mail.muni.cz>; occi-wg@ogf.org Cc: occiware@ow2.org Subject: Re: [occi-wg] Evolution proposal in "OCCI Platform" specification
Thanks a lot... it was a mistake ! Fixed now, in the attached version (and in the git repo, of course).
The target state for "configure" was "inactive", there is no "configured" state in the figure.
Thanks for reading so carefully, the mistake came through our peer review without being noticed !
Regards, Pierre-Yves Gibello - OCCIWare team
P.S. Please let us know of the process & schedule to integrate this in the next spec release, if any.
Le 25/03/2017 à 14:44, Boris Parak a écrit :
Dear Pierre-Yves Gibello,
AFAIK, this looks like a reasonable addition.
I noticed that you are using 'configured' as a target state in action tables. However, there is no such state declared in state tables or shown in state diagrams.
Regards, Boris Parak -- CESNET
On Fri, Mar 24, 2017 at 3:22 PM, Pierre-Yves Gibello <pygibello@linagora.com> wrote:
Dear OCCI team,
We at OCCIWare project (www.occiware.org) are using OCCI Platform to model and deploy/configure software applications in the cloud.
But we quickly came to the conclusion that the current "OCCI Platform" spec is too uncomplete, as we needed to extend it to cover some basic issues.
For instance, an application component (eg. a software component, like a database or an app server) will first be installed (we call that "deployed"), then configured, prior to managing its lifecycle (start/stop and so on).
OCCI Platform assumes the component is already installed and configured (it provides only "inactive" and "active" states with "start" and "shttps://github.com/gibello/occi-wgtop" actions), or that install/configure/start is a single action (which is not true).
What we propose here is adding 2 states ("undeployed" and "deployed") and 3 actions ("deploy", "configure" and "undeploy") in both the component and the application states (all modifications are located in chapters 3.1 and 3.2 of the OCCI Platform spec: figures 2 and 3 + tables 3 and 5). Of course, the new states and transitions can be considered optional by implementers, which would make things as simple as before for minimal use cases.
Attached, the new OCCI Platform spec we propose.
We cloned the OCCI specifications repository (redmine) on github, and the commits can be found here : https://github.com/gibello/occi-wg (simply "git clone" the repo, then "make" to build the specs).
Let us know what you think, and if relevant, which process to update the next version of "OCCI platform" specification.
Regards, Pierre-Yves Gibello - OCCIWare project
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
-- Philippe Merle Inria researcher http://chercheurs.lille.inria.fr/~pmerle/
Hi Alan et al., Le 01/02/2018 à 20:01, Sill, Alan a écrit :
Hi Philippe et al.,
I have spent some time looking over the document that you linked below. I agree with Andy that congratulations are in order.
Thank you.
In this paper, you have identified and proposed workable solutions for several areas in which the OCCI Platform model as currently published was just a starting point, and have gone further by implementing and making available tools through the OCCIware project.
Yes we do.
From an OGF and community point of view, the natural question would seem to be whether some of these concepts can be formalized through a revision or new derivative document to replace the existing one (https://www.ogf.org/documents/GFD.227.pdf) that can serve as a basis for further enhancing the OCCI specification set. There could be other documents in he set that need updating or revision based on practical experience.
I propose to revise the OCCI Platform document in order to integrate the notion of PlacementLink (or any other name), the extended state machine we proposed in our ModMaCAO paper and Pierre-Yves Gibello's revision proposal. I could do this job only from March. What do you think about this proposal?
A related question would be whether meetings of the OCCI-WG, virtual or real, would be useful to explore your work and these concepts in more detail, as well as other practical results from the OCCIware project and other implementations.
Definitely yes we should organize virtual or physical meetings to share results and prepare OCCI 1.3 or 2.0.
I note in passing that all of the current OCCi v1.2 documents are still in a proposed recommendation (P-REC) state, and that to advance from this to the full recommendation (REC) state, what is needed is agreement from within the working group that this is desired, plus at least two implementations for each specification and passage of an amount of time that is now smaller than the age of these documents. It would be a service to the community to clean up any current problems within this generation of specifications and get them to advance to the stage of full RECs. (Note that this does not preclude a future version that goes beyond the current state.)
Alan
A+ Philippe
On Feb 1, 2018, at 7:16 AM, Andy Edmonds <edmo@zhaw.ch <mailto:edmo@zhaw.ch>> wrote:
Congrats!
Andy Edmonds Æ Senior Researcher, ICCLab Institute of Information Technology Zürich University of Applied Sciences blog.zhaw.ch/icclab <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fblog.zhaw.ch%2Ficclab&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=jwgh7dTuyfVTuJEPgIG2VeZvWR1pHTT%2FSQKNuKdl1%2BM%3D&reserved=0>, keybase.io/dizz <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkeybase.io%2Fdizz&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=EMxxWJv3EaHklH7pQLBtmA4GwHugOV95poFcbNvluHk%3D&reserved=0>
On 1 February 2018 at 14:04, Philippe Merle <philippe.merle@inria.fr <mailto:philippe.merle@inria.fr>> wrote:
Hi,
We are pleased to announce that our recent paper "Model-Driven Configuration Management of Cloud Applications with OCCI" was accepted at the 8th International Conference on Cloud Computing and Services Science (CLOSER'18).
Title: Model-Driven Configuration Management of Cloud Applications with OCCI
Abstract: To tackle the cloud-provider lock-in, the Open Grid Forum (OGF) is developing the Open Cloud Computing Interface (OCCI), a standardized interface for managing any kind of cloud resources. Besides the OCCI Core model, which defines the basic modeling elements for cloud resources, the OGF also defines extensions that reflect the requirements of different cloud service levels, such as IaaS and PaaS. However, so far the OCCI PaaS extension is very coarse grained and lacks of supporting use cases and implementations. Especially, it does not define how the components of the application itself can be managed. In this paper, we present a model-driven framework that extends the OCCI PaaS extension and is able to use different configuration management tools to manage the whole lifecycle of cloud applications. We demonstrate the feasibility of the approach by presenting four different use cases and prototypical implementations for three different configuration management tools.
The camera-ready version is available at https://hal.inria.fr/hal-01678945/document <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhal.inria.fr%2Fhal-01678945%2Fdocument&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=cNuUYMBMVmjC4tdLE%2BJMdRSS%2BKe4616edbcsjw97PdM%3D&reserved=0>.
For more information, have a look at https://hal.inria.fr/hal-01678945 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhal.inria.fr%2Fhal-01678945&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=po3rU2LTOzDD2bYzMAtKdnM0CDFMFU891neziGh8X8Q%3D&reserved=0>.
Best regards Philippe Merle
-- Philippe Merle Inria researcher http://chercheurs.lille.inria.fr/~pmerle/ <https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fchercheurs.lille.inria.fr%2F%7Epmerle%2F&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=fKTmBRgqipS7%2BboZtdvKeJBGzLb98pWKhCegAkOA%2F8I%3D&reserved=0>
_______________________________________________ occi-wg mailing list occi-wg@ogf.org <mailto:occi-wg@ogf.org> https://www.ogf.org/mailman/listinfo/occi-wg <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Focci-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=9GGF5rJVfBdkTKGRgZZ4d1iT9kCdvYHlMA5tRHxF4s4%3D&reserved=0>
_______________________________________________ occi-wg mailing list occi-wg@ogf.org <mailto:occi-wg@ogf.org> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ogf.org%2Fmailman%2Flistinfo%2Focci-wg&data=02%7C01%7CAlan.Sill%40ttu.edu%7C5508d219f8b04fd1207808d5697623be%7C178a51bf8b2049ffb65556245d5c173c%7C0%7C0%7C636530878509262243&sdata=9GGF5rJVfBdkTKGRgZZ4d1iT9kCdvYHlMA5tRHxF4s4%3D&reserved=0
-- Philippe Merle Inria researcher http://chercheurs.lille.inria.fr/~pmerle/
participants (4)
-
Andy Edmonds -
Philippe Merle -
Pierre-Yves Gibello -
Sill, Alan