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

feature: volume and mount propagation for cri manager #717

Merged
merged 1 commit into from
Feb 9, 2018

Conversation

YaoZengzeng
Copy link
Contributor

Signed-off-by: YaoZengzeng [email protected]

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

fixes part of #635

Ⅲ. Describe how you did it

Ⅳ. Describe how to verify it

It has already passed the corresponding tests in cri-tools.

Ⅴ. Special notes for reviews

@codecov-io
Copy link

Codecov Report

Merging #717 into master will decrease coverage by 0.06%.
The diff coverage is 0%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #717      +/-   ##
==========================================
- Coverage    10.9%   10.84%   -0.07%     
==========================================
  Files          93       93              
  Lines        5482     5513      +31     
==========================================
  Hits          598      598              
- Misses       4836     4867      +31     
  Partials       48       48
Impacted Files Coverage Δ
daemon/mgr/container.go 3.47% <0%> (-0.06%) ⬇️
daemon/mgr/cri_utils.go 40.95% <0%> (-2.63%) ⬇️
daemon/mgr/spec_volume.go 0% <0%> (ø) ⬆️
daemon/mgr/cri.go 0% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70f33bf...04e9bc9. Read the comment docs.

@@ -829,6 +830,16 @@ func (mgr *ContainerManager) parseVolumes(ctx context.Context, c *types.Containe
}

source = mountPath
} else {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

func parseVolumes is not so good, and there are so much improvement we could do for it.

@allencloud
Copy link
Collaborator

Could we add a test case in integration test for this case?
I think it is not so hard for us to add and it is quite easy to test. @YaoZengzeng

@allencloud
Copy link
Collaborator

LGTM

@pouchrobot pouchrobot added the LGTM one maintainer or community participant agrees to merge the pull reuqest. label Feb 9, 2018
@allencloud allencloud merged commit 4eb0189 into AliyunContainerService:master Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
areas/storage kind/feature LGTM one maintainer or community participant agrees to merge the pull reuqest. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants