slides from unconference talk today (18 Apr 2013) with a quick overview of Oasis TOSCA, Oasis CAMP, and OpenStack Heat, and how they can align around a DSL. see also http://adrianotto.com/2013/04/what-is-camp/ and https://wiki.openstack.org/wiki/Heat/DSL .
Heard about Cloud Foundry? Already a Spring, Grails, Ruby, Node.js, Scala, or generalist programmer looking to understand what Cloud Foundry, the open source PaaS from VMware, means to you? Are you an architect trying to understand where PaaS fits it, and what it brings to the table? If you answered "yes" to any of those questions, then join the experts in this bootcamp to Cloud Foundry.
A way too long but entertaining talk given at the September 2015 Cloud Foundry Meetups in Vancouver and Calgary, Canada. Content is a mashup of my own slides and from many colleagues @ Pivotal.
In this session we'll discuss some of Kubernetes' basic concepts and talk about the architecture of the system, the problems it solves, and the model that it uses to handle containerized deployments and scaling.
Kubernetes for java developers - Tutorial at Oracle Code One 2018Anthony Dahanne
You’re a Java developer? Already familiar with Docker? Want to know more about Kubernetes and its ecosystem for developers? During this session, you’ll get familiar with core Kubernetes concepts (pods, deployments, services, volumes, and so on) before seeing the most-popular and most-productive Kubernetes tools in action, with a special focus on Java development. By the end of the session, you’ll have a better understanding of how you can leverage Kubernetes to speed up your Java deployments on-premises or to any cloud.
slides from unconference talk today (18 Apr 2013) with a quick overview of Oasis TOSCA, Oasis CAMP, and OpenStack Heat, and how they can align around a DSL. see also http://adrianotto.com/2013/04/what-is-camp/ and https://wiki.openstack.org/wiki/Heat/DSL .
Heard about Cloud Foundry? Already a Spring, Grails, Ruby, Node.js, Scala, or generalist programmer looking to understand what Cloud Foundry, the open source PaaS from VMware, means to you? Are you an architect trying to understand where PaaS fits it, and what it brings to the table? If you answered "yes" to any of those questions, then join the experts in this bootcamp to Cloud Foundry.
A way too long but entertaining talk given at the September 2015 Cloud Foundry Meetups in Vancouver and Calgary, Canada. Content is a mashup of my own slides and from many colleagues @ Pivotal.
In this session we'll discuss some of Kubernetes' basic concepts and talk about the architecture of the system, the problems it solves, and the model that it uses to handle containerized deployments and scaling.
Kubernetes for java developers - Tutorial at Oracle Code One 2018Anthony Dahanne
You’re a Java developer? Already familiar with Docker? Want to know more about Kubernetes and its ecosystem for developers? During this session, you’ll get familiar with core Kubernetes concepts (pods, deployments, services, volumes, and so on) before seeing the most-popular and most-productive Kubernetes tools in action, with a special focus on Java development. By the end of the session, you’ll have a better understanding of how you can leverage Kubernetes to speed up your Java deployments on-premises or to any cloud.
Triple-E’class Continuous Delivery with Hudson, Maven, Kokki and PyDevWerner Keil
At Maersk Line, not only the world's biggest ships 'Triple-E' class vessels are currently being built. Continuous Integration and Delivery on a similar scale using Hudson, Maven and tools like Kokki similar to Puppet or Chef are also practiced there.
This session is going to give a brief overview of Multi-Configuration (Matrix) job types used in most of these projects. Things are being built and deployed in a heterogenous environment, otherwise probably found only at large vendors of Public Cloud services.
2 Day Bootcamp for OpenStack--Cloud Training by Mirantis (Preview)Mirantis
Mirantis, the Global Engineering Services leader for OpenStack™ presents 2-day Bootcamp for OpenStack
www.mirantis.com/training
This two-day intensive course provides hands-on technical training for OpenStack aimed at system administrators and IT professionals looking to get started on an OpenStack Cloud deployment. Each of the two days will consist of lecture, demos and group exercises. Topics include:
• OpenStack Overview & Architecture: Project goals and use cases, basic operating and deployment principles
• Cloud Usage Patterns: OpenStack codebase overview; creating networks, tenants, roles, troubleshooting; Nexenta Volume Driver
• In Production: Deploying OpenStack for real-world use, and practice of OpenStack operation on multiple nodes
• Swift Object Storage: use cases, architecture, capabilities, configuration, security and deployment
• Advanced Topics: Software Defined Networking, deployment and issues workshop, VMWare/OpenStack comparison
PRE-REQUISITES: Comfortable with Linux CLI, understanding of virtualization & hypervisors, Some experience with Linux networking
All course materials will be provided by Mirantis, including access to shared compute resources for labs. A light breakfast and lunch will be available to all course participants.
Mirantis instructors are active code committers to the OpenStack project, with proven experience building OpenStack clouds in the real world. In parallel to delivering expert training, they also consult for some of the notable global companies using OpenStack – including Cisco, NASA, Dell and Internap.
Cloud orchestration major tools comparisionRavi Kiran
Cloud Orchestration major tools comparison (including history, installation, market share, integration with other public cloud system for each tool) For any clarification contact kiran79@techgeek.co.in
IBM BP Session - Multiple CLoud Paks and Cloud Paks Foundational Services.pptxGeorg Ember
Diese Präsentation beinhaltet Erfahrungen, Empfehlungen und Planungs-Gedanken, die man beachten sollte, wenn man multiple IBM Cloud Paks auf der Container Platform OpenShift installieren / deployen möchte. Es beschreibt die Grundlagen zu "common services", auch "foundational services" genannt, die als Basis-Services die Lauffähigkeit dieser Cloud Paks auf OpenShift erläutert und wie man Cloud Paks auch logisch trennen kann auf OpenShift worker nodes über taints und node selectors.
Cloud computing and OpenStack basic introduction. This presentation was given on November 13, 2014 at Universitat Politecnica de Catalunya. Barcelona, Spain.
Get you Java application ready for Kubernetes !Anthony Dahanne
In this demos loaded talk we’ll explore the best practices to create a Docker image for a Java app (it’s 2019 and new comers such as Jib, CNCF buildpacks are interesting alternatives to Docker builds !) - and how to integrate best with the Kubernetes ecosystem : after explaining main Kubernetes objects and notions, we’ll discuss Helm charts and productivity tools such as Skaffold, Draft and Telepresence.
This session provides an overview of how to build and deploy Spring-based applications to the Cloud Foundry platform.
The session will cover application configuration parameters, binding services to your application, deployment options using using STS, the vmc command tool, as well as the new Apache Maven plugin for Cloud Foundry. Gunnar will demonstrate how to deploy applications to both micro and public Cloud Foundry and will also show how debugging works with Cloud Foundry and how you can inspect services remotely using Caldecott.
Gunnar will also show various options to keep your War-files deployable to both Cloud Foundry and stand-alone Servlet Containers using auto-reconfiguration, the cloud namespace, and Spring 3.1 profiles.
Lastly, he will give a high-level overview how you can use Cloud Foundry together with Spring Integration in order to create scalable Spring applications.
Simplify Cloud Applications using Spring CloudRamnivas Laddad
Developing an application to a cloud platform involves working with deployed application's environment and connecting to services. Spring Cloud, a new project, simplifies these tasks in a variety of cloud platforms including Cloud Foundry and Heroku. Spring Cloud makes it possible to deploy the same artifact (a war or a jar) to multiple cloud environments. It supports multiple clouds through the concept of Cloud Connector and provides out of the box implementation for Cloud Foundry and Heroku. Spring Cloud is designed for extension, making it simple to create a cloud connector for other cloud platforms. Spring Cloud also supports connecting to multiple services through the concept of service connectors. Out of the box, it provides support for many common services, but also makes it easy to extend it to other services. While Spring Cloud can be used by applications using any JVM language and framework, it further simplifies Spring applications through Java and XML-based configuration. In this talk, we will introduce the Spring Cloud project, show how you can simplify configuring applications for cloud deployment, discuss its extensibility mechanism, and put it to good use by showing practical examples from the field.
Building Multi-Site and Multi-OpenStack Cloud with OpenStack CascadingJoe Huang
The slides used in the speech "Building multi-site and multi-openstack cloud with OpenStack cascading" in OpenStack Paris summit 2014. The slides cover the requirement and driving forces, case study of VDF, technologies eloboration and demo of OpenStack cascading.
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
Shared networks to support VNF high availability across OpenStack multi-regio...Joe Huang
Even now with all the advances to provide high level of resiliency in hardware and software components, it’s possible to have some failures. Those failures are undesirable for Enterprises and they are constantly looking for solutions which tolerate unexpected events to offer steady and unbroken services. Cloud computing solutions are not the exception. One way to achieve that is segregating the Cloud deployment in different regions.
For most of enterprise applications use stateful architectures, which means that they're constantly synchronizing their status among different instances. How to provide continuously service in case of a cloud failure happens?
During this presentation we will demonstrate how to architect an OpenStack multi-region solution through the existing official OpenStack projects like Neutron and Tricircle, demonstrate and compare the pros. and cons. of different tenant level L2/L3 networking topology across OpenStack clouds.
Container Orchestration with Docker Swarm and KubernetesWill Hall
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Kubernetes and Cloud Native Update Q4 2018CloudOps2005
This year’s final set of Kubernetes and Cloud Native meetups just took place. They kicked off in Kitchener-Waterloo on November 29th, and continued in Montreal December 3rd, Ottawa December 4th, Toronto December 5th, and Quebec December 6th. In preparation for the upcoming KubeCon and CloudNativeCon in Seattle, a wide range of open source solutions were discussed and, as always, beer and pizza provided. Ayrat Khayretdinov began each meetup with an update of Kubernetes and the Cloud Native landscape.
Connecting Commnities - online tools for networking for community groupsSimon Young
A presentation to the NZ Association of Community Access Broadcasters. A bit of a return to my roots as my career began in niche broadcasting at NZ's Christian radio network, which is where I began to learn about virtual communities. Hence the first message - it's not about technology, it is about communities.
This presentation outlines some of the many, many tools available, mostly for free.
Triple-E’class Continuous Delivery with Hudson, Maven, Kokki and PyDevWerner Keil
At Maersk Line, not only the world's biggest ships 'Triple-E' class vessels are currently being built. Continuous Integration and Delivery on a similar scale using Hudson, Maven and tools like Kokki similar to Puppet or Chef are also practiced there.
This session is going to give a brief overview of Multi-Configuration (Matrix) job types used in most of these projects. Things are being built and deployed in a heterogenous environment, otherwise probably found only at large vendors of Public Cloud services.
2 Day Bootcamp for OpenStack--Cloud Training by Mirantis (Preview)Mirantis
Mirantis, the Global Engineering Services leader for OpenStack™ presents 2-day Bootcamp for OpenStack
www.mirantis.com/training
This two-day intensive course provides hands-on technical training for OpenStack aimed at system administrators and IT professionals looking to get started on an OpenStack Cloud deployment. Each of the two days will consist of lecture, demos and group exercises. Topics include:
• OpenStack Overview & Architecture: Project goals and use cases, basic operating and deployment principles
• Cloud Usage Patterns: OpenStack codebase overview; creating networks, tenants, roles, troubleshooting; Nexenta Volume Driver
• In Production: Deploying OpenStack for real-world use, and practice of OpenStack operation on multiple nodes
• Swift Object Storage: use cases, architecture, capabilities, configuration, security and deployment
• Advanced Topics: Software Defined Networking, deployment and issues workshop, VMWare/OpenStack comparison
PRE-REQUISITES: Comfortable with Linux CLI, understanding of virtualization & hypervisors, Some experience with Linux networking
All course materials will be provided by Mirantis, including access to shared compute resources for labs. A light breakfast and lunch will be available to all course participants.
Mirantis instructors are active code committers to the OpenStack project, with proven experience building OpenStack clouds in the real world. In parallel to delivering expert training, they also consult for some of the notable global companies using OpenStack – including Cisco, NASA, Dell and Internap.
Cloud orchestration major tools comparisionRavi Kiran
Cloud Orchestration major tools comparison (including history, installation, market share, integration with other public cloud system for each tool) For any clarification contact kiran79@techgeek.co.in
IBM BP Session - Multiple CLoud Paks and Cloud Paks Foundational Services.pptxGeorg Ember
Diese Präsentation beinhaltet Erfahrungen, Empfehlungen und Planungs-Gedanken, die man beachten sollte, wenn man multiple IBM Cloud Paks auf der Container Platform OpenShift installieren / deployen möchte. Es beschreibt die Grundlagen zu "common services", auch "foundational services" genannt, die als Basis-Services die Lauffähigkeit dieser Cloud Paks auf OpenShift erläutert und wie man Cloud Paks auch logisch trennen kann auf OpenShift worker nodes über taints und node selectors.
Cloud computing and OpenStack basic introduction. This presentation was given on November 13, 2014 at Universitat Politecnica de Catalunya. Barcelona, Spain.
Get you Java application ready for Kubernetes !Anthony Dahanne
In this demos loaded talk we’ll explore the best practices to create a Docker image for a Java app (it’s 2019 and new comers such as Jib, CNCF buildpacks are interesting alternatives to Docker builds !) - and how to integrate best with the Kubernetes ecosystem : after explaining main Kubernetes objects and notions, we’ll discuss Helm charts and productivity tools such as Skaffold, Draft and Telepresence.
This session provides an overview of how to build and deploy Spring-based applications to the Cloud Foundry platform.
The session will cover application configuration parameters, binding services to your application, deployment options using using STS, the vmc command tool, as well as the new Apache Maven plugin for Cloud Foundry. Gunnar will demonstrate how to deploy applications to both micro and public Cloud Foundry and will also show how debugging works with Cloud Foundry and how you can inspect services remotely using Caldecott.
Gunnar will also show various options to keep your War-files deployable to both Cloud Foundry and stand-alone Servlet Containers using auto-reconfiguration, the cloud namespace, and Spring 3.1 profiles.
Lastly, he will give a high-level overview how you can use Cloud Foundry together with Spring Integration in order to create scalable Spring applications.
Simplify Cloud Applications using Spring CloudRamnivas Laddad
Developing an application to a cloud platform involves working with deployed application's environment and connecting to services. Spring Cloud, a new project, simplifies these tasks in a variety of cloud platforms including Cloud Foundry and Heroku. Spring Cloud makes it possible to deploy the same artifact (a war or a jar) to multiple cloud environments. It supports multiple clouds through the concept of Cloud Connector and provides out of the box implementation for Cloud Foundry and Heroku. Spring Cloud is designed for extension, making it simple to create a cloud connector for other cloud platforms. Spring Cloud also supports connecting to multiple services through the concept of service connectors. Out of the box, it provides support for many common services, but also makes it easy to extend it to other services. While Spring Cloud can be used by applications using any JVM language and framework, it further simplifies Spring applications through Java and XML-based configuration. In this talk, we will introduce the Spring Cloud project, show how you can simplify configuring applications for cloud deployment, discuss its extensibility mechanism, and put it to good use by showing practical examples from the field.
Building Multi-Site and Multi-OpenStack Cloud with OpenStack CascadingJoe Huang
The slides used in the speech "Building multi-site and multi-openstack cloud with OpenStack cascading" in OpenStack Paris summit 2014. The slides cover the requirement and driving forces, case study of VDF, technologies eloboration and demo of OpenStack cascading.
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
Shared networks to support VNF high availability across OpenStack multi-regio...Joe Huang
Even now with all the advances to provide high level of resiliency in hardware and software components, it’s possible to have some failures. Those failures are undesirable for Enterprises and they are constantly looking for solutions which tolerate unexpected events to offer steady and unbroken services. Cloud computing solutions are not the exception. One way to achieve that is segregating the Cloud deployment in different regions.
For most of enterprise applications use stateful architectures, which means that they're constantly synchronizing their status among different instances. How to provide continuously service in case of a cloud failure happens?
During this presentation we will demonstrate how to architect an OpenStack multi-region solution through the existing official OpenStack projects like Neutron and Tricircle, demonstrate and compare the pros. and cons. of different tenant level L2/L3 networking topology across OpenStack clouds.
Container Orchestration with Docker Swarm and KubernetesWill Hall
This presentation covers the basics of what container orchestration is providing pros and cons of Docker Swarm, Kubernetes and Amazon ECS and outlining the terms and tools you will need to successfully use them.
Kubernetes and Cloud Native Update Q4 2018CloudOps2005
This year’s final set of Kubernetes and Cloud Native meetups just took place. They kicked off in Kitchener-Waterloo on November 29th, and continued in Montreal December 3rd, Ottawa December 4th, Toronto December 5th, and Quebec December 6th. In preparation for the upcoming KubeCon and CloudNativeCon in Seattle, a wide range of open source solutions were discussed and, as always, beer and pizza provided. Ayrat Khayretdinov began each meetup with an update of Kubernetes and the Cloud Native landscape.
Connecting Commnities - online tools for networking for community groupsSimon Young
A presentation to the NZ Association of Community Access Broadcasters. A bit of a return to my roots as my career began in niche broadcasting at NZ's Christian radio network, which is where I began to learn about virtual communities. Hence the first message - it's not about technology, it is about communities.
This presentation outlines some of the many, many tools available, mostly for free.
You have it? Tips for successful business handoffsIan Lurie
How do you hand a task from one person to another? A project? A deliverable? Handoffs are the glue of a successful business. But we usually blow them.
Here are some techniques I've learned over the years. Oddly enough, I learned them
Myths and Realities of Cloud Data SecurityMichael Krouze
Debunking some of the "sound bite" myths around Cloud Data Security. Presentation done for the MinneAnalytics "Life Science Lean-In: Analytics & Big Data in Healthcare & Life Science"
How do nonprofit communicators rank and combine different goals? We took a look based on data from the 2013 Nonprofit Communications Trends Report. Full report at http://npmg.us/2013
Clocker: Managing Container Networking and PlacementDocker, Inc.
This talk introduces Clocker and shows how to bootstrap a Docker Cloud that is responsive and scalable, across a dynamic cluster of hosts and cloud providers. Clocker is an Apache licensed open source project that demonstrates intelligent placement, on-demand provisioning and autonomic management of containers using Apache Brooklyn as the central nervous system. The Clocker stack enhances the standard Docker installation using best practices for configuration and integrates Weave networking capabilities plus Apache jclouds for provisioning on any infrastructure. We will show how to use Clocker to deploy, monitor and scale complex applications defined using Brooklyn blueprints across a network of Docker containers in the cloud.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1FjjXpZ.
Andrew Kennedy talks about the reasons for creating a Docker cloud and how they realized that to do this properly they needed first class networking to handle composite distributed applications such as Riak. It was a short step from this to using Brooklyn itself to bootstrap a Docker cloud effectively colonizing the infrastructure. And so Clocker was born. Filmed at qconlondon.com.
Andrew Kennedy is a Senior Software Engineer at Cloudsoft and the founder of the Clocker project. He is a contributor to several Open Source projects including Apache jclouds and Apache Qpid and is also a founder member of the Apache Brooklyn project.
1. Using Apache Brooklyn and
Docker to Simulate your
Production Environments in
the Cloud
Andrew Kennedy
grkvlt@apache.org
2. ApacheCon Austin, TX; April 2015
Andrew Kennedy @grkvlt
Simulating Production
Using Apache Brooklyn and Clocker to Simulate
Production Environments in the Cloud
3. @grkvlt
Introduction
• Andrew Kennedy
– Clocker Project Founder and Lead Engineer
– Open Source and Distributed Systems
– Apache Committer for Brooklyn and Qpid
– github.com/grkvlt
• Cloudsoft Corporation
– Open Source Application Management Specialists
7. @grkvlt
What does it do?
1. Spins up and Manages Docker
Clouds
2. Serves up Containers on Demand
3. Manages Composite Application
Deployments on Docker
8. @grkvlt
What does it provide?
• Multi Host and Multi Container Applications
• Seamless Networking
– Communication Between Services
• Orchestration and Clustering
– Control of Containers
– Container Management
9. @grkvlt
Who is using it?
• Testing and Proof of Concept Stage
– Financial Services
– Insurance
• Production
– Multi-‐tenant Application Trial
– Container per service
– Ideally suited to the Clocker model
10. @grkvlt
Where can I find it?
• Open Source on GitHub
• Apache 2.0 Licensed
• http://clocker.io
• Status
• 0.8.0 Developer Preview available now
• 0.8.0 Release at Docker Meetup this week!
13. @grkvlt
Clocker and Brooklyn
• What is it?
– Brooklyn Application and Location
– Uses jclouds for Docker access
• What does it provide?
– First Class Docker Support in Brooklyn
– Optimized Brooklyn Blueprints for Docker
21. @grkvlt
Features
• Orchestrated Docker 1.5.0 deployment with SDN
integration
• Automated attachment of containers to multiple
dynamic networks
• Brooklyn application blueprints with network
topology
• Docker images as Brooklyn entity source
23. @grkvlt
Clocker Features
• Application Deployment
– Oasis CAMP YAML Blueprint
– TOSCA in Development
– Docker Compose
– Core Brooklyn
• Mixed Destinations
– Some Virtual Machines
– Some Bare Metal
– Some Containers
24. @grkvlt
Clocker Features
• Docker Extensions to Brooklyn
– Dockerfile or Image Specification for Installation
– Placement Strategies for Containers
– Create Docker Images and Networks
• Manages Docker Engine
– Deployment and Management
– Installation and Configuration
– Software-‐Defined Networking
33. @grkvlt
Container Placement
• Where do we want the service to run?
• Supply and Demand
– Here's the locations you can use...
– I want a very specific location...
• Docker Swarm
– Possible future integration point...
35. @grkvlt
Container Placement
• Supply
– Choose a Host from available
– Create new Host if required
• Start Container there
– Set CPU and Memory
– Attach to Network
36. @grkvlt
Container Placement
• Placement Strategies
– Random, Depth or Breadth First
– CPU or Memory Usage
– Memory, CPU or Container Limits
– Geographic Constraints
• User Defined
– Java Predicate
39. @grkvlt
Application Resilience
• Service Resilience and Replacement
–Restart Service and Container
–Application Level, Not Infrastructure
–Same as Cloud
• Snapshot Running Container for Restart
40. @grkvlt
Headroom
• Ensure resources available
• Based on MaxContainers strategy limit
– Or Percentage Utilization
– Or CPU and RAM allocation
• Scale Docker Host Cluster Automatically
– Add new Docker hosts
– Remove empty Docker hosts
41. @grkvlt
Software-‐Defined Networking
• Needed for Seamless Provisioning
• Host to Host Communication
– Same LAN Segment
– No Port Forwarding
– Natural Application Configuration
• Initial Driver was EPMD Applications
47. @grkvlt
Dev Cycle Reality
• My Laptop
• Jenkins Server
• Bob's Laptop
• Some spare VMs we found...
• The best we can afford
– until next year's budget...?
50. @grkvlt
Different Application
• Very Different!
– No resilient pairs
– No failover
– No load balancer
– No Clustering
– Single network, namespace, domain, etc.
51. @grkvlt
How can we fix this?
• Perfect worlds
• All environments identical
• Staging is an exact copy of production
– Ready for App and Infra cut-‐over
• UAT is Staging, with anonymized data
• And so on, rolling through environments
52. @grkvlt
How can we fix this?
• CI becomes CD
– Dedicated production-‐level environment for builds
– Successful builds promoted to UAT
• Test and Dev...?
– You have to make some sacrifices ;)
– But will try and test the HA mechanism and so on in
isolation
– But alt least Ops are happy
53. @grkvlt
How can we fix this?
• Imperfect world
• Or, the DevOps way
– We don't have enough money for six copies of our architecture
– Particularly at scale or with large data sets
– So we fake it!
• The important thing is our architecture
– It defines the application completely
– We describe this once in a blueprint
– And then deploy to our various environments
54. @grkvlt
Clocker and DevOps
• Application blueprint
• Describes
– Services
• Configuration
– Policies
– Networks
– Hierarchy
• Connections
• Can be deployed to any Brooklyn Location
55. @grkvlt
Clocker and DevOps
• Locations include
– Vagrant or other VMs on my laptop
– Apache jclouds supported providers
• On premise OpenStack CI cloud
• Public SoftLayer environment
• ... choose your favourite
– Docker Clouds using Clocker
• Containers instead of VMs
• Automatically
• No input from developer required
56. @grkvlt
There's More Than One Way...
• Could use Clocker and Docker everywhere
– Generate Docker image during build process
– Size underlying VMs appropriately
– Allocate different CPU/memory to containers
– Deploy images to Clocker everywhere
• Many enterprises not yet ready for this...