Download as PDF, PPTX
Uploaded byMichael Kennedy
Application Deployment at UC Riverside
Mike Kennedy, an enterprise architect at UC Riverside since 1995, discusses the modernization of application deployment processes using tools like Grails, GitLab, and Jenkins to improve control, logging, and collaboration between developers and DevOps. The presentation highlights key projects, current strengths and weaknesses of processes, and the importance of automation and communication in the application delivery cycle. Early outcomes indicate quick buy-in and positive feedback from both developers and DevOps teams, with all tools employed being free and open source.
More Related Content
![[Webinar] The Frog And The Butler: CI Pipelines For Modern DevOps](https://cdn.slidesharecdn.com/ss_thumbnails/jenkinsartifactory-170830053058-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Application Deployment at UC Riverside
Application Deployment at UC Riverside
- 1. Developer Toolchain at UCRiverside Mike Kennedy Enterprise Architect
- 2. Developer Toolchain at UCRiverside Mike Kennedy Enterprise Architect Application Deployment
- 3.
- 4. About Me • MikeKennedy
- 5. About Me • MikeKennedy • At UC Riverside since 1995 (Student then Staff)
- 6. About Me • MikeKennedy • At UC Riverside since 1995 (Student then Staff) • Enterprise Architect
- 7. About Me • MikeKennedy • At UC Riverside since 1995 (Student then Staff) • Enterprise Architect • Interests lie in web services, application architecture, integration, middleware
- 8. About Me • MikeKennedy • At UC Riverside since 1995 (Student then Staff) • Enterprise Architect • Interests lie in web services, application architecture, integration, middleware • Major projects - New SIS (Banner), UCPath, ServiceNow, New development environment, ESB
- 9.
- 10. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS
- 11. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS
- 12. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS
- 13. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS • Began effort to modernize: .NET vs. Java
- 14. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS • Began effort to modernize: .NET vs. Java • Ultimately settled on Grails (Groovy/JVM based framework)
- 15. Talk Background • Upuntil recently, applications developed using PL/SQL Web Toolkit and Oracle IAS • Began effort to modernize: .NET vs. Java • Ultimately settled on Grails (Groovy/JVM based framework) • Opportunity: Improve on application delivery processes and architecture (my focus today)
- 16.
- 17. Grails Grails Application Tomcat AppServer Java Virtual Machine (JVM) Operating System F5 app-prd-1.cis.ucr.edu app-prd-2.cis.ucr.edu APPPROD User 1 Tomcat Session Replication User 2 DatabaseConnection DatabaseConnection HTTP HTTP ProxyHTTP ProxyHTTP Puppet Server Deployment Server Configure Configure Configure Source Control Management Server (Git) ESB WebServiceCall Public Network Private Network Deploy Pull Nagios (Monitoring) Graphite (Performance Stats) Dev CIS CommitsCode Starts Deployments W rites Scripts Writes Modules W rites M onitoring Checks Monitor Collaboration Grails Application and Support Architecture https://app.ucr.edu/
- 18.
- 19. Process Improvement • Whatare the strengths/weaknesses of current process?
- 20. Process Improvement • Whatare the strengths/weaknesses of current process? • What is the target state?
- 21. Process Improvement • Whatare the strengths/weaknesses of current process? • What is the target state? • Identify technologies/tools that could help
- 22.
- 23. Legacy Deployment Process •Developer writes code and deploys
- 24. Legacy Deployment Process •Developer writes code and deploys • Developer has complete control
- 25. Legacy Deployment Process •Developer writes code and deploys • Developer has complete control • Little to no logging
- 26. Legacy Deployment Process •Developer writes code and deploys • Developer has complete control • Little to no logging • Potential issues with coordination
- 27. Legacy Deployment Process •Developer writes code and deploys • Developer has complete control • Little to no logging • Potential issues with coordination • Infrastructure (Dev Ops) not in the loop
- 28.
- 29. New Deployment Process Requirements •Developers must be empowered to work asynchronously from Dev Ops - BUY IN!
- 30. New Deployment Process Requirements •Developers must be empowered to work asynchronously from Dev Ops - BUY IN! • Must be logged and auditable
- 31. New Deployment Process Requirements •Developers must be empowered to work asynchronously from Dev Ops - BUY IN! • Must be logged and auditable • Automation! Automation! Automation!
- 32. New Deployment Process Requirements •Developers must be empowered to work asynchronously from Dev Ops - BUY IN! • Must be logged and auditable • Automation! Automation! Automation! • Implicit notification of events
- 33. New Deployment Process Requirements •Developers must be empowered to work asynchronously from Dev Ops - BUY IN! • Must be logged and auditable • Automation! Automation! Automation! • Implicit notification of events • Close collaboration between developers and dev ops teams
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. Develop • Gitlab • Gitserver (Source Control Management)
- 40. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like”
- 41. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End
- 42. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End • Code reviews
- 43. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End • Code reviews • Merge requests
- 44. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End • Code reviews • Merge requests • Open source
- 45. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End • Code reviews • Merge requests • Open source • On premise or cloud
- 46. Develop • Gitlab • Gitserver (Source Control Management) • Very “Github-like” • Web Front End • Code reviews • Merge requests • Open source • On premise or cloud
- 47.
- 48.
- 49.
- 50. Develop • Slack • Collaborationtool • Chat
- 51. Develop • Slack • Collaborationtool • Chat • Integrations galore!
- 52. Develop • Slack • Collaborationtool • Chat • Integrations galore! • Free w/ special EDU pricing for advanced features
- 53. Develop • Slack • Collaborationtool • Chat • Integrations galore! • Free w/ special EDU pricing for advanced features
- 54. Develop Developer Git Server(SCM) Collaboration Developer Developer
- 55. Develop Developer Git Server(SCM) Collaboration Push Developer Developer
- 56. Develop Developer Git Server(SCM) Collaboration Push Notify Developer Developer Receive
- 57. Develop Developer Git Server(SCM) Collaboration Push Developer Developer
- 58. Develop Developer Git Server(SCM) Collaboration Push Developer Developer Pull
- 59.
- 60.
- 61. Build • Gitlab, Slack •Jenkins
- 62. Build • Gitlab, Slack •Jenkins • Continuous Integration Server (CI) - Builds
- 63. Build • Gitlab, Slack •Jenkins • Continuous Integration Server (CI) - Builds • Can be triggered by branch push
- 64. Build • Gitlab, Slack •Jenkins • Continuous Integration Server (CI) - Builds • Can be triggered by branch push • We use special branch names - release/x.y.z
- 65.
- 66.
- 67.
- 68. Build • Gitlab, Slack •Nexus • Maven artifact repository
- 69. Build • Gitlab, Slack •Nexus • Maven artifact repository • Jenkins publishes built wars here
- 70. Build • Gitlab, Slack •Nexus • Maven artifact repository • Jenkins publishes built wars here • Can contain other artifacts (jars, zips)
- 71. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration
- 72. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovy
- 73. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovyPush
- 74. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovyPush NotifyReceive
- 75. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovyPush
- 76. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovyPush Build Webhook
- 77. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration file.groovy Push Pull
- 78. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration Push Pull Build WAR
- 79. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration Push Pull Notify Build WAR Receive
- 80. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration Push Pull Build WAR
- 81. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration Push Pull Publish Build WAR
- 82. Build Developer Git Server (SCM) CI(Build) Server Artifact Repository (Maven) Collaboration Push Pull Publish Build WAR
- 83.
- 84.
- 85. Deploy • Slack, Nexus •Rundeck
- 86. Deploy • Slack, Nexus •Rundeck • Job scheduler and runbook automation
- 87. Deploy • Slack, Nexus •Rundeck • Job scheduler and runbook automation • Jobs can be prebuilt and shared
- 88. Deploy • Slack, Nexus •Rundeck • Job scheduler and runbook automation • Jobs can be prebuilt and shared • Auditable
- 89. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N
- 90. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N Run
- 91. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N Run Execute
- 92. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N Run Execute Download WAR
- 93. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N Run Execute
- 94. App Server 2 AppServer 1 Deploy Developer Artifact Repository (Maven) Collaboration Job Scheduler/Deployment Server App Server N Run Execute Notify Receive
- 95.
- 96.
- 97.
- 98. Monitor • Slack • Nagios •Ping test
- 99. Monitor • Slack • Nagios •Ping test • Application availability
- 100. Monitor • Slack • Nagios •Ping test • Application availability
- 101. Monitor • Slack • Nagios •Ping test • Application availability • Graphite
- 102. Monitor • Slack • Nagios •Ping test • Application availability • Graphite • Application Metrics
- 103. Monitor • Slack • Nagios •Ping test • Application availability • Graphite • Application Metrics • JVM Performance
- 104.
- 105.
- 106.
- 107. Monitor • Logging • ELKstack • Log Stash (Log Collection)
- 108. Monitor • Logging • ELKstack • Log Stash (Log Collection) • Elastic Search (Log Indexing, Searching)
- 109. Monitor • Logging • ELKstack • Log Stash (Log Collection) • Elastic Search (Log Indexing, Searching) • Kibana (Visualization)
- 110. Monitor • Logging • ELKstack • Log Stash (Log Collection) • Elastic Search (Log Indexing, Searching) • Kibana (Visualization) • Splunk Killer?
- 111. Monitor • Logging • ELKstack • Log Stash (Log Collection) • Elastic Search (Log Indexing, Searching) • Kibana (Visualization) • Splunk Killer? • Check out Nick Turley’s talk: “Security Data Analytics Platform” tomorrow at 9am!
- 112. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Graphite
- 113. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Log Messages Graphite
- 114. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Log Messages View Graphite
- 115. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics View Graphite
- 116. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics View Graphite Monitor
- 117. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Notify Receive Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Receive View Graphite Monitor
- 118. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Notify Receive Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Receive View Graphite
- 119. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Notify Receive Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Receive View Graphite Metrics
- 120. Monitor App Server 2 AppServer 1 Developer Collaboration App Server N Notify Receive Dev Ops Log Collection and Visualization (ELK) Monitoring Performance Metrics Receive View GraphiteView Metrics
- 121.
- 122.
- 123.
- 124. Outcomes • Still early •Buy-in was quick
- 125. Outcomes • Still early •Buy-in was quick • Good feedback from developers and dev ops teams
- 126. Outcomes • Still early •Buy-in was quick • Good feedback from developers and dev ops teams • Many of the tools deployed used for non- development projects (New SIS)
- 127. Outcomes • Still early •Buy-in was quick • Good feedback from developers and dev ops teams • Many of the tools deployed used for non- development projects (New SIS) • All tools deployed are free and open source!
- 128.