Have you ever seen a problem in OpenStack where a VM loses its IP address? If you have, you know what a problem it can be — especially if you have a large number of nodes and VMs. Your clients get frustrated as they start losing connectivity with their VMs for no obvious reason. Even the cloud support team gets frustrated, as everything appears to be working with no hints in the log files as to what might be wrong. In this blog post, I would like to share my experience with OpenStack networking, and specifically the DHCP subcomponent that is responsible for allocating an IP address to a VM.
In the first part of this series discussing native replication in OpenStack Database (Trove) we talked about the different types of replication and how they work. Now we’re going to look at the community use-cases that replication solves, and at the ways in which we can implement these replication methods.
Glance can be used from the command line to do more than just add an image to a cluster. Here are some examples of what you can do with it.
Next up in our “Meet your OpenStack Training Instructor” series, we spend a few moments talking with Reza Roodsari. Tell us more about your background. How did you become involved in OpenStack training? Just like the satisfaction a person receives after they put together a good puzzle, I have always had passion for working with complex, intricate systems. For me, the cloud is …
(Guest Post) In May we announced the tech preview of the Oracle’s Distribution for OpenStack for Oracle Linux and Oracle VM. As we have been doing for many years with Linux and Xen, we plan to work with the OpenStack community and help make OpenStack an enterprise grade alternative for cloud deployments. We are very pleased with the Mirantis announcement today stating that Mirantis will offer …
One thing about OpenStack is that you can find lots of information on how to do specific things, such as start an instance or install a test cloud on VirtualBox, but there isn’t much out there to give you the Big Picture, such as how to design a massively-scalable OpenStack cloud, or a cloud that’s optimized for delivering streaming content. That’s why this past week a dozen OpenStack experts and writers from companies across the OpenStack ecosystem gathered at VMware’s Palo Alto campus for the OpenStack Architecture Design Guide book sprint. The intent was to deliver a completed book on designing OpenStack clouds — in just five days.
A busy week in OpenStack, headlined by the release of Swift 2.0 with Storage Policies, the launch of Project Calico -- an open source Layer 3 SDN architecture that meets requirements for NFV, and the release of RHELOSP 5.0. Meanwhile, contributors to the third OpenStack Book Sprint created a massive OpenStack Architecture Design Guide, soon to be available for download …
On July 8, Red Hat released version 5 of the Red Hat Enterprise Linux OpenStack Platform. RHELOSP 5.0 is based on April’s Icehouse release of OpenStack, plus RH Enterprise Linux 7, and RH Enterprise Virtualization 3.4 — both released last month. The new spin will offer three years of support, double that of RHELOSP 4, released seven months ago.
Network virtualization pioneers Metaswitch Networks announced the launch of Project Calico, to which they’ve contributed the initial codebase under a (permissive) Apache license. Calico uses Layer 3 internet core routing technologies and tools like Border Gateway Protocol (BGP) for route discovery to network VMs and hosts, whole datacenters, and multiple datacenter locations via carrier networks. The Calico project is part of Metaswitch’s Neuron initiative, which provides a continuous framework for Network Function Virtualization (NFV) that meets the needs of both datacenter operators running VM/host architectures with lots of virtualized tenant clusters and networks (i.e., the typical OpenStack use-case), and carriers building extremely high-density data centers that virtualize at Layer 3 and may use container-based (e.g., Docker, Flynn) isolation schemes.
On Tuesday last, OpenStack Object Storage (Swift) released an upgrade hailed as the most significant since the project was initially open sourced. Swift 2.0 debuts Storage Policies, a simplified way to dynamically requisition storage meeting application requirements for storage tier/medium type, speed, capacity, replication level — even geographic area, to enable compliance with data sovereignty laws and regulations. Extensions to the Storage Policies scheme will support additional new features expected later this year, such as Erasure Coding.