![\"Screen](\"http:\/\/blogs.nd.edu\/devops\/files\/2014\/07\/Screen-Shot-2014-07-01-at-11.42.45-PM.png\")
<\/a><\/p>\nWhat do we have now that we didn’t have before?<\/p>\n
- \n
- two Rails apps in production<\/li>\n
- a Banner API\u00a0<\/strong>poised to serve as a key data integration point for\u00a0the future<\/li>\n
- an automated app deployment tool<\/a><\/li>\n
- a new workflow<\/a> that\u00a0empowers developers and speeds app deployment<\/li>\n
- puppet manifests to create consistency between developer VMs and deployment environments (satisfying point 10 of the Twelve-Factor App<\/a>)<\/li>\n<\/ul>\n
<\/p>\n
What else?<\/p>\n
- \n
- the experience\u00a0to extend API services to other\u00a0data sources and consumers<\/li>\n
- an architectural framework for future Rails app development<\/li>\n
- a boatload of fresh Ruby on Rails knowledge<\/li>\n<\/ul>\n
<\/p>\n
Automation + Collaboration = Innovation. \u00a0Sound familiar? \u00a0These new practices and processes\u00a0are enhancing\u00a0our agility, velocity, and ability to deliver quality functionality to users.<\/p>\n
Big Thanks<\/h3>\n
I have often observed that some of the most fulfilling times working in the OIT are on outage weekends. \u00a0Communication is quick and actions are decisive\u00a0as disparate OIT teams come\u00a0together, often in the same room, to bring new functionality to our campus constituents. That unity of purpose is the heart of DevOps, and I am pleased to say that I have seen it happen on a day-to-day basis recently. Let me highlight some of the people and teams who made\u00a0this week a success, and who are laying\u00a0the foundation for a bright future of ND application development.<\/p>\n
Information Security<\/h4>\n
Jason Williams<\/strong> and his team were attentive and helpful in defining best practices for handling database and API credentials — something that is a little different in the new technology stack. \u00a0Not only that, but when we needed Webinspect scans done or firewall rules put in place quickly, Jason’s team was ready to jump in and take action to help us go live.<\/p>\n
Database Administration<\/h4>\n
Fred Nwangana<\/strong>‘s team was\u00a0involved from early on, helping shape how Rails applications would work in our environment. \u00a0Together we determined that this moment presents a great opportunity to decouple custom apps from the Banner database. \u00a0Vincent Melody<\/strong> in particular was a great help in provisioning database resources and helping drive\u00a0forward our process standardization.<\/p>\n
Change Control<\/h4>\n
Julie Stogsdill<\/strong> and Matt Pollard<\/strong>‘s contributions have been tremendous. \u00a0I came to them with Launchpad and a pretty clear agenda of putting TEST environment deployments in developers’ hands. \u00a0Rather than objecting to this idea, they helped me find ways to integrate the process into our change control system<\/a>. \u00a0The new workflow is even more flexible than I had hoped, and has already allowed us to push important changes to production, via RFC, without a hint of dread that the process is too slow.<\/p>\n
System Administration \/\u00a0Virtualization<\/h4>\n
I wrote\u00a0puppet manifests to provision our servers, but I would have gotten nowhere in our local infrastructure without help from Chris Fruewirth<\/strong>‘s team. \u00a0Milind Saraph <\/strong>and\u00a0Joseph Franco<\/strong>, plus\u00a0John Pozivilko <\/strong>from the virtualization team,\u00a0were a great help in creating hosts in VMWare, assigning IPs, updating systems, and answering lots of questions when my limited sysadmin knowledge hit a wall. \u00a0Plus, we are all going to be working toward increasing\u00a0puppet infrastructure management in the future. \u00a0Good stuff ahead there!<\/p>\n
Just the Beginning<\/h3>\n
People used to ask me how the new job was going. \u00a0There were so many things up in the air; how could I really give an answer? \u00a0So I’d say something like “ask me in six months.” \u00a0Well, now you can ask me any time, because the apps are live, the processes are working, and we are ready to take on new development challenges. There’s still more to tackle: expanding configuration management; exploring cloud infrastructure; implementing comprehensive\u00a0monitoring. \u00a0But for now, I want\u00a0to pause and say “thank you” to everyone who helped get us to this point. \u00a0Onward!<\/p>\n","protected":false},"excerpt":{"rendered":"
Last week, several new processes and technologies were asked\u00a0to sink or swim as the OIT and the Office of the Registrar brought\u00a0two new Ruby on Rails applications to production. \u00a0I’m pleased to announce that\u00a0due to a confluence of thorough planning, … Continue reading
- an automated app deployment tool<\/a><\/li>\n