Hi Veselin,
Yes to be clear, this is what we do as well. We label our gluster nodes as
‘storage’ or ‘glusterfs’ nodes and set
openshift_storage_glusterfs_nodeselector: to reflect that in the OSEv3.
Thanks,
Todd
Today's Topics:
2. Re: Container Ready/Native storage for OpenShift 3.9
(Rodrigo Bersa)
Message: 2
Date: Thu, 17 May 2018 09:18:04 -0300
From: Rodrigo Bersa <[email protected]>
To: Veselin Hristov <[email protected]>
Cc: users <[email protected]>, "Walters,Todd"
<[email protected]>
Subject: Re: Container Ready/Native storage for OpenShift 3.9
Message-ID:
<calgwpfea3wop3qibzqlkpnmm05b9odrz27aasbbhatwkwh5...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Veselin,
I don't think that allow applications to run on StorageNodes is a good
practice, so the resources on this machines can be exclusive for Gluster.
I would use a different label to avoid applications to run on StorageNode
instead of using schedulable=false.
Regards,
Rodrigo Bersa
Cloud Consultant, RHCVA, RHCE
########################################################################
The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM
########################################################################
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
