I’ve been experimenting a lot recently with making furniture out of MGP10 structural pine that I machine myself. The first few examples have been work stands for things like my Tormek in the garage. One of the things I need to do when making these stands is to turn a series of machined pine strips into panels. That’s where bar clamps come in handy. I recently discovered where to buy good quality clamps cheaply, and thought I’d share…
Catherine and I decided to make home made vanilla essence as part of our Christmas gifts for 2014. This turned out to be pretty easy, and result is really good. As part of that I turned bottle stoppers for the little decorative bottles we gave the essence out in. I also needed to explore what glue would work with silicone stoppers, which turned out to be a bit of an adventure.
I gave out a bunch of bowls at the work Christmas party, and to my embarrassment many people asked what wood and finish had been used. I of course didn’t remember because I made some of them over six months ago. I’m therefore going to try and do a better job of systematically documenting the things I make. This post is a first attempt at that.
For a while now I’ve been meaning to play with making a Thien Baffle for my garage workshop. The motivation is that whilst I have a quite nice 3HP dust extractor (for those in the market for such a thing — don’t spend $1,400 with some retailers — I am super happy with my $500 unit from Leda Machinery), I want to keep the number of times I change the bags to a bare minimum. I see the dust extractor as a way of controlling potentially dangerous very fine dust, whereas some of the machines in my workshop create a lot of very large shavings — the thicknesser seems like the most obvious culprit here. It would be cool to divert these larger shavings into a bin where I can just use them as garden mulch, and then save the dust extractor bags for the fine and more dangerous dust.
Trigger warning, I suppose. This like a Tom Clancy book, but with weirder sex, much of it non-consensual. Also, not as well thought through or as well researched or as believable. I couldn't bring myself to finish it.
Time for another summary I think, because announcing the review day seems to have caused a rush of new specs to be filed (which wasn't really my intention, but hey). We did approve a fair few specs on the review day, so I think overall it was a success. Here's an updated summary of the state of play: API Add more detailed network information to the metadata server: review 85673. Add separated policy rule for each v2.1 api: review 127863. Add user limits to the limits API (as well as project limits): review 127094. Allow all printable characters in resource names: review 126696. Consolidate all console access APIs into one: review 141065. Expose the lock status of an instance as a queryable item: review 127139 (abandoned); review 85928 (approved). Extend api to allow specifying vnic_type: review 138808. Implement instance tagging: review 127281 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Improve the return codes for the instance lock APIs: review 135506. Microversion support: review 127127 (approved). Move policy validation to just the API layer: review 127160. Nova Server Count API Extension: review 134279 (fast tracked). Provide a policy statement on the goals of our API policies:…
I got asked the other day how the reclaim_instance_interval in Nova works, so I thought I'd write it up here in case its useful to other people. First off, there is a periodic task run the nova-compute process (or the computer manager as a developer would know it), which runs every reclaim_instance_interval seconds. It looks for instances in the SOFT_DELETED state which don't have any tasks running at the moment for the hypervisor node that nova-compute is running on. For each instance it finds, it checks if the instance has been soft deleted for at least reclaim_instance_interval seconds. This has the side effect from my reading of the code that an instance needs to be deleted for at least reclaim_instance_Interval seconds before it will be removed from disk, but that the instance might be up to approximately twice that age (if it was deleted just as the periodic task ran, it would skip the next run and therefore not be deleted for two intervals). Once these conditions are met, the instance is deleted from disk.
We're now a few weeks away from the kilo-1 milestone, so I thought it was time to update my summary of the Nova specifications that have been proposed so far. So here we go... API Add more detailed network information to the metadata server: review 85673. Add separated policy rule for each v2.1 api: review 127863. Add user limits to the limits API (as well as project limits): review 127094. Allow all printable characters in resource names: review 126696. Expose the lock status of an instance as a queryable item: review 127139 (abandoned); review 85928 (approved). Implement instance tagging: review 127281 (fast tracked, approved). Implement the v2.1 API: review 126452 (fast tracked, approved). Improve the return codes for the instance lock APIs: review 135506. Microversion support: review 127127 (approved). Move policy validation to just the API layer: review 127160. Nova Server Count API Extension: review 134279 (fast tracked). Provide a policy statement on the goals of our API policies: review 128560. Sorting enhancements: review 131868 (fast tracked, approved). Support JSON-Home for API extension discovery: review 130715. Support X509 keypairs: review 105034 (approved). API (EC2) Expand support for volume filtering in the EC2 API: review 104450. Implement tags for volumes and…
I originally read this as a series of short stories released on the kindle, but the paperback collation of those has been out for a while and deserved a read. These stories are classic Scalzi, and read well. If you like the Old Man's War universe you will like this book. The chapters of the book are free standing because of how they were originally written, and that makes the book a bit disjointed. The cliff hanger at the end is also pretty annoying given the next book hasn't been released. So, an interesting experiment that perhaps isn't perfect, but is well worth the read.
I don't read a lot of non-fiction, but I decided to finally read this book having had it sit on the shelf for a few years. I'm glad I read it, but as someone who regularly eats in the US I am not sure if I should be glad or freaked out. The book is an interesting study in how industrialization without proper quality controls can have some pretty terrible side effects. I'm glad to live in a jurisdiction where we actively test for food quality and safety. The book is a good read, and I'd recommend it to people without weak stomaches.