For safety reasons, please STOP scalr on ALL nodes with scalr-server-manage stop all command before upgrading to this version.


Starting with Scalr Enterprise Edition 7.5.3 a license file is required to be uploaded to /etc/scalr-server/license.json. Scalr will be distributing license files to all existing customers. For more information, please review our Licensing FAQ.  Please contact support with any questions.

7.6.3

Release Date: 20/Jun/17

New Feature

Improvement

Bug


Added headers

Header add strict-transport-security “max-age=31536000; includeSubDomains”
Header add x-frame-options “SAMEORIGIN”
Header add X-Content-Type-Options “nosniff”
Header add X-XSS-Protection “1; mode=block”
Header add Referrer-Policy “no-referrer”


1. BC change in APIv2. Network identifier for GCE cloud was changed.

Before:

POST /api/v1beta0/user/5/farms/9800016/farm-roles/ HTTP/1.1 
Content-Type: application/json; charset=utf-8 
X-Scalr-Key-Id: APIK4I12345 
X-Scalr-Date: 2017-06-19T16:18:49Z 
X-Scalr-Signature: PROVIDED  
Content-Length: 264 
{"alias":"gce-farm-role-test","cloudPlatform":"gce","role":{"id":"64080"},"cloudLocation":"us-central1","availabilityZones":["us-central1-a"],"instanceType":{"id":"n1-standard-1"},"networking":{"networks":[{"id":"network-test"}],"subnets":[{"id":"network-test"}]}} 

HTTP/1.1 201 Created 
Server: nginx/1.12.0 
Date: Mon, 19 Jun 2017 16:18:50 GMT 
Content-Type: application/json; utf-8 
Content-Length: 573 
Connection: keep-alive 
Vary: Accept-Encoding 
X-Powered-By: Scalr API/1beta0 
X-Original-Content-Length: 573 

{"meta":{"requestId":"46ba2685-91dc-4910-bc32-86664115e669"},"data":{"id":77,"alias":"gce-farm-role-test","farm":{"id":9800016},"role":{"id":64080},"cloudPlatform":"gce","cloudLocation":"us-central1","availabilityZones":["us-central1-a"],"instanceType":{"id":"n1-standard-1"},"scaling":{"enabled":true,"minInstances":1,"maxInstances":2,"scalingBehavior":"launch-terminate","considerSuspendedServers":"running","rules":[]},"networking":{"networks":[{"id":"network-test"}],"subnets":[{"id":"network-test"}],"hostname":{"type":"TemplateHostnameConfiguration"}}},"warnings":[]}

After:

POST /api/v1beta0/user/5/farms/9800016/farm-roles/ HTTP/1.1 
Content-Type: application/json; charset=utf-8 
X-Scalr-Key-Id: APIK412345 
X-Scalr-Date: 2017-06-19T16:27:55Z 
X-Scalr-Signature: PROVIDED  
Content-Length: 324 
{"alias":"gce-farm-role-test","cloudPlatform":"gce","role":{"id":"64080"},"cloudLocation":"us-central1","availabilityZones":["us-central1-a"],"instanceType":{"id":"n1-standard-1"},"networking":{"networks":[{"id":"scalr-labs\/global\/networks\/network-test"}],"subnets":[{"id":"network-test"}]}}

HTTP/1.1 201 Created 
Server: nginx/1.12.0 
Date: Mon, 19 Jun 2017 16:27:57 GMT 
Content-Type: application/json; utf-8 
Content-Length: 633 
Connection: keep-alive 
Vary: Accept-Encoding 
X-Powered-By: Scalr API/1beta0 
X-Original-Content-Length: 633 

{"meta":{"requestId":"e145a35e-c175-44ac-a69e-237eb584394d"},"data":{"id":98,"alias":"gce-farm-role-test","farm":{"id":9800016},"role":{"id":64080},"cloudPlatform":"gce","cloudLocation":"us-central1","availabilityZones":["us-central1-a"],"instanceType":{"id":"n1-standard-1"},"scaling":{"enabled":true,"minInstances":1,"maxInstances":2,"scalingBehavior":"launch-terminate","considerSuspendedServers":"running","rules":[]},"networking":{"networks":[{"id":"scalr-labs\/global\/networks\/network-test"}],"subnets":[{"id":"network-test"}],"hostname":{"type":"TemplateHostnameConfiguration"}}},"warnings":[]}


7.6.2

Release Date: 9/Jun/17

New Feature

Improvement

Bug


1. BC change in APIv2

After: Clone Farm responds with 201 HTTP Status code. Before: It responded with 200.

After: Copy Image responds with 201 HTTP Status Code. Before: It responded with 200.


7.6.1

Release Date: 1/Jun/17

Improvement

Bug


1. BC change in behavior

Almost all services will not handle objects from the suspended Environments.

2. BC change in APIv1 and APIv2

