There are a large number of categories that you can choose from as you can see below:
You will need an account to cast your vote.
It is quite interesting to see that some of the sessions are targeted at how you can migrate your workloads away from VMware and onto OpenStack, something that I think people will be looking into a lot more in the near future.
I also have a few sessions that you can cast your vote – if you so choose..
In July, 2014 The OpenStack Foundation brought twelve members of the OpenStack community together at VMware HQ in Palo Alto, California to produce the OpenStack Design Guide in just 5 days. This panel brings many of these authors together for an open discussion about how to architecture an OpenStack cloud.
Bring your real-world questions and be prepared to talk OpenStack architecture with a panel of experts from across multiple disciplines and companies. We’ll be drawing on real architecture and design problems taken from real-world experiences working with, and developing solutions, built on OpenStack. Following a brief introduction, panelists are ready to field questions from both the moderator and audience members and provide ongoing discussion the design process for architecting cloud solutions based on OpenStack.
This session will go over how the Video Service provider group has added focus to deployment of its platform to support OpenStack. How this has evolved over the past year, the challenges that came up along the way and how these challenges were addressed - and solved.
I have been designing VMware clouds and architectures for the past 4 years, and have now moved my focus to OpenStack. The change was not a simple one. There are terminology differences, architectural differences, differences in use cases. Differences in considerations regarding storage design, networking, automation, deployment - across almost every single aspect of the solution.
In this session you will learn what kind of change in mindset is needed, how to adapt to different architectural constraints, requirements and technical decisions.
The Cisco OpenStack Installer provides automated deployment of OpenStack core components, as well as monitoring, storage, and high availability components. The release schedule of Cisco OSI parallels the community release. Where possible, Cisco OSI provides unmodified OpenStack code. Every new release of Cisco OSI follows the latest community stable release; however, in some cases Cisco might provide more recent patches that have been accepted into the OpenStack stable branches, but have not yet become part of an OpenStack stable release.
The Cisco OSI code update policy is to contribute code upstream to the OpenStack project and absorb patches into Cisco OpenStack Installer after they have been accepted upstream. Cisco deviates from this policy only when patches are unlikely to be reviewed and accepted upstream in time for a release or for a customer deadline (in such cases Cisco applies the patches to the repositories, submits them upstream, and replaces the local change with the upstream version when it is becomes accepted). Cisco also uses and contributes to modules from other upstream sources including Puppet Labs on StackForge.
In this hands on lab you will learn how to deploy OpenStack with the the Cisco OSI - knowledge that you will be able to take back with you to your organization and utilize for your own deployments.
This session proposal came as a result of a conversation on a blog post with Stefano Maffulli with regards to the acceptance of non-developers into the OpenStack world.
What tools are needed to interact with the developers - and the “developly challenged” people who are now starting to interact with wider OpenStack community. Because of the plethora of tools and the substantial on-ramp and learning curve in order to adapt - non-devs are finding it hard to contribute-voice their concerns or help.
This session will go over the tools used today, which tools should be used and when - and what we can expect in the future
Remember – you are the one who decides what content you want to see – your vote counts!