abiquo / abiquo-cookbook

Chef cookbook for the Abiquo platform

Abiquo Cloud Platform

Abiquo represents the next generation of Cloud management solutions. Designed to meet strategic objectives, rather than as a temporary tactical fix, it is built to realize our vision of virtualized infrastructure management. Based on open standards, Abiquo allows organizations of all sizes to dramatically improve business agility, mitigate risk, and reduce costs.

Resources

• Abiquo: The official site with all resources.
• Community: Check out the User Manual, the Administrator guide and all documentation.
• Build Abiquo: How to build the platform from scratch.
• API reference: Integrate with Abiquo with the REST API.
• Issue tracking: Report and keep track of any issue in the platform.

License

See licensing details in the legal folder.

abiquo-cookbook's Issues

Drop iptables in favor of firewalld

Since 4.5, support for Centos 6 has been dropped and since firewalld is the standard FW in Centos 7, we should try and use it instead of iptables.

Add the ability to have more than 1 vhost

For multi site setups this will be useful.

Upgrade recipe does not upgrade non-abiquo packages

In the case you have a separare DB server, running the upgrade recipe won't upgrade MariaDB, Redis or RabbitMQ packages if needed.

Standalone server does not download cert

In the scenario where UI is installed separately from the server, the server won't download the SSL cert from Apache since it does not include the certificate recipe.

Watchtower liquibase has to be run on installation

Seems that the watchtower schema is just the initial version. If liquibase for wt does not run you can't remove VMs and stuff...

Allow to configure OAuth apps

Useful for example for M and other integrations.

Cassandra does not start in CentOS 7

For some reason, the Cassandra service fails to start in CentOS 7. When executed manually, apparently it starts properly. The monitoring kitchen suite fail for this reason on C7.

/cc @chirauki

yum clean metadata seems to be useless

Thoughts:

• yum update step is prechecked in cookbook compile time (no changes found)
• yum clean metadata is done after that check (very useless)

This causes no package update

Fix haproxy service order

It is actually enabling the service (or restarting) before the config has been written.

WS listen address default does not make sense

Since it is now running in RS and accessed from the portal, it should listen in 0.0.0.0 instead of 127.0.0.1.

Improve Websockify config

With recent changes to the RPM build we should provide a way to better handle the configuration of the websockify daemon.

Watchtower DB update is not run on upgrade

Same for kinton liquibase

  * execute[liquibase-update] action nothing (skipped due to action :nothing)
  * execute[watchtower-liquibase-update] action nothing (skipped due to action :nothing)

Certificate downloads are wrongly check for existence

https://github.com/abiquo/abiquo-cookbook/blob/master/providers/download_cert.rb#L43L47

The check is based in the existence of a file with the specified name. If the remote endpoint changed the certificate at any time, the new cert won't be downloaded again. We should check this against cert fingerprint.