### Let’s explain what is RDO
Officially the RDO acronym doesn’t mean anything, I believe is sort of ReDhat Openstack. RDO is a “community”effort to bring OpenStack to Fedora, CentOS and RHEL. Well, much more than a community, is basically a beta testing of the next RedHat “enterprise” flavor of OpenStack. RedHat has a strong commitment on OpenStack and a large number of people have been hired. What I learned from the tests:
- Ubuntu is still ahead of RedHat in field experience, as most of the development is done on Ubuntu, but they’re doing a great job and quickly catching up.
- Although using Python to generate Ruby sounds crazy, PackStack is doing the job quite nicely and you can have a nice playground in basically no time. The answer file is a great idea when you have to replicate the environments, say as a professional services.
- Having also a monitoring suite (Nagios) deployed with the infrastructure could be a nice plus.
- GluterFS is not that bad and I decided to go for it as a redundant NFS system at home and in my servers in colocation.
- Openvswitch is something I always wish to explore and, once understood, along with IP nets and IP VPN opens up a world of new possibilities, also if OpenStack is not involved.
- Everything in one box, the simplest installation
- Two servers, one holding all the packages with an extra compute
- Two servers, GlusterFS Backend and VLAN-based Neutron
What comes with RDO
RDO is a yum repo hosted on Fedora project and works with Fedora and RHEL6 or 7.
The installer and required package is PackStack (openstack-packstack). Packstack is a command-line Python utility that uses Puppet modules to deploy various parts of OpenStack on multiple pre-installed servers automatically. Basically it contains a puppet master and some puppet modules, then the Python code generates the temporary puppet modules that creates or modify the infrastructure. At the end of installation, packstack creates an “answer file” that can be modified and re-applied to reconfigure the infrastructure.
- Cinder (supported backends: lvm, gluster, nfs)
- Neutron (defaults to openvswitch, vLAN ranges and tunnel supported)
- Heat (CloudWatch APIs available)
- Tempest test suite is also available
Test 1: everything in one box
Test 2: two servers, one holding all the packages with an extra compute
Test 3: two servers, GlusterFS Backend and VLAN-based Neutron
- Keystone and start integrating SecurePass as authentication schema
- Openvswitch and find out best practices to configure networking in an enterprise environment