If you missed our presentations at the OpenStack Summit in Atlanta, you have a second chance to see them with the videos bellow.

High Availability in Neutron – Getting the L3 Agent Right

Speakers: Emilien Macchi and Sylvain Afchain
Slides: Neutron-L3-HA-Summit-eNovance-template.pdf.

To provide public connectivity to virtual machines, you can install the Neutron L3 Agent which aims to connect your VM to external networks (Internet for example) through virtual routers and also connect VM between internal private networks.

Also, your VMs could be reachable from outside by using floating IP, thanks to NAT process to reach the VM. The L3 Agent was multi-node ready from Grizzly release, but if you lost an L3 agent node, you also lost virtual routers and then the external connectivity for virtual machines.
Until Icehouse, there was not proper way to bring L3 connectivity highly available without losing the agent scalability.

This talk will provide a view of the work which has been made on the L3 agent and the virtual routers during the last release regarding to the high availability. The High Availability of the L3 agent will ensure there will be no downtime between external and internal networks and between internal networks connectivity, even with the lost of one or more l3 nodes.
We will also see the new features that could be brought in the next release, which will improve routing scalability, especially for the east-west traffic.

Are Enterprises Ready for the OpenStack Transformation?

Speaker: Nick Barcet
Slides: http://fr.slideshare.net/NicolasBarcet/are-enterprises-ready-for-the-openstack-transformation

OpenStack is not product, it’s a process. Building an OpenStack cloud should never be the beginning nor the end of a cloud project. This is so because:

• OpenStack is not a product that tries to solve any one business problem in particular, but a technology that aims to be usable by as many as possible
• Since the beginning of computing, projects which include a culture shift require the for the enterprise processes to evolve too, and this is often the hardest part of a cloud project
• OpenStack is a growing technology, as are the requirements of users, and if you do not plan to make your cloud continuously evolve, you are as good not doing an enterprise cloud project

Based on our experience delivering cloud project to enterprises, this presentation will give some key learnings on what are the required steps to make sure that your enterprise is ready for the OpenStack transformation.

Delivering OpenStack Clouds as a Factory

Speaker: Nick Barcet
Slides: http://fr.slideshare.net/NicolasBarcet/building-cloudasa-cloudfactory-openstack-fr

“OpenStack is not a state, it’s a process.” Seeing how quickly OpenStack evolves, one should consider that setting up a cloud infrastructure is never done. The more you wait to do your updates, the more difficult these updates become. Since the whole system and its API have, by definition, been exposed to a large number of users; one cannot leave a cloud without security and maintenance updates. OpenStack deployments should therefore be conceived as a chain of continuous integration platforms that allows the operator to validate ongoing evolutions and fixes automatically, providing him with enough evidence to let his cloud be continuously deployed.

This presentation will describe how eNovance sets up such a chain for its deployments, what the advantages and challenges we encountered along the way.

How Do You Agile Your Global Team to Contribute to OpenStack

Speakers: Alexis Monville and Frédéric Lepied
Slides: http://www.slideshare.net/alexis/how-do-you-agile-your-global-team-to-contribute-to-openstack

These days everybody knows how to scale a distributed system all over the globe without any single point of failure and communicating between each others in a clustered way.

If you think about it, distributed servers are not so much different than distributed teams, they need to get along together and be synchronized.

But is it really? Human are humans after all and are not servers.

In this session we will go over how eNovance started growing up his development team in a distributed way following the agile’s values and principles. This session will explain how to schedule and iterate keeping the pace of Openstack releases. We will also cover how we organize our scrums, sprint planning, review, retrospective facing different time zones with our distributed teams.

How do you agile your global team to contribute to OpenStack is the talk for everyone who wants to scale agile in multiple distributed teams contributing upstream to Openstack and other open source projects.

WhatTheStack? A Tool Based on Tempest to Verify your Deployments

Speakers: Christian Schwede and Nick Barcet
Slides: whatthestack-using-tempest-for-testing.pdf

OpenStack service interoperability is becoming a major requirement for developers and users of public clouds. With more and more OpenStack-based deployments available to the public it is getting harder and harder to choose a vendor that ensures API interoperability. To make things worse, you might want to have some external testing for verification.
Luckily there is already an existing project that executes tests against the OpenStack API: Tempest. Tempest is used daily to test thousands of deployments, namely devstack in Zuul. It is used to verify patches for API interoperability and to check if a new patch doesn’t break existing functionality.
Experienced operators can configure and use Tempest to test not only a local devstack environment but their own deployment; however asking users to configure and test several OpenStack deployments is a tedious task.
We built a tool around OpenStack Tempest to simplify this process for users, developers, operators and distribution builders. whatthestack discovers common settings required to create a configuration for Tempest and executes Tempest tests against a given OpenStack deployment. A subset of Tempest tests is executed to verify common API interoperability; these tests do not require an administrator account and therefore are executable by regular users.

