greetings everyone.
I've been playing around with openshift staging for the last few weeks and enabling some cool features. :) However, I now seem to have gotten it in a odd state and I think it's time to do a fresh install.
If no one objects soon, I will reinstall it this afternoon, then run all the various app playbooks to redeploy them.
Hopefully after that we will have multitenant networking (all apps are isolated from each other unless we want to allow them to talk), metrics/logging/alerting (with all the cool apps: kibana/elasticsearch/prometheus/fluentd/etc).
If all looks well with this, we can roll this out to prod after beta (probibly by doing a reinstall there as well).
kevin
I've been playing around with openshift staging for the last few weeks and enabling some cool features. :)
Cool! I seem to remember that having persistent storage in our Openshift instance was a difficult thing. I'm considering Openshift to setup a PyPI caching proxy for us, and that will require some disk space. Is this still an issue?
A.
On 09/11/2018 09:26 AM, Aurelien Bompard wrote:
I've been playing around with openshift staging for the last few weeks and enabling some cool features. :)
Cool! I seem to remember that having persistent storage in our Openshift instance was a difficult thing. I'm considering Openshift to setup a PyPI caching proxy for us, and that will require some disk space. Is this still an issue?
Well, sorta yeah. We do have it to where we can use nfs volumes for the registery (because they required storage for that), but it's not really a good solution for everything as it's very manual.
Could this caching proxy just use EmpyDir (ie, only for the life of that pod) and just refresh when it restarts? If it really needs disk, might be better to do on a vm at this point.
Hopefully we can get to where our persistent storage story is better down the road...
kevin
Could this caching proxy just use EmpyDir (ie, only for the life of that pod) and just refresh when it restarts? If it really needs disk, might be better to do on a vm at this point.
Since it's just caching, I guess that would be sufficient, unless we cycle the pod frequently. It would be Really Bad Luck if the pod and PyPI went down at the same time, right?
A.
On 09/12/2018 12:31 AM, Aurelien Bompard wrote:
Could this caching proxy just use EmpyDir (ie, only for the life of that pod) and just refresh when it restarts? If it really needs disk, might be better to do on a vm at this point.
Since it's just caching, I guess that would be sufficient, unless we cycle the pod frequently. It would be Really Bad Luck if the pod and PyPI went down at the same time, right?
Indeed. Another possible option to look at is that openshift can also save the last artifacts and reuse them if you are doing a layered s2i image. That of course doesn't help for new items if pypi was down or something, but it would at least mean fetching the things that didn't change would be fast.
kevin
infrastructure@lists.fedoraproject.org