SafeScale v19.03.2

Bugfix:

Kong version is now forced to 1.0

SafeScale v19.03.1

Bugfix:

Cluster expand is now working properly

v19.03.0

Safescale v19.03.0 is out

!!!IMPORTANT NOTE!!!

This version breaks backward compability, due to important changes in metadata handling. Don't use the new binaries with old SafeScale environments.

Notables changes (for sure not in any significant order):

• Introduces the new revision system, using <YY>.<MM>.<PatchLevel> format.
• Binaries broker and brokerd are renamed safescale and safescaled
• Binary deploy has been merged in safescale and doesn't exist anymore; its functionalities are now available in safescale
• Not all cluster flavors are currently available: only BOH (Bunch Of Hosts) and SWARM are useable. The others flavors will be available again as fast as possible
• Important work has been done to separate provider support codes, separating "stack" (like openstack, aws, ...) and real "provider" (using a stack); we hope this will help to speed up new provider support and ease user contribution.
• Total overhaul of the metadata system, to allow backward compatibility (starting from this release...)
• Ubuntu 18.04 replace Ubuntu 16.04 as default Linux distribution
• Documentation has been fixed, completed, extended

New providers (in beta)

• "openstack": to use for example with in-premise openstack implementation. WARNING: this "provider" is in early stage and not yet well validated: use with extreme caution.
• "local": libvirt-based provider designed to use local hypervisor (not distributed with current binaries, you have to build from source to try it, cf. LIBVIRT_PROVIDER.md)

Bugfixes:

- Issue #63   
- Issue #61
- Issue #53
- Issue #52
- Issue #50
- fixed multiple race conditions when using goroutines
- fixed GPU indication detection in scanner database

SafeScale v0.1.1

Changes:

• Issue #48, enhancement: add availability zone management, mandatory now at OpenTelekom Cloud
• Issue #46: can't create duplicate network anymore
• Fix: broker share inspect must show mounts
• Fix: some build issues resolved
• Enhancement: improved integration tests (still WIP)
• Enhancement: Add images and templates filtering for OpenTelekom Cloud. Not all images and templates are usable in SafeScale context
• Doc: updates

SafeScale v0.1

First usable release of SafeScale broker, brokerd and deploy

binaries status

• broker and brokerd are considered stable
• deploy is considered beta
• perform is considered alpha

Noticeable changes with the release

Storage format of metadata

The metadata were previously stored as binary equivalent of go data structures using gob. Decision has been taken to replace this method by JSON to ease portability.
The side effect of this change is that any existing metadata are unreadable by the binaries starting with 0.1. You will have to start from zero.
Care has been taken in the encoding of metadata starting with the release 0.1 to be able to support evolution in the future.
The next release will be able to encrypt metadata content (currently everything is stored as-is, in clear text).

configuration file tenants.toml

The syntax of the file has changed, a documentation describing in details the syntax will be provided soon in doc/TENANTS.md.
In the meantime, please follow examples in doc/USAGE.md and submit issues if needed.

NAS becomes Share

In every command and in the documentation, NAS has been replaced by Share for clarity. NAS carried dual significations in SafeScale, being a server exporting a share (a NAS), and being a share in itself. It was confusing for people having experience with real NAS.
broker nas commands become broker share.

Container becomes Bucket

Because container can represent Object Storage as well as... docker container for example, the object storage "container" is now called bucket.
broker container commands become broker bucket.