Too much going on:
Now, I will go back to drafting documentation while I wait for AT&T to reconfigure my DSL and kill my landline. I've had a POTS ("plain old telephone service") twisted-pair line longer than most people on earth have been alive. After today, no longer. I don't think I'll miss it, either. I only have it because I have a business-class DSL, which I don't need anymore, and the only people who call it want money from me.
Odd that I'm finding this out through the Chicago Tribune:
Amazon.com has introduced a way for users to quickly save and send news articles as well as other items to their Kindle devices for later, off-line reading.
The new feature can be added by users in a variety of ways. Amazon has made it possible for users to send items to their Kindles through Web browser extensions for Google Chrome and Firefox, as a feature that can be installed on Macs or PCs, from Google Android mobile devices, or from users' emails.
Cool. Look for the button to appear on The Daily Parker very soon.
Now that I can send directly to Kindle, and after having Instapaper crash frequently on my Android device, I might switch. Though this does underscore the risks start-ups take when they develop relatively simple ideas into software. Other, larger companies can kill you.
I've fixed seven annoying bugs and added three minor features to Weather Now, including:
- Fixed searching from the search box so you can enter an airport code directly;
- Fixed the Last 24 hours page to show day and night icons properly;
- Added a status page so users can peek under the hood; and
- Tweaked a few things in the background worker process around logging and status update alerts.
A minor bug fix release like this used to take a couple of hours to deploy, because I had to update the code running on the web server file-by-file. I got the process down to about an hour—but I still had to bring the application offline to make the update.
Since I put it up in Microsoft Windows Azure, publishing an update takes about 15 minutes, is completely automated, and doesn't require taking the site down. The great Inner Drive migration continues to pay dividends.
Regular blog readers know that since moving to my current apartment in February 2008, the Inner Drive Technology International Data Center has occupied a couple square meters of my home office. I've also mentioned lower energy use since I started to move everything out of the IDTIDC and into Microsoft Azure.
Something else has happened to my electricity bill. In November, we citizens of Chicago voted to pool our electricity buying to get the lowest electricity cost possible. Well, the new regime kicked in last month, and the 660 kw/h I used in February cost 25% less than the 610 kw/h I used in January—which was the lowest use ever for this place.
It helps, also, that since moving my email to the cloud in June, I've used an average of 224 kw/h less electricity each month year-over-year.
I can't wait to see my bill for March. They read my meter on the 7th or 8th to prepare the bill I just got; the IDTIDC shut down on the 10th.
After four years or so, I've changed the Daily Parker's skin.
Looking back at my other, dead blog enticed me to play with the theme control for a few minutes. And then I decided, you know, Mads Simple looks really clean and elegant, but I'm kind of tired of it.
So? Blue enough for you?
Years ago, I had two blogs: one for work, and one for everything else. Eventually I stopped having two blogs because...well, laziness?
The old blog is back. I discovered I had dead links, and it was simple enough to drag the old blog out of archives and throw it onto my general-purpose VM.
Actually, I cheated. I only threw the content up there. I used The Daily Parker's blog engine with all its customization and just copied the old content up to the VM.
It's kind of interesting, looking back on the things I was working on seven years ago. I am particularly happy, given everything I did this past weekend, to link back to November 2006, when I built my last data center.
I'm paying 90% of my attention right now to a Windows Azure online training class. I already knew a lot of the material presented so far, but not all of it. It's like re-taking a class you took as an undergraduate; the 10% you didn't know is actually really helpful.
Like next week's class, which will go over Infrastructure as a service: a lot has changed in the last year, so it should be valuable.
Apparently, though, my homework is to build an Azure web site this week. Not a multi-tier application with a worker role. Just a web site. How adorable.
The Inner Drive Technology International Data Center is no more.
This morning around 8:15 CDT I updated the master DNS records for Weather Now, and shut down the World Wide Web service on my Web server an hour later. All the databases are backed up and copied; all the logs are archived.
More to the point, all the servers (except my domain controller, which also acts as a storage device) are off. Not just off, but unplugged. The little vampires continue to draw tens of Watts of power even when they're off.
The timing works out, too. My electric meter got read Thursday or Friday, and my Azure billing month starts today. That means I have a clean break between running the IDTIDC and not running it,* and by the beginning of May I'll have more or less the exact figures on how much I saved by moving everything to the Cloud.
Meanwhile, my apartment is the quietest it's ever been.** The domain controller is a small, 1U server with only one cooling fan. Without the two monster 2U units and their four cooling fans (plus their 12 hard drives), I can suddenly hear the PDC...and now I want to shut it down as well.
* Except for the DSL and land-line, which should be down in a couple of weeks. I'll still have all the expense data by May.
** Except for the two blackouts. Now, of course, I never need worry about a blackout again—unless it hits the entire country at once, which would create new problems for me.
Weather Now is fully deployed to the Cloud. As soon as the Worker Role finishes parsing the last few hours of weather, I'll cut over the DNS change, and it will be live.
Actually, that's not entirely true; I'm going to cut over the DNS in the morning, after I know I fixed the bugs I found during this past week's shake-down cruise.* So if you want to see what a weather site looks like while it's back-filling its database, you can go to its alias, http://wx-now.cloudapp.net. (Because of how Azure works, this will remain its alias forever.)
Time to meet my friends, who are wondering where I am, no doubt.
* Bugs fixed: 13. Total time: 6.9 hours (including 2.4 to import and migrate the Gazetteer).
The final deployment of Weather Now encountered a hitch after loading exactly 3 million (of 7.2 million) place names. I've now kludged a response for the remaining 4.2 million rows, and a contingency plan should that upload fail.
Meanwhile, I have a saturated Internet connection. So rather than sit here and watch paint dry, so to speak, I'm bringing back some of the bugs that I decided to postpone fixing. The end result, I hope, will be a better-quality application than I'd planned to release—and a rainy Saturday made useful.