TACKLING BIG-IP BLUE-GREEN DEPLOYMENTS IN PRIVATE CLOUD USING F5 & VMWARE ANSIBLE MODULES 1 Eric McLeroy, Sr. Specialist Solutions Architect, Ansible by Red Hat [email protected]Payal Singh, Principal Solution Engineer, F5 Networks [email protected]
26
Embed
TACKLING BIG-IP BLUE-GREEN DEPLOYMENTS IN PRIVATE … F5 Tackling BIG IP... · TACKLING BIG-IP BLUE-GREEN DEPLOYMENTS IN PRIVATE CLOUD USING F5 & VMWARE ANSIBLE MODULES 1 Eric McLeroy,
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
TACKLING BIG-IP BLUE-GREEN DEPLOYMENTS IN PRIVATE CLOUD USING F5 & VMWARE ANSIBLE MODULES
Global Load BalancingGeographic load balancingInfrastructure Monitoring
BIG-IP LTM
BIG-IP LTM
LTM VIP visibility into BIG-IP DNS
HOW IT WORKS
Wide IP(my-wide-ip.example.com)
Pool
LTM1 Virtual IP
LTM2 Virtual IP
Members
Users
VIP down OR Pool down
Pool of Servers
Pool of Servers
100%
BIG-IP BIG-IP
LTM
13
DEMO
1) PROVISION AND LICENSE A VIRTUAL BIG-IP ‘LTM2’ IN VMWARE
2) SWITCH TRAFFIC FROM ‘LTM1’ TO ‘LTM2’
Demo Part1
Develop an automated workflow to provision, license and configure a BIG-IP in a VMware environment
Spin up BIG-IP in vCenter * BIG-IP VE template is created on vcenter
Reconfigure the network adaptor settings
Grab the VM IP assigned by DHCP to the BIG-IP VE
License the BIG-IP VEOnboard the BIG-IP (Hostname/NTP/DNS/SSHD)
Network the BIG-IP (VLAN/Self-IP)
Import and activate the ASM policy
Add pool members and pool
Add virtual server and attach the ASM policy to it
Ansible Tower
Playbook
Provision the BIG-IP with ASM module
1
2
vCenter
BIG-IP LTM2
15
DEMO PART1: VIDEO AND PLAYBOOK WALKTHROUGH
Demo Part2
Steps:• Setup connectivity between LTM2 and DNS• Add LTM2 to DNS WideIP pool• For traffic switch: Disable the virtual server on LTM1
MGMT IP – 10.192.73.218Self-IP – 10.168.68.10
Virtual IP – 10.168.68.11
BIG-IP
Data Center
BIG-IP LTM1 VE
MGMT IP – 10.192.73.246Self-IP – 10.168.68.5
Virtual IP – 10.168.68.12
MGMT IP – 10.192.73.219Self-IP – 10.168.68.100Listener Virtual IP – 10.168.68.101 (53)
BIG-IP LTM2 VE
Setup complete with DNS Connectivity to be setup with DNS
17
DEMO PART2: VIDEO AND PLAYBOOK WALKTHROUGH
Alternative Solutions
If a Static MGMT IP needs to be assigned to the BIG-IP instead of using DHCP for MGMT IP (BIG-IP Version 13.1+)
1) Edit the OVA file using a tool like COT (Common OVF Tool) cot edit-properties <source filename>.ova -p net.mgmt.addr=""+string -p net.mgmt.gw=""+string –p user.root.pwd=""+string -p user.admin.pwd=""+string -u -o <destination filename>.ova
2) Edit the OVA (template) properties so that when you deploy BIG-IP VE, you can specify values for the management IP address and default passwords. Example snippet
3) Use an Ansible playbook to execute deploying the OVA file (Step 2)https://github.com/f5rstahl/simple-ansible-playbookhttps://github.com/payalsin/f5-ansible/tree/master/playbooks/spinup-demo/static
Get started on your automation journey:• www.f5.com/supernetopsLearn more about solution: (webinars, modules, blogs)– www.ansible.com/f5Solution Overview: • https://www.f5.com/pdf/solution-center/f5-ansible-overview.pdfWhitepaper: – https://f5.com/Portals/1/PDF/Partners/automating-f5-big-ip-platform-with-ansible.pdfCurrent F5 modules in Ansible core:– http://docs.ansible.com/ansible/list_of_network_modules.html#f5Request feature-enhancements:– https://github.com/F5Networks/f5-ansible/issuesDownload Current Ansible (2.6):– http://releases.ansible.com/ansible/