cloudstack collab - killing of the dinosaurs

Killing oFf the Dinosaurs

Noel King, John Turner

DISCLAIMER NOTE !!

All characters and events in this presentation — even those based on real people — are entirely fictional.

!Any resemblance between dinosaurs and real persons, living or dead, is purely coincidental. !However, those depicted by the evolutionary series are real and may be in the audience (look for the reaction!).

#CCCEU13 #KillBarney

Configosaurus Rex


Configosaurus RexCharacteristics

• Configurations drift between: • Applications. • Application environments. • Servers within an application tier.




Cause of Death • Configuration pushed through a delivery pipeline. • Configuration managed through Chef. • Restricted access to servers. • Tooling to compensate for restricted access. • Immutable servers.




Cause of Death • Configuration pushed through a delivery pipeline. • Configuration managed through Chef. • Restricted access to servers. • Tooling to compensate for restricted access. • Immutable servers.

Cost Knight Capital Americas LLC

$465 MILLION


Testodactyl


Testodactyl

Characteristics • Over reliance on manual testing. • Focus on system testing. • Requires dedicated end-to-end system.


Testodactyl

Characteristics • Over reliance on manual testing. • Focus on system testing. • Requires dedicated end-to-end system.

Cause of Death • Testing as part of feature definition. • Emphasis on testing components/services. • Well defined boundaries and contracts. • Includes functional and non-functional testing. • Exploratory testing is the small end of the wedge.


INFRA-raptor


INFRA-raptorCharacteristics

• Over provisions hardware just in case. • Number of nodes. • Number of environments.

• Retains hardware unnecessarily.


INFRA-raptorCharacteristics

• Over provisions hardware just in case. • Number of nodes. • Number of environments.

• Retains hardware unnecessarily.

Cause of Death • Provision on demand, as a service. • Environments are lifecycle managed. • Usage based billing promotes efficiency.


DOCUsaSurus


DOCUsaSurus

Characteristics • Maintains a large filing cabinet. • Documents and files everything! • Often quotes audit and compliance.


DOCUsaSurus

Characteristics • Maintains a large filing cabinet. • Documents and files everything! • Often quotes audit and compliance.

Cause of Death • Living documentation / automatic document

production. • Derived from:

• User stories. • Source control commit comments. • Acceptance test definitions. • Build pipeline stage promotion.


Monasaurus


MonasaurusCharacteristics

• Monitors infrastructure metrics. • Focus on incident response. • Generates little insight. • Long mean time to recovery.


MonasaurusCharacteristics

• Monitors infrastructure metrics. • Focus on incident response. • Generates little insight. • Long mean time to recovery.

Cause of Death • Application performance monitoring.

• Autonomous instrumentation. • Log search and aggregation. • DevOps


TriTechatops


TriTechatopsCharacteristics

• Loves to introduce new technology. • Little consideration for impact:

• Budget • Complexity • Operational management


TriTechatopsCharacteristics

• Loves to introduce new technology. • Little consideration for impact:

• Budget • Complexity • Operational management

Cause of Death • Managed technology introduction. • Ownership resides within architecture. • Application service menu. • Enforcement within the PaaS layer.


Extinction


evolution


Dryopithecus


Dryopithecus

• Manual testing on completion of development. • Systems integration is onerous and occurs after

development completion. • Environment provisioning is manual and

expensive. • Deployment is manual. • Development groups have goals that bring them

into conflict. • Change management is ad-hoc.


Ramapithecus


Ramapithecus

• Clear product ownership. • Change management controls. • Business participants collaborate on delivery

related activities and decisions. • Some automated testing. • Production-like test environments. • Scripted builds and configuration. • Iterations of one month or more.


Homo Erectus


Homo Erectus

• Trunk based development with continuous integration.

• Sufficient test automation to detect critical defects.

• Provisioning of environments is mostly automated.

• Database changes are versioned and scripted.


Neanderthal


Neanderthal

• Deployment pipeline automatically rejects bad changes from version control.

• Cross-functional end-to-end product-centric teams manage products throughout life cycle.

• Comprehensive automated test suites created through TDD/ATDD.

• Teams monitor and manage work in progress and deliver work in small batches.


Modern Man


Modern Man

• Requirements describe how the value of the feature will be measured.

• Product teams are responsible for implementing metrics to gather data.

• Systems are architected to support continuous deployment.

• Database changes are decoupled from application deployments.


Help WantedCheck out

workwithpaddy.com


cloudstack collab - killing of the dinosaurs

Technology

cause of death testing

system testing

application environments

manual testing

number of environments

cause of death configuration

application tier

immutable servers