The document discusses automating project initiation to enable rapid deployment of functioning software. It highlights challenges such as environment setup and manual work that delay development, proposing solutions like automating these setups. The authors encourage a DevOps culture and open-source efforts while emphasizing the importance of metrics and standardization in modernizing processes.

1. Automate Project Initiation
to Deploy in Minutes
By Shawn Sherwood and Ted Tollefson
@shawn_sherwood and @tedtollefson
1

2. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
2

3. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Elevator Pitch
Goal
Deliver functioning software as fast as possible.
Challenge
The setup of environments, tooling, and code delays the start of development (lots
of tickets and manual, error-prone work).
Solution
Automate the setup of environments, tooling and code.
3

4. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Quick Survey
How long does it take you to get a new application into production?
- > 1 month
- 1 month - 2 weeks
- 2 weeks - 2 days
- Less?
4

5. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Demo
Provision a new project with
• Code
• Git repo
• CI / CD pipeline
• Environment(s)
5

6. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Design
• Blueprints
• New project initiation
• Existing project “retrofit”
• Day 2 provisioning
• Plugins
• PF4J (https://github.com/decebals/pf4j)
• Input / output specs
• Lifecycle events
• Shared context
6

7. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Organizational Journey
• Drive a DevOps culture
• Standardize existing processes
• Rapidly modernize
7

8. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
The take away
• We are seeking to open source Kick Start
• Don’t wait - start your journey today
• Collect metrics
• Self-service automation via APIs
• Define standard architectures/templates
• Contact us
8

9. Unless otherwise indicated, these slides are © 2013 -2016 Piv otal Software, Inc. and licensed under a
Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Possibilities
Additional blueprint ideas
• GCP or Azure provisioning
• Hadoop
• Machine Learning
• Serverless functions
• Data Warehousing
9

10. Learn More. Stay Connected.
@tedtollefson
@shawn_sherwood
10
#springone@s1p