-
Notifications
You must be signed in to change notification settings - Fork 3
/
ec2_byo_instance.yml
88 lines (77 loc) · 3.52 KB
/
ec2_byo_instance.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
# general configuration applicable to the entire app
general:
name: llama3b-g6e-byo-instance
aws:
# This is the path to the hf token file that contains your custom
# hf token
hf_token_fpath: /tmp/hf_token.txt
# AWS region, this parameter is templatized, no need to change
region: {{region}}
# steps to run the fmbench orchestration
# test. If all steps are set to yes, the security
# group will be greated, the keys will be generated at
# instance creation, EC2 instances will be created,
# the FMBench orchestration test will run and then at the
# end the infrastructure (in this case EC2 instances) will
# be deleted.
# All results are stored in the local results directory at the end of the
# FMBench orchestration test.
run_steps:
security_group_creation: yes
key_pair_generation: no
deploy_ec2_instance: yes
run_bash_script: yes
delete_ec2_instance: yes
security_group:
group_name: fmbench_orchestrator_sg
description: MultiDeploy EC2 Security Group
# If VPC Is left empty, boto3 automatically gets the default VPC for your region
# If your current region does not have an active default VPC set up, set it up manually
# following the steps here: https://docs.aws.amazon.com/vpc/latest/userguide/work-with-default-vpc.html#create-default-vpc
vpc_id:
key_pair_gen:
#Need to change this name to something better?
# This assumes that if key_pair_generation is false, you have the key pair stored in the root.
# If so, change the file name to your KP name and the script will pick it up.
key_pair_name: H1-kp
#Instance follows the format below.
# instance_id: {instance_id_here} if Instance_id, then you need to bring your own private key
# private_key_fname: key_pair/fmbench_orchestrator_1-us-east-1
# OR
# - instance_type: {instance_name_here}
# region: {region_here}
# ami_id: {ami_id_here}
# device_name: /dev/sda1
# ebs_del_on_termination: True | False
# ebs_Iops: 16000
# ebs_VolumeSize: {Volume_Size_Here}
# ebs_VolumeType: {Volume_type_Here}
# #Defaults to none, You can use either Reservation Id ARN or both (The below 3 fields are optional)
# CapacityReservationPreference: open | none
# CapacityReservationId: {The ID of the Capacity Reservation in which to run the instance.}
# CapacityReservationResourceGroupArn: {The ARN of the Capacity Reservation resource group in which to run the instance.}
### REQUIRED WITH ABOVE:
# startup_script: startup_scripts/gpu_ubuntu_startup.txt
# post_startup_script: post_startup_scripts/fmbench.txt
# fmbench_config: https://raw.githubusercontent.com/dheerajoruganty/multi-deploy-ec2/refs/heads/main/configs/config-ec2-llama3-8b.yml
### OPTIONAL:
# fmbench_llm_tokenizer_fpath: fmbench_llm_utils/tokenizer.json
# fmbench_llm_config_fpath: fmbench_llm_utils/config.json
# fmbench_tokenizer_remote_dir: /tmp/fmbench-read/llama3_tokenizer/
# # Timeout period in Seconds before a run is stopped
# fmbench_complete_timeout: 1200
## US-EAST-1 Mapping:
# Neuron AMI : ami-05d498302130f9036
# DeepLearning AMI AL2 : ami-07f302d2a74e2b584
# Al2 AMI, CPU bench : ami-0e54eba7c51c234f6
# Take the below as list of dict as there might be 2 instances with the same AMI
instances:
- instance_id: i-your-instance-id
private_key_fname: key_pair/H1-kp.pem
region: {{region}}
startup_script: startup_scripts/ubuntu_startup.txt
post_startup_script: post_startup_scripts/fmbench.txt
# Timeout period in Seconds before a run is stopped
fmbench_complete_timeout: 2400
fmbench_config:
- fmbench:llama3/8b/config-ec2-llama3-8b-g6e-2xlarge.yml