Notes on adding the Fuse Cartridge using RPM.

Fuse can be used on OpenShift using the Fuse Cartridge, the code for which can be found on github:https://github.com/jboss-fuse/fuse-openshift-cartridge. During the setup phase of a Fuse based application on OpenShift it downloads a big zipfile. I've been working on an rpm that includes the zip file to avoid this big download, to shorten the application setup and so it doesn't depend on a network connection to the outside.

At the moment the rpm is build from the openshift-enterprise-rpm-6.1 branch https://github.com/jboss-fuse/fuse-openshift-cartridge/tree/openshift-enterprise-rpm-6.1, and the finished product is placed in nexus.

If you want to build the rpm by hand use 'rpmdev-setuptree', copy the zip to ~/rpmbuild/SOURCE (this needs to be the cartridge zip containing the fuse.zip), copy the spec file to rpmbuild/SPEC and then build the rpm using 'rpmbuild -ba openshift-origin-cartridge-fuse.spec'.

Next copy the rpm to your OpenShift node and install it using rpm -U , and once it's done restart the

ruby193-mcollective service on node and import cartridge on broker 

 #oo-admin-ctl-cartridge -c import-node --obsolete  --activate 

You can check fuse cartridge is listed by rhc cartridge-list. Note that I only found the oo-admin-ctl-cartridge command on OpenShift Enterprise and not on Origin.

At this point the Fuse application should also be listed on the application page.

You can create a new gear from there or you can use rhc:

rhc app create fuse fuse -g medium

It should now have created a running Fuse gear. Please note that on my little laptop it took roughtly 15 minutes for it to show up and rhc and the console were sort of in a frozen state.

Add Medium Gear Capablity on OpenShift

The OpenShift Virtual Machine download is pre-configured with one node, in one district with a small gear profile. There are two ways to add another gear size

• add another node, in a new district with medium gears, but easier is it to
• remove the district restriction and allow both small and medium gears.

Edit the /etc/openshift/plugins.d/openshift-origin-msg-broker-mcollective.conf, and set
DISTRICTS_ENABLED=false
DISTRICTS_REQUIRE_FOR_APP_CREATE=false
NODE_PROFILE_ENABLED=false
ZONES_REQUIRE_FOR_APP_CREATE=false

Next in edit the /etc/openshift/broker.conf and set
VALID_GEAR_SIZES="small,medium"
DEFAULT_GEAR_CAPABILITIES="small,medium"

Then restart the node to let the changed take effect. If you have an existing user you may need to add the medium capability explicitly  using something like oo-admin-ctl-user -l demo --addgearsize medium.

Notes on Getting started with OpenShift

There are two versions of the RedHat Cloud: OpenShift Origin (the project) and OpenShift Enterprise. I needed the completely stable version, so I downloaded the OpenShift from https://access.redhat.com/home.  Navigate to the OpenShift Enterprise page, as shown in Figure 1.

Figure 1. Download OSEoD Virtual Machine

From here I downloaded the OSEoD Virtual Machine, which is a (large) vmdk file. This vm has a 10 Gb hard drive with only a few hunderd Mb of free space on it. On OSX I'm using VirtualBox and to increase this drive you will need to convert it to a vdi format. There is a great detailed writeup by Thomas Vial on this.

1. Convert to vdi:

VBoxManage clonehd box-disk1.vmdk box-disk1.vdi --format vdi

2. Extend to 30 Gb:

VBoxManage modifyhd box-disk1.vdi --resize 30720 

3. Now create a new virtual machine and hook it up to this new large file. Then under the settings for the CD/DVD drive point this to the GParted ISO on your disk. Now when you start the OpenShift VM, GParted is stared and you can extend the sda2 partition, and use all the newly created 20Gb. Now apply to the file system. Then disconnect the GParted iso and restart.

4. Now when the OpenShift VM comes up, sudo to root and now the new space needs to be added to the LVM. Check with 'df' what the LVM partition needs to be extended and use '

'lvm vgdisplay' to get the Free PE and using lvm lvdisplay  you can find the Current LE,

the Current LE + FreePE gives the new volume size. Use lvm lvresize -l  

to resize. Finally use resize2fs to use the new size. Verify with 'df' that the LVM is now larger. For more details see the centos docs.

5. Finally there are two small issues you have to workaround, the /etc/resolve.conf is recreated with every reboot of the server you need to manually add 'nameserver 127.0.0.1' back in. The other issue is that the harddrive is set to dynamically allocate space. This process slowed down the creation of an application for me such that OpenShift began to lock up. Copying a huge file into the filesystem, and then deleting it to force the allocation fixed that for me.