Devops for Growth

Yann Degat, Solutions Architect chez OVH, explique pourquoi il a choisi de mettre à la disposition de la communauté Devops, des templates pour démarrer Terraform avec OVH. Il revient également sur les usages auxquels ils répondent.

(...)

Le choix de Terraform 

Plusieurs outils d’orchestration cloud permettent de faire de « l’Infrastructure as code ». Pour Yann, c’est le logiciel Terraform* qui répond le mieux au besoin, « car il a été, dès le départ, conçu pour gérer tout le cycle de vie de l’infrastructure. Et aussi parce qu’il est open source et bénéficie d’une communauté très active. » Enfin, c’est aussi parce qu’il supporte plusieurs fournisseurs que Yann en a fait une priorité. « Dans une perspective d’infrastructure multitechnologique et/ou multicloud, Terraform permet de décrire de l’infrastructure à provisionner chez différents fournisseurs ». Pour Yann, « choisir son orchestrateur, c’est un peu comme un artisan avec sa propre boîte à outils ! Chacun sélectionne ceux avec lesquels il est le plus à l’aise. L’important reste ce qu’on fait avec. Les recettes Terraform que nous écrivons vont nous permettre de démontrer toute la valeur de notre plateforme et tout ce que l’on peut faire avec OVH. »

Tacker is an official OpenStack project building a Generic VNF Manager (VNFM) and an NFV Orchestrator (NFVO) to deploy and operate Network Services and Virtual Network Functions (VNFs) on an NFV infrastructure platform like OpenStack. It is based on ETSI MANO Architectural Framework and provides a functional stack to Orchestrate Network Services end-to-end using VNFs.

Cross-project collaboration is something OpenStack community has embraced for a long time. Common libraries like Oslo reduces the time and effort to build a new service. Another way this manifests is in new OpenStack services getting built using existing services to solve an higher level use-case.

In this talk we are present how the band of projects comprising of Mistral, Tacker, Neutron, Heat, TOSCA-parser and Barbican came together to build an industry leading ETSI NFV Orchestrator that leveraged the best of these projects. Each of these projects brought in critical functionalities needed towards the final product. You will learn how, when strung together, this solution follows the classic Microservices design pattern that the industry is rapidly adopting.

Click h

The project is still quite healthy and is following the usual hype curve: OpenStack is finally mature enough that it’s less interesting to talk about, so it’s understandable that people think something happened.

The folks asking me this question are generally curios and good intentioned, and I think my answer says a lot about my professional background, so even during an interview I indulge in a short ramble.

I know, I know … I should have written about it at the time, but I had other things going on and wasn’t making space in my life to write. So I’ve decided to revisit the topic today. Next time someone asks me, I’ll just point them here 

• A trust is a promise to allow delegation at some point in the future. The actual delegation is performed in the token. The trust is used to get the token.
• The data for the delegation itself is simply the uuid user_ids for the trustor and trustee, along with the privileges that are being delegated.
• The delegated privileges are a combination of a tenant id and a number of roles that must be a subset of the roles assigned to the trustor.

Octavia is an open source, operator-scale load balancing solution designed to work with OpenStack.

Octavia was born out of the Neutron LBaaS project. Its conception influenced the transformation of the Neutron LBaaS project, as Neutron LBaaS moved from version 1 to version 2. Starting with the Liberty release of OpenStack, Octavia has become the reference implementation for Neutron LBaaS version 2.