OpenStack as a Software Factory Mehdi Abaakouk Nick Barcet - - PowerPoint PPT Presentation

▶

Feb 19, 2023 327 likes •553 views

OpenStack as a Software Factory Mehdi Abaakouk Nick Barcet mehdi@enovance.com nick@enovance.com @nijaba Who Are We? American Head Office European Head Office Paris, France Montral, Canada Founded 2008 R&D office R&D office

SLIDE 1

OpenStack as a Software Factory

Mehdi Abaakouk mehdi@enovance.com Nick Barcet nick@enovance.com @nijaba

SLIDE 2

Partnership with

Who Are We?

Founded

2008

Team

90+

Growth

200%

Clients

200+

European Head Office American Head Office Asian Head Office

Paris, France Montréal, Canada Singapore

R&D office

San Francisco, USA

R&D office

Bangalore, India

SLIDE 3

OpenStack makes most developers dubious...

SLIDE 4

How can Openstack handle

Contribution of 400 developers / month?
Developers from 250 companies?
10+ integrated projects?

SLIDE 5

And yet release a new version

every 6 months
with 400 new features
without major inconsistencies?

SLIDE 6

With a single release manager

Who still has time to play ping pong???

SLIDE 7

The answer lays in the process...

SLIDE 8

...and test driven development

SLIDE 9

OpenStack's Contribution Process

SLIDE 10

Everything in Git

Process description and code
Infrastructure used to handle the process
Code to deploy the infrastructure

100 times better than documentation of a manual process that is never up to date...

SLIDE 11

This is so good that we had to offer to share it with others...

SLIDE 12

…and offer a solution to use it on premise

SLIDE 13

Step by step

1. Deploy OpenStack as a private cloud
2. Deploy Software Factory
3. Connect Redmine, Jira, ...
4. Create a new project
5. Start coding!

SLIDE 14

Why is this so great?

SLIDE 15

Improve efficiency

Nothing is local, everything is shared
Control access rights
Contributive model
No need for a full release team
Factorize hardware needs

⇒ Stop learning how to build and get coding

SLIDE 16

Reproducible environments

Dynamically provision test environments

when needed by Jenkins

Allow developers to generate a test

environment for debugging at will

Store validated releases and customer

specific environments (in Swift)

SLIDE 17

Parallelize work

Validate code changes and multiple

deployments environments at once

Accommodate more devs working on the

same projects

Limit wait times

⇒ Industrializes development and...

SLIDE 18

Release more often!

SLIDE 19

How do we deliver it?

eDeploy + Puppet
Heat + Puppet
Scalable Git
Scalable Artefact repo
Manage project
Onsite consulting

⇒ Private cloud ⇒ Deploy Software Factory ⇒ Swift as backend ⇒ Swift again ⇒ Django based web UI ⇒ Implement specific workflow + Specific connectors + Specific dvcs, languages...

SLIDE 20

Where are we with it?

Dogfooding within eNovance
First customer trial in progress

V1.0 GA planned in 3 months

SLIDE 21

Questions?

Mehdi Abaakouk mehdi@enovance.com Nick Barcet nick@enovance.com @nijaba