Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS EC2 Container Service support #1317

Merged
merged 1 commit into from
Oct 22, 2015
Merged

AWS EC2 Container Service support #1317

merged 1 commit into from
Oct 22, 2015

Conversation

jfeala
Copy link
Contributor

@jfeala jfeala commented Oct 17, 2015

From the AWS website,

Amazon EC2 Container Service (ECS) is a highly scalable, high performance
container management service that supports Docker containers and allows you
to easily run applications on a managed cluster of Amazon EC2 instances.

To use ECS, you create a "task definition" JSON that defines the docker run command for one or more containers in a task or service, and then submit this JSON to the API to run the task.

This wrapper allows you to create Luigi Tasks to submit ECS tasks. You can either pass a dict (mapping directly to the taskDefinition JSON) or an Amazon Resource Name (arn) for a previously registered taskDefinition.

Testing was performed on the default cluster created through the ECS console first run wizard

Requires boto3, configured with valid AWS credentials

@jfeala
Copy link
Contributor Author

jfeala commented Oct 18, 2015

ah ok, just realized master is failing too. Will rebase and try again once that's fixed up


Requires:
* boto3 package
* Amazon AWS credentials discoverable by boto3 (e.g., by using `aws configure`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you checked that the docs render properly? You can use tox to generate docs too: https://github.com/spotify/luigi/blob/master/CONTRIBUTING.rst#writing-documentation

@Tarrasch
Copy link
Contributor

Tests and docs included. Awesome! Can you just amend and rebase and fix the minor issues I pointed out?

From the AWS website,

> Amazon EC2 Container Service (ECS) is a highly scalable, high
performance
> container management service that supports Docker containers and
allows you
> to easily run applications on a managed cluster of Amazon EC2
instances.

To use ECS, you create a "task definition" JSON that defines the
`docker run`
command for one or more containers in a task or service, and then
submit this
JSON to the API to run the task.

This wrapper allows you to create Luigi Tasks to submit ECS
`taskDefinition`s.
You can either pass a dict (mapping directly to the `taskDefinition`
JSON) or an
Amazon Resource Name (arn) for a previously registered `taskDefinition`.

Testing was performed on the default cluster created through the ECS
console
[first run wizard](https://console.aws.amazon.com/ecs/home#/firstRun)

Requires boto3, configured with valid AWS credentials
@jfeala
Copy link
Contributor Author

jfeala commented Oct 19, 2015

thanks for the advice, docs are reformatted from markdown to reStructuredText and look much better now. Rebased, tox passes locally. Should be all set.

@Tarrasch
Copy link
Contributor

Thanks!! :)

@Tarrasch
Copy link
Contributor

I don't see how this can harm the 2.0 release. So merging.

Tarrasch added a commit that referenced this pull request Oct 22, 2015
AWS EC2 Container Service support
@Tarrasch Tarrasch merged commit cee1169 into spotify:master Oct 22, 2015
@jfeala
Copy link
Contributor Author

jfeala commented Oct 22, 2015

cool, thanks! Glad to have made it into 2.0!

On Thu, Oct 22, 2015 at 9:20 AM, Arash Rouhani notifications@github.com
wrote:

I don't see how this can harm the 2.0 release. So merging.


Reply to this email directly or view it on GitHub
#1317 (comment).

Jacob Feala, PhD
Scientific Investigator II, Bioinformatics
H3 Biomedicine
300 Technology Square
Cambridge, MA 02139
(mobile) 858-366-2951
Jacob_Feala@H3Biomedicine.com

[This e-mail message may contain privileged, confidential and/or
proprietary information of H3 Biomedicine. If you believe that it has been
sent to you in error, please contact the sender immediately and delete the
message including any attachments, without copying, using, or distributing
any of the information contained therein. This e-mail message should not be
interpreted to include a digital or electronic signature that can be used
to authenticate an agreement, contract or other legal document, nor to
reflect an intention to be bound to any legally-binding agreement or
contract.]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants