Start AWS Instance
Ansible Setup
- Locally clone the fcrepo4-ansible project
- Follow the README and install the required software and set system environment variables
- There are two configuration to choose from:
- Fedora 4 with a file-based database (default)
- Fedora 4 with a PostgreSQL database
- Run
```
cd /path/to/fcrepo4-ansiblevagrant up --provider aws
``` - The Fedora 4 is accessible at this URL: http://[SERVER IP]:8080/fcrepo/
Puppet Setup
- Locally clone the fcrepo-aws-puppet project
- Follow the README from the fcrepo-aws-puppet project
- There are two configurations to choose from:
- Single node, async-indexing (default)
- Includes YourKit agent for remote profiling
- Clustered
- Single node, async-indexing (default)
...
Fedora 4 can be run in a clustered configuration on AWS. We ran performance benchmarks using these additional java opts:
Code Block |
---|
### # Clustering ### JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.infinispan.cache_configuration=config/infinispan/clustered/infinispan.xml" JAVA_OPTS="${JAVA_OPTS} -Djgroups.tcp.address=<aws-private-ip>" JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.ispn.numOwners=2 -Djava.net.PreferIPv4Stack=true" # The jgroups-ec2.xml file is included in ispn's jars JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.ispn.jgroups.configuration=jgroups-ec2.xml" # This property overwrites the S3 bucketname variable in jgroups-ec2.xml JAVA_OPTS="${JAVA_OPTS} -Djgroups.s3.bucket=fcrepo4-cluster-0" |
Most importantly, we used the jgroups-ec2 configuration, which enables auto-discovery of nodes by writing content into an S3 bucket.
...