If a user wants to benchmark on a pre existing instance that does not have FMBench installed, they would have to stop the instance, update the user data and re run the instance. Now in this case, the start up script is directly run on the pre existing instance before running the benchmarking test.
Made the key pair name independent of the region in the case of when a user wants to benchmark on a pre existing instance. If a user has already configured a key pair that does not contain the region name, they would face an error because the orchestrator always appends the region to the key pair name (even in the case of byo instance). Now that is handled.
This is handled with a bring your own instance test on a g5.24xl for llama3.1 8b instruct.
This PR contains the following:
If a user wants to benchmark on a pre existing instance that does not have FMBench installed, they would have to stop the instance, update the user data and re run the instance. Now in this case, the start up script is directly run on the pre existing instance before running the benchmarking test.
Made the key pair name independent of the region in the case of when a user wants to benchmark on a pre existing instance. If a user has already configured a key pair that does not contain the region name, they would face an error because the orchestrator always appends the region to the key pair name (even in the case of byo instance). Now that is handled.
This is handled with a bring your own instance test on a g5.24xl for llama3.1 8b instruct.