Share usage guide #675
Share usage guide #675
Conversation
imran-ansari
commented
Jul 8, 2019
imran-ansari
commented
- Added share usage guide
- Linked it to the entry point README.md
* Added share usage guide * Linked it to the entry point README.md
|
@prablr79 , @amitk1977 , @wdurairaj , @nilangekarss , shashi, @sandesh-desai , @virendra-sharma - Please review the changes |
Also added links to individual command usage list
docs/share_usage.md
Outdated
| EOF | ||
| ``` | ||
|
|
||
| At this point, after creating the **SC** and **PVC** definitions, the volume hasn’t been created yet. The actual volume gets created on-the-fly during the pod deployment and volume mount phase. |
There was a problem hiding this comment.
IN DYNAMIC PROVISIONING Volume dets created after PVC creation. In case of shares, user needs to wait until inspect on the share shows the AVAILABLE status after this user can create a POD.
There was a problem hiding this comment.
@imran-ansari IN DYNAMIC PROVISIONING Volume dets created after PVC creation. In case of shares, user needs to wait until inspect on the share shows the AVAILABLE status after this user can create a POD.
There was a problem hiding this comment.
@imran-ansari IN DYNAMIC PROVISIONING Volume dets created after PVC creation.
This text has been borrowed from volume usage page - check this out That would also need correction.
There was a problem hiding this comment.
@imran-ansari i Agree this should also get changed in volume examples
docs/share_usage.md
Outdated
| capacity: | ||
| storage: 10Gi | ||
| accessModes: | ||
| - ReadWriteOnce |
There was a problem hiding this comment.
Change this to ReadWriteMany
docs/share_usage.md
Outdated
| name: pvc-first | ||
| spec: | ||
| accessModes: | ||
| - ReadWriteOnce |
There was a problem hiding this comment.
Change this to ReadWriteMany
| @@ -1,6 +1,7 @@ | |||
| ## HPE 3PAR Volume Plugin for Docker | |||
|
|
|||
| HPE Docker Volume Plugin is an open source project that provides persistent storage and features for your containerized applications using HPE 3PAR StoreServ Storage arrays. | |||
| It supports both block and file (NFS shares) based features. | |||
|
|
|||
There was a problem hiding this comment.
@imran-ansari Can you please add issue #683 and #688 as a Limitations. And trouble shooting for 683.
|
|
||
| ```yaml | ||
| $ sudo kubectl create -f - << EOF | ||
| --- |
There was a problem hiding this comment.
Actually the correct POD definition after some analysis is this
kind: Pod
apiVersion: v1
metadata:
name: podfiletestw4-uid-gid-nosecurity
spec:
containers:
- name: nginx
securityContext:
privileged: true
capabilities:
add: ["SYS_ADMIN"]
allowPrivilegeEscalation: true
image: nginx
volumeMounts:
- name: export
mountPath: /export
restartPolicy: Always
volumes:
- name: export
persistentVolumeClaim:
claimName: sc-file-pvc-uid-gid
There was a problem hiding this comment.
need to merge POD def in the file
There was a problem hiding this comment.
PR updated accordingly. @wdurairaj - please check. I've updated security-context both in static as well dynamic provisioning sections.
|
@imran-ansari i hope you have update the review comments, can i merge this ? |
| when used in file driver configuration, it is ignored. | ||
| 3. When two backend sections are identically defined, even then each backend | ||
| is treated differently and results in having their individual default FPGs | ||
| when default share creation is done using both the backends. |
There was a problem hiding this comment.
@imran-ansari I think we should add below limitations as well. Or can pick the necessary limitations of these:
- While working in K8S environment it is recommended to use below steps:
If working with dynamic provisioner-
After creating SC and PVC it is recommended to inspect the share to check the status of the share creation.
It is recommended to create a POD only after inspect of share shows status as AVAILABLE. If the user tries to create a POD
before inspect of share staus becomes AVAILABLE, user will see error messages in logs indicating share is in CREATING state.
POD describe may show warning messages indicating Mount has failed as share is still in creating state.
If working with Static provisioner-
After creation of PV and PVC actula share doesnt get created at 3PAR. When user creates POD, dory invokes create share and later
it invokes mount share commands. Hence user may experiece few minutes of delay for getting POD in running state.
User may also see multiple error messages indication "mount for share is failed as share is still in creating state".
This is because once the PVC status becomes BOUND dory tries to create pod continuously.
-
There can be maximum of 256 shares which can be created using docker volume plugin. This is because,
share is internally mapped to docker volume. There is a 3PAR limit on number of FPGs per node pair (16 FPGs).
Each FPG can have max 16 stores. There is 1:1 mapping mentained for store and share. -
Even though 3PAR vfs can have max 4 IPs associated with it, docker user can have max 1 IP associated with VFS.
There was a problem hiding this comment.
PR updated accordingly. Please check.
