►
From YouTube: Deploying vSphere Integrated Containers Appliance v1.3.1
Description
See our updated video for v1.4.0 at https://youtu.be/DKR7ijfEHis
This video tutorial demonstrates the deployment of the vSphere Integrated Containers (VIC) appliance version 1.3.1 with a user provided TLS certificate.
For more information please visit the vSphere Integrated Containers product page:
https://www.vmware.com/products/vsphere/integrated-containers.html
A
Hi
I'm
Andrew
Chen
tech
lead
for
the
vSphere
integrated
containers
appliance
today.
I'll
demonstrate
the
installation
of
Davich
appliance
version,
131
I've
downloaded
the
OVA
for
the
Vic
appliance
and
we'll
start
its
deployment
using
the
Flex
based
vSphere
web
client,
html5
client
and
the
legacy
Windows
client
are
not
supported
for
initial
installation.
A
You
may
later
use
the
html5
client
with
the
Vic
plug-in
to
manage
your
vSphere
integrated
containers,
virtual
container
hosts
to
deploy
I
select,
the
OVA,
provide
a
VM
name
and
data
center
or
folder,
and
select
the
compute
resource
where
the
appliance
will
be
run.
I
accept
the
license
and
select
a
datastore.
A
The
Vic
appliance
requires
a
minimum
of
80
gigabytes
of
storage,
20
gigabytes
each
for
the
system,
disk
logs
database
and
application
storage,
biggest
consumer
of
storage
on
the
Vic
appliance
is
the
container
registry.
If
you
plan
to
store
more
than
20
gigabytes
of
container
images,
the
size
of
this
disk
can
be
increased.
A
The
other
disks
can
also
be
resized.
According
to
your
usage,
another
consideration
when
selecting
the
datastore
is
for
future
upgrades
of
the
Vic
appliance.
The
upgrade
process
requires
deployment
of
the
new
Vic
appliance.
So
the
datastore
needs
to
be
able
to
accommodate
both
the
old
appliance
and
the
new
appliance
during
the
upgrade
process.
A
future
video
will
demonstrate
the
entire
upgrade
process.
A
Next
select
a
network,
the
Vic
appliance
has
one
network
interface.
This
interface
is
used
for
both
management
and
client
interaction.
The
appliance
needs
to
be
able
to
communicate
with
the
vCenter
server
and
the
PSC
for
management
functionality.
The
administrator
also
initializes
the
appliance,
as
we
will
see
later
in
this
demo
through
a
web
interface
on
the
appliance
for
client
usage
users
of
the
container
registry
and
container
management
portal
access
these
services
that
are
running
on
the
appliance.
A
Additionally,
the
appliance
must
be
reachable
by
container
host
that
wish
to
use
the
container
registry.
During
the
customization
step,
we
can
configure
the
settings
for
the
appliance
for
a
basic
install.
You
may
accept
the
defaults
for
all
values
and
only
provide
a
root
password
for
the
appliance
by
default.
The
appliance
uses
DHCP
to
obtain
network
configuration
and
Auto
generates
a
self-signed
TLS
certificate.
Also
note
that
SSH
is
enabled
by
default,
as
this
is
used
for
debugging
and
when
upgrading
the
appliance
in
the
future.
A
To
SSH
to
the
appliance
use
the
username
root
and
the
root
password
that
you
set
in
this
screen
later
updates
to
the
root
password
must
be
made
from
within
the
operating
system
by
SS
aging
into
the
appliance
for
this
demo.
I
will
go
over
the
available
deployment
options
and
use
a
custom
TLS
certificate
to
use
a
static,
IP
address,
provide
the
IP
address,
subnet,
mask
default,
gateway,
DNS
servers,
domain
search
path
and
fully
qualified
domain
name
of
the
appliance
here.
If
these
fields
are
left,
blank
DHCP
will
be
used
for
container
registry.
A
You
may
configure
the
port
that
the
registry
and
notary
listen
on
for
the
management
portal.
You
may
configure
the
port
that
the
management
portal
listens
on
and
provide
a
custom
TLS
certificate
by
providing
the
certificate
key
and
CA
cert.
This
certificate
will
also
be
used
for
the
registry
I've
generated
a
CA
private
key
and
certificate
here
paste
the
PEM
encoded
values
into
the
appropriate
fields.
A
A
A
Note
that
the
value
you
pasted
for
the
certificate
in
section
4.2
will
be
presented
to
clients,
as
is
if
your
TLS
certificate
requires
an
intermediate
CA.
You
should
concatenate
the
one
or
more
CI
certs
with
the
server
certificate
to
create
the
certificate
chain
before
pasting
it
in
section
4.2
for
the
file
server,
which
displays
the
initialization
and
getting
started
page.
You
may
configure
the
port
and
provide
a
custom
TLS
certificate.
I
will
use
the
same
certificate
as
I
used
for
the
management
portal.
A
Finally,
example:
users
are
created
in
the
platform
services
controller
during
the
appliance
deployment.
This
allows
for
easy
testing
of
the
different
personas
that
can
access
the
container
management
portal
and
container
registry.
You
may
uncheck
the
box
to
skip
the
creation
of
these
example.
Users
review
the
configuration
and
click
finish
to
start
deployment.
The
speed
of
your
deployment
will
vary
depending
on
your
vSphere
environment
and
network
conditions.
A
A
A
As
we
can
see,
the
appliance
is
using
the
certificate
that
we
provided
during
deployment.
Once
appliance
services
are
started,
we
can
initialize
the
appliance
through
this
modal
on
the
getting
started.
Page
enter
the
vCenter
server,
location
administrator
credentials
and
if
using
an
external
PSC,
provide
those
details
as
well.
A
When
a
green
bar
is
displayed
at
the
top
of
the
getting
started
page,
the
appliance
is
successfully
initialized.
If
a
red
bar
is
displayed,
appliance
Nishal
ization
has
failed.
If
the
page
is
refreshed,
the
red
bar
will
go
away,
but
the
appliance
remains
uninitialized.
On
the
getting
started
page,
there
is
a
link
to
the
Vic
documentation.
You
may
also
download
the
files
needed
to
deploy
a
VCH
contained
in
the
vSphere
integrated
containers
engine
bundle.
Finally,
we
have
a
link
to
the
container
management
portal.
A
A
We
can
see
that
this
screen
is
where
you
can
create
a
project
within
the
management
portal
under
registries
by
default,
docker
hub
and
the
registry
running
on
the
appliance
are
added
under
configuration.
You
can
download
the
registry
root
certificate.
This
is
needed
by
docker
clients
to
be
able
to
connect
to
the
registry.
If
using
auto-generated
self-signed
certificates
under
Identity,
Management
users
and
groups,
you
can
manage
users
roles
and
see
the
default
users
that
were
created
during
deployment.
A
When
we
later
have
a
virtual
container
host
deployed,
we
can
add
that
here.
This
will
enable
us
to
deploy
containers
to
that
VCH
through
the
container
screen
on
the
container
screen.
We
can
deploy
containers
by
specifying
the
container
image
container
name
and
the
command
to
run
thanks
for
watching,
and
you
can
find
out
more
about
vSphere
integrated
containers
at
github,
comm,
slash,
VMware,
slash,
Vic
product.