DevOps for accuracy, repeatability, and productivity at UC Davis Schools of Health.
DevOps means different things to different groups, at UC Davis we have utilized Docker, Jenkins, ELK, and Ansible for automated deploys and will be rolling out continuous integration and continuous deploy (CI/CD). We have learned so far that the “how” of DevOps is far more important than the “what”.
UC Davis Schools of Health develops and supports software in-house that results in over 120 different deployable applications (i.e. Applications, APIs, etc.). Across the different development environments, this represented a large amount of work with no guarantee (?) of repeatability. The application environment software was inconsistently versioned, out-of-date, and inconsistently configured.
The DevOps team defined the goals for the first round of improvements using some of the foundations of DevOps. Configurations are managed and stored in the same manner as applications themselves. Logs are streamed to a useful repository. Services are strictly bound to a port. Application environments are built from the ground up on demand and completely removed when upgraded or no longer needed (disposability).
My presentation will focus on the collaboration process with the developer group, the technology stack, configuration management and the technology as a commodity. I will also demonstrate some automationprocesses.
Attendees who are familiar with software deployment and lifecycle will get the most benefit from this session.
Software Installation Expectation
Chrome web browser.
Session Skill Level
Developing and Sustaining Health Technology