Community Training Classes & Labs > F5 Programmability Training Index
Module 1: Imperative Automation with the BIG-IP iControl REST API¶
![digraph breadcrumb {
rankdir="LR"
ranksep=.4
node [fontsize=10,style="rounded,filled",shape=box,color=gray72,margin="0.05,0.05",height=0.1]
fontname = "arial-bold"
fontsize = 10
labeljust="l"
subgraph cluster_provider {
style = "rounded,filled"
color = lightgrey
height = .75
label = "Provider"
bigip [label="BIG-IP",color="steelblue1"]
iapps [label="iApp Templates\n& Deployments"]
iwf_templates [label="Service\nTemplates"]
}
subgraph cluster_tenant {
style = "rounded,filled"
color = lightgrey
height = .75
label = "Tenant"
iwf_catalog [label="Service\nCatalog"]
iwf_deploy [label="Service\nDeployment"]
}
iwf_deploy -> iwf_catalog -> iwf_templates -> iapps -> bigip
}](../../_images/graphviz-8f6e1e6309cc8bb48fd578ead6ceecdbce4b69cd.png)
In this module you will learn the basic concepts required to interact with the BIG-IP iControl REST API. Additionally, you will walk through a typical Device Onboarding workflow to deploy a fully functional BIG-IP Active/Standby pair. It’s important to note that this module will focus on demonstrating an Imperative approach to automation.
Note
The Lab Deployment for this lab includes two BIG-IP devices. For most of the labs, we will only be configuring the BIG-IP A device (management IP configuration and licensing has been completed). BIG-IP B will have some minimal configuration pre-loaded. In real-world scenario, it would be necessary to perform Device Onboarding functions on ALL BIG-IP devices. In this lab exercise, we chose to perform it only on a single device due to lab time allocation constraints.
Note
In order to confirm the results of REST API calls made in this lab, it’s recommended to keep GUI/SSH sessions to BIG-IP and iWorkflow devices open. By default, BIG-IP and iWorkflow will log all the REST API related events locally to restjavad.0.log . These logs can also be directed to a remote syslog server (see https://support.f5.com/csp/article/K13080). On a side note, the ltm log files listed below contains log messages specific to BIG-IP local traffic management events.
- BIG-IP:
- /var/log/ltm
- /var/log/restjavad.0.log
- iWorkflow:
- /var/log/restjavad.0.log
- Lab 1.1: Exploring the iControl REST API
- Lab 1.2: REST API Authentication & ‘example’ Templates
- Lab 1.3: Review/Set Device Settings
- Lab 1.4: Basic Network Connectivity
- Lab 1.5: Building Imperative Workflows with Postman Collections
- Lab 1.6: Build a BIG-IP Cluster using a Collection
- Lab 1.7: Build a Basic LTM Config using REST Transactions