-
Notifications
You must be signed in to change notification settings - Fork 77
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
RFD 26: discussion #56
Comments
That should be Also the affinity section mentions "~=" as an operator. This should instead
FWIW there is the questionably useful:
Update to mdata-dict docs for this? (http://eng.joyent.com/mdata/datadict.html)
Has there been any testing how some example NFS clients (smartos, lx, docker) Is there an operator guide plan for volumes? Seems like one might be useful
Perhaps s/labels/tags?
Was there a mention that one cannot alter what volumes are attached to an
FWIW, that reduces the upper limit on the length of the given volume name
It wasn't clear to me: This involves adding a 'type' field to packages?
How does an inactive VM because active again? My understanding of "inactive"
Thoughts on not returning deleted/failed vols by default in ListVolumes? My main argument for limiting the default query is to reduce large accidental |
Done.
Done.
I think the intention with
Sounds good, see https://smartos.org/bugview/TRITON-10. I wonder though how discoverable this doc is. I always forget it's there.
Programs performing operations on the remote FS hosted by the given CN would retry indefinitely and hang until the remote FS is back up. We didn't perform any extensive testing for this though, so I'll see if there are some tests we might have missed and we should perform sooner rather than later.
There's no such guide for now.
Yes, see https://smartos.org/bugview/TRITON-11. I did not open a DOC ticket because I couldn't find a "component" that seemed to be relevant.
Sure, the "labels" terminology comes from docker, I'm good with tags if this is more consistent with Triton. Can you confirm that?
That's a good point, created https://smartos.org/bugview/VOLAPI-82.
No, it introduces a separate class of packages called "volume packages", which have a
Inactive is anything that is not
That was actually a mistake, I hadn't updated this part of the RFD. We don't store We could list only "active" volumes by default, that is volumes in state |
Yah, it isn't. It might be linked to in some of our docs, but I'm not sure. jclulow has identified that it does need to find a better home.
https://apidocs.joyent.com/cloudapi/#ListMachineTags
I think that might cause fewer surprises to users. E.g. "failed" ones are more likely to surprise client code written to handle the more common active volumes. Listing "failed" ones is, I would think, a less common action. Not like our APIs don't have pitfalls bigger than this tho. :) |
Just for the record, we agreed we didn't want to make work, and so this won't be changed before integration to master. |
This RFD has been published and while additional feedback is welcome, this discussion issue is being closed. All changes necessary to implement the first milestone described in this RFD ("master-integration") have been integrated into the |
This issue represents an opportunity for discussion of RFD 26 Network Shared Storage for Triton.
The RFD has gone through a lot of iterations already, and has been in progress for a long time. However, I think now is the time for a final round of review and feedback before the current prototype is integrated into the master branches of the relevant code repositories.
The text was updated successfully, but these errors were encountered: