default to not assign ip address

Author: ErinWeisbart

config.py

@@ -24,6 +24,7 @@
 MACHINE_PRICE = 0.20
 EBS_VOL_SIZE = 30                       # In GB.  Minimum allowed is 22.
 DOWNLOAD_FILES = 'False'
+ASSIGN_IP = 'False'                     # If false, will overwrite setting in Fleet file
 
 # DOCKER INSTANCE RUNNING ENVIRONMENT:
 DOCKER_CORES = 4                        # Number of CellProfiler processes to run inside a docker container

documentation/DCP-documentation/config_examples.md

@@ -46,6 +46,7 @@ Our internal configurations for each pipeline are as follows:
 | EBS_VOL_SIZE (if using S3 mounted as a file system) | 22 | 22 | 22 | 22 | 22 | Files are read directly off of S3, mounted as a file system when `DOWNLOAD_FILES = False`. |
 | EBS_VOL_SIZE (if downloading files) | 22 | 200 | 22 | 22 | 40 | Files are downloaded to the EBS volume when `DOWNLOAD_FILES = True`. |
 | DOWNLOAD_FILES | 'False' | 'False' | 'False' | 'False' | 'False' |   |
+| ASSIGN_IP | 'False' | 'False' | 'False' | 'False'  | 'False' |  |
 | DOCKER_CORES | 4 | 4 | 4 | 4  | 3 | If using c class machines and large images (2k + pixels) then you might need to reduce this number. |
 | CPU_SHARES | DOCKER_CORES * 1024 | DOCKER_CORES * 1024 | DOCKER_CORES * 1024 | DOCKER_CORES * 1024 | DOCKER_CORES * 1024 | We never change this. |
 | MEMORY | 7500 | 7500 | 7500 | 7500 | 7500 | This must match your machine type. m class use 15000, c class use 7500. |

documentation/DCP-documentation/costs.md

@@ -2,18 +2,24 @@
 
 Distributed-CellProfiler is run by a series of three commands, only one of which incurs costs at typical scale of usage:
 
-[`setup`](step_1_configuration.md) creates a queue in SQS and a cluster, service, and task definition in ECS. 
-ECS is entirely free. 
+[`setup`](step_1_configuration.md) creates a queue in SQS and a cluster, service, and task definition in ECS.
+ECS is entirely free.
 SQS queues are free to create and use up to 1 million requests/month.
 
 [`submitJobs`](step_2_submit_jobs.md) places messages in the SQS queue which is free (under 1 million requests/month).
 
-[`startCluster`](step_3_start_cluster.md) is the only command that incurs costs with initiation of your spot fleet request, creating machine alarms, and optionally creating a run dashboard. 
+[`startCluster`](step_3_start_cluster.md) is the only command that incurs costs with initiation of your spot fleet request, creating machine alarms, and optionally creating a run dashboard.
 
-The spot fleet is the major cost of running Distributed-CellProfiler, exact pricing of which depends on the number of machines, type of machines, and duration of use. 
+The spot fleet is the major cost of running Distributed-CellProfiler, exact pricing of which depends on the number of machines, type of machines, and duration of use.
 Your bid is configured in the [config file](step_1_configuration.md).
+Simple spot fleet configurations can be minimized by:
+
+1) Optimize `MACHINE_TYPE` and `EBS_VOL_SIZE` based on the actual memory and harddrive needs of your run.
+2) When possible, mount your S3 bucket using S3FS so that you can set `DOWNLOAD_FILES = 'False'` to not incur file egress costs.
+3) Set `ASSIGN_IP = 'False'` so that you don't pay for IPv4 addresses per EC2 instance in your spot fleet.
 
 Spot fleet costs can be minimized/stopped in multiple ways:
+
 1) We encourage the use of [`monitor`](step_4_monitor.md) during your job to help minimize the spot fleet cost as it automatically scales down your spot fleet request as your job queue empties and cancels your spot fleet request when you have no more jobs in the queue.
 Note that you can also perform a more aggressive downscaling of your fleet by monitor by engaging Cheapest mode (see [`more information here`](step_4_monitor.md)).
 2) If your job is finished, you can still initiate [`monitor`](step_4_monitor.md) to perform the same cleanup (without the automatic scaling).
@@ -23,14 +29,16 @@ Note that you can also perform a more aggressive downscaling of your fleet by mo
 After the spot fleet has started, a Cloudwatch instance alarm is automatically placed on each instance in the fleet.
 Cloudwatch instance alarms [are currently $0.10/alarm/month](https://aws.amazon.com/cloudwatch/pricing/).
 Cloudwatch instance alarm costs can be minimized/stopped in multiple ways:
+
 1) If you run monitor during your job, it will automatically delete Cloudwatch alarms for any instance that is no longer in use once an hour while running and at the end of a run.
 2) If your job is finished, you can still initiate [`monitor`](step_4_monitor.md) to delete Cloudwatch alarms for any instance that is no longer in use.
 3) In [AWS Cloudwatch console](https://console.aws.amazon.com/cloudwatch/) you can select unused alarms by going to Alarms => All alarms. Change Any State to Insufficient Data, select all alarms, and then Actions => Delete.
 4) We provide a [hygiene script](hygiene.md) that will clean up old alarms for you.
 
