Hi everyone,
the-new-hotness [0] was recently moved to OpenShift 4 cluster [1] on staging. One of the latest commits added support for Redis as cache to the-new-hotness and according to the Redis documentation there is an OpenShift 4 operator for Redis [2].
The question is: Do we want to use operators or just write the deployment by yourself in ansible? Or it is possible to convert the Redis deployment made by operator to ansible?
I would prefer to have everything in the ansible in case we need to start with fresh OpenShift project.
What do you think?
Michal
[0] - https://github.com/fedora-infra/the-new-hotness [1] - https://console-openshift-console.apps.ocp.stg.fedoraproject.org/ [2] - https://docs.redis.com/latest/kubernetes/deployment/openshift/openshift-oper...
You could develop re-usable ansible roles that would fit both scenarios.
An ansible operator can load external roles as any ansible project.
On Thu, May 19, 2022 at 2:37 PM Michal Konecny mkonecny@redhat.com wrote:
Hi everyone,
the-new-hotness [0] was recently moved to OpenShift 4 cluster [1] on staging. One of the latest commits added support for Redis as cache to the-new-hotness and according to the Redis documentation there is an OpenShift 4 operator for Redis [2].
The question is: Do we want to use operators or just write the deployment by yourself in ansible? Or it is possible to convert the Redis deployment made by operator to ansible?
I would prefer to have everything in the ansible in case we need to start with fresh OpenShift project.
What do you think?
Michal
[0] - https://github.com/fedora-infra/the-new-hotness [1] - https://console-openshift-console.apps.ocp.stg.fedoraproject.org/ [2] -
https://docs.redis.com/latest/kubernetes/deployment/openshift/openshift-oper... _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Thu, May 19, 2022 at 02:45:03PM -0300, Leonardo Rossetti wrote:
You could develop re-usable ansible roles that would fit both scenarios.
An ansible operator can load external roles as any ansible project.
Yeah... take a look at the oraculum app in ansible. They are using redis there, should be able to re-use that, or perhaps we could even abstract it out.
kevin --
On Thu, May 19, 2022 at 2:37 PM Michal Konecny mkonecny@redhat.com wrote:
Hi everyone,
the-new-hotness [0] was recently moved to OpenShift 4 cluster [1] on staging. One of the latest commits added support for Redis as cache to the-new-hotness and according to the Redis documentation there is an OpenShift 4 operator for Redis [2].
The question is: Do we want to use operators or just write the deployment by yourself in ansible? Or it is possible to convert the Redis deployment made by operator to ansible?
I would prefer to have everything in the ansible in case we need to start with fresh OpenShift project.
What do you think?
Michal
[0] - https://github.com/fedora-infra/the-new-hotness [1] - https://console-openshift-console.apps.ocp.stg.fedoraproject.org/ [2] -
https://docs.redis.com/latest/kubernetes/deployment/openshift/openshift-oper... _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
--
Leonardo Rossetti
Senior Software Engineer,
Red Hat https://www.redhat.com
lrossett@redhat.com https://www.redhat.com
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
infrastructure@lists.fedoraproject.org