-
Notifications
You must be signed in to change notification settings - Fork 0
Steps for executing system tests using Docker Swarm based System Test Framework
-
An AWS account.
-
Terraform installed.
-
aws-access-key
,aws-secret-key
,aws-region
andAWS key pem file
from AWS console.
-
aws-cred-path
- the absolute path where AWS.pem
file is located. -
config-path
- the absolue path where AWS config terraform files are located.($rootDir/test/system/aws
) -
pravega-org-name
- the default ispravega/pravega
and if it is a fork that you are using, then usefork-name/pravega
(github user-name/repo-name). Some forks might be likexxxx/pravega1
. In such cases, we should use the samexxxx/pravega1
. -
branch-name
- the branch against which you want to run system tests. -
image-version
- should be same asbranch-name
. -
commit-id
- the commit id for the latest commit to your branch.
To execute system tests
./gradlew clean --info startSystemTestsWithDocker -DskipServiceInstallation=false -Dlog.level=DEBUG -DexecType=DOCKER -PawsExecution=true -Paws_access_key=<aws-access-key> -Paws_secret_key=<aws-secret-key> -Paws_region=<aws-region> -Paws_key_name=<aws-key-name> -Pcred_path=<aws-cred-path> -Pconfig_path=<config-path> -Ppravega_org=<pravega-org-name> -Ppravega_branch=<branch-name> -DimageVersion=<pravega-image-version> -DawsExec=true
To collect logs into s3 bucket
./gradlew --info collectSystemTestLogsFromAws -Paws_access_key=<aws-access-key> -Paws_secret_key=<aws-secret-key>
-Paws_region=<aws-region> -Paws_key_name=<aws-key-name> -Pcred_path=<aws-cred-path> -Pconfig_path=<config-path>
-Ppravega_org=<pravega-org-name> -Ppravega_branch= <branch-name> -Ptravis_commit=<commit-id>
Use travis.yml
Note: Logs are stored in the following format:
branch-name
|
commit-id
|
log-files
Pravega - Streaming as a new software defined storage primitive
- Contributing
- Guidelines for committers
- Testing
-
Pravega Design Documents (PDPs)
- PDP-19: Retention
- PDP-20: Txn timeouts
- PDP-21: Protocol revisioning
- PDP-22: Bookkeeper based Tier-2
- PDP-23: Pravega Security
- PDP-24: Rolling transactions
- PDP-25: Read-Only Segment Store
- PDP-26: Ingestion Watermarks
- PDP-27: Admin Tools
- PDP-28: Cross routing key ordering
- PDP-29: Tables
- PDP-30: Byte Stream API
- PDP-31: End-to-end Request Tags
- PDP-32: Controller Metadata Scalability
- PDP-33: Watermarking
- PDP-34: Simplified-Tier-2
- PDP-35: Move controller metadata to KVS
- PDP-36: Connection pooling
- PDP-37: Server-side compression
- PDP-38: Schema Registry
- PDP-39: Key-Value Tables
- PDP-40: Consistent order guarantees for storage flushes
- PDP-41: Enabling Transport Layer Security (TLS) for External Clients
- PDP-42: New Resource String Format for Authorization
- PDP-43: Large Events
- PDP-44: Lightweight Transactions
- PDP-45: Healthcheck
- PDP-46: Read Only Permissions For Reading Data
- PDP-47: Pravega Message Queues