Once the installation is complete on all the nodes you need for the UForge AppCenter, you are now ready to configure all the UForge AppCenter services. This is done via the UForge Deployment Wizard that guides you through the final steps of the installation process.
The name of
LVM VolGroup Name must be unique. The default when installing UForge will have a format similar to
vg_uss_150910-lv_uss_150910. If your scanned instance has the same volume group name, or if you set up advanced partitioning with the same name, you will get an error when migrating.
Launching Deployment Wizard¶
To launch the UForge Deployment Wizard, use your browser and go to one of the nodes that have been installed:
http://<ip address of the node>:9998/deployments
Fill in the wizard, note that all the fields are mandatory.
Enter the Organization name. This is the name of the default Organization. The organization groups all the operating systems, formats and users for the platform.
Enter an email address. This is the email address of the root administrator of UForge. All administration email notifications are sent to this email address.
Set the root administrator’s password. The password must be at least eight characters long, including at least one uppercase character, one lowercase character, and at least one digit. The following special characters are allowed: hyphen (-) and underscore (_). No other special characters are allowed, including spaces.
Provide a username, email and password for an initial user account to be created. This user account will have administration access rights for the default Organization.
Provide the UForge activation key and credential information to be able to receive UForge updates. If you do not have this information, please contact your vendor.
Select the operating systems and formats you would like to install. When you select an OS, a default mirror location is indicated. This is used for synchronization of packages and distributions. You can either accept the default values or modify the value to synchronize with another mirror.
Set the internet connection. By default, UForge expects to have a direct connection to the internet. If you de-select this option, you will need to enter the proxy hostname and port.
Set the SMTP Server to use for sending email notification messages created by UForge. If you want to use a SMTP relay, then also indicate the relay hostname and port number.
Enter the Web Server IP address, external hostname and the database IP address.
The external hostname is used to construct two external URL endpoints. The first as the external URL endpoint of the user interface, and the other for REST API calls and command-line usage. The external hostname should normally be a fully qualified hostname. For example, if the external hostname is
uf.example.com, then the following URL endpoints are created:
These external URL endpoints can be changed after the initial configuration is complete, refer to Modifying the UForge Platform External URL Endpoints for more information.
In order to avoid potential errors due to length limits, it is recommended that the external host name of UForge be limited to 170 characters.
Select if OS and image storage should be local or remote. OS storage will be used for distributions, which image storage will include user data such as images, projects, mysoftware and other user data created with UForge.
- If you choose to use a remote storage, indicate the NFS server with mount point and you should enter the full path for the OS directory e.g.
- If you select remote storage for the image store, you have to make sure that the path
USER_DATAexists, with the correct permissions i.e. tomcat:tomcat. Refer to UForge Repository on Shared Storage, step 4, Check mount points, for more details.
Indicate the generation cluster compute node hostnames. You can add additional compute nodes by clicking the add button.
Once you have finished the configuration, click the
The deployment may take a few hours, depending on the number of operating systems you have chosen.
If the deployment starts but seems to hang (for example it remains in the
Startingmode in the progress bar, or never goes beyond
Initializing), there may be an error in the data entered into the wizard. In order to resume the deployment, log into the AppCenter server, and run the following command:
service oas-deploy restart. You can then re-load the deployment URL in your browser, correct the data which was wrong and click
Once the deployment is complete, click
As part of the deployment phase, the wizard logs all the steps of the configuration. These logs include the administration passwords and other sensitive data you have used to configure this platform. It is important that these logs do not remain on the machine once the deployment is finished. To do this:
$ cd /var/log/UShareSoft $ /bin/rm -rf oas-deploy
The following ports need to be configured for your UForge AppCenter.
- 20 and 21
- 22 for SSH
- 443 and 80
- 80 and 443
In addition, communication ports between UForge and the cloud platform to which you will publish the images have to be open and depend entirely on your cloud platform configuration, see Cloud Platform Default Ports for more information. All other ports not in this list should be blocked by the firewall to protect internal services from outside access.
Some cloud platforms will reject uploading machine images, if the HTTP request date is in the future of the target cloud platform. To ensure proper function of UForge, please edit ‘server’ directives in
/etc/ntp.conf if UForge servers cannot connect to NTP servers on the internet.
If you want to contact NTP servers on the internet, then port 123 (UDP) should be opened on your firewall.
If you have deployed UForge AppCenter and believe that ntp is not correctly setup, check if the log file
/var/log/UShareSoft/oas-deploy/logs/deployment/UForgeDeploy.pl/latestOASlog/<IP ADDRESS OF NODE>/NodeSetup.pl_4.log contains the error:
[OAS ERRR] Unable to configure ntpd service.
If this is the case, make sure that you configure ntp with an ntp server accessible from your environment (UForge uses pool.ntp.org by default). Assuming this ntp server has FQDN accessible.ntp.server, then run the command: