forked from vmware/vic
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Portlayer images use standard Join pattern (vmware#7397)
This brings consistent organisation and naming of files to the storage portlayer and moves Image to use the standard Join/Bind semantic. Previously container images were injected into the cVM spec inline in the exec component of the portlayer. This was tech debt from the very early days of the project before the Join/Bind semantic was fully established. This also moves and renames files to make it easier to locate specific portions of code, both within a single implementation and across implementations (implementations are currently nfs and vsphere). This adds package documentation to provide developers with some introduction and guidance at a high level. It does not detail many of the lower level packages. There are some additional structure naming changes that could be made for consistency, and some leaking abstractions (e.g. exposing volume type to handlers) that should eventually be addressed. This is merge without those as it is a significant improvement over current state of affairs and may simplify some outstanding work.
- Loading branch information
Showing
63 changed files
with
1,828 additions
and
1,252 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.