OVAs

You can enable users to build and boot virtual servers from OVA images. To enable the usage of OVA, you mount a source location to which OVA is uploaded on a Control Panel server with a destination location where OVA is stored on a backup server

Mount OVA Locations

The can mount OVA locations in the on_app.yml file:

  • Source Path on Control Panel Server (ova_path) - specifies the location where OVAs are downloaded/uploaded on the Control Panel server. By default, the location is /data. You can change it to any other suitable location. Make sure that this location is mounted to the specified destination location.
  • Destination Path on Backup Server (ova_path) - specifies the location where OVAs are stored on the backup server. By default, the location is /data. You can change it to any other suitable location with the onappowner and read/write access. Make sure that this location is shared with the specified source location.

CloudBoot compute resources mount the /data location automatically at boot to the /onapp/tools/recovery on a backup server. For more information on using OVAs on CloudBoot backup servers, refer to the Administration Guide

Enable Permissions in Control Panel UI

Make sure to enable the following permissions for your Admin and other roles in the Control Panel user interface:

  • Any action on OVAs - the user can take any action on OVAs

  • Create a new OVA - the user can create a new OVA file

  • Destroy any OVA - the user can delete any OVA (own, user, and public)

  • Destroy own OVA - the user can delete only own OVA

  • Destroy user OVA - the user can delete OVAs created by any user but not public OVAs

  • Make any OVA public - the user can make public any OVA available to all users

  • Make own OVA public - the user can make public only own OVAs

  • Create and manage OVAs - the user can create and edit/delete/view OVAs

  • Manage public OVAs - the user can manage public OVAs

  • Create and manage user OVAs - the user can view/create/edit/delete OVAs created by any user

  • See all OVAs - the user can view all OVAs in the cloud

  • See own OVAs - the user can only view OVAs created by themselves

  • Read all public OVAs - the user can view all public OVAs

  • See user OVAs - the user can view OVAs created by any user in the cloud

  • Unlock any OVA - the user can unlock any OVA that is currently being converted

  • Update any OVA - the user can edit any OVA in the cloud

  • Update own OVA - the user can edit only own OVA

  • Update user OVA - the user can edit OVAs created by any user in the cloud


Use OVA on CloudBoot

You can enable OVA on Static and CloudBoot resources. To use OVA on a CloudBoot backup server, some additional steps are required. Follow the next procedure to enable OVA for CloudBoot backup servers: 

  1. Connect to the Control Panel server via SSH. 
  2. Edit the /etc/exports file on the line  /data X.X.X.X/YY(ro,no_root_squash, where X.X.X.X/YY is  your network/subnet. Change the permissions from ro to rw and save the file.
  3. Restart the NFS service as follows:

    /etc/init.d/nfs restart

    It is not recommended to restart the NFS service at the same time when files are in use from the NFS share.

  4. Share the /data directory as described in the Mount OVA Locations section.
  5. Go to Control Panel > Settings > Compute Resources Label of the required CloudBoot compute resource.
  6. Click Actions > Edit next to the CloudBoot backup server.

  7. Add the following into the Custom Config box:

    cp /etc/lvm/lvm.conf /etc/lvm/lvm.conf.orig
    sed -i 's/^[[:space:]]*filter = .*$/filter = \[ "r\|\/dev\/nbd\|" \]/g' /etc/lvm/lvm.conf
  8. Click Save.
  9. Reboot your CloudBoot backup server.

    You can also execute the custom config command directly on a backup server to apply it without the reboot.

On this page: 


See also: