Yossi Weihs

So I believe that – so I'll actually attempt an answer here, right, because it is a podcast and we've got interested minds here.

So in merging the products, we actually ported over the server, the OPM server.

So I would believe that the majority of the APIs, if not all of them, should still be there.

For example, what we have is we have a feed, a real-time feed of performance metrics out to using collect D format that can go into Graphite or Grafana.

That's still in play.

So really the name of the game here is take nothing away.

Does that help?

Of course.

We've got a whole bunch of super eager engineers just chomping at the bit to get this on a container.

And honestly, we've got some experiments going in-house.

We're looking to get people to tell us, yes, we will run it on a container because obviously every additional distribution package is a cost to us.

So we'll need to see that there's enough willingness to consume Ocum as a container.

We're very interested.

It is a journey and it, and it is also an evolution, you know, I'll call maybe you commented earlier in security and there's an area that, that has gone through a transformation and a lot of learning and customer feedback for us.

Um, and that's around the security and patching of our third party components that we use, such as the MySQL database.

And what we've learned there is that a lot of customers want to really be in the driver's seat and control when and how patches get rolled out.

And so as we've released one release after another of Unified Manager on Linux,

we've actually been slowly morphing the way we package it to the point where we are actually not shipping those third-party components anymore.

And we have opened it up so that customers can basically patch these at their own time and leisure.

And, you know, that removes a lot of the friction from the security process.