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] Add support for EC2 #14

Open
wants to merge 18 commits into
base: master
Choose a base branch
from
Open

Conversation

danhunsaker
Copy link
Contributor

Plus a plethora of new features for everyone!

danhunsaker and others added 18 commits August 6, 2018 22:12
Completed:
- `meta` controller (integration tests)
- `keys` controller (integration tests)

TODO:
- `servers` controller (integration tests)
- all adapters (unit tests)
- all tasks (unit tests)
- `models` utility (unit tests)
- `output` utility (unit tests)
Disable testing `azure` Classic, as it appears to fnally be phasing out, properly, on Microsoft's side. The adapter itself will be fully removed at a later date.
Completed:
- `meta` controller (integration tests)
- `keys` controller (integration tests)
- `servers` controller (integration tests)
- `models` utility (unit tests)
- `output` utility (unit tests)

TODO:
- all adapters (unit tests)
- all tasks (unit tests)
Wanted to test even the base adapter, mostly to cut down on the sheer amount of stuff being tested in each adapter's own implementation. If it works in the base, and we don't override it in the provider-specific, then we shouldn't have to test it again there.
Ensure we're still doing things the same way in the new adapter that we were in the old one. This is in preparation for layering in new features for the adapter, and from there, doing similar for other adapters as well.
Libcloud doesn't provide this info, so we have to grab it directly ourselves, still. So we'll also cache the results for 24 hours, to keep things nice and fast.
- Add support for specifying a VPC ID, and Availability Zone distribution, via custom configuration values passed during server creation.
- Find or create resources needed to properly set up servers as required for Nanobox.
- Create and honor `Nanobox: {boolean}` tags. `true` means "prefer this resource", while `false` means "this resource is unavailable".
Assume PV if the generation isn't known.
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.

2 participants