In this session, we will quickly run through the Summit schedule, highlights, housekeeping items and logistics. It will also introduce the Active Technical Contributors to the Design Summit working sessions, which will run Monday - Thursday.
The keynote presentations will be Tuesday and Wednesday morning, starting at 9 am.
Personas were made famous by Alan Moore in "The Inmates are Running the Asylum," a seminal book on user interface design for computer programmers. They have been used for decades in the marketing industry, in user experience design, and in product planning to help target specific market segments with features, ads, and product design.
Personas help you frame feature discussions while developing your software, guide your communication and event strategy, and ultimately help you to have a more popular, better project. As the OpenStack project evolves beyond its original base and seeks to engage with a broader user community, understanding the profile of OpenStack users becomes critical in increasing participation and thus improving the project.
This session will cover the basics of:
* What is a persona and why should I care?
* How do I come up with persona(s) for my project?
* What can I do with personas?
This session will be useful to those interested in better understanding their target audiences, and specifically those seeking to grow a community around an open source project.
Is this your first OpenStack summit? Unlike most conferences, you are invited to participate and play an active role. But... where to start? The rationale and the organization that allows such a unique collaborative design will be explained. This is your chance to get answers and get the best of it!
During this session we will let the attendants know some details about the summit, including who will be attending, different tracks and purposes, which sessions/talks are the most suitable for beginners and how they can participate. This short introduction will be followed by a a lively presentation of the most common situations and how to behave when facing them. It will be a miniature experience of a first participation to the summit.
Currently we have an archetecture that should support scalling but
some code is missing.
How does the heat-api find the correct engine to talk to?
How would a "heat list" work?
(Session proposed by Angus Salkeld)
In this session, I will talk about some of the problems we face in deploying openstack by using openstack. I'll point at areas where the bare metal driver needs better integration with other services (eg. Quantum and Cinder), how we really need an inventory database (I'm looking at you, HealthNMon), how the Nova scheduler needs to be aware of hardware, and how Heat is taking over the world. I might even propose that it's possible to bootstrap yourself right out of your own boots!
(Session proposed by Devananda van der Veen)
OpenStack supports many different compute, storage and networking environments for various deployment models. Over the past 15 years, major investments went into building Fibre Channel storage infrastructures. Are you asking yourself “How can I extend OpenStack to utilize my existing FC SAN environment or does OpenStack block storage support FC storage?”
Attend this session to learn about an initiative supported by a group of tier-one, FC-SAN, vendors including Brocade, HP, EMC, and IBM, to make FC technology relevant in an OpenStack environment. Two new Fiber Channel blueprints and their implementations for the Grizzly release and beyond as well as considerations around managing FC SAN volumes and zones from an OpenStack orchestration perspective will be covered. If you are considering moving your dev/test or storage/backup or business applications to the cloud and extending your future FC private cloud environment to leverage OpenStack then plan on attending this discussion.
Upgrade Orchestrations are essential! We're both delighted and frustrated by OpenStack's pace of innovation because by the time we get the current release working then new hotness arrives. Last year, it was enough to just install OpenStack, but now we think it's required to have an upgrade plan. As the founders of Crowbar, we are leaders in the cookbook design for OpenStack and have a lot of experience with orchestration for OpenStack deployments. This community discussion about our proposed upgrade pattern reviews our devops recommendations (do NOT mix cookbooks for multiple releases) and orchestration design (dedicated cookbooks for orchestration). If you're interested in cookbooks that are testable and minimize complexity then this session is for you! We want orchestrations between versions that can focus on the specific use-cases around the migration scenarios like incremental, fastest-possible, change of operating system, or VM migration. If you agree that migrations between versions are also very important then look no farther!
In this session I would like to talk about a Cloud Monitoring Solution for OpenStack Cloud using “Healthnmon” which is currently available under “stackforge”. Healthnmon intends to provide Cloud Monitoring service for OpenStack Cloud Resources and Infrastructure with a pluggable framework for
Healthnmon is targeted for private, public and hybrid cloud solutions, covering KVM, Hyper-V and ESX hypervisor technologies. Healthnmon solution aims at providing an architecture that supports the infrastructure management, getting insights into the underlying hypervisor features, topology details, Cloud resource and application monitoring.
A Healthnmon driver implementation collects the Cloud Resource Inventory, Usage, Alerts. The session will cover the following
Representing the user committee, we will review the current status of the OpenStack user committee, its scope, the plans for next year along with the input from the user groups, industry sectors and foundation members.
Discussions on the best approaches to identify user requirements, profile the user community and continue supporting the ongoing user activities around OpenStack will be welcome. Some initial ideas are available at https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8Y qEToyo/edit
This session is a 201 level technical deep dive on the VMware/Nicira Network Virtualization Platform (NVP). NVP is a virtual networking platform powering many OpenStack production environments as the networking engine behind Quantum. In this session we’ll explore the distributed systems architecture of the NVP Controller Cluster, the core functionality and behavior of NVP’s primary system components, and the logical networking devices and security tools NVP produces for consumption. High availability deployments, and packet flows for common scenarios will be discussed. And finally, we’ll take a look at how the physical network fabric can be architected for NVP deployments.
Some of the session topics include:
System Components Review
NVP Controller Cluster Hypervisor Nodes NVP Gateway Nodes NVP Service Nodes
NVP Controller Cluster
Scale-out control plane & HA control and management channels
NVP enabled Hypervisors
Scale-out data plane
NVP Security Groups
NVP Logical Network Devices
QoS, NA T, Monitoring, Security
Scale-out & HA
Connecting to external networks
Physical network design with NVP
Typical cloud deployments - be it Openstack, Eucalyptus etc - have a separate control layer installed and upgraded using separate tools (which might be hand-configured PXE + preseeding, Crowbar, Cobbler, Orchestra/MAAS, FAI etc). As a result you have two distinct provisioning systems in play, which allows for more operator error and requires increased special cases in automation.
Using Openstack’s bare-metal hypervisor, we are building a fully self contained cloud, where the control layer for the cloud is itself deployed and upgraded via the same cloud API.
Come hear me talk about the challenges involved in bootstrapping and operating such an environment, the benefits it can bring and what you can do with it!
A predecessor of this talk was given at Linux.conf.au in January of this year where it was well received.
Cloud Foundry is an open source platform as a service (PaaS), providing a choice of clouds, developer frameworks and application services. Cloud Foundry makes it faster and easier to build, test, deploy and scale applications. Today's enterprises are looking to add PaaS capabilities to their private and public cloud infrastructure to decrease time to market for their applications and increase their developer productivity. This session will cover the natural synergy between the leading open PaaS solution, CloudFoundry, and the industry's leading open IaaS, OpenStack.
Dekel Tankel, Director of Product Marketing for Cloud Foundry, will present a broad introduction to Cloud Foundry, its core features and unique position in the PaaS landscape. Ferran Rodenas, Staff Engineer for Cloud Foundry, will discuss how the Cloud Foundry operational management tool, BOSH, interfaces with OpenStack to run PaaS on a wide range of infrastructure. If you are interested in PaaS, Cloud Foundry, or how the OpenStack ecosystem is enabling a new breed of cloud abstraction, then be sure to attend this session.
In the summer of 1787, a community of diverse individuals with a common challenge met in Philadelphia, Pennsylvania to discuss their problems with the Articles of Confederation and work towards a better outcome.
The attendees desired that the different states better understand and communicate with each other, and so they debated how best to do something new while organizing a framework for the entities which were represented and those new ones which were to come. The result of those discussions became the U.S. Constitution which has stood for over 225 years.
Come discover the similarities between Open Source and OpenStack communities and the Constitutional Convention over 200 years ago and what lessons there might be from history for our community.
OpenStack has evolved quickly but it can be improved with management tools. We’ll explore dashboards and API management of OpenStack private clouds. We’ll compare the advantages of management at different layers--the cloud, the infrastructure and the applications.
OpenStack and KVM/QEMU support a cornucopia of image and disk formats. With so many options it can be difficult to understand all the various trade-offs of these formats.
We will explore some of the more common image formats and disk formats and their trade-offs. We will cover tips and tricks for converting image formats, and working with these images directly. Additionally we will dive into how nova, libvirt, and KVM interact with these formats when doing various operations such as snapshoting and image resizing. We will look at best practices for configuring the guest operating systems such as default login credentials, network configuration, and device/performance optimization. Finally we will look at how to pre-install tools to assist in configuring the OS at VM creation as well as how to interact with the metadata API.
Contrail (http://contrail-project.eu) is a running FP7 EU research project. The main achievement of the project will be a tightly integrated software stack in open source including a comprehensive set of system, runtime and high level services providing standardized interfaces for supporting cooperation and resource sharing over Cloud federations. The main contribution of CONTRAIL is an integrated approach to virtualization, offering Infrastructure-as-a-Service, services for IaaS Cloud Federation, and Platform-as-a- Service. It aims at equalling current commercial Clouds, and surpassing them in a number of selected key domains to facilitate industrial up-take of Federated Cloud computing.
We would like to present the current status of the project as well as expected final results, focusing on Cloud Federation and security aspects.
In the first part of the presentation, architecture of the Contrail software stack is given, with short introduction to each of the main components and their interaction/role in the overall picture. These include the description of:
In the second part of the presentation a more detailed workflow of information is provided with the focus on the role and the benefits of the Federation. We will provide an overview how deployment documents (like SLA and OVF) are used, how providers are selected and SLA negotiation process is started. The deployment document is then pushed to the provider's layer where it is deployed to the reserved/free infrastructure. Last, we touch how the application is being monitored and how SLA violations are being handled.
In the last, third part, we focus on security issues that need to be solved when Cloud Federation is introduced. Our approach has been to make use of external components (such as an XACML implementation, SAML, OAuth and OpenID libraries), combined with components developed by the project when no external component is available. By maintaining modularity and loose coupling, we ensure maximal reusability of components, as well as leave the option to replace components. Together, these components form a framework for federated identity management and delegation framework in federated environment. We are promoting the reuse of this framework with other projects, as well as the reuse of individual components. Broadly, the security components in Contrail consist of: federation database provided through federation API, identity provider and attribute authority, CA Server, OAuth components, Virtual Infrastructure Network’s certificate agency, and Usage Control Authorization Service.
During the presentation we will also focus on technical problems we encountered during the development, such as the integration of the developed components, and remaining technical open issues yet to be solved, e.g. aggregation of monitoring/accounting (big) data, and delegation process within Virtual Infrastructures Networks (Contrail’s SDN solution).
A Lightning talk is a short presentation, no longer than 5 minutes. Unlike other presentations at the OpenStack Summit. the lightning talks are unstructured and can be about anything: from code, to running, to any hobby you may have. You can use slides but the 5 minutes need to take into account setting up of your equipment.
You sign up for giving the talk the same day you'll want to deliver it. Participate to the opening sessions every day for more details.
Be creative and have fun.
Becoming an OpenStack contributor is easy, people are welcoming, and it's a rewarding experience. To the point that we forget that it's worth training for it. Running is easy too. But if you want to go to the Olympics or get sponsored, you better learn and train for them.
Ceilometer was a deliberate contribution to OpenStack: Nick Barcet and I started careful planning for it in March 2012. One summit and twelve man-months of work later, it has become an OpenStack incubated project.
In November 2012 twelve computer science students at the Université du Litoral in the north of France contributed to OpenStack for the first time. For half of them it was their first exposure to the social dynamics of Free Software contributions. It took a few hours of their time, and you could feel, even through IRC, that it was a defining moment for their future professional life.
Nick Barcet's happiness when Ceilometer became an incubated project under his leadership is very much like the sparkle that was in William Oprandi's eyes when his documentation patch got merged into OpenStack.
Will William Oprandi need twenty years of experience to go from contributing a one-liner to driving a new component in OpenStack? Upstream University ( http://upstream-university.org/ ) was funded by the Free Software Foundation France shortly after the April 2012 OpenStack summit to speed up the process, and enable even a skilled contributor to level up. It celebrates its first anniversary with a training session ( http://upstream-university.org/news/2013/02/11/upstream-university-openstack-summit/ ) dedicated to OpenStack in Portland, just before the summit. Feel free to apply to the April 13th session (http://upstream-university.org/apply/ ).
In this panel, members from AMD, Arista, Brocade, EMC, HortonWorks, NetApp and Rackspace will discuss the Enterprise OpenStack ecosystem and speak about benefits and motives for making OpenStack a core part of their product offering.
Synopsis: There is no easy answer or magic solution when architecting your private cloud. OpenStack is flexible and can be designed in many ways which can be a blessing or a curse. The goal of this talk is to provide guidance on how to start thinking about your private cloud architecture.
I am continuing this series from my operational talks at the Grizzly Summit and would like to make this a standard talk at every summit. We've been working with Folsom for 6 months and will be updated as such.
1. Build with the end in mind (don't paint yourself into an architectural corner)
2. Images and Storage
3. Architecture examples and thoughts for the following environment sizes: a. 1-20 physical nodes
b. 20-100 physical nodes
4. Performance Considerations and Bottlenecks
5. Lessons Learned
6. Operational updates
7. Q/A and Community Input
In our internal research at Rackspace, the number one customer concern around security is Data Protection. While there are many aspects to protecting customer data, encryption is typically a key part of most solutions. This importance can be seen in every compliance regime and a large suite of encryption providers, both open-source and commercial. However, these sources tend to lack technical implementation detail, especially around the hardest part of designing an encryption scheme, key management.
This presentation will cover Cloud Keep, an open source project sponsored by Rackspace to build a secure, Cloud-ready key management solution. We hope to solve a need for our customers as well as other OpenStack projects, several of which have published blueprints around encryption recently (Cinder: https://blueprints.launchpad.net/nova/+spec/encrypt-cinder-volumes, Swift:
https://blueprints.launchpad.net/swift/+spec/encrypted-objects). We will walk through our plans for the system, its technical architecture and demonstrate our current proof of concept implementation.
In this session, we'll discuss experiences to date and near-term plans for expanding the community through user groups and universities.
Network virtualization has become a very hot topic over the last year. What began as an intriguing piece of technology is quickly becoming a fundamental requirement of scalable, next generation cloud infrastructure. Some of the top developers in this space including Big Switch Networks, Midokura, NEC, and NTT/Ryu
will join an industry panel to discuss the present and future of network virtualization software. Some of the topics that may be discussed include:
Use cases / reasons addressed by network virtualization technology
Current state of technology adoption
Emerging technologies (VXLAN, NVGRE, OpenFlow, etc.), hardware changes, Quantum development and integration, etc.
Impact of open source
Come join us to learn where network virtualization is going!
OpenStack is now installed. Now how do you operate it? How do you perform upgrades? Join Director of Software Development Jason Cannavale, as he demonstrates and discusses the Rackspace Private Cloud approach to operating an OpenStack powered cloud and simplifying the operator experience.
With two public cloud services in production, one at Rackspace and another at HP, OpenStack Project Reddwarf (http://wiki.openstack.org/Reddwarf) is increasing the value of both OpenStack and the affiliated project ecosystem. Since the last summit, we've increased community collaboration and accelerated development to make Reddwarf easier to consume and develop, as well as added many new features! Join Rackspace and HP as we discuss the value Reddwarf brings to Openstack, the progress we've made, the challenges we have faced, and our vision for the future. In this session, you will get a chance to hear how Reddwarf simplifies the management and maintenance of database systems in the cloud, understand how you can begin to leverage it, and learn how you can become active in the community.
OpenStack has shattered adoption benchmarks set by previous open source projects and gained acceptance as the de facto standard for open source public and private clouds. As the global demand for OpenStack expertise increases, employers are finding it difficult to recruit talent, which is slowing down the ability for organizations to adopt and implement OpenStack and supporting tools and services. For the community and the project to continue to flourish, an effort must be made not only to focus on creating the next wave of OpenStack experts, but to enable application developers to build and deploy on the plethora of public and private OpenStack clouds coming in the next few years.
As a follow-up to last year's successful OpenStack Careers Panel, come join Rackspace Cloud Evangelista Niki Acosta, as she shares her thoughts on the OpenStack talent gap and what the community must do-- short term and long term-- to accelerate adoption and usage of OpenStack-powered public and private clouds.
How do you design and deploy a hybrid cloud application service using Openstack, VMware Vcenter and HP Public Cloud Service? How do you automatically scale your multi-tier application to respond
to peak demand?
This presentation will focus on the architecture blueprint and best practices for designing a scalable hybrid cloud application service using Openstack API and HP Cloud technology components.
It will also highlight the following aspects:
-Application resource management
-Orchestration of an application deployment on top of Openstack cloud -Performance and Security considerations
Ceilometer is now one year old, and we just delivered our first synchronized release with OpenStack, our second official release.
During the past 6 months, and as a follow up to the intense discussions we had at the last summit, we delivered a much more robust
solution which perimeter and architecture has been extended from just metering to metric gathering at large accross all OpenStack projects.
This talk will first shortly go back on the project history, then explain the architecture evolution and uses cases it now permit and will close by explaining how you can put Ceilometer into action on your own projects.
Legal: Discussion around legal topics for companies contributing to or consuming the OpenStack software
In this 90-minute session, we'll explore the new OpenStack Community Activity Board, as well as facilitate an overall discussion about community metrics and other quantitative ways to measure who built Grizzly.
RedHat has created it's own OpenStack distribution that is now in preview and still a bit rough around the edges, but promises to include what is needed to deploy & evaluate a truly & complete Open Cloud environment. In addition, Red Hat wants there to be a widely used open-source community developed PaaS model for the cloud which includes being open to participation by a community of peers.
To really create a open cloud environment and to make it useful, you need to complete the stack with an PaaS. Just getting a cloud environment up and running is no longer enough. The challenge that OpenStack faces is how to get people, applications and services working on OpenStack out of the box.
One approach to the problem is to combining all the necessary pieces that go into building an OpenStack cloud (compute, storage, networking, management) with a platform as a service (PaaS) into your OpenStack distribution.
OpenShift Origin project is licensed under the Apache License 2.0, a permissive and widely-used open source license, which was selected so that the code would be available for use by the broadest range of
individuals and organizations. This is the same license chosen by the OpenStack project, for much the same reason. This license is already well known and understood by individuals and organizations already involved in cloud computing and in enterprise scale open source development.
In this session, I'll discuss RedHat's efforts with OpenStack, Fedora, & OpenShift Origin to create a more complete OpenStack distribution. Our community initiatives to ensure Origin easily and seamlessly integrates on any OpenStack distribution and how to you can add Origin into your own OpenStack distributions.
Boris from Russia here... We do much OpenStack at Mirantis. Much customer ask us to make cloud controller is highly available. Also much customer is cheap and ask only free, open source stuff in their cloud. At Mirantis we like make customer happy, so we make puppet recipe to make very highly available OpenStack for free. In this talk I make simple demonstration that even a goat that had a lot of vodka can understand how is use open puppet recipes to make highly available OpenStack and pay zero rubles to anyone. Also, a goat.
We will continue the 90-minute session, we'll explore the new OpenStack Community Activity Board, as well as facilitate an overall discussion about community metrics and other quantitative ways to measure development activities of OpenStack.
IBM has built its cloud strategy around OpenStack. As such IBM is investing to make OpenStack good enough for a broad range of customers. Likewise, IBM is providing proprietary value add via well designed OpenStack extension points and by building additional capabilities above the OpenStack IaaS.
This presentation will introduce IBM's new suite of cloud product offerings with a deep dive into some of the key areas which extend the open source projects. Likewise we'll describe the capabilities that are layered above OpenStack which can interoperate with other OpenStack compatible clouds, both on and off premises.
We'll show how IBM's breadth of technologies developed internally and acquired are being integrated into the OpenStack ecosystem. Finally, we'll introduce an online marketplace for everything OpenStack from free and open source images and scripts, to chef cookbooks, to commercial automation assets.
The open source configuration management and automation framework Chef is used to deploy and manage many large public and private installations of OpenStack and supports a wide variety of deployment scenarios. Chef for OpenStack is a project based on the healthy exchange of code, ideas and documentation for deploying and operating OpenStack with Chef. With involvement from Intel, AT&T, Dell, HP,
Rackspace and many others there is a community of collaboration between users, developers and operators. This session will discuss the currently available resources and documentation, the evolution and layout of the project and the roadmap going forward.
Grizzly Revolution! OpenStack Summit Kickoff Party
When: Monday/April 15, 2013/6:30-8:30PM
Where: Leftbank Annex at 101 North Weidler Street, Portland
What: Ample food, open bar, DJ, magicians and more
RSVP here: http://openstacksummitkickoffportland2013.eventbrite.com/#
YOU LIKE PARTY… WE LIKE PARTY, ALSO. ESPECIALLY TO DEPLOY BEAR, FOOD AND DRINK MUCH. JOIN OTHER CLOUDING PEOPLES TO MAKE PARTY FOR KICKOFF OF SUMMIT AT PORTLAND 2013 AND WELCOME GRIZZLY REVOLUTION 2013 AND CLOUD OF OPENSTACK. ALSO, FUN.
It’s back! The 2013 OpenStack Summit Kickoff Party is hosted once again by Mirantis, with co-sponsorship by Dell.
Celebrate the Grizzly Revolution 2013, the explosive growth of OpenStack and the Portland Summit, and while we're at it, start lubricating the machinery for Havana.
RSVP here: http://redhatpartyopenstacksummit.eventbrite.com/#
Join us at Spirit of 77 (across the street from the Convention Center) from 8:30-10:30 p.m. on Monday, April 15th for great food, drinks, and giveaways.
Party limited to the first 400 people.
OpenStack is more than just software, it's a community and platform ecosystem. In this session, Jonathan and special guests will cover the forces that impact platform success, as well as the latest stats and upates on the community front.
Come early - you won't want to miss the first few minutes!
Over the past three years, interest in OpenStack has evolved from developers to early adopters and users. Business users are now running OpenStack to meet real business needs. The more they work with OpenStack, the more they ask for new features and configurations. Some are even contributing code back to the community. In this keynote, Rackspace SVP and GM Jim Curry teams up with HubSpot CIO Jim O'Neill to present HubSpot's journey into OpenStack and the business advantages it has produced.
HubSpot is an all-in-one marketing Software as-a-Service set of solutions that includes blogging, analytics, social media, email, automation, keyword research functions and more. The company serves more than 8,600 companies in 56 countries worldwide.
Find out why HubSpot loves OpenStack and see their live demo as an OpenStack user take center stage.
Brian will talk about why Red Hat gravitated to OpenStack, and how we are committed to bringing a community to subscription model around the technology that aims to redefine IT.
Samsung SDS will present a case study on using OpenStack to support its massive mobile ecosystem.
Topics will include:
1. Cloud services based on smart devices and ecosystem
2. Hybrid Architecture and its solutions
3. Collaboration with Rightscale and Canonical partners
4. Lessons Learned
How can Hadoop take advantage of OpenStack and how can the OpenStack meet the needs of a demanding Hadoop cluster? In this session, we will briefly look at the Hadoop’s design decisions; come up with the best practices for deploying and running Hadoop on OpenStack and some of the challenges around it. We’ll also look at the ongoing work in the Hadoop and OpenStack community, and explore how we can make OpenStack a better platform for Hadoop and big data.
Building upon his popular blog posts and diagrams (http://ken.pepple.info), Ken will walk through the architecture of OpenStack Grizzly and describe it's key software components and important interactions with a special focus on recent changes. After finishing with the software architecture, he will discuss common physical design patterns available for large scale deployments.
A lot of effort has gone into cloud storage peformance benchmarking, both of swift and other cloud stacks and part of the result is a lot of confusion in the numbers, in large part because there is no standard. This is further complicated because some implementations are written in java, some in python and some in raw curl. Furthermore, the underlying libraries themselves can cause variances as they do not all use the same buffer sizes, enable/disable ssl-compression and probably other parameters as well.
I would like to talk about our benchmarking methodologies at HP as well as describe a tool suite I've developed that implements them and share some results of benchmarking our own OpenStack implementation. One thing I've discovered over previous months of testing is that both latency and cpu overhead can have a major impact on performance and those are captured as well, something most tools typically don't report.
The tools are written in python and use the OpenStack python-swiftclient library.
The OpenStack project does an insane amount of automated testing as part of the development cycle, but up until now there has been no corresponding testing that can be performed against running public clouds. While we want to do that, before we can test other people's clouds for compatibility, we need to be able to express what it is they need to be compatible with.
It turns out that OpenStack is rich enough now to express a reference implementation in terms of itself, using heat templates. Some people think that's a great end to itself - deploy your OpenStack using OpenStack - but others are not quite as sure about that yet, and have significant investment in things like chef, puppet, crowbar or cobbler. To meet the needs of expressing a useful set of testable information and not leave that specification as an academic exercise, or as the recipient of more tool wars - we've come up with a plan to have the heat templates describe the state, the "what" if you will, and to describe a clear boundary line across which metadata is passed to the tools on the individual nodes that will turn that metadata into configuration.
Over the course of the talk, we'll discuss:
Re-launched in 2002, BestBuy.com has grown to be the third most visited retail e-commerce site for the US holiday season. Facing increasing traffic and continued growth, BestBuy.com has engaged in an effort to re-architect and re-platform the site. A key component of these re-platform efforts is the hyper-scale CDC (Continuous Delivery Cloud). The CDC, based on the Openstack Essex release powers 40+ development teams today and is an innovation catalyst which enables thousands of automated tests running each day, early integration, and R&D for cloud deployments.
In this session we'll cover:
Using OpenStack in the context of a cloud service provider carries some considerations. A key differentiator is user experience and in order to provide as a service.
In this session we will discuss the key differentiations required from a portal, based on the target audiences of the platform, a reference architecture for the inclusion of business support services, key OpenStack components and how they are included in this architecture and some best practices for improving user experiences around OpenStack.
Charles Babbage's Difference Engine amazed Ada Lovelace with its unprecedented engineering feats just like OpenStack amazes people today. We have some stories to share about learning, exploring new territory and making new connections. This story is about newcomers working on OpenStack as interns. Three were in the GNOME Outreach Program for Women from January to March. One has been an intern twice at two different OpenStack companies.
For the Outreach Program for Women, three mentors worked with interns; one from the Image service (glance) project, one from the Dashboard (horizon) project, and one from the documentation project. For the company internships, mentors at the company worked with the intern. We want to share their stories so you can learn about our current OpenStack internships and future plans for such programs. We will talk about what they worked on while interning, what struggles they faced while learning everything about OpenStack, and where they want to go from here. We can provide metrics that show the impact of involving women in Open Source, and metrics about the impact these interns have on the projects. We want to describe the future vision for internship programs based on the lessons learned recently.
If you are an organization looking to hire OpenStack interns, or a potential intern seeking an internship, this session is for you.
Let’s discuss Hadoop for OpenStack log analysis! Hadoop can support operational monitoring, troubleshooting, and capacity planning in a consistent and open way. We’ll share the work we’ve started, and lead an interactive discussion of different approaches already in play. Our goal is to collaborate on the best patterns for different deployment environments.
Even with Quantum lingering right around the corner, nova-network still has its place in existing OpenStack clouds and will be used in the immediate future for many deployments. The goal of this talk is to provide in depth information about nova-network and items to consider when architecting your cloud.
OpenStack Expertise Level: Beginner - Intermediate with good working knowledge of networking, linux networking and iptables.
1) nova-network overview
2) nova-network options
3) iptables and ebtables
4) Floating IPs
5) Considerations for integrating into your existing network
6) Example architectures
A Lightning talk is a short presentation, no longer than 5 minutes. Unlike other presentations at the OpenStack Summit. the lightning talks are unstructured and can be about anything: from code, to running, to any hobby you may have. You can use slides but the 5 minutes need to take into account setting up of your equipment.
You sign up for giving the talk the same day you'll want to deliver it. Participate to the opening sessions every day for more details.
Be creative and have fun.
When someone hears that Rackspace deploys from OpenStack trunk into a production cloud environment, there are generally lots of questions (and sideways glances at the perceived insanity.) In this session, we'll address both the business strategy behind this approach and begin a deeper conversation with the OpenStack Community.
- What does an trunk deployment look like (branch management, merge conflicts, etc)? Why does Rackspace deploy OpenStack from trunk into production?
- What are the benefits gained going this route vs using an official release candidate? What makes keeping up with trunk difficult?
- What does having the largest OpenStack deployment running within weeks of trunk give back to the Community?
- How can embracing this strategy help make OpenStack a better project for all deployers? What innovation and collaboration will we be able to foster in the next release cycle? We'll address these questions and others!
Here at NetApp, we've learned a few things lately about OpenStack.
We've seen a rapid rise in OpenStack interest and activity among our customers, prospects and partners. It's a wonderful reminder that the investments we’ve made over the past several years to enable NetApp solutions to be provisioned and managed smoothly within an OpenStack environment represent a tremendous opportunity to leverage the best of open source ingenuity combined with powerful storage and data management.
Along the way, we’ve accumulated a fair amount of tangible insight on the value of OpenStack, its evolution in the market, and the storage solutions being deployed with it. We’ve also found plenty of truth, myth, and folklore. Come hear as we review NetApp’s real-world discoveries about OpenStack and find out what myths need retiring as well as which truths need uncovering.
People frequently ask how they can get started with OpenStack development. There's a process which needs to be followed, from setting up a launchpad account, to signing the CLA, to sending off you first patch with adequate testing. In this session Michael Still, a Nova core reviewer, will guide the audience through this process and send off a patch to a real bug in the Nova codebase, stopping to answer questions along the way.
After the session attendees should know everything they need to about the OpenStack development environment to start sending off real patches.
This discussion will cover how to use existing tool chains (oz, boxgrinder, veewee) to automate building homogenous, patched OS images for cloud consumers, as well as functionally testing and deploying your images using continuous integration.
This session is a panel discussion of OpenStack users having experience deploying Quantum in production environments, backed by network virtualization technology from a variety of vendor solutions and open source projects. Moderated by independent industry analyst Brad Casemore of IDC, the panel will be asked to discuss specific networking challenges faced before and after deploying Quantum and network virtualization; the impact it’s had on their production cloud deployments, and their sense of where the technology is at today and where it needs to evolve in the short and long term.
Panel will include Quantum users from eBay and HP clouds, among others.
Flexibility and interoperability: They are important elements for adopting cloud computing and IBM believes that an Open Cloud Architecture and nimble open source technology translate into savings for our clients and will rapidly expand the cloud marketplace. IBM together with OpenStack will deliver open IaaS offerings for our clients and business partners. In this session, Angel Diaz, IBM VP Software Standards, Cloud Labs and HiPODS, highlights IBM commitment, vision, and offerings built on OpenStack, for all types of clouds. From simple to implement, to massively scalable, and feature rich, Client interest is accelerating at an impressive rate and Angel will highlight the top use cases IBM is addressing with their clients.
So, you've got an OpenStack cluster up and running, now what? How do you build a "Cloudy" application that leverages the power of an OpenStack cloud. During this session we will walk through some of the considerations for building applications on OpenStack. We will show you how to leverage OpenStack to scale up and scale down your application infrastructure. We'll walk through architecture considerations for a "Cloudy" application and provide you with plenty of tips for getting the most out of OpenStack.
One of the great challenges of of monitoring any large cluster is how much data to collect and how often to collect it. Those responsible for managing the cloud infrastructure want to see everything collected centrally which places limits on how much and how often. Developers on the other hand want to see as much detail as they can at as high a frequency as reasonable without impacting the overall cloud performance.
To address what seems to be conflicting requirements, we've chosen a hybrid model at HP. Like many others, we have a centralized monitoring system that records a set of key system metrics for all servers at the granularity of 1 minute, but at the same time we do fine-grained local monitoring on each server of hundreds of metrics every second so when there are problems that need more details than are available centrally, one can go to the servers in question to see exactly what was going on at any specific time.
The tool of choice for this fine-grained monitoring is the open source tool collectl, which additionally has an extensible api. It is through this api that we've developed a swift monitoring capability to not only capture the number of gets, put, etc every second, but using collectl's colmux utility, we can also display these in a top-like formact to see exactly what all the object and/or proxy servers are doing in real-time.
We've also developer a second cability that allows one to see what the Virtual Machines are doing on each compute node in terms of CPU, disk and network traffic. This data can also be displayed in real-time with colmux.
This talk will briefly introduce the audience to collectl's capabilities but more importantly show how it's used to augment any existing centralized monitoring infrastructure.
Join this panel of infrastructure and cloud hardware experts in a spirited discussion about what works (and what does not) for OpenStack deployments. We’ve assembled hardware and solution vendors together in a panel so that operators can learn from their field experience. We’ll also be hearing about what makes individual offerings advantaged for OpenStack and how to build a cloud that can scale.
PayPal is the world's most successful e-commerce payment platform.
In Fall of 2012 PayPal embarked on a pilot OpenStack project aimed at transforming its global infrastructure into an agile, open and robust cloud platform.
Today the first PayPal production applications are running on OpenStack. By end of fall 2013, we expect several thousand instances in production supporting web and mid-tier applications. Along the way, PayPal solved several technical challenges making OpenStack high available, scalable and easy to operate at scale.
Swift is a multi-tenant, highly scalable and durable object storage system that is designed to store large amounts of unstructured data at low cost.
This session will provide an overview of Swift’s architecture and its components. It will also cover real- world use cases, illustrating how high-volume websites use Swift and how the technology enables storage infrastructure-as-a-service.
The OpenStack Swift introduction is aimed at attendees who want to understand the design goals of Swift and how they can best make use of this OpenStack component. It will be an informative introduction for those interested in running Swift or contributing to the Swift project.
How different are servers from VMs? Do we need special tools to manage servers, or can we adapt a more cloud-like pattern in managing them at scale? Heat has been designed to deploy cloud applications on top of OpenStack. But with Nova Baremetal, the line blurs between cloud and real server. As part of the OpenStack - on OpenStack, or "TripleO" project, we're excited to use Heat to manage a complete deployment of OpenStack. We'll be sharing the various techniques we make use of in Heat to leverage its orchestration capabilities in fully automating the deployment and management of OpenStack.
From a public cloud big enough to make Jeff Bezos crap his pants, down to a single-node DevStack environment under VirtualBox, this talk will cover why scale matters and what you must take into account when planning an OpenStack deployment. Scalability details of specific OpenStack components (compute, block and object storage, and networking), their inherent limits, and effective workarounds will be discussed along with a review of a few deployments that worked and others that didn’t.
It has been a whirlwind first 3 years for OpenStack with project and community rapidly coalescing. Tremendous strides have been made since Rackspace and NASA launched the project, but was does the
long term future hold? Where will OpenStack be in July 2020? Join OpenStack Co-Founder Jim Curry to discuss where our project might be headed and the potential pitfalls and innovations that may await.
In this case study, MercadoLibre, the e-commerce leader in Latin America, will show you how they developed a solution based on OpenStack Swift.
They will share a brief story about how they are moving away from NFS to a highly scalable and durable Object Storage solution, using a Flexible RESTful HTTP API, and commodity hardware to store large amounts of data.
This presentation will walk you through the different stages of their implementation, sharing experiences and tips of how it was pushed into production.
In the infrastructure space, there is a growing trend of companies calling themselves “software defined (x)”. Often, it’s a vendor that is re-positioning a decades old product. Though on occasion, it’s smart, nimble startups and wise incumbents seeing a new way of delivering infrastructure. Either way, the term “software defined” is with us to stay and there is real meaning and value behind it if you look past the hype.
In this session, Ben Cherian will educate the audience on what software-defined networking is and relay the potential for this modern approach.
As the main sponsors of Ubuntu, Canonical is deeply experienced with running instances in all the major public clouds, and as one of the first members of the OpenStack project, also has organizational expertise with the private cloud.
With this all in mind, we asked our IS team a question:
Would it be possible for us to move to a cloud-centric workflow across the entire company? Supporting not only the internal systems that keep Canonical running, but also parts of the widely popular and globally used Ubuntu project?
The answer was "Yes"....but we learned a ton and would like to share some of the things we learned around the following topics:
Organizational needs of moving from a traditional "IS over here and developers over there” to "DevOps".
Workflows - How code gets from a laptop to production quickly and tested?
What happens when things fail? How do you roll back?
Inktank Ceph is a transformational open source storage solution fully integrated into OpenStack providing scalable object and block storage (via Cinder) using commodity servers. The Ceph solution is resilient to failures, uses storage efficiently, and performs well under a variety of VM Workloads.
Dell Crowbar is an open source software framework that can automatically deploy Ceph and OpenStack on bare metal servers in a matter of hours. The Ceph team worked with Dell to create a Ceph barclamp (a crowbar extention) that integrates Glance, Cinder, and Nova-Volume. As a result, it is lot faster and easier to install, configure, and manage a sizable OpenStack and Ceph cluster that is tightly integrated and cost- optimized.
Hear how OpenStack users can address their storage deployment challenges:
Considerations when selecting a cloud storage system
Overview of the Ceph architecture with unique features and benefits
Overview of Dell Crowbar and how it can automate and simplify Ceph/OpenStack deployments Best practices in deploying cloud storage with Ceph and OpenStack
Co-presented by Kamesh Pemmaraju, Product Manager from Dell and Miroslav Klivansky, Technical Marketing Engineer from Inktank.
Gather with marketers and event planners in the OpenStack community for a chance to network and discuss 2013 plans, in particular to provide feedback for a new marketing portal.
Food and drinks will be provided - join us!
You’ve got your shiny new OpenStack environment running, and discovered there is an enhancement you’d like to get back into the main OpenStack release. But where do you begin? What steps do you need to take to go from a raw idea, to code that can make it’s way through the OpenStack review and release process, all the way into the next OpenStack release?
This talk will trace this path. We’ll explain process that you need to follow (bugs/blueprints and the CLA), dive into the tools that you’ll need to get comfortable with (git, gerrit, launchpad), figure out who this Jenkins guy is, and how to make him happy, and how to successfully navigate the review process to get your code in shape and landed in OpenStack proper. You’ll walk away with a roadmap of how to contribute features and bug fixes to OpenStack.
According to Wikipedia, Disaster Recovery (DR) is "the process, policies and procedures . . for recovery . . . of technology infrastructure . . . after a natural or human-induced disaster." The ability to recover quickly with minimal data loss after a disaster such as a fire, hurricane, etc., can make the difference between an organization staying in business or vanishing. In an OpenStack environment there are multiple approaches of realizing this recovery which differ in how much work is lost (the recovery point objective - RPO) and how long it takes to recover (the recovery time objective - RTO). These approaches trade-off up-front effort and cost (when there is no disaster) against greater data loss (RPO) and much longer recovery times (RTO) after a disaster. The appropriate approach depends upon the organization's objectives.
In this presentation, after a brief background on DR concepts, we will survey the various approaches that can be used to provide DR for an OpenStack cloud, showing how the up-front investment impacts RPO and RTO. We will start by considering solutions that work in any OpenStack environment, independent of the underlying physical infrastructure; while these solutions are relatively simple, they lead to long recovery times and significant data loss. We will also consider solutions integrated with the application, i.e., provided from within the guest; these solutions typically provide higher quality of service but at the drawback of being application specific. Finally, we will consider approaches which take advantage of advanced functions seen in storage controllers; these approaches can avoid all (or most) data loss and often can recover quickly, but require up front investment.
This panel will bring together the co-authors of the missing OpenStack Operations Guide, a book written in 5 days for the benefit of the entire OpenStack community. They will discuss the trials and tribulations of writing a book in such a short period of time, from the conception and proposal to the process and publication. The importance of documentation cannot be understated and this panel will highlight the efforts that the doc team are going to in order to produce the documentation necessary for a successful OpenStack ecosystem.
And bring your questions. No subjects are taboo. Ask about the stress, logisitics, collaboration, and whatever else you can think of. Tell us what you thought was missing from the book or what could be improved. Your willing panelists will answer anything!
The first 60 attendees to the panel will get a printed copy of the OpenStack Operations Guide courtesy of Rackspace.
Interoperability allows OpenStack users to transfer workloads between providers; however, even minor differences between deployments can create significant interop challenges. By solving these problems, we can create a clouds that provide fault tolerance at the technical, geographic and commercial level. Join us for a lively discussion about the opportunities and challenges facing us in our quest for workload portability. Our panel includes a broad range of representatives on both the infrastructure, client and system side.
RSVP here - http://hppartyatopenstack.eventbrite.com/#
Vamanos a la fiesta Havana! (come party Havana style!)
We'll have lots of great food, sounds from a fantastic local Portland Cuban band and drinks, all at Sandbox Studios, just minutes away from the Oregon Convention Center.
Transportation will be available from the Convention Center to the Sandbox Studios. Transfer time is 5-7 minutes from the Convention Center. Transfers start at 6:15pm. Shuttle pickup location is the main entrance to the Oregon Convention Center on NE Martin Luther King - Jr. Blvd between NE Holladay and NE Lloyd Blvd.
The Sandbox Studios is also on the MAX and accessible via the train.
Nos veremos allí!
RSVP here - http://puppetlabsopenstackparty.eventbrite.com/#
Join us at Puppet Labs' headquarters for our OpenStack Summit After-Hours party. Mingle with Puppet Labs employees and other OpenStack Summit attendees, and check out our cool new space. We'll have drinks, food, a dj, and plenty of great conversations.
RSVP here: http://womenofopenstackbreakfast.eventbrite.com
Please join your fellow women of OpenStack for a Networking Breakfast during the Summit.
While are all welcome, we want to first invite women working on OpenStack-related projects to mingle and network. We'll have a full buffet breakfast, smoothie bar and copies of Sheryl Sandberg's book, Lean In: Women, Work, and the Will to Lead.
Our three OpenStack interns will be attending the Summit and the breakfast; these young women from Argentina and Canada are participants in the GNOME Foundation's Outreach Program for Women. They're excited to be able to attend the Summit and meet with you.
We hope you'll take this opportunity to get to know others in the OpenStack community and share ideas for how to create more opportunities for women to get involved.
In this session, we will hear directly from NSA and CERN about how research and government organizations are benefitting from OpenStack. Mark Collier will make a brief introduction, followed by two presentations from an NSA cloud architect and physicist at the University of Victoria:
OpenStack at the National Security Agency (NSA)
Speaker: Nathanael Burton, NSA
What does "cloud" mean at NSA and a discussion of how OpenStack fits into the NSA ecosystem. How a small team drove massive process and efficiency change to become one of the NSA's largest hosting platforms. Fostering an environment where creativity and development risk are balanced within the bounds of existing enterprise processes and priorities. Methods for avoiding the "tragedy of the commons".
Clouds in High Energy Physics
Speaker: Randall Sobie, Institute of Particle Physics and University of Victoria
The presentation will describe the motivation for using cloud computing in high energy physics research. In particular, the talk will focus on the experiments at the Large Hadron Collider (LHC) located at the CERN LCEaboratory in Geneva which recently found evidence for the Higgs boson. We will highlight the challenge of analyzing the LHC data using computing resources distributed around the world. We will show that clouds can be used in a number of ways in high energy physics and describe our experiences in this rapidly changing field of computing.
OpenStack has won support across the IT industry from users, developers, cloud providers, and vendors from around the world. The OpenStack community has delivered incredible innovation, and demand for more innovation, performance, and quality is accelerating. As the only vendor-neutral open source community for cloud, OpenStack is gaining rapid momentum and Hewlett Packard is contributing as one of the few vendors who are delivering generally available enterprise solutions on top of OpenStack today. Join Saar Gillai, SVP and General Manager of HP Converged Cloud, to learn about HP’s journey with OpenStack and how OpenStack could evolve to help accelerate cloud innovation.
OpenStack on Ubuntu is now a production cloud infrastructure in telco, service provider and enterprise settings. While the pace of innovation continues to accelerate at the edge, core functions have matured, and we can share insights and operational experience gained from standing up and supporting those platforms. Mark Shuttleworth will discuss OpenStack production challenges and solutions for telco’s and service provider customers and chart the course for an expanding network of partners and solution providers who are collaborating around Ubuntu to accelerate cloud services.
At the last OpenStack summit we received a message from the Enterprise on the missing features in OpenStack (see: "Enterprise to OpenStack: Here's what you're missing" -
http://www .openstack.org/summit/san-diego-2012/openstack-summit-sessions/presentation/enterprise-to- openstack-here-s-what-you-re-missing)
That message was received lound and clear. While some of the points are still valid today, there is also a clear answer back from OpenStck to Enterprise: "Boldly go where few yet have gone so far..."
In this session will be covering the lessons we have learned so from positioning OpenStack in the Enterprise space:
The CMS and ATLAS online clusters consist of more than 3000 computers each. They have been exclusively used for the data acquisition that led to the Higgs particle discovery, handling 100Gbytes/s data flows and archiving 20Tbytes of data per day.
An openstack cloud layer has been deployed on the newest part of the clusters (totalling 1300 hypervisors and more than 13000 cores in CMS alone) as a minimal overlay so as to leave the primary role of the computers untouched while allowing an opportunistic usage of the cluster.
This presentation will show how to share resources with a minimal impact on the existing infrastructure. We will present the architectural choices made to deploy an unusual, as opposed to dedicated, "overlaid cloud infrastructure". These architectural choices ensured a minimal impact on the running cluster configuration while giving a maximal segregation of the overlaid virtual computer infrastructure. The use of openvswitch to avoid changes on the network infrastructure and encapsulate the virtual machines traffic will be illustrated, as well as the networking configuration adopted due to the nature of our private network. The design and performance of the openstack cloud controlling layer will be presented. We will also show the integration carried out to allow the cluster to be used in an opportunistic way while giving full control to the CMS online run control.
Infrastructure-as-a-Service, as exemplified by the success of commercial cloud computing service providers, has clearly proven to be the fastest way to develop and deploy elastic web applications. With the introduction of OpenStack, SDN and API’s for programmatic control over both physical and virtual infrastructure, an opportunity emerges for a completely new way to think about “infrastructure as a service” for both tenants and system administrators alike. This talk will focus on how we and others in the community are working with OpenStack and extending the Quantum network service to explore new ways to think about the delivery of network services and infrastructure management. While still in it’s early formative stage, this approach promises to bring new meaning and possibilities for infrastructure-as-a-service limited only by our own imagination.
OpenStack is the fastest growing open source movement in history, but its marketing momentum has largely outrun its technology growth. Why are organizations so eager to embrace OpenStack? Some components – like Swift – are ready for prime time. But others – like Horizon and Quantum – are still evolving. What needs the most attention: networking, storage, compute, or something else? Where are the reference
architectures and real world deployments? How are different product and service companies implementing OpenStack in production today? We'll go beyond the hype and dig deep on OpenStack, exploring all that is great and all that needs serious work. Attendees will leave with a firsthand account of the State of the Stack, ready to help their organizations embrace OpenStack armed with practical knowledge.
In this session, end users will be walked through installing and configuring OpenStack Cinder and Quantum. This interactive configuration session will provide detail in setting up:
Attendees should bring a laptop with Vagrant installed (vagrantup.com) as well as either Virtualbox or VMware Fusion.
Take full advantage of the cloud value proposition. Emulate and improve upon the existing features we've used in our existing virtualized environments, mainly VMware, to an OpenStack platform using RightScale. See how traditional infrastructure features such as automation, HA and Vmotion are managed at the cloud and application layer.
By the summit, the NeCTAR Research Cloud will have been operating in production for more than a year.
A federated Infrastructure-as-a-Service cloud for use in any discipline across the Australian research community has provided virtual machines and object storage to researchers around the country. Within the next eight months, it will expand to 30,000 cores over 8 sites distributed over an area comparable to the USA, using OpenStack Compute Cells.
Using this as a platform, the sector is moving to build an array of services and software solutions to enhance research ability and collaboration. This presentation builds on the existing case study (http://www.openstack.org/user-stories/nectar/collaborative-research/) to introducing the design, and address the challenges encountered in operating a multi-site cloud for researchers from Archaeology to Wine.
For the technical: we'll dive into cells, list real hardware specifications, talk about HA, puppet, and more For the manager: ask us about how few people we need to run a cloud of this scale, and how we build up the stack.
In this session Intel focuses on continued momentum for Trusted Compute Pools in OpenStack, a graphical SWIFT object store benchmarking tool, and enhancements across compute, networking, and storage targeted for future OpenStack releases. The session will conclude with the latest developments in Intel’s own deployment and use of OpenStack for their hybrid cloud.
Cloud brings the promise of quickly spinning up virtual machines and application, but network services often lag behind lacking the automation and rapid provisioning capabilities of compute. We will be discussing the benefits of enabling advanced network services in your cloud such as Server Loadbalancing, site and user VPNs, and Firewalls via Quantum's REST APIs that would enable on-demand provisioning of these services at the time of application deployment. We will also explore the benefits of using virtual appliances to deliver these services on top of standard x86 servers to reduce specialized hardware requirements for cloud build-out to decouple network service feature delivery from hardware installs, procurement, and forklift upgrades.
To conclude, we'll be showing an early integration demo previewing some of VMware's networking and security services in action through Quantum which you won't want to miss!
A Lightning talk is a short presentation, no longer than 5 minutes. Unlike other presentations at the OpenStack Summit. the lightning talks are unstructured and can be about anything: from code, to running, to any hobby you may have. You can use slides but the 5 minutes need to take into account setting up of your equipment.
You sign up for giving the talk the same day you'll want to deliver it. Participate to the opening sessions every day for more details.
Be creative and have fun.
This session will feature Mark Muehl, SVP, Product Engineering at Comcast who will present an overview of their OpenStack strategy and deployment plans followed by a Q&A session with OpenStack Foundation Vice-chair Lew Tucker.
Comcast Cable is the nation's largest video, high-speed Internet and phone provider to residential customers under the XFINITY brand and also provides these services to businesses. Comcast has invested in technology to build an advanced network that delivers among the fastest broadband speeds, and brings customers personalized video, communications and home management offerings.
While it's still an evolving area, the industry now has a a few years of virtual networking under its belt. And with many production deployments, and standard abstraction layers like Quantum, OpenStack is leading the way. In this talk, I'll draw from my experience of hundreds of customers visited, hundreds of thousands of miles flown, and dozens of deployments to describe use cases, what works, what doesn't, and where things seem to be going.
I will also touch on VMware's progress on vSphere in OpenStack and our plans for VMware NSX, the industry's first unified network virtualization platform out later this year.
On a beefy machine (24 cores, 96 GB RAM, SSD), booting a single instance (from "nova boot" to ACTIVE) takes seconds. However, when you try booting 20 instances in parallel, the last instance might not be ACTIVE for minutes! While you're waiting, you notice that the host's CPUs and disk are mostly idle and there's plenty of free RAM. While your instances are BUILDING, you wonder what's going on -- why's this taking so long?
It turns out that lengthy portions of the boot process are serialized by contention for software resources, like iptables, database connections, libvirt, and the python interpreter! In this talk, we show how tools like strace and Tracelytics can be used to identify bottlenecks in Openstack. We present techniques for eliminating these bottlenecks, such as coalescing updates to iptables and avoiding greethreads pitfalls, and demonstrate how boot can scale!
Juju is a terrific way to get an OpenStack cloud up and running. What about after you've got OpenStack?
Empty clouds are no fun, people need to run services on clouds, like Hadoop, MongoDB, PostgreSQL, MySQL, Jenkins ... the list goes on and on. On top of that your developers are looking for ways to consume your cloud; and they're writing applications that are just as diverse in Python, Rails, Node.js, PHP, and Java and other platforms.
At Ubuntu we're working on solving these problems, how do you manage your cloud at the higher service level? How do you bring the speed of cloud deployments down to your developers so they can leverage the cloud faster?
We've built a tool called Juju that makes deploying services on an OpenStack cloud very simple, and we've got over 110+ services ready to go. This workshop will be a technical overview of how Juju works, and how you can use it to make deploying services in OpenStack simpler for you; we'll also cover how to write your own orchestration scripts (that we call charms) for your self so that you can rapidly deploy your
applications in OpenStack.
Whether it's regulatory issues, early cloud market questions, licensing uncertainty, or competitive pressures, cloud service providers around the world are facing unique challenges in their markets to build a business and gain traction. In this session, we'll hear from service providers across four continents that have chosen OpenStack as their cloud platform. We'll learn the unique technology and market drivers that led them to OpenStack, how OpenStack is enabling them to compete in the global IaaS market and where they think OpenStack should go next.
Networking challenges in data center and cloud environments have received significant attention by industry and standards organizations. The data center environment is dominated by the presence of software networking components (vswitches) in server hypervisors, which may outnumber by an order of magnitude the physical networking nodes. Bridging the gap between server based networking and existing network services is a significant challenge, since the ultimate goal is the design of end-to-end network services. When it comes to advanced L3 services and interoperability with existing managed VPN services, existing solutions rely on static routing and/or centralized routing mechanisms that cannot meet the requirements for resiliency and dynamic networking.
This talk will discuss a simple approach for this problem, which combines traditional control plane and routing protocol approaches with the flexibility of SDN architectures and Openflow. The mechanism relies on maintaining an Openflow interface to hypervisors and utilizing existing routing mechanisms when a scaled out data center deployment is required to federate a number of SDN controllers, or to interoperate with traditional MPLS/VPN network services without the need for dedicated gateways or complex OSS integrations.
From a deployment perspective, we will discuss how this approach can be easily integrated within the Openstack Quantum framework by requiring minimal modifications. The solution also enables the federation and interoperability of Openstack deployments at the network layer even across administrative domains as well as the extension of enterprise networks into Quantum managed networks.
The presentation will conclude with a live demo of the solution.
OpenStack currently enables the provisioning and operation of applications on cloud VMs, but what if you want to provision onto real hardware instead of VMs? Wouldn't it be nice to use OpenStack for this, too?
Going one step further, what if you could easily use OpenStack itself to orchestrate the deployment and scaling of an OpenStack cloud onto new machine nodes?
At HP Cloud Services, we think that the possibility of a single suite of tools and a unified API for managing both physical and virtual resources is very exciting. Working with others in the community, we have added the "baremetal" compute driver to the Grizzly release of OpenStack to provide a common framework for deploying images to real hardware. We will present the current design of the driver, some limitations it currently has, how to simulate an environment for dev/test purposes, and cover some of the quirks in deploying it. After all, this isn't your average hypervisor.
Companies large and small are utilizing the agility and ease of use found in the public cloud. However for large enterprises the public cloud is expensive at scale and availability is not guaranteed For smaller SME's experiencing rapid growth, every day is one step closer to a call from the CFO regarding another rapid growth... cost.
In my presentation I will go over two use cases, one will feature a very large Fortune 100 company experiencing an increasing internal customer base moving to Amazon AWS for rapid provisioning of new infrastructure and how we used OpenStack to provide feature parity, ease of use and self-provisioning to move those customers back into an on-premise private cloud. My second use case will cover a rapidly growing and large consumer of Amazon AWS who was feeling the pain/costs associated with running entirely in the public cloud and found economies of scale in an OpenStack based private cloud.
Both cases illustrate big wins for OpenStack, and the ability to provide massive value to both Fortune 1000's and rapid growth SME's.
1.Identify test gaps for all core services Swift,Nova, Keystone, Cinder and Quantum projects .
2.From gaps, identify new tests to be written to have coverage.
3.Discuss as part of design session that leads to new blueprints and blueprint ownership for Havana release
(Session proposed by Ravikumar Venkatesan)
Software Defined Networking (SDN) is a hotbed of activity with established players as well as well-funded start-ups tackling the largely unsolved problem of large-scale network virtualization in cloud deployments. OpenStack Quantum provides the foundational interfaces to bring in SDN technologies to the OpenStack environment. The ultimate goal is to finally free applications from being aware of specific networking details (like ports, IP addresses etc) and at the same time reducing the operational costs of managing the switching fabric in the era of cloud and mobile computing. Companies have a variety of approaches and solutions to this. In this panel discussion, Dell will moderate a discussion with experts from Big Switch, Midokura Dell, and others, to talk about the evolution of this exciting new space and its relevance within the OpenStack context.
Nnamd Orakwue, Vice President, Cloud, Dell
Joseph B George, Director of Product Strategy for Revolutionary Cloud and Big Data Solutions, Dell
We need to have a lengthy (ie more than 40 minutes) session with representatives from as many countries as we have attending to share ideas and experiences. With a free form agenda and full audience participation encouraged, the forum is designed to improve communications and help user groups from around the world grow and thrive.
Can we build an OpenStack HA solution that allows the same type of automation as Amazon AWS? This session compares an OpenStack HA reference architecture to Amazon to see how OpenStack stacks up.
As OpenStack goes real world production environment, the real world problems like reliability, high availability need to be addressed. In this session, we will explore various time-tested techniques for improving availability of your applications on OpenStack private cloud.
We'll be joined by RIghtScale customer, Samsung SDS, to discuss their revolutionary OpenStack project. Samsung SDS has devised a multi-cloud architecture that leverages OpenStack and AWS to enable cloud-bursting while eliminating latency and security issues. Samsung SDS will review the architecture and technologies they are levering to make this solution possible.
Key take-aways from the presentation would be:
Users will get access to a live OpenStack + Quantum setup and be able to walk through key quantum deployment use cases, with members of the Quantum core development team available to provide guidence and answer questions.
At the OpenStack conference 6 months ago we presented a similar Quantum hands on lab led by several members of the Quantum core team and it was standing room only. We'd like to run another session this time, incorporating lessons learned from the previous sesion and also including new Quantum capabilities introduced in the Grizzly release.
Demonstrated features will include:
Two years ago, Rackspace set out on a quest to build a public cloud in the open, powered by OpenStack. Building the Open Cloud from an idea to a viable deployment of thousands of servers has come with lots of growing pains. We've also gained a little bit of wisdom along the way and are ready to keep pushing for great things. In this case study, we will talk about the various deployment strategies we have used, our experience with them, and how what worked for 200 nodes didn't always work for 1,000 nodes. We'll end by look at how we will get to the first 10,000+ node deployment and stay continuous.
How much for an Openstack Cloud please?
That's it! You're ready! You know everything there is to know about OpenStack.
It's architecture, features and a bunch of other cool stuff.
But finally: How much does an OpenStack Cloud cost?
During this talk, we'll work on two real production use cases to provide you with a detailed, yet simple, financial analysis that will help you budget your future cloud projects. We’ll present the case of a basic simple infrastructure and a second example will treat of a much more complex, high end platform.
Kio Networks, one of the largest data centers in Latin America, will share with the audience a case study for building its public cloud with OpenStack and the challenges that involves entering the Latin American market in the world of cloud computing.
Kio Networks has commited with OpenStack Foundation as Corporate Sponsor as the first Latin American company to be involved with the Foundation and with the community to promote the use of a real Open Source Cloud Computing OS in the region.
OpenStack high availability has seen a lot of progress since it was defined as an overarching design goal during the Folsom cycle. Not only is there now a reference architecture for highly available OpenStack infrastructure services, but OpenStack is also gradually growing native high availability features. In this session, we are giving an overview of the current state of high availability technology in OpenStack, and an outlook as we enter the Havana cycle.
In particular, this session covers >
High Availability features in OpenStack Compute (Nova):
High availability improvements in OpenStack Networking (Quantum)
Attendees should have a good general understanding of OpenStack components. High availability experience is a plus, but not required.
EIG/Bluehost is one of the largest hosting companies in the world. The scale of our systems at Bluehost have been rapidly increasing. We are challenged with respect to how to manage such large server farms distributed across multiple data centers that are geographically distant. Although the main stream products at BlueHost still reside on traditional hosting platforms that have their own idiosyncratic requirements, we have been seeking an ideal cloud-based solution for an efficient management system in a highly scalable environment. We chose to leverage Openstack in provisioning tens of thousands of servers while meeting customers’ availability requirements.
In this talk, we will present our use case of Openstack in a traditional hosting environment. Although it can be considered odd or appear to be a conflict between 'traditional hosting' and 'cloud,' Openstack has been a good decision with which we could successfully launch our cloud-based traditional hosting products for dedicated servers and virtual private servers (VPS). We also plan on utilizing other benefits that exist in Cloud technologies so as to improve our hosting products as much as possible. We have learned many useful lessons from our unique experience, including the scalability issues that we faced while operating tens of thousands of servers and the stability issues that each OpenStack subcomponent currently has, as well as the architectural design considerations while using OpenStack. We are interested in sharing with the OpenStack community our experiences and code for some new features that we have added to OpenStack. We would like to obtain feedback from the community and also contribute our experiences back to the community.
SUSE®, a pioneer in open source software, provides reliable, interoperable Linux and cloud infrastructure solutions that give enterprises greater control and flexibility. More than 20 years of engineering excellence, exceptional service and an unrivaled partner ecosystem power the cloud infrastructure solutions that help our customers improve resource utilization and speed the delivery of IT services to meet changing market needs. Whether the enterprise is deploying services in a public, private, or hybrid cloud environment, SUSE has a secure, compliant and fully supported solution. Come learn how SUSE Cloud will help you meet the demands of cloud computing in your organization.
In only 2 years eNovance has built a strong business activity around Openstack on the European Market. We started from close to zero, and we're now one of the key players on Openstack in Europe.
During this session we will talk about building an ecosystem, convincing partners, building alliances, hiring the best employees and more...
The goal of this session is to share our strategy and concrete examples about how one can develop a strong activity around Openstack.
In this talk we will explain how to make some OpenStack services highly available in active / active mode, or active / passive for some of them. We will also approach the subject of shared storage and how OpenStack is using it. We will share our experience on production environments where High Availabity is one of our top priority.
RSVP for a chance to win a Jawbone Jambox! Compliments of RightScale
Up Your Game at the Rackspace Party
Wednesday, April 17th at 6:30pm – 10:30pm
Castaway - 1900 NW 18th Ave Portland, OR 97209
OpenStack changed the game! Now it’s time to ‘Up Your Game’ at the Rackspace party. Come celebrate our victories and achievements in building the open cloud together.
Join us for amazing food, specialty cocktails sponsored by RightScale, digital caricatures created by our on-site artist, Rock Band stage, Xbox dance station, Wii Sports station, & more. Transportation will be provided to Castaway from 6-7pm. Shuttle buses will be available outside the Oregon Convention Center off Holladay Street and 1st Avenue. Shuttles will be available until 11pm for return drop offs to host hotels.
Project Updates: Opportunity for newly elected PTLs to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release.
Come to this session to get an update on Marconi, an OpenStack queuing and notification service described at http://wiki.openstack.org/marconi
Marconi aims to be pragmatic, building upon the real-world experiences of teams who have solid track records running and supporting web-scale message queuing systems.
Join Rackspace's Kurt Griffiths, Principal Architect, and Allan Metts, Engineering Director, to learn about the work that has been done and the path ahead -- including a description of the project, milestones, how it works, and an early demo.
As a message bus, Marconi allows cloud developers to use a REST API to easily distribute tasks to multiple workers across the components of an OpenStack deployment. Publish-subscribe semantics are also supported, allowing notifications to be distributed to multiple listeners at once.
Users will be able to customize Marconi to achieve a wide range of performance, durability, availability, and efficiency goals.
Security is important when deploying any distributed application especially the one responsible for running all of the virtual machines in your data center. When deploying Open Stack, many of the security implementation details are left unspecified. This is where FreeIPA comes to the rescue. This session will show how guidance on how FreeIPA can be used to help secure communication, provide authentication and authorization capabilities for a large scale Open Stack deployment.
Cloud Networking introduces several new concepts and practices that change the way traditional networks are being built and managed. Network architects, solution designers and application developers need to
understand these new networking capabilities to take advantage of the cloud. This talk aims to demystify cloud networking to the above audience by providing a deep dive analysis of the various cloud networking models and capabilities by using specific networking scenarios from the OpenStack Quantum service and Amazon EC2. We will also examine how these capabilities could be leveraged to build fault-tolerant cloud applications.
This hands on lab will provide an oppurtunity to see how easy it is to use Puppet to deploy OpenStack environments.
It will cover the architectural details of the Puppet modules used for installation, and explain how to easily get up and going with a fully functional OpenStack environment.
Requirements: This lab assumes that you have a laptop with the following installed:
The lab also assumes reasonable networking connectivity in the lab.
OpenStack Object Storage Update: Opportunity for PTLs to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release.
Ceph is an open source distributed object store, network block device, and file system. Ceph can be used for object storage through its S3 and Swift APIs. It can also provide storage for network block devices, with the thin provisioning and copy-on-write cloning features necessary to support large-scale virtualization.
Since the Folsom release, Cinder makes block storage for backing VMs a first class feature in OpenStack. Block devices can be created from images stored in Glance, and with Ceph's RBD behind both, new VMs can be created faster while using less space. In the latest Ceph ‘Bobtail’ release, you can start many VMs instantly by cloning from templates. Also, on the storage backend side, you will see increased I/O performance due to improved threading.
This session will cover an intro to Ceph, the current status of Ceph and Grizzly, the latest features of the Ceph Bobtail release and also the technical implications and the advantages of block storage within OpenStack.
OpenStack is extensively used in industry today. With increasing collaborations both within a single organization and between several, resource sharing is a natural extension to the existing implementation of isolated tenants (ie allow resource sharing between tenants within an organization). Furthermore, the access
and resource sharing between different cloud installations is also unattended to. We propose the addition of a service which handles both these requirements ie, resource sharing between tenants within a single organization and also tenants between different cloud installations. Our proposal (which will be submitted as a blueprint and is under implementation) aims to provide a multi-tenant federated access to resources within OpenStack. A federation is an association comprising any number of service providers and identity providers, in this scenario would mean different openstack clouds/installations. Multi-tenancy support is defined as the capability of a single cloud instance to provide its service to several customers/tenants simultaneously which in this case not only refers to the mere existence of several tenants but also resource sharing capability between the tenants within the same cloud instance or other cloud instances due to the concept of federated access.
This brings forth the need for improved Identity Management and Policy Enforcement which doesn’t rework existing deployments but rather extends them to the the required functionality seamlessly. We model the functionality of this service and the required extensions to be made to accommodate it. The crux of our model lies in the way we represent each user and his capabilities. The current system uses a 3-Tuple mechanism of (Subject, Privilege, Object) to represent users and the resources they are allowed access to. We plan to extend this to a 5-Tuple mechanism (Issuer, role(Issuer,roleName), Privilege, Interface, Object) so as to incorporate RBAC and provide access to remote resources outside of the same tenant and cloud installation.
Our talk will deal with a detailed look into this proposal.
Existing approaches to delivering persistent block storage in OpenStack focus on integrating existing SAN/NAS hardware solutions, using Distributed File Systems (DFS), or using simple Direct Attached Storage (DAS) with Cinder. There is another alternative: scale-out block storage nodes with intelligent scheduling. This is the same approach that Amazon Web Services (AWS) uses for Elastic Block Storage (EBS) and it's worth taking a close look at the pros and cons. This presentation will explore the differences between SAN, NAS, DFS, DAS, and EBS. We will look at the implicit and explicit contracts that users and operators get from the different approaches and look at a variety of failure conditions. EBS may not be right for some clouds, but for many it's an important and viable alternative to the existing approaches.
OpenStack Networking Update: Opportunity for newly elected PTLs to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release
Recently we've started work on BillingStack which is a billingsystem that is based on the ideas to be like a "OpenStack" project, meaning do something and do it very well. It's at the time being re-written from a Java / Grails implementation initially conceived by it's original author Luis Gervaso from the former company called StackSherpa.
Similarities to BillingStack and OpenStack:
Until now we have implemented / planning alot of features like:
Other projects we are working on and planning are:
I would like to present you BS with a small initial demo of our capabilities and tell you about future hopes and plans.
In Keystone v3 (Grizzly release), the Domains feature encapsulates users and projects into logical entities that can represent accounts, organizations, etc. However, currently there is no capability or mechanism to manage or enforce quotas at the domain level. Assigning or updating values or limits to a domain will allow the cloud administrator to evaluate domain lists and consumption. In order to achieve these capabilities it will be required to implement quota management and quota monitoring for Keystone domains, by which domain usage can be managed and enforced.
The goal is to support quotas at the OpenStack Domain level.
Eventlet is a core library that Openstack depends on for network communications. Eventlet is not magic, though often it is treated as such. In this talk, I will dispell the magic, and discuss best practices for using Eventlet.
Due to security, licensing, and networking particularities, as well as a resource-heavy boot and runtime profile, running Windows in a cloud environment poses a unique set of challenges to implementers of OpenStack public and private clouds.
Despite these challenges, enterprises are increasingly looking to deploy Windows virtual desktops and servers in their OpenStack environments - both to replace physical desktops as well as to move their Windows-based server applications to a more economical virtualization platform.
In this talk we present best practices and pitfalls learned over the course of several pilot and production Windows-on-OpenStack deployments, including: - Understanding how Windows works in the context of an OpenStack cloud: images, instances, etc. - Methods for mitigating the "boot storm" incited by booting large numbers of Windows VMs. - Integrating with existing Windows networking services, such as Active Directory. - Desktop personalization, access marshalling, and session management. - License and license key management for short-lived Windows VMs. - Strategies for the reduction of runtime resource usage for large Windows deployment.
This session will include the following subject(s):
Distributed & scalable alarm threshold evaluation:
A simple method of detecting threshold breaches for alarms is to do so directly "in-stream" as the metric datapoints are ingested. However this approach is overly restrictive when it comes to wide dimension metrics, where a datapoint from a single source is insufficient to perform the threshold evaluation. The in-stream evaluation approach is also less suited to the detection of missing or delayed data conditions.
An alternative approach is to use a horizontally scaled array of threshold evaluators, partitioning the set of alarm rules across these workers. Each worker would poll for the aggregated metric corresponding to each rule they've been assigned.
The allocation of rules to evaluation workers could take into account both locality (ensuring rules applying to the same metric are handled by the same workers if possible) and fairness (ensuring the workload is evenly balanced across the current population of workers).
Logical combination of alarm states:
A mechanism to combine the states of multiple basic alarms into overarching meta-alarms could be useful in reducing noise from detailed monitoring.
We would need to determine:
* whether the meta-alarm threshold evaluation should be based on notification from basic alarms, or on re-evaluation of the underlying conditions
* what complexity of logical combination we should support (number of basic alarms; &&, ||, !, subset-of, etc.)
* whether an extended concept of simultaneity is required to handle lags in state changes
The polling cycle would also provide a logical point to implement policies such as:
* correcting for metric lag
* gracefully handling sparse metrics versus detecting missing expected datapoints
* selectively excluding chaotic data.
This design session will discuss & agree the best approaches to manage this distributed threshold evaluation, while seemlessly handling up- and down-scaling of the worker pool (i.e. fairly re-balance and avoid duplicate evaluation).
OpenStack Nova Update: Opportunity for to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release
In this talk we introduce Curvature – an interactive visual orchestration tool for applications on OpenStack. We also describe Donabe – a recursive container service – and how both can be leveraged in conjunction to create and deploy recursively stackable application topologies from virtual machine images and Quantum networking components.
Curvature’s approach to service deployment allows the user to define a workload at a higher level of abstraction than current deployment tools. Users draw their desired application topology on a canvas using a toolset of Quantum L2/L3 components and virtual machine images. This topology can then be deployed onto a running OpenStack environment at the click of a button – with Curvature handling all of the orchestration necessary for provisioning the workload, i.e. the Quantum networks and Nova VMs. We demonstrate this design and deployment workflow in real time on a live OpenStack environment using real- world use cases.
This talk showcases Curvature’s functionality both with and without Donabe to demonstrate how these services will radically change the user experience of cloud application deployment.
Most companys today have taken the age old security models and "Virtualized" them to be used in todays "cloud" market. Vendors have come to market with "Virtual" Firewalls, IPS, HIPS/HIDS, etc that all claim to be the pancea that solves your cloud "security" issues. The problem exists when we rely our "virtual" security infrastructure to protect our sensative 'real' information.
During this talk we will walk through the current state of Virtualization security. We will look at products both free ( as in speech, and as in beer) , and commercial products -- and show where they fail and how; in some cases they leave you in a worse position after implementing.
The hypervisor is a huge attack surface; there’s no defense in depth when your only security controls are provided by the provider (Hypervisor vendor, cloud provider, etc ). How do you gain visibility into a system that by design is constructed to keep you out?
Whether it is IAAS or PASS, Public or Private - there is no good compensating control around a system that is closed and only allows access to very specific parts, and uses a "trust me" security methodology.
As a community we need to innovate, leverage different ways to address our security concerns, get rid of the "catsup" on "ketchup" approach to Cloud security, piling on legacy security infrastrucutre up and down the stack, duplicating efforts along the way.
This presentation will outline where our current security strategys fail, and can be circumvented -- and also gives insite on how to make things better going forward.
With the Grizzly release comes many new and exiciting features for Windows Server 2012 and Hyper-V. We will discuss new features including
This session will include the following subject(s):
Time series data manipulation in nosql stores:
Ceilometer currently supports multiple storage drivers (mongodb, sqlalchemy, hbase) behind a well-defined abstraction.
The purpose of this design session is to discuss how well suited the existing nosql stores are to the efficient manipulation of time-series data.
The questions to be decided would include:
* whether we could optimize/improve our existing schemas in this regard
* whether we should consider a storage driver based on Cassandra in order to take advantage of it's well-known suitability for TSD
(Session proposed by Eoghan Glynn)
The dotted line between metering and metric/alarms:
There is clear commonality in the data acquisition & transformation layers for gathering metering and metric data.
However the further we venture through the pipeline, there are also operation concerns around over-sharing of common infrastructure in the transport and storage layers.
We need to tie to down exactly where we see the dotted line between the handling of metering and metric data, deciding whether:
* a common conduit in the form of AMQP should be used for publication (for example given that during a brownout in the RPC layer, we would need a timely metric flow more than ever)
* a common storage layer should be used for persistence (for example given that data retention requirements may differ significantly)
* a common API layer should provide aggregation (for example given that certain aggregations such as percentile may make far more sense for metric rather than metering data)
OpenStack Dashboard/Horizon and Image service / Glance Updates: Opportunity for newly elected PTLs to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release.
With the continued adoption of OpenStack infrastructure, many open source projects face the challenge of integrating with OpenStack in order to remain relevant to customers. oVirt and the Open Virtualization Alliance (OV A) are two communities dedicated to the advancement of the open source KVM hypervisor. oVirt is an open-source management infrastructure for KVM, whereas the OVA is dedicated to driving
adoption of KVM in the marketplace. Together these efforts have increased the use of KVM by customers, and created a healthy ISV ecosystem around the open source technology.
The growth of KVM also presents some interesting opportunities for improving both OpenStack and oVirt. oVirt can provide rich services to Cinder, Glance, Quantum, and Nova. In this presentation we will discuss both the value and the technical implementation for each of these integration points, and the future of the oVirt project within the context of OpenStack. Additionally,we will discuss best practices in open source community development along with an overview of the business value of KVM on OpenStack.
This presentation will provide an update on the progress in adding federated authentication and authorisation to OpenStack via modifications to the Keystone v3 API. This will allow organisations to use their existing internal authentication systems so that their users can access both public clouds and internal private clouds and services using the same set of credentials. This will simultaneously reduce the management overhead costs to the organisation and the multiple credential management nightmare to users.
This talk will be of general interest to all OpenStack users.
The current implementation of VMware VC compute driver for OpenStack uses one proxy server to run nova-compute service to manage a cluster. In this session, we would cover the changes implemented to enhance VMware VC Compute driver so that it runs as a Proxy Compute Service to manage multiple VMware vCenter Clusters and Resource Pools as compute nodes. These proposed changes are in line with nova Bare metal proxy driver.
Highlights of these changes:
This workshop will teach attendees how to deploy OpenStack Swift from the ground up. It will be a hands- on training where the audience will learn by doing rather than listening. Come with a laptop, or feel free to watch and learn.
In this session, the audience will be guided through a deployment and configuration of OpenStack Swift by the experts at SwiftStack. We will walk you through the architecture of Swift while demonstrating a step- by-step installation from the ground up.
Attendees will learn:
- Swift's architecture (The Ring, Zones, Partitions, Accounts & Containers)
- How to bootstrap a basic Swift installation
- The guts of how OpenStack Swift works
- Swift’s failure recovery mechanisms
The attendees interested in participating should bring their laptops (with virtualization extensions enabled in the BIOS), and we will provide a virtual machine image that will be used in the workshop.
DNS is one of those things in life one often takes for granted. It just works. It is however, the phone book of the Internet. Without DNS, maintaining lookup data would be a difficult endevor. With Openstack, there is certainly a need for a DNS service, particularly, something that works well with Openstack and adheres to its standards and philosophy. One such project is Moniker.
Moniker is a an Openstack-inspired DNS as-a-service project. It is intended to be used to provide DNS service from the entry point of creating, updating, maintaining and deleting DNS data using the Moniker API, to providing DNS resolution for users. It is a very modular project, allowing for the use of whatever DNS server and organization demands, or the database where DNS data is stored. It is also intended to work in conjunction with other components such as Nova.
Moniker is an ideal project to use for developing DNS as a service for an organization, and HP in particular is building their DNSaaS product based on Moniker.
This discussion will provide an overview of Moniker as well as in-depth discussion of the various components such as:
* Moniker processes and configuration
* How Moniker allows multiple DNS server backends and creating new backends
* How Moniker allows backend database storage
* Using the Moniker API
Also, a demonstration of using Moniker will be given, showing DNS domain creation, modification and deletion, followed by a question and answer session.
OpenStack Grizzly will finally include support for elastic load balancing. Quantum LBaaS project provides a standardized REST API that abstracts diverse hardware and software-based load balancers. This allows administrators and applications to instantiate and configure virtual and physical load balancers on demand.
The talk will walk attendees through key features of Quantum LBaaS and will include a live demonstration of managing HA-proxy instances. We will also discuss supported load balancers and go over the future roadmap.
This interactive session will cover automation and management tools for OpenStack Swift. Attendees will learn about the deployment mechanisms behind the scenes of SwiftStack. This is a hands-on workshop where we will install and configure a SwiftStack cluster in a virtual machine on attendees’ laptops.
In this workshop, attendees will learn about:
Attendees should bring their laptops (with virtualization extensions enabled in the BIOS), and we will provide a virtual machine image that will be used during the workshop.
We need to tie down the requirements for managing the state and history of alarms, for example providing:
* an API to allow users define and modify alarm rules
* an API to query current alarm state and modify this state for testing purposes
* a period for which alarm history is retained and is accessible to the alarm owner (likely to have less stringent data retention requirements than regular metering data)
* an administrative API to support across-the-board querying of state transitions for a particular period (useful when assessing the impact of operational issues in the metric pipeline)
OpenStack Block Storage Update: Opportunity for PTLs to share the state of the project, major topics being discussed at the Summit, user feedback, and their vision and roadmap for the next release.
Getting an X Ray is sometimes a life saving procedure but did you know that X Rays are named X Rays because when they were first discovered their discoverers did not know their nature, hence the X. Come join a discussion about the current state of the data center while we look to the future and how together we can do more.
This talk is a break down of security concerns relating to the OpenStack Folsom Release. The purpose of this talk is to look at past vulnerabilities in Folsom, existing security models, and emerging technologies that will impact those models. The presentation will follow the flow of describing several deployment models in terms of their security attributes. The next phase will be the discussion of specific protocols in use and their individual security characteristics. I will present statistics on where past vulnerabilities have been found and reported allowing us to consider how we can better address security in our continuous integration
processes. The goal of this talk is to present a map of where we are today, and expose some of the issues we have yet to face.
We present the Openstack architecture that integrates Openflow based software defined networking (SDN) enabling automation and provisioning of network services spanning virtual switches (OVS) and physical switches. The talk will provide a deep understanding of the architecture components and the interactions. We will also discuss the unique benefits of SDN/openflow vis-a-vis Openstack, compare with existing Quantum supported networking architectures and share our deployment based experiences.
In this workshop attendees will follow along with the presentation and learn to use the Razor Provisioning Engine along with Opscode Chef to deploy OpenStack to bare metal in an easy to do, easy to maintain, easy to scale fashion. Key take-away:
Since its inception in 2009, Deltacloud has been focussed on bridging the gaps between various IaaS cloud API's by offering a RESTful API that can be used against various backend clouds. Over time, the project has been expanded to include frontends for Amazon's EC2 API and DMTF's CIMI.
This talk will provide an overview of what Deltacloud is, what the supported frontends and backends are, and how to use it with Openstack. It will also explain how Deltacloud is used be a number of projects to achieve cross-cloud portability.
OpenStack is complex, and like all complex systems needs to have some extra attention paid when hardening the environment. This session will cover some basic cloud security concepts and then dive into the practicalities of securing your OpenStack deployment and the steps necessary to design your OpenStack Private Cloud in preparation to undergo a PCI-DSS Audit.
This presentation will be an in-depth critique of the existing OpenStack networking approach, with a focus on how the Nova network controller is more of a hindrance than a help. We will also discuss the changes in Quantum's functionality required to close the gap, and alternative solutions. How can we make networking in OpenStack robust, high performance, and fault tolerant? What do typical large scale networks look like and what lessons can we learn from them? Is there an approach to networking we can take that is the same with a handful of servers as it is with hundreds of racks?