Getting Started with OpenStack, Red Hat Summit 2016

This document provides an overview of the key components of network virtualization solutions. It begins with an introduction and agenda. The main body then discusses the following key components: decoupled control and data planes using SDN protocols like OpenFlow; a centralized network controller that maintains topology information; northbound programmatic APIs; virtualized network services like firewalls and load balancers; and the use of encapsulation protocols to provide network traffic isolation. It concludes with a brief introduction to VMware NSX as an example implementation of network virtualization.

As Infrastructure Architect at Essent Belgium, Michiel Van Wambeke will elaborate on their experiences within their cloud infrastructure at Essent.be

CAM - Cloud Automation Manager is a centralized and modular microservices plugins-based framework for DevOps and automation of Entereprise software development and service provider cloud operations using a single pane of glass using opensource architecture

Mellanox provides open Ethernet switches that decouple switch software and hardware, allowing users freedom to choose any software to run on any hardware. This includes open source options like Quagga and SONiC. Mellanox's SN series switches run on ONIE, an open source bootloader that allows installation of any network OS. Mellanox's switch software drivers provide standard APIs like SAI and SDK that abstract the hardware and allow network OSes to run. This enables the use of switches with Linux and popular open source networking software.

The document discusses Cloud Development Kit (CDK) as the next big thing for infrastructure as code (IaC). It provides an overview of IaC and some of its challenges around misconfiguration and security. The introduction of CDK aims to address these challenges by allowing IaC to be implemented as a programming language, inheriting strengths like object-oriented programming and better testing capabilities. Examples are shown for CDK on AWS, Terraform, and Kubernetes to demonstrate how infrastructure can be defined and provisioned code. The document concludes with a proposed practice of using CDK to define cloud infrastructure for a micro-services system from business applications.

During this session, you'll have a look at how to realize a Microservices architecture (MSA) using the latest Microsoft technologies available. We will start with the fundamental theories behind MSA and show you how this can be realized with Microsoft technologies such as Azure Service Fabric. This session is a real must-see for any developer that wants to stay ahead of the curve in modern architectures

Microservices allow for extensible app architecture and a vendor-agnostic, scalable infrastructure. While microservices simplify app deployments, they come at a price: because they’re so fragmented, it is more difficult to track and manage all the independent, yet interconnected components of an app. All this information (requirements, code, test cases and results, build artifacts, and deployment blueprints) needs to live somewhere and most importantly be versioned. Using a real example and a live demonstration of Perforce Helix, Docker and Selenium, get best practices and tips for enabling a robust, scalable and extensible pipeline to support today’s modern app delivery.

This document outlines a presentation on service meshes and Istio. It discusses microservices architectures and the challenges of microservices, introduces service meshes as a solution to these challenges, and provides an overview of Istio's architecture and key capabilities. The presentation uses the Bookinfo sample application to demonstrate basic traffic routing and shifting with Istio. It also allows time for questions at the end.

The document discusses a panel at a conference on Software Defined Networking (SDN). The panel will discuss whether SDN is a promise or a reality, and features panelists from industry and academia including representatives from Datacom, UFSCar, Algar, and NIC.BR.

Workshop presentation at SALAD 2015 workshop based on this paper: http://ceur-ws.org/Vol-1359/paper1.pdf

While service meshes may be the next "big thing" in microservices, the concept isn't new. Classical SOA attempted to implement similar technology for abstracting and managing all aspects of service-to-service communication, and this was often realized as the much-maligned Enterprise Service Bus (ESB). Several years ago similar technology emerged from the microservice innovators, including Airbnb (SmartStack for service discovery), Netflix (Prana integration sidecars), and Twitter (Finagle for extensible RPC), and these technologies have now converged into the service meshes we are currently seeing being deployed. In this talk, Daniel Bryant will share with you what service meshes are, why they're well-suited for microservice deployments, and how best to use a service mesh when you're deploying microservices. This presentation begins with a brief history of the development of service meshes, and the motivations of the unicorn organisations that developed them. From there, you'll learn about some of the currently available implementations that are targeting microservice deployments, such as Istio/Envoy, Linkerd, and NGINX Plus

Packet is a bare metal cloud platform that provisions premium server configurations within 5 minutes globally. It offers the best of cloud (fast deployment, flexible pricing, global footprint) combined with colocation benefits (premium hardware, best networks, no co-tenancy). Packet aims to simplify infrastructure through next-gen software and hardware, with curated server types available starting at $0.05/hour and a performance network optimized for optimal routes and access. It integrates with leading platforms and offers private deployments, with a focus on containers and future technologies.

This document discusses virtual private networks (VPNs) and provides information on various VPN types and implementations. It begins by explaining that VPNs are used to connect private networks via the internet in a secure manner. It then covers IP-based VPNs and their components like encryption and encapsulation. The document also summarizes VPN characteristics, types including server, firewall and router-based, architectures, best practices, and different implementation methods such as IPSec and SSL-based VPNs.

The service mesh is an infrastructure component that helps manage services running within our clusters. Without any changes to service or application code, solutions like Istio and Linkerd provide features to manage container deployments at scale. With Istio we get traffic management, security, rate limiting, monitoring, and many more things out of the box. We will discuss these solutions and some of their features at a high level, then roll in some specific demonstrations of using a service mesh to route and shift service traffic, easily manage deployments and test our services with micro benchmarks and fault injection.

In this position paper, we discuss our experiences with a lightweight Web of Things (WoT) toolkit and use those experiences to explore what an effective WoT toolkit looks like. We argue that while the WoT community has experimented, like us, with a variety of toolkits, it hasn’t yet found one that appeals sufficiently to a broad range of developers. This failure, we believe, is hindering the adoption of the WoT and the growth of the community. We conclude the paper with a set of open questions, which, although not exhaustive, are aimed at opening up a community discussion on the needs of developers and how best the community can meet those needs and so further the adoption of the WoT. In essence, we believe that the time may be right to begin to agree on some basic functionality and approaches to WoT toolkits.