ibm-mas / ansible-devops

Ansible collection supporting devops for IBM Maximo Application Suite
https://ibm-mas.github.io/ansible-devops/
Eclipse Public License 2.0
49 stars 89 forks source link

Add Openshift mesh support to the collection #220

Open robbinmav opened 2 years ago

robbinmav commented 2 years ago

please add an option so administrators can request that openshift service mesh support is added. I understand that this would logically be related to the ocp_setup_mas_deps role.

It would need MAS specific documentation explaining: how to configure it how to interpret/visualise its results e.g. tracing a couple of common activities - logging in / performing some action in the Manage front-end / integration operation

As an administrator my preference would be this to be installed by default. My experience is that customers management teams are very nervous about installing a tool unless IBM have installed it. Installing it by default would mean that support teams could get the benefit of the tool without having to fight to get it installed.

Adding in this functionality would make it easier for support staff (IBM and customer/BPs) to understand where requests are being routed and where they could be failing.

Benefits of implementing this: Quicker fault investigations because path of service requests are easier to see Development able to focus on feature development rather than explaining how the requests were being routed

whitfiea commented 2 years ago

Installing service mesh on its own won't provide any benefit as no namespaces/deployments in MAS have been setup/tested to support servicemesh (istio). From reading the details on servicemesh it seems that when you add a namespace to the member roll, access to the serivces/pods in the namespace are not accessible to callers outside the service mesh (https://docs.openshift.com/container-platform/4.8/service_mesh/v2x/ossm-create-mesh.html). This would mean further work is needed to ensure that new apps that are created are added to the mesh and that all the deployments would need to be updated to add the annotation to create the require sidecar aswell.

Until MAS and each App in MAS has tested with a sidecar and being part of the servicemesh then I don't see any benefit to installing just OpenShift service mesh as part of ocp_setup_mas_deps, unless you have seen some benefit in this already @robbinmav ?

robbinmav commented 2 years ago

Hi. This was raised after a discussion with an IBMer.

I raised it because support staff need to be able to identify the flow of requests as the components handle individual requests. Currently it is very hard to identify which components are involved in handling a request

whitfiea commented 2 years ago

@robbinmav I have been checking on this within the MAS dev team and currently there are technical blockers that stop the enablement of the istio sidecars which are needed to enable service mesh for MAS. There is a desire to resolve this and get service mesh working but as yet no targeted date for that. Until MAS supports the use of service mesh then we can't add this support into mas_devops ansible collection.

I will leave this issue here for now and come back to it when support is declared by MAS for servicemesh.