In order to use cloud-init on Hyper-V, create the hyperv-iso directory in the VM repository folder, which for the default platform will be:
After creating the folder, remember to set the owner to the "tomcat" user.
In private cloud, you must provide an NFS server, which shares the repository folder for each Abiquo datacenter using hypervisors, for storing the Apps library of VM templates (disk images). The Remote Services and hypervisors mount and access the shared folder using NFS or CIFS (SAMBA for Hyper-V).
When you configure the platform, enter the location of the NFS repository, which is the IP address and folder. The platform will automatically configure the NFS server as follows.
The firewall requirements are access to NFS on ports TCP/UDP 2049 and TCP/UDP 111 (RPC) for the following servers:
If anything goes wrong with the automatic configuration of the NFS repository, then the NFS repository and the platform may not function correctly. Of the remote services, the Appliance Manager adds VM templates to the repository and manages them, and the Business Process Manager converts VM templates to different disk formats. Hypervisors copy VM templates from the repository to deploy them.
Here are some more details about how the platform configures the NFS server:
Automatically configuring the abiquo.properties files on the Remote Services server (or the Monolithic server). For a separate NFS configuration, the abiquo.properties file should look as follows.
Automatically mounting the repository folder on the Remote Services and V2V Services servers. The install process should automatically configure the /etc/fstab with the values you enter for the NFS repository.