...
See the page on Repository Administration for instructions on how to backup and restore data from Synapse schemas. To migrate data from one instance to another in a stack the current procedure is to take a back up of the old stack, shut the stack down, and then copy the data to the new stack. Note there is a small risk of data changed in the old stack being lost if somebody adds something to the repository after the backup process has completed. This will be addressed by PLFM-404 404 . (Even if you shut down the Synapse web portal before you take the backup, changes can still come in via the repo API, which must be up to take the backup.) In meantime, workaround by communicating with team members and our small user base.
...
Once you have CNAMES pointed to the new stack, update stackInstance-stack.properties file, upload to S3, and restart the app servers to apply the change. Having our components talk to each other via the public aliases avoids security exceptions. See PLFM-506 506 .
Deploy From Artifactory
Create an IAM credentials file, using the platform credentials, per http://stackoverflow.com/questions/5396932/why-are-no-amazon-s3-authentication-handlers-ready
The IAM key should be AWSAccessKeyId=AKIAINNFCDBA3NBOQO2Q
Point to this file from the environment variable AWS_CREDENTIAL_FILE
In trunk\tools\SynapseDeployer\main.py
set the following
- version = '0.8' # set to the actual version to be deployed
- isSnapshot = True
- beanstalk_application_name =
set to 'Synapse-Staging' for staging, 'Synapse' for Synapse
- componentsToUpgrade: set to the target stack, e.g. 'prod-b-auth' for stack 'b' of alpha/prod
- make sure deploymentBucket=elasticbeanstalk-us-east-1-325565585839
...