blog.oddbit.com

So, the Kilo release notes say: nova-manage migrate-flavor-data But nova-manage says: nova-manage db migrate_flavor_data But that says: Missing arguments: max_number And the help says: usage: nova-manage db migrate_flavor_data [-h] [--max-number <numb…

I work for an organization that follows the common model of assigning people systematically generated user ids.

In an OpenStack environment, cloud-init generally fetches information from the metadata service provided by Nova.

Next week is the Red Hat Summit in Boston, and I’ll be taking part in a Project Atomic presentation in which I will discuss various (well, two) options for deploying Atomic into an OpenStack environment, focusing on my heat-kubernetes templates.

Someone named hithard on StackOverflow was trying to clone a git repository via https, and was running into an odd error: “Cannot communicate securely with peer: no common encryption algorithm(s).”.

Because nobody asked for it, this is my opinion on the use of the MAINTAINER directive in your Dockerfiles.

This is a terrible hack.

Most major distributions now provide “cloud-enabled” images designed for use in cloud environments like OpenStack and AWS.

I recently had the chance to help a colleague debug some problems in his OpenStack installation.

This is another post that is primarily for my own benefit for the next time I forget how to do this.

If a picture is worth a thousand words, then code that generates pictures from words is worth…uh, anyway, I wrote a script that produces dot output from Pacemaker start and colocation constraints: https://github.com/larsks/pacemaker-tools/ You can pass th…

I’ve recently spent some time working with Pacemaker, and ended up with an interesting collection of XPath snippets that I am publishing here for your use and/or amusement.

In some ways, the most exciting thing about Docker isn’t the ability to start containers.

This is a long-form response to this question, and describes how to get the nova-docker driver up running with devstack under Ubuntu 14.04 (Trusty).

I have recently started running some “real” services (that is, “services being consumed by someone other than myself”) on top of Kubernetes (running on bare metal), which means I suddenly had to confront the question of how to provide external access to K…

This post comes about indirectly by a request on IRC in #rdo for help getting nova-docker installed on Fedora 21.

I saw a request from a customer float by the other day regarding the ability to filter the XML used to create Nova instances in libvirt.

In this post, we’ll look at a method for building minimal Docker images for dynamically linked ELF binaries, and then at a tool for automating this process.

While working with Docker the other day, I ran into an undesirable interaction between Docker and systemd services that utilize the PrivateTmp directive.

I regularly use OpenStack on my laptop with libvirt as my hypervisor.

I have recently been doing some work with Kubernetes, and wanted to put together a minimal image with which I could test service and pod deployment.

One of the new features available in the Juno release of OpenStack is support for serial console access to your Nova servers.

Setting the stage I ran into a problem earlier this week deploying RDO Icehouse under RHEL 6.

Recently, I’ve been playing around with Fedora Atomic and Kubernetes.

While experimenting with Fedora Atomic, I was looking for an elegant way to automatically deploy Atomic into an OpenStack environment and then automatically schedule some Docker containers on the Atomic host.

If you want to build a Windows image for use in your OpenStack environment, you can follow the example in the official documentation, or you can grab a Windows 2012r2 evaluation pre-built image from the nice folks at CloudBase.

I like Docker, but I’m not a huge fan of using shell scripts for complex system configuration…and Dockerfiles are basically giant shell scripts.

The current version of Docker has a very limited set of networking options: bridge – connect a container to the Docker bridge host – run the container in the global network namespace container:xxx – connect a container to the network namespace of another…

Would you like to run some custom Python code when Nova creates and destroys virtual instances on your compute hosts?

Sometimes you want to quickly share a screenshot with someone.

I ran a Google Hangout this morning on Deploying with Heat.

I spent some time today learning about Heat autoscaling groups, which are incredibly nifty but a little opaque from the Heat command line, since commands such as heat resource-list don’t recurse into nested stacks.

This is a companion to my article on the Docker plugin for Heat.

This post accompanies my article on the Docker plugin for Heat.

I have been looking at both Docker and OpenStack recently.

This is a companion to my article on the Docker plugin for Heat.

I’ve been playing with Docker a bit recently, and decided to take a look at the nova-docker driver for OpenStack.

Until recently I had a bcache based setup on my laptop, but when forced by circumstance to reinstall everything I spent some time looking for alternatives that were less disruptive to configure on an existing system.

Update (2018-03-22) Since I wrote this document back in 2014, Docker has developed the macvlan network driver.

For a small project I’m working on I needed to attach a few buttons to a Raspberry Pi and have some code execute in response to the button presses.

After a recent upgrade of my Fedora 20 system to kernel 3.15.mumble, I started running into a problem (BZ 1121345) with my Docker containers.

In the old days (so, like, last year), Neutron supported a single external network per L3 agent.

This article expands on my answer to Add multiple specific IPs to instance, a question posted to ask.openstack.org.

I’ve just put a video on Youtube that looks at the steps required to set up the external bridge (br-ex) on a single-interface system:

In my previous post I discussed a problem I was having setting a persistent MAC address on an OVS bridge device.

Normally I like to post solutions, but today’s post is about a vexing problem to which I have not been able to find a solution.

Termshare is a tool for sharing your terminal in a browser session.

These are my notes on making OpenStack play well with firewalld and NetworkManager.

I run OpenStack on my laptop, and I’ve been chasing down a pernicious problem with OVS bridge interfaces under both F19 and F20.

Due to an unfortunate incident involving sleep mode and an overheated backpack I had the “opportunity” to rebuild my laptop.