It’s funny.\u00a0 When we recently started working on an upgrade of our Intranet social media platform, and we were trying to figure out how to meld the infrastructure-change-heavy operation with the need for devs, designers, and testers to be able to start working on the system before “three months from now,” we broached the idea of “maybe we should do that in iterations!”\u00a0 First, get the new wiki up and working.\u00a0 Then, worry about tuning, switching the back end database, etc.\u00a0 Very basic, but it got me thinking about the problem in terms of “hey, Infrastructure still operates in terms of waterfall, don’t we.”<\/p>\n
Then when Peco and I moved over to NI R&D and started working on cloud-based systems, we quickly realized the need for our infrastructure to be completely programmable – that is, not manually tweaked and controlled, but run in a completely automated fashion.\u00a0 Also, since we were two systems guys embedded in a large development org that’s using agile, we were heavily pressured to work in iterations along with them.\u00a0 This was initially a shock – my default project plan has, in traditional fashion, months worth of evaluating, installing, and configuring various technology components before anything’s up and running. \u00a0 But as we began to execute in that way, I started to see that no, really, agile is possible for infrastructure work – at least “mostly.”\u00a0 Technologies like cloud computing help, but there’s still a little more up front work required than with programming – but you can get mostly towards an agile methodology (and mindset!).<\/p>\n
Then at OpsCamp last month<\/a>, we discovered that there’s been this whole Agile Operations\/Automated Infrastructure\/devops movement thing already in progress we hadn’t heard about.\u00a0 I don’t keep in touch with The Blogosphere ™ enough I guess.\u00a0 Anyway, turns out a bunch of other folks have suddenly come to the exact same conclusion and there’s exciting work going on re: how to make operations agile, automate infrastructure, and meld development and ops work.<\/p>\n So if\u00a0 you also hadn’t been up on this, here’s a roundup of some good related core thoughts on these topics for your reading pleasure!<\/p>\n It’s funny.\u00a0 When we recently started working on an upgrade of our Intranet social media platform, and we were trying to figure out how to meld the infrastructure-change-heavy operation with the need for devs, designers, and testers to be able to start working on the system before “three months from now,” we broached the idea […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[85],"tags":[172,628,632,631],"class_list":["post-398","post","type-post","status-publish","format-standard","hentry","category-automation","tag-agile","tag-automation","tag-devops","tag-operations"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n