-Cloudwatch Dashboards [are currently free](https://aws.amazon.com/cloudwatch/pricing/) for 3 Dashboards with up to 50 metrics per month and are $3 per dashboard per month after that. 
+Cloudwatch Dashboards [are currently free](https://aws.amazon.com/cloudwatch/pricing/) for 3 Dashboards with up to 50 metrics per month and are $3 per dashboard per month after that.
 Cloudwatch Dashboard costs can be minimized/prevented in multiple ways:
+
 1) You can choose not to have Distributed-CellProfiler create a Dashboard by setting `CREATE_DASHBOARD = 'False'` in your [config file](step_1_configuration.md).
 2) We encourage the use of [`monitor`](step_4_monitor.md) during your job as if you have set `CLEAN_DASHBOARD = 'True'` in your [config file](step_1_configuration.md) it will automatically delete your Dashboard when your job is done.
 3) If your job is finished, you can still initiate [`monitor`](step_4_monitor.md) to perform the same cleanup (without the automatic scaling).
-4) You can manually delete Dashboards in the [Cloudwatch Console]((https://console.aws.amazon.com/cloudwatch/)) by going to Dashboards, selecting your Dashboard, and selecting Delete.
+4) You can manually delete Dashboards in the [Cloudwatch Console]((https://console.aws.amazon.com/cloudwatch/)) by going to Dashboards, selecting your Dashboard, and selecting Delete.

documentation/DCP-documentation/step_1_configuration.md

@@ -17,6 +17,7 @@ It need not be unique, but it should be descriptive enough that you can tell job
 ***
 
 ### AWS GENERAL SETTINGS
+
 These are settings that will allow your instances to be configured correctly and access the resources they need- see [Step 0: Prep](step_0_prep.md) for more information.
 
 Bucket configurations allow you to read/write from/to different bucket in different accounts from where you are running DCP.
@@ -53,10 +54,15 @@ The minimum allowed is 22.
 If you have multiple Dockers running per machine, each Docker will have access to (EBS_VOL_SIZE/TASKS_PER_MACHINE)- 2 GB of space.
 * **DOWNLOAD_FILES:** Whether or not to download the image files to the EBS volume before processing, as opposed to accessing them all from S3FS.
 This typically requires a larger EBS volume (depending on the size of your image sets, and how many sets are processed per group), but avoids occasional issues with S3FS that can crop up on longer runs.
+* **ASSIGN_IP:** Whether or not to assign an a public IPv4 address to each instance in the spot fleet.
+If set to 'False' will overwrite whatever is in the Fleet file.
+If set to 'True' will respect whatever is in the Fleet file.
+Distributed-CellProfiler originally defaulted to assign an IP address to each instance so that one could connect to the instance for troubleshooting but that need has been obviated by the level of logging currently in DCP.
 
 ***
 
 ### DOCKER INSTANCE RUNNING ENVIRONMENT
+
 * **DOCKER_CORES:** How many copies of your script to run in each Docker container.
 * **CPU_SHARES:** How many CPUs each Docker container may have.
 * **MEMORY:** How much memory each Docker container may have.
@@ -83,8 +89,9 @@ See [Step 0: Prep](step_0_prep.med) for more information.
 
 ***
 
- ### MONITORING
- * **AUTO_MONITOR:** Whether or not to have Auto-Monitor automatically monitor your jobs.
+### MONITORING
+
+* **AUTO_MONITOR:** Whether or not to have Auto-Monitor automatically monitor your jobs.
 
 ***
 
@@ -111,6 +118,7 @@ Useful when trying to detect jobs that may have exported smaller corrupted files
 ***
 
 ### CELLPROFILER SETTINGS
+
 * **ALWAYS CONTINUE:** Whether or not to run CellProfiler with the --always-continue flag, which will keep CellProfiler from crashing if it errors.
 Use with caution.
 This can be particularly helpful in jobs where a large number of files are loaded in a single run (such as during illumination correction) so that a corrupted or missing file doesn't prevent the whole job completing.
@@ -120,6 +128,7 @@ We suggest using this setting in conjunction with a small number of JOB_RETRIES.
 ***
 
 ### PLUGINS
+
 * **USE_PLUGINS:** Whether or not you will be using external plugins from the CellProfiler-plugins repository.
 When True, passes the `--plugins-directory` flag to CellProfiler.
 Defaults to the current v1.0 `CellProfiler-plugins/active_plugins` location for plugins but will revert to the historical location of plugins in the `CellProfiler-plugins` root directory if the `active_plugins` folder is not present.
@@ -147,7 +156,7 @@ If you need to use deprecated plugin organization you can access previous commit
 
 ### EXAMPLE CONFIGURATIONS
 
-!(Sample_Distributed-CellProfiler_Configuration_1)[images/sample_DCP_config_1.png]
+![Sample_Distributed-CellProfiler_Configuration_1](images/sample_DCP_config_1.png)
 
 This is an example of one possible configuration.
 It's a fairly large machine that is able to process 64 jobs at the same time.
@@ -159,9 +168,9 @@ The Config settings for this example are:
 
 **DOCKER_CORES** = 4        (copies of CellProfiler to run inside a docker)  
 **CPU_SHARES** = 4096       (number of cores for each Docker * 1024)  
-**MEMORY** = 15000          (MB for each Docker)    
+**MEMORY** = 15000          (MB for each Docker)
 
-!(Sample_Distributed-CellProfiler_Configuration_2)[images/sample_DCP_config_2.png]
+![Sample_Distributed-CellProfiler_Configuration_2](images/sample_DCP_config_2.png)
 
 This is an example of another possible configuration.
 When we run Distributed CellProfiler we tend to prefer running a larger number of smaller machine.
@@ -175,4 +184,4 @@ The Config settings for this example are:
 
 **DOCKER_CORES** = 4        (copies of CellProfiler to run inside a docker)  
 **CPU_SHARES** = 4096       (number of cores for each Docker * 1024)  
-**MEMORY** = 15000          (MB for each Docker)    
+**MEMORY** = 15000          (MB for each Docker)

example_project/config.py

@@ -21,6 +21,7 @@
 MACHINE_PRICE = 0.13
 EBS_VOL_SIZE = 22                       # In GB.  Minimum allowed is 22.
 DOWNLOAD_FILES = 'False'
+ASSIGN_IP = 'False'                     # If false, will overwrite setting in Fleet file
 
 # DOCKER INSTANCE RUNNING ENVIRONMENT:
 DOCKER_CORES = 1                        # Number of CellProfiler processes to run inside a docker container

example_project_CPG/config.py

@@ -22,6 +22,7 @@
 MACHINE_PRICE = 0.13
 EBS_VOL_SIZE = 22                       # In GB.  Minimum allowed is 22.
 DOWNLOAD_FILES = 'True'
+ASSIGN_IP = 'False'                     # If false, will overwrite setting in Fleet file
 
 # DOCKER INSTANCE RUNNING ENVIRONMENT:
 DOCKER_CORES = 1                        # Number of CellProfiler processes to run inside a docker container

files/exampleFleet_us-east-1.json

@@ -32,7 +32,7 @@
           "DeviceIndex": 0,
           "SubnetId": "subnet-WWWWWWWW",
           "DeleteOnTermination": true,
-          "AssociatePublicIpAddress": true,
+          "AssociatePublicIpAddress": false,
           "Groups": [
             "sg-ZZZZZZZZZ"
           ]

files/exampleFleet_us-west-2.json

@@ -32,7 +32,7 @@
           "DeviceIndex": 0,
           "SubnetId": "subnet-WWWWWWWW",
           "DeleteOnTermination": true,
-          "AssociatePublicIpAddress": true,
+          "AssociatePublicIpAddress": false,
           "Groups": [
             "sg-ZZZZZZZZZ"
           ]

run.py

@@ -21,6 +21,7 @@
 REQUIREMENTS_FILE = False
 ALWAYS_CONTINUE = 'False'
 JOB_RETRIES = 10
+ASSIGN_IP = 'True'
 
 from config import *
 
@@ -595,7 +596,11 @@ def startCluster():
         spotfleetConfig['LaunchSpecifications'][LaunchSpecification]["UserData"]=userData
         spotfleetConfig['LaunchSpecifications'][LaunchSpecification]['BlockDeviceMappings'][1]['Ebs']["VolumeSize"]= EBS_VOL_SIZE
         spotfleetConfig['LaunchSpecifications'][LaunchSpecification]['InstanceType'] = MACHINE_TYPE[LaunchSpecification]
-
+    if not ASSIGN_IP:
+        try:
+            spotfleetConfig['LaunchSpecifications'][0]['NetworkInterfaces'][0]['AssociatePublicIpAddress'] = False
+        except:
+            print("Couldn't add or overwrite 'AssociatePublicIpAddress' to False in spot fleet config.")
 
     # Step 2: make the spot fleet request
     ec2client=boto3.client('ec2')