Since Walmarts “OneOps” platform has been open sourced and placed on github for the world to use I have added yet another project onto my TODO list.
From a quick read OneOps is designed to deploy VMs from a single management infrastrcture onto any cloud platform; Azure, Rackspace, Amazon or even a local OpenStack system… basically being able to redeploy to whatever is cheapest at the time.
It is unlikely to be usable by me unless I install it on bare metal as the minimum hardware requirements seem to be 16Gb of memory… but for testing the installation and configuration steps I have fired up a 4Gb VM to work out how to get the software installed, when I have that tested/documented I will use bare metal.
The first step for me was obviously to install the documentation. That is very briefly covered in the readme at the main documentation project at https://github.com/oneops/oneops.github.io. Did I mention very briefly.
Fortunately the Fedora documentation at https://developer.fedoraproject.org/tech/languages/ruby/gems-installation.html covered most of the steps needed to install ruby/gems.
The steps here are how to install the documentation, based on a merging of the references above. The commands need to be run as root of course.
dnf install ruby-devel dnf group install "C Development Tools and Libraries" dnf install redhat-rpm-config patch git gem install jekyll gem install redcarpet useradd oneops su - oneops git clone https://github.com/oneops/oneops.github.io.git cd oneops.githup.io jekyll serve --no-watch
And then… you should be able to view the documentation using a local browser at http://127.0.0.1:4000/
And there is my first obvious problem. Netstat does indeed show a service listening on 127.0.0.1 port 4000… the key problem being it is listening only on 127.0.0.1 not on 0.0.0.0… the VM is a “server” with no desktop environment and it has no web browsers and because it is bound to localhost using a browser from another machine cannot read the doco !.
I installed my favourite text browser lynx onto the VM and confirmed the doco is being served correctly, but of course it is hard to follow the doc in a text browser.
Lots of grep on 127.0.0.1 and localhost failed to find where it was set.
So Day 2 to Day N will be trying to find where that is set so the documentation is network available via a gui browser rather than only available to localhost. If I cannot find that by the weekend I will install apache and “proxy” to the port, but I am trying to minimise software installs to just what is required.
So watch this space.
