This document discusses zero-configuration provisioning of Kubernetes clusters on unmanaged infrastructure. It describes using immutable bootstrapping to provision operating systems and install Docker and Kubernetes (using Kubeadm) across nodes without requiring centralized orchestration or SSH access. The document also discusses potential future directions for the Kubernetes community regarding node admission controls and dynamic Kubelet configuration to further reduce external configuration requirements during cluster provisioning.
What is Digital Rebar Provision (and how RackN extends)?rhirschfeld
Walks through how Digital Rebar Provision rethinks bare metal automation beyond simple O/S install into an integrated workflow system for building data center underlay.
INCLUDES VIDEO OF PRESO
The document discusses infrastructure as code and related concepts. It introduces just enough operating systems using Vagrant and VeeWee to package applications. Just enough image building is covered using VeeWee to create minimal OS images from source configurations. Just enough infrastructure code is explained through configuration management tools like Chef Solo, Chef Server, and Crowbar that allow infrastructure to be coded and version controlled. The presentation aims to provide feedback to further the discussion on DevOps approaches.
This document discusses Relay, a new project that aims to provide a complete solution for continuously deploying applications and infrastructure. Relay will orchestrate actions across existing tools and services by listening to cloud events and triggers from services. It will use a taxonomy of reusable, modular workflow steps that can be combined to build workflows as code in YAML. The document provides examples of step types like trigger steps, action steps, and query steps. It also outlines Relay's integration ecosystem and upcoming release timeline.
This document discusses automating the application lifecycle using infrastructure as code principles. It demonstrates building infrastructure like VPCs and databases automatically with CloudFormation templates. It then shows deploying application components like load balancers and servers from templates. It discusses updating applications by building new server images from code changes rather than modifying existing servers. This allows deploying updates instantly by replacing server instances. The talk concludes that automating infrastructure and deployments in this way allows integrating new applications or changes much faster.
In this webinar, Alex Casalboni will overview the main FaaS concepts and best practices (Function as a Service), explore the open-source FaaS options and discuss pros and cons of deploying and managing your own serverless platform on Kubernetes.
Continuous Integration with Cloud Foundry Concourse and Docker on OpenPOWERIndrajit Poddar
This document discusses continuous integration (CI) for open source software on OpenPOWER systems. It provides background on CI, OpenPOWER systems, and the Cloud Foundry platform. It then describes using the Concourse CI tool to continuously build a Concourse project from a GitHub repository. Key steps involve deploying OpenStack, setting up a Docker registry, installing BOSH and Concourse, defining a Concourse pipeline, and updating the pipeline to demonstrate the CI process in action. The document emphasizes the importance of CI for open source projects and how it benefits development on OpenPOWER systems.
Cloud providers like Amazon or Goggle have great user experience to create and manage PaaS and IaaS services. But is it possible to reproduce same experience and flexibility locally, in on premise datacenter? This talk describes success story of creation private cloud based on DC/OS cluster. It is used to host and share different services like hadoop or kafka for development teams, dynamically manage services and resource pools with GKE integration.
This document discusses zero-configuration provisioning of Kubernetes clusters on unmanaged infrastructure. It describes using immutable bootstrapping to provision operating systems and install Docker and Kubernetes (using Kubeadm) across nodes without requiring centralized orchestration or SSH access. The document also discusses potential future directions for the Kubernetes community regarding node admission controls and dynamic Kubelet configuration to further reduce external configuration requirements during cluster provisioning.
What is Digital Rebar Provision (and how RackN extends)?rhirschfeld
Walks through how Digital Rebar Provision rethinks bare metal automation beyond simple O/S install into an integrated workflow system for building data center underlay.
INCLUDES VIDEO OF PRESO
The document discusses infrastructure as code and related concepts. It introduces just enough operating systems using Vagrant and VeeWee to package applications. Just enough image building is covered using VeeWee to create minimal OS images from source configurations. Just enough infrastructure code is explained through configuration management tools like Chef Solo, Chef Server, and Crowbar that allow infrastructure to be coded and version controlled. The presentation aims to provide feedback to further the discussion on DevOps approaches.
This document discusses Relay, a new project that aims to provide a complete solution for continuously deploying applications and infrastructure. Relay will orchestrate actions across existing tools and services by listening to cloud events and triggers from services. It will use a taxonomy of reusable, modular workflow steps that can be combined to build workflows as code in YAML. The document provides examples of step types like trigger steps, action steps, and query steps. It also outlines Relay's integration ecosystem and upcoming release timeline.
This document discusses automating the application lifecycle using infrastructure as code principles. It demonstrates building infrastructure like VPCs and databases automatically with CloudFormation templates. It then shows deploying application components like load balancers and servers from templates. It discusses updating applications by building new server images from code changes rather than modifying existing servers. This allows deploying updates instantly by replacing server instances. The talk concludes that automating infrastructure and deployments in this way allows integrating new applications or changes much faster.
In this webinar, Alex Casalboni will overview the main FaaS concepts and best practices (Function as a Service), explore the open-source FaaS options and discuss pros and cons of deploying and managing your own serverless platform on Kubernetes.
Continuous Integration with Cloud Foundry Concourse and Docker on OpenPOWERIndrajit Poddar
This document discusses continuous integration (CI) for open source software on OpenPOWER systems. It provides background on CI, OpenPOWER systems, and the Cloud Foundry platform. It then describes using the Concourse CI tool to continuously build a Concourse project from a GitHub repository. Key steps involve deploying OpenStack, setting up a Docker registry, installing BOSH and Concourse, defining a Concourse pipeline, and updating the pipeline to demonstrate the CI process in action. The document emphasizes the importance of CI for open source projects and how it benefits development on OpenPOWER systems.
Cloud providers like Amazon or Goggle have great user experience to create and manage PaaS and IaaS services. But is it possible to reproduce same experience and flexibility locally, in on premise datacenter? This talk describes success story of creation private cloud based on DC/OS cluster. It is used to host and share different services like hadoop or kafka for development teams, dynamically manage services and resource pools with GKE integration.
This video is part of our talk about BOSH held by the CEO of anynines - Julian Fischer (Twitter: @fischerjulian) - at the SUSECON 2016 in Washington, D.C..
Orchestration tool roundup kubernetes vs. docker vs. heat vs. terra form vs...Nati Shalom
Video recording: https://www.youtube.com/watch?v=tGlIgUeoGz8
It’s no news that containers represent a portable unit of deployment, and OpenStack has proven an ideal environment for running container workloads. However, where it usually becomes more complex is that many times an application is often built out of multiple containers. What’s more, setting up a cluster of container images can be fairly cumbersome because you need to make one container aware of another and expose intimate details that are required for them to communicate which is not trivial especially if they’re not on the same host.
These scenarios have instigated the demand for some kind of orchestrator. The list of container orchestrators is growing fairly fast. This session will compare the different orchestation projects out there - from Heat to Kubernetes to TOSCA - and help you choose the right tool for the job.
Session link from teh summit: https://openstacksummitmay2015vancouver.sched.org/event/abd484e0dedcb9774edda1548ad47518#.VV5eh5NViko
Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deploym...VMware Tanzu
Speakers: Alexander Lomov and Alan Moran, Altoros
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Achieving Continuous Delivery: An Automation Storyjimi-c
Continuos Deployment is the act of deploying software constantly. The idea is if "release early, release often" is good, releasing very often is better. It's not trivial. Automation is part of the battle, and testing is another. Learn to use tools like Jenkins and Ansible to move from deploying software once a month to 15 times every hour, and why you'll want to.
Presented at PyCon 2015 in Montreal
This document discusses autoscaling in Kubernetes. It describes horizontal and vertical autoscaling, and how Kubernetes can autoscale nodes and pods. For nodes, it proposes using Google Compute Engine's managed instance groups and cloud autoscaler to automatically scale the number of nodes based on resource utilization. For pods, it discusses using an autoscaler controller to scale the replica counts of replication controllers based on metrics from cAdvisor or Google Cloud Monitoring. Issues addressed include rebalancing pods and handling autoscaling during rolling updates.
The document discusses challenges of deploying Kubernetes on-premise, including how load balancers are provisioned without cloud providers, using Nginx and Haproxy for load balancing on bare metal. It also covers how persistent volumes are provisioned with CSI drivers like Ember CSI to interface with storage backends, and tools for deploying and managing on-premise Kubernetes clusters like RKE.
The document discusses using OpenStack Ironic to provision bare metal servers. Key points include:
- Ironic allows provisioning of physical servers alongside virtual instances managed by Nova.
- Commands are provided to enroll bare metal nodes in Ironic, create ports, validate and power on nodes, and deploy an image using Nova.
- Tips discuss issues with large-scale deployments, PXE boot, and driver/library conflicts.
Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!smalltown
This document summarizes a talk about building, shipping, and running applications in production using containers on AWS. It discusses migrating an existing service from an on-premise data center to AWS, refactoring the application into microservices and containerizing it using Docker. It then covers setting up a Kubernetes cluster on CoreOS to orchestrate the containers across AWS, addressing challenges like application state, updates and monitoring. Terraform is presented as a way to define infrastructure as code and provision AWS resources. Logging, metrics collection and monitoring the Kubernetes cluster are also discussed.
How to Achieve Canary Deployment on KubernetesHanLing Shen
This document provides an overview of how to achieve canary deployments on Kubernetes. It begins with background on AWS Elastic Beanstalk and Kubernetes. It then explains blue/green deployments and canary deployments. The remainder of the document demonstrates how to set up canary deployments on Kubernetes using multiple deployments, services, and labels to route a portion of traffic to a new version. It also discusses tools like Helm and Jenkins that can help automate the canary deployment process.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
Serverless frameworks are changing the way we do computing. In open source container world, Kubernetes is playing a pivotal role in manifesting this. This presentation will go deep into various features of Kubernetes to create serverless functions.
Also includes a comparative study of various serverless frameworks such as Kubeless, Fission and Funktion are available in open source world. Will conclude with an implementation demo and some real world use cases.
Presented in serverless summit 2017: www.inserverless.com
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Wouldn't it be great for a new developer on your team to have their dev environment totally set up on their first day? What about having your CI tests running in the background while you work on new features? What about having the confidence that your dev environment mirrors testing and prod? Containers enable this to become reality, along with other great benefits like keeping dependencies nice and tidy and making packaged code easier to share. Come learn about the ways containers can help you build and ship software easily.
This document discusses Docker best practices and provides an overview of deploying Alfresco Content Services using Docker containers. It begins with 8 best practices for working with Docker, such as packaging a single application per container and building the smallest possible image. It then covers a Docker hands-on lab and demonstrates deploying Alfresco using Docker Compose for local development. The document compares standard installation to using Docker images and discusses the Alfresco Content Services packaging repositories.
Programmability and Automation in Data Center Networks: A talk on Hot Air Bal...Joel W. King
The document discusses a talk given on programmability and automation in data center networks. It covers topics like using Ansible, Jinja templates, and Excel spreadsheets to configure and automate Cisco Nexus and ACI networks. Specific points include using Ansible to deploy ACI fabrics using XML/JSON playbooks, understanding REST APIs and markup languages, and thinking like a programmer to improve network automation. The talk emphasizes that automation tools allow network engineers to focus on applications rather than infrastructure and help adopt a DevOps mindset for networking.
Docker allows building portable software that can run anywhere by packaging an application and its dependencies in a standardized unit called a container. Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes can replicate containers, provide load balancing, coordinate updates between containers, and ensure availability. Defining applications as Kubernetes resources allows them to be deployed and updated easily across a cluster.
2016 - Easing Your Way Into Docker: Lessons From a Journey to Productiondevopsdaysaustin
Presentation by Steve Woodruff
The story of how SpareFoot broke up its monolithic application into micro services, deployed Docker into production, and established a "contract" between Dev and Ops.
This video is part of our talk about BOSH held by the CEO of anynines - Julian Fischer (Twitter: @fischerjulian) - at the SUSECON 2016 in Washington, D.C..
Orchestration tool roundup kubernetes vs. docker vs. heat vs. terra form vs...Nati Shalom
Video recording: https://www.youtube.com/watch?v=tGlIgUeoGz8
It’s no news that containers represent a portable unit of deployment, and OpenStack has proven an ideal environment for running container workloads. However, where it usually becomes more complex is that many times an application is often built out of multiple containers. What’s more, setting up a cluster of container images can be fairly cumbersome because you need to make one container aware of another and expose intimate details that are required for them to communicate which is not trivial especially if they’re not on the same host.
These scenarios have instigated the demand for some kind of orchestrator. The list of container orchestrators is growing fairly fast. This session will compare the different orchestation projects out there - from Heat to Kubernetes to TOSCA - and help you choose the right tool for the job.
Session link from teh summit: https://openstacksummitmay2015vancouver.sched.org/event/abd484e0dedcb9774edda1548ad47518#.VV5eh5NViko
Cloud Foundry Summit 2015: Managing Multiple Cloud with a Single BOSH Deploym...VMware Tanzu
Speakers: Alexander Lomov and Alan Moran, Altoros
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Achieving Continuous Delivery: An Automation Storyjimi-c
Continuos Deployment is the act of deploying software constantly. The idea is if "release early, release often" is good, releasing very often is better. It's not trivial. Automation is part of the battle, and testing is another. Learn to use tools like Jenkins and Ansible to move from deploying software once a month to 15 times every hour, and why you'll want to.
Presented at PyCon 2015 in Montreal
This document discusses autoscaling in Kubernetes. It describes horizontal and vertical autoscaling, and how Kubernetes can autoscale nodes and pods. For nodes, it proposes using Google Compute Engine's managed instance groups and cloud autoscaler to automatically scale the number of nodes based on resource utilization. For pods, it discusses using an autoscaler controller to scale the replica counts of replication controllers based on metrics from cAdvisor or Google Cloud Monitoring. Issues addressed include rebalancing pods and handling autoscaling during rolling updates.
The document discusses challenges of deploying Kubernetes on-premise, including how load balancers are provisioned without cloud providers, using Nginx and Haproxy for load balancing on bare metal. It also covers how persistent volumes are provisioned with CSI drivers like Ember CSI to interface with storage backends, and tools for deploying and managing on-premise Kubernetes clusters like RKE.
The document discusses using OpenStack Ironic to provision bare metal servers. Key points include:
- Ironic allows provisioning of physical servers alongside virtual instances managed by Nova.
- Commands are provided to enroll bare metal nodes in Ironic, create ports, validate and power on nodes, and deploy an image using Nova.
- Tips discuss issues with large-scale deployments, PXE boot, and driver/library conflicts.
Kubernetes Day 2017 - Build, Ship and Run Your APP, Production !!smalltown
This document summarizes a talk about building, shipping, and running applications in production using containers on AWS. It discusses migrating an existing service from an on-premise data center to AWS, refactoring the application into microservices and containerizing it using Docker. It then covers setting up a Kubernetes cluster on CoreOS to orchestrate the containers across AWS, addressing challenges like application state, updates and monitoring. Terraform is presented as a way to define infrastructure as code and provision AWS resources. Logging, metrics collection and monitoring the Kubernetes cluster are also discussed.
How to Achieve Canary Deployment on KubernetesHanLing Shen
This document provides an overview of how to achieve canary deployments on Kubernetes. It begins with background on AWS Elastic Beanstalk and Kubernetes. It then explains blue/green deployments and canary deployments. The remainder of the document demonstrates how to set up canary deployments on Kubernetes using multiple deployments, services, and labels to route a portion of traffic to a new version. It also discusses tools like Helm and Jenkins that can help automate the canary deployment process.
OpenStack Summit Vancouver: Lessons learned on upgradesFrédéric Lepied
Deploying OpenStack in production at any scale, upgrade support is one of the requirements to have a successful deployment. Without upgrade management, adeployment will have bugs and security issues from day 1. Also in longer term, it will miss the latest features that OpenStack offers.
Serverless frameworks are changing the way we do computing. In open source container world, Kubernetes is playing a pivotal role in manifesting this. This presentation will go deep into various features of Kubernetes to create serverless functions.
Also includes a comparative study of various serverless frameworks such as Kubeless, Fission and Funktion are available in open source world. Will conclude with an implementation demo and some real world use cases.
Presented in serverless summit 2017: www.inserverless.com
CAPS: What's best for deploying and managing OpenStack? Chef vs. Ansible vs. ...Daniel Krook
Presentation at the OpenStack Summit in Tokyo, Japan on October 29, 2015.
http://sched.co/49vI
This talk will cover the pros and cons of four different OpenStack deployment mechanisms. Puppet, Chef, Ansible, and Salt for OpenStack all claim to make it much easier to configure and maintain hundreds of OpenStack deployment resources. With the advent of large-scale, highly available OpenStack deployments spread across multiple global regions, the choice of which deployment methodology to use has become more and more relevant.
Beyond the initial day-one deployment, when it comes to the day-two and beyond questions of updating and upgrading existing OpenStack deployments, it becomes all the more important choose the right tool.
Come join the Bluebox and IBM team to discuss the pros and cons of these approaches. We look at each of these four tools in depth, explore their design and function, and determine which scores higher than others to address your particular deployment needs.
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Paul Czarkowski - Cloud Engineer at Blue Box, an IBM company
Daniel Krook - Senior Software Engineer, Cloud and Open Source Technologies, IBM
Wouldn't it be great for a new developer on your team to have their dev environment totally set up on their first day? What about having your CI tests running in the background while you work on new features? What about having the confidence that your dev environment mirrors testing and prod? Containers enable this to become reality, along with other great benefits like keeping dependencies nice and tidy and making packaged code easier to share. Come learn about the ways containers can help you build and ship software easily.
This document discusses Docker best practices and provides an overview of deploying Alfresco Content Services using Docker containers. It begins with 8 best practices for working with Docker, such as packaging a single application per container and building the smallest possible image. It then covers a Docker hands-on lab and demonstrates deploying Alfresco using Docker Compose for local development. The document compares standard installation to using Docker images and discusses the Alfresco Content Services packaging repositories.
Programmability and Automation in Data Center Networks: A talk on Hot Air Bal...Joel W. King
The document discusses a talk given on programmability and automation in data center networks. It covers topics like using Ansible, Jinja templates, and Excel spreadsheets to configure and automate Cisco Nexus and ACI networks. Specific points include using Ansible to deploy ACI fabrics using XML/JSON playbooks, understanding REST APIs and markup languages, and thinking like a programmer to improve network automation. The talk emphasizes that automation tools allow network engineers to focus on applications rather than infrastructure and help adopt a DevOps mindset for networking.
Docker allows building portable software that can run anywhere by packaging an application and its dependencies in a standardized unit called a container. Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. It groups containers that make up an application into logical units for easy management and discovery. Kubernetes can replicate containers, provide load balancing, coordinate updates between containers, and ensure availability. Defining applications as Kubernetes resources allows them to be deployed and updated easily across a cluster.
2016 - Easing Your Way Into Docker: Lessons From a Journey to Productiondevopsdaysaustin
Presentation by Steve Woodruff
The story of how SpareFoot broke up its monolithic application into micro services, deployed Docker into production, and established a "contract" between Dev and Ops.
Rob Hirschfeld talk at the 2017 KubeCon in Austin, TX. In this talk he presents an Immutable Bootstrap demo of Kubernetes using Kubeadm to provision on bare metal. Talk URL http://sched.co/CU8h.
How Percolate uses CFEngine to Manage AWS Stateless InfrastructurePercolate
The document discusses how Percolate uses CFEngine to manage their infrastructure on AWS in a stateless way. Some key points:
1) CFEngine allows Percolate to define infrastructure policies that automatically enforce the desired configuration on servers, providing a documented and scalable approach.
2) By managing all infrastructure as code in Git, and avoiding server state, Percolate's infrastructure is resilient and can be migrated or changed easily.
3) This stateless approach means Percolate avoids backup overhead and can freely launch/replace instances, reducing costs through use of spot instances.
We are providing infrastructure operations for a client using Docker and Ansible specialties. This includes continuous integration and delivery using GitLab for source control and CI/CD pipelines, building Docker images, testing containers, and deploying images to pre-production environments using Ansible, Docker Compose, and the Docker Engine. Future plans include implementing service discovery and smoke testing.
Immutable pattern in IT infrastructure architecture. Building own OS'es and containers to deliver software.
Examples for delivery pipelines. Pros and cons for containers and configuration managers. Docker, Ansible, Chef, AWS CloudFormation, GCE, Terraform.
Composable Infrastructure Talk at Interop ITX 2018RackN
Composable infrastructure allows physical server resources like CPUs, memory, storage and networking to be pooled and allocated dynamically to workloads. This contrasts with traditional static physical servers or virtual servers. Composable infrastructure aims to provide benefits like reduced overprovisioning and improved time to deploy services, but it adds complexity and its use cases are currently limited. While an emerging technology, it does not provide clear advantages over traditional virtual or physical infrastructure for many customers.
This document discusses Docker concepts like images vs containers, base images, Dockerfiles, volumes, and ways of building Docker images. It also covers topics like configuration, discovery, routing, and other Docker tools. Specifically, it explains that images are blueprints for containers, containers are instances of images that are writeable, and images are not after creation. It also discusses choosing a base image, tags/versions, and dissects example Dockerfiles.
The document describes a Bucharest Big Data Meetup occurring on June 5th. The meetup will include two tech talks: one on productionizing machine learning from 7:00-7:40 PM, and another on a technology comparison of databases vs blockchains from 7:40-8:15 PM. The meetup will conclude from 8:15-8:45 PM with pizza and drinks sponsored by Netopia.
Preview of my Immutable Infrastructure presentation. Talks about what it is and why immutable is important. Also covers options on creating immutable deployments.
Preview of Rob Hirschfeld and Shane Gibson's Immutable Infrastructure presentation at Container World 2018. Talks about what it is and why immutable is important. Also covers options on creating immutable deployments.
Preview of Rob Hirschfeld and Shane Gibson's Immutable Infrastructure presentation at Container World 2018. Talks about what it is and why immutable is important. Also covers options on creating immutable deployments.
Puppet Camp Melbourne Nov 2014 - A Build Engineering Team’s Journey of Infras...Peter Leschev
A Build Engineering Team’s Journey of Infrastructure as Code - the challenges that we’ve faced and the practices that we implemented as we went along our journey.
Choosing the Right Framework for Running Docker Containers in ProdJosh Padnick
In this talk, I cover the key elements of running multiple Docker containers per VM, the major frameworks available to assist with this, and when to choose each.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativecornelia davis
The document discusses how Kubo can be used as a gateway to running cloud-native workloads. It outlines different types of workloads like code developed internally which may change frequently or code from third parties. For internally developed code, Kubo allows maintaining existing processes while deploying container images instead of infrastructure. For external code and data-centric workloads, Kubo provides benefits like health management, multi-cloud support, and operating system/Kubernetes upgrades without affecting applications. The document calls developers to run workloads on Cloud Foundry Container Runtime and share experiences.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativeVMware Tanzu
You’re at the Cloud Foundry Summit, which means you are by definition a cloud-native enthusiast. There’s no question that building apps in this architectural style will produce resilient, scalable software in an agile manner, and allow you to operate it far more efficiently than you’ve been able to in the past. But you’ve also got a whole lot of software in your company’s portfolio that isn’t there yet. Do you have to resign yourself to the pains of managing those applications the old way until you can finally refactor them to be cloud-native? Kubo to the rescue.
You can run legacy applications on Kubo without significant refactoring – pure and simple. As an added bonus, it allows you to satisfy the CIO mandate of running containers (check). But it’s far more than that – running those workloads on Kubo offers advantages over running them on traditional virtualized infrastructure. This session covers those advantages –resource consolidation, health management, multi-cloud and more. It will also present the abstractions in Kubernetes, things like pods and stateful sets, that support running legacy workloads in the cloud environments that are far more distributed and changing than they have been in the past. It’s a first step to cloud-native.
[OpenInfra Days Korea 2018] Day 2 - E4 - 딥다이브: immutable Kubernetes architectureOpenStack Korea Community
Linuxkit is a toolkit for building custom minimal and immutable Linux distributions. It allows building Linux distributions from code in a declarative YAML file. The distributions are built as Docker images for security and portability. Linuxkit uses containerization to build the OS, making it modular and customizable. It aims to provide secure defaults without compromising usability through immutable infrastructure principles.
Similar to #SREcon Immutable Infrastructure: rethinking configuration mgmt (20)
Short presentation about how RackN is creating bare metal data center automation for enterprise and edge infrastructure at the most basic level.
Includes a video of Rob giving the presentation
Open Patterns for Day 2 Ops [Gluecon 2017]rhirschfeld
Short presentation talking about how to create shared open best practices for upgrades and ongoing operations. Includes a demo of four upgrade patterns.
This document provides a diagram of the Kubernetes architecture. It shows that Kubernetes is made up of a control plane consisting of components like etcd, API server, and scheduler that run on master nodes. It also shows that Kubernetes manages pods running on worker nodes through kubelets and container managers. The diagram further illustrates add-ons like DNS, monitoring, and networking that are commonly used with Kubernetes.
OpenStack on Kubernetes (BOS Summit / May 2017 update)rhirschfeld
This document discusses using Kubernetes as an underlay platform for OpenStack. Some key points:
1. Kubernetes is becoming more widely used and understood by operators compared to OpenStack. Using Kubernetes as an underlay could improve simplicity, stability, and upgrade processes for OpenStack.
2. There are still many technical challenges to address, such as networking, storage, tooling to manage OpenStack on Kubernetes, and ensuring containers meet Kubernetes' immutable infrastructure requirements.
3. Using Kubernetes as an underlay risks further confusing the messaging around OpenStack by implying Kubernetes is more stable or a replacement target. Clear communication will be important to avoid undermining OpenStack.
The developer rebellion against infrastructurerhirschfeld
My DevOpsDays 2017 Lightening Talk covering why developers don't want to do operations work and are making platforms so they don't have to do it anymore
IBM Interconnect: Think you can Out Innovate Open Sourcerhirschfeld
Joint Presentation with Rob Hirschfeld and Chris Ferris at IBM Interconnect. We cover what makes open source projects succeed and struggle based on our experience with numerous projects. [video pending]
CHECK OUT THE MARCH 17 UPDATE > https://www.slideshare.net/rhirschfeld/joint-openstack-kubernetes-environment-march-17-update/
Presented at the OpenStack summit, this presentation discusses the practical reality & timing of using Kubernetes as an underlay for OpenStack.
Containers, orchestration and security, oh my!rhirschfeld
This document provides an overview of containers, orchestration, and security as it relates to deploying container applications in production using Kubernetes. It discusses what Kubernetes is and its key design elements. It then outlines the reference layers needed for Kubernetes cluster operations including prerequisites, control services, worker nodes, cluster add-ons, and user applications. Finally, it discusses some of the challenges of operating Kubernetes in production including networking complexity, ensuring high availability, and integrating security.
My Gluecon presentation about hybrid infrastructure and container orchestration deployment. I talk about why composability matters and how AWS sets the standard.
OpenStack Preso: DevOps on Hybrid Infrastructurerhirschfeld
Discusses the approach for making hybrid DevOps workable including what obstacles must be overcome. Includes demo of multiple OpenStack clouds & Kubernetes deploy on AWS, Google and OpenStack
Hybrid is normal! Be more like AWS! Decompose DevOps tasks!
Short presentation addressing the challenges of building and operating hybrid infrastructure.
Narration! https://www.youtube.com/watch?v=uorHrvMgwc0
This document lists DefCore Co-Chairs Rob Hirschfeld and Egle Sigler. It then lists several OpenStack APIs under categories like Required, Advisory, Deprecated, Removed, and their status. Key APIs listed include Compute, Object, Auth-token, Compute-servers-metadata from projects like nova and keystone.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Full-RAG: A modern architecture for hyper-personalizationZilliz
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
2. 2
@zehicle #immutable
Involved in Open Ops Software:
Digital Rebar Project
Kubernetes ClusterOps SIG
OpenStack Board
Your Humble Presenter
I’m all about automating infrastructure.
Rob Hirschfeld (aka @zehicle)
Co-Founder of RackN
rob@rackn.com
3. 3
@zehicle #immutable
Storytime! “Self-Bootstrapping Kubernetes”
Kubecon in Nov 2017 we created this demo
Simple “immutable” Idea:
1) In Memory Boot Machines
2) Install Docker
3) Elect Leader
4) Run Kubeadm on Leader
5) Run Kubeadm on Remainder
But….it’s shockingly hard to maintain.
Dependencies breaks the installation
And they are constantly changing.
7. 7
@zehicle #immutable
But… I Infrastructure as Code?!
Sorry. Mutability adds complexity
Traditional “build-in place” approaches
● Have hidden dependency graphs
● Create variation between environments
● Are harder to “lock down” due to config
AND OMG… updates and patches are even harder
● Idempotent operations are difficult
● Roll backward is next to impossible!
● Creating indeterminate state
8. 8
@zehicle #immutable
Traditional “build-in place” approaches
● Have hidden dependency graphs
● Create variation between environments
● Are harder to “lock down” due to config
AND OMG… updates and patches are even harder
● Idempotent operations are difficult
● Roll backward is impossible
● Creating indeterminate state
But… I Infrastructure as code?!
Sorry. Mutability adds complexity
Let’s o k w !
11. 11
@zehicle #immutable
Traditional Deploy and Configure
System is configured in situ from
a least common denominator
baseline.
This can be “immutable-like”
under the right conditions.
We’ll come back to that...
Delivery Pipeline
Deployment
Code
Build
Integrate
Run
Configure
12. 12
@zehicle #immutable
Shifting Configuration BEFORE Deployment
In our ideal delivery pipeline,
configuration is before
deployment.
Running systems are delivered as
a complete runnable unit for
deployment.
Delivery Pipeline
Deployment
Code
Build
Integrate
Run
Configure
13. 13
@zehicle #immutable
Shifting Configuration BEFORE Deployment
In reality, it’s very hard to create a
distinct artifact for every running
instance; instead, we create
incremental versions.
So we do some initialization of the
reusable versioned instance.
Cloud init is the most commonly
known pattern for this.
Delivery Pipeline
Deployment
Code
Build
Integrate
Run
Configure
Ini iz !
V
15. 15
@zehicle #immutable
Which Enables… Delegating Operations
If you can make your artifacts
immutable then you can delegate
management of them to a
platform like Kubernetes.
Kubernetes does not configure
infrastructure. It maintains state
based on a manifest.
StateManager
(e.g.Kubernetes)
Code
Build
Integrate
Run
Configure
Delivery Pipeline
16. 16
@zehicle #immutable
Which Enables… Delegating Operations
If you can make your artifacts
immutable then you can delegate
management of them to a
platform like Kubernetes.
Kubernetes does not configure
infrastructure. It maintains state
based on a manifest.
StateManager
(e.g.Kubernetes)
Code
Build
Integrate
Run
Configure
Delivery Pipeline
Kub te ? W !
Is ut > K8s?
17. Immutable is a DevOps Pattern
<<< Shift Left & Create/Delete
22. 22
@zehicle #immutable
The Problem
Immutability <<< Shifting Left
patch 1 patch 2
t e d s o n't
s o t c 2!
What Madness?
● We have to maintain root access
● Patches assume system state
● Patches create dependency graphs
● Coordination? Should we halt work?
● Drift is inevitable!
package
server
image
provision
server
initial
config
24. 24
@zehicle #immutable
Apply cloud and container lessons to our Bare Metal …
Immutability <<< Shifting Left
package
server
image
provision
server
initial
config
destroy!!
25. 25
@zehicle #immutable
Apply cloud and container lessons to our Bare Metal …
Immutability <<< Shifting Left
destroy!!
destroy!!patch 1
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
26. 26
@zehicle #immutable
Apply cloud and container lessons to our Bare Metal …
Immutability <<< Shifting Left
destroy!!
destroy!!patch 1
depatch 2
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
27. 27
@zehicle #immutable
Apply cloud and container lessons to our Bare Metal …
Immutability <<< Shifting Left
destroy!!
destroy!!patch 1
patch N
depatch 2
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
package
server
image
provision
server
initial
config
29. 29
Immutable Provisioning systems
treat infrastructure as a black box
Cloud-like Integration and Staged Workflow
Provisioning
System
Requested
State
Returned
State
REST
API
Event
Hook
30. 30
Cloud-like Integration and Staged Workflow
Immutable Provisioning systems
treat infrastructure as a black box
Provision requests are for a system state
with optional parameters.
The intermediate changes to achieve the
state are not exposed to the requester.
Provisioning
System
Reset Join
Install
Config
Test
Requested
State
Returned
State
REST
API
Event
Hook
31. 31
Cloud-like Integration and Staged Workflow
Immutable Provisioning systems
treat infrastructure as a black box
Provision requests are for a system state
with optional parameters.
The intermediate changes to achieve the
state are not exposed to the requester.
REMEMBER: Operators of the
provisioning system require high
transparency, stages and control.
Provisioning
System
Reset Join
Install
Config
Test
Requested
State
Returned
State
REST
API
Event
Hook
No h n
op i n !
33. 33
Provision
1: Baseline + Configuration
Benefit: Easiest to achieve with current tools, Safer than Patching
Challenge: Lots of Post-Configuration, Not Really “Immutable”, Slow
Instead of relying on patches, rely on starting from a pristine image
ResetBaseline Configure Run
Additional Reference https://thenewstack.io/immutable-hardware-ops-hygiene-security-efficiency/
34. 34
Benefit: Fast reset times, forces good behavior
Challenge: Provisioning becomes critical path, still have dependency graph
Like #1 but clean-up is simply a reboot. Favors smaller footprint O/S.
2: Live Boot + Configuration
Provision RebootBaseline Configure Run
35. 35
3: Image Deploy
Benefit: Shorter time to ready, highly controlled (“shift left”), rollback
Challenge: Harder to create and deploy images
Image is deployed from source instead of Baseline + Configure
Provision
Deploy
Image
Run Provision
Deploy
Image
Run
36. 36
3: Image Deploy
Benefit: Shorter time to ready, highly controlled (“shift left”), rollback
Challenge: Harder to create and deploy images
Image is deployed from source instead of Baseline + Configure
Provision
Deploy
Image
Run Provision
Deploy
Image
Run
Ini iz !
V
Ini iz !
V
37. 37
So… Let’s talk Image Creation
Ideally in an automation build process.
You DO THE CONFIGURATION on a
live system (so you still need
configuration tools) and then capture
the image into a portable format.
Tools like Hashicorp Packer, Image
Builder, WBIC or raw images are used
to create source files (e.g. AMI, OVS).
38. 38
So… Let’s talk Image Creation
Ideally in an automation build process.
You DO THE CONFIGURATION on a
live system (so you still need
configuration tools) and then capture
the image into a portable format.
Tools like Hasicorp Packer, Image
Builder, WBIC or raw images are used
to create source files (e.g. AMI, OVS).
Tha n li ot
of k & re y ow!
41. 41
Build Pipeline Deploy
Immutable Demo
Prep: Image is pre-created from reference system.
Stage: Boot RAM image and write image to disk(s)
Reference
System
Image
Target System
RAM BOOT
WriteRead
42. 42
Build Pipeline Deploy
Immutable Demo
Prep: Image is pre-created from reference system.
Stage: Boot RAM image and write image to disk(s)
Deploy: Reboot and run
Reference
System
Image
Target System
RAM BOOT
Target System
RUNNING
Reboot
Write RunRead
43. Thank you!
Questions?
Interested in IMMUTABLE METAL?
It’s complicated, but we can get you there.
Start at http://portal.rackn.io
• Quickstart takes about 30 minutes
• Use your own hardware, VirtualBox or Packet.net
account
– use “RACKN100” on Packet.net for credit