Menu

Chef Supermarket

Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

View our collection of guides, documentation, and articles

Cookbooks
Advanced Options

Select Badges

Select Supported Platforms

Select Status

RSS

f5-bigip (4) Versions 0.5.2

Installs/Configures f5-icontrol

Policyfile
Berkshelf
Knife 
cookbook 'f5-bigip', '~> 0.5.2', :supermarket
cookbook 'f5-bigip', '~> 0.5.2'
knife supermarket install f5-bigip
knife supermarket download f5-bigip
README
Dependencies
Changelog
Quality 0%

f5-bigip cookbook

Build Status

Control F5 load balancer config

Requirements

An F5 to manage

Usage

You assign this to a node to manage an F5 devices

Attributes

  • node['f5-bigip']['credentials']['databag'] - Databag with credentials
  • node['f5-bigip']['credentials']['item'] - Databag Item with credentials
  • node['f5-bigip']['credentials']['key'] - Key in Databag Item with credentials
  • node['f5-bigip']['credentials']['host_is_key'] - Set to true to grab specific credentials for each f5 host based on f5 hostname being used as a key in the specified databag::item
  • node['f5-bigip']['provisioner']['databag'] - Databag that contains an item for each f5 you want to manage with f5::provisioner. Check test/integration/data_bags/f5-provisioner-* for sample data bag structures.

Definitions

f5_vip

This definition is a wrapper for the f5_ltm_node, f5_ltm_pool and f5_ltm_virtual_server LWPRs. It allows you to specify all the required info into the f5_vip definition which will then be translated into the necessary LWRP declarations.

Parameters

Attr Default/Req? Type Description
f5 REQUIRED String f5 to create the node on
nodes REQUIRED Array[String] Nodes (ip addresses) to load balance the VIP against
pool REQUIRED String Name to create node with
lb_method LB_METHOD_ROUND_ROBIN String Load balancing method
monitors [] Array[String] Monitors to check that nodes are available
virtual_server resource's name String Name of virtual server to create on f5
destination_address REQUIRED String Destination IP Address
destination_port 443 Integer Destination Port
vlan_state 'STATE_DISABLED' String Wether list of VLANs are disabled or enabled
vlans [] Array[String] List of VLANs to enabled or disable based on vlan_state
profiles [{<br/>'profile_context' => 'PROFILE_CONTEXT_TYPE_ALL',<br/>'profile_name' => '/Common/tcp'<br/>}] Array[Hash] Profiles to associate to virtual server
snat_type 'SRC_TRANS_NONE' String Snat type to set on virtual server
snat_pool '' String Snat pool to use if snat_type set to 'SRC_TRANS_SNATPOOL', otherwise ignored
default_persistence_profile '' String Default persistence profile to associate with virtual server
fallback_persistence_profile '' String Fallback persistence profile to associate with virtual server
rules [] Array[String] iRules to associate with virtual server

Example

The simplest VIP declartion that takes as many defaults as possible:
ruby
f5_vip 'testing.test.com' do
f5 'test-f5.test.com'
nodes ['10.10.10.10', '10.10.10.11']
pool 'test-pool'
destination_address '192.168.1.10'
end

It will create
* Two nodes, named after their ip addresses
* A pool referencing the nodes as members with no monitors
* A virtual server listening on <destination_address>:443

A fully user defined VIP:
ruby
f5_vip 'testing.test.com' do
f5 'test-f5.test.com'
nodes ['10.10.10.10', '10.10.10.11']
member_port 4443
pool 'test-pool'
lb_method 'LB_METHOD_RATIO_MEMBER'
monitors ['/Common/https', '/Common/tcp']
destination_address '192.168.1.10'
destination_port 8443
profiles [
{ 'profile_context' => 'PROFILE_CONTEXT_TYPE_ALL', 'profile_name' => '/Common/tcp' },
{ 'profile_context' => 'PROFILE_CONTEXT_TYPE_ALL', 'profile_name' => '/Common/http' }
]
vlan_state 'STATE_ENABLED'
vlans ['/Common/vlan123', '/Common/vlan234']
snat_type 'SRC_TRANS_SNATPOOL'
snat_pool '/Common/snat_pool'
default_persistence_profile '/Common/test_persistence_profile'
fallback_persistence_profile '/Common/test2_persistence_profile'
rules ['/Common/_sys_auth_ldap', '/Common/_sys_auth_radius']
end

LWRPs

These LWRPs allow you to idempotently manage various F5 resources. This is accomplished by using a 'proxy' node that manages the F5 through the use of the F5's APIs.

f5_ltm_node

