It’s increasingly complex to map disaster recovery (DR) business requirements to business processes, service requirements and technology. How do you make sense of it all? Here are some things to think about as you consider DR in the context of modern, 'cloudy' IT.
After following the first three posts, we now have a Rackspace Private Cloud powered by OpenStack running with two Controllers (HA) and three Computes. So now what? Well the first thing we need to do is get our hands dirty with the OpenStack Networking component, Neutron, and create a network that our instances can be spun up on.
In this infographic, we visualize some of the biggest—and most intriguing—sources of data in the world, some from our own customers.
In the first two posts I covered the basics: what hardware is involved and the basic network services that form the basis of my Rackspace Private Cloud install. In this post, I set up Rackspace Private Cloud to give an OpenStack environment consisting of highly available Controllers running as a pair with services such as the OpenStack APIs, Neutron, Glance and Keystone and three compute servers allowing me flexibility to do some testing.
In the first part of this series, I introduced the kit that makes up my home lab. There’s nothing unusual or special in the kit list, but it certainly is affordable and makes entry into an OpenStack world very accessible. This post explains some more basics of my networking: DHCP, DNS, Proxy and TFTP.
With OSCON underway this week in Portland, it's fitting that open source software played a major role in the discovery that Harry Potter author J.K. Rowling penned a new book under a pseudonym.