Section | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Deployed Stacks
We now have the following CNAMEs for Synapse in the sagebase.org domain:
...
- crowd-dev.sagebase.org – for the dev/test Crowd instance, the default for our code base (-> elastic IP 50.17.192.58)
- crowd.sagebase.org – for the production Crowd instance, specified in Synpase via a system property, as documented on Synapse Stack Deployment (-> elastic IP 50.17.212.74)
Current Beanstalk Resources LAST UPDATED: 20Jun2011
CNAME | Beanstalk Name | Beanstalk URL | war file version | Crowd Instance | Database | Service group | ||
---|---|---|---|---|---|---|---|---|
synapse-alpha.sagebase.org | Prod-SynapseWeb |
| prod-synapseweb.elasticbeanstalk.com |
| SynapseWebAlpha_0.4_16June_svn3014 |
|
| prod |
reposvc-alpha.sagebase.org | Prod-RepoService | prod-reposervice.elasticbeanstalk.com | SynapseRepoService_0.4_14June2011 |
|
| prod | ||
auth-alpha.sagebase.org | Prod-Auth | prod-auth.elasticbeanstalk.com | Prod-AuthVersion |
|
| prod | ||
n/a | Staging-Auth |
|
|
|
| staging | ||
n/a | Staging-SynapseWeb |
|
|
|
| staging | ||
n/a | Staging-RepoService |
|
|
|
| staging |
Synapse Deployment Instructions
Get the built artifacts from Artifactory
You should not be deploying anything you built yourself on your local machine. Only deploy builds generated by Bamboo and stored in Artifactory.
Create Beanstalk Environments (Skip this section if using existing Environments.)
log in to AWS
http://aws.amazon.com/console/
...
Create two more, so that there is one for Auth services, one for Repo services, and one for SynapseWeb
Create Host Name
Sign in to GoDaddy, select sagebase.org, and launch Domain Manager.
...
Ditto for auth-prod and reposvc-prod
Create MySQL database
If necessary, create a new schema in the AWS RDS, e.g. using MySQL Workbench.
The schema name, for example, might be 'prodRepositoryDb'
Configure Environments
For the authentication service:
Click on 'edit configuration' in the Beanstalk UI.
...
-DACCEPT_ALL_CERTS=true -Dorg.sagebionetworks.stack=staging -Dorg.sagebionetworks.stackEncryptionKey=integration-test-only-encryption-key
For the Repo service:
For 'HTTPS Listener port' choose '443'.
...
-DACCEPT_ALL_CERTS=true -Dorg.sagebionetworks.stack=staging -Dorg.sagebionetworks.stackEncryptionKey=integration-test-only-encryption-key
For the Synapse Web Application:
For 'HTTPS Listener port' choose '443'.
For 'SSL Cert' choose arn:aws:iam::325565585839:server-certificate/SynapseCert
Set up Crowd
If necessary, the instructions are here:
http://sagebionetworks.jira.com/wiki/display/PLFM/Setting+Up+Production+Crowd
Restarting Crowd
If the server goes down:
To check if Crowd is up, in web browser go to
https://crowd.sagebase.org:8443/crowd
You should see Crowd log-in page. If not then ssh in to crowd.sagebase.org as ec2-user, using the standard key for 'platform' owned ec2 instances, PlatformKeyPairEast
...
The above instructions apply to 'crowd-dev.sagebase.org' as well as 'crowd.sagebase.org'.
How to run the Data Loader
On one of the local servers, goto /work/platform/DatasetMetadataLoader and execute the following:
Code Block |
---|
# Make sure you have the latest version svn up # Execute the loader # Replace <repo_instance> and <auth_instance> by the repository and authentication instances. # Either make sure that demouser@sagebase.org is a Synapse administrator on crowd, or replace it by a Synapse administrator account python datasetCsvLoader.py -d ./AllDatasets.csv -l ./AllDatasetLayerLocations.csv -e http://<repo_instance>/repo/v1 -a http://<auth_instance>/auth/v1 -m /work/platform/DatasetMetadataLoader/platform.md5sums.csv -u demouser@sagebase.org -p demouser-pw |
Verify Deployment
To verify deployment, run top-level queries against the repository instances from an authenticated account.
...