[odo] odo project performance investigation

[GeekArthur]

Description of the enhancement:

Currently the ODO project build for create and update use case becomes slower than before.

Two possible causes:

• Latest Changes on upstream (ODO CLI, ImageStream, templates, etc)
• Turbine layer ping logic or timing issue exists in Turbine layer

[GeekArthur]

I can take a look at this issue. please assign to me.

[GeekArthur]

For 0.7.0, we can do more investigation on image stream and template to ensure they are compatible with each other with the latest stable odo CLI.

[GeekArthur]

We can work on this issue with this one: #1115 together since they all related with finding image stream, template with better performance.

[GeekArthur]

Here is the officially odo supported image stream

"redhat-openjdk-18/openjdk18-openshift:latest",
        "openjdk/openjdk-11-rhel8:latest",
        "openjdk/openjdk-11-rhel7:latest",
        "rhscl/nodejs-8-rhel7:latest",
        "rhoar-nodejs/nodejs-8:latest",
        "rhoar-nodejs/nodejs-10:latest",
        "bucharestgold/centos7-s2i-nodejs:8.x",
        "bucharestgold/centos7-s2i-nodejs:10.x",
        "centos/nodejs-8-centos7:latest",

Len is working on testing the performance of the image stream with our templates

[GeekArthur]

Latest performance update is here: #1115 (comment)

[GeekArthur]

Both Len's metrics #1115 (comment) and reply from odo folks can prove that no big difference among different image streams. We check our ping logic, there is no problem. With the latest odo CLI, the performance is improved, sometimes the delay is due to environment issue (cluster VMs maintenance), I don't think we can do more given the investigation and current improved performance, so close the issue.