[Interoperability] CompatibleOne Cloud Agregation Proof of Concept

Sun Nov 13 04:39:05 PST 2011

FYI news from CompatibleOne

-----
To : compatible general 
from : Jamie Marshall 
Date : 11/12/2011 08:05PM

Dear All,

Yesterday morning, Friday the 11th of November 2011, I put the final touches to the integration of the Open Nebula Client within the OpenNebula Procci for use by the Accords brokering and provisioning platform of CompatibleOne.

I provide all you with a copy of the manifest and the instance data concerning the two provisioned compute instances, one on the OpenNebula platform at TSP and the other on the OpenStack platform at eNovance. 

It is a great moment to actually see that which we have been hoping and working for over these past months actually operational at last.

Looking forward to your remarks and observations, and I would like to add that it has been an great pleasure to work with you all on this project.

Sincerely
Jamie

(ps: the source is published on the ow2 gitorious under the accords platform project )
---------------------------------------------------------------------------------------------------------------------------------------------------------
CompatibleOne : Cloud Agregation Proof of Concept ( IJM, 11/10/2011 )
---------------------------------------------------------------------------------------------------------------------------------------------------------
1) Here is the mixed operation manifest where in red you can see the explicite declaration of use of opennebula as the provider for the SqlDatabase node, and of openstack as the provider for the Xwiki node.

<?xml version="1.0" encoding="UTF8"?>
<manifest name="POCXWIKI" xmlns="http://www.compatibleone.fr/schemes/cords.xsd">
        <description>
        This file contains the description of the X-Wiki System for the Compatible One
        Proof of Concept of Automatic Provisioning and Configuration
        </description>
        <node name="sqldatabase" provider="opennebula" >
                <infrastructure name="dualcore"/>
                <image name="mysql"/>
        </node>
        <node name="xwiki1" provider="openstack">
                <infrastructure name="quadcore"/>
                <image name="xwiki"/>
        </node>
        <configuration name="pocxwiki">
                <action name="connectxwiki1"
                        type="cordscript"
                        expression="xwiki1.configure(sqldatabase.hostname);"/>
        </configuration>
        <account name="compatibleOnePocXwiki">
                <user name="jamie"/>
                <user name="fabio"/>
                <user name="jeanpierre"/>
        </account>
        <security name="public" level="public"/>
</manifest>

2) Here is the information retrieved from the OpenNebula platform concerning the SqlDatabase virtual machine:

GET /compute/664 HTTP/1.1
HTTP/1.1 200 OK

<COMPUTE href="http://localhost:4567/compute/664">
<ID>664</ID>
<NAME>sqldatabase</NAME>
<INSTANCE_TYPE>small</INSTANCE_TYPE>
<STATE>ACTIVE</STATE>
<DISK>
<STORAGE href="http://localhost:4567/storage/64" name="compatibleOne"/>
<TYPE>DISK</TYPE>
<TARGET>hda</TARGET></DISK>
<NIC>
<NETWORK href="http://localhost:4567/network/68" name="LAN_Jamie"/>
<IP>10.142.40.4</IP>
<MAC>02:00:0a:8e:28:04</MAC>
</NIC>
<NIC>
<NETWORK href="http://localhost:4567/network/66" name="PUB_Compatible"/>
<IP>157.159.249.199</IP>
<MAC>02:00:9d:9f:f9:c7</MAC>
</NIC>
</COMPUTE>

you can see the two network interfaces, the second as its name suggests is the Public interface and the IP address
in red is retrieved by the OnProcci to use as the hostname value for use by the configuration instrcution

       xwiki1.configure(sqldatabase.hostname)

from the above manifest.

3) Here is the information retrieved from the OpenStack platform describing the Xwiki virtual machine:

GET /compute/347 HTTP/1.1
HTTP/1.1 200 OK

{ "server":
{ "status":"ACTIVE", "updated":"2011-11-11T09:28:33Z", "hostId":"be5522dad4a1cac65089dbf3b8dde8765d6e5ef9d936a7f78e091622", "user_id":"jamie.marshall", "name":"xwiki1", "links":
[
{ "href":"http://94.143.114.137:8774/v1.1/prologue/servers/347", "rel":"self"},
{ "href":"http://94.143.114.137:8774/prologue/servers/347", "rel":"bookmark"}], "addresses":
{ "private":
[
{ "version":"4", "addr":"10.42.9.5"}]}, "tenant_id":"prologue", "image":
{ "id":"39", "links":
[
{ "href":"http://94.143.114.137:8774/prologue/images/39", "rel":"bookmark"}]}, "created":"2011-11-11T09:28:24Z", "uuid":"25dccf0d-d146-4650-b5b0-f3b3283ce230", "accessIPv4":"", "accessIPv6":"", "key_name":"null", "progress":"100", "flavor":
{ "id":"12", "links":
[
{ "href":"http://94.143.114.137:8774/prologue/flavors/12", "rel":"bookmark"}]}, "config_drive":"", "id":"347", "metadata":
{ "publisher":"http://127.0.0.1:8086", "ServerName":"xwiki1", "contract":"http://127.0.0.1:8095/openstack/a2a99723-62ea-417f-a35e-3237eca8a118", "sqldatabase_hostname":"157.159.249.199"}}}

In blue and red you can see that the meta data has been created by the sqldatabase_hostname instruction using the 
public IP address of the SqlDatabase machine on the OpenNebula platform.

---------------------------------------------------------------------------------------------------------------------------------------------------------
End of Proof of Concept
---------------------------------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/interoperability-opennebula.org/attachments/20111113/83a4eb07/attachment.htm>