Versions Compared

Version Old Version 16 New Version 17
Changes made by

MS

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Replace ? for | and ??? for |-- on the tree command examples

...

We are going to describe this setup assuming the scenario described below. Note that you will need to adjust the rest of the commands in this document to suit your environment (mostly host names and IPs).

MachineHost nameIP Address
Abiquo Monolithic & Apache2 SSL front-end

api.example.com
theme1.example.com
theme2.example.com 

192.168.1.100
Datacenter2 Remote Servicesdc2rs.example.com192.168.1.150


Note
titleSetup disclaimer
  • Users must be able to reach api.example.com, theme1.example.com and theme2.example.com (i.e. DNS names must be resolvable)
  • Abiquo API and RS must be able to reach each other by DNS names

...

Code Block
# tree /var/www/html/ui/

/var/www/html/ui/
???|-- config
?|   ???|-- client-config.json
?|   ???|-- tutorials
...
???|-- theme
?|   ???|-- abicloudDefault
...

We need to create a configuration file and theme folder per subdomain. In the sample scenario the structure will look like:

Code Block
# tree /var/www/html/ui/
/var/www/html/ui
???|-- config
?|   ???|-- theme1.json
?|   ???|-- theme2.json
...
???|-- theme1
...
???|-- theme2
...

You can have different property configuration in each config json file, but it is very important that the config.endpoint property points to its related API subdomain URL:

...

Code Block
# tree /etc/httpd/conf.d/

/etc/httpd/conf.d
???|-- api.conf
???|-- theme1.conf
???|-- theme2.conf

First of all you need to change api.conf. This VirtualHost configuration file will group SSL access for all Abiquo Appliance Manager webapps and the API endpoint: (api.conf)

...