Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Emily Jiang
    @Emily-Jiang
    ah. ok. maybe we can cancel this one and next week's one as I will be traveling next week.
    Ken Finnigan
    @kenfinnigan
    fine with me @Emily-Jiang
    Emily Jiang
    @Emily-Jiang
    ok. cancelled
    talk to you next week
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang I don't have anything for this weeks meeting
    Emily Jiang
    @Emily-Jiang
    @kenfinnigan I don't have any agenda either. shall we cancel this one? I am keen to utlise the new Rest Client and Open tracing in MP 2.2. What is your plan from Red Hat impl of MP 2.2? Quarkus or Thorntail update?
    also trying out the newly released Istio 1.1
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang fine with me to cancel
    Thorntail already has an MP 2.2 release out
    And Quarkus is being updated I believe
    Emily Jiang
    @Emily-Jiang
    MP 2.2 the Feb release?
    Ken Finnigan
    @kenfinnigan
    yeah
    Emily Jiang
    @Emily-Jiang
    ah. smallrye passed tck. In this case, I will go ahead to tidy up the service a code to use rest client
    Emily Jiang
    @Emily-Jiang
    @kenfinnigan I thought you announced that Red Hat is not going to invest Thorntail for future MP releases
    Is MP 2.2 the last Thorntail release?
    which version of Thorntail support MP 2.2?
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang didn't announce anything like that. Just that v2 will be the only stream we continue for a bit as Quarkus is the future
    MP 2.2 won't be the last Thorntail release, it's Thorntail 2.4.0.Final
    Emily Jiang
    @Emily-Jiang
    ok. thanks Ken! I reread your blog, which does say Thorntail will keep going for next 18 months. Thanks for the clarification
    Emily Jiang
    @Emily-Jiang
    I am visiting a customer tomorrow, so I won't be able to join the call
    Ken Finnigan
    @kenfinnigan
    I’m good with cancelling
    Emily Jiang
    @Emily-Jiang
    ok. thanks Ken!
    cancelling
    cancelled
    Emily Jiang
    @Emily-Jiang
    I am on holiday for 2 weeks from today. @kenfinnigan do you have anything to discuss? If not, we can cancel it.
    Ken Finnigan
    @kenfinnigan
    I don’t at present. I’m good with cancelling for next couple of weeks
    Emily Jiang
    @Emily-Jiang
    Thanks @kenfinnigan! Cancelled
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang FYI I don't have anything to discuss at tomorrow's call
    Emily Jiang
    @Emily-Jiang
    @kenfinnigan neither do I. @vadimeisenbergibm cannot make it. Let's cancel it
    cancelled
    Emily Jiang
    @Emily-Jiang
    @kenfinnigan I don't have any issue to discuss today. I am in the middle of doing all the update to test my changes but not get to a point where I can do a PR. Do you have anything to discuss?
    Ken Finnigan
    @kenfinnigan
    @Emily-Jiang I don’t have anything either
    Ken Finnigan
    @kenfinnigan
    Thanks @Emily-Jiang. I will be at Red Hat Summit next week so won’t be attending the call.
    I think you’re traveling too if I recall. So maybe cancel next week as well?
    Emily Jiang
    @Emily-Jiang
    yep
    let's cancel the call for this week and next week
    Kevin Durant
    @Pikachu15103123
    Is there anyone can tell me the tracing process of service mesh Istio?
    Ken Finnigan
    @kenfinnigan
    What do you mean by process @Pikachu15103123
    Kevin Durant
    @Pikachu15103123
    @kenfinnigan well, workflow I mean, which is what contains in the request, like when service A sends a request to service B, how do I know when a span begins and when it ends? Do i need to do write it specifically each time i manually set a span?
    Or Istio can automatically create a span when a service A send a request to service B, and record the time, this operation name, logs and so on. if it is this way, how does it collect each span, where it will put the data so other tools like Kiali can make a visual service graph?
    Ken Finnigan
    @kenfinnigan
    @Pikachu15103123 Istio provides tracing information irrespective of what your application does
    but that will only show istio ingress to sidecar, etc
    if you want application traces to be included, and then propagated between calls, just use MP OpenTracing
    I believe the latest MP OpenTracing will automatically propagate the B3 Headers from Istio on the incoming request onto an outgoing request if it's using the MP REST Client to make the call
    otherwise you will need to manually extract and then propagate the header onto the next call
    Emily Jiang
    @Emily-Jiang
    yes, as @kenfinnigan said, the MP Open Tracing will propagate the 7 headers Istio needs to build an overall trace
    and show up as one chain in Jaeger. The current app in servicea has the headers propagated
    I am trying to update to the latest MP 2.2 to remove the headers as they are propagated by default by MP Rest Client and MP Open Tracing
    Kevin Durant
    @Pikachu15103123
    what’s MP Opentracing?
    Kevin Durant
    @Pikachu15103123
    I was very confused about the relationship between Jaeger, Zipkin, Prometheus, Kiali and Istio. as you two said Istio injects sidecar to pod, how it works to produce a service graph with its own? Does that mean in fact the span data of Jaeger was from Istio sidecar?