v4.0.0-M7

Yorc Changelog

4.0.0-M7 (November 29, 2019)

BREAKING CHANGES

Changes on the REST API

Deployment updates

Until now deployments updates (which is a premium feature) were made on the same API operation than submitting a deployment with a given identifier:
PUT /deployments/<deployment_id>.
The decision on updating a deployment or creating a new one was based on the existence or not of a deployment with the given identifier.

This was confusing and makes error handling on clients difficult. So we decided to split those operations on two different API endpoints.
Submitting a deployment with a given identifier remain as it was, but updating a deployment is now available on the PATCH /deployments/<deployment_id> endpoint.

Trying to update a deployment on an OSS version will now result in a 401 Forbiden error instead of a 409 Conflict error previously.
Submitting a deployment with an identifier that is already used will still result in a 409 Conflict error but without an informative message indicating that a
premium version is required to perform a deployment update.

This is tracked on (GH-547: Refactor Deployment updates API).

Others

• API /health changed to /server/health (GH-551)

FEATURES

• Enrich Yorc REST API with endpoints and handlers for locations management (GH-479)
• Loading bar while bootstrap (GH-254)

ENHANCEMENTS

• Allow to specify query parameters in infrastructure usage queries (GH-543)

BUG FIXES

• Duplicate SLURM job info log in case of failure (GH-545)

v4.0.0-M6

Yorc Changelog

4.0.0-M6 (November 08, 2019)

ENHANCEMENTS

• Add Consul DB migration of hostspools due to locations modifications (GH-531)
• Allow to provide inline configuration options for generated sbatch scripts (GH-537)
• Optionally source an environment file before submitting slurm jobs (GH-541)
• Update Infrastructure collector feature to handle locations (GH-533)
• Refactor deployments package to be able to use different storage backends - part One: Reduce Consul coupling / Add Context parameter (GH-530)

BUG FIXES

• YORC_LOCATIONS_FILE_PATH env variable and locations_file_path command flag are not working (GH-535)

v4.0.0-M5

Yorc Changelog

4.0.0-M5 (October 11, 2019)

BREAKING CHANGES

The support of locations in Yorc (issue GH-478), provides the ability to create several locations of a given infrastructure type (Openstack, Google Cloud, AWS, SLURM, Hosts Pool).

It introduces breaking changes in Yorc configuration as described below.

It is not anymore possible to define infrastructure properties through:

• environment variables, like YORC_INFRA_OPENSTACK_AUTH_URL
• yorc server command flags, like --infrastructure_openstack_auth_url.

Yorc configuration file does not anymore contain infrastructures definitions. This configuration provides now the path to a file defining locations for any of these types: Openstack, Google Cloud, AWS, SLURM.

For example, this Yorc configuration file in previous version allowed to define a single infrastructure of type OpenStack:

resources_prefix: yorc-
consul:
  address: http://consul-host:8500
  datacenter: dc1
infrastructures:
  openstack:
    auth_url: http://1.2.3.4:5000
    tenant_name: mytenant
    user_name: myuser
    password: mypasswd
    region: RegionOne
    private_network_name: private-net
    default_security_groups: [group1,default]

This becomes now in this version:

resources_prefix: yorc-
consul:
  address: 127.0.0.1:8500
locations_file_path: /path/to/locations.yaml

And file /path/to/locations.yaml contains locations definitions, for example here two OpenStack locations :

locations:
  - name: myFirstOpenStackLocation
    type: openstack
    properties:
      auth_url: http://1.2.3.4:5000
      tenant_name: mytenant
      user_name: myuser
      password: mypasswd
      region: RegionOne
      private_network_name: private-net
      default_security_groups: [group1,default]
  - name: mySecondOpenStackLocation
    type: openstack
    properties:
      auth_url: http://5.6.7.8:5000
      tenant_name: mytenant
      user_name: myuser
      password: mypasswd
      region: RegionOne
      private_network_name: private-net
      default_security_groups: [group1,default]

When a Yorc server is starting and has no location defined yet, it will read this locations configuration file and create the corresponding locations.
Once this has been done, the locations configuration file won't be used anymore. Next version of Yorc will provide CLI and APIs allowing to create/update/delete locations.

Regardings Hosts Pool, the file format allowing to define one Hosts Pool hasn't changed.
But the CLI commands have now a mandatory argument to provide the location name: -l locationName or --location locationName.

For example, this command was executed in previous Yorc version to create/update a Hosts Pool from a file:

