December 4, 2024 • 17 mins
Cybersecurity is more than just backup and recovery—it’s also business continuity and finding effective ways of keeping data secure and operations running smoothly.
Shelby Skrhak speaks with Michael St-Jean, global partner business executive at Red Hat, about:
To join the discussion, follow us on Twitter @IngramMicroUSA #B2BTechTalk
Listen to this episode and more like it by subscribing to B2B Tech Talk on Spotify, Apple Podcasts or Spreaker.
Shelby Skrhak speaks with Michael St-Jean, global partner business executive at Red Hat, about:
- How Red Hat supports business continuity
- How Veeam Kasten ties into OpenShift
- What partners should know about modern workloads
To join the discussion, follow us on Twitter @IngramMicroUSA #B2BTechTalk
Listen to this episode and more like it by subscribing to B2B Tech Talk on Spotify, Apple Podcasts or Spreaker.
Mark as Played
Transcript
Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:07):
You're listening to B to B Tech Talk with Ingram Micro,
a place to learn about how to grow your business
and stay ahead of technological advances before they become mainstream.
This episode is sponsored by ingram Micro's Expantage, the Next
Level way to transform your business's potential and reshape how
customers see you through advanced transactional data. Let's get into it.
Speaker 2 (00:29):
Welcome to B to B Tech Talk with Ingram Micro.
I'm your host Shelby Skirhawk, and our guest today is
Michael Saint John, Global partner business executive for red Hat.
Speaker 3 (00:39):
Michael, welcome, Thank you very much, glad to be here.
Speaker 2 (00:43):
Yeah, thank you for being here. So today we're talking
about red hat Open Shift and the them cast and solution.
But first let me introduce you some more. So tell
us about your role there at red Hat and how
you made your way there.
Speaker 3 (00:57):
Sure. Yeah, well, I lead the tech strategy for red
Hat's partner ecosystem cross Route Initiatives. So what that means
really is this is where we are building collaboration among
all of the partners within our ecosystem. So think about
solutions that we might be creating with our hardware partners
like Dell, or HPE, for example, or with component providers
(01:20):
like Intel and Nvidia, and of course software solutions like
being Cast. And my team works across all of these
partnerships and then with regional and global system integrators, service providers,
value added resellers and such to deliver a more complete
experience for organizations who use our products. As far as
my journey goes, you know, I've spent the last three
(01:42):
decades working with ecosystem partners. I started off as a
field solution architect and then led technical alliances for strategic
partners for most of my career. I came to RedHat
about seven years ago, working in our Hybrid Platforms business unit,
and then moving into this role about two years ago.
Speaker 2 (02:03):
Okay, excellent, So you see, I'm sure you've seen a
lot of changes and how red Hat has has approached
you know, solutions, and I think it's I'm sure you've
seen also the challenges that have come about. So let's
talk about backup recovery. Let's I guess maybe set the
(02:23):
stage for what are the problems that we're talking about,
you know, what are those things that we are needing
to solve?
Speaker 3 (02:30):
Yeah, So no, I think when we consider business critical workloads. Specifically,
there's got to be a clear strategy around business continuity,
and yes that begins with like backup and recovery, but
it should also include a robust data security and disaster
recovery strategy as part of that. So I think one
(02:50):
challenge that some folks who are not responsible for business
continuity is that they typically overlook that there's really no right,
one right answer. It's not a simple answer. You start.
You have to start with a deep understanding of the
criticality of each of the workloads and then taking into
(03:11):
consideration let's say, if a highly critical workload might be
dependent on less critical workloads, that might raise the bar
for all of all of the workloads in the ecosystem, right,
and then trying to quantify losses. Should one of these
workloads be unavailable for a minute, for an hour, for
a day, and what is the quantifiable loss? It might
(03:35):
be a loss of revenue, or it might be a
loss of reputation. Even in some extreme cases it could
also mean loss of life. So you know, depending on
your industry and where you're building those workloads, it could
have a significant value. But then you know, building a
strategy that includes backup and recovery for all these workloads,
(03:56):
but then also provides levels of synchronous or asynchronous disass
recovery across maybe a campus or a city or even
a continent, depending on the criticality of those workloads. It's
really imperative as we look at you know, not just
backup recovery, but this whole business continuity space and doing
this efficiently but more importantly effectively. It's not an easy
(04:21):
thing to do. And so I also see, like the
rise in cybersecurity and ransomware attacks, data security is also
squarely in the realm of business continuity and disaster recovery
as we move forward.
Speaker 2 (04:36):
So yeah, you've covered a lot there, so obviously the
pivot to cybersecurity that it's more than just backup and recovery.
It's the business continuity and that can mean anything from
like you said, loss of revenue to an emergency management
you know, loss of life. So translating that into the
(04:57):
technology then, so I guess give me a basic then
understanding of what the redhead open shift, you know, the
vmcast and solution we're talking about, and how that is,
you know, how that squares with backup and recovery and
business continuity sure.
Speaker 3 (05:17):
Yeah, So you know, modern application development platforms like red
Hat open Shift, it can really drive increased developer productivity,
faster development cycles. Actually, we've seen a number of studies.
In fact, there's one report by IDC that cited lower
costs of operation, less on planned downtime, all while delivering
(05:39):
huge increases and feature releases resulting in higher revenues and large, large,
large scale higher revenues. Yeah as well. But at the
same time, recent changes in the virtualization marketplace have have
been forcing a lot of organizations to rethink where their
traditional virtualized workloads might want to live in the future,
(06:03):
right and reconsidering their platform modernization options. As part of
that red Hat open Shift in addition to being an
excellent modern application development and deployment platform. And by the way,
you don't have to take my work for it. You
can check out some of the reports by Gartner and
Forrester in that regard. But in addition to the container
(06:23):
based workloads, there's also a feature within open Shift called
open ship versualization that allows organizations to move existing traditional
workloads onto the platform. Now, certainly, from a cost perspective,
businesses can possibly see large cost savings upfront and then
they don't ever really need to modernize those applications. If
(06:47):
they don't want to, they can just lift and shift
those workloads onto open ship visualization. But imagine the potential
now that the customers have and when they want to
start building out modern applications or may be refactory build
some of their current apps, they already have the platform there.
It's already built. And when they're ready to adopt things
(07:08):
like AI workloads, OpenShift AI is just another layer of
functionality that they can turn on if and when they
need it. But you know, with all these great advantages,
I think you still need to ensure that you have
business continuity across all and that's where the partnership with
Beam comes in for us. Not only is Beam reputed
(07:30):
in the industry for providing, you know, business continuity solutions
for workloads and virtual machines, but a few years back
when they acquired a company called cast in that brought
us into the Kubernetes space. Even when I started working
with cast and probably about six years ago, they already
had a strong presence in Kubernetes space backup and recovery.
(07:52):
And in the past several years, I've watched the vam
cast and solution grow to include product features that stand
out in the disaster recovery space as well, and with
a real focus on cybersecurity, governance and compliance. You know,
not only do they provide best in class products that
are integrated with things like open Shift, Advanced cluster Management,
(08:15):
and advanced cluster security, they also provide best practices, including
some tools like demos and lab guides. Even like last
week we were talking about a new validated pattern. They
published a validated pattern with us that helps customers and
system integrators are like to deliver solutions faster and most importantly,
(08:38):
in a repeatable and extensible manner. So it's been a
great relationship with them.
Speaker 2 (08:43):
Well, so, so you mentioned, you know the modern workload
and application modernization and how you know casting brought in Kubernetes.
Can we basically let's outline the difference then, because I
understand backup re cover is different in Kubernetes than it
would be in your traditional on prem data center setup. Right.
Speaker 3 (09:07):
Yeah, Well, a lot of the concepts are the same,
but there are fundamental differences that need to be taken
into account. I think one of the main differences is
when you consider where your application keeps its state. And
what I mean by this is if the infrastructure where
the application is running goes down and then you restart
(09:28):
that application somewhere else, does it nowhere it left off?
What's the recovery point for the application? So in traditional
machine workloads, the state is typically held at the application
or web service layer, and then you back up your data,
recover it, mount it to your application. When it restarts,
(09:48):
you're good to go. But Kubernetes as a platform is
ephemeral by nature, meaning that when the service goes down,
it restarts elsewhere. It's really good at restarting services, but
that service and forgets everything that it was doing previously.
And the way that we get around that in an
open shift cluster is through the persistent storage layer. So
(10:11):
the storage actually holds the state of the applications, so
that when an application restarts, the persistent storage volume claim
that your application has is still in there, and then
the application can recover its state. Now, this is a
common concept for application workload resiliency in Kubernetes. But what
(10:32):
happens if the infrastructure goes down, Well, yeah, that's where
you may have to recover from a backup, or you
have to recover to another cluster somewhere that has either
a synchronous or an asynchronous copy of your data.
Speaker 2 (10:47):
So then understanding open shift virtualization with VM and cast and,
I want to make sure that I do understand the
role that VM and castin has with red hat. How
do these work together?
Speaker 3 (11:02):
Right? Yeah, So the solution is Viamcasten and as I mentioned,
Kubernetes is ephemeral. In order for the application to have
the context to what data was associated with it, the
backup needs to be cluster aware, and so with the
cast and product, you're able to back up not only
your persistent volume data but also your internal images complete
(11:27):
with cluster aware metadata, so your open shift cluster resources
have context with your data. This is all delivered through
APIs within cast and so Casten is able to grab
cluster resources and internal images to create a complete backup
that then can be restored once cluster is back online
(11:47):
or maybe to a separate cluster. But beyond that, Casten
operates with a strong security everywhere edict as well, so
this includes building image scanning and a policy guardrails right
at the development life cycle, but also integration with authentication
protocols and secrets as well as backup immutability in the
(12:09):
event of a ransomware attack or some other disaster. It
also provides auditing and integration with threat detection tools like
our advanced cluster security product like that I mentioned earlier,
and then role based access controls to enhance some security
operations as across the cluster across platform.
Speaker 2 (12:30):
So then let's get into so we've talked about how
red haat works, then the vamcast and solution, I guess
for the Ingram micro partner, reseller, just someone in the
channel that's listening and understanding. Okay, so how all of
this works within the Kubernetes, within the modern workload. What
(12:50):
can you say, as kind of a summary a step back,
what should the partner or reseller know about this this
solution that is that makes it wundantly clear that this is, uh,
you know, this is how modern workloads are running and
being secured, and that this is uh really the next level.
Speaker 3 (13:12):
Yeah, so I think maybe some of the resellers don't
really need to know all of the technical details as
to you know, why why things are a little bit different,
but rest assured that you know, as they're as they're
looking at a customer's workload, they definitely need a complete
(13:32):
business continuity and disaster recovery strategy going forward. And you know,
being able to work with a company that is steeped
in that profile, has a long pedigree for doing backup
recovery solutions for machine workloads as well as Kubernetes workloads,
I think is very helpful. And then having that that
(13:56):
additional capability around UH security and you know, cybersecurity and
disaster recovery capabilities is very important for customers that you'll
be talking about as they're moving to more modernized platform
or modern application development and deployment strategy.
Speaker 2 (14:17):
Right right, Well, as we do start to wrap up
our episode, we always ask our guests the same final question,
and it's a broad one, so I'll warn you. It's
where do you see technology going in the next year?
So it can be within this space or or obviously
something else that you're keeping an eye on. And you know,
(14:38):
I'm curious, like, where are we going to be this
time twenty twenty five?
Speaker 3 (14:42):
Yeah, Well, so you know, everybody talks about AI these days,
but you know, certainly, I think we're in the midst
of seeing a huge infrastructure transformation in the short term. Now,
how that's all going to shake out, I can't be
certain of that, but it's clear to me it's I
(15:02):
think it's a clear bet that a lot of organizations
are going to be looking at how they can future
prove their investments. So take care of the near term
business needs while ensuring that you have a path forward
to modernize application deployments, right, they have to in order
to survive. Really, if you think about the future of
(15:23):
modern business applications, there will come a time when the
talent pool out there will be firmly steeped in things
like declarative methodologies, using get ops framework. It's in CICD pipelines,
you know, it's that whole application development methodology and the
tools that we use will change over time. It's already happening.
(15:46):
And then there was even a Gartner report recently that
predicted by twenty twenty seven some seventy five percent of
AI workloads would be running in containers. So it's clear
to me anyway that that's the future. And at the
same time, cybersecurity attacks are on the rise. There's never
been a time when application business continuity and disaster recovery
(16:07):
has been more critical. Than it is today, and I
only see that trend increasing over time.
Speaker 2 (16:14):
Well, we're definitely in changing times now. So for listeners
who want to have any questions about something that we
talked about today or want to find out more, how
should they reach out?
Speaker 3 (16:26):
Yeah? Sure, so we have lots of joint assets available
on the web where you can find out more information.
But probably the easiest way to find out more is
to reach out to the Ingram Micro Market Development Team.
You can just send an email to them, either to
vm MD at ingrammicro dot com and just for spelling,
(16:48):
VM is spelt with two e's in an A, so
it's am and then MD at ingrammicro dot com or
to the red Hat team. So at mdteam at ingrammicro
dot com. They can provide some additional help or get
you in touch with one of our subject matter experts
(17:10):
as well. Well.
Speaker 2 (17:11):
Michael, I appreciate the time and insight today. Thank you
so much for joining me.
Speaker 3 (17:15):
Sure it was a pleasure.
Speaker 2 (17:17):
Yeah, and thank you listeners for tuning in and subscribing
to B to B Tech Talk with Ingram Micro. If
you haven't already subscribed, be sure to do so and
don't forget. You can find all of these episodes on
the ingram Micro Expantage platform. Until next time, I'm Shelby Skirhawk.
Speaker 1 (17:34):
You've been listening to B to B tech Talk by
Ingram Micro. This episode was sponsored by Ingram Micro Exvantage.
B to B tech Talk is a joint production between
Sweetfish Media and Ingram Micro. To listen to this episode
and many others, visit ingrammicro dot com.
You're listening to B to B Tech Talk with Ingram Micro,
a place to learn about how to grow your business
and stay ahead of technological advances before they become mainstream.
This episode is sponsored by ingram Micro's Expantage, the Next
Level way to transform your business's potential and reshape how
customers see you through advanced transactional data. Let's get into it.
Speaker 2 (00:29):
Welcome to B to B Tech Talk with Ingram Micro.
I'm your host Shelby Skirhawk, and our guest today is
Michael Saint John, Global partner business executive for red Hat.
Speaker 3 (00:39):
Michael, welcome, Thank you very much, glad to be here.
Speaker 2 (00:43):
Yeah, thank you for being here. So today we're talking
about red hat Open Shift and the them cast and solution.
But first let me introduce you some more. So tell
us about your role there at red Hat and how
you made your way there.
Speaker 3 (00:57):
Sure. Yeah, well, I lead the tech strategy for red
Hat's partner ecosystem cross Route Initiatives. So what that means
really is this is where we are building collaboration among
all of the partners within our ecosystem. So think about
solutions that we might be creating with our hardware partners
like Dell, or HPE, for example, or with component providers
(01:20):
like Intel and Nvidia, and of course software solutions like
being Cast. And my team works across all of these
partnerships and then with regional and global system integrators, service providers,
value added resellers and such to deliver a more complete
experience for organizations who use our products. As far as
my journey goes, you know, I've spent the last three
(01:42):
decades working with ecosystem partners. I started off as a
field solution architect and then led technical alliances for strategic
partners for most of my career. I came to RedHat
about seven years ago, working in our Hybrid Platforms business unit,
and then moving into this role about two years ago.
Speaker 2 (02:03):
Okay, excellent, So you see, I'm sure you've seen a
lot of changes and how red Hat has has approached
you know, solutions, and I think it's I'm sure you've
seen also the challenges that have come about. So let's
talk about backup recovery. Let's I guess maybe set the
(02:23):
stage for what are the problems that we're talking about,
you know, what are those things that we are needing
to solve?
Speaker 3 (02:30):
Yeah, So no, I think when we consider business critical workloads. Specifically,
there's got to be a clear strategy around business continuity,
and yes that begins with like backup and recovery, but
it should also include a robust data security and disaster
recovery strategy as part of that. So I think one
(02:50):
challenge that some folks who are not responsible for business
continuity is that they typically overlook that there's really no right,
one right answer. It's not a simple answer. You start.
You have to start with a deep understanding of the
criticality of each of the workloads and then taking into
(03:11):
consideration let's say, if a highly critical workload might be
dependent on less critical workloads, that might raise the bar
for all of all of the workloads in the ecosystem, right,
and then trying to quantify losses. Should one of these
workloads be unavailable for a minute, for an hour, for
a day, and what is the quantifiable loss? It might
(03:35):
be a loss of revenue, or it might be a
loss of reputation. Even in some extreme cases it could
also mean loss of life. So you know, depending on
your industry and where you're building those workloads, it could
have a significant value. But then you know, building a
strategy that includes backup and recovery for all these workloads,
(03:56):
but then also provides levels of synchronous or asynchronous disass
recovery across maybe a campus or a city or even
a continent, depending on the criticality of those workloads. It's
really imperative as we look at you know, not just
backup recovery, but this whole business continuity space and doing
this efficiently but more importantly effectively. It's not an easy
(04:21):
thing to do. And so I also see, like the
rise in cybersecurity and ransomware attacks, data security is also
squarely in the realm of business continuity and disaster recovery
as we move forward.
Speaker 2 (04:36):
So yeah, you've covered a lot there, so obviously the
pivot to cybersecurity that it's more than just backup and recovery.
It's the business continuity and that can mean anything from
like you said, loss of revenue to an emergency management
you know, loss of life. So translating that into the
(04:57):
technology then, so I guess give me a basic then
understanding of what the redhead open shift, you know, the
vmcast and solution we're talking about, and how that is,
you know, how that squares with backup and recovery and
business continuity sure.
Speaker 3 (05:17):
Yeah, So you know, modern application development platforms like red
Hat open Shift, it can really drive increased developer productivity,
faster development cycles. Actually, we've seen a number of studies.
In fact, there's one report by IDC that cited lower
costs of operation, less on planned downtime, all while delivering
(05:39):
huge increases and feature releases resulting in higher revenues and large, large,
large scale higher revenues. Yeah as well. But at the
same time, recent changes in the virtualization marketplace have have
been forcing a lot of organizations to rethink where their
traditional virtualized workloads might want to live in the future,
(06:03):
right and reconsidering their platform modernization options. As part of
that red Hat open Shift in addition to being an
excellent modern application development and deployment platform. And by the way,
you don't have to take my work for it. You
can check out some of the reports by Gartner and
Forrester in that regard. But in addition to the container
(06:23):
based workloads, there's also a feature within open Shift called
open ship versualization that allows organizations to move existing traditional
workloads onto the platform. Now, certainly, from a cost perspective,
businesses can possibly see large cost savings upfront and then
they don't ever really need to modernize those applications. If
(06:47):
they don't want to, they can just lift and shift
those workloads onto open ship visualization. But imagine the potential
now that the customers have and when they want to
start building out modern applications or may be refactory build
some of their current apps, they already have the platform there.
It's already built. And when they're ready to adopt things
(07:08):
like AI workloads, OpenShift AI is just another layer of
functionality that they can turn on if and when they
need it. But you know, with all these great advantages,
I think you still need to ensure that you have
business continuity across all and that's where the partnership with
Beam comes in for us. Not only is Beam reputed
(07:30):
in the industry for providing, you know, business continuity solutions
for workloads and virtual machines, but a few years back
when they acquired a company called cast in that brought
us into the Kubernetes space. Even when I started working
with cast and probably about six years ago, they already
had a strong presence in Kubernetes space backup and recovery.
(07:52):
And in the past several years, I've watched the vam
cast and solution grow to include product features that stand
out in the disaster recovery space as well, and with
a real focus on cybersecurity, governance and compliance. You know,
not only do they provide best in class products that
are integrated with things like open Shift, Advanced cluster Management,
(08:15):
and advanced cluster security, they also provide best practices, including
some tools like demos and lab guides. Even like last
week we were talking about a new validated pattern. They
published a validated pattern with us that helps customers and
system integrators are like to deliver solutions faster and most importantly,
(08:38):
in a repeatable and extensible manner. So it's been a
great relationship with them.
Speaker 2 (08:43):
Well, so, so you mentioned, you know the modern workload
and application modernization and how you know casting brought in Kubernetes.
Can we basically let's outline the difference then, because I
understand backup re cover is different in Kubernetes than it
would be in your traditional on prem data center setup. Right.
Speaker 3 (09:07):
Yeah, Well, a lot of the concepts are the same,
but there are fundamental differences that need to be taken
into account. I think one of the main differences is
when you consider where your application keeps its state. And
what I mean by this is if the infrastructure where
the application is running goes down and then you restart
(09:28):
that application somewhere else, does it nowhere it left off?
What's the recovery point for the application? So in traditional
machine workloads, the state is typically held at the application
or web service layer, and then you back up your data,
recover it, mount it to your application. When it restarts,
(09:48):
you're good to go. But Kubernetes as a platform is
ephemeral by nature, meaning that when the service goes down,
it restarts elsewhere. It's really good at restarting services, but
that service and forgets everything that it was doing previously.
And the way that we get around that in an
open shift cluster is through the persistent storage layer. So
(10:11):
the storage actually holds the state of the applications, so
that when an application restarts, the persistent storage volume claim
that your application has is still in there, and then
the application can recover its state. Now, this is a
common concept for application workload resiliency in Kubernetes. But what
(10:32):
happens if the infrastructure goes down, Well, yeah, that's where
you may have to recover from a backup, or you
have to recover to another cluster somewhere that has either
a synchronous or an asynchronous copy of your data.
Speaker 2 (10:47):
So then understanding open shift virtualization with VM and cast and,
I want to make sure that I do understand the
role that VM and castin has with red hat. How
do these work together?
Speaker 3 (11:02):
Right? Yeah, So the solution is Viamcasten and as I mentioned,
Kubernetes is ephemeral. In order for the application to have
the context to what data was associated with it, the
backup needs to be cluster aware, and so with the
cast and product, you're able to back up not only
your persistent volume data but also your internal images complete
(11:27):
with cluster aware metadata, so your open shift cluster resources
have context with your data. This is all delivered through
APIs within cast and so Casten is able to grab
cluster resources and internal images to create a complete backup
that then can be restored once cluster is back online
(11:47):
or maybe to a separate cluster. But beyond that, Casten
operates with a strong security everywhere edict as well, so
this includes building image scanning and a policy guardrails right
at the development life cycle, but also integration with authentication
protocols and secrets as well as backup immutability in the
(12:09):
event of a ransomware attack or some other disaster. It
also provides auditing and integration with threat detection tools like
our advanced cluster security product like that I mentioned earlier,
and then role based access controls to enhance some security
operations as across the cluster across platform.
Speaker 2 (12:30):
So then let's get into so we've talked about how
red haat works, then the vamcast and solution, I guess
for the Ingram micro partner, reseller, just someone in the
channel that's listening and understanding. Okay, so how all of
this works within the Kubernetes, within the modern workload. What
(12:50):
can you say, as kind of a summary a step back,
what should the partner or reseller know about this this
solution that is that makes it wundantly clear that this is, uh,
you know, this is how modern workloads are running and
being secured, and that this is uh really the next level.
Speaker 3 (13:12):
Yeah, so I think maybe some of the resellers don't
really need to know all of the technical details as
to you know, why why things are a little bit different,
but rest assured that you know, as they're as they're
looking at a customer's workload, they definitely need a complete
(13:32):
business continuity and disaster recovery strategy going forward. And you know,
being able to work with a company that is steeped
in that profile, has a long pedigree for doing backup
recovery solutions for machine workloads as well as Kubernetes workloads,
I think is very helpful. And then having that that
(13:56):
additional capability around UH security and you know, cybersecurity and
disaster recovery capabilities is very important for customers that you'll
be talking about as they're moving to more modernized platform
or modern application development and deployment strategy.
Speaker 2 (14:17):
Right right, Well, as we do start to wrap up
our episode, we always ask our guests the same final question,
and it's a broad one, so I'll warn you. It's
where do you see technology going in the next year?
So it can be within this space or or obviously
something else that you're keeping an eye on. And you know,
(14:38):
I'm curious, like, where are we going to be this
time twenty twenty five?
Speaker 3 (14:42):
Yeah, Well, so you know, everybody talks about AI these days,
but you know, certainly, I think we're in the midst
of seeing a huge infrastructure transformation in the short term. Now,
how that's all going to shake out, I can't be
certain of that, but it's clear to me it's I
(15:02):
think it's a clear bet that a lot of organizations
are going to be looking at how they can future
prove their investments. So take care of the near term
business needs while ensuring that you have a path forward
to modernize application deployments, right, they have to in order
to survive. Really, if you think about the future of
(15:23):
modern business applications, there will come a time when the
talent pool out there will be firmly steeped in things
like declarative methodologies, using get ops framework. It's in CICD pipelines,
you know, it's that whole application development methodology and the
tools that we use will change over time. It's already happening.
(15:46):
And then there was even a Gartner report recently that
predicted by twenty twenty seven some seventy five percent of
AI workloads would be running in containers. So it's clear
to me anyway that that's the future. And at the
same time, cybersecurity attacks are on the rise. There's never
been a time when application business continuity and disaster recovery
(16:07):
has been more critical. Than it is today, and I
only see that trend increasing over time.
Speaker 2 (16:14):
Well, we're definitely in changing times now. So for listeners
who want to have any questions about something that we
talked about today or want to find out more, how
should they reach out?
Speaker 3 (16:26):
Yeah? Sure, so we have lots of joint assets available
on the web where you can find out more information.
But probably the easiest way to find out more is
to reach out to the Ingram Micro Market Development Team.
You can just send an email to them, either to
vm MD at ingrammicro dot com and just for spelling,
(16:48):
VM is spelt with two e's in an A, so
it's am and then MD at ingrammicro dot com or
to the red Hat team. So at mdteam at ingrammicro
dot com. They can provide some additional help or get
you in touch with one of our subject matter experts
(17:10):
as well. Well.
Speaker 2 (17:11):
Michael, I appreciate the time and insight today. Thank you
so much for joining me.
Speaker 3 (17:15):
Sure it was a pleasure.
Speaker 2 (17:17):
Yeah, and thank you listeners for tuning in and subscribing
to B to B Tech Talk with Ingram Micro. If
you haven't already subscribed, be sure to do so and
don't forget. You can find all of these episodes on
the ingram Micro Expantage platform. Until next time, I'm Shelby Skirhawk.
Speaker 1 (17:34):
You've been listening to B to B tech Talk by
Ingram Micro. This episode was sponsored by Ingram Micro Exvantage.
B to B tech Talk is a joint production between
Sweetfish Media and Ingram Micro. To listen to this episode
and many others, visit ingrammicro dot com.
Popular Podcasts
Stuff You Should Know
If you've ever wanted to know about champagne, satanism, the Stonewall Uprising, chaos theory, LSD, El Nino, true crime and Rosa Parks, then look no further. Josh and Chuck have you covered.
Dateline NBC
Current and classic episodes, featuring compelling true-crime mysteries, powerful documentaries and in-depth investigations. Follow now to get the latest episodes of Dateline NBC completely free, or subscribe to Dateline Premium for ad-free listening and exclusive bonus content: DatelinePremium.com
The Joe Rogan Experience
The official podcast of comedian Joe Rogan.