projectatomic / atomicapp

[UNMAINTAINED] This is the reference implementation of the Nulecule container application Specification: Atomic App
102 stars 70 forks source link

AWS provider #95

Open goern opened 10 years ago

goern commented 10 years ago

As a deployment guy I want to use an AWS provider so that my docker containers get startet on AWS (either using kube on AWS or some native AWS)

goern commented 10 years ago

see also https://github.com/openshift/origin/issues/2406

aweiteka commented 9 years ago

@goern do we want to pull this in to the CDK GA milestone or push it out?

vpavlin commented 9 years ago

I'd like to raise the priority of this as I got couple of requests for AWS provider at LinuxCon and at Docker Meetup.

adimania commented 9 years ago

Hi Guys, Any updates here? I would love to use this in a production like environment at the moment. @dustymabe @cdrage @kadel @bexelbie

cdrage commented 9 years ago

Errrrrr...

To be honest here I have no idea what this particularly means. Are you saying you want to control an AWS ec2 vps with atomicapp? It would be as simple as pointing your docker-config to that machine (ex. using docker-machine), correct me if I'm wrong.

If we're talking about full-on AWS integration with atomicapp this may be outside the scope of the spec / would need adjustments to it.

@aweiteka @goern @vpavlin

could any of you clarify on this issue?

adimania commented 9 years ago

Hi @cdrage,

I am looking for a provider for Amazon EC2 container service, to manage containers, not vps.

cdrage commented 9 years ago

Okay, I think this may be outside the scope of atomicapp imo..

If there's a library or something to communicate to the amazon ec2 api service I guess we can implement it, but that'll be another dependency.

Another issue is maintainability as well as the future of adding google's service as well.

can you open up an issue against the nulecule spec outlining what you'd like to have implemented in detail? @adimania

rtnpro commented 9 years ago

On Feb 4, 2016 2:19 AM, "Charlie Drage" notifications@github.com wrote:

Okay, I think this may be outside the scope of atomicapp imo..

If there's a library or something to communicate to the amazon ec2 api service I guess we can implement it, but that'll be another dependency.

From a community standpoint, I see a value addition with the AWS container provider. Not everyone use Openshift or Kubernetes.

adimania commented 9 years ago

there is a python api and it is packaged for Fedora and Epel (https://admin.fedoraproject.org/pkgdb/package/rpms/python-boto/). So from dependency standpoint, I think it should not be a big problem. AWS ECS provides services similar to kubernetes where you can write in the config files for components (they call it cluster, services and tasks). I think it should align with the scope of atomicapp closely, and I am willing to help with the concepts and explanations on components. However, if you feel that it does not align with atomicapp goals, please feel free to decline.

cdrage commented 9 years ago

If anyone wants to take the helm for this addition so be it :)

Just thinking about it again, but it would be cool to be able to talk to Amazon / Google 's container platforms. Via atomicapp in order to do all the deployment and such of each containerized Nulecule app.

I'm assuming the best one for Google would be google-api-python-client.