Get the Development, QA, Staging or Production Environment you need at the click of a button. The current situation: It wouldn’t be a bold statement to say that all software’s ultimate goal is to enhance the customer experience. How many times have we not read such comments on app stores or heard business say? “Great app, but I can only give it three stars until the developers add ...” But the Development team’s side of the story is “I am waiting for the environment to test the code with new features” Continuous Delivery and Continuous Integration can help release software updates more frequently and with almost no manual intervention, but there are some bottlenecks to being able to do this. Following are a few: - Delay in getting the Environments Lack of self-provisioning creates dependency on IT department. Lack of easily customizable Environments For Development, Testing and Staging with new features or updates to dependencies. Manual Provisioning of Environments Being repetitive and involving several steps, we would not be able to leverage the power of Automated Deployments and CI. And the hilarious but unfortunately true risk of “Oh! But it works on my laptop!” Not being able to recreate the environments easily and consistently can lead to not being able to recreate performance issues or release code or updates to production confidently! Inconsistent environments could result in such scenarios as a new update has been released to the production system and the system Admin might have put in the configuration or dependencies that only he or she is aware of to get the app working. Similarly the developer might have put in the unique settings on his or her laptop to get the code working on his or her workstation or laptop. Due to which every server becomes “works of art” and as unique as snowflakes. Needless to say inconsistent environments make it very difficult to determine why an application breaks when it's promoted to the next environment. Wasting the Developer and Operation teams time in determining if an issue is due to the source code or environment configuration. What is an Environment? It is not just an image or template of a virtual machine but all the compute, storage, network and several other resources (XaaS) that are required to host your application. Quite simply put, everything you can find inside the server room! Environments on Demand at the click of a button A solution that could give the Development, QA, Staging or Production Environment at the click of a button could remove all the bottlenecks and risks that we had discussed earlier and at the same time orchestrate Software-Defined Compute, Networking, Storage, Security and such to provide a smart infrastructure that is aware of resources needed by the application and is adaptive and responsive to the workloads dues to fluctuating business demand. All this while being easy to customise and simple

1. Software
Defined
Environment
Getting Dev, QA, Staging or
Production environment in a
click using Open Standards
Software like OpenStack,
Go CD…
One click deployments!

2. 2
““Great app, but I
can only give it
three stars until
the developers
add ...”

3. 3
“I am waiting for
the environment
to test the code
with new features”

4. software updates are
not being released
frequently?
Continuous Delivery can help but what can
make it really possible?
4

5. Bottlenecks
Delay in getting Environments
Lack of self-provisioning creates dependency on IT.
Lack of easily customizable Environments
For Dev, Testing and Staging with new features or updates to
dependencies.
Manual Provisioning
Being repetitive and cannot leverage the power of Automated
Deployments and CI. 5

6. 6
“Oh! But it works
on my laptop!”

7. 7

8. But now with
Software Defined
Environments
Or
Environments on
Demand
Or
Phoenix
environments 8

9. “ In One Click
Devs, QAs and Sys
Admins can get the
Environment they
need! ”
9

10. Define
SDE
Orchestrates Software-Defined Compute,
Networking, Storage, Security and such to
provide a smart infrastructure that is aware
of resources needed by the application
and is adaptive and responsive to the
workloads dues to fluctuating business
demand while also being simple to use.
10

11. Demo
11

12. 12
Provisioning
infrastructure resources
Installing Operating
System
on both
Creating VMs
to be web server
to be Database Server
Configures the server
Ready the App for
deployment
Fetch repo
build
Run Unit
& Functional tests
deploy
Smoke test

13. How can Environments on Demand help!
Self Provisioning, empowers the Devs and QAs
to bring up self provision environments, cutting delay due to dependency and
bureaucracy!
Push-button deployments to get
environments easily and run
automated tests, any version of the app to any environment. Helping in getting
faster feedback.
13

14. This is how easy it should be to define an environment
machines:
db:
mysql_5.0.27
www:
ruby19
passenger
nginx
network:
domain: qa1.example.com
14
man readable
&
asy to define

15. This is how easy it should be to define an environment
machines:
db:
mysql_5.0.28
www:
ruby19
passenger
nginx
network:
domain: qa1.example.com
15
man readable
&
asy to define

16. Other advantages
Automating orchestration
vastly reduces the possibility of human error, and makes it possible to scale
far beyond what people could do manually.
Reducing the cost
of cloud ownership by sharing resources and time to market drastically and
reuse your existing hardware resources.
Increase the quality of
service
16

17. Mitigating the risks by providing
Consistent Environments
throughout the software dev. process from Dev’s laptop up to
Production
Phoenix Environments
Providing resilient, fault tolerant Environments which can bring up
your infrastructure in one click
17

18. Infrastructure as code – IMMUTABLE!
• Extend the advantages
of version
controlfrom your app to
Infrastructure.
•Auto deployment
will cut the repetitive and manual process of configuring
all infrastructure resources.
• Get a unified view simplifying the18
“Welcome
to the
age of
Software
Defined
Economy.”

19. Do we need to throw
away what we have!
Suppose we already have our cloud, like
using Xen, VMWare and such…
19

20. Using OpenStack you
would have the
advantages of both
worlds!
It is interoperable with existing private
cloud providers like VMWare, Xen and such.
20

22. What else can TW help
• Cloud Ready your App to be hosted on
either private, public or hybrid cloud
• Auto scaling
• Fault Tolerant
22

23. THANK YOU
For questions or
suggestions:
meghdoot@thoughtworks.co
m
For questions or
suggestions:
meghdoot@thoughtworks.co
m