Message Queue on OCCI
Dear all, we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components. If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI. It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like. Cheers, Maik ================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Maik, Do you have an API you can show us? That is the best way to get started alexis On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
There are a few initiatives starting up focusing on PAAS. Messaging is included in those works... It may be prudent to align with existing standards and works. cheers, gary On 7/31/2012 3:44 AM, Alexis Richardson wrote:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Hi Alexis, Thanks for your interest. I have attached a short summary where i explain what we will to. Cheers, Maik ================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Thanks Maik. What would be examples of "OCCI forward the actions from the client to the message queue"? alexis On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Hi, at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client. Cheers, Maik ================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
OK. It might be worth considering other examples, eg Amazon SQS/SNS... On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Hi, after few weeks of discussion we have an idea how we can combined our services, message system and occi. The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats. Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services. After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP. In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms). Cheers Maik Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote:
Dear all,
we currently think about expanding OCCI so it supports a message queue between client and service provider. Our project contains simulation services in the cloud. For this we need a communication between client and simulation services. In one case it will be used to transmit control commands and receive status changes. Inside our project, we use RabbitMQ for messaging between client and simulation services, and among the different simulation service components.
If this message queue would be part of an OCCI implementation, we could realize our management tasks for cloud simulation services via OCCI.
It would be very nice to hear if somebody has already thought about this or could help collect ideas on how such an OCCI Extension could look like.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Maik, I like this idea, but why not go further and wrap the AMQP messages into a general HTTP format? alexis On Tue, Aug 28, 2012 at 4:37 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
after few weeks of discussion we have an idea how we can combined our services, message system and occi.
The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats.
Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services.
After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP.
In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms).
Cheers Maik
Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Maik,
Do you have an API you can show us? That is the best way to get started
alexis
On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote: > Dear all, > > we currently think about expanding OCCI so it supports a message >queue > between client and service provider. > Our project contains simulation services in the cloud. For this we >need >a > communication between > client and simulation services. In one case it will be used to >transmit > control commands > and receive status changes. Inside our project, we use RabbitMQ for > messaging between > client and simulation services, and among the different simulation >service > components. > > If this message queue would be part of an OCCI implementation, we >could > realize our management tasks for > cloud simulation services via OCCI. > > It would be very nice to hear if somebody has already thought about >this or > could help collect ideas on > how such an OCCI Extension could look like. > > Cheers, > Maik > > > ================================================================== > GWDG - Gesellschaft für wissenschaftliche > Datenverarbeitung mbH Göttingen > Am Fassberg 11, 37077 Göttingen > Geschäftsführer: Prof. Dr. Ramin Yahyapour > Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger > Sitz der Gesellschaft: Göttingen > Registergericht: Göttingen > Handelsregister-Nr. B 598 > WWW: www.gwdg.de > ------------------------------------------------------------------ > Fon: 0551 39-20364 > Fax: 0551 201-2150 > AG (e)Science > E-Mail: maik.srba@gwdg.de > > > _______________________________________________ > occi-wg mailing list > occi-wg@ogf.org > https://www.ogf.org/mailman/listinfo/occi-wg >
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
There is no need to wrap AMPQ in HTTP. The only thing needed for occi is the mixin(s) representing the service entry points. -gary On 8/29/2012 3:50 AM, Alexis Richardson wrote:
Maik,
I like this idea, but why not go further and wrap the AMQP messages into a general HTTP format?
alexis
On Tue, Aug 28, 2012 at 4:37 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
after few weeks of discussion we have an idea how we can combined our services, message system and occi.
The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats.
Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services.
After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP.
In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms).
Cheers Maik
Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi Alexis,
Thanks for your interest. I have attached a short summary where i explain what we will to.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 31.07.12 11:44 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
> Maik, > > Do you have an API you can show us? That is the best way to get > started > > alexis > > On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> wrote: >> Dear all, >> >> we currently think about expanding OCCI so it supports a message >> queue >> between client and service provider. >> Our project contains simulation services in the cloud. For this we >> need >> a >> communication between >> client and simulation services. In one case it will be used to >> transmit >> control commands >> and receive status changes. Inside our project, we use RabbitMQ for >> messaging between >> client and simulation services, and among the different simulation >> service >> components. >> >> If this message queue would be part of an OCCI implementation, we >> could >> realize our management tasks for >> cloud simulation services via OCCI. >> >> It would be very nice to hear if somebody has already thought about >> this or >> could help collect ideas on >> how such an OCCI Extension could look like. >> >> Cheers, >> Maik >> >> >> ================================================================== >> GWDG - Gesellschaft für wissenschaftliche >> Datenverarbeitung mbH Göttingen >> Am Fassberg 11, 37077 Göttingen >> Geschäftsführer: Prof. Dr. Ramin Yahyapour >> Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger >> Sitz der Gesellschaft: Göttingen >> Registergericht: Göttingen >> Handelsregister-Nr. B 598 >> WWW: www.gwdg.de >> ------------------------------------------------------------------ >> Fon: 0551 39-20364 >> Fax: 0551 201-2150 >> AG (e)Science >> E-Mail: maik.srba@gwdg.de >> >> >> _______________________________________________ >> occi-wg mailing list >> occi-wg@ogf.org >> https://www.ogf.org/mailman/listinfo/occi-wg >>
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
Sure. But I think OCCI users will also want an all HTTP option. Just a thought.. On Wed, Aug 29, 2012 at 3:48 PM, Gary Mazz <garymazzaferro@gmail.com> wrote:
There is no need to wrap AMPQ in HTTP. The only thing needed for occi is the mixin(s) representing the service entry points.
-gary
On 8/29/2012 3:50 AM, Alexis Richardson wrote:
Maik,
I like this idea, but why not go further and wrap the AMQP messages into a general HTTP format?
alexis
On Tue, Aug 28, 2012 at 4:37 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
after few weeks of discussion we have an idea how we can combined our services, message system and occi.
The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats.
Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services.
After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP.
In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms).
Cheers Maik
Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote: > > Hi Alexis, > > Thanks for your interest. I have attached a short summary where i > explain > what we will to. > > Cheers, > Maik > > > ================================================================== > GWDG - Gesellschaft für wissenschaftliche > Datenverarbeitung mbH Göttingen > Am Fassberg 11, 37077 Göttingen > Geschäftsführer: Prof. Dr. Ramin Yahyapour > Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger > Sitz der Gesellschaft: Göttingen > Registergericht: Göttingen > Handelsregister-Nr. B 598 > WWW: www.gwdg.de > ------------------------------------------------------------------ > Fon: 0551 39-20364 > Fax: 0551 201-2150 > AG (e)Science > E-Mail: maik.srba@gwdg.de > > > > > > > > Am 31.07.12 11:44 schrieb "Alexis Richardson" unter > <alexis@rabbitmq.com>: > >> Maik, >> >> Do you have an API you can show us? That is the best way to get >> started >> >> alexis >> >> On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> >> wrote: >>> >>> Dear all, >>> >>> we currently think about expanding OCCI so it supports a message >>> queue >>> between client and service provider. >>> Our project contains simulation services in the cloud. For this we >>> need >>> a >>> communication between >>> client and simulation services. In one case it will be used to >>> transmit >>> control commands >>> and receive status changes. Inside our project, we use RabbitMQ for >>> messaging between >>> client and simulation services, and among the different simulation >>> service >>> components. >>> >>> If this message queue would be part of an OCCI implementation, we >>> could >>> realize our management tasks for >>> cloud simulation services via OCCI. >>> >>> It would be very nice to hear if somebody has already thought about >>> this or >>> could help collect ideas on >>> how such an OCCI Extension could look like. >>> >>> Cheers, >>> Maik >>> >>> >>> ================================================================== >>> GWDG - Gesellschaft für wissenschaftliche >>> Datenverarbeitung mbH Göttingen >>> Am Fassberg 11, 37077 Göttingen >>> Geschäftsführer: Prof. Dr. Ramin Yahyapour >>> Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger >>> Sitz der Gesellschaft: Göttingen >>> Registergericht: Göttingen >>> Handelsregister-Nr. B 598 >>> WWW: www.gwdg.de >>> ------------------------------------------------------------------ >>> Fon: 0551 39-20364 >>> Fax: 0551 201-2150 >>> AG (e)Science >>> E-Mail: maik.srba@gwdg.de >>> >>> >>> _______________________________________________ >>> occi-wg mailing list >>> occi-wg@ogf.org >>> https://www.ogf.org/mailman/listinfo/occi-wg >>> > > _______________________________________________ > occi-wg mailing list > occi-wg@ogf.org > https://www.ogf.org/mailman/listinfo/occi-wg >
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
+1 On Wed, Aug 29, 2012 at 4:48 PM, Gary Mazz <garymazzaferro@gmail.com> wrote:
There is no need to wrap AMPQ in HTTP. The only thing needed for occi is the mixin(s) representing the service entry points.
-gary
On 8/29/2012 3:50 AM, Alexis Richardson wrote:
Maik,
I like this idea, but why not go further and wrap the AMQP messages into a general HTTP format?
alexis
On Tue, Aug 28, 2012 at 4:37 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
after few weeks of discussion we have an idea how we can combined our services, message system and occi.
The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats.
Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services.
After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP.
In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms).
Cheers Maik
Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
Thanks Maik.
What would be examples of "OCCI forward the actions from the client to the message queue"?
alexis
On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote: > > Hi Alexis, > > Thanks for your interest. I have attached a short summary where i > explain > what we will to. > > Cheers, > Maik > > > ================================================================== > GWDG - Gesellschaft für wissenschaftliche > Datenverarbeitung mbH Göttingen > Am Fassberg 11, 37077 Göttingen > Geschäftsführer: Prof. Dr. Ramin Yahyapour > Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger > Sitz der Gesellschaft: Göttingen > Registergericht: Göttingen > Handelsregister-Nr. B 598 > WWW: www.gwdg.de > ------------------------------------------------------------------ > Fon: 0551 39-20364 > Fax: 0551 201-2150 > AG (e)Science > E-Mail: maik.srba@gwdg.de > > > > > > > > Am 31.07.12 11:44 schrieb "Alexis Richardson" unter > <alexis@rabbitmq.com>: > >> Maik, >> >> Do you have an API you can show us? That is the best way to get >> started >> >> alexis >> >> On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> >> wrote: >>> >>> Dear all, >>> >>> we currently think about expanding OCCI so it supports a message >>> queue >>> between client and service provider. >>> Our project contains simulation services in the cloud. For this we >>> need >>> a >>> communication between >>> client and simulation services. In one case it will be used to >>> transmit >>> control commands >>> and receive status changes. Inside our project, we use RabbitMQ for >>> messaging between >>> client and simulation services, and among the different simulation >>> service >>> components. >>> >>> If this message queue would be part of an OCCI implementation, we >>> could >>> realize our management tasks for >>> cloud simulation services via OCCI. >>> >>> It would be very nice to hear if somebody has already thought about >>> this or >>> could help collect ideas on >>> how such an OCCI Extension could look like. >>> >>> Cheers, >>> Maik >>> >>> >>> ================================================================== >>> GWDG - Gesellschaft für wissenschaftliche >>> Datenverarbeitung mbH Göttingen >>> Am Fassberg 11, 37077 Göttingen >>> Geschäftsführer: Prof. Dr. Ramin Yahyapour >>> Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger >>> Sitz der Gesellschaft: Göttingen >>> Registergericht: Göttingen >>> Handelsregister-Nr. B 598 >>> WWW: www.gwdg.de >>> ------------------------------------------------------------------ >>> Fon: 0551 39-20364 >>> Fax: 0551 201-2150 >>> AG (e)Science >>> E-Mail: maik.srba@gwdg.de >>> >>> >>> _______________________________________________ >>> occi-wg mailing list >>> occi-wg@ogf.org >>> https://www.ogf.org/mailman/listinfo/occi-wg >>> > > _______________________________________________ > occi-wg mailing list > occi-wg@ogf.org > https://www.ogf.org/mailman/listinfo/occi-wg >
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
_______________________________________________ occi-wg mailing list occi-wg@ogf.org https://www.ogf.org/mailman/listinfo/occi-wg
-- Nothing is ever easy...
I really like the use-case here - as it illustrates a multi-protocol scenario using OCCI. Andre Merzky wrote:
+1
On Wed, Aug 29, 2012 at 4:48 PM, Gary Mazz <garymazzaferro@gmail.com> wrote:
There is no need to wrap AMPQ in HTTP. The only thing needed for occi is the mixin(s) representing the service entry points.
-gary
On 8/29/2012 3:50 AM, Alexis Richardson wrote:
Maik,
I like this idea, but why not go further and wrap the AMQP messages into a general HTTP format?
alexis
On Tue, Aug 28, 2012 at 4:37 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
after few weeks of discussion we have an idea how we can combined our services, message system and occi.
The idea is, that we extend the OCCI interface with AMQP besides HTTP. Then we can connect OCCI with an message bus. Table 1 shows what i mean with extension. The different interfaces can combined with different OCCI Dataformats.
Picture 2 shows connection of OCCI, Service and Message Bus. Here we can exchange AMQP/OCCI messages between the services.
After i read the new OCCI JSON rendering document writen by Florian Feldhaus and Ralf Nyren, i see the new changes about Actions. Actions are now defined in action_category and instantiated in action. Thats a good thing because now we can uses this action instance as messages and send them via AMQP.
In combination with OCCI Mixins we can create a service specific eventsystem were we can exchange messages between different services. In this case the service provider can characterize there own service interfaces as OCCI Mixin. He delivers the characterization with the service to the platform. Both service and client use OCCI. The service client can discover or use the interface and the service adapter interprets the OCCI messages or send messages. So we can simple combine provided services over OCCI (theoretical distributed over several platforms).
Cheers Maik
Am 01.08.12 15:05 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
OK.
It might be worth considering other examples, eg Amazon SQS/SNS...
On Wed, Aug 1, 2012 at 1:36 PM, Srba, Maik <maik.srba@gwdg.de> wrote:
Hi,
at the moment i see 4 actions here. One is "startlisten" to say OCCI that now the client will listen to the message queue and "stoplisten" to stop listening. One other is "send" to request a message over OCCI to the message queue that can listen by the application and at last i see "receive" to ask OCCI if there are any new messages from the queue for the client.
Cheers, Maik
================================================================== GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Fassberg 11, 37077 Göttingen Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen Handelsregister-Nr. B 598 WWW: www.gwdg.de ------------------------------------------------------------------ Fon: 0551 39-20364 Fax: 0551 201-2150 AG (e)Science E-Mail: maik.srba@gwdg.de
Am 01.08.12 13:48 schrieb "Alexis Richardson" unter <alexis@rabbitmq.com>:
> Thanks Maik. > > What would be examples of "OCCI forward the actions from the > client to > the message queue"? > > alexis > > On Wed, Aug 1, 2012 at 12:40 PM, Srba, Maik <maik.srba@gwdg.de> wrote: >> Hi Alexis, >> >> Thanks for your interest. I have attached a short summary where i >> explain >> what we will to. >> >> Cheers, >> Maik >> >> >> ================================================================== >> GWDG - Gesellschaft für wissenschaftliche >> Datenverarbeitung mbH Göttingen >> Am Fassberg 11, 37077 Göttingen >> Geschäftsführer: Prof. Dr. Ramin Yahyapour >> Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger >> Sitz der Gesellschaft: Göttingen >> Registergericht: Göttingen >> Handelsregister-Nr. B 598 >> WWW: www.gwdg.de >> ------------------------------------------------------------------ >> Fon: 0551 39-20364 >> Fax: 0551 201-2150 >> AG (e)Science >> E-Mail: maik.srba@gwdg.de >> >> >> >> >> >> >> >> Am 31.07.12 11:44 schrieb "Alexis Richardson" unter >> <alexis@rabbitmq.com>: >> >>> Maik, >>> >>> Do you have an API you can show us? That is the best way to get >>> started >>> >>> alexis >>> >>> On Mon, Jul 30, 2012 at 8:32 AM, Srba, Maik <maik.srba@gwdg.de> >>> wrote: >>>> Dear all, >>>> >>>> we currently think about expanding OCCI so it supports a message >>>> queue >>>> between client and service provider. >>>> Our project contains simulation services in the cloud. For this we >>>> need >>>> a >>>> communication between >>>> client and simulation services. In one case it will be used to >>>> transmit >>>> control commands >>>> and receive status changes. Inside our project, we use RabbitMQ for >>>> messaging between >>>> client and simulation services, and among the different simulation >>>> service >>>> components. >>>> >>>> If this message queue would be part of an OCCI implementation, we >>>> could >>>> realize our management tasks for >>>> cloud simulation services via OCCI. >>>> >>>> It would be very nice to hear if somebody has already thought about >>>> this or >>>> could help collect ideas on >>>> how such an OCCI Extension could look like. >>>> >>>> Cheers, >>>> Maik >>>> >>>> >>>> ================================================================== >>>> GWDG - Gesellschaft für wissenschaftliche >>>> Datenverarbeitung mbH Göttingen >>>> Am Fassberg 11, 37077 Göttingen >>>> Geschäftsführer: Prof. Dr. Ramin Yahyapour >>>> Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger >>>> Sitz der Gesellschaft: Göttingen >>>> Registergericht: Göttingen >>>> Handelsregister-Nr. B 598 >>>> WWW: www.gwdg.de >>>> ------------------------------------------------------------------ >>>> Fon: 0551 39-20364 >>>> Fax: 0551 201-2150 >>>> AG (e)Science >>>> E-Mail: maik.srba@gwdg.de >>>> >>>> >>>> _______________________________________________ >>>> occi-wg mailing list >>>> occi-wg@ogf.org >>>> https://www.ogf.org/mailman/listinfo/occi-wg >>>> >> _______________________________________________ >> occi-wg mailing list >> occi-wg@ogf.org >> https://www.ogf.org/mailman/listinfo/occi-wg >> tps://www.ogf.org/mailman/listinfo/occi-wg
participants (5)
-
Alexis Richardson -
Andre Merzky -
Gary Mazz -
Michael Behrens -
Srba, Maik