CompatibleOne Cloud Broker – Setup

This article describes how CompatibleOne can be setup and executed.

Cloud Brokering

See the CompatibleOne site for details on how the authors solved cross-vendor cloud brokering in a completely opensource solution. We will use this for our testing.

Use Case: We want to take a hardened image running on an Amazon EC2 server and migrate it to Microsoft’s Azure Platform. This first article discusses the underlying setup for CompatibleOne. We verify using an OpenStack implementation running on the low-cost Digital Ocean cloud provider; we’ll get to EC2 and Azure in a future article.

OpenStack

The CompatibleOne documentation has a brief tutorial on OpenStack, so we have a separate article on OpenStack setup which you can review.

CompatibleOne Host Platform

CompatibleOne runs on various Linux distributions. You can get the CompatibleOne software from this link and the choices are CentOS, RedHat (RHEL), Fedor, Ubuntu, and Debian. We chose Debian.

Our preference is to install and run CompatibleOne locally so we can do offline testing. We first tried to get the package to build and install using Cygwin so we could run CompatibleOne on our local laptop but that failed. We ended up using VMware Workstation and downloading a minimal (“network”) 32-bit Debian image so we could keep the footprint small.

OpenSSL, CompatibleOne, and Debian. CompatibleOne was built with Debian 6 in mind but the current version is Debian 7. Debian 7 uses the long-awaited OpenSSL v1.0 but CompatibleOne requires OpenSSL 0.9.8; this can be downloaded from this Debian link and installed as follows: dpkg -i libssl0.9.8_0.9.8o-4squeeze14_i386.deb

CompatibleOne Install

CompatibleOne comes with a reasonably complete documentation guide and using apt-get install compatibleone-accord as documented in the CompatibleOne Debian reference.

Once installed the system initially came up fine.

CompatibleOne – After First Boot

Upon a reboot, the CompatibleOne system services did not start:

root@CompatibleOne:/# co-status
-----------------------------
 Accords Platform Components
-----------------------------

Note that no services display. However, the co-check command reported that all categories were installed properly:

root@CompatibleOne:/# co-check
-- Verification of Accords Platform Category Managers --
-- import : OK
-- manifest : OK
-- node : OK
-- infrastructure : OK
[...output cut...]
-- paas_environment_template : OK
-- paas_environment_variable : OK
-- Verification Terminated --

Starting the CompatibleOne system reported an error:

root@CompatibleOne:/# co-start
./rest: no such directory

Instead, use the auto-installed /etc/init.d/compatibleone start command and all is well:

root@CompatibleOne:/# co-status
-----------------------------
 Accords Platform Components
-----------------------------
tcp        0      0 0.0.0.0:8109            0.0.0.0:*               LISTEN      3704/conagios
tcp        0      0 0.0.0.0:8110            0.0.0.0:*               LISTEN      4074/paasprocci
tcp        0      0 0.0.0.0:8112            0.0.0.0:*               LISTEN      4010/cnprocci
tcp        0      0 0.0.0.0:8113            0.0.0.0:*               LISTEN      4042/eziprocci
tcp        0      0 0.0.0.0:8086            0.0.0.0:*               LISTEN      3556/publisher
[...output cut...]
tcp        0      0 0.0.0.0:8106            0.0.0.0:*               LISTEN      3674/slam
tcp        0      0 0.0.0.0:8107            0.0.0.0:*               LISTEN      3684/copaas
tcp        0      0 0.0.0.0:8108            0.0.0.0:*               LISTEN      3694/coeasy