Forbid terminating, suspending and resuming operations for all Servers from locked Farms.

3. BC change in APIv2

Farm.alias size will be validated and should not be more than 100 characters.

Requests like:

PATCH http://84a25f59c550.test-env.scalr.com/api/v1beta0/user/5/farm-roles/46/ HTTP/1.1 
Content-Type: application/json; charset=utf-8 
X-Scalr-Key-Id: APIK12345678 
X-Scalr-Date: 2017-06-01T17:53:23Z 
X-Scalr-Signature: V1-HMAC-SHA256 12345678= 
Content-Length: 251 
{"alias":"new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value-new-very-looooong-alias-value"}

Responds with:
{
	"meta": {
		"requestId": "f1e990ce-2241-45d3-bd4a-77bc469ddc8c"
	},
	"errors": [{
		"code": "InvalidValue",
		"message": "The maximum length for property 'alias' is 100."
	}]
}

7.6.0

Release Date: 25/May/17

New Feature

Improvement

Bug


1. BC change in APIv2

Azure FarmRole object:

  • Field FarmRole.cloudFeatures.storageAccount - is optional now
  • Field FarmRole.availabilityZones[0] (availabilitySets). Managed availabilitySets cannot be used together with FarmRole.cloudFeatures.storageAccount

Changed HTTP code for some error situations: 422 -> 409

  • When on AWS Farm Roles field EphemeralStorage.template is used
  • When on AWS Farm Roles field RootStorageConfiguration.tempalte.sourceSnapshot is used
  • When size of the snapshot is bigger than PersistentStorageTemplate.tempalte.size field
  • When on AWS PersistentStorageTemplate.tempalte.sourceSnapshot snapshot is not encrypted but PersistentStorageTemplate.template.cloudFeatures.isEncrypted=true is passed

2. BC change in behavior

Before:
dateAdded - a date when the server was launched (created). It had been updated on every Server resume.
dateInitialized - a date when the server initially goes running. It had never been changed.

After:
dateAdded - a date when the server was launched (created). It won't be changed.
dateInitialized - a date when the server wen running for the last time (resume). It is updated after successful launch or resume.

3. BC change in behavior

In case if agent is not available API will return an error on attempt to execute Orchestration on the target server


  • updated apache-libcloud to 2.0

  • updated pbr to 3.0.1
  • added mitmproxy 0.18.2

7.5.3

Release Date: 27/Apr/17

For a summary see the Scalr Enterprise 7.5.3 Product Update blog post

New Feature

Improvement

Bug


  • updated cryptography to 1.8.1
  • updated apache-libcloud to 2.0.0rc2
  • removed m2crypto
  • removed pycrypto
  • added scalr/fatmouse

7.5.2

Release Date: 06/Apr/17

New Feature

Improvement

Bug


1. BC change in APIv2

FarmRole cloudFeatures.customSpecification field was renamed to cloudFeatures.customizationSpec.
Before:

"cloudFeatures": {
    "computeResource": "string", 
    "customSpecification": "string", 
    "dataStore": "string", 
    "folder": "string", 
    "hosts": [
      "string"
    ], 
    "resourcePool": "string", 
    "type": "VmwareCloudFeatures"
  }

After:

"cloudFeatures": {
    "computeResource": "string", 
    "сustomizationSpec": "string", 
    "dataStore": "string", 
    "folder": "string", 
    "hosts": [
      "string"
    ], 
    "resourcePool": "string", 
    "type": "VmwareCloudFeatures"
  }

7.5.1

Release Date: 21/Mar/17

New Feature

Improvement

Bug


  • docopt to 0.6.2
  • cherrypy to 10.1.1

7.5.0

Release Date: 02/Mar/17

New Feature

Improvement

Bug


BC сhanges in APIv2

FarmRole object was completely rediscovered

BeforeAfter
Renamed (with changes in structure in some cases)
FarmRole.platformFarmRole.cloudPlatform
FarmRole.instances.instanceType.idFarmRole.instanceType.id
FarmRole.placement.regionFarmRole.cloudLocation
FarmRole.placement.availabilityZonesFarmRole.availabilityZones
FarmRole.placement.vpcFarmRole.networking.network
FarmRole.placement.subnetsFarmRole.networking.subnets
Removed
FarmRole.instance–
FarmRole.placement–
FarmRole.placement.router–
(object) PlacementConfiguration–
(object) AwsVpcPlacementConfiguration–
(object) AwsClassicPlacementConfiguration–
Added
–FarmRole.networking
–FarmRole.bootstrapping
–FarmRole.security
–FarmRole.cloudFeatures
–(object) NetworkConfiguration
–(object) ChefServerBootstrapConfiguration
–(object) ChefSoloBoostrapConfiguration
–(object) SecurityConfiguration
–(object) CloudFeatures


BC Changes in Farm's owner history

