►
Description
INDUS Conclave- South 2016
A
B
B
First
of
all,
I
want
to
thank
all
of
you
for
joining
us
for
the
session.
It's
a
day,
long
session
I
know.
After
my
session,
we
are
going
to
have
lunch.
I
am
there
between
you
and
the
lunch.
So
knowing
that,
so
my
session
is
going
to
be
on
the
solutions,
what
we
have
for
love
economy.
Actually,
the
topic
given
for
this
whole
day
event
is
really
very
nice.
We
talked
about
the
idea,
economy,
ajai,
economy
and
live
economy.
All
of
them
are
same.
B
So
this
is
the
idea
economy
or
the
lively
economy.
These
are
slight.
Probably
all
of
you
would
have
seen
by
2020.
We
talked
about
about
one
trillion
applications
which
is
going
to
go
around
about
100
billion
connected
devices.
We
also
call
number
a
is
something
called
as
IOT
has
a
whole
world
now,
which
is
revolving
around
ideas.
So
what
that
means
is
that
who
is
able
to
commercialize
their
ideas,
foster
they
are
going
to
be
the
winner.
Who
is
going
to
be
not?
B
He
may
be
having
thousands
of
ideas
when
I
tell
he
the
company,
the
organization
may
have
thousands
of
ideas
if
they
cannot
be.
If
those
all
cannot
be
commercialized,
that
means
they
are
going
to
lose
out
in
the
market.
I
want
to
just
give
an
example,
two
examples.
The
first
example
is
that,
just
about
23
days
back,
you
hear
about
one
mobile
company,
okay,
which
starts
with
a
which
is
going
to
open
developer
center
in
bangalore.
They
are
going
to
hire
about
40,000
square
feet
space.
B
B
Sorry
everything
now
the
ideas
how
we
can
transform
the
to
the
applications
and
another
example
which
I
want
to
give
is
that
now
because
of
the
agility,
if
somebody
is
able
to
be
agile
enough
to
produce
an
application,
I
have
one
of
my
friend:
he
is
working
in
the
US
for
a
oil
and
gas
company
and
recently
the
established
you
know,
office
in
bangalore,
HSR
layout
and
the
rose
our
equipment
for
developing
an
application
which
is
mobile,
based
application.
What
that
it
is,
they
gave
that
project
to
Bangalore.
B
You
not
believe
me
what
that
it
is.
They
went
to
the
goofy
side.
There
was
some
small
developer.
They
took
just
about
three
days
time
to
complete
that
project.
They
developed
the
very
nice
application
and
gave
it
back
and
which
is
used
by
the
US
company
and
what
that
means
in
this
is
there.
It
came
from
there.
It
came
to
Bangalore.
It
went
to
to
be
all
these
you
see,
but
what
is
very,
very
important
is
that
the
agility
right,
the
agility.
B
B
If
you
ask
me
whether
that
is
going
to
be
economical,
that
you
have
to
do
TCO
our
way
all
of
them,
but
when
you
look
at
it
may
be
very
good
model
to
an
extent
when
you
grow
up
to
certain
number
of
workloads
or
the
number
of
workloads.
If
you
go
beyond
that,
that
may
not
be
but
two
reasons
compelling
reasons
for
people
going
for
cloud.
Is
that
the
first
one,
the
first
at
which
I
am
going
to
deploy
my
application?
B
You
go
to
AWS
or
your
hybrid
solutions,
whatever
you
consider
it
may
be
about
one
hour.
Time
are
45
minutes.
My
application
may
be
a
vm
or
physical
machine,
which
is
ready.
There
is
a
first
reason.
The
second
reason
is
the
manageability.
If
you
can
bring
the
same
kind
of
attributes
to
your
infrastructure,
which
is
there
a
on-premise,
you
can
do
much
better
than
whatever
the
cloud
can
do.
B
So,
if
you
look
at
what
this
leaves
us
is
that
it
leaves
us
with
x
model
IT.
That
is
what
what
IDC
and
gartner
call
one
needs
for
the
traditional
applications.
It
may
be
SI
p,
hana
or
it
may
be
a
database
machines.
These
are
other
traditional
applications.
The
other
side.
You
have
the
infrastructure
for
idea
economy.
If
you
look
at
these,
two
are
two
distinct
solutions
or
two
distinct
applications:
the
requirements
in
the
traditional
applications.
You
do
not
expect
a
company
to
grow
100
times
within
five
years.
It's
no
way
possible.
B
Unless
there
is
going
to
be
a
huge
number
of
occasions
and
mergers,
a
company
which
has
got
10,000
people
know
where
it
can
go
to
one
lakh
or
two
lakh
people
within
a
short
span
of
time,
but
whereas,
if
we
consider
maybe
and
e-commerce
portal
or
it
may
it
may
be
a
hotel
for
a
web
application,
this
all,
which
is
so
erratic.
I
am
going
to
give
a
new
scheme.
Okay,
maybe
you
know
about
the
billion
dollar
sale
and
all
these,
so
these
are
some
of
the
applications.
B
If
you
look
at
these
are
our
cloud
native
and
it
is
very
difficult
to
predict
what
is
that
you
know
kind
of
go
into
how
so
what
that
means
is
that
that
is
what
called,
as
you
are,
throwed
enabled
idea
academy
applications.
These
two
required
two
different,
distinct
solutions.
When
I
tell
the
traditional
applications,
which
requires
a
scalability
availability
and
all
those
whatnot,
but
whereas
the
cloud
enabled
has
a
given
you
an
example,
people
look
at.
Maybe
I
am
very
sure
that
you
have
business
team
as
well.
When
they
come
to
you,
they
will
tell.
B
Can
you
give
me
certain
applications?
I
want
to
go
live
within
a
week,
have
an
issue.
That
is
what
the
situation
currently,
but,
whereas
as
an
infrastructure
or
an
application,
it
may
not
be
possible
for
us
to
go
and
put
them
on
life
so
now
how
we
can
look
at
something
completely
different,
which
will
call
for
a
new
experience
which
is
rebooting
your
current
infrastructure,
so
how
the
infrastructure
should
look
like
what
we
call
by
model.
B
I
should
be
able
to
provision
for
both
cloud-enabled
applications,
which
is
really
very,
very
prevalent,
but
we
cannot
just
go
away
from
your
traditional
applications.
I
need
to
look
at
something
which
I
can
have
all
these
together.
The
moment
you
have
an
infrastructure
which
can
be
shared
by
all
of
them.
You
are
going
to
benefit
from
that
and
which
will
surely
going
to
help
you
to
reduce
the
expenses,
and
it
is
surely
so.
This
is
a
second
one,
which
is
something
like
a
mandate.
As
I
mentioned,
people
go
to
cloud.
B
If
you
are
able
to
provision
something
at
cloud
speed,
I
can
provision
in
premise
as
well,
maybe
about
15
mins
time
or
maybe
in
seconds
away,
if
I
am
able
to
provision
and
give
it
to
the
business.
That
is
what
what
is
required
and
develop
more
apps
foster
the
more
foster
you
develop.
Your
business
gives
that
foster
and
you
are
going
to
need
in
your
field
of
business.
Whatever
we
are
doing,
what
we
are
doing
is
HPE,
even
at
Packard.
Enterprise
is
launching
something
called
as
composable
infrastructure,
which
in
another
quarter
this
quarter.
B
What
we
are
targeting
and,
in
fact,
actually
this
platform,
which
was
launched
in
lost,
discover
which
was
in
December,
and
there
are
a
lot
of
development
work
and
Alliance
work
with
like
ASAP
is
Microsoft
all
of
them.
It
is
going
on
and
it
is
going
to
hit
the
cell
cycle
in
just
about
a
quarter.
What
this
means
is
that
there
are
four
definitions.
The
first
one
is
that
you
will
be
able
to
run
anything
on
this
composer
infrastructure,
so
you
will
not
be
left
with
a
siloed
approach.
B
Siloed
approach
I
have
a
particular
infrastructure
which
is
used
only
for
this
particular
database,
or
it
is
used
only
for
this
particular
workload.
It
may
be
Hana
as
well,
or
it
may
be
a
Hadoop
or
it
may
be
exchanged.
So
what
you
do
is
that
you
are
going
to
have
an
infrastructure
which
is
composable
infrastructure.
You
will
be
able
to
compose
and
recompose,
depending
on
your
workload.
That
is
run
anything
and
you
will
also
be
able
to
move
faster.
So
that
is
another
key
element.
B
Currently,
if
you
look
at,
we
are
not
able
to
move
that
applications
or
the
workloads
faster.
So
that's
the
reason
we
are
really
fixated
to
1,
given
infrastructure
for
that
particular
workload,
so
that
results
in
under
utilization
and
war
were
proficient.
That
is
what
it
helps
you
to
reduce
the
capital
expenses
and
the
efficiency
and
unlocking
value
which
I
am
going
to
cover
subsequently.
B
So
what
you
see
in
this
slide,
these
three
are
the
guiding
principles
for
this
architecture.
The
first
one
is
fluid
resourceful.
What
we
are
going
to
do
is
that
in
this
infrastructure,
once
it
is
going
to
be
available
in
another
quarter,
so
it
is
going
to
give
you
a
fluidity
in
nature.
You
do
not
need
to
be
telling
that
this
particular
system
is
defined
only
to
run
this
particular
application,
and
this
is
for
only
these
database.
So,
for
next
five
years
it
has
to
run
only
in
this.
That
is
not
the
case.
B
Instead
of
that,
you
compose
it
for
given
application
or
workload,
rather
not
the
application
for
the
workload
ones.
That
usage
is
completed.
You
just
define
another
recompose
that
and
recompose.
So
what
that
means
is
that
you
are
going
to
recompose
for
your
actual
demand
of
the
workload
that
is
going
to
help
you
to
reduce
your
capital
expenses.
Then
the
second
one
is
software,
different
intelligence.
What
is
going
to
bring
in,
depending
on
your
workload,
you
define,
who
are
maybe
a
curious
or
what
are
the
characteristics
of
the
applications
you
define
for
the
application?
B
Okay,
it
is
going
to
be
something
like
a
stateless.
As
long
I
am
going
to
run
workload,
a
I
am
going
to
have
this
state.
What
load
be
requires
a
different
state,
I
more
to
that
by
just
doing
software
different
configuration.
That
is
the
second
one.
Then
the
third
one
is
unified,
APA,
a
single
line
of
code,
the
single
line
of
code,
which
helps
you
to
provision.
It
may
be
a
database.
It
may
be
a
virtualization.
It
may
be
a
container
whatever
the
workload
you
want:
infrastructure
or
the
applications
using
a
single
code.
B
It
may
have
some
storage,
it
may
have
some
networking
or
compute
and
all
those
will
be
proficient
in
a
single
line
of
code.
These
are
the
elements
which
is
making
this
infrastructure
to
deploy
your
workload
at
cloud-like
speed,
and
we
are
very,
very
excited
about
this
particular
one
and
young
daughter
as
well,
had
released.
Also
you
grow
such
you
can
search
in
the
google
something
called
as
composable
infrastructure.
You
are
very
sure
you
will
see
lot
of
hits
on
that
and
which,
which
is
going
to
be
released
in
another
quarter.
B
As
I
said
so
this
word.
The
architecture
is
what
you
see:
it's
a
completely
grown
sub
approach,
so
none
of
the
existing
products
what
we
use
for
these,
so
these
are
completely
different
frames,
servers
and
storage.
As
networking
it
is
going
to
help
you
to
come
force
workload
for
a
compute
for
the
storage
and
also
for
the
networking
as
well.
Okay,
so
really,
as
I
said,
we
are
very,
very
exited
about
this.
Now
I
just
come
to
the
next
one.
B
If
you
look
at
the
business
data,
that's
what
what
we
talked
about
the
Hana
or
traditional
applications
and
everything
here
you
have
the
machine
data
which
is
I've
OT
and
the
other
one
is
the
human
data
which
is
growing
exponentially.
In
fact,
you
know
whenever
every
two
years
or
three
years,
I
am
change.
I
am
seeing
that
the
numbers
are
changing
completely
earlier.
We
used
to
tell
maybe
about
10
billion
devices.
Now
we
are
talking
about
hundred
billion
devices.
Similarly,
the
applications
as
well.
B
We
were
talking
about
some
billions
earlier
now
it
is
trillions
in
another
23
years.
It
will
be
much
more
than
that
as
well
and
in
fact,
HP
also
HPE
also
am
working
on
another
project.
You
hear
something
called
as
the
machine
so
which
is
another
roadmap
which
may
be
available
after
two
or
three
years.
So
what
these
all
are
about
is
that
how
it
is
possible
for
us
to
acquire
data
faster
and
do
analytics
and
give
the
data
back?
Okay,
the
whole
essay
p
hana
is
about
that
now.
B
What
is
a
requirement
for
the
infrastructure
which
is
going
to
host
SI
p
Hana
is
that
you
are
going
to
talk
about
scalability
and
scalability
is
that
these
are
the
traditional
applications.
It
is
not
that
today,
I
want
to
start
with
thousand
users.
After
three
years,
I
am
going
to
go
to
10,000
users.
I
can
go
and
do
a
forklift
upgrade.
Am
I
right?
We
can't
do
that.
B
So
what
is
required
is
that
the
scale
with
which
we
are
able
to
expand
the
system
today,
my
my
company,
which
is
hosting
maybe
thousand
users
I,
want
to
go
10,000
users
or
I,
have
few
modules
included
now
tomorrow.
I
want
to
have
more
modules.
I
do
not
want
to
have
a
siloed,
so
that
is
what
the
scalability
is,
how
it
is
possible
for
us
to
scale
without
disturbing
our
existing
applications
or
the
workload
and,
at
the
same
time,
whatever
scale
we
talk
about.
B
The
performance
should
not
be
affected
and
the
performance
should
be
such
a
way.
The
linearity
when
I
am
having
a
to
system
configuration
which
is
giving
me
some
next
performance
when
I
am
adding.
Furthermore,
it
should
give
me
in
addition
to
that,
what
is
the
performance
you
are
going
to
get?
That
is
what
performance
and
the
third
one
the
first
two
are
combined
with
the
third
one.
I
am
very
sure
when
we
talk
about
Hana
or
ASAP
solution,
which
is
business-critical
applications
there.
B
We
are
not
talking
about
a
scale
out,
even
those
Caleb
model
is
available,
but
the
scale
out
like
a
web
server
and
cloud
enabled
application.
When
we
tell
netflix.
For
example,
you
see
these
are
our
thousands
of
servers.
What
you
run,
if
maybe
about
hundred
servers
down
I,
have
no.
Nobody
cares
about
that
right,
hp.com,
natl
hp.com,
when
we
run
in
the
back
end.
B
There
are
several
hundreds
of
servers
if
something
goes
down,
nobody
bothers
so
the
availability
is
much
more
critical
here
and
at
the
same
time,
what
is
the
kind
of
TC
war
you
are
going
to
pay?
You
are
going
to
eat,
it
is
going
to
cost
you
the
TCO
and
our
way.
That
is
very,
very
important.
Now
lost.
For
four
years
we
have
been
seeing
SI
p
hana.
Now
this
becomes
even
more
critical,
the
TCO
then
the
last
one
is
about
the
experience
we
help.
B
B
These
convert
systems
are
built
on
HPE
servers
and
the
storage
and
networking
all
of
them,
which
is
factory
integrated,
validated
by
hewlett-packard
enterprise
and
ASAP,
and
in
fact
you
know,
we
also
have
our
development
center,
along
with
situated
in
world
of
Jesus
in
Germany,
along
with
ACP,
so
that
the
interaction
will
be
much
faster,
much
quicker.
So
what
this
does
is
there?
Frankly,
you
do
not
need
to
worry
about
what
is
a
firmware
level
island
and
what
is
the
system
inside
that?
B
B
It
may
take
a
week
more
than
a
traditional
system,
which
is
called
as
do
you
buy
everything
separately
and
do
it,
but
whereas
in
this
everything
is
factory
integrated
validated
the
image,
what
we
use
is
validated
by
HPE
and
also
ASAP
engineering
as
well.
Now
this
the
ownership
comes
from
HP.
I
am
going
to
just
cover
little
later
about
that.
So
this
is
one
what
you
can
take
note
of
I,
don't
know
whether
the
market
share
in
248
16
circuits.
B
What
we
do-
and
this
is
available
with
Intel's
e7
processors-
okay,
which
is
the
latest
generation
e7,
has
four
processors,
then
the
last
one
is
mission-critical
availability
which
I
will
just
park
because
I
want
to
just
cover
that
later.
So
what
HPE
provides
is
that
we
have
different
offerings,
as
we
can
see
here.
I
want
to
have
on
premise
and
that's
what
what
we
see
and
also,
if
you
want
to
have
hybrid,
which
the
previous
person
transfer
was
selling
was
telling
about.
This
is
a
hybrid.
B
If
you
look
at
which
we
cannot
ignore
the
reason
he
said,
you
also
need
to
have
your
on-premise
and
hybrid
as
well.
If
you
look
at
the
hybrid
which
supports,
we
have
something
called
as
flexible
capacity
which
currently
I
want
to
have
maybe
about
one
TB
care
system
and
tomorrow,
I
want
to
scale
it
to
60
B,
but
whereas
I
I
do
not
have
even
I
may
not
have
time
to
go
and
procure
at
the
time.
B
Instead
of
that,
I
will
keep
it
on
the
all
the
time
on
site
and
whenever
I
need
I,
just
enable
it
by
the
license
so
which
is
called
as
flexible
capacity
services,
which
is
part
of
the
solution,
then.
Finally,
if
you
look
at
on-demand
on
the
cloud
as
well,
what
we
have,
which
is
called
as
many
service
for
ASAP
Hana
and
ASAP
Hana
as
a
service.
B
So
all
these,
if
you
look
at
what
comes
with
all
of
them,
is
that
factory
integration
and
factory
integration,
which
is
combined
with
the
on
say,
whatever
factory
integration
we
do
on-site,
you
will
have
to
give
some
of
the
environment
variables.
It
may
be
an
IP
address.
It
may
be
your
usernames
credentials,
all
of
them
which,
although
all
of
them,
will
be
captured
and
which
can
be
deployed.
It
helps
you
to
reduce,
maybe
month
or
two
months
it
takes
for
you
to
deploy.
B
B
Actually,
we
have
a
couple
of
options
available
here,
as
you
can
see
here
something
Taylor
data
center
integration.
What
that
means
is
that
you
may
already
have
some
of
the
components
may
be
a
storage
or
some
of
the
components
elements
you
already
have
in
your
on-premise.
If
you
wanted
to
use
that,
then
you
will
go
for
the
Taylor
data
center
appliance,
okay,
so
which
is
more
tailored
for
the
particular
environment.
B
Okay,
the
performance
on
Intel,
the
latency
is
or
the
response
times
which
we
guarantee
with
the
appliance,
because
it
is
a
completely
controlled,
enrollment,
certified
and
validated
by
HPE
and
ASCAP.
The
second
one
is
fostered
time
to
value
which
I
mentioned.
We
do
not
do
the
do-it-yourself
approach
on-site
everything
we
had
done
at
the
factory
and
factory
when
I
tell
this
really
very
experienced
lost
20
30.
40
years
we
had
been
building
systems
so
the
same
lines.
B
What
we
you
for
the
images,
what
we
have
for
essay
p,
then
the
lowest
lifetime
tseebo
single
point
of
support,
which
I
will
just
completely
later
so,
along
with
this.
What
also
we
have
is
that
we
have
something
called
as
service
got
for:
relax
okay
service
got
for
ASAP
extension.
What
it
does
is
that
it
helps
you
to
keep
your
system
or
application
available.
B
B
So
in
this
how
fast
it
is
possible
for
you
to
bring
up
the
applications,
so
the
the
service
got
extension
for
ASAP,
which
helps
to
do
that,
which
is
a
software
component
again
service
got
feel
for
linux,
which
is
not
a
newer
software
which
is
there
with
us
almost
about
twenty
plus
years
we
have
been
using
service
guard
for
unix
and
the
same
codes.
What
we
use
as
a
service
guard
for
linux
as
well
so
which
is
again
20
years
plus
really
very,
very
well
proven
so,
which
is
available
not
at
the
operating
system
level.
B
As
an
availability
at
the
application
level,
then
this
is
a
loss,
one
which
is
called
as
center
of
excellence.
What
we
is,
we
don't
treat
ASAP
hora
installation
as
a
traditional
database
or
application
installation-
okay,
and
we
don't
treat
this
as
a
general
hardware
installation
as
well.
You
end
up
this
road
about
three
four
kilometers.
We
have
a
center
of
excellence,
which
is
sitting
here
called
Jia
tech
park.
There
is
a
specialized
routine,
which
is
actually,
which
is
a
virtual
team,
even
though
which
is
based
out
of
here.
B
They
connect
with
with
ASAP
in
gentleman
as
well
and
Australian
team
and
the
used
it's
a
virtual
team.
They
follow
the
Sun
model,
that's
how
they
operate.
What
this
team
does
is
that
whenever
there
is
a
call
logged
for
ASAP,
hana
appearance,
so
ET
is
going
to
hit
the
center
here
and
what
that
means
is
that
they
know
exactly.
What
is
that
you
are
running?
B
What
is
a
forum
where
you
run
and
what
is
the
way
special
mirin
and
what
is
a
database
version
you
run
and
operating
system
they
have
completely
and
with
the
experience
and
they
expose
whatever
they
would
have
received
and
engineering
validations.
They
know
what
could
be
the
reason
and
wat
ER.
They
should.
Whatever
the
reasons
you
are
called,
and
it
will
be
much
faster
for
them
to
resolve
as
well,
and
it
is
combined
with
something
called
as
insight,
remote
support,
which
is
part
of
all
our
systems
and
what
it
does.
B
Is
it
it's
kind
of
call
home
whenever
there
is
a
failure?
Happens,
it
automatically
locks
a
call
with
Hewlett
Packard
enterprise.
So
with
this,
what
you
see
is
that
you
do
not
need
to
go
to
multiple
teams.
Hpe
is
a
single
point
for
you
to
contact
whether
it
is
a
hardware.
There
is
an
operating
system
and
the
tie-up
with
ASAP
what
we
have
the
collaboration
with
ASAP,
what
we
have
at
the
engineering
level,
what
we
work
with
them
will
be
able
to
resolve
our
issues
much
faster
to
bring
your
applications
life.
B
So
this
is
another
one,
which
is
a
growing
example
of
what
we
are
doing
in
this
two
thousand
four
hundred
plus
and
counting.
So
these
are
some
numbers
which
you
can
see
to
yourself
as
well,
so
here
I
want
to
thank
you
and
also
summarize
the
first
part.
What
I
covered
is
about
the
composable
infrastructure.
So,
as
I
mentioned,
the
compressible
infrastructure,
we
have
three
guiding
principles:
one
needs
it.
The
fluid
resource
pools,
the
other
one
is
software-defined
your
software
different
m
plates.
B
The
third
one
is
about
the
unified
APA,
which
is
a
single
code
which
helps
you
to
apply
everything
which
is
a
compatible
infrastructure.
The
second
part
we
covered
about
yes,
ap
Hana,
why
hpe
for
acp
hana?
Ok,
so
these
are
the
things
what
I
covered.
So
we
are
where
I
am
joined
by
onam
here
and
also
there
were
here.
Three
of
us
are
here
from
keyword,
Packard
Enterprise.
We
are
going
to
be
around
here
doing
lunch
time,
so
you
can
also
custom
questions.
B
A
C
B
We
know
you
know
they
know
very
well.
You
know
these
from
IBM,
so
the
question
is
about
the
composer
infrastructure.
The
possible
infrastructure
is
an
infrastructure
which
is
going
to
host
your
physical
workloads.
It
is
going
to
host
your
virtual
workload
and
can
be
hyper
converged
as
well
and
also
the
containers.
Basically,
you
can
put
everything
in
that.
That
is
not
going
to
be
just
hyper
converged
for
hyper
converged.
We
have
a
separate
appliance,
which
is
called
as
hyper
converged
380
so,
which
is
a
to
you
box.
In
that
you
will
have
lot
of
VMs.
B
We
can
do
that,
so
that
is
hyper
converged,
but
whereas
this
is
a
blade
server
architecture
in
which
you
can
have
physical
virtual
and
contains
see
HPE,
what
we
want
to
do
is
it
we
wanted
to
go
along
with
the
industry.
One
is
that
we
want
to
do
pioneer
in
the
industry
the
way
how
we
had
done
the
blade
servers
way
back
in
nineteen.
Ninety
nine,
then
we
introduce
the
c-class
weights
in
2004,
the
same
thing
available
for
even
yes,
ap
horn
as
well.
B
Now
what
we
are
going
to
launch
next
is
a
compressible
infrastructure
and,
at
the
same
time,
what
we
are
seeing
in
the
industry
is
that
the
virtualization,
which
is
prevalent
for
lost
10
years,
we
are
seeing
adoption
of
containers
in
the
last
few
years
right,
you
are
seeing
radar
curves
on
the
containers
which
helps
you
to
put
more
workload
in
a
given
server
host.
So
what
we
do
is
that
by
end
of
this
year,
every
Hewlett
Packard,
Enterprise,
Server,
shipped
out
of
factory,
will
have
the
containers
which
is
license
and
also
pre-installed.