AWS:Set up account - Revision history

Btingle: /* Installation */

2022-10-19T20:38:54Z

Installation

← Older revision		Revision as of 20:38, 19 October 2022
Line 33:		Line 33:
	docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock -it dockingorg/aws-setup</nowiki>		docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock -it dockingorg/aws-setup</nowiki>

	[[File:~~Awsdock~~-~~imagetut~~-~~step1~~.png\|~~thumb~~\|Example session depicting pulling the aws-setup image, running it, authenticating with AWS, and initializing the account.]]		[[File:Step1-docktut-again.png\|x300px\|Example session depicting pulling the aws-setup image, running it, authenticating with AWS, and initializing the account.]]

	= Container Environment =		= Container Environment =

Btingle: /* Environment Creation */

2022-10-19T20:36:11Z

Environment Creation

← Older revision		Revision as of 20:36, 19 October 2022
Line 99:		Line 99:

	[[File:Step6.png\|none\|x150px]]		[[File:Step6.png\|none\|x150px]]
	~~<nowiki>What bucket would you like to attach to this environment? mybucket</nowiki>~~

	Set MAX_CPUS for your environment to desired value. This parameter refers to the maximum number of jobs that can be run in parallel. You should set this at or below the suggested value- this value is derived from the AWS imposed resource limit. You can learn more about resource limits and how to increase them at this page: [[Docking_Submission_On_AWS#Resource_Limits]]		Set MAX_CPUS for your environment to desired value. This parameter refers to the maximum number of jobs that can be run in parallel. You should set this at or below the suggested value- this value is derived from the AWS imposed resource limit. You can learn more about resource limits and how to increase them at this page: [[Docking_Submission_On_AWS#Resource_Limits]]

Btingle: /* Environment Creation */

2022-10-19T20:35:40Z

Environment Creation

← Older revision		Revision as of 20:35, 19 October 2022
Line 97:		Line 97:

	Attach the bucket you created to the environment. Don't qualify this with the s3:// path, just the plain name.		Attach the bucket you created to the environment. Don't qualify this with the s3:// path, just the plain name.

			[[File:Step6.png\|none\|x150px]]
	<nowiki>What bucket would you like to attach to this environment? mybucket</nowiki>		<nowiki>What bucket would you like to attach to this environment? mybucket</nowiki>

	Set MAX_CPUS for your environment to desired value. This parameter refers to the maximum number of jobs that can be run in parallel. You should set this at or below the suggested value- this value is derived from the AWS imposed resource limit. You can learn more about resource limits and how to increase them at this page: [[Docking_Submission_On_AWS#Resource_Limits]]		Set MAX_CPUS for your environment to desired value. This parameter refers to the maximum number of jobs that can be run in parallel. You should set this at or below the suggested value- this value is derived from the AWS imposed resource limit. You can learn more about resource limits and how to increase them at this page: [[Docking_Submission_On_AWS#Resource_Limits]]

	~~<nowiki>How many CPUS would you like to allocate~~ to this ~~environment at maximum? [suggested: 128]: </nowiki>~~		Set BID_PERCENTAGE for your environment to desired value. See section below for more explanation of this parameter, it can potentially save you money. If you're not sure, keep the default.

	~~Set BID_PERCENTAGE for your environment to desired value~~. ~~See section below for more explanation of this parameter, it can potentially save~~ you ~~money. If you're not sure, keep the default.~~		[[File:Stepwhatever2.png\|x119px\|Prompts where you will set MAX_CPUS and BID_PERCENTAGE are highlighted]]
	~~<nowiki>What is your bid percentage threshold for spot instances? See the docs for more info on this parameter. [default: 100~~]~~: 100</nowiki>~~

	=== Bid Percentage ===		=== Bid Percentage ===

Btingle: /* S3 Bucket */

2022-10-19T20:22:50Z

S3 Bucket

← Older revision		Revision as of 20:22, 19 October 2022
Line 75:		Line 75:

	It is best to have a dedicated S3 bucket for each region you create an environment for, due to the cost of inter-region data transfer.		It is best to have a dedicated S3 bucket for each region you create an environment for, due to the cost of inter-region data transfer.

			[[File:Awsdock-Step3-flowchart.png\|thumb\|Diagram explaining how to create an S3 bucket. Note the region- N.Virginia aka us-east-1. This is the optimal region for running docking.]]

	=== First time setup ===		=== First time setup ===

Btingle: /* Installation */

2022-10-19T20:12:55Z

Installation

@@ Line 33: / Line 33: @@
 docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock -it dockingorg/aws-setup</nowiki>
-If you're using a remote docker instance through the DOCKER_HOST environment variable, for example on windows WSL2, you can use the following script in place of 'docker run':
+[[File:Awsdock-imagetut-step1.png|thumb|Example session depicting pulling the aws-setup image, running it, authenticating with AWS, and initializing the account.]]
 = Container Environment =

Btingle at 22:10, 11 October 2022

2022-10-11T22:10:34Z

← Older revision		Revision as of 22:10, 11 October 2022
Line 15:		Line 15:

	<nowiki>		<nowiki>
	docker pull ~~btingle~~/aws-setup		docker pull dockingorg/aws-setup
	docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -it ~~btingle~~/aws-setup</nowiki>		docker run -v /var/run/docker.sock:/var/run/docker.sock --rm -it dockingorg/aws-setup</nowiki>

	Explanation of arguments:		Explanation of arguments:
Line 31:		Line 31:

	<nowiki>		<nowiki>
	docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock -it ~~btingle~~/aws-setup</nowiki>		docker run --privileged --rm -v /var/run/docker.sock:/var/run/docker.sock -it dockingorg/aws-setup</nowiki>

	If you're using a remote docker instance through the DOCKER_HOST environment variable, for example on windows WSL2, you can use the following script in place of 'docker run':		If you're using a remote docker instance through the DOCKER_HOST environment variable, for example on windows WSL2, you can use the following script in place of 'docker run':
Line 45:		Line 45:

	# essentially we are just forwarding the DOCKER_HOST information to the container (making sure to use host.docker.internal if DOCKER_HOST is localhost)		# essentially we are just forwarding the DOCKER_HOST information to the container (making sure to use host.docker.internal if DOCKER_HOST is localhost)
	docker run --env DOCKER_HOST=$prot//$host:$port --rm -it ~~btingle~~/awsdock-setup</nowiki>		docker run --env DOCKER_HOST=$prot//$host:$port --rm -it dockingorg/awsdock-setup</nowiki>

	= Container Environment =		= Container Environment =
Line 53:		Line 53:
	If you have files you'd like to access from the container, you can link them in using the docker "-v" option. By default we link the docker socket using this option ("-v /var/run/docker.sock:/var/run/docker.sock"), but you can link any number of directories or files in this manner. For example, if you would like the contents of the "/tmp" directory on your local machine to be available under "/temp" in the docker image, you would add the following option to your "docker run" command: "-v /tmp:/temp", for a final command of:		If you have files you'd like to access from the container, you can link them in using the docker "-v" option. By default we link the docker socket using this option ("-v /var/run/docker.sock:/var/run/docker.sock"), but you can link any number of directories or files in this manner. For example, if you would like the contents of the "/tmp" directory on your local machine to be available under "/temp" in the docker image, you would add the following option to your "docker run" command: "-v /tmp:/temp", for a final command of:

	<nowiki>docker run -v /tmp:/temp -v /var/run/docker.sock:/var/run/docker.sock --rm -it ~~btingle~~/aws-setup:latest</nowiki>		<nowiki>docker run -v /tmp:/temp -v /var/run/docker.sock:/var/run/docker.sock --rm -it dockingorg/aws-setup:latest</nowiki>

	If you're an advanced user and you'd like to create your own version of the aws-setup image with certain software preinstalled, you can request us for access to the aws-setup repository, which contains the scripts and Dockerfile we use to set up the docker image. You can also build your own image using our aws-setup image as a base.		If you're an advanced user and you'd like to create your own version of the aws-setup image with certain software preinstalled, you can request us for access to the aws-setup repository, which contains the scripts and Dockerfile we use to set up the docker image. You can also build your own image using our aws-setup image as a base.

Frodo: asdf

2022-09-14T21:30:52Z

asdf

← Older revision		Revision as of 21:30, 14 September 2022
Line 1:		Line 1:
			* Tutorial 1 AWS:Set up account THIS TUTORIAL

	* Tutorial 1 AWS:Set up account
	* Tutorial 2: [[AWS:Upload files for docking]]		* Tutorial 2: [[AWS:Upload files for docking]]
	* Tutorial 3: [[AWS:Submit docking job]]		* Tutorial 3: [[AWS:Submit docking job]]

Frodo: asdf

2022-09-14T21:30:30Z

asdf

← Older revision		Revision as of 21:30, 14 September 2022
Line 1:		Line 1:


	* Tutorial 1 ~~of the~~ AWS ~~Docking tutorial.~~		* Tutorial 1 AWS:Set up account
	* Tutorial 2: [[AWS:Upload files for docking]]		* Tutorial 2: [[AWS:Upload files for docking]]
	* Tutorial 3: [[AWS:Submit docking job]]		* Tutorial 3: [[AWS:Submit docking job]]

Frodo: asdf

2022-09-14T20:42:56Z

asdf

← Older revision		Revision as of 20:42, 14 September 2022
Line 1:		Line 1:


	* ~~Part~~ 1 ~~of 3~~ of the AWS Docking tutorial.		* Tutorial 1 of the AWS Docking tutorial.
	* ~~Next~~ Tutorial #2: [[AWS:Upload files for docking]]		* Tutorial 2: [[AWS:Upload files for docking]]
	* ~~Third~~ Tutorial #3: [[AWS:Submit docking job]]		* Tutorial 3: [[AWS:Submit docking job]]
			* Tutorial 4: [[AWS:Merge and download results]]
			* Tutorial 5: [[AWS:Cleanup]]


	= Installation =		= Installation =

Frodo: asdf

2022-09-14T20:40:45Z

asdf

← Older revision		Revision as of 20:40, 14 September 2022
Line 1:		Line 1:


	Part 1 of 3 of the AWS Docking tutorial.		* Part 1 of 3 of the AWS Docking tutorial.
	Next Tutorial #2: [[AWS:Upload files for docking]]		* Next Tutorial #2: [[AWS:Upload files for docking]]
	Third Tutorial #3: [[~~Docking_Submission_On_AWS~~]]		* Third Tutorial #3: [[AWS:Submit docking job]]

	= Installation =		= Installation =