Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.

Register now! openstacksummitfall2012.eventbrite.com
View analytic
Monday, October 15 • 5:20pm - 6:00pm
General Bare-Metal Provisioning Framework

Sign up or log in to save this to your schedule and see who's attending!

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.


Speakers
avatar for Ken Igarashi

Ken Igarashi

Sr. Research Engineer, NTT DOCOMO, NTT docomo
Ken Igarashi is one of the first members of proposing OpenStack Bare Metal Provisioning (currently called "Ironic"). He is leading OpenStack based private cloud team as a developer and operator.
DK

David Kang

David Kang received Ph.D. at the department of Computer Science from University of Maryland at College Park, Maryland, U.S.A. in 1999, M.S. degree in Electrical and Computer Engineering at Carnegie Mellon University, Pittsburgh, U.S.A. in 1993, and B.S. degree in Computer Engineering, Seoul National University, Seoul, South Korea, in 1988. Since 1999, he is a computer scientist at University of Southen California - Information... Read More →
avatar for Mikyung Kang

Mikyung Kang

USC/ISI
Mikyung Kang received B.S., M.S., and Ph.D. degrees in Computer Science and Statistics from Jeju National University, Jeju, South Korea, in 1998, 2001, and 2006. In 2007, she was a research scholar at University of Southen California - Information Sciences Institute (USC/ISI), Arlington, Virginia, U.S.A. Since Feb. 2008, she is a research programmer II in the Adaptive Parallel Execution (APEX) research group at USC/ISI. Her research interests... Read More →


Monday October 15, 2012 5:20pm - 6:00pm
Manchester A

Attendees (113)