Support: 1-800-961-4454
Getting an application designed, tested and running, then updating and improving it is no easy task — even in the best of times. There is a continuing quest for tooling that delivers automation of this work to allow more focus on what matters most: fast, efficient development. This automation is increasingly sought via a platform service layer that abstracts the compute, networking and storage details of the infrastructure service layer — offering simplification for application developers and the cloud operators who support them.
Adding Extra Compute Nodes to Rackspace Private Cloud
You are pouring a sizeable portion of your life into building a world-class product. Amid the stress and passion of building out new features and fixes, it is important to also develop the discipline of automated testing and configuration management. Here’s why:
Austin-based writer and artist Austin Kleon kicked off SXSW Interactive with his panel called “Show Your Work,” based on his latest book by the same title. Kleon argued that showcasing the creative process holds as much benefit for the creator as the end result. By showing your work, you are not operating in isolation, but becoming part of a scene. This community is where ideas are exchanged and valuable networks are made.
So 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. For the home lab, I have dumb unmanaged switches – and I take advantage of that by creating a Flat Network that allows my instances access out through my home LAN on the subnet.
When we started OpenStack, the goal was to form a community of like-minded companies and contributors to push for an open alternative to proprietary cloud software. We saw open source as a platform to foster swift innovation and to give customers more choice.
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.
Every year, hundreds of developers, users and administrators of OpenStack apply to speak at the annual OpenStack Summit, which takes place May 12 through May 16 this year in Atlanta.
Introduction I am frequently asked by analysts, users, the media and even other vendors about the production readiness of OpenStack, to which I affirm in the positive. There are also often questions about the differences between the various OpenStack distributions and offerings. I answer whenever possible by drawing the distinction between OpenStack as the open source project and as the products and services available to help make it a production-ready cloud platform. If you are unclear about the difference between an open source project and a product, I hope this blog post serves as a useful primer. I will highlight the concept of OpenStack as a service offering (yes, Cloud-as-a Service is a thing) to the concepts of project and product, using our Rackspace Private Cloud (RPC) as the canonical example for both a product and a service. To help illustrate the distinctions, I will discuss the differences between the three offerings by examining three categories:
Racker Powered
©2014 Rackspace, US Inc.