HostBill installation is fully automated and takes just seconds, more info at Installation
This module support two ways of settings up ssh access with password authentication, trough root password injection and cloud-init scripts.
You can read more on how to enable password injection for different hypervisors here: http://docs.openstack.org/admin-guide/compute-admin-password-injection.html
To use cloud-init script, you will need to enter it in your product configuration, under "Misc" tab.
It allows you to use "$password" variable that will be replaced with actual root password when new VM is created.
It is possible to use smarty templates for user data script, you can access $service
, $client
, $forms
and $password
variables to customise your script.
Please refer to this list to find out proper variable names - Available Email Variables
You can access form components values trough $forms
variable, this guide illustrates how to find proper variable names - Forms: Accessing Forms elements in email templates
#cloud-config hostname: {$service.domain} users: - name: {$forms.username.value} gecos: {$client.firstname} {$client.lastname} passwd: {$password|md5} sudo: ['ALL=(ALL) NOPASSWD:ALL'] groups: sudo shell: /bin/bash runcmd: - {$forms.recipe.variable_id} - restart ssh |
Problem:
Connection timed out
Solution:
Make sure that hostbill server is able to connect to your openstack server.
After authentication openstack returns with list of available api endpoints, hostbill will test those endpoints using admin api interface (adminURL). make sure that url provided in error message is accessible from your server,
Problem:
Admin API interface is not available for some services (eg. compute, network)
Solution:
Rename includes/modules/Hosting/openstack/endpoints.php.example to endpoints.php, you can edit that file to select which url type will be used for each service.
Problem:
Test connection returns:
500 Internal Server Error. Test did not completed, check your error logs for more information.
Solution:
There was an error while testing connection status, check Extras > System Logs > Error logs for more information.