dev ops•
2015
DevOps est une démarche de collaboration
agile entre Etudes (Dev), Production (Ops) et
Métiers (Business) sur l’ensemble du cycle de
vie du service du design au support en
production.
Nos groupes produits pratiquent DevOps depuis
des années (Windows, Office, Visual Studio…), nous
faisons partie des pionniers du DevOps avec
Amazon, Google et Facebook et comme nos
clients, nous avons dû nous transformer et intégrer
DevOps.
DevOps est une démarche de collaboration agile entre Dev, Production (Ops) et Business sur l’ensemble du cycle de vie du service du design au support en production.
Culture de collaboration
AutomatisationAccelerating
delivery
Amélioration de
la qualité de
service
Amélioration
continue
Monitor & Learn
continuous
feedback
Accélération du
provisionning
Fiabilisation des
déploiements
Automatisation
des tests
Accélération du
Time to Market
Accélération des
résolutions
d’incidents
(MTTR)
Industrialisation
des
déploiements
DevOps assessment
1 Agile operations
5 Construire la roadmap contextualisée du clientétapes pour aller vers un modèle DevOps optimal
Agile development
Agile collaboration
DevOps for business
5 DevOps strategy
ops
ops
dev
devbiz
board
5 se
ns
du feedbac
kdan
s une d
ém
arch
e D
evO
ps L’oreille de l’utilisateur
Les yeux de l’utilisateur
Les nez de l’utilisateur
La voix de l’utilisateur
La main de l’utilisateur
cloud strategy
provisioning (on premise or in the cloud)
production
ops
staging
ops
integration
ops
build strategy
dev
dev
dev
agile practices & method
business implication cases & needs management
agile infrastructure management
capacity/change/configmanagement
incident & problems management
proactive monitoringservices level management
and catalogagile master management
infrastructure as a code
Réussir sa collaboration agileacteurs (dev-ops-biz) pour un succès commun3
common metrics
replicationreplication
teststests tests
tests strategy & automation
biz
apps metrics & telemetry
release automation
database lifecycle
IT security
Build
Test
Deploy Environments Monitor and Learn
Processes
Dev/Test
Integration
Pre-Production
ProductionConfiguration
Develop
DEV
BIZ
OPS
Outiller sa démarche devopsusages pour toutes les pratiques7
Business case
A new release is ready to be deployed
STAGING CAEAGENCE
RMOperations team and brand team are
notified that a new package will be deployed on staging CAE environment.
OR
KO
Change request
OK
PRODUCTION CAE
OR
KO
Incident request
OK
Push the package in Release
Management
RM Check current version
CD / WEBROLES
Proceed to functional tests
Incident Request Release done
Push the package in Release Management
RMNotify the deployment failure causes to
operations teams and brand team
Package sitecore data
New request
RM Deploy the package
RM Patch config files for current environment
RM Verify the deployed release
RM Deploy data if needed
RMNotify operations team and brand team
of sucessful deployment status
Wait to deploy the release
OK
Push the package in Release Management
RM
Operations team and brand team are notified that a new package will be
deployed on production CAE environment.
RM Check current version
RM Deploy the package
RM Patch config files for current environment
RM Verify the deployed release
RM Deploy data if needed
RMNotify operations team and brand team
of sucessful deployment status
RMNotify the deployment failure causes to
operations teams and brand team
RM Backup the database
RM Build the azure sitecore package
RMNotify backup and build status to
operations team
RM Deploy the package on offline side
RM Proceed to integrity tests
RM Set website offline if needed
OR
RMSave an historic version of the package
and notify it
Validate the restore in Release Management
RM Restore database
Validate the package in Release Management
RM Push website online
KO
side2side
RMNotify the restore status to operations
team
Proceed to functional testsProceed to functional tests
Proceed to functional tests
RM Block the publish function
A release contain :- Build *- Config file- Instructions- SQL scripts- Needed Data (sitecore package)
Not included in a release and not automated
Not included in a release and not automated.Contain instructions.
AUTOMATED !
Y
AX B
Etapes Activités
Age
nce
Mar
qu
e
Infr
astr
uct
ure
L'O
real
Infr
astr
uct
ure
Ext
ern
e
Dev
elo
pp
emen
t
L'O
real
Push the package in Release Management A R I I IStaging CAE
Operations team and brand team are notified that a new package will be
deployed on staging CAE environment.A I I I I
Check current version I I A R I
Deploy the package A I R R I
Patch config files for current environment A I R R C
Deploy data if needed A I R R C
Verify the deployed release A I R R I
Notify operations team and brand team of sucessful deployment status I I A I I
Proceed to functional tests A R I I I
Notify the deployment failure causes to operations teams and brand team I I A R I
Production CAE
Push the package in Release Management A R C I I
Block the publish function A I R R C
Operations team and brand team are notified that a new package will be
deployed on production CAE environment.A I I I I
Check current version C I R R A
Deploy the package A I R R C
Patch config files for current environment A I R R C
Deploy data if needed A I R R C
Verify the deployed release A I R R I
Notify operations team and brand team of sucessful deployment status I I A I I
Proceed to functional tests A R I I I
Notify the deployment failure causes to operations teams and brand team I I A R I
CD / Webroles
Push the package in Release Management A R C C C
Backup the database I I A R R
Build the azure sitecore package C I A R R
Notify backup and build status to operations team I I A R I
Set website offline if needed I I A R I
Deploy the package on offline side C I A R R
Proceed to integrity tests A I R R I
Proceed to functional tests R A I I I
Validate the restore in Release Management C I A R C
Restore database I I A R C
Notify the restore status to operations team I I A I I
Validate the package in Release Management A R C C C
Push website online A C R R C
Save an historic version of the package and notify it I I A R C
DevOps