I ended up finding this https://github.com/openshift/openshift-ansible-contrib/blob/master/reference-architecture/aws-ansible/playbooks/roles/openshift-volume-quota/tasks/main.yaml which was a good pointer.
Putting gquota on the atomicos-root never seems to apply. On Wed, 28 Sep 2016 at 16:14 Andrew Lau <and...@andrewklau.com> wrote: > lol - thanks > > Is `/mnt/openshift-xfs-vol-dir` a predefined mount or something? I'm not > seeing this anywhere in the docs either > > > On Wed, 28 Sep 2016 at 11:49 Clayton Coleman <ccole...@redhat.com> wrote: > >> If you can prevent your eyes from bleeding through sheer strength of will >> - gaze upon the setup code here: >> >> >> https://github.com/openshift/vagrant-openshift/blob/master/lib/vagrant-openshift/action/install_origin_base_dependencies.rb#L262 >> >> I thought there was doc for this but I'm not seeing it in my quick >> searches. >> >> On Sep 27, 2016, at 9:12 PM, Andrew Lau <and...@andrewklau.com> wrote: >> >> I noticed support for emptyDir volume quota was added in 1.3, is there >> any documentation on how we can enable this on atomic hosts? Setting gquota >> in /etc/fstab doesn't apply. >> >> "Preliminary support for local emptyDir volume quotas, set this value to >> a resource quantity representing the desired quota per FSGroup, per node. >> (i.e. 1Gi, 512Mi, etc) Currently requires that the volumeDirectory be on an >> XFS filesystem mounted with the 'gquota' option, and the matching security >> context contraint’s fsGroup type set to 'MustRunAs'." >> >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >>
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
