The folks here at Intel see me as a bit of an Ubuntu fanboy. For the most part, I spend a lot of time in the lab working on the ONP Server using CentOS. For me, it is less about being an Ubuntu fan and more about using a platform that is easier choice for Openstack developers. I recently had an opportunity to peel off an extra ONP Server and install the new Ubuntu 15.04 to have a look.
OpenStack Swift is a highly available, distributed, eventually consistent object/blob store. Object Storage is ideal for cost effective, scale-out storage. It provides a fully distributed, API-accessible storage platform that can be integrated directly into applications or used for backup, archiving, and data retention. For more information please refer http://docs.openstack.org/developer/swift/.
Openstack* is a highly flexible open source virtualization management and orchestration software solution. Openstack* establishes virtual machine (VM) connectivity based on the many networking options supported by Neutron. Neutron abstracts Linux network configurations using
OpenStack employs DevStack for integration testing and development purposes. In previous iterations of DevStack, baremetal provisioning was only simulated via Ironic by having physical machines replaced with virtual machines.
With recent patches supplied by Intel, the ability to test/tryout baremetal provisioning is more simple and easy. Previously DevStack could only support Ironic configuration using the pxe_ssh driver. Patches have now made the agent_ipmitool driver available as well. Rapid baremetal setup is now much easier with this additional DevStack support.
This article explores the internal details of provisioning a physical machine using OpenStack*. Steps for setting up OpenStack are included, and no special hardware is required to begin use. If you already use OpenStack, follow these instructions using the hardware you currently have. If you are new to OpenStack, you will need a commodity access switch and two physical servers with ports connected to a switch that is on the same VLAN or broadcast domain.