$ yorc hp apply myhostspool.yaml

It is now:

$ yorc hp apply -l myLocation myhostspool.yaml

See Yorc documentation for additional details:

• section configuration
• section on CLI commands related to Hosts pool

FEATURES

• Yorc support of Kubernetes StatefulSet (GH-206)
• Add support for asynchronous operations execution on plugins (GH-525)

ENHANCEMENTS

• Locations concept in Yorc ([GH-478(https://github.com//issues/478))

BUG FIXES

• Kubernetes Jobs do not support Service IP injection (GH-528)
• BadAccess error may be thrown when trying to resolve a TOSCA function end up in error (GH-526)
• Fix possible overlap on generated batch wrappers scripts when submitting several singularity jobs in parallel (GH-522)
• Bootstrap wrongly configures on-demand resources on OpenStack (GH-520)

v4.0.0-M4

Yorc Changelog

4.0.0-M4 (September 19, 2019)

BUG FIXES

• Fixed a bug preventing OpenStack Networks from being created (GH-515)
• Having a deployment named as a prefix of another one causes several issues (GH-504)
• A deployment may disappear from the deployments list while its currently running a purge task (GH-504)
• A4C Logs are displaying stack error when workflow step fails (GH-460)
• Bootstrap on OpenStack doesn't allow floating IP provisioning (GH-516)

v4.0.0-M3

Yorc Changelog

4.0.0-M3 (August 30, 2019)

SECURITY FIXES

• Fixed a vulnerability that could allow an attacker to read the content of a file stored on Yorc host by pretending it is an ssh key. (GHSA-8vhw-qv5r-38h5)

BUG FIXES

• Undeploying an application with a running workflow should not be possible (GH-460)

v3.2.4

Yorc Changelog

3.2.4 (August 30, 2019)

SECURITY FIXES

• Fixed a vulnerability that could allow an attacker to read the content of a file stored on Yorc host by pretending it is an ssh key. (GHSA-8vhw-qv5r-38h5)

v4.0.0-M2

Yorc Changelog

4.0.0-M2 (August 09, 2019)

ENHANCEMENTS

• Should support the creation of OpenStack Compute instances using bootable volume (GH-461)
• Allow to disable automatic Consul snapshots and restore when upgrading Yorc using ̀YORC_DISABLE_CONSUL_SNAPSHOTS_ON_UPGRADE env variable (GH-486)
• Allow to update instance attribute when creating attribute notifications (GH-491)
• Use the new Yorc plugin provided by Alien4Cloud (the Yorc Provider) in the bootstrap process. (GH-494)
• Missing documentation on premium features (GH-407)

v3.2.3

Yorc Changelog

3.2.3 (July 16, 2019)

ENHANCEMENTS

• Allow to disable automatic Consul snapshots and restore when upgrading Yorc using ̀YORC_DISABLE_CONSUL_SNAPSHOTS_ON_UPGRADE env variable (GH-486)

BUG FIXES

• Failure to deploy/undeploy big application: Transaction contains too many operations (GH-484)

v4.0.0-M1

Yorc Changelog

4.0.0-M1 (July 12, 2019)

BREAKING CHANGES

• Start v4.0 cycle (GH-444):
  • deprecated API functions are now removed
  • the former and deprecated way to handle Kubernetes deployments is not supported anymore

BUG FIXES

• Wrong resources allocation on shareable Hosts Pool (GH-426)
• Deleting one host in Pool deletes other hosts having as prefix the deleted hostname (GH-430)
• Yorc should support long standard operation names as well as short ones (GH-300)
• Fix attributes notifications for services (substitutions) (GH-423)
• Monitoring can be stopped before the job termination (GH-438)
• mem_per_node slurm option parameter is limited to integer number of GB (GH-446)
• Job node state remains to "executing" when Ansible job fails (GH-455)
• Panic occurs uploading job slurm artifacts during load test (GH-465)

ENHANCEMENTS

• Support OpenStack Block storage API v3 (GH-440)
• Expose bypass error parameter on workflow (GH-425)
• Support Alien4Cloud 2.2 (GH-441)
• Allow to provide extra env vars to Alien4Cloud during bootstrap (GH-452)
• Port CLI and Rest API minor changes for premium update feature (GH-467)
• Port changes for update nodes (GH-476)

v3.2.2

No updates on Yorc Engine, changes are located on Yorc Alien4Cloud Plugin for this release.