All history of the changes of owners and teams of the Farms are writing now to auditlog as farm.ownership_change event.



  • onelogin/php-saml to v2.10.4
  • adodb/adodb-php to v5.20.9


7.4.0

Release Date: 14/Feb/17

New Feature

Improvement

Bug


1. BC change in APIv2

ReadOnly properties must not be used in API requests. 
Before:
Request to create Farm


POST http://my.scalr.lo/api/v1beta0/user/5/farms/ HTTP/1.1 
Content-Type: application/json; charset=utf-8 
X-Scalr-Key-Id: APIEXAMPLEKEY 
X-Scalr-Date: 2017-02-08T12:15:07Z 
Content-Length: 215 

{
	"name":"api-example-before",
	"description":"",
	"status":"terminated",
	"teams":[{
		"id":4,
		"name":"Users"
	}],
	"project":{
		"id":"96082d7c-1b16-4f8e-abde-0db37848db73"
	},
	"timezone":"Europe\/Moscow",
	"launchOrder":"sequential"
}


Response created Farm


{
	"meta": {
		"requestId": "7f0c2c4c-8894-4e4d-9d8f-8ad064bf4ecb"
	},
	"data": {
		"id": 9800017,
		"name": "api-example-before",
		"description": "",
		"status": "terminated",
		"owner": {
			"id": 2,
			"email": "test@scalr.com"
		},
		"teams": [{
			"id": 4,
			"name": "Users"
		}],
		"project": {
			"id": "96082d7c-1b16-4f8e-abde-0db37848db73"
		},
		"timezone": "Europe\/Moscow",
		"launchOrder": "sequential"
	},
	"warnings": []
}


After:
the same request to create Farm


POST http://my.scalr.lo/api/v1beta0/user/5/farms/ HTTP/1.1 
Content-Type: application/json; charset=utf-8 
X-Scalr-Key-Id: APIEXAMPLEKEY 
X-Scalr-Date: 2017-02-08T12:23:11Z  
Content-Length: 214 

{
	"name":"api-example-after",
	"description":"",
	"status":"terminated",
	"teams":[{"id":4,"name":"Users"}],
	"project":{"id":"96082d7c-1b16-4f8e-abde-0db37848db73"},
	"timezone":"Europe\/Moscow",
	"launchOrder":"sequential"
}

You will get the next error message with http 400 code


 {
 	"meta": {
 		"requestId": "25d5852c-2676-4e3b-a683-17578003b336"
 	},
 	"errors": [{
 		"code": "InvalidStructure",
 		"message": "You are trying to set read-only property 'status'."
 	}]
 }


2. BC Change in APIv2

Before: The following property values of objects returned as an integer instead of boolean type:

  • Script
    • blockingDefault
  • Image
    • scalrAgentInstalled
    • cloudInitInstalled]
  • OpenstackCloudCredentials
    • sslVerification
  • GlobalVariable
    • hidden
    • locked

After: The following property values of objects return as boolean type:

  • Script
    • blockingDefault
  • Image
    • scalrAgentInstalled
    • cloudInitInstalled]
  • OpenstackCloudCredentials
    • sslVerification
  • GlobalVariable
    • hidden
    • locked


7.3.2

Release Date: 30/Jan/17


New Feature

Improvement

Bug


  • boto to 2.45.0


  • Apache to 2.4.25
  • OpenSSL to 1.0.2k
  • PHP to 5.6.30


7.3.1

Release Date: 23/Jan/17


Improvement

Bug


IMPORTANT UPDATE: VPC Configuration Moves from FARM to FARM ROLE - User action may be required


  • google/apiclient to v2.1.1
  • php-amqplib/php-amqplib to 2.6.3


7.3.0

Release Date: 10/Jan/17


New Feature

Improvement

Bug

openssl - 1.0.1u
php - 5.6.28


7.2.2

Release Date: 12/Dec/16

Improvement

Bug


7.2.1

Release Date: 05/Dec/16

Improvement

Bug


Roles with Scalr Agent v. <= 0.13.6 with XML type of messages are not supported anymore


7.2.0

Release Date: 01/Dec/16

New Feature

Improvement

Bug


  • pyvmomi to 6.5


7.1.1

Release Date: 14/Nov/16

Improvement

Bug

7.1.0

Release Date: 31/Oct/16

New Feature

Improvement

Bug


1. BC change in APIv2:

If object violates Scalr Policy, API will return 409 ApiErrorResponse with PolicyViolation code. Previously it returned different error codes.


  • onelogin/php-saml to 2.10.1


7.0.0

Release Date: 05/Oct/16

New Feature

Improvement

Bug

1. BC change in Policy Engine:

Lease Management setting has become one of the Policy Engine policy and can be configured with Policy Group of Reclamation type. Therefore users which did not have access to Governance but had access to Lease Configuration will loose access to Lease Management.


  • justinrainbow/json-schema to 3.0.1


Previous versions