openstack Featured New Game Plus - Resurgence: (re)taking the cloud by storm It's been a couple months, so I'm checking in to talk about how NG+ at Rackspace has been going, things I've learned, where some issues have been, and alluding to where we're going as this next chapter gets underway. * Yes, the cloud
btrfs Featured Migrating a BTRFS Volume Between Devices When using BTRFS volumes it's sometimes necessary to move things around. BTRFS has some great tools to assist operators to move volumes and this post will cover one available method. What is this post about While the reasons to move a device from one place to another are
openstack-ansible Nova-Compute + LVM, an IOPS Love Story The OpenStack Nova project has long had the ability to provision instances into logical volumes however in my travels I've found most deployments don't use it as the go-to instance storage. However recently I've been asked by a couple folks how it can be
openstack-ansible Minimal OpenStack-Ansible deployment Deploying OpenStack-Ansible, and following the deployer documentation, will result in a production-ready OpenStack Cloud. A typical deployment requires operators to setup various network interfaces, use different VLAN tags, and create several purpose-built bridges. But what if these typical requirements couldn't be met or what if the goal was
nspawn Featured OpenStack-Ansible machinectl image management With recent changes in OpenStack-Ansible we're now able to import and export container images for using the built-in systemd tooling via machinectl. This gives us the ability to rapidly provision or replace containers as needed from a pre-seeded source. In this post, I'll cover how an
nspawn OpenStack-Ansible Machinectl Storage setup When using the machinctl container storage backend you've got choices on how to setup your host machines. This article will cover the three very common deployment situations. 1. Simply let systemd back the /var/lib/machines directory using a loop device file which has been formatted BTRFS; this
nspawn Networkd for nspawn with OpenStack-Ansible Within this post, I will cover the systemd-networkd aspect of the PR to create a systemd-nspawn driver within OSA. This post will be working with systemd-networkd and systemd-resolved to integrate nspawn containers within the existing topology of a typical OpenStack-Ansible deployment. Getting systemd-networkd working for you One of the container
nspawn Featured Nspawn OpenStack with OpenStack-Ansible The OpenStack-Ansible project has been around for a few years now but if you're unfamiliar with it, the TL;DR is it's an OpenStack deployment project running OpenStack services within containers and uses Ansible. The original project came from the Rackspace Private Cloud, and when it
cloud Rolling Restart using OpenStack-Ansible Sometimes it's useful to do a rolling restart of OpenStack services throughout the cloud. In OpenStack-Ansible we've the means to make this easy, you just need a little BASH to tie it all together. In this little aside, I'm restarting the entire cloud using
enroll Featured OSIC Enrolling Baremetal (Ironic) Nodes The OSIC has a diverse set of hardware specifications that we provide to our users. Because of the hardware profile diversity enrolling nodes within Ironic requires a little bit of tender love and care to get them all happy. To ease the enrollment process a playbook was created which allows
ironic Featured OSIC Building Baremetal (Ironic) Images This is a quick rundown on the steps used to create the OSIC baremetal images. For a more detailed rundown on Ironic image building please read the following post. Install required apt packages apt-get install -y qemu uuid-runtime curl kpartx Install the disk-image-builder (DIB) pip install diskimage-builder --isolated Clone the
osic Featured OSIC Baremetal (Ironic) Access Quick Start List: * Getting Started * Getting SSH Access * Getting HTTP Access * Adding Keys to an Existing jump box * Building Baremetal nodes * Notes Getting started 1. Login to the OSIC at "https://cloud1.osic.org": 2. Access Cloud1 "RegionOne" to build your jump box: 3. Create a
openstack Enable Automated Ironic Cleaning Enabling the Ironic Automated cleaning in OpenStack-Ansible is recommended for every deployment. While this is an "optional" setting, it should be enabled for general stability and data security; if you're not familiar with the Ironic cleaning service please review the documentation found here. Sadly the automated
openstack Featured Multi-hypervisor OpenStack Cloud Chose your own mis-adventure TL;DR Just tell me how to do it When deploying an OpenStack cluster its highly likely that you will, at some point, want to dive into other compute types allowing a project the ability to chose the best compute resources based on their needs. While
cloud Finding variable collision in Ansible from group_vars When you start building large complicated Ansible deployments the likely hood that your using group_vars in new and exiting ways is VERY high due to the desire to co-locate configuration for nodes based on group membership into once place. If you are at the point where nodes are members
openstack Auto tests patches for OpenStack-Ansible with OpenStack If you have access to an OpenStack cloud that can accept user-data then spinning up a test node for a given patch is super simple. All you need to do is create a user-data script with the following contents: #!/bin/bash OS_REPO="https://git.openstack.org/openstack/openstack-ansible-os_
rackspace Auto-deploy an OpenStack-Ansible using "nova boot" with user-data Building an OpenStack-Ansible test deployment within an OpenStack cloud has never been simpler; just boot the node, pass some user-data, profit! Before building instances, check the system requirements to ensure you're building VMs of an adequate size. If you're access to the OpenStack environment is through
