F5 Meetup presentation automation 2017

Editor's Notes

• #6: This is where iApps come into play. iApps are the templatization of application delivery policy. iApps take all the rich functionality that we learned from our Alliance Partnerships, that same application fluency that formed the deployment guides, and turns them into an intuitive, wizard-style implementation. As an example, I saw this demo myself in one of our Technology Centers, the Exchange Deployment Guide, all 119 pages of instruction, which takes a typical admin a week to work through, this was boiled down to 5 simple questions. In just a couple of minute, the same complex, yet functionally rich implementation has taken place and, here’s a really important part, no functionality was sacrificed. You’ll see the market followers out there pushing ease of deployment, but without F5’s history and application fluency, they will fall short of expectation.
• #7: This is where iApps come into play. iApps are the templatization of application delivery policy. iApps take all the rich functionality that we learned from our Alliance Partnerships, that same application fluency that formed the deployment guides, and turns them into an intuitive, wizard-style implementation. As an example, I saw this demo myself in one of our Technology Centers, the Exchange Deployment Guide, all 119 pages of instruction, which takes a typical admin a week to work through, this was boiled down to 5 simple questions. In just a couple of minute, the same complex, yet functionally rich implementation has taken place and, here’s a really important part, no functionality was sacrificed. You’ll see the market followers out there pushing ease of deployment, but without F5’s history and application fluency, they will fall short of expectation.
• #8: https://devcentral.f5.com/wiki/iApp.AppSvcsiApp_overview.ashx
• #11: All these programmability options are not in silos We have TMSH which is like CLI on the box with pretty good TCL scripting capabilities iControl REST and SOAP you guys must be aware off iApps Which is packaged business logic we will talk about the same iCall this is for visibility and conrtrol iRule this to manipulate the application traffic both at server side and client side. Like I said all these capabilities are not in Silos they are very well used to gether.
• #30: Device = Physical BIG-IP and VE RPM (Node.js) Libraries: Provisioning Settings & Reset Download: https://devcentral.f5.com/d/f5-devops-library-provisioning-230 Provision BIG-IP device NTP servers & timezone Licensing BIG-IP using single registration key, supports BYOL Syslog server FQDN Device name DNS search domain list Factory Reset BIG-IP Device Factory reset via standard iControl REST API Eliminates all data plane configuration, device trust, and system settings Management IP and licenses are not reset HA Pairing Download: https://devcentral.f5.com/d/f5-devops-library-clustering-231 Provision a basic BIG-IP HA pair 2 device Active/Standby cluster Single default traffic group Automatic cluster synchronization (CMI) Creation of vLAN and self-IP for HA sync
• #31: Puppet support iApp v1 (TCL) deployments. NOT iApps LX (Node.js). Puppet Proxy is needed when Puppet Agent cannot be loaded directly on the managed device. Target wrote a Chef cookbook which is on their own GitHub repository (not on F5’s GitHub) Ansible module docs: https://github.com/F5Networks/f5-ansible/tree/master/docs/modules