f5_ltm_node - Used to manage nodes.

Attributes

Attr Default/Req? Type Description
node_name The resource name String Name to create node with
address node_name String IP address to create node with
f5 REQUIRED String f5 to create the node on
enabled true true/false State node should be in

If the address attribute is unset, the node_name (which in turn defaults to the resource's name) will be used instead.

Examples

The following creates a node with name and address of 10.10.10.10:
ruby
f5_ltm_node '10.10.10.10' do
f5 'f5-test.test.com'
enabled true
end

The following creates a node named test-node.test.com with 10.10.10.10 as the ip address:
ruby
f5_ltm_node 'test-node.test.com' do
address '10.10.10.10'
f5 'f5-test.test.com'
enabled true
end

f5_ltm_pool

f5_ltm_pool - Used to manage pools

Attributes

Attr Default/Req? Type Description
pool_name The resource name String Name to create node with
f5 REQUIRED String f5 to create the node on
lb_method LB_METHOD_ROUND_ROBIN String Load balancing method
monitors [] Array[String] Monitors to check that pool members are available
members [] Array[Hash] Members to add to the pool

Example

f5_ltm_pool 'test' do
  f5 'f5-test.test.com'
  lb_method 'LB_METHOD_ROUND_ROBIN'
  monitors ['http']
  members [
    {
      'address'   => '10.10.10.10',
      'port'      => 80,
      'enabled'   => true
    },
    {
      'address'   => '10.10.10.11',
      'port'      => 80,
      'enabled'   => true
    }
  ]
end

f5_ltm_monitor

f5_ltm_monitor - Used to manage monitors.

Attributes

Attr Default/Req? Type Description
monitor_name resource's name String Name of monitor to create on f5
f5 REQUIRED String f5 to create the node on
parent 'https' String Name of parent monitor
interval 5 Integer Monitor interval
timeout 16 Integer Monitor timeout
dest_addr_type 'ATYPE_STAR_ADDRESS_EXPLICIT_PORT' String Address types used to differentiate various node definitions
dest_addr_ip '0.0.0.0' String IP address
dest_addr_port 443 Integer Port
user_values {} Hash Hash of user specific values

Example

f5_ltm_monitor 'test' do
  f5 'f5-test.test.com'
  parent '/Common/new_https'
  interval 20
  timeout 40
end

f5_ltm_virtual_server

f5_ltm_virtual_server - Used to manage virtual servers

Attributes

Attr Default/Req? Type Description
vs_name resource's name String Name of virtual server to create on f5
f5 REQUIRED String f5 to create the node on
destination_address REQUIRED String Destination IP Address
destination_port REQUIRED Integer Destination Port
default_pool REQUIRED String Pool for virtual server to use
vlan_state 'STATE_DISABLED' String Wether list of VLANs are disabled or enabled
vlans [] Array[String] List of VLANs to enabled or disable based on vlan_state
profiles [{<br/>'profile_context' => 'PROFILE_CONTEXT_TYPE_ALL',<br/>'profile_name' => '/Common/tcp'<br/>}] Array[Hash] Profiles to associate to virtual server
snat_type 'SRC_TRANS_NONE' String Snat type to set on virtual server
snat_pool '' String Snat pool to use if snat_type set to 'SRC_TRANS_SNATPOOL', otherwise ignored
default_persistence_profile '' String Default persistence profile to associate with virtual server
fallback_persistence_profile '' String Fallback persistence profile to associate with virtual server
rules [] Array[String] iRules to associate with virtual server
enabled true true/false Enable or disable the virtual server

Example

f5_ltm_virtual_server 'vs_new' do
  f5 'f5-test.test.com'
  destination_address '10.11.10.10'
  destination_port 80
  default_pool 'new'
  enabled true
end

Recipes

  • f5-bigip::default - install the required packages and gems required to interact with the F5 API.
  • f5-bigip::provisioner - Make the node that is assigned this recipe an f5 provisioner system. This recipe will dynamically define LWRPs to create the nodes, pools and virtual servers as defined by the databag value node['f5']['provisioner']['databag'].
    • Each item in the databag represents an F5
    • Basically lets you define your F5 with JSON
    • Example @ [test/integration/data_bags/f5-provisioner-1/test.json](test/integration/data_bags/f5-provisioner-1/test.json)

Testing

Installing gems with bundler is a little different then normal in this case. The f5-icontrol gem supported by F5 is not on rubygems.org. There IS an f5-icontrol gem on rubygems.org that is not what we want that someone else created.

So for convenience the f5-icontrol gem from F5 is included with this cookbook. For spec testing the Gemfile references f5-icontrol. Using the :path option to reference the local gem does not work per https://github.com/bundler/bundler/issues/2298. So I used the workaround described in the referenced issue.

bundle install --no-cache

Then run the tests!

bundle exec foodcritic -f any -f ~FC015 -X spec .
bundle exec rspec --color --format progress
bundle exec rubocop

Notes on Integration Testing

Why Vagrant

This cookbook uses Vagrant combined with Virtualbox and chef-minitest for testing. It would be great to use test-kitchen instead. Unfortunately there are several reason Vagrant is a better solution for this cookbook:

  • test-kitchen does not support multiple VMs natively
  • test-kitchen does not support multiple converges
  • test-kitchen creates/destroys the environment every run making testing take longer
    • Testing for this cookbook can be done with Vagrant's 'provision' which leaves the VMs up and running. test-kitchen was taking about 5min per test run whereas Vagrant takes 45 seconds per test run.

Using Vagrant with lab F5 hardware

To use Vagrant you'll first need to make sure you have the following vagrant plugins:

  • vagrant-omnibus (1.4.1 tested)
  • vagrant-berkshelf (3.0.1 tested)

You'll need to modify [test/integration/data_bags/f5/creds.json](test/integration/data_bags/f5/creds.json) with the correct username/password.

Then you'll need to update hostname in [test/integration/data_bags/f5-provisioner-1/test.json](test/integration/data_bags/f5-provisioner-1/test.json) and [test/integration/data_bags/f5-provisioner-2/test.json](test/integration/data_bags/f5-provisioner-2/test.json) with the IP address of the F5 to connect to.

Finally, update any IPs in the minitest files with the IP of your F5: [files/default/tests/minitest/create_test.rb](files/default/tests/minitest/create_test.rb), [files/default/tests/minitest/provisioner_test.rb](files/default/tests/minitest/provisioner_test.rb)

Now you should be able to create an admin node AND run a test:

vagrant up admin

After the VM have been created subsequent testing can be done by doing:

vagrant provision admin

Notes for maintainers with access to F5 VE Vagrant box

If you have access to an F5 VE Vagrant box

Create test environment AND run a test:

vagrant up

After the VMs have been created subsequent testing can be done by doing:

vagrant provision

License and Authors

Author:: Jacob McCann (jacob.mccann2@target.com)

Copyright:: 2013, Target Corporation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

chef-vault >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

f5-bigip Cookbook CHANGELOG

This file is used to list changes made in each version of the f5-bigip cookbook.

v0.5.2

  • Remove subdirs in libraries folder (#9)

v0.5.1

  • Bugfix: Load System.Inet interface (#7)

v0.5.0

  • Add support for non-ip node name to f5_ltm_node

v0.4.1

  • Uptick to re-upload to supermarket after encountering CHEF-672 which caused knife to upload with missing library files

v0.4.0

  • Initial Release

Collaborator Number Metric 
            
0.5.2 failed this metric
Failure: Cookbook has 1 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric 
            
0.5.2 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric 
            
0.5.2 failed this metric
FC064: Ensure issues_url is set in metadata: f5-bigip/metadata.rb:1
FC065: Ensure source_url is set in metadata: f5-bigip/metadata.rb:1
FC066: Ensure chef_version is set in metadata: f5-bigip/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: f5-bigip/metadata.rb:1
FC069: Ensure standardized license defined in metadata: f5-bigip/metadata.rb:1
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_config_sync.rb:59
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:96
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:110
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:123
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:136
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:168
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_monitor.rb:227
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_node.rb:71
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_node.rb:83
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_node.rb:85
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_node.rb:125
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_pool.rb:85
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_pool.rb:98
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_pool.rb:117
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_pool.rb:135
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_pool.rb:147
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:132
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:145
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:158
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:174
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:186
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:204
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:222
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:234
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:319
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:340
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:347
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:354
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:391
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:403
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:417
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:446
FC085: Resource using new_resource.updated_by_last_action to converge resource: f5-bigip/libraries/provider_ltm_virtual_server.rb:461
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric 
            
0.5.2 failed this metric
Failure: Cookbook should not contain binaries. Found:
f5-bigip/files/default/f5-icontrol-11.4.1.0.gem

Testing File Metric 
            
0.5.2 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric 
            
0.5.2 failed this metric
Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number

target-cookbooks target-cookbooks
Jacob McCann

Details

View Source View Issues

Updated March 17, 2016 Created on

Supported Platforms

    None Specified

License

Apache 2.0

Download Cookbook