running Teastore on Ubuntu VMs

[miwitte]

I know this was originally developed to run on docker and it does that well. I have inherited an environment where TeaStore is running as VMs using Ubuntu. The individual has left and it no longer works. This ran fine as a VM, and we had AppDynamics agents on the VMs, and we have the VMs running on Cisco ACI network switch fabric. The fabric is monitored by NEXUS Dashboard and Nexus Insights, and we pull Application performance data from TeaStore into AppDynamics and then correlate the NEXUS Insights database to get a holistic application and network view. I cannot find any instruction on how to port this over to turn on VMWare so we can gather physical network flows. Running on containers works, we just have the port of the app to VMWare.

This is a great app to be able to show performance impact in the AppDynamics app as well as the NEXUS dashboard to see real-time flow drops when we apply load. Any help with the porting of this to a VM-based Linux solution is greatly appreciated. Ive been using this for 2 years to demo Cisco NEXUS Insights and AppDynamics integration but it broken.

[SimonEismann]

Hi @miwitte, great to hear that you guys find the TeaStore to be useful!

Unfortunately, we do not provide any documentation on how to run the TeaStore outside of Docker containers. Generally, the idea would be to run an apache tomcat on each of the VMs and deploy the service .war files to the Tomcat. Basically, this would mean that you run the same setup/configuration steps that are used in the docker file on each VM. Take a look at the following two docker files to get an idea of what we set up within a docker container:

https://github.com/DescartesResearch/TeaStore/blob/master/services/tools.descartes.teastore.auth/Dockerfile
https://github.com/DescartesResearch/TeaStore/blob/master/utilities/tools.descartes.teastore.dockerbase/Dockerfile

However, since in your scenario you inherited an environment that was previously working, it might also make sense to track down what broke. To test this, I would first see if running older versions of TeaStore fixes the issue (i.e., is this something we broke) and if that does not help check out the recent changes to your environment and see if undoing any of the recent changes fixes your issue.

Otherwise, if you can post the individual service/tomcat logs I could take a look at them and see if anything sticks out to me.