A new version of Altai Private Cloud for Developers 1.1.1 is ready to use. In this release, we support reliable updates from any previous Altai version..
This release is recommended to use for everyone instead of 1.1.0. Update procedure from any previous release is safe and automated – just follow our upgrade guide.
Other important changes:
- guess root partition of virtual machine images for setting login credentials;
- add script for LDAP configuration after Altai installation;
- support instance live migration;
- fix VNC security problem that occurs for deleted instances;
- strong validation of Altai configuration parameters to determine installation/updating problems earlier;
- bugfixes in UI;
- correct adding records for NS servers on zone creation;
- purge info about deleted instances from database.
We are glad to announce a new version of Altai Private Cloud for Developers.
This update introduces out-of-the-box LDAP/AD support in Altai Cloud. It should help to manage cloud users and authorization in companies where LDAP or AD is used.
A new version of Altai Private Cloud for Developers 1.0.2 is ready to use. In this release, we reviewed and cleaned up third-party packages and made bugfixes, primarily to user interface.
This release is recommended to use for everyone instead of 1.0.1. Update procedure is safe and automated – just follow our upgrade guide.
A new version of Altai Private Cloud 1.0.1 is ready to use. This is bugfix release. It is recommended to use for everybody instead of 1.0.0. Read our upgrade guide to do this.
`nova-dns` package was developed to solve two tasks:
- map instance’s hostnames to ip addresses in DNS
- provide REST API to manage DNS
To solve first task service monitor message bus (RabbitMQ). For every started instance service add DNS record, for terminated – remove. DNS name is choose in form hostname.tenant_name.root_zone. If zone for tenant_name doesn’t exists yet, it is created and populated automatically.
To solve second task service start REST API server on specified ip/port. REST API supports authentication against keystone and utilize keystone’s RBAC.
As a DNS backend PowerDNS is used, but other backends (for example for Bind) can be added later.
Next we are going to add support for PTR zones and add ability to create personal zone for every started instance.
Now nova-billing has a Django-based web interface – horizon-billing (https://github.com/griddynamics/horizon-billing).
horizon-billing is packaged to a homonymous RPM (path for RHEL: http://yum.griddynamics.net/yum/diablo/, for CentOS: http://yum.griddynamics.net/yum/diablo-centos/).
To enable it in dashboard, install the horizon_billing package and turn it
on in /etc/openstack-dashboard/local/local_settings.py:
- add ‘horizon_billing’ to INSTALLED_APPS tuple;
- add ‘billing’ to ‘dashboards’ key in HORIZON_CONFIG.
After installation, a new “Billing” panel is added after “Project” and “Admin”.