Operationalizing the network on target with F5 and Chef
Operationalizing the network continues to be a driving force behind DevOps and SDN. The ability to solve real problems using programmability to automate and orchestrate infrastructure provisioning and configuration across the application release process remains the hope for many interested in one or the other - and often times both. A recent Avaya sponsored, Dynamic Markets survey (reg required) dove deep into the demesne of SDN and found that many of the problems companies have - and expect to be solved by SDN - are directly related to provisioning, configuration and downtime concerns around services and applications across the network. We (as in the corporate We) know that no single vendor is going to be able to solve this challenge. Not alone. SDN and operationalizing the network necessarily requires an ecosystem. And not just an ecosystem comprised of strategically aligned vendor partners, but customers, as well. After all, customers are the ones with the problem to be solved, and no one understands how to best solve that problem like they do. Integration and packaging is something vendors can (and should) do to enable customers to do what they need to do to solve their problems with service configuration, network management and application performance. Because customer processes and environments are not turn key; they aren't one-size fits all. This kind of ecosystem requires an open approach to APIs, integration and sharing of solutions across the entire ecosystem - in every direction. That's why it was so awesome to see what Target recently offered to the Chef community - an F5 BIG-IP Cookbook. One of the goals of F5 through DevCentral has always been to provide customers with the information they need to take advantage of our APIs and this an excellent example of what that can produce. Because it hasn't been just about giving customers the tools, but also encouraging an open-source attitude toward sharing of solutions built around our programmability. That openness turned into something awesome for not just Target but the open source community at large, and offers a great foundation and framework from within which organizations can solve at least one of their service configuration issues with SDN. And because it's a Chef cookbook, that means there are many other cookbooks that can be used to solve some of the other service configuration challenges organizations have. That's what an SDN ecosystem comprised of vendors and customers, enabled by an open source attitude, should be doing. Enabling orgs to solve real challenges and resolve real issues by operationalizing the network. You can find out more about F5 and Chef and how we help operationalize the network this week at Chef Conf (we're hanging at table #T6) or by following F5 on Twitter (@f5networks). If you're looking for more Chef + F5 goodness, feel free to check out these resources: https://supermarket.chef.io/cookbooks/f5/versions/0.2.0 https://devcentral.f5.com/s/articles/automating-web-app-deployments-with-opscode-chef-and-icontrolChefConf 2015 – Automate All Your Puns
#chefconf #f5 Chef turns infrastructure into code. It also gives the casual blog writer a terrible temptation to descend into pun-filled drivel. Which would be a shame as the ability to automate and operationalize our infrastructure has never been more relevant. That’s why I’m excited to be attending Chefconf 2015 in Santa Clara. We will be at stand T6 with a number of F5’ers eager to talk about how to integrate Chef and F5 platforms. More importantly we’re here to listen to how you’d like to do it. I’m hoping we can come away from the show having learnt as much from the attendees as they have from us. I’m looking forward to hearing about scenarios where customers have been able to deploy and build whole architectures and have a BIG-IP or LineRate instance programmatically configured to supply layer 4-7 services to the application. Just as you write recipes for server and software deployments, you probably want to add in things like security, load balancing or SSL decryption. In preparation for the event, I’ve been reviewing and testing out what’s available for Chef and F5 today. There are a few cookbooks out there – most notably from Target – who are also giving a talk at the conference and from Sean Walberg - and a while back we even published a basic F5 develop recipe on Devcentral. These are all great, but they are written to use the SOAP/XML iControl API. I think that there might be an opportunity to do something with the new(er) REST API – iControl REST. iControl REST offers a simpler but still powerful API that uses JSON for sending key:value pairs to the BIG-IP – something Chef users will be familiar with. It’s really well documented and there are some great examples in the code share and a functional Ruby script. The LineRate platform, too has been REST API enabled from day one and is ready to automate. So if you‘d like to bring your Chef skills to our booth, we’ll be happy to run though the API and how to create, configure and delete objects and settings on our platforms using iControl. The REST is up to you (I’m sorry I held out as long as I could).
