►
Description
Guest Speaker: Harold Wong, Senior Software Development Engineer, Microsoft Azure
Deploying OpenShift in Azure isn’t that radically different than deploying in another cloud provider or on-premises. There are infrastructure items that will need to be configured in Azure that has some uniqueness to it. Although you can do all the work manually and then install OpenShift via Ansible Playbook, the easier way is to take advantage of Azure ARM templates to help automate the deployment of all the “stuff”. In this briefing, Harold Wong will walk us through a live demonstration of how to use some existing ARM templates to deploy OpenShift Origin and OpenShift Container Platform in an automated fashion.
A
A
Good
morning,
everyone
and
welcome
again
to
another
openshift
Commons
briefing.
Today,
we're
really
pleased
to
have
with
us
from
Microsoft
Harold
Wang,
who
is
one
of
the
lead
child
architects,
working
with
red
hat,
on
making
OpenShift
work
wonderfully
on
Azure
and
he's
going
to
be
regaling
us
with
stories
of
how
to
do
that
and
talk
through
using
what
they
call
Quick
Start
templates.
So
without
any
further
ado,
I'm
going
to
let
Harold
introduce
himself
in
this
topic.
A
B
Perfect
so
yes,
my
name
is
Harold
Wong
and
I
am
with
Microsoft.
I
am
what's
called
a
cloud
architect,
or
sometimes
my
title
could
also
be
Technical
Evangelist.
Ultimately,
what
I
do
is
I
work
with
partners
to
make
sure
that
their
products
or
to
help
them
get
their
products
working
in
Microsoft,
Azure
correctly
or
to
put
things
into
the
marketplace.
B
B
So
then
I
guess
it'll
just
make
sense
for
me
to
keep
on
going
and
I
have
a
few
slides
so
that
I
can
talk
through
a
few
things
first
and
then
I
will
spend
the
majority
of
the
time
demoing
and
and
walking
through
what
it
actually
takes
to
install
openshift
on
Azure.
So
if
you
look
at
openshift,
openshift
has
a
lot
of
infrastructure
components
that
are
required
right.
You
need
a
VM,
you
need
networking
components
and
so
I
just
wanted
to
put
simply
up
on
the
slide.
B
What
are
some
of
the
core
adder
components
that
will
need
to
be
deployed
right,
so
you're
going
to
need
to
deploy
your
VMs,
that
you
can
deploy
your
master
nodes
and
your
infrastructure
nodes
and
your
application
nodes
and
so
forth.
So
that
might
be
three:
it
might
be
30.
It
might
be.
You
know
a
hundred
VMs
all
depending
on
the
size
of
the
cluster
you
want
to
deploy
with
those
VMs
you're
gonna
need
to
deploy.
You
know,
network
interface
cards
and
so
forth,
as
well
from
a
networking
perspective.
You'll
need
a
virtual
network.
B
I
know
I'm
going
out
of
order
in
that
virtual
network.
It's
essentially
a
private
virtual
network
in
Azure,
where
you
create
subnets,
and
then
you
put
the
VMS
on
those
subnets
all
right
within
that
for
access
from
the
internet
and
whatnot
you'll
probably
need
low
balancers.
So
we
do
have
adder
load
balancers
and
with
these
low
balancers
you
will
create
a
probe
that
will
check
for
the
health
of
a
connection.
Then
you'll
create
low
balancing
rules
using
those
probes.
B
So
if
I've
got
one
public,
IP
associate
with
a
low
balancer,
that's
gonna
low
balance,
three
master
nodes
behind
it
I
would
create
a
low
balancing
rule
for
the
console
access
right,
port
84
43.
If
I'm
going
to
do
cockpit
for
90
90
and
whatever
else
you
might
need,
you
can
create
NAT
rules
so
that
you
can
allow
incoming
traffic
such
as
SSH.
B
If
you
want
to
expose
SSH
directly
to
the
master
nodes,
then
you
would
create
a
NAT
rule
that
says:
I
want
port
2200
to
point
to
port
22
on
master
node,
one
and
so
forth.
You
will
also
need
network
security
groups
which
allow
you
to
lock
down
traffic
and
say
I
only
allow
certain
types
of
traffic
to
this
set
of
VMs,
or
this
set
of
this
particular
subnet.
So
network
security
groups
allow
you
to
control
what
type
of
network
traffic
is
allowed
in
as
well
as
out
from
your
VMs.
B
A
public
IP
is
just
a
an
entity
that
allows
you
to
specify
whether
you
want
public
IP
access
to
a
given
VM
or
to
a
low
balancer
or
whatnot
right.
So
you
don't
have
to
assign
public
I
piece
of
every
individual
BM.
Probably
don't
want
to
do
it
and
I'll
show
you
I,
don't
actually
do
that.
We
only
due
to
the
low
balancer
so
that
you
have
access
to
the
low
balancers
for
master
access
or
access
to
the
router,
which
is
sitting
on
the
infrastructure
net.
And
then
you
do
need
storage.
B
So
all
of
these
VMs
have
OS
disks
and
data
disks
that
are
associated
with
them
and
you
need
to
have
storage
accounts
to
store
all
those
disks
for
I,
also
use
as
restore
or
for
the
sorry
for
the
docker
registry
that
we
deploy.
The
private
registry
I
do
use
Azure
storage,
so
I
provision,
Azure
storage
for
that
as
well,
and
then
we
link
it
so
that
you
have
persistent
storage
for
your
registry
all
right.
So
these
are
just
some
core
components.
So
I
wanted
to
make
sure
you
understood.
B
You
still
need
all
of
that
infrastructure
stuff.
However,
you
deploy
it
manually
or
automatically.
It
needs
to
be
deployed,
and
then
this
is
just
a
quick
diagram
showing
you
what
I
generally
deploy
using
my
templates
for
Azure
right
I've
got
a
master
subnet,
where
I
throw
in
my
master
nodes
I,
throw
in
my
infrastructure
nodes
I
also
have
one
VM
that
acts
as
the
internal
load
balancer
running
H,
a
proxy
for
internal
communication
with
the
master
nodes
and
then
I
have
application
knows
that
deploy
to
a
node
subnet,
and
you
can
see.
B
I've
got
two
low
bouncers
that
I
deploy
the
ports
that
are
exposed,
there's
a
public
IP
on
in
front
of
each
one
of
those
and
then
the
the
NAT
rules
or
the
ports
that
are
open
so
that
you
can
gain
access
as
appropriate
and
then
in
terms
of
installing
OpenShift
I.
Don't
think
I
need
to
explain
how
to
install
OpenShift
I
just
put
this
down
so
that
I
can
make
it
clear
that
installing
openshift
in
azure
is
really
no
different
than
installing
OpenShift
in
your
on-prem
datacenter
in
AWS
in
google
cloud.
B
It
doesn't
really
matter
right.
If
you
can
set
up
infrastructure
somewhere,
you
can
install
OpenShift
in
the
exact
same
manner.
So
you
would
install
your
rel
instance.
You'd
install
all
the
necessary
tools,
create
your
config
files,
and
then
you
run
the
open
ship,
ansible
playbook
and
however
long
it
takes
for
that
to
run.
You
know,
10
minutes,
30,
minutes,
40
minutes.
Depending
on
how
many
cluster
nodes
you
deploy,
it
probably
takes
a
little
bit
longer.
Then
you
have
your
open
shift
cluster
up
and
running
right.
B
B
The
install
of
openshift
or
you
can
create
what's
called
arm
templates,
where
you
define
the
stuff
that
you
want
to
deploy,
you
create
all
the
necessary
scripts
and
in
the
arm
templates,
you
say,
go
run
these
scripts
and
then
you
answer
a
few
questions
and
you
tell
as
you
take
this
script,
follow
this
arm
template
file
in
the
parameter,
answer
file
that
I
created
and
go.
Do
your
thing
and
I
walk
away
and
I
come
back
later,
and
it's
all
done
right.
That's
fully
automated
there's
a
few
pre
steps.
B
I
have
to
do,
but
for
the
most
part
it's
an
automated
install,
and
so
what
I
actually
want
to
do
in
the
rest
of
this
time
is
walk
through
beginning
to
end
what
it
would
take
to
use
an
existing
arm.
Template
I'm,
not
asking
you
to
go,
create
one
I'm,
not
gonna!
Show
you
how
to
create
one,
but
I
will
show
you
the
templates
that
I've
created
the
scripts
that
are
used
and
if
you
want
to
deploy
openshift
origin.
B
The
very
first
link
we'll
take
you
to
a
what's
called
a
as
a
QuickStart
template
that
deploys
openshift.
I
am
gonna,
say
right
now
that
is
not
100%
working
and
it's
only
deploying
origin.
1.3
I
have
not
updated
that
one.
That's
in
my
to-do
list,
I've
been
spending
more
of
my
time
getting
open
shift,
container
platform
working
correctly
and
and
fully
functional
and
whatnot.
So
that
is
in
my
own
repo
and
that's
the
one
I'm
gonna
pretty
much
walk
through.
So
let
me
go
ahead
and
break
out
of
the
slides.
B
B
B
I
guess
it's
just
a
little
bit
delay,
but
hopefully
everybody
can
see
my
my
chrome
and
this
one
is
the
Azure
QuickStart
template.
You
can
see
I
only
something
was
updated
14
days
ago,
because
I
had
to
correct
an
error
in
a
script.
This
one
takes
a
little
bit
longer
because
I
don't
control
this
repo
and
every
time
I
make
a
change
to
it.
I
have
to
go
fight.
Somebody
internally
to
say:
please
merge
my
change
in
and
so
either
way
this
one
I'm
hoping
to
have
fully
updated.
B
B
On
this
first
right
in
here,
you'll
see,
there's
a
parameter
section
where
I
decide
define
all
the
parameters
that
I
accept,
including
VM
size.
I
can
even
say
you
know,
which
ones
are
the
allowed
sizes
define
this
size,
admin
username,
so
I
asked
for
a
bunch
of
different
inputs
and
then
I
define
a
bunch
of
variables
that
I
end
up
using
things
that
I
don't
need
input
for,
but
you
know
I
build.
B
There
are
things
that
are
needed,
like
the
name
of
the
host,
so
I
create
a
bash
and
host
there's
a
master
host
nodes,
the
infra
host
the
low
balancer
host
and
so
I
create
names
based
on
some
of
the
parameter
inputs
that
I've
asked
for
so
I
define
a
bunch
of
different
variables
that
that
I
end
up
using.
Let
me
scroll
down
over
here
and
then
the
key
thing
is
I,
define
all
the
resources
that
are
going
to
be
created.
Here
you
can
see,
there's
a
network
security
group,
that's
created
and
based
on
the
name.
B
This
is
for
the
bastion
host
right,
where
I
allow
only
port
22
to
connect
to
it
right
so
that
I
can
SSH
into
it
and
do
troubleshooting
and
make
sure
that
the
install
worked
correctly.
I
create
an
NSG
for
the
load,
balancer
hosts
and
there's
an
NSG
for
the
master
host,
the
infra
host
and
so
forth.
Alright,
so
I
define
all
of
the
different
resources.
Don't
worry
about
understanding
all
the
resources
right
now.
Just
know
that
I
define
them.
B
There's
documentation
that
you
can
read
to
really
understand
what
all
of
these
resources
are,
but
so
I
create
a
virtual
network.
I
create
all
the
different
storage
accounts.
I
create
a
public
IP
address
right,
whether
it's
a
static
or
dynamic
and
I
create
two
that
three
two
that
are
static,
one,
that's
dynamic,
I
create
these
availability
sets
right
and
then
one
of
the
things
I
wanted
to
show
when
I
create
my
virtual
machine.
B
You
know
it's
very
convoluted
and
complex
looking,
but
it
doesn't
matter
what
order
I
create
where
I
define
my
resources.
Ashur
will
try
to
deploy
them
all
in
parallel.
Unless
you
tell
it
hey,
this
resource
depends
on
this
resource
existing
first.
So
when
you
create
a
virtual
machine
before
the
virtual
machine
can
be
created,
you
do
need
to
have
the
NIC
created.
That's
going
to
be
a
social
with
that
VM
and
the
storage
account
so
that
the
OS
disks
and
whatnot
can
be
created.
So
I
define
all
the
resources
in
any
way
shape
or
order.
B
I
want
and
I
just
define
the
dependencies
so
that,
if
this
resource
depends
on
two
other
or
three
other
resources,
it
waits
for
those
resources
to
be
completed
before
it
moves
on
and
so
deploying
all
the
infrastructure
resources
straightforward.
Once
you
understand
how
to
use
this
template
and
once
again,
I'm
not
asking
you
to
create
it.
B
That
you
can
just
see
an
example
my
deploy
OpenShift,
so
I
have
a
script
that
essentially
sets
all
the
necessary
files
I
need.
It
creates
the
different
yamo
files,
I'm
gonna
use
for
the
different
playbook,
so
I'm
gonna
run.
It
creates
my
host
file
as
I
need
and
I
know.
This
is
a
little
hard
to
read,
but
you
can
see
there
are
different
pieces
that
are
being
done,
but
this
is
just
your
your
regular
host
file
that
you
would
create
for
installing
OpenShift.
B
You
may
not
use
all
of
the
same
parameters
I
use
here,
but
I
do
build
this
so
that
then
the
ansible
playbook
knows
what
to
do
all
right.
So
enough
of
that
jump
back
over
to
the
parameters
file.
So
this
one
here
is
just
a
parameters
file
that
explains-
or
it
kind
of
has
gears
where
you
fill
in
all
the
inputs
right,
the
VM,
the
master
VM
size
or
the
node
VM
size
and
the
instance
count
and
I
put
things
in
that
says.
B
Like
change
me
right,
these
are
the
things
you
need
to
change
or
set
the
different
values
for
so
what
I
did?
In
my
little
demo,
one
is
I
prefilled
a
bunch
of
stuff
in
alright,
like
my
VM
size,
I
want
to
use
the
public
DNS
name,
I
want
to
use
and
by
the
way,
these
need
to
be
unique,
so
be
very
careful
what
you
put
in
there
in
terms
of
their
their
DNS
names
that
get
published
in
DNS
this
one.
B
Since
its
container
platform,
I
am
asking
for
the
cloud
access,
username
and
password
and
a
pool
ID
so
that
you
can
I,
can
authenticate
to
your
Red
Hat
subscription
and
then
subscribe
or
register
all
of
the
instances
and
attach
to
the
pool
that
has
openshift
and
do
all
the
install
right.
We
put
in
the
public
key
I'll.
Explain
this
resource
group
thing
for
a
key
vault.
B
Actually,
I'll
explain
it
now,
that's
so
that
we
can
pass
in
the
private
key
in
a
secure
manner
and
then,
if
you
have
a
zip
tie
or
if
you're
gonna
use
a
a
custom
domain
like
for
me,
I
might
use
apps
that
we
OCD
dotnet
and
I'd
put
that
in
over
here
and
then
this
one
would
be
changed
to
custom
alright.
So
let
me
go
over
to
my
shell.
B
If
you
look
at
my,
is
that
if
you
look
at
the
repo
and
read
through
the
readme,
the
readme
does
say
you
do
need
to
generate
your
SSH
key
pair.
So
let
me
just
go:
do
that
real,
quick
right,
I'm
gonna
walk
through
this,
so
it's
in
my
directory
here
I've
got
all
these
little
JSON
files
that
I'm
gonna
use
so
I'll
do
the
SSH
key
Jen
I'll
just
do
ID
RS.
B
B
You
see
I've
got
my
ID
underscore
RSA,
my
ID
underscore
our
say:
dot
pug.
So
those
are
my
keys
and
if
I
keep
reading
through
it
says,
hey
here's
how
you
would
go
ahead
and
create
the
key
vault
right
and
I
provide
PowerShell
steps
as
well
as
a
sure
CLI
step.
So
you
do
need
to
install
the
address.
You
lie.
If
you
haven't
already
done
that
I'll
give
you
a
link
to
to
do
that.
But
let
me
go
ahead
and
do
the
azure
login.
B
Need
to
put
in
this
code
because
of
the
dual
factor,
authentication
mechanism
and
then
I
authenticate
here-
go
back
to
this
piece
and
hopefully
it
will
authenticate
shortly
and
there
we
go
so
now.
I'm
authentic
ated
into
my
address,
subscription
from
the
CLI
and
I
am
just
gonna
go
ahead
and
follow
these
steps.
Essentially
that
say:
here's
how
you
create
the
key
ball
to
store
the
key.
It's
not
that
difficult!
B
It
does
require
some
typing,
so
I'm
gonna
do
a
sure
group
create,
and
if
you
really
want
to
learn
more,
you
can
look
up
documentation
on
the
azure
CLI
commands,
but
these
are
the
basic
ones
for
creating
a
resource
group.
So
I'm
gonna
do
as
your
group
create.
Let's
see
our
G
demo
West
us.
You
know
what
let
me
just
make
sure
I
don't
already
have
that
you.
B
B
B
B
B
Id
underscore
RSA,
so
I'm
going
to
read
in
the
private
key
and
inject
it
into
that
secret
and
now
I
need
to
do
as
your
Eve
alt
that
policy
I
need
to
allow
this
key
Balt
to
be
used
for
template
deployments.
So
I'm
gonna
do
set
policy.
U
HW
demo
vault
one
and
then
enabled
for
template
deployment.
True.
B
So
you
can
see
that
it
is
holding
my
my
private
key
appropriately.
So
that's
the
very
first
step,
so
the
next
step
is
and
I'm
not
gonna.
Do
this
I
already
have
one
that's
created,
but
we
would
go
in
and
edit
the
azure
deploy
parameters
follow
with
all
the
appropriate
things.
Like
my
ssh
public
key,
I
would
put
in
my
you
know.
This
thing
would
be
what
HW
demo
key
vault
and
so
forth
right.
So
I'm
not
gonna,
do
that
here.
Instead,
I
will
just
go
ahead
and
go
back
to
my
show.
B
B
If
I
typed
everything
properly,
you
can
see
hey
now
it
started
or
it
created
a
deployment
and
if
I
go
back
to
my
GUI,
it's
just
easier
to
show
on
a
demo
like
this,
you
can
see
the
resource
group.
Five
zeroes
open
shift,
one
I
come
over
here.
You
can
see
that
resources
are
now
starting
to
be
deployed
right.
All
of
these
network
security
groups.
There's
a
public
IP
over
here.
This
thing
called
availability
sets
my
virtual
network.
If
I
sit
here
and
refresh
you'll,
see
a
bunch
of
other
things
slowly
pop
up.
B
If
I
look
here,
you'll
see
it
says,
deployments
and
there's
one
thing
deploying
right
now:
if
I
click
over
to
here,
you'll
see
the
deployment
name,
I
called
it
open
shift
three
four
and
if
I
click
on
it
you'll
see
the
status
of
everything
and
over
here
you'll
see
that
there
are
inputs.
So
these
are
all
the
inputs
that
I
put
in
anything.
That
is
a
security
thing
like
a
password
I,
don't
display
all
right,
so
that's
hidden,
and
then
you
can
see
the
status
of
what's
going
on
anything
green
means
those
are
already
completed.
B
B
So
if
I
refresh
hopefully-
and
this
will
take
a
little
bit
of
time
so
I'm
not
gonna-
sit
here
during
the
whole
course
of
this
and
wait
for
it
to
complete.
Instead,
you
know
how
it
goes
with
demos.
I've
got
something
in
the
oven,
though
last
night
I
deployed
to
a
resource
group
called
OCP,
3/4
gee
and
you
can
see
similar
things.
There's
a
you
know:
bastion
node
public
IP,
there's
a
bunch
of
network
security
groups.
B
I've
got
my
deployments
and
that
it
says
succeeded.
You
can
see
this
one
has.
This
is
the
one
I
was
showing
you
in
the
other
one
where
I
called
it
open
shift,
3,
4
same
concept,
you'll
see
all
the
input
parameters
that
were
supplied.
It
you'll
see
all
the
things
here
are
green,
but
one
thing
after
it
completes
that
you'll
see
here
and
when
the
one
I
just
started
completes
I'll.
Have
it
there
as
well
as
I
output,
some
key
things
so
that
you
know
how
to
connect
to
this
instance.
B
B
B
Why
can't
get
the
metrics
right
now,
but
you
can
see
that
I've,
the
registry
deployed
there's
the
router
deployed
and
if
I
come
in
and
look
at
the
docker
registry
and
look
at
the
environment
variables,
what
I
did
as
part
of
the
automated
deployment
is
I
automatically
use
Azure
storage.
So
you
can
see
I
set
the
environment
variable
for
registry
storage
to
be
a
sure,
and
then
there
is
a
account
name
and
an
account
key
so
that
we
can
access
it
and
then
I
created
a
folder
called
registry
in
there.
B
This
one
here
and
if
you're
not
familiar
with
the
azure
portal,
it
I
know
I
might
be
walking
a
little
bit
fast,
but
this
is
not
the
time
to
actually
go
and
give
you
a
full.
You
know
tutorial
of
the
portal,
but
other
way
you
can
maneuver
around
in
here,
as
well
as
from
the
command-line,
it's
just
easier
to
show
in
a
in
a
demo
a
nice
little
GUI.
So
you
can
see
that
this
storage
account
had
a
registry
container
or
folder
created
and
in
there
there's
nothing
right
now.
B
B
And
this
will
take
just
a
few
minutes
to
complete
I
hope
and
what
I
wanted
to
show
is
once
it
starts
going
is
we
should
be
able
to
see
the
fact
that
the
registry
actually
is
being
used
over
here
so
well?
Let
that
run
I'll
come
back.
Let
me
just
open
another
portal
here:
real
quick,
so
I
can
bounce
back
and
forth
between
the
two
screens.
B
Let's,
let's
just
check
on
the
status
of
this
deployment,
see
how
it's
doing
all
right,
so
you
can
see
that
my
VMs
were
created.
It's
actually
now
deploying
or
running
scripts
to
prep,
all
the
nodes
and
so
forth.
Things
are
coming
along
good.
Why
don't
I
take
some
time
right
now,
while
we
wait
for
this
quick,
kick
my
PHP
example
to
deploy
and
answer
some
questions
so.
A
B
Yeah,
absolutely
so
let
me
in
fact,
let
me
show
you
in
my
little
github
repo
after
you
read
through
the
instructions.
There's
this
thing
that
says
deploy
to
Azure
if
I
click
on
that
it'll
literally
take
me
to
my
Azure
portal.
Take
the
contents
of
that
template
file
and
inject
it
into
a
what's
called
a
template
deployment,
and
now
from
the
GUI
I
put
in
the
saying
you
know,
I
enter
the
name
of
the
resource
group.
B
I
want
to
create,
and
the
nice
thing
here
is
anything
where
I
put
a
like
a
list
of
things
that
you
can
select
from
you
just
literally
select
from
the
list.
So
here
I
would
do
HW
master,
DNS,
HW,
infra
DNS,
something
for
the
master
count.
I
can
choose
one
or
three
or
the
node
instance
count.
I
can
choose
one
through
30
solitude
15
right
for
the
dis,
sighs
I,
give
you
three
options:
I'll
choose
the
128
there.
It
is
all
right,
so
I
can
definitely
just
answer
these
questions
here.
A
B
A
B
There
there
are
pointers
that
go
back
to
it,
so
if
I'm,
looking
at
my
github,
just
bring
this
back
up
in
this
a
sure
deploy
JSON
file
which,
if
I
come
over
here,
you'll,
see
there's
this
artifacts
location.
It
points
to
my
github
repo
under
master,
which
is
essentially
here.
So
whenever
a
script
runs,
it
literally
pulls
it
from
this
scripts
directory.
A
B
B
This
one
is
quote-unquote
the
official
stuff
right,
the
ones
that
Microsoft
somebody
at
Microsoft
has
officially
blessed
and
said
it
does
work
right,
not
that
we
necessarily
support
it,
but
it
does
work,
and
so
this
one
I
do
plan
to
put
my
openshift
container
platform
templates
into
the
QuickStart
templates,
as
well
as
updating
the
OpenShift
origin,
one
that
I
created.
This
is
the
one
I
created
as
well.
Okay,
it's
just
that
in
order.
A
B
The
way
I
do
things
with
that
key
vault,
which
is
a
requirement
that
the
QuickStart
template
team
put
on
me
anyway,
is
to
put
anything
into
the
QuickStart
template.
They
need
to
use
this
key
ball
and
because
of
the
key
vault
usage,
the
automated
testing
fails
every
single
time,
because
it
can't
generate
that
key
ball
automatically
for
the
test,
so
it
will
fail
and
then
I
have
to
go.
B
B
B
This
it,
no,
it
failed,
so
I
must
have
gotten
something
wrong.
Oh
you
know
what
I
did
my
DNS
name
I
forgot
to
change
it,
so
it
was
already
in
use,
but
it
would
not
complete
just
because
this
normally
takes
if
I'm,
especially
with
15
agent
nodes,
it'll,
probably
take
about
35
to
45
minutes
to
complete,
so
it
doesn't
happen
in
10
minutes.
B
B
Where
does
he
specify
that
right
here,
mm-hmm,
you
know,
say:
it'll
made
deploy
into
retry
59
times
before
it
completes
on
the
sixtieth,
so
that
just
adds
time,
because
there's
a
wait
period
between
each
retry
good
to
know
yeah.
So,
let's
at
least
go
see
if
my
registry
out
there
so
member
I
deployed
that
make
my
PHP
app
you
see
in
the
azure
storage
account
there
is
the
cakephp
my
example
I
just
wanted
to
show
that
the
layers
are
pulled
in
and
it
is
stored
in
in
the
storage
account.
A
B
Yeah,
so
if,
if
you
have
any
questions,
feel
free
to
reach
out
to
me,
my
email
address
is
Harold
long
at
Microsoft
comm,
and
if
you
have
any
feedback
you
would
like
to
include
into
this
particular
repo
before
it
gets
into
the
QuickStart
templates.
Please
let
me
know
as
well,
because
I
can
make
those
change
his
way
easier
now
versus
in
a
month.
So.
A
What
we'll
probably
do
is
I'll
I'll
post
this
on
our
open
ship,
vlog
and
we'll
see
what
we
get
for
feedback
on
it.
I
really
is,
as
Steve
is
saying,
very
nice
to
see
this
running
on
Azure
and
thank
you
very
much
for
all
the
work
that
you've
obviously
done
making
it
work
so
smoothly.
So
you
know
hopefully
get
a
few
more
folks
going
on
this
I
know
we
have
one
group
of
folks
down
in
Brazil.
We
have
to
get
up
cloud
folks
or
running
on
Azure,
quite
happily
hosting
a
public
pause
there.
A
So
on
we
know
this
is
the
one
of
them
more
viable
options
for
running
this
open,
shifted
scale
so
fully
we'll
get
some
more
feedback
and
the
P
more
people
working
on
this
with
you
and
you'll
get
some
more
feedback
at
the
azure
at
the
open
ship,
Commons
gathering
in
Berlin
in
a
couple
of
weeks
too
as
well.
So
thank
you
very
much
for
doing
this.
Oh
you're.
B
A
Now
they
know
who
you
are
Harold
so
watch
out.
They
want
to
feedback
pretty
fast.
So
thank
you
again
for
a
particular
time
to
do
this,
and
this
video
should
be
posted.
If
you
can
send
me
a
couple
of
links
to
form
the
different
repos
that
will
be
great
and
you'll,
get
it
all
up
there
and
get
you
some
more
feedback,
and
hopefully,
if
you're
commenting
and
giving
you
some
issues
as
well.