jgreenemi/Parris

Add support for AWS Spot Instances/other options besides On-Demand instances.

Open

#7 opened on Jan 2, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (320 stars) (22 forks)batch import
enhancementhelp wanted

Description

The tool is set to launch servers in the On-Demand way, meaning this is the most expensive way to go about it. This should be changed such that users can introduce the use of Spot instances to save on costs, or even take advantage of Reserved Instances if they have RI capacity already set aside. I'm unfamiliar how the latter works when used with CFN stacks, so this will require additional research.

Contributor guide

Tech stack
pythonaws
Domain
cloudinfrastructuredevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
AWS EC2 pricingCloudFormation stacksPython programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Review the existing code for launching EC2 instances, likely in a Python script that generates CloudFormation templates. Identify where instance type and purchase option are defined. For Spot Instances, modify the code to allow users to specify Spot price and allocation strategy. For Reserved Instances, research how to incorporate them into CloudFormation stacks, as this may require additional AWS API calls. The issue mentions that the tool currently only supports On Demand instances, so the goal is to add alternative purchase options.