The document summarizes the OpenStack Interoperability Working Group's efforts to promote interoperability across OpenStack distributions and products. It discusses how the group develops guidelines specifying required capabilities and tests. Products must pass these tests to be considered interoperable and qualify for the OpenStack logo program. The guidelines aim to ensure a consistent user experience while allowing flexibility in implementations. The document also outlines the group's governance process and opportunities for participants to provide feedback to help improve interoperability standards over time.
Interoperability: The Elephants in the Room & What We're Doing About ThemMark Voelker
Talk by Mark Voelker and Chris Hoge at the OpenStack Newton Design Summit in April 2016. In this talk, we describe why interoperability for OpenStack clouds matters, what some of the major pain points are when trying to write a cross-cloud app, and what's being done to make those problems a thing of the past. We'll also discuss DefCore's role in shedding light on the problems and creating strong feedback loops..
A session in the DevNet Zone at Cisco Live, Berlin. At the moment, this is the DoE: DevOps of Everything. DevOps is about culture first but many people take shortcuts to tools and workflow. They forgot the essence of DevOps which is about people and not only from Dev to Ops. In this session, we will show you how we are currently building a DevOps culture with a focus on continuous improvement.
Navigating the open stack ecosystem summit vancouver.pptxSriram Subramanian
The document discusses accelerating adoption of Open Infrastructure and provides an overview of Solinea and CloudDon. It describes Solinea as a software and services company focused on cloud computing and CloudDon as a research, analysis and systems integration provider focused on OpenStack. The document also provides statistics on OpenStack's growth, projections for its market size, and discusses the various components that make up the growing OpenStack ecosystem including distributions, public cloud providers, professional services, and more.
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
Bringing DevOps to Routing with evolved XR: an overviewCisco DevNet
A session in the DevNet Zone at Cisco Live, Berlin. This session is a fresh perspective on the routing world, focused on the growing influence of DevOps style workflows in routing deployments across Web scale service providers. With the adoption of a 64-bit linux OS, support for Linux containers (LXC/Docker) and an open architecture that enables automated configuration management off the bat, the evolution of IOS-XR has placed it right in the midst of DevOps and SDN. In this session we dive deep into the application-hosting infrastructure, Modular software delivery techniques and support for zero touch provisioning and configuration management tools that integrate seamlessly with the M2M interfaces exposed by IOS XR. We look at deployment techniques of web scale service providers that is gradually influencing the rest of the market and introduce a variety of use cases around automated NetOps, traffic-engineering, Telemetry and data-center cluster schedulers that showcase the power of an open, automatable network operating system.
AWS Summit Tel Aviv - Enterprise Track - Enterprise Apps & HybridAmazon Web Services
The document summarizes a presentation given at the AWS Summit 2013 in Tel Aviv on using AWS for enterprise applications and hybrid environments. The presentation covered:
1. Using AWS to extend on-premises data center capacity and provide flexible infrastructure for new projects.
2. Connecting the on-premises environment to AWS through a virtual private cloud (VPC) and direct connect.
3. Leveraging AWS for development, testing, and continuous deployment activities.
4. Examples of running enterprise workloads like Oracle databases, SAP applications, and Microsoft software on AWS.
Monolithic to Microservices + Docker = SDLC on Steroids!Docker, Inc.
Ashish Sharma, SS&C Eze -
SS&C Eze provides various products in the stock market domain. We spent the last couple of years building Eclipse which is an investment suite born in cloud. The journey so far has been very interesting. The very first version of the product were a bunch of monolithic windows services and deployed using Octopus tool. We successfully managed to bring all the monolithic problem to the cloud and created a nightmare for ourselves. We then started applying microservices architecture principles and started breaking the monolithic into small services. Very soon we realized that we need a better packaging/deployment tool. Docker looked like a magical solution to our problem. Since its adoption, It has not only solved the deployment problem for us but has made a deep impact on different aspects of SDLC. It allowed us to use heterogeneous technology stacks, simplified development environment setup, simplified our testing strategy, improved our speed of delivery, and made our developers more productive. In this talk I would like to share our experience of using Docker and its positive impact on our SDLC.
Interoperability: The Elephants in the Room & What We're Doing About ThemMark Voelker
Talk by Mark Voelker and Chris Hoge at the OpenStack Newton Design Summit in April 2016. In this talk, we describe why interoperability for OpenStack clouds matters, what some of the major pain points are when trying to write a cross-cloud app, and what's being done to make those problems a thing of the past. We'll also discuss DefCore's role in shedding light on the problems and creating strong feedback loops..
A session in the DevNet Zone at Cisco Live, Berlin. At the moment, this is the DoE: DevOps of Everything. DevOps is about culture first but many people take shortcuts to tools and workflow. They forgot the essence of DevOps which is about people and not only from Dev to Ops. In this session, we will show you how we are currently building a DevOps culture with a focus on continuous improvement.
Navigating the open stack ecosystem summit vancouver.pptxSriram Subramanian
The document discusses accelerating adoption of Open Infrastructure and provides an overview of Solinea and CloudDon. It describes Solinea as a software and services company focused on cloud computing and CloudDon as a research, analysis and systems integration provider focused on OpenStack. The document also provides statistics on OpenStack's growth, projections for its market size, and discusses the various components that make up the growing OpenStack ecosystem including distributions, public cloud providers, professional services, and more.
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
Bringing DevOps to Routing with evolved XR: an overviewCisco DevNet
A session in the DevNet Zone at Cisco Live, Berlin. This session is a fresh perspective on the routing world, focused on the growing influence of DevOps style workflows in routing deployments across Web scale service providers. With the adoption of a 64-bit linux OS, support for Linux containers (LXC/Docker) and an open architecture that enables automated configuration management off the bat, the evolution of IOS-XR has placed it right in the midst of DevOps and SDN. In this session we dive deep into the application-hosting infrastructure, Modular software delivery techniques and support for zero touch provisioning and configuration management tools that integrate seamlessly with the M2M interfaces exposed by IOS XR. We look at deployment techniques of web scale service providers that is gradually influencing the rest of the market and introduce a variety of use cases around automated NetOps, traffic-engineering, Telemetry and data-center cluster schedulers that showcase the power of an open, automatable network operating system.
AWS Summit Tel Aviv - Enterprise Track - Enterprise Apps & HybridAmazon Web Services
The document summarizes a presentation given at the AWS Summit 2013 in Tel Aviv on using AWS for enterprise applications and hybrid environments. The presentation covered:
1. Using AWS to extend on-premises data center capacity and provide flexible infrastructure for new projects.
2. Connecting the on-premises environment to AWS through a virtual private cloud (VPC) and direct connect.
3. Leveraging AWS for development, testing, and continuous deployment activities.
4. Examples of running enterprise workloads like Oracle databases, SAP applications, and Microsoft software on AWS.
Monolithic to Microservices + Docker = SDLC on Steroids!Docker, Inc.
Ashish Sharma, SS&C Eze -
SS&C Eze provides various products in the stock market domain. We spent the last couple of years building Eclipse which is an investment suite born in cloud. The journey so far has been very interesting. The very first version of the product were a bunch of monolithic windows services and deployed using Octopus tool. We successfully managed to bring all the monolithic problem to the cloud and created a nightmare for ourselves. We then started applying microservices architecture principles and started breaking the monolithic into small services. Very soon we realized that we need a better packaging/deployment tool. Docker looked like a magical solution to our problem. Since its adoption, It has not only solved the deployment problem for us but has made a deep impact on different aspects of SDLC. It allowed us to use heterogeneous technology stacks, simplified development environment setup, simplified our testing strategy, improved our speed of delivery, and made our developers more productive. In this talk I would like to share our experience of using Docker and its positive impact on our SDLC.
DEVNET-1102 Introduction to the DevNet Sandbox and IVTCisco DevNet
Come to this session to hear about the DevNet Sandbox and how it can accelerate your product development and reduce IVT costs! DevNet Sandboxes are an easy to use, cost-effective alternative to building out your own hardware lab and testing environment for many applications integrating with Cisco Technologies. All DevNet members have access to our sandbox labs for development, internal testing and in some cases IVT!. In this session you will learn about technologies offered, lab features and our roadmap for new labs and IVT programs.
1. Traditional database development faces issues like lack of source control, tedious deployment scripts, and manual processes.
2. DevOps principles like continuous integration, static code analysis, and automation can help address these issues. Database changes can be tracked in source control and deployed automatically.
3. There are different approaches to database deployment like state-based using DACPAC files or migration-based using incremental scripts stored in source control. Tools like SSDT, ReadyRoll, and Flyway support these approaches.
First steps into developing an application as a suite of small services, and analysis of tools and architecture approaches to be used.
Topics covered:
1) What is a micro service architecture
2)Advantages in code procedures, team dynamics and scaling
3) How container services such as docker assist in its implementation
4) How to deploy code in a micro services architecture
5) Container Management tools and resource efficiency (mesos, kubernetes, aws container service)
6) Scaling up
By PeoplePerHour team
presented by CTO Spyros Lambrinidis & Senior DevOps Panagiotis Moustafellos @ Docker Athens Meetup 18/02/2015
Infrastructure as Code represents treating infrastructure components like software that can be version controlled, tested, and deployed. The document discusses tools and techniques for implementing Infrastructure as Code including using version control, continuous integration/delivery, configuration automation, and virtual labs for testing changes. It provides examples of workflows using these techniques and recommends starting small and evolving Infrastructure as Code practices over time.
Drone fly - Decoupling Event Listeners from the Hive MetastoreAbhimanyu Gupta
Drone Fly is a distributed Hive metastore events forwarder service that allows users to deploy metastore listeners outside the Hive metastore service. It works by installing a single Apiary Kafka listener in the metastore, which writes events to a Kafka queue. Drone Fly then reads these events from Kafka and forwards them to any listeners installed on its classpath, mimicking the Hive metastore context. This decouples listeners from the metastore to avoid issues like performance problems or downtime when installing or changing listeners.
All Things Jenkins and Cloud Foundry (Cloud Foundry Summit 2014)VMware Tanzu
The document discusses Jenkins and how it can be used with CloudFoundry. It provides an overview of Jenkins and CloudBees, and how Jenkins can be deployed on-premise with CloudFoundry. It also describes the benefits of Jenkins Enterprise and Operations Center by CloudBees, which provide professional support, high availability, security and other features for deploying and managing Jenkins in enterprise environments.
Mirantis OpenStack 4.0 includes OpenStack Havana, hardened packages, the Savana, Murano, and Ceilometer projects, and most of all, the ease of deploying with Fuel.
[Presented at All Things Open 2015 in Raleigh, NC, USA]
OpenStack is one of the fastest-growing and exciting open source projects of our time. OpenStack has drawn together technologists from all over the world to create a cloud operating system and a huge, diverse community behind it. This talk will provide an introduction to OpenStack for newcomers to the project of those who just want to know more. We’ll take a brief look at OpenStack’s history, get a technical overview of the project, learn how to contribute, and check out a few emerging trends and hot topics in the OpenStack world.
DevNexus 2015
Docker: containerizing a monolithic app into a microservice-based PaaS
Convert a monolithic application into a microservice-based PaaS using Docker and related, containerization technologies. This will be the third presentation of a series of presentations that began greater than one year ago to evangelize the benefits of Docker. The scope of content spans from a development environment to a hybrid PaaS, and how Containerization is an enabler of architectural choice, innovation, scalability, and polyglot solutions.
The basics of Docker will be examined including repositories, brief discussion about managing and monitoring Docker containers, service discovery, and security. New and emerging technologies will be a constant theme, particularly about microservices, in addition to the ongoing evolution of the market and what the future may bring. Common organizational issues (and tactical solutions) that may impede successful decomposition and migration of legacy monoliths will be discussed, including security, DevOps and refactoring.
Hypothetical architectures will be described for building progressively more robust and complex applications and deployment models. The goal is to highlight the power, flexibility and scalability that containers enable.
Examples will start simple, from a local development environment, that is a simple two container setup that encapsulate a database and application tier. Subsequent discussion will involve progressively more complex and robust deployments that include features such as service discovery, automatic load balancing, and abstractions to simplify linking of containers including service gateways. With the stopping point of a hybrid PaaS.
Collaborating with OpenDaylight for a Network-Enabled CloudTesora
OpenDaylight is an open source SDN platform developed under the Linux Foundation. It aims to promote adoption of SDN through an industry-supported common platform. OpenDaylight has over 31,000 commits from nearly 700 contributors, representing over 2.6 million lines of Java code. It is used in over 150 commercial deployments and integrates with OpenStack for network virtualization and NFV services. Future releases will improve scaling, performance, and application integration through projects like Genius and NetVirt.
MJC 2021: "Debugging Java Microservices Running on Kubernetes with Telepresence"Daniel Bryant
The document discusses using Telepresence to improve the development workflow for Java microservices running on Kubernetes. Telepresence allows developers to run their code locally while still connecting to the Kubernetes cluster, improving the speed of the inner development loop. It supports various workflows from small to large systems. The benefits of Telepresence include using local tools, connecting to cloud resources, and a very fast inner loop. It is an open source project maintained by the CNCF.
This document provides an overview of Docker and cloud native training presented by Brian Christner of 56K.Cloud. It includes an agenda for Docker labs, common IT struggles Docker can address, and 56K.Cloud's consulting and training services. It discusses concepts like containers, microservices, DevOps, infrastructure as code, and cloud migration. It also includes sections on Docker architecture, networking, volumes, logging, and monitoring tools. Case studies and examples are provided to demonstrate how Docker delivers speed, agility, and cost savings for application development.
LJC 4/21"Easy Debugging of Java Microservices Running on Kubernetes with Tele...Daniel Bryant
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
Kellyn Pot’Vin-Gorman discusses DevOps tools for winning agility. She emphasizes that while many organizations automate testing, the DevOps journey is longer and involves additional steps like orchestration between environments, security, collaboration, and establishing a culture of continuous improvement. She also stresses that organizations should not forget about managing their data as part of the DevOps process and advocates for approaches like database virtualization to help enhance DevOps initiatives.
Implementing FaaS on Kubernetes using KubelessAhmed Misbah
This session discusses implementing Function-as-a-Service (FaaS) on Kubernetes using Kubeless. FaaS is part of Serverless architectures, which offer benefits such as reduced operational and development costs and optimized scaling. Those benefits are essential for companies looking to survive the economic crisis caused by COVID-19.
The session is organized so that it would introduce the audience to Serverless Architectures. It then covers Function-as-a-Service in details and how it is an evolution of Cloud services and Software Architectural styles. Finally, it covers Kubeless, the K8s native FaaS platform and most common FAQs on it.
This presentation is to reflect on the amazing advancement of the open source community in the field of Cloud Computing and how does it now allow us to build reliable software components quickly within truly agile infrastructure.
Puppet Camp Charlotte 2015: Managing middleware with PuppetPuppet
Managing middleware with Puppet can be challenging due to the complex nature of middleware applications and configurations. Some key challenges include having multiple software development lifecycles to manage for applications and middleware updates, issues with ownership of configuration directories, maintaining idempotency when applying configurations, and managing customizations while avoiding naming conflicts. The document recommends isolating any company-specific customizations into a wrapper module to more easily contribute standard configuration back to the open source community. Active management of middleware is important for security and availability reasons.
Continuous Delivery leveraging on Docker CaaS by Adrien BlindDocker, Inc.
At Societe Generale GBIS, time to market & quality matters; hence we do love continuous delivery. In this context, we’re considering the Container as a Service pattern: artifacts produced by the continuous integration chain would become self-sufficient “dockerized” application modules, onboarding both code and subsequent system requirements; then, a CaaS cloud would enable to host these containers. In this talk, I’ll present our usecase and current findings, considering both technical & operational aspects. We’ll talk about software factories, immutable IT, registries, containers configuration, API-driven infrastructure, DevOps roles shifts. Finally, we’ll discuss pros/cons of this solution toward regular IaaS and PaaS.
The document describes an inaugural OpenStack meetup organized by Mark T. Voelker, Arvind Somya, and Amy Lewis on 2013-03-07. The meetup included welcome remarks and introductions of OpenStack, OpenStack Quantum, and installing DevStack. Speakers included Mark Voelker, Kyle Mestery, and Arvind Somya. Pizza was served afterwards.
OpenStack: Everything You Need To Know to Get Started (ATO2014)Mark Voelker
Slides for my talk at All Things Open 2014
OpenStack is widely recognized as a leading open source cloud computing platform and has attracted plenty of attention from developers, end users, IT companies, and media. As OpenStack continue to gain adoption, the audience of potential users continues to expand. Whether you’re building a public cloud service or private clouds for e-commerce, video/collaboration apps, sceintific research, NFV, or are simply looking for a more elastic model of infrastructure, OpenStack is an option to consider. This talk will serve as an extensive introduction for newcomers to OpenStack. We’ll discuss both the software itself and the makeup of the community of developers and users around it. We’ll learn how to contribute to OpenStack, who’s using it today, different deployment scenarios and use cases, and provide both online and local resources for learning more. We’ll also provide an introduction to incubated components, underpinning pieces, and pointers to installers and service providers who can help you get started.
DEVNET-1102 Introduction to the DevNet Sandbox and IVTCisco DevNet
Come to this session to hear about the DevNet Sandbox and how it can accelerate your product development and reduce IVT costs! DevNet Sandboxes are an easy to use, cost-effective alternative to building out your own hardware lab and testing environment for many applications integrating with Cisco Technologies. All DevNet members have access to our sandbox labs for development, internal testing and in some cases IVT!. In this session you will learn about technologies offered, lab features and our roadmap for new labs and IVT programs.
1. Traditional database development faces issues like lack of source control, tedious deployment scripts, and manual processes.
2. DevOps principles like continuous integration, static code analysis, and automation can help address these issues. Database changes can be tracked in source control and deployed automatically.
3. There are different approaches to database deployment like state-based using DACPAC files or migration-based using incremental scripts stored in source control. Tools like SSDT, ReadyRoll, and Flyway support these approaches.
First steps into developing an application as a suite of small services, and analysis of tools and architecture approaches to be used.
Topics covered:
1) What is a micro service architecture
2)Advantages in code procedures, team dynamics and scaling
3) How container services such as docker assist in its implementation
4) How to deploy code in a micro services architecture
5) Container Management tools and resource efficiency (mesos, kubernetes, aws container service)
6) Scaling up
By PeoplePerHour team
presented by CTO Spyros Lambrinidis & Senior DevOps Panagiotis Moustafellos @ Docker Athens Meetup 18/02/2015
Infrastructure as Code represents treating infrastructure components like software that can be version controlled, tested, and deployed. The document discusses tools and techniques for implementing Infrastructure as Code including using version control, continuous integration/delivery, configuration automation, and virtual labs for testing changes. It provides examples of workflows using these techniques and recommends starting small and evolving Infrastructure as Code practices over time.
Drone fly - Decoupling Event Listeners from the Hive MetastoreAbhimanyu Gupta
Drone Fly is a distributed Hive metastore events forwarder service that allows users to deploy metastore listeners outside the Hive metastore service. It works by installing a single Apiary Kafka listener in the metastore, which writes events to a Kafka queue. Drone Fly then reads these events from Kafka and forwards them to any listeners installed on its classpath, mimicking the Hive metastore context. This decouples listeners from the metastore to avoid issues like performance problems or downtime when installing or changing listeners.
All Things Jenkins and Cloud Foundry (Cloud Foundry Summit 2014)VMware Tanzu
The document discusses Jenkins and how it can be used with CloudFoundry. It provides an overview of Jenkins and CloudBees, and how Jenkins can be deployed on-premise with CloudFoundry. It also describes the benefits of Jenkins Enterprise and Operations Center by CloudBees, which provide professional support, high availability, security and other features for deploying and managing Jenkins in enterprise environments.
Mirantis OpenStack 4.0 includes OpenStack Havana, hardened packages, the Savana, Murano, and Ceilometer projects, and most of all, the ease of deploying with Fuel.
[Presented at All Things Open 2015 in Raleigh, NC, USA]
OpenStack is one of the fastest-growing and exciting open source projects of our time. OpenStack has drawn together technologists from all over the world to create a cloud operating system and a huge, diverse community behind it. This talk will provide an introduction to OpenStack for newcomers to the project of those who just want to know more. We’ll take a brief look at OpenStack’s history, get a technical overview of the project, learn how to contribute, and check out a few emerging trends and hot topics in the OpenStack world.
DevNexus 2015
Docker: containerizing a monolithic app into a microservice-based PaaS
Convert a monolithic application into a microservice-based PaaS using Docker and related, containerization technologies. This will be the third presentation of a series of presentations that began greater than one year ago to evangelize the benefits of Docker. The scope of content spans from a development environment to a hybrid PaaS, and how Containerization is an enabler of architectural choice, innovation, scalability, and polyglot solutions.
The basics of Docker will be examined including repositories, brief discussion about managing and monitoring Docker containers, service discovery, and security. New and emerging technologies will be a constant theme, particularly about microservices, in addition to the ongoing evolution of the market and what the future may bring. Common organizational issues (and tactical solutions) that may impede successful decomposition and migration of legacy monoliths will be discussed, including security, DevOps and refactoring.
Hypothetical architectures will be described for building progressively more robust and complex applications and deployment models. The goal is to highlight the power, flexibility and scalability that containers enable.
Examples will start simple, from a local development environment, that is a simple two container setup that encapsulate a database and application tier. Subsequent discussion will involve progressively more complex and robust deployments that include features such as service discovery, automatic load balancing, and abstractions to simplify linking of containers including service gateways. With the stopping point of a hybrid PaaS.
Collaborating with OpenDaylight for a Network-Enabled CloudTesora
OpenDaylight is an open source SDN platform developed under the Linux Foundation. It aims to promote adoption of SDN through an industry-supported common platform. OpenDaylight has over 31,000 commits from nearly 700 contributors, representing over 2.6 million lines of Java code. It is used in over 150 commercial deployments and integrates with OpenStack for network virtualization and NFV services. Future releases will improve scaling, performance, and application integration through projects like Genius and NetVirt.
MJC 2021: "Debugging Java Microservices Running on Kubernetes with Telepresence"Daniel Bryant
The document discusses using Telepresence to improve the development workflow for Java microservices running on Kubernetes. Telepresence allows developers to run their code locally while still connecting to the Kubernetes cluster, improving the speed of the inner development loop. It supports various workflows from small to large systems. The benefits of Telepresence include using local tools, connecting to cloud resources, and a very fast inner loop. It is an open source project maintained by the CNCF.
This document provides an overview of Docker and cloud native training presented by Brian Christner of 56K.Cloud. It includes an agenda for Docker labs, common IT struggles Docker can address, and 56K.Cloud's consulting and training services. It discusses concepts like containers, microservices, DevOps, infrastructure as code, and cloud migration. It also includes sections on Docker architecture, networking, volumes, logging, and monitoring tools. Case studies and examples are provided to demonstrate how Docker delivers speed, agility, and cost savings for application development.
LJC 4/21"Easy Debugging of Java Microservices Running on Kubernetes with Tele...Daniel Bryant
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
Kellyn Pot’Vin-Gorman discusses DevOps tools for winning agility. She emphasizes that while many organizations automate testing, the DevOps journey is longer and involves additional steps like orchestration between environments, security, collaboration, and establishing a culture of continuous improvement. She also stresses that organizations should not forget about managing their data as part of the DevOps process and advocates for approaches like database virtualization to help enhance DevOps initiatives.
Implementing FaaS on Kubernetes using KubelessAhmed Misbah
This session discusses implementing Function-as-a-Service (FaaS) on Kubernetes using Kubeless. FaaS is part of Serverless architectures, which offer benefits such as reduced operational and development costs and optimized scaling. Those benefits are essential for companies looking to survive the economic crisis caused by COVID-19.
The session is organized so that it would introduce the audience to Serverless Architectures. It then covers Function-as-a-Service in details and how it is an evolution of Cloud services and Software Architectural styles. Finally, it covers Kubeless, the K8s native FaaS platform and most common FAQs on it.
This presentation is to reflect on the amazing advancement of the open source community in the field of Cloud Computing and how does it now allow us to build reliable software components quickly within truly agile infrastructure.
Puppet Camp Charlotte 2015: Managing middleware with PuppetPuppet
Managing middleware with Puppet can be challenging due to the complex nature of middleware applications and configurations. Some key challenges include having multiple software development lifecycles to manage for applications and middleware updates, issues with ownership of configuration directories, maintaining idempotency when applying configurations, and managing customizations while avoiding naming conflicts. The document recommends isolating any company-specific customizations into a wrapper module to more easily contribute standard configuration back to the open source community. Active management of middleware is important for security and availability reasons.
Continuous Delivery leveraging on Docker CaaS by Adrien BlindDocker, Inc.
At Societe Generale GBIS, time to market & quality matters; hence we do love continuous delivery. In this context, we’re considering the Container as a Service pattern: artifacts produced by the continuous integration chain would become self-sufficient “dockerized” application modules, onboarding both code and subsequent system requirements; then, a CaaS cloud would enable to host these containers. In this talk, I’ll present our usecase and current findings, considering both technical & operational aspects. We’ll talk about software factories, immutable IT, registries, containers configuration, API-driven infrastructure, DevOps roles shifts. Finally, we’ll discuss pros/cons of this solution toward regular IaaS and PaaS.
The document describes an inaugural OpenStack meetup organized by Mark T. Voelker, Arvind Somya, and Amy Lewis on 2013-03-07. The meetup included welcome remarks and introductions of OpenStack, OpenStack Quantum, and installing DevStack. Speakers included Mark Voelker, Kyle Mestery, and Arvind Somya. Pizza was served afterwards.
OpenStack: Everything You Need To Know to Get Started (ATO2014)Mark Voelker
Slides for my talk at All Things Open 2014
OpenStack is widely recognized as a leading open source cloud computing platform and has attracted plenty of attention from developers, end users, IT companies, and media. As OpenStack continue to gain adoption, the audience of potential users continues to expand. Whether you’re building a public cloud service or private clouds for e-commerce, video/collaboration apps, sceintific research, NFV, or are simply looking for a more elastic model of infrastructure, OpenStack is an option to consider. This talk will serve as an extensive introduction for newcomers to OpenStack. We’ll discuss both the software itself and the makeup of the community of developers and users around it. We’ll learn how to contribute to OpenStack, who’s using it today, different deployment scenarios and use cases, and provide both online and local resources for learning more. We’ll also provide an introduction to incubated components, underpinning pieces, and pointers to installers and service providers who can help you get started.
OpenStack: Toward a More Resilient CloudMark Voelker
Since it's inception over four years ago, OpenStack has become the most popular open source software for building many types of clouds in part due to the flexibility it provides. As more adoption increases, interest has increased in building OpenStack clouds on a highly available control plane infrastructure. In this talk we will provide an introduction to today's OpenStack community and software, then dive deeper into how to build more highly available, scalable OpenStack architectures. - See more at: http://www.percona.com/news-and-events/percona-university-smart-data-raleigh/openstack-toward-more-resilient-cloud#sthash.wicdUMdH.dpuf
DefCore: The Interoperability Standard for OpenStackMark Voelker
This presentation provides an introduction to the OpenStack DefCore Committee, which is working to create interoperability standards for OpenStack Powered clouds. You'll gain insight into the interoperability challenges of OpenStack clouds, and learn how DefCore creates it's Guidelines. Learn why the Technical Committee, Board of Directors, end users, and vendors have a seat at the table. You'll laugh, you'll cry, you'll immediately want to stop talking about cloud computing and go watch science fiction all night.
This talk was originally presented at the Triangle OpenStack Meetup Group's September 21, 2015 meeting in Durham, NC. A recording can be found here (this talk starts at the 46:10 mark): https://vmware.webex.com/vmware/lsr.php?RCID=a51f9e6882f54ccab8b715c8c0162484
A new revision with updates was given at a meeting of the China Open Source Cloud League on May 20, 2016 in Beijing. The slides here on Slideshare represent that presentation.
What's New in Grizzly & Deploying OpenStack with PuppetMark Voelker
The document outlines the agenda for the May Triangle OpenStack Meetup, including:
- Welcome and introductions starting at 4:30pm
- Two technical talks from 4:45-5:30pm on new features in the Grizzly release of OpenStack and automating OpenStack with Puppet
- An open question and answer forum from 5:30-5:45pm
- Pizza will be served around 5:45pm
Bios of the three meetup organizers are also provided.
Considerations for Operating An OpenStack CloudMark Voelker
My talk from All Things Open 2014
Over the past four years, OpenStack has become a widely adopted cloud operating system. Cloud computing has made many tasks like creating new servers and networks easy for end users by creating abstractions above the infrastructure. However, cloud operators need to maintain not only the cloud operating system itself, but all of the underpinning systems beneath it. The challenges of managing a set of distributed systems isn’t small, but with proper tooling is well within reach. This talk will discuss considerations for cloud operators such as logging, storage, monitoring, high availability, configuration management with a focus on OpenStack clouds with a focus on open source solutions for common issues encountered when operating an OpenStack cloud. We’ll consider data gathered from the community and discuss “day 1″ and “day 2″ concerns as well as established patterns and technology choices among OpenStack deployers today.
OpenStack + VMware: Deploy, Upgrade, & Operate a Powerful Production OpenStac...Mark Voelker
In this sponsored session from the OpenStack Summit in Barcelona (October 2016), we discuss VMware Integrated OpenStack (VIO). We explain what VIO is and describe it's underpinning components, as well as how it solves real-world problems such as: how to make administering an OpenStack cloud easier, fast deployments and reliable, zero-workload-downtime upgrades, architectural decoupling of the control and data planes, and solving the "empty cloud" problem.
In this talk from the OpenStack Summit in Barcelona (October 2016), we explain the appetite for skipping OpenStack upstream releases in production deployments, talk about when skipping releases might or might not be right for your cloud deployment, and demonstrate how we successfully upgraded OpenStack clouds from IceHouse to Kilo (skipping Juno) and Kilo to Mitaka (skipping Liberty).
This document provides an overview and introduction to VMware Virtual SAN (VSAN). It discusses the VSAN architecture which uses SSDs for caching and HDDs for storage. It also covers how VSAN can be configured through storage policies assigned at the VM level. The document outlines how VSAN provides a software-defined storage solution that is hardware agnostic and can elastically scale storage performance and capacity by adding servers and disks.
vRealize Network Insight 3.3 provides enhanced visibility, troubleshooting, and control for virtual networks. It supports more NSX events, allows custom user-defined events, and provides more detailed micro-segmentation views. The update also improves event management with new filtering options and severity indicators. Support is expanded for features like NAT and integration with products including NSX 6.3 and Palo Alto Networks.
This document provides an introduction to virtualization. It defines virtualization as running multiple operating systems simultaneously on the same machine in isolation. A hypervisor is a software layer that sits between hardware and guest operating systems, allowing resources to be shared. There are two main types of hypervisors - bare-metal and hosted. Virtualization provides benefits like consolidation, redundancy, legacy system support, migration and centralized management. Key types of virtualization include server, desktop, application, memory, storage and network virtualization. Popular virtualization vendors for each type are also listed.
This document discusses Ebsco's implementation and use of OpenStack for their IT infrastructure. Some key points:
- Ebsco is a leading provider of online research content and discovery services for libraries. They needed a self-service infrastructure and full-stack automation for their development and operations teams.
- They chose OpenStack because it provides standardized compute, network and storage interfaces that allow various products to integrate easily. It also allows them to build an infrastructure as a service platform for their teams.
- Currently, Ebsco runs 3 OpenStack clouds supporting over 1,100 instances across development, testing and production environments. They have focused on skills training, vendor integration challenges, deployment difficulties and adoption rates over the course of
Interoperable Clouds and How to Build (or Buy) ThemMark Voelker
This document summarizes a presentation about interoperability between OpenStack and other open source infrastructure projects like Kubernetes. It discusses how the OpenStack Interoperability Working Group defines guidelines for compatibility between different OpenStack distributions. While no distribution will be identical, following these guidelines ensures core capabilities are supported across approved implementations. It encourages selecting technologies based on common interfaces like APIs, Terraform, or Kubernetes rather than any single vendor implementation to avoid lock-in and allow flexibility.
DevOps Fest 2020. Kohsuke Kawaguchi. GitOps, Jenkins X & the Future of CI/CDDevOps_Fest
CI/CD process has been something your DevOps engineer purpose-built for your team. But with Kubernetes & cloud-native, that’s becoming “legacy.” The rising level of platform abstraction allows all the good practices that the industry has developed over time to be integrated, hidden, and simplified behind just one practice called “GitOps.” That simplified world is what Jenkins X enables.
We will discuss GitOps, Jenkins X, and how that combination drastically simplifies cloud-native web app development. You’ll understand why traditional DevOps is not suitable in a Kubernetes and cloud-native world, explore GitOps principles and discover how they facilitate high-velocity app development.
And finally, Kohsuke will make a fool of himself by talking about the future — now that Jenkins X simplifies the CD process, where is the next frontier?
The document discusses the DefCore process, which defines the minimum standards required for products to be labeled "OpenStack". It aims to drive interoperability through common validation testing and implementation of core code sections. The process balances community and vendor input, with the community writing tests and vendors performing self-testing. It will approve guidelines every few months delineating required capabilities validated by tests as well as designated core code sections. It seeks community review of the 2015A guidelines before they are approved by the OpenStack Board to govern what functionality and code is required for OpenStack products and platforms.
A list of action items you want to keep in mind when you're devsecops'ing for your cloudnative environments. Given as a part of a talk on the Modern Security series (
https://info.signalsciences.com/securing-cloud-native-ten-tips-better-container-security).
Gartner Infrastructure and Operations Summit Berlin 2015 - DevOps JourneyKelly Looney
The document discusses the DevOps journey of a large online gaming company with separate sports betting and poker/casino divisions that were merged. It outlines the challenges of integrating different code bases and cultures. Key steps taken include adopting Agile, moving to Git/Jenkins, implementing monitoring with AppDynamics, and moving to containers. Automating testing environments and adopting continuous delivery principles helped improve quality and allow smaller, more frequent changes. Monitoring provided visibility and helped identify issues and refactoring needs. The changes helped bring development and operations teams together.
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown
This document provides an overview of DevOps principles and practices. It discusses the rise of DevOps as a movement to improve collaboration between development and operations teams. Common DevOps misconceptions are addressed. The CALMS framework of culture, automation, lean, measurement, and sharing is introduced as guiding principles. A roadmap for DevOps adoption is presented, along with take-home activities. The document aims to educate about DevOps in 3 sentences or less.
Cloud and Network Transformation using DevOps methodology : Cisco Live 2015Vimal Suba
Content presented as part of Cisco Live 2015 in San Diego
Why DevOps and what it means to be a DevOps-Enabled Organization?
Recommendations on Toolchain, Metrics framework, best practices and tips to help you embark on your IT Organization on DevOps journey
This document discusses challenges and lessons learned with OpenStack deployments and MySQL. It provides background on the author and their experience with OpenStack. Key points include that OpenStack is not simple to deploy and lacks capabilities required for production use out of the box. The document also discusses eNovance's OpenStack product, which aims to deliver a fully highly available OpenStack deployment with support for features like high availability, upgrades, and multi-data center capabilities. MySQL is commonly used as the database for OpenStack services, and the document shares experiences using Galera clustering for MySQL.
Continuous Delivery: How RightScale Releases WeeklyRightScale
Continuous delivery may be a natural for greenfield workloads, but how do you take an existing seven-year-old SaaS application and move from multi-month to weekly release cycles? Find out how our team — developers, QA, and ops — worked together to change our process and along the way changed their own ideas of what was possible.
This document discusses using both "sledgehammer" and "fine brush" approaches to quality assurance (QA). It describes how the AdoptOpenJDK Quality Assurance (AQA) project has progressively refined its QA process from initial brute force techniques to more targeted testing. The AQA project aims to ensure quality across the broadest range of OpenJDK platforms through an open, community-driven approach that evolves alongside the JDK.
Start with passing tests (tdd for bugs) v0.5 (22 sep 2016)Dinis Cruz
"Turning TDD upside down - For bugs, always start with a passing test" - Common workflow on TDD is to write failed tests. The problem with this approach is that it only works for a very specific scenario (when fixing bugs). This presentation will present a different workflow which will make the coding and testing of those tests much easier, faster, simpler, secure and thorough'
Presented at LSCC (London Software Craftsmanship Community) http://www.meetup.com/london-software-craftsmanship on sep 2016.
(SPOT205) 5 Lessons for Managing Massive IT Transformation ProjectsAmazon Web Services
Choice Hotels is undertaking a multiyear, $20 million project to recreate our core business engines on AWS. In trying to approach this complex undertaking, we determined that the project itself is a system too. You can apply principles of good architecture and design work in how you approach the project structure and management. Come to this talk by Choice Hotels’ CTO to learn five key lessons and 20 concrete takeaways that you can implement today to help your AWS projects succeed.
CarTrawler's Feature Team Architecture and Development Process Showcase by Lu...Lucas Sacramento
This document summarizes an architecture and development showcase. It discusses using a monorepo development approach, development process involving tech discussions, coding, and code reviews, and a pipeline involving linting, unit testing, static analysis, building, acceptance testing, visual regression testing, and performance auditing. It also discusses using containers and Kubernetes for container orchestration to provide benefits like provisioning, deployment, resource allocation, health monitoring, scaling, self-healing, automated rollouts and rollbacks, and service discovery/load balancing.
A presentation on the CarTrawler Next Generation Platform, giving an overview of the monorepo, development process, pipeline, container orchestration, and all the supporting tooling.
Innovate Better Through Machine data AnalyticsHal Rottenberg
This talk was presented at IP Expo Manchester in May, 2016. the themes discussed are:
- how does machine data relate to devops?
- how can tracking this data lead to better outcomes?
- what types of data are important to track?
Similar to InteropWG Intro & Vertical Programs (May. 2017) (20)
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
2. 2
Perhaps inherent in that ambition is the promise of interoperability.
Code against one set of capabilities and API’s, take your pick of many
public clouds, distributions, appliances, and services.
As it turns out, even clouds that are on some level the same
can look and act very differently.
OpenStack aims to be a “ubiquitous Open Source Cloud Computing platform that will meet the
needs of public and private clouds, regardless of size…”
3. 3
There are ~4,650 config options in the tc-approved-release OpenStack projects.
And ~1,073 policy.json configurations (as of late 2015).
OpenStack has a lot of nerd knobs that can
affect how a cloud behaves. In fact…
4. 4
You can also put things in front of OpenStack that change the behavior users
see…like firewalls.
…and load
balancers, API
gateways, SSL
configurations…
5. The mechanics of what’s under the hood may change behavior too…
(take image formats supported by various virt drivers & storage platforms for example) 5
6. 6
And of course different types of workloads
use the cloud in different ways…
8. Mark T. Voelker (@marktvoelker)
• OpenStack Architect @ VMware, Interop Working Group co-chair
• Fact: can be bribed with doughnuts
• In copious (hah!) spare time: OpenStack solutions, Big Data, Massively Scalable Data Centers, DevOps,
making sawdust with extreme prejudice, raising two great kids with my awesome wife in North Carolina
“A computer nerd….is somebody who uses a computer in order to use a computer.”
–Douglas Adams
9. 9
[note: this talk will be slightly more entertaining if you’re a science fiction fan…
…otherwise it will merely be somewhat informative.]
10. 10
Why Should Vendors Care
About Interoperability
Standards?
• It’s good for your users
• It helps you promote your product
• It helps applications be developed
for your platform
• It’s now required if you want to
call your product OpenStack.
11. 11
def list_images():
“”” A function to list images. Because all OpenStack Powered Platforms can do that…somehow.””"
if $cloud == ‘vendorA’:
# TODO: this also works for vendorX
list_images_via_nova_image_api()
elif $cloud == ‘vendorB’:
# TODO: this also worked for vendorY last week but now, um?
list_images_via_glance_v1()
elif $cloud == ‘vendorC’:
list_images_via_glance_v2()
else:
# I dunno what cloud this is, but it’s OpenStack Powered! So something must work.
# Resort to trial and error since we don’t know.
try:
list_images_via_nova_image_api()
except NopeError:
# D’oh, guess that wasn’t it…
try:
list_images_via_glance_v1()
except StillNopeError:
# Aww…well third time’s the charm?
try:
list_images_via_glance_v2()
except NopeNopeNopeError:
rage_quit()
This function could
also be called:
not_winning()
13. 13
Soon
Soon:
Want to prevent that?
When the community
works together with
the Interop Working
Group, we can.
To understand how,
you need to know how
OpenStack is
governed.
15. 15
The Technical Committee provides:
“technical leadership for OpenStack as
a whole…..enforces OpenStack ideals
(Openness, Transparency,
Commonality, Integration, Quality…),
decides on issues affecting multiple
projects…..”
16. 16
“The Board of Directors provides strategic & financial oversight of Foundation resources and staff.”
Which
includes
these things
openstack.org/marketplace
17. 17
Interop WG is a Board activity.
• One Director serves as co-chair, other
co-chair elected by participants.
• It’s work and procedures must ultimately
be approved by a vote of the Board, not
the +2’s of it’s most trusted reviewers.
• It produces “Guidelines”, not
infrastructure code.
• It can use the OpenStack trademark and
logo as both a carrot and stick.
• It can make requirements for products
that call themselves OpenStack.
18. 18
So what’s a Guideline, then?
• A list of Capabilities that products
must support.
• A list of Tests products must pass
to prove it.
• A list of Designated Sections of
OpenStack code they must use to
provide those Capabilities.
(also: a list of exceptions & things that
might be required in the future)
19. 19
What’s the cadence of Guidelines?
• New Guideline every 6 months
• Each Guideline covers 3 OpenStack releases
• Only the newest 2 can be used for new logo
program qualification
20. 20
Things you won’t find in
Interoperability Guidelines:
• Stuff that end users don’t
see or can’t use:
• Admin-only API’s
• RPC API’s
• DB Schema
• HA Requirements
• Stuff that’s intentionally
pluggable:
• Virt/net/storage drivers
• Middlewares
• Specific databases
• Stuff that doesn’t have tests
• Stuff that’s being
deprecated (usually…more
on that in a minute)
21. 21
How do we decide what
gets in?
10 Guiding Principles
12 Core Criteria
A giant list of tests
New Capabilities must be
“advisory” (non-required)
for one Guideline before
becoming required.
22. 22
Interop Criteria
(Currently all weighted fairly
equally with a few small
deviations)
https://github.com/openstack/interop/blob/master/doc/source/process/CoreCriteria.rst
26. 26
Say more to me about these tests….
• Must be under TC governance
• All tests today are in Tempest (per the TC’s request)
• Must work on all releases covered by a Guideline
• Typically run via the RefStack wrapper which reports results to
refstack.openstack.org and shows which Guidelines you meet
Details:
http://openstack.org/interop
http://refstack.openstack.org
27. 27
Sometimes things go amiss…
Tests can be “flagged” (not required
for the duration of the Guideline) in
some cases:
• Capability fails to meet Criteria
(e.g. was scored incorrectly)
• Test fails/is skipped due to an
accepted bug in the project
• Test fails/is skipped due to an
accepted bug in the test
• Test fails because it requires non-
required Capabilities
• Test reflects an implementation
choice that isn’t widely deployed
even though the Capability itself
is.
28. 28
When does all this happen?
• Summit-3 months: preliminary draft
• Summit-2 months: ID new Capabilities
• Summit-1 month: Score Capabilities
• Summit: “Solid” draft
• Summit+1 month: Self-testing
• Summit+2 months: Test Flagging
• Summit+3 months: Board Approval
(Note: 2015 was weird in that we had a very
accelerated schedule to get DefCore
bootstrapped…above is what it looks like
from now on.)
31. 31
• It didn’t meet Criteria
(scored too low)
• It wasn’t scored in time
(scoring is surprisingly hard
to get right)
• It was admin-only or driver-
specific
• That project isn’t yet widely
deployed
• There wasn’t a test for it
• It didn’t score highly across
all releases covered in that
Guideline
• Nobody brought it up yet
33. 33
I’m the Interop WG co-chair.
I have a blog post you should read!
http://markvoelker.github.io/blog/defcore-for-devs/
• Document it well
• Ensure it has usable tests
• Foster adoption among users,
SDK’s, & other projects
• Be patient: needs to be in 3
OpenStack releases
34. 34
Do we get to offer feedback?
Absolutely!
• Feedback built into Interop WG
scoring cycles
• Feedback encouraged for
Advisory capabilities
• Feedback encouraged via flag
requests
• Feedback via User Survey
• Feedback via RefStack
community-visible results (you may also buy me a beer & bend
my ear about interoperability anytime)
35. 35
How do I make RefStack work for me?
It’s actually not that hard.
Instructions here which boil down to:
1. Download refstack-client.
2. Run the “setup_env” script.
3. Configure tempest for your cloud.
4. Run refstack-client to execute tests.
5. Upload results to refstack.openstack.org and review.
36. 36
Why run all the tests &
upload results?
Because more data is
better.
This gives us additional data
about what works in your cloud.
With data from lots of clouds, we
can make better scoring
decisions in the future when
considering adding Capabilities
to Guidelines.
37. 37
What if I don’t pass all the
required tests?
Don’t panic.
• Figure out why some tests failed.
• Was it environmental (e.g. a timeout due to
storage being slow)? Tweaking tempest
config may help.
• Was it due to a bug in the test?
• Was it due to a bug in OpenStack?
• Do you have grounds for requesting a flag?
• Valid reasons for flagging a test and how to
do it can be found here.
• Talk to us!
• We have an interest in helping you succeed.
• interop@openstack.org is here to help!
• Catch us on IRC at #openstack-interop or
#openstack-refstack.
38. 38
What’s Next?
• Work begins on 2017.08
• More testing
• Vendors currently testing against just-released 2017.01
• Vertical Programs
• Example: what would “OpenStack Powered NFV” look like?
• New add-on programs and/or “vertical” programs
• Example: what would “OpenStack Powered Compute with
Database” look like?
• Could these be a conduit to projects defining (early on, for
themselves) what interoperability looks like to users of their
project?
39. 39
Sometimes the enemy is us.
• Sometimes projects are slow
to adopt support for each
others’ new API’s and features.
• Sometimes projects provide
multiple ways to do the same
things (and sometimes they’re
mutually exclusive).
• Sometimes we don’t have
good data about what’s really
supported.
• Sometimes tests use admin
credentials unnecessarily or
lump many Capabilities into
one test.
40. 40
For this to work, we have to communicate as one community.
• Board of Directors/Interop
Working Group
• Technical
Committee/technical
contributors
• End Users
• Vendors
• Ecosystem
42. 42
What interoperability issues
should I, an end user, watch
out for ?
Here’s that report again.
1. How we test interop
2. Variance in API evolution
3. External network connectivity
4. API and Policy discoverability
5. Understanding the Interop WG
50. 50
…are
probably a
bit different
than the one
you have on
your phone.
(or in your router,
submarine, cash
register, seatback
entertainment unit,
or drone)
51. 51
We still think of both
as “Linux.”
They’re just
specialized for
specific use cases.
We’re seeing
specialization in
OpenStack now too.
52. 52
Within products
addressing a
particular use case,
interoperability is
still useful and
important.
Otherwise things
might not behave
as expected when
moving from one
cloud or product to
another.
53. 53
We’re just getting started
designing vertical programs.
Much depends on the use case.
Some things a use case might
need:
• Capabilities not commonly
exposed in general purpose
compute clouds
• Specific attributes in the API
• Scenario tests (beyond API
availability, maybe beyond
Tempest)
• Specific control plane design
choices
• Performance criteria.
• Admin API’s
• Different OpenStack projects
54. 54
The key is to take the general
methodology and criteria we’ve
already developed….
...and apply them in a way that’s
specific to a vertical use case.
55. 55
• Same BoD approval
• Same schema
• Same general process
• Same criteria (?)
• Builds on Powered (?)
• Different tests
• Different reporting
• Different mechanics
56. 56
And of course it sometimes helps to work
with our friends in adjacent
communities…
57. 57
Some examples of
things a general-
purpose compute
clouds might not need
for interoperability that
an NFV cloud might:
• SR-IOV support
• High PPS network
dataplane rates
• Provider network
support
• NUMA topology
aware scheduling
• CPU pinning
• Active-active control
plane design
choices
58. 58
We’d like to get
moving quickly on
developing programs
for vertical use cases.
There seems to be
demand, and people
ready to help. NFV
seems like a good first
target.
Buckle up!
59. 59
I’ll be jumping in myself.
Speaking of which, we should really wrap up today’s
talk and get on with it…
60. Want to learn more?
• 2017.01 Guideline
• 2016.08 Guideline
• Next Guideline draft
• Public RefStack Server
• OpenStack Interop Homepage
• Core Criteria
• Interop WG procedural overview
• Lexicon of Interop WG terms
• Interop WG wiki & meeting Info
• How to submit patches
61. 61
“Do what I do. Hold on tight and pretend it’s a plan!”
Yes, the title is a Doctor Who quote. Get used to it, you’re going to be seeing a lot of Doctor Who in the next hour or so.
Example: the spring 2015 user survey revealed that 7% of production deployments include Sahara. So even though it’s been part of the old Integrated Release since Juno, we’re not likely to include it in a Guideline yet. In essence, most of the world doesn’t consider it a “core” part of the stack.
The Keystone v3 API made it’s first appearance in Grizzly. Neutronclient supported it in Juno.
Nova still talks to the Glance v1 API today even through v3 is now being planned and v2 is current.
You can’t simultaneously deploy nova-net and neutron.
You can attach instances directly to an externally-routable provider network, or you can use floating IP’s for external reachability.