SafeScale v19.06.0

News:

• !!BETA!! driver gcp for Google Cloud Platform. Considered beta in this release, some parts of the driver may change in the near future (in particular the parameters to use in tenants definition file, currently being as provided by GCP, but not following SafeScale formalism)
• K8S (kubernetes) cluster flavor is restored (after being suspended in releases v19.03.x) and is based on the last stable version of Kubernetes at cluster creation
• DCOS cluster flavor is restored (after being suspended in releases v19.03.x) and is based on DCOS v1.13
• In tenant definition file :
  • added keyword WhitelistTemplateRegexp to define a list of white-listed host templates using regexp
  • added keyword BlacklistTemplateRegexp to define a list of black-listed host templates using regexp
  • added keyword WhitelistImageRegexp to define a list of white-listed host images using regexp
  • added keyword BlacklistImageRegexp to define a list of black-listed host images using regexp
  • added keyword AvailabilityZone to set the availability zone wanted for the tenant. This keyword is mandatory for almost all the providers (notable exception being OVH which doesn't have multiple availability zones at the time being)
• In safescale host create, added parameter --sizing in replacement of --cpu,--ram,--disk (which are still present but deprecated); documentation has not been updated on that point, please see safescale host create --help for details
• In safescale cluster create, added --sizing, --gw-sizing, --master-sizing, --node-sizing in replacement of --cpu, --ram, --disk (which are still present but deprecated); documentation has not been updated on that point, please see safescale host create --help for details

Changes:

• Kong (used as reverse proxy for clusters) upgraded to v1.1
• Command safescale results are now consistently returning json data, except for safescale ssh connect and safescale ssh run
• Operator account used by SafeScale on remote hosts has been changed from gpac to safescale. To continue to use resources created with v19.03, you can use the keyword OperatorUsername: gpac in compute section of tenants description file
• feature description file:
  • added the ability to target gateway when a feature is installed on a cluster
  • added the ability to define a default value for a parameter

Fixes:

• Various data races found and fixed in safescale and safescaled
• Coherent availability zone is now enforced through tenants file; this ensures all resources are created in the same availability zone (not guaranteed in previous versions)
• Network creation ensures CIDR are RFC1918-compliant; it's not possible to ask for routable CIDR anymore

Documentation:

• Added doc about feature (usage and file description)
• Overall documentation update (but not complete yet)