As I introduced in my previous post there are two main options when considering an OpenStack environment; private Cloud RDO or OSP and we often find that cutting edge hardware requires cutting edge software.
OCF partners with RedHat who back the RDO project, a freely available community-supported distribution of OpenStack that runs on RedHat Enterprise Linux (RHEL), as well as providing a commercially supported RHEL operating system projects distribution. Because the latest version of RDO tends to be released in only a matter of days after the upstream release itself, it may make more sense to test and deploy with this distribution than the commercially supported distribution – but this is reliant on the user being willing to self-support.
Conversely, although RedHat arrived relatively late to the OpenStack party, they are now a major contributor and as partners we are able to draw on that resource to get issues resolved in short order. They are also working to close the stabilisation gap between upstream and OSP releases.
In RDO, the build process for compute or controller node images varies considerably with various options to build from development, tested or stable branches. It is one of the most challenging areas, as bugs fixed in one branch don’t necessarily appear in other branches. Some branches purely receive the updates from upstream with no backporting – taking newer updates and porting them to older versions of the system. So the time that is spent backporting bugs and applying fixes – work generally carried out by RedHat engineers in OSP – often takes place during deployment and inevitably more time is consumed.
Another fundamental aspect is the support coverage provided by RedHat – core components such as Nova, Keystone and Neutron will be covered – but other, newer or more esoteric projects may not. Currently, for example, support for Murano and Magnum doesn’t exist in OSP.
If containers are an important aspect of deployment (which we’re increasingly finding they are) then customers are more likely to be driven down the self-support route. Indeed, I see containers as the defining technology for OpenStack and its continuing success will, in part, depend on its ability to provide a service for this popular tool.
At OCF, we are very lucky to have a very talented OpenStack team. Whether you are a research intensive institution or a commercial organisation, we pride ourselves in being able to design, procure, implement and support your very own OpenStack to suit your needs. It’s our job to ensure the outcome meets the design.
Please get in contact with us to arrange a consultation with one of our team.