GIG Cloud has just received another update and it comes packed with a number of new and exciting features. What's special about this update is that it allows for more flexibility in accessing resources and getting data about them. In this post, we will go through a brief description of each of the following features:

  • Anti-affinity
  • API endpoints for configuring Traefik proxy on cloudspaces
  • Access control to the resources based on organization membership
  • Extend access to the billing API for the admins of Accounts, Cloudspaces and VMs
  • API call for retrieving maximum G8 capacity
  • Add API endpoint to retrieve consumption information about specific resources over time
  • Allow creating an account owned by an organization instead of a user

Anti-affinity

With anti-affinity you can add more robustness to your applications and VMs. Anti-affinity allows you to specify labels to your Virtual Machines; these labels are used to figure out where these VMs get deployed. Anti-affinity ensures that no 2 VMs with the same label end up on the same physical node. That being said, in the very unlikely scenario of a cloud failure, rest assured that one of the two machines will still be up and running. For more details on how to use this feature, please see this tutorial

Example:

Consider the case where you need 3 Virtual Machines as follows:

VM1 has labels application server & db server
VM2 has labels db server & cache server
VM3 has labels cache server

Using these labels VM1 & VM3 might be deployed on the same physical node, while VM2 will never share the same physical node with either VM1 or VM3 since it shares a label with both.

API endpoints for configuring Traefik proxy on cloudspaces

Now you can add and remove proxy configurations to your cloudspaces via the new addProxy and removeProxy API calls. This allows you to use a number of features offered by Traefik in order to handle traffic within your cloudspaces. In this tutorial we provide a more detailed description of this feature as well as some examples on how to use it.

Access control to the resources based on organization membership

With this feature, you can define organizations (groups) which users can be granted membership to. You can then add access control for a group (instead of a specific user) to Accounts, Cloudspaces or Virtual Machines. Then you can simply add users to that group which will allow them to share the same access level to these resources. This is made possible by the new API calls addGroup and deleteGroup

Example

Consider the case where you have 10 users that work in 2 different teams. Team 1 requires access to cloudspace_1, while team 2 requires access to cloudspace_2. However, they all need to have access to cloudspace_3. In this case you can create 3 groups, team 1, team 2 and team common. After that, you grant team 1 group access to cloudspace_1 and do the same for team 2 and team common on both cloudspace_2 and cloudspace_3

Now instead of adding group access for your individual users on 3 different cloudspaces, you can simply make them members of their corresponding groups. This also allows you to change access levels for a huge number of users by simply changing their group access in which they belong.

Extend access to the billing API for the admins of Accounts, Cloudspaces and VMs

It's now possible for users who are not in billing group to calculate billing information about the resources which they have admin access to.

API call for retrieving maximum G8 capacity

Starting from this release, we provide an API call to calculate the maximum capacity of a G8 based on it's current situation. This serves as an actual measurement not a theoretical one.

Add API endpoint to retrieve consumption information about specific resources over time

Now you can retrieve billing information about 1 specific resource instead of the whole environment. In addition to that, the billing API is now extended to provide the ability to retrieve consumption information in time-series format over a specific period of time. This is done by extending the current billing API to include a new API call /billing/calculateTimeseries as well as improving the API call billing/calculate to query information about a specific resource.

Allow creating an account owned by an organization instead of a user

Now you can create accounts that do not belong to a specific user, but instead belong to a specific group. This allows you to give multiple users access to an account in the same create API call.

Categories:

Tags:

No responses yet

    Leave a Reply