neutron/neutron/services/loadbalancer/drivers/radware/workflows
Avishay Balderman 98c1ce4c1f Radware LBaaS driver implementation
Change-Id: I43f666ed6716c16b0ef95bc7ed58c4c422a7fd89
Implemnts: blueprint radware-driver-for-lbaas
2013-10-07 17:24:15 +02:00
..
common/groovy Radware LBaaS driver implementation 2013-10-07 17:24:15 +02:00
openstack_l2_l3 Radware LBaaS driver implementation 2013-10-07 17:24:15 +02:00
openstack_l4 Radware LBaaS driver implementation 2013-10-07 17:24:15 +02:00
readme.txt Radware LBaaS driver implementation 2013-10-07 17:24:15 +02:00

readme.txt

The Radware LBaaS driver uploads ADC workflows on-demand into vDirect. The ADC Workflows are composed from files which are located underneath this workflows directory.
The workflows directory is part of the Radware LBaaS driver code included in OpenStack.

Those ADC Workflows are instantiated and run in the vDirect Virtual Machine.
Radware's OpenStack LBaaS driver, uses vDirect REST API to activate those workflows and CRUD configuration in the Alteon device.

An ADC workflow is composed from:
1. A mandatory XML file called workflow.xml which defines the different states and the transition flow between states as well as "linking" to the actual code that can be done on each state.
2. ADC Configuration Template files with extension .vm which are using an extended apache velocity template engine syntax
3. ADC Configuration Groovy script file with extension .groovy