Compose Notes - Cloud naming and a password warning

Cloud Names

When people have a number of database deployments with Compose, it could be hard remembering which cloud platform they are on. We already have Amazon Web Services (AWS) and SoftLayer (SL) hosting available and there's always more cloud platforms we are looking to support in future.

As it previously stood, you had to go into each deployment and look at the overview to see on which cloud it resided on...

Overview

When you're trying to see where all your deployments are, you don't need to be clicking in on each one. So, we've put it up front on the main list of your deployments. Where it was just showing a region, now it shows the cloud platform and the region like this:

New deployment

This will also help distinguish between similarly named regions on different cloud platforms in future.

Passwords, a warning

The short version of this warning is, we strongly recommend that administration passwords within Compose databases only be changed through the Compose console for that database. Not doing so could result in time being spent repairing the deployment at some point in the future.

The long version of the warning is this. As part of Compose's orchestration and management of database deployments we use the administration password inside the cluster to perform administration tasks. As a cluster, that password needs to be synchronized with all the data bearing instances of the database and depending on the database, may be used for other tasks to manage or scale the database. We handle this synchronization in the Compose console. That means when you change the admin password, Compose takes care of updating it where it needs to be updated.

But, if you use the command line or API to force a password change on that administration user, we can't execute that synchronization process. This could mean, for example, that the password only changes on one node of the cluster and locks out the other nodes. It also means that the Compose management tools won't get updated and when they next have to reconfigure something they are unable to do so.

"Why don't you stop us from doing that?" you may ask. We don't modify the databases we deploy from their upstream versions so we don't add "management extensions" to the code that might do password capture. That does mean, though that we can't put up "guard rails" to block you from changing your admin password. We rely upon you to ensure you don't attempt to do so to keep your database running, only use the Compose console to change your admin password. This only applies to the admin password though; you have complete freedom to create, modify and delete all other users passwords.