Virtual Factory Configuration

Configuration file location

The Virtual Factory module is configured in a single file named config.xml that can be found in WEB-INF/classes/conf/config.xml file into the virtualfactory war.

Configuration file contents

• Hypervisors:
  • HyperV: HyperV specific configuration. Forget these values if you are not planning to use HyperV
    • user: HyperV user.
    • password: HyperV password.
    • wsmanPort: The port where the Hypervisor web service is listening.
    • localRepositoryPath: The local repository path.
    • destrinationRepositoryPath: Where the NFS is mounted to access to shared virtual images.
  • ESXi: ESXi specific configuration. Forget these values if you are not planning to use ESXi.
    • user: The ESXi user.
    • password: ESXi password.
    • sanDatastore: The target datastore where to load the virtual images to deploy.
    • VmfsDatastore: The target datastore where the images will be deployed.
    • igonrecert: If certificate must be ignored.
  • XenServer: XenServer specific configuration. Forget these values if you are not planning to use XenServer.
    • user: The XenServer user.
    • password: XenServer password.
    • abiquoRepository: The location of the Abiquo Repository containing image files.
• Rimp: WSman configuration files. Forget these values if you are not planning to use WSman-dependant hypervisors (KVM/XEN/VirtualBox).
  • user: WSMan user.
  • password: WSMan password.
  • timeout: Time in miliseconds to wait the connection.
  • port: The port where the WSMan web service is listening.
• Networking: Networking configuration values. Forget these values if you are not planning to use WSman-dependant hypervisors (KVM/XEN/VirtualBox).
  • bridgePrefix: The prefix used when creating the bridge with the NIC connected to service network.

Hypervisor credentials In the current release, Abiquo can only connect to the Hypervisors using this config file credentials. This meants that only one user and password are used to connect to all hypervisors of the same type. This is a known limitation that will be solved in future releases.

Important considerations

• All the "Hypervisor-native" specific configuration (ESXi, HyperV, XenServer) must match with the actual Hypervisor configuration.
• Take into account that the same configuration will work with the nodecollector and the vsm, so, the configuration of the chosen Hypervisor must be the same in all the projects.
• The WSMan configuration files should match with the /etc/openwsman/openwsman.conf file in the target Node machine. For instance, consider the following openwsman.conf (please note the 'port' and the 'basic_password_file' values):

and the auth.passwd says the following

(the auth.passwd is generated with the htpasswd program)

So, the configuration of this part of the file should be

Default configuration file contents