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
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.
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).
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
Software systems produce events but often do so in non-uniform ways. A system may log information to a file in a grammar that requires comprehension to extract meaning from the output. A system may also send events to other systems in a structured manner such as REST. Other systems may event output events directly into a database for storage or pass them to a queue for distribution to interested consumers.
In highly diverse, clustered environments like those seen in many OpenStack deployments, the system event landscape can become complex, difficult to manage and over time become opaque to the point where events generated no longer provide value. The information in many of these events have definite business value, whether it be to meter a tenant or to communicate that a portion of the cluster has been damaged or degraded. Therefore, it’s imperative, despite the complexity of the event ecosystem, to capture this information in a standardized and scalable manner.