Skip to content
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.

spec pods: Clarify empty volume kind #449

Merged
merged 1 commit into from
Jul 8, 2015
Merged

spec pods: Clarify empty volume kind #449

merged 1 commit into from
Jul 8, 2015

Conversation

kibra
Copy link
Contributor

@kibra kibra commented Jun 18, 2015

The spec for the "empty" volume kind is unclear. See #183 for the issue/discussion around this.

Note: My change proposes the rather strong spec of: lifetime of the empty volume == lifetime of the pod
I feel that this makes the use case of "empty" more clear than specifying lifetime of the empty volume >= lifetime of the pod as was suggested in #183 (comment) However, I don't have a strong opinion around this, and would be happy to change what I wrote.

@kibra
Copy link
Contributor Author

kibra commented Jun 18, 2015

This clarification is needed to unblock some rkt work: rkt/rkt#1040

@mpasternacki
Copy link
Contributor

👍 Question of a volume lifetime seems to be dependent on #276 (define "pod exits"), so I'd say it's out of scope now.

@jonboulle
Copy link
Contributor

LGTM. @thockin ?

@jonboulle
Copy link
Contributor

@kibra can you rewrite your commit message please - Clearify --> Clarify

@kibra
Copy link
Contributor Author

kibra commented Jun 20, 2015

@jonboulle Fixed, thanks for the catch.

@jonboulle jonboulle changed the title spec pods: Clearify empty volume kind spec pods: Clarify empty volume kind Jun 22, 2015
@kibra
Copy link
Contributor Author

kibra commented Jul 7, 2015

@jonboulle Ping. I'm not super happy with my language here, but I think it's a least a step forward. Let me know if there's something you think I should change.

* **kind** (string, required) either "empty" or "host". "empty" fulfills a mount point by ensuring the path exists (i.e., writes go to the app's chroot). "host" fulfills a mount point with a bind mount from a **source**.
* **readOnly** (boolean, optional, defaults to "false" if unsupplied) whether or not the volume will be mounted read only.
* **kind** (string, required) either:
* **empty** - creates an empty directory on the host and bind mounts it into the container. All containers in the pod share the mount, and the lifetime of the volume is equal to the lifetime of the pod (i.e. the directory on the host machine is removed when the pod exits)
Copy link
Contributor

Choose a reason for hiding this comment

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

(i.e. the directory on the host machine is removed when the pod exits)

This makes me a little uneasy. How about "the directory on the host machine is removed when the pod's filesystem is garbage collected"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jonboulle Agreed. That makes much more sense.

@jonboulle
Copy link
Contributor

@kibra One more tweak then LGTM

@kibra
Copy link
Contributor Author

kibra commented Jul 8, 2015

@jonboulle Thanks for the feed back. I've updated my PR.

@jonboulle
Copy link
Contributor

thanks!

jonboulle added a commit that referenced this pull request Jul 8, 2015
spec pods: Clarify empty volume kind
@jonboulle jonboulle merged commit 806b17c into appc:master Jul 8, 2015
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants