search for: mountpath

...don''t mind if I have to rewrite my code or start from scratch, but I need help to create my mountpoint location with root:root/755 and after mounting allow the same location to have a different owner:group/ permissions. These are the defines I use at this moment define lvm::createfs ( $mountpath = undef, $mountpoint = undef, $lvsize = undef, $fstype = undef, $vgname = undef, $lvname = "${name}", $requisite = '''' ) { # Load defaults require lvm::params # Check mountpath equals root $rootpath = $mountpath ? { ''/'' =&...

...e thing i would like to highlight is that all the three containers are using the *same* PVC - name: gluster-vol1 persistentVolumeClaim: claimName: gluster-dyn-pvc Above is common for all three. What differs is shown below: a) postgresql-deployment.yaml volumeMounts: - name: gluster-vol1 mountPath: /var/lib/postgresql b) redisio-deployment.yaml volumeMounts: - name: gluster-vol1 mountPath: /var/lib/redis c) gitlab-deployment.yaml volumeMounts: - name: gluster-vol1 mountPath: /home/git/data Any suggestion? Also, i ? guess this is not the right way to use the same PVC/Storage Class fo...

...;> - name: gluster-vol1 >> persistentVolumeClaim: >> claimName: gluster-dyn-pvc >> >> Above is common for all three. What differs is shown below: >> >> a) postgresql-deployment.yaml >> >> volumeMounts: >> - name: gluster-vol1 >> mountPath: /var/lib/postgresql >> >> b) redisio-deployment.yaml >> >> volumeMounts: >> - name: gluster-vol1 >> mountPath: /var/lib/redis >> >> c) gitlab-deployment.yaml >> >> volumeMounts: >> - name: gluster-vol1 >> mountPath: /home/...

...e containers are getting ~40G > of local storage, that's more than enough for virt-v2v to run and > store the appliance and overlays. Everything should just work once > you remove that /var/tmp mountpoint and leave it as local storage. > > ie these lines are removed: > - mountPath: /var/tmp > name: v2v-conversion-temp > > Or: > > (2) We could implement more fine-grained temporary directory control, > allowing the appliance and v2vovl* files to be placed separately. > However it would still be wrong to mount the place where libguestfs > creates...

...dts smb: \> ls ... Error in dskattr: code 0 smb: \> read_socket_with_timeout: timeout read. read error = Connection reset by peer. Broken Pipe With debugging set to 10 the server tells me: [2001/04/25 16:03:16, 5] smbd/quotas.c:disk_quotas(497) disk_quotas: looking for mountpath (NFS) "nfsserver:/export/homes6" [2001/04/25 16:03:16, 5] smbd/quotas.c:nfs_quotas(333) nfs_quotas: looking for mount on "nfsserver" [2001/04/25 16:03:16, 5] smbd/quotas.c:nfs_quotas(334) nfs_quotas: of path "nfsserver:/export/homes6" [2001/04/25 16:03:16, 5] smbd/...

...gluster.org/docs/index.php/GlusterFS_oVirt_Setup_Guide Where we fit in? 1. Libvirt No modifications for libvirt we use the same framework given by libvirt, but modify out own mount.glusterfs to handle the ways of NFS parameters. mount -t glusterfs <glusterfs-server>:<volume-name> <MOUNTPATH> 2. Ovirt Technical Details: "GlusterfsStoragePool" a new class added in support of Glusterfs for task-omatic daemon. Now with this Ovirt server can generate same task events like start_vm, migrate_vm, refresh_storage_pool etc., with glusterfs too. Glusterfs awareness were added in...

...al storage. Assuming all these containers are getting ~40G of local storage, that's more than enough for virt-v2v to run and store the appliance and overlays. Everything should just work once you remove that /var/tmp mountpoint and leave it as local storage. ie these lines are removed: - mountPath: /var/tmp name: v2v-conversion-temp Or: (2) We could implement more fine-grained temporary directory control, allowing the appliance and v2vovl* files to be placed separately. However it would still be wrong to mount the place where libguestfs creates the appliance (by default /var/tmp) on...

Previously we placed large files in g#get_cachedir () (usually /var/tmp). However the problem is this ties the libguestfs appliance and the virt-v2v overlay files to the same location. When virt-v2v is run in a container, or any other situation where local storage is limited, it's helpful to be able to put the overlay files on an externally mounted PVC, which might be using NFS and shared

...e containers are getting ~40G > of local storage, that's more than enough for virt-v2v to run and > store the appliance and overlays. Everything should just work once > you remove that /var/tmp mountpoint and leave it as local storage. > > ie these lines are removed: > - mountPath: /var/tmp > name: v2v-conversion-temp > > Or: > > (2) We could implement more fine-grained temporary directory control, > allowing the appliance and v2vovl* files to be placed separately. > However it would still be wrong to mount the place where libguestfs > creates...