Applies To:

Show Versions Show Versions

Manual Chapter: Deploying iWorkflow Virtual Edition
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

About VE Xen Project deployment

To deploy the iWorkflow™ Virtual Edition (VE) system on Xen Project, you perform these tasks:

  • Verify the host machine requirements.
  • Deploy an iWorkflow™ system as a virtual machine.
  • Deploy a BIG-IP® system.
  • After you have deployed the virtual machines, log in to the iWorkflow VE system and run the Setup utility. Using the Setup utility, you perform basic network configuration tasks, such as assigning VLANs to interfaces.
  • Configure secure communication between the iWorkflow system and the BIG-IP device.

Host machine requirements and recommendations

To successfully deploy and run the iWorkflow™ VE system, the host system must satisfy minimum requirements.

The host system must include these elements:

  • CentOS, Debian, Fedora, RHEL, or Ubuntu with the Community Xen package. The Virtual Edition and Supported Hypervisors Matrix, published on the AskF5™ web site, http://support.f5.com identifies the Linux versions that are supported.
  • Connection to a common NTP source (this is especially important for each host in a redundant system configuration)
Important: The hypervisor CPU must meet the following requirements:
  • Use a 64-bit architecture.
  • Have support for virtualization (AMD-V or Intel VT-x) enabled.
  • Support a one-to-one thread-to-defined virtual CPU ratio, or (on single-threading architectures) support at least one core per defined virtual CPU.
  • Intel processors must be from the Core (or newer) workstation or server family of CPUs.

Deploying the iWorkflow VE virtual machine

The primary task in deploying iWorkflow™ VE on the open source Xen Project environment is creating and executing a configuration file that sets up most of what you need to get up and running.

Important: Do not modify the configuration of the Xen Project guest environment with settings less powerful than the ones recommended in this document. This includes the settings for the CPU, RAM, and network adapters. Doing so might produce unexpected results.
  1. In a browser, open the F5 Downloads page (https://downloads.f5.com).
  2. Download the iWorkflow v2.x/Virtual Edition file package. The file name ends in .qcow2.zip.
    The file package creates a 95GB disk footprint at installation.
  3. Extract the two files from the Zip archive and save them where your qcow2 files reside on the Xen Project server.
    Important: Two files are created when you extract the qcow file. You must install the larger file first.
    • The name of the larger file is similar to iWorkflow-<version_number>.<build_number>.qcow2.
    • The name of the smaller file is similar to iWorkflow-<version_number>.<build_number>.DATASTOR.LTM.qcow2.
  4. Generate a MAC address for the network interface card associated with the management interface.
    Important: Be sure that the MAC address you create starts with the prefix 00:16:3e:.
    To create this address, you can use a tool such as MAC Address Generator (http://www.miniwebtool.com/mac-address-generator/).
  5. Use an editor to create an iWorkflow VM definition file that specifies the required parameters for your VM.
    # vi /etc/xen/<config_file_name>
    Important: The sample configuration file provided here serves only as an example of the kinds of parameters you need to specify for your virtual machine. The actual file that you create will likely contain different parameters and settings.
    Note: Internal and external interfaces are optional and not required. iWorkflow does not require multiple network interfaces.
                        name = <config_file_name>
                        maxmem = 4096
                        memory = 4096
                        vcpus = 2
                        builder = "hvm"
                        boot = "c"
                        pae = 1
                        acpi = 1
                        apic = 1
                        hpet = 1
                        localtime = 0
                        on_poweroff = "destroy"
                        on_reboot = "restart"
                        on_crash = "restart"
                        sdl = 0
                        vnc = 1
                        vncunused = 1
                        keymap = "en-us"
                        disk = [ 'tap:qcow2:/<vdisk_path>/iWorkflow-<version_number>.<build_number>.qcow2,hda,w', 
                                  'tap:qcow2:/<vdisk_path>/iWorkflow-<version_number>.<build_number>.DATASTOR.LTM.qcow2,hdb,w',]
                        vif = [ "mac=00:16:<mgmt_interface_mac>,bridge=mgmtbr,script=vif-bridge",
                        "mac=00:16:3e:<external_interface_mac>,bridge=ext_bridge,script=vif-bridge",
                        "mac=00:16:3e:<internal_interface_mac>,bridge=int_bridge,script=vif-bridge",]
                        parallel = "none"
                        serial = "pty"
                        #pci = [ '05:10.0', '05:10.1' ]
                        
    Important: The last line of the example configuration file contains an optional entry that specifies the IDs for PCI external and internal network interface cards (NIC). This optional entry is required for SR-IOV support. Naturally, if you use this entry, you omit the external and internal bridges specified in the vif section.
    Once you have perfected and saved your configuration file, you are ready to create the iWorkflow VM,
  6. Run the configuration file using an open source tool such as xm.
    xm create /etc/xen/<config_file_name>
    The console should indicate a successful start up by displaying something similar to this: Started domain <config_file_name>(id=444).
  7. Allow some time for the boot-up process; then, you should be able to connect to the iWorkflow console using a command similar to the following:
    # xm console <config_file_name>

Accessing the iWorkflow VE management user interface

If your network has DHCP, an IP address is automatically assigned to iWorkflow™VE during deployment. You can use this address to access the iWorkflowVE user interface or tmsh command-line utility.

If no IP address was assigned, you can assign one by using the iWorkflowConfiguration utility.

  1. At the password prompt, type default.
  2. Type config and press Enter.
    The F5 Management Port Setup screen opens.
  3. Click OK.
  4. If you want DHCP to automatically assign an address for the management port, select Yes. Otherwise, select No and follow the instructions for manually assigning an IP address and netmask for the management port.

You can use a hypervisor generic statement, such as tmsh list sys management-ip to confirm that the management IP address has been properly assigned.

You can now log into the iWorkflow VE user interface, and license and provision iWorkflow VE.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)