dcsimg
Read more on "Real World Open Source" »

TripleO Evolves for OpenStack Deployments

By Sean Michael Kerner (Send Email)
Posted April 14, 2016


There are a lot of different ways to deploy an open-source OpenStack cloud, and one of the best ironically is with OpenStack itself, via a project known as OpenStack on OpenStack (OOO), or just simply TripleO.

Mark McLaughlin OpenStack Technical Director of Red Hat, explained to ServerWatch that his company uses a lightweight OpenStack deployment Red HatRed Hat refers to as the undercloud. TripleO is used for workflow, enabling and deploying nodes that enable the undercloud.

"With Red Hat OpenStack Platform (OSP) 6, which was based on OpenStack Juno, TripleO debuted as a tech preview and we added it as fully supported for OpenStack Kilo and OSP 7," McLoughlin explained.

The productized version of the open-source TripleO effort is called OSP Director by Red Hat. McLaughlin noted that TripleO is the fully-supported default approach for Red Hat OpenStack as well as for Red Hat's partners to integrate with.

TripleO's Evolution to Match Real-World Challenges

Since Red Hat started using TripleO for production deployments, the technology has evolved to match challenges found in the field. McLaughlin noted that the first version of TripleO in OSP 6 didn't support IPv6, which is something that Red Hat customers needed.

IPv6 support was integrated into the upstream TripleO project during the OpenStack Liberty and Mitaka development cycles and has been backported into OSP 7.

"TripleO is a very active project, and we have a lot of developers working on it," McLaughlin said. "It's a deployment tool that really cuts it for doing production, real-world deployments that include complex networking and storage configurations."

That said, McLaughlin noted TripleO isn't a project with a whole lot of community momentum behind it and isn't widely used for Do-It-Yourself (DIY) use-cases. However, TripleO is working out well for Red Hat and its customers.

From a deployment perspective, McLaughlin explained that with TripleO deployments, there are essentially a number of OpenStack Heat templates. Heat is an OpenStack orchestration project.

The Heat templates could include specific templates for a given vendor's technology. For example, NetApp has a storage template to enable their technology in a Red Hat cloud.

Looking Forward for TripleO

Looking forward, for the new OpenStack Newton development cycle, McLaughlin said that TripleO will expand further.

"We're going to expand the template model to be more granular and pluggable," McLaughlin said.

The basic idea behind the expanded template model for TripleO is to enable developers and vendors to more rapidly add new technologies that can be deployed. By templating all the potential services in an OpenStack deployment, it will also be easier to scale and add new services.


Sean Michael Kerner is a senior editor at ServerWatch and InternetNews.com. Follow him on Twitter @TechJournalist.

Follow ServerWatch on Twitter and on Facebook

Page 1 of 1

Read more on "Real World Open Source" »

Comment and Contribute

Your name/nickname

Your email

(Maximum characters: 1200). You have characters left.


 

 


Thanks for your registration, follow us on our social networks to keep up-to-date