Your own kubernetes castle

This was a session Brian Verkley and I delivered in Las Vegas for EMC World 2016 called 12 Factor App FTW ! In this presentation we talked to each of the 12 factors and how it can relate to the operations side of the house.

This document discusses infrastructure as code and provides examples using tools like Chef, Vagrant, and Jenkins. It summarizes building a Jenkins server from source control using Chef recipes to install Java, add users, and install packages to set up the service. It emphasizes best practices like version control, testing, and treating infrastructure like code.

Avishkar Nikale who is Senior Technical Architect at LTI took a Session on "DevSecOps with GitLab" at Global Testing Retreat #ATAGTR2019 Please refer our following post for session details: https://atablogs.agiletestingalliance.org/2019/12/06/global-testing-retreat-atagtr2019-welcomes-avishkar-nikale-as-our-esteemed-speaker/

The document discusses DevOps and how Puppet can be used to automate infrastructure provisioning and application deployments. It provides an overview of the Puppet architecture and workflow where developers check code into a repository, it is built, tested and then deployed to Azure. Puppet is used to configure and manage virtual machines and applications on Azure. It also lists several Linux distributions and common applications that are supported by Puppet and Microsoft.

Soon after Java burst into the world in the 90s it started to gatecrash the parties of its enterprise computing seniors, whose initial amused response was -- You're Not On The List, You're Not Coming In. But EJBs turned heads in the 20th Century and when the Java Enterprise platform emerged, it started getting more invites until it was the party. Now Java EE is grown up with its own kids - EE7 is already two years old. How is it and the platform doing? The party is now in the cloud and the guest list includes many different language technologies and fast-moving open-source innovations. Is Enterprise Java still relevant here? And if it is, what does it need to keep doing or what does it need to change to stay on the VIP list?

Delivering value to the business faster thanks to Continuous Delivery and DevOps is the new mantra of IT organizations. In this webinar, CloudBees will discuss how Jenkins, the most popular open source Continuous Integration tool, allows DevOps teams to implement Continuous Delivery. You will learn how to: * Orchestrate Continuous Delivery pipelines with the new workflow feature, * Scale Jenkins horizontally in your organization using Jenkins Operations Center by CloudBees, * Implement end to end traceability with Jenkins and Puppet and Chef. http://devops.com/news/ci-and-cd-across-enterprise-jenkins/ https://github.com/CloudBees-community/vagrant-puppet-petclinic

SpringOne 2021 Session Title: Spring Data JDBC: Beyond the Obvious Speaker: Jens Schauder, Staff Engineer at VMware

The document provides a 6 step approach to transforming enterprise applications: 1. Re-organizing to DevOps; 2. Implementing self-service, on-demand infrastructure; 3. Automating deployments using tools like Puppet, Chef, and Kubernetes; 4. Establishing continuous integration and deployment pipelines; 5. Adopting advanced deployment techniques like blue-green deployments; 6. Moving to a microservices architecture.

Many Java-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can't be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help. Join me to learn about: - The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop - An exploration of how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine - The benefits of getting a "hot reload" fast feedback loop between applications being developed locally and apps running in the remote environment - A tour of Telepresence, from the sidecar proxy deployed into the remote K8s cluster to the CLI - An overview of using "preview URLs" and header-based routing for the sharing, collaboration, and isolation of changes you are making on your local copy of an intercepted service

At GOTO Amsterdam in 2019 I presented how to create an effective cloud native developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I'll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software. In this talk, you will: - Learn why the core tenets of continuous delivery -- speed and safety -- must be considered in all parts of the cloud native SDLC - Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis - Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger) - Explore the importance of cultivating an effective cloud platform and associated team of experts - Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes

The document describes a case study of CollabNet implementing a CI-as-a-Service solution for a large financial services company with over 4000 users across 100 teams developing over 150 applications using multiple technologies. The solution involved provisioning Jenkins servers on demand using Lab Management, integrating tools like TeamForge, Subversion, Nexus and SonarQube on a common platform to provide standardized CI tooling and processes managed by a dedicated build engineer. This helped establish a collaborative development culture, improve productivity and reduce costs.

A short timelined description of DevOps at Morpho made for ParisDevOps meetup of 2nd of December 2014