The document discusses implementing DevOps at scale using dynamic test environments. It outlines challenges with static test environments including lack of repeatability and fixed configurations. Dynamic sandboxes delivered as a service are presented as an approach to enable continuous testing by providing on-demand, flexible test environments that integrate with DevOps pipelines. A case study demonstrates how a global manufacturer used dynamic sandboxes to improve developer productivity, reduce risk through production-like testing, and provide better visibility and control of infrastructure usage.

1. Quali
Implementing DevOps at Scale
using Dynamic Test Environments Pascal Joly

2. Agenda
2
1 Intro
2 Challenges
3 Approach
4 DEMO
5 Q&A

3. 01
02
03
Venture-funded start-up focused on Cloud
Automation and Orchestration. Managing
$Billions in Infrastructure.
Delivers “Cloud Sandboxes” - Replicas of
production environments delivered as-a-
service.
Strong Innovation DNA – Trusted by customers
Worldwide. Managing millions of Infrastructure
elements
About Quali
3
150+ customers – Cloud providers, Telcos, Enterprises
– across FSI, Retail, Healthcare and Government
~120 employees in USA, Israel and Europe focused on
serving customers worldwide150+

4. Infographic
Download here: http://bit.ly/2nY4FTB

5. 46%
Lack Self-Service Access
33%
> 1 week
Time to
Deliver Infrastructure
Infrastructure Agility
26%
> 1 month
#2
Barrier to
DevOps
Automation
Automation
“Continuous Test”
Application Environment Complexity
68% 70% <23%
App Complexity
Impedes Agility
Want Hybrid
Clouds
Applications on
Hybrid Clouds
*Based on Quali 2016 survey of 2045 respondents
DevOps Challenges: the numbers

7. Continuous Testing Enables Velocity
Start coding
Servers
delivered
IT builds Dev/Test
environments
Request Dev/Test
resources from IT
Project starts
Gather requirements
Prioritize work
IT kicks off
procurement Deployment
Performance
testing
Testing
Bug fixing
Production

8. DevOps Paradigm
SPEED
(PERFORMANCE)
QUALITY
(RISK)
ENVIRONMENT
Move Fast, But Minimize Risk…and Oh, Don’t Break Things

9. Static Test Environments
• Setup once (manually)
• Resources are pre-
allocated
• WOMM
• Not repeatable
• Fixed configuration

10. Shifting to Dynamic Environments
(Sandboxes)

11. Static Vs. Dynamic Environments
STATIC
• Setup once (manually)
• Resources are pre-allocated
• WOMM
• Not repeatable
• Fixed configuration
DYNAMIC (Sandboxes)
• Resources allocated on demand and
reclaimed automatically
• Can select what’s saved between
sessions
• Repeatable
• Flexible configuration
• Require orchestration

12. Orchestration and Blueprinting Make Dynamic
Environments Repeatable

13. Dynamic Environments Enable Self-Service

14. Dynamic Environments Are a Live Context Users Can
Interact With

15. Visibility and Control

16. Dynamic Environments as part
of the DevOps tool chain

17. CI/CD: Gluing it all together?
Dev Load Security Integration
Staging/
Production

18. Dynamic environments are a part of an End-to-End
DevOps pipeline
Dev
Quali
Sandboxes
Deploy
Teardown
Deploy
Teardown
Deploy
Teardown
Deploy
Teardown
Deploy
Teardown

19. DevOps Automation Journey: a Practical Approach
• P/V Infra.
• Applications
• Database
• Tools
• Services
MODEL

• Discovery
• Configuration
(P/V Infra.,
Applications)
• User to group
mapping
INVENTORY

INFRA/APP OWNER
• Publish self-
service
catalogs
• Workflows
• Standardized
CREATE
BLUEPRINTS

BLUEPRINT DESIGNER
AUTOMATE &
ORCHESTRATE
• Deploy
• Active
Environments
“Cloud
Sandboxes”
• On any cloud

BLUEPRINT CONSUMER BLUEPRINT CONSUMER
BI &
ANALYTICS
• Visibility
• Costing
• Utilization
• RoI
INFRA/APP OWNER
6
WORKFLOW
Consume
• Single pane of
glass
• Console RDP
and SSH
• API Access
• Tools


20. Case Study: Global Manufacturer
Digital Transformation to Sustain Competitive Edge
• Distributed R&D across
several countries
• Enterprise Scale
Development (100+
developers and testers)
• Main use case: production
and dev/test in the public
cloud (Microsoft Azure)

21. DevOps Pain Points
• Scalability and maintainability
• Release velocity vs. quality assurance
• Control cloud consumption (IT)
• Enforcing standards
Developer/Tester/TL
“I need access to a
configured
environment”
DevOps Team
“I need to improve
the productivity of
my dev/test teams”

22. Technical Accomplishments (phase 1)
• Blueprint and standardize
environments for three main use cases
relevant for the SCRUM teams
• Remove dependency on static
environments and the overhead of
maintaining them
Feature validation
environment
Development
Environment
CI nightly
environments

23. Technical Accomplishments (Phase 2)
• Defined the orchestration workflow using a
building block based orchestration platform.
• Integrated environments with other eco-
system tools
Copy artifacts
Redact data
Deploy release
Configure 3rd
party components
Apply project
settings
Start app
Install dependencies

24. 24
DEMO

25. Tying it back together
Scaling DevOps
Blueprint Automation within the CI/CD pipeline, enable faster Time-to-Market
for digitization for your entire organization
Reduce Risk
Production-like sandbox as-a-service with continuous testing increase quality
with better predictability
Better Visibility and Control
Centralized Management of your infrastructure consumption and applications
artifacts
Benefits of using Dynamic Test Environments for DevOps

26. Ask for a Technical Demo
(30-min web conference)
Start a Free Trial
(30-min web conference)
Want to Learn More?
Contact us: info@quali.com

27. Questions?

28. Sauce Labs and CloudShell: Under the Hood

29. CloudShell Sandbox in the DevOps Tool Ecosystem
Test framework
Build / Release Automation
Repository
Bug tracking Monitoring
Data Virtualization
Cloud & ContainersConfiguration
Management
Physical
Infrastructure