John Strunk

Milestones have been created across the repos listed above. AIs to repo owners to ensure issues are tagged properly: - @amarts glusterfs - @atinmu glusterd2 - @JohnStrunk anthill, csi -...

Following up on my AI from today's meeting, I have moved everything that was in the alpha1 & beta0 milestones to the following labels: GCS/alpha1, GCS/beta0. I have not assigned...

> I tried to test this out. Centos-atomic does not have `socat` available which is required for Helm to work, and centos-atomic doesn't provide an easy way to get it...

With #69 merged, Helm should now work, so this approach is now viable. However, this PR is significantly out of date wrt how we are currently deploying GCS components.

Today this is very manual. We will be working to automate it in the future.

Also related is the operator work on adding persistence: https://github.com/coreos/etcd-operator/issues/1323. I'm trying to figure out the status. WRT using embedded... I don't know that this is going to make it...

> I propose the plan of doing gluster-block CSI like gluster/gluster-csi-driver#10 (comment) I think it is reasonable to have (all) the provisioning handled by the CSI block driver. I'm still...

> Why the requirement to separate the gluster and gluster-block containers at this stage? The gluster server pods are no longer a DaemonSet and no longer use the host network....

gd2 pods don't use host networking anymore. If they get packaged together, g-b would also not be using host network. Will it work in such an environment?

If the components are "things we would deploy as a part of gcs" (i.e., they would be deployed if and only if GCS is deployed), they should be in the...