Linux brought us main stream open source software. OpenStack gave us open source cloud but we aren't done yet. Open Compute has arrived. The Open Compute Project is an open source hardware platform that will change the way we design and deploy data centers. From software definition to supply chain management to efficiency, Open Compute will prove to be a game changer in the scale out data center.
We will discuss how the open source Cloud Foundry project is used by Appfog to extend OpenStack to create true hybrid clouds. Inter-cloud connections and workload portability across various instances of OpenStack will be dived into. Demonstrations of how developers can simply create applications in their language of choice, deploy to instances of public OpenStack-based Clouds (i.e. HP Public Cloud, Rackspace, etc.), and easily move workloads from one cloud to another will be shown.
Comcast has been building out its private cloud to host its next-generation Cloud TV platform (http://techcrunch.com/2012/05/21/comcast-x1/), and as part of that effort the Comcast Silicon Valley Innovation Center has developed and in the process of open sourcing a compatible version of Amazon's Simple Notification Service (SNS) and Simple Queue Service (SQS) that we plan to contribute to or integrate with OpenStack. We've built these services on top of Redis (http://redis.io/) and Cassandra (http://cassandra.apache.org/) for multi-data-center availability and extreme scalability and very low latency.
I'd like to present the work we've done to date and get feedback from the OpenStack community. By the time of this conference our code will be open sourced on GitHub and available to the community.
With one production service already available at Rackspace and another on in the works at HP, cloud database services are quickly changing the landscape around OpenStack Compute. Join Rackspace and HP for a lively discussion on how we are adding value to OpenStack with database services (Project RedDwarf). As more companies move their applications and data to the cloud, it is becoming increasingly difficult to manage and maintain database systems on default virtual servers. RedDwarf simplifies database management in the cloud while providing a model for extensible service deployment that will be used to deliver not only database services, but also other services in the future. In this session you will get a chance to hear about RedDwarf’s progress and future plans and learn how you can become active in the community.
The Ceilometer project was started 6 months ago on the realisation that all public cloud provider wanting to use OpenStack would need to rewrite exactly the same code to properly meter the use of their infrastructure. Ceilometer stated goal is not to provide a full billing solution. It deliberately limits itself to the first phase: collecting the information needed to establish billing lines.
The project description states:
"Ceilometer aims to deliver a unique point of contact for billing systems to aquire all counters they need to establish customer billing, accross all current and future OpenStack components. The delivery of counters must be tracable and auditable, the counters must be easily extensible to support new projects, and agents doing data collections should be independent of the overall system."
A first version of Ceilometer will be released in parallel to Folsom's release, and the project has been submited as an incubation project in OpenStack.
This session aims at providing an overview of what the project offers today, how to deploy it and how it can be connected to rating and billing engines.
Ceph is an open source distributed object store, network block device, and file system. Ceph can be used for object storage through its S3-compatible REST interface. 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. With 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 RBD behind both, new VMs can be created faster while using less space. This session will cover the current status of the integration, and discuss the technical implications and the advantages of block storage within the OpenStack cloud operating system.
This talk provides an overview of Heat, a peek inside the CloudFormation template language, and a live demonstration of heat technologies. Heat provides an Apache 2 licensed CloudFormation orchestration engine that orchestrates cloud infrastructure resources such as storage, networking, instances, and applications into a repeatable running environment for OpenStack IAAS platforms. Heat also provides several advanced features such as authentication, nested stacks, high availability, and auto-scaling which are demonstrated.
The audience will learn how Heat applies to OpenStack cloud environments using repeatable orchestration templates. OpenStack Summit attendees can learn about the emerging CloudFormation template standard and its impact on Linux and open source cloud communities. A speaker experienced with live demonstrations makes the medium technical difficulty approachable through real-life examples.
Nova (OpenStack Compute) gives us agility and flexibility for computing infrastructures. Virtualization plays an important role in Nova to provide those agility and flexibility; however, there is a performance penalty caused by virtualization. For example, there is significant performance degradation for response time and context switch on virtualized servers compared to bare-metal servers. Some (non-x86 based) machine architectures of interest to technical computing users have either poor or non-existent support for virtualization. Also some users want to use bare-metal machine itself w/o virtualization. One alternative to using virtualization to provision hardware in a cloud environment is to do bare-metal provisioning: rebooting the machine to a fresh system image before handing over control to the user, and wiping the local hard drive when the user is done with the resources.
NTT docomo and USC/ISI are proposing "General Bare-Metal Provisioning Framework on OpenStack (http://wiki.openstack.org/GeneralBareMetalProvisioningFramework)" to solve the problems. In the framework, we extended legacy schedulers to be able to provision an instance to both virtual and bare-metal machines. We also introduced a new nova-compute node that can manage several bare-metal machines. We embedded fault-tolerance of the nova-compute, since the failure of the nova-compute affectes to several bare-metal machines. x86_64 and TILEPro64 machines have already supported and more cpu architectures can be supported by adding CPU specific drivers to the nova compute node (e.g. power management and OS installation).
Using this, we can install VM image to a bare-metal machine directly using exact same API used in Nova. Since there is no hypervisor that isolates users from underlying resources, we integrated several components to achieve the same isolation level as provided by Nova. We replaced the following Nova functions to manage bare-metal machines.
1. Turn the power on and off -> IPMI (PXE) or PDU (non-PXE)
2. VM image provisioning -> PXE or non-PXE Boot
3. Network isolation -> Quantum + OpenFlow
4. iSCSI isolation -> IP access limitation
5. Console Access -> Serial over LAN
We believe this function gives several benefits to users.
1. A user can provision an instance to a virtual machine and a bare-metal machine through the same API. Therefore, we can use all the ecosystem created on top of Nova for a bare-metal server provisioning. For example, we can extend/shrink Nova Compute nodes based on a resource utilization using Auto-Scaling for VM.
2. We can migrate an instance from a virtual machine to a bare-metal machine based on a server load.
3. We can manage/update Nova infrastructure using Nova.
4. Various heterogeneous architectures (e.g. ARM, GPU) can be incorporated into the cloud with the bare-metal provisioning technique. We have shown provisioning the systems with x86_64 and TILEPro64 processors as bare-metal machines.
During the presentation, we will explain the current architecture proposed for grizzly release and a way of supporting new CPU architectures. We will also demonstrate auto-scaling of Nova compute by using this function.
