Sorry for the lack of updates, it's been rather busy! I'm on my 7th draft beer of the night (from my own keg) and I figured that I am appropriately drunk to make a post. I've been making a lot of progress in system management, including Ansible and one-off scripts. Ansible is so hardcore... I love every bit of using it. Every time we come across a system-wide issue, instead of thinking "How long will this take 6 people to complete" I think "How could I implement this in Ansible and knock it out today?"
So far as I've seen, Ansible is an incredibly sturdy system with a lot of built-in modules that can already accomplish 99% of what I need to do. The other 1% can be accomplished with a 50-100 line shell script that I can integrate directly into Ansible and provide extra functionality for custom applications... which is absolutely fantastic. System consistency and integrity is just a few lines of BASH, and voila! I can run it against the entire datacenter in one go.
"But G4," you might ask, "Why not use Puppet or Chef?" Why, the answer is simple! Puppet and Chef require a lot more time and effort to set up. A lot of companies need to dedicate an entire team just to configuring these systems. With Ansible, I've gotten an entire datacenter's worth of configuration management finished in just two weeks. I haven't gone it alone, though... I've had a bit of input from one of the Sysadmins and a few people from my team. But seriously... The number of people it takes to get Ansible going effectively can be as low as 1. Especially if you're running a simple Apache stack or simple clustering. If you're clever and learn quickly, you can knock this stuff out by yourself. It really is incredible.
In personal news, I got my new copter all tuned in so that I can do flips. It feels a lot more responsive than my old flight controller (Multiwii (old) vs KK2.0) and I feel like I can do a lot with it. The only things I'm missing now are GPS position hold and return to home... plus a little bit more granular control over flight characteristics. The KK2 doesn't have board-controlled curves, so I have to do that on my transmitter... but that's just a little issue, and I'm not really concerned about it. What really matters is that I can still do lazy rolls through the sky, and have a nice, solid link and responsive feedback. I'll post some videos up on here when it warms up a bit.
In other news, I now have my own draft system for beer. It's been quite a hassle... Midwest Supplies is normally very reliable for me, but this time has been quite a misstep for them. They initially told me they'd have my keg to me last Tuesday at the latest, and then it took a week for them to ship it, and another 3 days to get to me. I was pretty happy when I saw the package at the door, and then I opened the box... and it was a keg short. Kegs are easy to count. They're big. How do you miss one? Normally you'd expect that if you spend over $300 somewhere they'll actually pay attention to the order. But, I suppose not. I'm definitely going to think twice about ordering kegs from them again.
At any rate, though, my beer is turning out better than I expected after the initial taste test. It absorbed a lot of flavor from a previous failed brew (superclove cider), but it seems to be balancing out quite nicely after only a day of conditioning. I'm excited to see how it turns out in a few weeks. But, until then, I'll be doing my next brew on Saturday. Glory to Arstostka!
So far as I've seen, Ansible is an incredibly sturdy system with a lot of built-in modules that can already accomplish 99% of what I need to do. The other 1% can be accomplished with a 50-100 line shell script that I can integrate directly into Ansible and provide extra functionality for custom applications... which is absolutely fantastic. System consistency and integrity is just a few lines of BASH, and voila! I can run it against the entire datacenter in one go.
"But G4," you might ask, "Why not use Puppet or Chef?" Why, the answer is simple! Puppet and Chef require a lot more time and effort to set up. A lot of companies need to dedicate an entire team just to configuring these systems. With Ansible, I've gotten an entire datacenter's worth of configuration management finished in just two weeks. I haven't gone it alone, though... I've had a bit of input from one of the Sysadmins and a few people from my team. But seriously... The number of people it takes to get Ansible going effectively can be as low as 1. Especially if you're running a simple Apache stack or simple clustering. If you're clever and learn quickly, you can knock this stuff out by yourself. It really is incredible.
In personal news, I got my new copter all tuned in so that I can do flips. It feels a lot more responsive than my old flight controller (Multiwii (old) vs KK2.0) and I feel like I can do a lot with it. The only things I'm missing now are GPS position hold and return to home... plus a little bit more granular control over flight characteristics. The KK2 doesn't have board-controlled curves, so I have to do that on my transmitter... but that's just a little issue, and I'm not really concerned about it. What really matters is that I can still do lazy rolls through the sky, and have a nice, solid link and responsive feedback. I'll post some videos up on here when it warms up a bit.
In other news, I now have my own draft system for beer. It's been quite a hassle... Midwest Supplies is normally very reliable for me, but this time has been quite a misstep for them. They initially told me they'd have my keg to me last Tuesday at the latest, and then it took a week for them to ship it, and another 3 days to get to me. I was pretty happy when I saw the package at the door, and then I opened the box... and it was a keg short. Kegs are easy to count. They're big. How do you miss one? Normally you'd expect that if you spend over $300 somewhere they'll actually pay attention to the order. But, I suppose not. I'm definitely going to think twice about ordering kegs from them again.
At any rate, though, my beer is turning out better than I expected after the initial taste test. It absorbed a lot of flavor from a previous failed brew (superclove cider), but it seems to be balancing out quite nicely after only a day of conditioning. I'm excited to see how it turns out in a few weeks. But, until then, I'll be doing my next brew on Saturday. Glory to Arstostka!