OpenStack VPS And Cloud For WHMCS
Line 1: | Line 1: | ||
− | |||
− | |||
<meta name="keywords" content="openstack vps for whmcs, openstack vps configuration, whmcs openstack vps management, whmcs openstack vps installation, whmcs openstack vps common problems, about whmcs openstack vps, whmcs openstack vps documentation, whmcs openstack vps faq, whmcs openstack vps help, whmcs openstack vps guide, whmcs openstack vps wiki, whmcs openstack vps tutorial, whmcs openstack vps tips, whmcs openstack vps wiki"></meta> | <meta name="keywords" content="openstack vps for whmcs, openstack vps configuration, whmcs openstack vps management, whmcs openstack vps installation, whmcs openstack vps common problems, about whmcs openstack vps, whmcs openstack vps documentation, whmcs openstack vps faq, whmcs openstack vps help, whmcs openstack vps guide, whmcs openstack vps wiki, whmcs openstack vps tutorial, whmcs openstack vps tips, whmcs openstack vps wiki"></meta> | ||
<meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The OpenStack VPS For WHMCS Module."></meta> | <meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The OpenStack VPS For WHMCS Module."></meta> | ||
Line 20: | Line 18: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 30px;"|✔ Change Password - Xen Virtualization Only | |style="padding: 0px 0px 0px 30px;"|✔ Change Password - Xen Virtualization Only | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Rescue/Unrescue Server | ||
|} | |} | ||
{| | {| | ||
Line 41: | Line 42: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 30px;"|✔ Enable Backups Routing | |style="padding: 0px 0px 0px 30px;"|✔ Enable Backups Routing | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Execute Custom Scripts On Boot | ||
|} | |} | ||
{| | {| | ||
Line 57: | Line 61: | ||
{| | {| | ||
|style="padding: 0px 0px 0px 30px;"|✔ Reset Network | |style="padding: 0px 0px 0px 30px;"|✔ Reset Network | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Rescue/Unrescue Server | ||
|} | |} | ||
{| | {| | ||
Line 94: | Line 101: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 0px 30px;"|✔ VCPUs |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Region | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 10px 30px;"|✔ Custom Script Files | ||
|} | |} | ||
*'''Required Components:''' | *'''Required Components:''' | ||
Line 117: | Line 130: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With <u>[ | + | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With <u>[https://www.modulesgarden.com/products/whmcs/advanced-billing Advanced Billing For WHMCS]</u> - Server Resource Usage Billing |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With <u>[https://www | + | |style="padding: 0px 0px 0px 30px;"|✔ Integrated With <u>[https://www.modulesgarden.com/products/whmcs/server-allocator Server Allocator For WHMCS]</u> - Automatic Assignment Of Specified Servers To Products |
|} | |} | ||
{| | {| | ||
Line 126: | Line 139: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports Cloud-Init Scripts |
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 0px 30px;"|✔ Supports PHP 5. | + | |style="padding: 0px 0px 0px 30px;"|✔ Supports OpenStack Ocata and Earlier |
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 0px 30px;"|✔ Supports PHP 5.4 Up To PHP 7 | ||
|} | |} | ||
{| | {| | ||
Line 151: | Line 167: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 10px 15px;"|'''2. In the downloaded file you will find two packages that support different PHP versions.'''<br/>As presented on the screen below, the first one is dedicated to PHP 7, while the second one is aimed at PHP 5. | + | |style="padding: 0px 0px 10px 15px;"|'''2. In the downloaded file you will find two packages that support different PHP versions.'''<br/>As presented on the screen below, the first one is dedicated to PHP 7, while the second one is aimed at PHP 5.4 up to PHP 5.6.<br/>It does not apply to open source versions.<br/> |
'' '''Note''': You can check current PHP version in your WHMCS. To do so proceed to ''' 'Utilities' → 'System' → 'PHP Info'.''' | '' '''Note''': You can check current PHP version in your WHMCS. To do so proceed to ''' 'Utilities' → 'System' → 'PHP Info'.''' | ||
|} | |} | ||
Line 194: | Line 210: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 15px 15px;"|'''8. Next, enter your server name, IP address/hostname, username, password and admin tenant ID.'''<br /> | + | |style="padding: 0px 0px 15px 15px;"|'''8. Next, enter your server name, IP address/hostname (which may required API version at the end of the address), username, password and admin tenant ID.'''<br /> |
− | Choose '' 'OpenStackVPS' '' from a dropdown menu and press '' 'Save Changes' ''.''' | + | Choose '' 'OpenStackVPS' '' from a dropdown menu and press '' 'Save Changes' ''.'''<br /> |
+ | ''Note: To find your ''' 'Tenant ID' ''' log in to your OpenStack panel and go to the 'Indentity' → 'Projects' menu. ''<br /> | ||
+ | ''There identify the row which corresponds to your project. The 'Tenant ID' is located in the 'Project ID' column for the identified project.'' | ||
|} | |} | ||
{| | {| | ||
Line 251: | Line 269: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|'''16. Now, go to the '' 'Module Settings' '' section, choose both '' 'OpenStackVPS' '' and your previously created server group from dropdown menus.'''<br /> | |style="padding: 0px 0px 15px 15px;"|'''16. Now, go to the '' 'Module Settings' '' section, choose both '' 'OpenStackVPS' '' and your previously created server group from dropdown menus.'''<br /> | ||
− | + | Module should automatically save and reload settings. If not, click on '' 'Save Changes' '' manually.''' | |
|} | |} | ||
{| | {| | ||
Line 329: | Line 347: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px | + | |style="padding: 0px 0px 30px 25px;"|[[File:OSV20.png]] |
|} | |} | ||
+ | ==Custom Config Scripts== | ||
{| | {| | ||
− | |style="padding: 0px | + | |style="padding: 10px 0px 15px 15px;"|'''24. In this area, you can write a custom script using [https://raymii.org/s/tutorials/Automating_Openstack_with_Cloud_init_run_a_script_on_VMs_first_boot.html Cloud-Init] to be executed on newly created VMs.'''<br /> |
+ | This way you can automate your work instead of making all kinds of specific images for specific tasks manually. <br /><br /> | ||
+ | '''Important notes:''' | ||
+ | *Scripts can be written in standards like '''Bash''' or '''[http://www.yaml.org/about.html YAML]'''. | ||
+ | *Initial scripts have to be supported by VPS operating system to be executed properly. | ||
+ | *Scripts should be used only by advanced users. The incorrect use of the scripts may damage your system! | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV44.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|On the example below, we will show an examplary script responsible for setting the password to '' 'newpass01' '' for the Ubuntu root user.<br /> | ||
+ | You can achieve it by writing: | ||
+ | chpasswd: | ||
+ | list: | | ||
+ | ubuntu:newpass01 | ||
+ | expire:False | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV45.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 15px 15px;"|You can configure scripts in the same format, but for clients' individual choice when ordering the product.<br /> | ||
+ | All you need to do is add a new configurable option and assign it to the OpenStack VPS product.<br /> | ||
+ | ''Note: these scripts are executed regardless of the script specified in the module settings.''<br /> | ||
+ | The easiest way is through edition of the existing 'Configurable options for OpenStack VPS' group, and adding a new configurable option there.<br /> | ||
+ | For example, if you want to offer pre-installed PHP version depending on the client's choice, you can add a new option named '''script_PHP|PHP version''' and then define multiple options, like on the screenshot below: | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV46.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|Afterwards, your clients can choose during the ordering process: | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV47.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 15px;"| | ||
+ | Using this method, you can perform assorted actions on newly created machines, e.g.: modifying files, preinstalling & preconfiguring software, executing any statements that would normally be executed via terminal.<br /><br /> | ||
+ | The general rule is that configurable option names should begin with '''script_prefix''' to be recognized as containing a custom script.<br /> | ||
+ | Then, choices under the option have their own names which are matched with a name of existing file with corresponding script under the | ||
+ | '''yourWHMCS/modules/servers/OpenStackVPS/scripts''' path.<br /> | ||
+ | Note that files with scripts have to have '''exactly''' extension corresponding to the given entries in the configurable options.<br /><br /> | ||
+ | In the example above, there are two options: '''php5.yml''' and '''php7.yml''', therefore it makes the module read corresponding files:<br /> | ||
+ | *modules/servers/OpenStackVPS/scripts/php5.yml | ||
+ | or | ||
+ | *modules/servers/OpenStackVPS/scripts/php7.yml | ||
+ | You can add many scripts in this exact way. | ||
|} | |} | ||
Line 382: | Line 449: | ||
{| | {| | ||
|style="padding: 0px 0px 30px 25px;"|[[File:OSV28.png]] | |style="padding: 0px 0px 30px 25px;"|[[File:OSV28.png]] | ||
+ | |} | ||
+ | ===Rescue Mode=== | ||
+ | {| | ||
+ | |style="padding: 10px 0px 15px 15px;"|The rescue mode provides a mechanism for VM access even in case the VM's image renders the instance inaccessible - e.g. if instance's filesystem becomes corrupted. <br /> | ||
+ | The rescue VM will be launched to permit the user to fix their VM. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV48.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"| | ||
+ | Before you continue please note that the rescue VM will be set up with the same network configuration as the real VM. <br /> | ||
+ | Moreover, a new root password will be generated and the VM status will change to 'RESCUE'.<br /> | ||
+ | The new VM will also have a rescue image as the primary filesystem and the secondary filesystem would be the original VM's primary filesystem.'' <br /> | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 25px;"|[[File:OSV49.png]] | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 20px 15px;"|When you want to disable the rescue mode, click the 'Unrescue' buton. TheVM status will then also return to 'ACTIVE'. | ||
+ | |} | ||
+ | {| | ||
+ | |style="padding: 0px 0px 30px 25px;"|[[File:OSV50.png]] | ||
|} | |} | ||
Line 414: | Line 504: | ||
{| | {| | ||
|style="padding: 0px 0px 15px 15px;"|To restore VPS from backup, simply press '' 'Restore' '' button next to it.<br /> | |style="padding: 0px 0px 15px 15px;"|To restore VPS from backup, simply press '' 'Restore' '' button next to it.<br /> | ||
− | As you may notice on the following screen, presented earlier '' ' | + | As you may notice on the following screen, presented earlier '' 'First Backup' '' backup was replaced with '' 'New Backup' ''.<br /> |
It was caused by backup routing feature which was triggered by reaching backups file limit. | It was caused by backup routing feature which was triggered by reaching backups file limit. | ||
|} | |} | ||
Line 485: | Line 575: | ||
{| | {| | ||
|style="padding: 10px 0px 15px 15px;"|When you combine OpenStack VPS For WHMCS with [http://www.docs.modulesgarden.com/Advanced_Billing_For_WHMCS Advanced Billing For WHMCS], you will be able to set up additional billing options.<br /> | |style="padding: 10px 0px 15px 15px;"|When you combine OpenStack VPS For WHMCS with [http://www.docs.modulesgarden.com/Advanced_Billing_For_WHMCS Advanced Billing For WHMCS], you will be able to set up additional billing options.<br /> | ||
− | Module allows you to charge your customers based on the server resources used by them. | + | Module allows you to charge your customers based on the server resources used by them.<br /> |
+ | ''Note: Advanced Billing currently supports only API prior V3 (OpenStack Ocata). A new compatibility will be added soon.'' | ||
|} | |} | ||
{| | {| | ||
Line 491: | Line 582: | ||
|} | |} | ||
{| | {| | ||
− | |style="padding: 0px 0px 20px 15px;"|With Advanced Billing module, you can also display your customers the current server resource usage | + | |style="padding: 0px 0px 20px 15px;"|With Advanced Billing module, you can also display your customers the current server resource usage, their cost, usage history and charts. |
|} | |} | ||
{| | {| |
Revision as of 15:16, 26 July 2017
Contents |
About OpenStack VPS For WHMCS
OpenStack VPS For WHMCS is a module which allows you to automatically provision virtual servers to your customers. The great advantage of this module is the fact that customers can order and manage virtual servers, backups and many more in your own WHMCS client area. |
- Admin Area Features:
✔ Create/Suspend/Unsuspend/Terminate Server |
✔ Change Package - Supports Configurable Options |
✔ Change Password - Xen Virtualization Only |
✔ Rescue/Unrescue Server |
✔ View Server Status And Details |
✔ View Interface Details |
✔ View List Of Scheduled Tasks |
✔ Configure Client Area Features Per Product |
✔ Define Backup Quantity Limit |
✔ Set Security Groups |
✔ Enable Backups Routing |
✔ Execute Custom Scripts On Boot |
✔ Run Extended Connection Test |
- Client Area Features:
✔ View Server Status And Details |
✔ Start/Stop/Pause/Unpause/Resume/Rebuild Server |
✔ Reboot Server - Soft/Hard |
✔ Reset Network |
✔ Rescue/Unrescue Server |
✔ Change Password For Xen Virtualization |
✔ Access noVNC VNC, RDP, SPICE Or Serial Console |
✔ Create/Restore/Delete Backups |
✔ Download Public & Private SSH Keys |
✔ View List Of Scheduled Tasks |
- Configurable Options:
✔ Flavor |
✔ VM Image |
✔ IP Addresses |
✔ Backups Files Limit |
✔ Disk |
✔ RAM |
✔ VCPUs |
✔ Region |
✔ Custom Script Files |
- Required Components:
✔ Keystone |
✔ Glance |
✔ Nova |
✔ Neutron |
✔ Ceilometer (Required For Advanced Billing For WHMCS) |
- General Info:
✔ Automated Generation Of SSH Keys - Public SSH Key Is Injected To VM Automatically |
✔ Integrated With Advanced Billing For WHMCS - Server Resource Usage Billing |
✔ Integrated With Server Allocator For WHMCS - Automatic Assignment Of Specified Servers To Products |
✔ Multi-Language Support |
✔ Supports Cloud-Init Scripts |
✔ Supports OpenStack Ocata and Earlier |
✔ Supports PHP 5.4 Up To PHP 7 |
✔ Supports WHMCS Templates Five and Six |
✔ Supports WHMCS V6 and V7 |
Installation and Configuration
This tutorial will show you how to successfully install and configure OpenStack VPS For WHMCS. We will guide you step by step through the whole installation and configuration process. |
Installation
1. Log in to your client area and download the module. |
2. In the downloaded file you will find two packages that support different PHP versions. As presented on the screen below, the first one is dedicated to PHP 7, while the second one is aimed at PHP 5.4 up to PHP 5.6. It does not apply to open source versions. Note: You can check current PHP version in your WHMCS. To do so proceed to 'Utilities' → 'System' → 'PHP Info'. |
3. Extract the downloaded file and choose the one with the right PHP version. Upload and extract the PHP file into the main WHMCS directory. The content of PHP version files should look like this. |
4. When you install OpenStack VPS For WHMCS for the first time you have to rename 'license_RENAME.php' file. File is located in 'modules/servers/OpenStackVPS/license_RENAME.php' . Rename it from 'license_RENAME.php' to 'license.php' . |
5. In order to configure your license key, you have to edit a previously renamed 'license.php' file. Enter your license key between quotation marks as presented on the following screen. |
6. Next step is setting up a cron job (each 5 minutes suggested). Use cron job below but switch 'your_whmcs' with your root WHMCS path. php -q /your_whmcs/modules/servers/OpenStackVPS/cron/cron.php |
Configuration of Server
7. Now, we will show you how to configure a new product. Go to the 'Setup' → 'Products/Services' → 'Servers' and press 'Add New Server' . |
8. Next, enter your server name, IP address/hostname (which may required API version at the end of the address), username, password and admin tenant ID. Choose 'OpenStackVPS' from a dropdown menu and press 'Save Changes' . |
9. After you configure your server correctly, you can check connection with OpenStack server. Simply edit previously created server and press 'Test Connection' as shown on the screen below. |
10. It is time to create a server group. To do so, click on 'Create Server Group' . |
11. Enter name, click on your previously created server, press 'Add' and afterwards 'Save Changes' . |
Configuration of Product
12. In order to create and configure a product, go to the 'Setup' → 'Products/Services' → 'Products/Services' . Click on 'Create a New Group' . |
13. Enter product group name and press 'Save Changes' . |
14. When you have a product group, you can create your product. To create a product click on 'Create a New Product' . |
15. Afterwards, choose your product group and type from dropdown menus, enter your product name and press 'Continue'. 'Product Type' should be set to 'Hosting Account'. |
16. Now, go to the 'Module Settings' section, choose both 'OpenStackVPS' and your previously created server group from dropdown menus. Module should automatically save and reload settings. If not, click on 'Save Changes' manually. |
17. Start from selecting 'Default Tenant' . 'Check access' will return 'OK' if you set up permissions correctly. |
18. Afterwards, set up a network. Choose 'Fixed Network' , 'Floating Network' and 'Default Number Of IP Addresses' . You can set up network in two ways. You can find more information about the configuration here. |
19. At this step you can set up backups. Mark 'Backups Routing' checkbox if you want to replace oldest backup with newest one when backups file limit is reached. |
20. Mark security group from 'Use Security Groups' and select 'Console Type' . If you wish to use SSH keys, leave 'Inject SSH Key' marked (virtualization has to support 'Inject File' feature). |
21. Finish through selecting features available at the client area. Mark checkbox next to feature in order to enable it. Press 'Save Changes' when you are done. |
VPS With Predefined Resources
Our module allows you to offer OpenStack VPS to your clients in two ways, with predefined resources and configurable resources. In this section we will show you configuration of VPS with predefined resources. |
22. Select 'Default Flavor' and 'Default VM Image' . 'Default Flavour' defined resources assigned to VM while 'Default VM Image' allows you to choose VM image used to create new VM. |
Congratulations! You have just finished the installation and configuration of the module with predefined resources. |
VPS With Configurable Resources
23. Preparing VPS with configurable options consists of pressing 'Generate default' as shown on the following screen. It will prepare default configurable options which can be afterwards easily edited as described in this article.
Note: The second and the third options causes a new flavor being made on your server each time a new order is made. |
Custom Config Scripts
24. In this area, you can write a custom script using Cloud-Init to be executed on newly created VMs. This way you can automate your work instead of making all kinds of specific images for specific tasks manually.
|
On the example below, we will show an examplary script responsible for setting the password to 'newpass01' for the Ubuntu root user. You can achieve it by writing: chpasswd: list: | ubuntu:newpass01 expire:False |
You can configure scripts in the same format, but for clients' individual choice when ordering the product. All you need to do is add a new configurable option and assign it to the OpenStack VPS product. |
Afterwards, your clients can choose during the ordering process: |
Using this method, you can perform assorted actions on newly created machines, e.g.: modifying files, preinstalling & preconfiguring software, executing any statements that would normally be executed via terminal.
or
You can add many scripts in this exact way. |
Management
OpenStack VPS For WHMCS allows your customers to manage their OpenStack VPS via client area in your WHMCS system. You can monitor and manage each product from your WHMCS admin area. |
Ordering
Owing to configurable options, you are able to offer product which your clients can tailor according to their needs. Additionally, you are able to set up pricing for each configurable option, which make your offer even more competitive. |
Client Area
Client area interface of OpenStack VPS should look like the one on the screen below. As you can see, control panel contains useful options needed for managing VPS. Module allows your customers to easily start/stop, pause/unpause, resume, soft reboot, hard reboot and reset network of their servers through pressing specified button. |
Rebuild
Rebuild feature allows your clients to change server image. Press 'Rebuild' button as shown on the following screen in order to move to the rebuild page. |
To reinstall your server, choose an image and confirm through clicking on 'Rebuild' button. |
Rescue Mode
The rescue mode provides a mechanism for VM access even in case the VM's image renders the instance inaccessible - e.g. if instance's filesystem becomes corrupted. The rescue VM will be launched to permit the user to fix their VM. |
Before you continue please note that the rescue VM will be set up with the same network configuration as the real VM. |
When you want to disable the rescue mode, click the 'Unrescue' buton. TheVM status will then also return to 'ACTIVE'. |
noVNC Console
One of the most interesting functionality is a noVNC console where your clients can remotely manage server. To access it, simply press on the 'Console' button. |
noVNC is a browser based VNC client. It was implemented using HTML5 Canvas and WebSockets. |
Backups
Your customers can also create a backup of VPS. To do so, press 'Backups' button. |
Now, choose backup name and press 'Backup Now' button. |
To restore VPS from backup, simply press 'Restore' button next to it. As you may notice on the following screen, presented earlier 'First Backup' backup was replaced with 'New Backup' . |
SSH Keys
Due to limitation in WHMCS product create process, OpenStack VPS For WHMCS generates SSH key pair automatically. Public SSH key is automatically injected into VM while private key can be downloaded from the client area. |
Public SSH key in other hand, can be downloaded as many times as your client will need it. Press 'Download Public Key' as shown on the following screen to save it on your disk. |
Network Configuration Cases
OpenStack VPS For WHMCS allows you to set up two types of network. First one is a network without floating IP address. |
Second type of network is a network with floating IP address. Select 'Shared Network' as 'Fixed Network' and 'Public' as 'Floating Network' . |
Configurable Options
In case that standard configuration is not fitting your needs, you can adjust it through configurable options. To do so, go to 'Setup' → 'Products/Services' → 'Configurable Option' and press edit button next to configurable option used by your product. |
Here you can view the products that this configurable option group is assigned to. Now we will show you how to edit options. Let's say that you want to add an option to order VPS with 8GB (8192 MB) RAM. |
You will see a popup window, so make sure that your browser will not block it. To add new option, enter it in a textbox under all other options. If you want to replace it with option you currently have, simply edit its textbox. |
Management of Billing
When you combine OpenStack VPS For WHMCS with Advanced Billing For WHMCS, you will be able to set up additional billing options. Module allows you to charge your customers based on the server resources used by them. |
With Advanced Billing module, you can also display your customers the current server resource usage, their cost, usage history and charts. |
Tips
1. Due to some requests may take time to be completed, we implemented 'Scheduled Tasks' . Tasks visible at 'Scheduled Tasks' are subsequently performed by cron job. |
2. Important: module has to use admin endpoints instead of public endpoints. In properly configured OpenStack server, wget from WHMCS server should be able to get any data from any admin endpoint. wget openstack:9292 --2014-03-31 09:35:24-- http://openstack:9292/ Resolving openstack(openstack)... 192.168.1.222 Connecting to openstack(openstack)|192.168.1.222|:9292... connected. HTTP request sent, awaiting response... 300 Multiple Choices Length: 520 [application/json] Saving to: `index.html' 100%[==========================================================>] 520 --.-K/s in 0s 2014-03-31 09:35:24 (118 MB/s) - `index.html' saved [520/520]
wget openstack:8777 --2014-03-31 09:41:05-- http://openstack:8777/ Resolving openstack(openstack)... 192.168.1.222 Connecting to openstack(openstack)|192.168.1.222|:8777... connected. HTTP request sent, awaiting response... 401 Unauthorized Authorization failed. |
3. A primary IP address is always assigned by OpenStack server when a VM is created Therefore, if you decide to order 2 IP addresses, then 3 addresses will be assigned. The primary one and the two additionally ordered. If you wish only one IP address to be assigned to a single product, please set the filed 'Default Number Of IP Addresses' to '0' or leave it empty in the product's 'Module Settings'. |
Common Problems
1. When you have problems with connection, check whether your SELinux or firewall does not block ports. |
2. 'Connection Error: No route to host' error. Reason: WHMCS server can not resolve OpenStack endpoint hostnames. |
Afterwards, check each URL from 'adminurl' column using 'ping' command at your WHMCS server. All URLs which are not reachable have to be added to 'hosts' file on a server with your WHMCS. |
3. In case of persisting connection problems, please make sure you have the following ports open:
8774, 35357, 9292, 5000, 8777, 9696, 8776 |