Automatic maintenance of tag feeds
I recently added some scripts to automatically generate tag feeds for
my blog when pushing new content. I'm using GitHub Pages to publish
everything, so it seemed easiest to make tag generation part of a
pre-push hook (new in Git 1.8.2). This hook is run automatically as
part of the
git push operation, so it's the perfect place to insert
generated content that must be kept in sync with posts on the blog.
Enabled blog comments
json-tools: cli for generating and filtering json
Interacting with JSON-based APIs from the command line can be difficult, and OpenStack is filled with REST APIs that consume or produce JSON. I've just put pair of tools for generating and filtering JSON on the command line, called collectively json-tools.
Both make use of the Python dpath module to …read more
Quantum in Too Much Detail
I originally posted this article on the RDO website.
This document describes the architecture that results from a particular OpenStack configuration, specifically:
- Quantum networking using GRE tunnels;
- A dedicated network controller;
- A single instance running on a compute host
Much of the document will be relevant to other configurations, but details will vary based on your choice of layer 2 connectivity, number of running instances, and so forth.
The examples in this document were generated on a system with Quantum
networking but will generally match what you see under Neutron as
well, if you replace
neutron in names. The OVS flow
rules under Neutron are somewhat more complex and I will cover those
in another post.
Moving to GitHub
This blog has been hosted on scriptogram for the past year or so. Unfortunately, while I like the publish-via-Dropbox mechanism, there have been enough problems recently that I've finally switched over to using GitHub Pages for hosting. I've been thinking about doing this for a while, but the things that finally pushed me to make the change were:
- Sync problems that would prevent new posts from appearing (and that at least once caused posts to disappear).
- Lack of any response to bug reports by the site maintainers.
A benefit of the publish-via-Dropbox mechanism is, of course, that I already had all the data and didn't need to go through any sort of export process.read more