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

Design for AWS IaaS targeting #3

Closed
joeduffy opened this issue Nov 3, 2016 · 3 comments
Closed

Design for AWS IaaS targeting #3

joeduffy opened this issue Nov 3, 2016 · 3 comments
Labels
area/tooling impact/breaking Fixing this issue will require a breaking change
Milestone

Comments

@joeduffy
Copy link
Member

joeduffy commented Nov 3, 2016

We need a design for how to target AWS as the cloud provider and ECS as the scheduler.

@joeduffy joeduffy added area/tooling impact/breaking Fixing this issue will require a breaking change labels Nov 3, 2016
@joeduffy
Copy link
Member Author

joeduffy commented Nov 23, 2016

There is a start of this at AWS and ECS. There are still many open questions, however, particularly how the primitive Mu stack types project onto the target abstractions.

@joeduffy joeduffy modified the milestones: MU0, S9 Jan 8, 2017
@joeduffy
Copy link
Member Author

Most of this has evaporated, given our decision to expose elements in their raw form. I am tempted to close this out, however surely we will face some of the unanswered questions in the above-linked documents as we bring up the V0.9 and V1.0 systems. So I will keep this open for now.

Note that most of the above open issues are now part of the higher-level layers. For example, when we ever had the notion of a "cluster" or "VM" or something that is more abstract than just provisioning resources in their raw form. These used to be part of the mu namespace itself, however now these have become part of the cross-cloud mu/x package.

@joeduffy
Copy link
Member Author

As described above, this is obsolete. (Or, specifically, we've changed how we are approaching this problem.) I'm closing this out in favor of #78.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tooling impact/breaking Fixing this issue will require a breaking change
Projects
None yet
Development

No branches or pull requests

1 participant