[Fiware-miwi] WebTundra fi-lab and chef recipe: story so far

[Erno Kuusela]

Hello,

In last weekly there was talk about sharing these. Here's
how far I've got:

0) Requested and eventually got an account to http://130.206.80.61/ (per
instructions in minutes)

1) Followed general patterns in
http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_create_recipes_for_the_GEs

(At some point realized that this vm management UI is just the standard
OpenStack one, lot of info on the web.)

for chef specific things, the googel doc doc was better,
https://docs.google.com/document/d/1r-CBmWbGjh0p_EPoxTz26xJGWe5Z8zpYGQ9uZvVwc1A/edit?pli=1
(and also chef material on the web)

2) create keypair in openstack ui

3) Launch an instance by going to "images" tab and selecting one.
There's no image matching the name in wiki ("paas-chef-solo-templ"), I
used the Ubuntu-chef image instead.  Instance creation didn't work first
time around (sometime last week, status just showed "error" and nothing
in log), but today it worked.

4) edit security groups. The "From port" and "to port" in the ui means
the start and end of a port range, not source and destination ports. 
Also -1 seems to be code for "any".  To get working TCP you have to pass
ICMP unreachables for PMTU discovery, so add ICMP -1 -1 0.0.0.0/0 in
addition to your TCP ports.

5) allocate public IP for your instance. The UI hanged every time for
me.  But when trying to allocate from the second (not default) net8100
pool the IP was eventually allocated when I reloaded the UI.
Assigning this to my instance worked OK.

(ideally create volumes and containers here, but their creation didn't
work)

6) no dns is provided, i put it under our own domain
as fi-vm1.playsign.net

7) connect using something like
ssh -l root -i ~/src/fiware/filab/erno-filab-keypair.pem fi-vm1.playsign.net

8) install latest security patches
(apt-get update && apt-get dist-upgrade && reboot)

9) see that chef bits are already installed (chef-solo and chef-client).
Here i decided to do also the recipe development work on the vm
(usually that's on your workstation). So on the vm intiialize
a recipe template (knife create webtundra)

10) filled out the README and metadata and put recipe in
recipes/default.rb, made a test.json with run_list containing
"recipe[webtundra]", and tested using chef-solo -j test.json.
after a few trial and errors I had the WebTundra zip downloaded
and unpacked under web root, and dependency packages (unzip, apache2)
working in the recipe.

11) Following the google doc I moved the installation part from
default.rb into 1.0.0_install.rb and made additional
corresponding start/stop/uninstall recipes.

12) This fiware-required format no longer works with chef-solo (at least
I didn't immediately see how to run without a default recipe). But
there should be an automated testing system in fi-lab chef servers,
so according to the howto in the wiki I up loaded the recipe to the
svn. You can see the recipe in svn (under GESoftware/webtundra/).

13) I didn't yet find out where I can request an user account to the
auto-testing chef server....