This session will explain in more details the objectives of whatthestack, as well as demonstrate it’s use. It will end with a 2 way forum to gather idea and potential feedback that we will use for future directions of the tool.

Extend Swift by Developing Your Own Middlewares

Speaker: Christian Schwede
Slides: developing-your-own-swift-middleware.pdf

OpenStack Swift already covers a broad range of use cases and fulfill requirements by operators and users – be it different authentication backends, support for 3rd party APIs or using different storage backends.

However, in some cases you might need a functionality that is currently missing in Swift. Swift uses wsgi middlewares for basic and optional functionalities which makes it easy to extend and make it fit to your needs.

This talk will give an overview on how Python wsgi middlewares are working in general and how to use them. After that a summary of already existing 3rd party middlewares for Swift will be given and we will have a look how to write your own Swift proxy server middlewares and tests to fulfill your needs. At the end you should be able to start writing your own middlewares based on the shown examples.

Public Cloud on OpenStack: The Challenge of Knowing What to Push to Production and How to

Speaker: Nick Barcet

Public Cloud on OpenStack: The Challenge of Knowing When and What to Push to Production
Everyone’s watching when you put your production cloud out for public consumption. There’s no room for error when customers are counting on you to deliver a stable, high-performance Infrastructure-as-a-Service. This panel covers the critical decisions that drive adoption of new features and releases of OpenStack and the things to consider when trading off between cutting edge features and stability. Learn how industry leading OpenStack-powered public cloud providers keep close to trunk through continuous integration continuous deployment (CICD) and other techniques.
Everyone’s watching when you put your production cloud out for public consumption. There’s no room for error when customers are counting on you to deliver a stable, high-performance Infrastructure-as-a-Service. This panel covers the critical decisions that drive adoption of new features and releases of OpenStack and the things to consider when trading off between cutting edge features and stability. Learn how industry leading OpenStack-powered public cloud providers set up OpenStack for public clouds, keep the software updated while maintaining high levels of availability. We’ve assembled a panel of operations and engineering leaders from several public cloud providers to provide an overview of their operations and answer your questions.

OpenStack and Ceph: the Winning Pair

Speaker: Sébastien Han
Slides: ceph_openstack_the_winning_pair.pdf

Ceph has become increasingly popular and saw several deployments inside and outside OpenStack. The community and Ceph itself has greatly matured.
Ceph is a fully open source distributed object store, network block device, and file system designed for reliability, performance,and scalability from terabytes to exabytes. Ceph utilizes a novel placement algorithm (CRUSH), active storage nodes, and peer-to-peer gossip protocols to avoid the scalability and reliability problems associated with centralized controllers and lookup tables.
The main goal of the talk is to convince those of you who aren’t already using Ceph as a storage backend for OpenStack to do so. I consider the Ceph technology to be the de facto storage backend for OpenStack for a lot of good reasons that I’ll expose during the talk.
Since the Icehouse OpenStack summit, we have been working really hard to improve the Ceph integration. Icehouse is definitely THE big release for OpenStack and Ceph.
In this session, Sebastien Han from eNovance will go through several subjects such as:

• Ceph overview
• Building a Ceph cluster – general considerations
• Why is Ceph so good with OpenStack?
• OpenStack and Ceph: 5 minutes quick start for developers
• Typical architecture designs
• State of the integration with OpenStack (icehouse best additions)
• Juno roadmap and beyond

OpenStack Swift as a Backend for Git

Speaker: Chmouel Boudjnah
Slides: http://fr.slideshare.net/chmouel/git-with-swift-atlanta-2014

Openstack Swift is an efficient way to store data and let you enjoy its data safety, high availability and horizontal scalability capabilities. Git is designed to store its objects using traditional block storage systems but they generally does not provided the same capabilities as Swift offers. Why not using Swift for storing Git repositories ?

This talk will give an overview of Git server side (what it is done when you fetch/push to a remote Git repository). After this general introduction we will explain why and how with extended a Python library called Dulwich (full python Git implementation) to be able to use a Git bare repositories stored in Swift. Furthermore we will talk about the eventual consistency of Swift and the impacts on the Git data model. At the end we will give you the resources to start trying Dulwich with a Swift backend.