SDLC for Pivotal Platform powered by Spring Initializr and Concourse
0 likes437 views
The document presents an overview of the Software Development Life Cycle (SDLC) for the Pivotal platform using Spring Initializr, Concourse, and Spinnaker, emphasizing the need for automation and efficiency in managing microservices. It discusses the challenges of handling numerous microservices in a complex environment and proposes a cohesive strategy to unify development, monitoring, and deployment through various tools and automation techniques. Key components and processes are highlighted, including API usage for service setup, template inheritance, and extensions to Spring Initializr for customized applications.
![Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Spinnaker provides template inheritance
13
spin application save --application-name myApp --owner-email theemail@company.com --cloud-providers "cloudfoundry"
spin pipeline save --file thepipeline.json
{
"schema": "v2",
"application": "{{name}}",
"name": "Deploy Red/Black",
"template": {
"artifactAccount": "front50ArtifactCredentials",
"reference": "spinnaker://RedBlackDeplTemplate",
"type": "front50/pipelineTemplate",
},
"variables": {
"waitTime": 4
},
"exclude": [],
…
{
"schema": "v2",
"application": "myApp",
"name": "Deploy Red/Black",
"template": {
"artifactAccount": "front50ArtifactCredentials",
"reference": "spinnaker://RedBlackDeplTemplate",
"type": "front50/pipelineTemplate",
},
"variables": {
"waitTime": 4
},
"exclude": [],
…
Before Result](https://image.slidesharecdn.com/sdlcforpivotalplatformjpa1-191018154148/85/SDLC-for-Pivotal-Platform-powered-by-Spring-Initializr-and-Concourse-13-320.jpg)
SDLC for Pivotal Platform powered by Spring Initializr and Concourse
- 1. SDLC for Pivotal Platform, Powered by Spring Initializr, Concourse and Spinnaker October 7–10, 2019 Austin Convention Center
- 2. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Developer’s Haiku "here is my source code run it on the cloud for me i do not care how" However, someone must care…….namely the platform SRE team. 2
- 3. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal SRE Team Haiku "here are my servers go make them a cloud foundry i do not care how" However, someone must care…….namely the CF engineering team! 3
- 4. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Spring Boot SDLC Haiku “Initialzer complexity disappears i do not care how” However, someone must care…….namely the development team! 4
- 5. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Microservices in an enterprise landscape Issue: Amount of microservices, multi-cloud, redundant code, manual setup Reality: In a complex environment we needed to: • Unifying development • Logging, monitoring, metrics, configuration, code structure • Find a way to setup new microservices fast in our SDLC • Repository, pipelines, monitoring, logging, etc. • Apply changes in our SDLC fast to the existing services 5 Automation is key in a world of microservices
- 6. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ SDLC components 6 Microservice Code Repo Build pipeline Artifact Repo Security Scan Code Quality Test exec. Deployment Runtime env. Log dashboard Monitoring / alerting Document CollaborationMetrics
- 7. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Automation requires APIs To automate the setup of a new service in all SDLC components, the components need to provide an API or other way to configure it • REST and/or Web-service APIs • Command line interfaces (CLI) • The capability to define the configuration in a text format (YAML for example) Provide a templating mechanism would be great 7
- 8. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ The perfect fit Pivotal platform, Concourse and Spinnaker provide all we need for an automated setup • Pivotal platform - platform as a service to manage containers and / or micro services • cf CLI - cf push myApp.yml • Manifest files with variable substitution support • Concourse - build pipeline tool • fly CLI - fly -t myTeam sp -p myPipeline.yml • Pipelines defined in yaml format with variable substitution support • Spinnaker - Continuous delivery platform • spin CLI - spin pipeline save --file myApp.json • Template inheritance 8
- 9. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Generate vs. Inject Generating pipelines, job descriptions or manifest files should be avoided. Instead, focus on injecting dynamic values into standard pipeline/processes • Jobs, pipelines, etc. will continuously be improved. You do not want to regenerate them all the time • Your infrastructure landscape might be complex • Different environments (dev, qa, customer test, performance, prod, etc.) • Multiple data centers (primary, disaster recovery) • Multiple Pivotal platform foundations in each data center • Multiple regions (US, Europe, Asia, etc.) 9 Always generate only, what is service specific
- 10. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Handling permutations? Define your configuration and then create files per permutation. An example: 10 Dev Env Qa Prod Foundation Primary nonprod DR prod Primary prod Region US Europe ASIA Template MyApp config for Prod primary datacenter in Europe MyApp App
- 11. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Pivotal Platform manifest file example 11 Env Foundation host: prim-host.abc.com Region region: europename: my-app App env: prod - - - Applications: - name: ((name)) - memory: 2G - routes: - route: ((name))-((env)).((region))-((host)) - - - Applications: - name: my-app - memory: 2G - routes: - route: my-app-prod.europe-prim-host.abc.com Template Result cf push --vars-file app.yml --vars-file prod.yml --vars-file primary.yml --vars-file europe.yml -f template.yml
- 12. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Concourse example 12 resources: - name: cf-performance type: cf source: api: https://api.system.((region))-((host)) username: ((cf_username)) password: ((cf_password)) organization: ((org)) Org Foundation host: prim-np.abc.com Region region: europename: my-app App org: MY_ORG fly -t np_us set-pipeline -p perf_my-app -c perf-pipeline.yml -l perf.yml -l team.yml -l primNonProd.yml … fly -t np_us unpause-pipeline -p perf_my-app resources: - name: cf-performance type: cf source: api: https://api.system.europe-prim-np.abc.com username: my_deployment_user password: the_secret organization: MY_ORG env: perf Env
- 13. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Spinnaker provides template inheritance 13 spin application save --application-name myApp --owner-email [email protected] --cloud-providers "cloudfoundry" spin pipeline save --file thepipeline.json { "schema": "v2", "application": "{{name}}", "name": "Deploy Red/Black", "template": { "artifactAccount": "front50ArtifactCredentials", "reference": "spinnaker://RedBlackDeplTemplate", "type": "front50/pipelineTemplate", }, "variables": { "waitTime": 4 }, "exclude": [], … { "schema": "v2", "application": "myApp", "name": "Deploy Red/Black", "template": { "artifactAccount": "front50ArtifactCredentials", "reference": "spinnaker://RedBlackDeplTemplate", "type": "front50/pipelineTemplate", }, "variables": { "waitTime": 4 }, "exclude": [], … Before Result
- 14. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Extending Spring Initializr 14 Spring Initializr supports generation of standardized Spring Boot applications out of the box. However, it can be also easily extended to create customized applications: Demo will show how to: • Add your company libraries • Create your own files (e.g. service specific variable files like app.yml) • Extend the UI to add your own values
- 15. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Initializr related projects https://github.com/spring-io/ start.spring.io start-site https://github.com/spring-io/initializr start-client Web project Generator (do not touch)
- 16. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Extending Spring Initializr 16 DEMO
- 17. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Adding fields to the Initializr Controller ModelAttribute UI applicationId start-client Start-site WebProjectRequest Initializr Request parameter to bean mapping Generator ProjectDescription Project request to description converter Spring boot app