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

Machine API related house keeping #3612

Closed
6 tasks done
gazarenkov opened this issue Jan 5, 2017 · 4 comments
Closed
6 tasks done

Machine API related house keeping #3612

gazarenkov opened this issue Jan 5, 2017 · 4 comments
Assignees
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.

Comments

@gazarenkov
Copy link
Contributor

gazarenkov commented Jan 5, 2017

It is umbrella epic to cover cleaning all the machine API related things.

The problem is that as a result of evolution of our vision many abstractions, classes, UI components and even API(s) now looks odd.
It is a quite big pile of code which we do not effectively use but have to support, test and package.
But the even bigger problem is that such a code makes a big deal of confusing for community developers who is not familiar with the history.

@gazarenkov gazarenkov added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Jan 5, 2017
@gazarenkov gazarenkov self-assigned this Jan 5, 2017
@vazexqi
Copy link
Contributor

vazexqi commented Jan 6, 2017

Could you clarify on what "remove machine API since it is not used anymore" means?

Based on an earlier comment at #2847 (comment)
it seems that the Machine API can be used to create machines that are not just docker-based. Are you removing this feature and making an assumption that all machines in the future will be docker-based?

@TylerJewell
Copy link

no no - definitely keeping the ability to swap out docker runtimes for other runtimes. We depend upon that in a number of ways. I think it was just a language thing in his explanation of how the API will be refactored.

@vazexqi
Copy link
Contributor

vazexqi commented Jan 6, 2017

Thanks for the clarification @TylerJewell.

@TylerJewell
Copy link

BTW - the 5.0.0 release has been made, though we have a lot of cleanup stuff around docs and other areas before we ship it. So you are seeing a lot of housekeeping issues being created as we are taking the next couple months to focus on performance, code cleanup, and other things to make the project easier to manage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
Projects
None yet
Development

No branches or pull requests

4 participants