[ 
https://issues.apache.org/jira/browse/IGNITE-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332550#comment-15332550
 ] 

Igor Rudyak commented on IGNITE-3293:
-------------------------------------

Alexey,

1) All user related documentation is already available on Ignite website: 
https://apacheignite.readme.io/docs/aws-infrastructure-deployment

2) Added more comments to all shell scripts.

3) By the nature of AWS bootstrap scripts it's not possible to store all these 
variables AWS_CLI_DOWNLOAD_URL, JDK_DOWNLOAD_URL and TESTS_PACKAGE_DONLOAD_URL 
in one place - cause every bootstrap script should be self contained. As you 
may also found there are several absolutely same functions which I just copy 
and pasted among cassandra-bootstrap.sh, ignite-bootstrap.sh, 
tests-bootstrap.sh & master-bootstrap.sh scripts. That's because of the same 
limitation. However I moved as much as it was possible common functions and 
configuration settings into common.sh and env.sh scripts. These scripts are 
downloaded from S3 with the tests package once all the required pre-requisites 
(JDK, AWS CLI and etc.) installed on EC2 node by bootstrap script.

4) This is hardcoded static IP address inside Amazon Cloud, where they are 
hosting their metadata service. It provides REST API and allows each EC2 
instance to get information about itself: 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html



> AWS bootstrap scripts patch for Ignite-Cassandra 
> -------------------------------------------------
>
>                 Key: IGNITE-3293
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3293
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.6, 1.7
>            Reporter: Igor Rudyak
>            Assignee: Igor Rudyak
>
> New version of AWS bootstrap script having:
> 1) Gaglia monitoring
> 2) Allows to manually trigger tests execution multiple times on the same 
> ifstastructure



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to