►
From YouTube: Automation of (Legacy) Telco platforms using IaaC Tools
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everybody
welcome
to
this
webinar,
in
which
we
will
talk
about
automation
of
telecommunications
platforms
and,
in
particular,
those
legacy
telecommunication
platforms
so
again,
hi
everyone,
hi
suavek,
hi
tomas.
So
what's
the
plan
for
today,
after
shortly
introducing
ourselves,
we
will
briefly
describe
what
cisco
broadworks
is
the
platform
which
we
are
going
to
automate
in
this
webinar,
we'll
discuss
briefly
the
tools
that
we
used.
A
What
was
difficult
in
this
in
this
in
this
undertaking
and
then
last
but
not
least,
we
will
show
you
a
complete
demo
of
automated
deployment
of
a
cisco,
broadworks
voice
platform.
Oh,
who
are
we
I
will
start
by
introducing
myself.
My
name
is
david
mielnick.
I
am
the
delivery
director
of
the
telco
service
unit.
Here
at
software
mind
we
carry
out
projects
related
to
collaboration,
code
control,
observability
and
automation
of
core
network
telco
platforms.
B
A
What
we'll
show
you
in
this
webinar
is
an
extract
of
a
much
wider
project
in
which,
of
course,
there
are
cloud
native
applications.
There
are
kubernetes
but,
like
we
said,
we
want
to
focus
on
legacy
telco
platforms,
and
this
is
what
we
we
are
going
to
discuss,
what
we're
going
to
show
you
and
then,
in
the
end,
we
are
going
to
demonstrate
the
deployment
of
automated
automated
deployment
of
a
cisco
broadworks
platform.
B
Soft
is
a
communication
software
platform
that
is
delivered
by
cisco.
It's
in
general,
it's
embedded
in
service
provided
network
and
provides
you
various
services
for
unified
communication,
communicators
for
mobile
users
for
sip
sip
trunks
for
sub
terminals
and
those
combined
users
with
a
massive
services
that
also
broadsoft
provide.
You
provides
you
you
may
build.
You
know
from
big
scale,
businesses
to
small
businesses.
You
know
full
fully
full
mesh
of
services
that
simply
drives
your
business
and
in
general
this
may
be.
B
The
services
from
broadsoft
are
offered
to
the
customers
right
and
you
know,
sometimes,
even
if
you
call
some
call
centering
example,
you
may
not
even
be
aware
that
you
use
bloodsoft,
because
you
just
call
in
transparent,
let's
say
way
and
you
you
reach
some
call
center
from-
I
don't
know
bank
or
any
other
enterprise,
and
you
you
don't
know
that
you've
been
served
by
broadside
right
now.
So,
let's
talk
about,
let's
say
lots
of
components
that
we
will
use
today
during
our
demo.
B
B
So
today,
on
doing
our
demo
we'll
build
application
server
as
a
cluster
setup.
We
have
also
a
media
server
mainly
is
rtp
streams.
So
whenever
you
have
any
com
conferences,
you
know
calls
whenever
you
have
any
announcement
head
from
broadsoft.
Many
are
several
involved
network
server
is
something
additional.
It
simply
supports
application
server
and
other
elements
of
broad
soft
components
to
serve
traffic
rest
and
network
function.
B
Manager
is
something
that
is
nothing
strictly
involves
or
directly
involves
doing
the
the
call
service,
but
it
supports
operational
team
simply
to
monitor
broads
of
network
components
in
our
case,
we'll
use
nfm
as
a
license
broker,
because
you
must
know
that
broadsoft
is
a
licensed
software
and
before
you
proceed
with
lots
of
configuration,
you
need
provide
license,
and
for
this
purpose
we
use
a
network
function
manager
as
alliance's
broker.
B
So
we
have,
let's
say,
set
of
licenses
installed
on
the
nfm
and
we
use
a
api
simply
to
install
install
license
on
the
servers
that
we'll
have
in
this
demo.
B
B
Based
on
the
domain
right,
so
we
we
can
have
a
management
infrastructure
tools
and
some
configuration
management
tools.
As
you
can
see
on
these
charts,
we
have
several
tools
that
can
even
overlaps
domains
right,
so
some
some
of
tools
may
operate
on
management,
infrastructure
and
and
managing
and
application
manager
configuration
as
well,
and
but
there
are
also
some
rather
some
other
tools
that
are
focused
mainly
on
the
single
domain.
B
A
Swabbik,
it
there's
an
apparent
question
why
we
have
chosen
ansible
entire
farm
and
not
only
ansible.
If
we
see
that
it
also
covers
the
infrastructure
management
area.
B
In
general,
terraform
is
very
useful
for
management
infrastructure
and
I
will
tell
you
a
little
bit
more
about
the
terraform
and
probably
you
might
let's
say
guess
why
I
let's
say
I
choose
a
terraform
to
build
our
infrastructure.
B
B
Popularity,
it
might
be
also
a
point
right,
but
hopefully
that
on
the
next
few
slides,
we
will
go
a
little
bit
deeper
into
terra,
formal
ansible,
and
we
must
simply
discuss
it.
Why
we
decided
to
have
it
that
way:
sure,
okay,
okay,
so
regarding
terraforms,
so
extra
was
about
terraform.
B
So,
as
I
mentioned
before,
it's
rather
professional
infrastructure
tool
and
it
has
a
hcl
files
that
are
let's
say,
written
in
human
readable
form
where
you
may
simply
define
some
on-premise
or
cloud
resources
and,
moreover,
it
has
a
declarative
approach,
what
it
means.
What
is
behind
that,
in
general,
you
put
you
define
some
infrastructure,
so
you
described
some
infrastructure
inside
and
up
to
terraform
to
deliver
this
infrastructure
for
you.
So
we
don't
care
about
the
order.
B
We
simply
define
some
define
some
files
where
we
described
out
the
infrastructure,
even
if
it's
somehow
combined
a
little
bit
in
an
example
like
kubernetes
cluster
and
so
on.
So
this
is
a
very
let's
say,
a
big
advantage
from
our
perspective.
B
Moreover,
terraform
detects
the
state,
so
it
it
recognizes
what
element
were
created
and
it
simply
detects
the
state
of
this
element
later
on
and
another,
let's
say
big
advantage
from
my
point
of
view-
is
that
telephones
provide
diagnostics.
B
Okay,
so
let's
talk
about
about
ansible
a
little
bit,
so
it's
rather
configuration
management
tool
and
ansible
is
used
mainly
for
application,
installation
and
application
management.
Moreover,
it
might
be
used
also
for
your
operating
system
preparation,
because
it
may
simply
change
single
files,
single
lines
in
the
file
and
so
on.
So
it
tracks
also
those
and
decided
that
you
that
you
have
you
know
proper
configuration
inside.
B
Moreover,
it's
rather
approach
than
the
classified
what
it
means
that
the
order
of
our
tasks
in
the
playbook
is
important.
A
So
we
can,
I
can
see
already
that
there
are
some
benefits
of
of
of
why
we
have
chosen
ansible
for
someone
that
knows
how
the
installation
of
broad
works
is
arranged
and,
having
in
mind
that
the
operating
system
have
to
be
prepared
in
a
special
way,
according
to
the
prerequisites
and
and
installation
would
require
a
more
procedural
approach.
But
the
obvious
question
is
why
we
have
chosen
ansible
and,
for
example,
not
other,
not
other
application
and
configuration
management
tools
like
chef,
for
example,.
B
My
my
response
is
quickly
agentless
in
general.
Ansible,
from
my
point
of
view,
requires
only
ssh
connectivity,
while
with
other
tools,
we
have
to
also
install
some
agents.
So
it
brings
some
additional
efforts
on
the
environment
that
that
is,
let's
say,
provisioned
and
that's
why
we
used
ansible.
C
Yeah,
I
think
this
is
also
the
adventure
is
also
the
simplicity
of
its
configuration
files
yeah.
We
use
we
use
language
syntax
in
ansible
playbooks,
which,
which
is
well
known,
I
think
worldwide
in
id
world.
So
this
is
the
also
the
advantage.
A
B
Okay,
we
had
this,
let's
say,
challenges
or
steps
that
we
had
to
address.
So.
First
of
all,
we
have
to
choose
some
infrastructure
provisioning
so
regarding
we
need
to
choose
our
infrastructure
provider
and
the
tool
that
we
that
we
use
for
provisioning
management
right.
B
Second,
is
that
blocksoft
requires
some
additional
per
person
of
the
linux
system,
so
we
need
to
be
very
strict
in
scope
of
providing
linux
machine
and
it
should
be
configured
according
to
to
cisco,
cisco
broadworks
requirements.
B
Moreover,
we
have
to
also
install
third
party
installations,
so
what
it
means
that
we
should
provide
some
additional
software,
because
without
broad
bloodsoft
application
won't
be
installed
correctly.
B
Next
challenge
we
had
is
providing
broadsoft
software
itself
perform
the
installation,
and
then
blotson
has
also
post
install
tasks.
So
before
we
start
an
application
before
we
license
the
application
need
to
perform
some
additional
steps.
So
after
broads
of
ins
after
birth
of
installation,
extra
task
has
to
be
done
right,
so
extra
task
has
to
be
performed
before
before
server
is,
let's
say,
operational
and
ready
for
for
configuration.
So
this
this
task
has
to
be
also
addressed
for
us
and
then
next
challenge
is
to
proper
license
delivery.
B
As
I
mentioned
you
before,
we
have
an
fm,
so
we
need
to
somehow
combine
an
fm
to
provide
license
in
automatic
manner.
For
us
and
the
last
but
not
least,
probably,
a
brush
of
configuration
brosoft
do
not
support.
Doesn't
broadsoft
simply
doesn't
support
country
flat,
config
files
right?
B
B
And
what
is
important
here
is
that
we
decided
in
that
case
that
so,
if
we
are
not
able
to
provide
you
plot,
config
right,
like
in
an
example
for
apache,
you
may
simply
provide
some
template
with
the
config
and
apache
or
nginx
will
is
configured
properly
for
you
and
and
that's
what
you
want
to
here.
We
need
to
progress,
let's
say
figure
out
some
different
solution,
so
I
will
tell
you
a
little
more
how
we
address
it
on
next
slide,
so
how
we
challenge
the
addresses.
B
So
for
linux
system,
preparation
and
the
third
purchase
of
installation,
and
so
on,
we
use
ansible,
but
the
fact
that,
as
I
said,
that
it's
very
handy
for
configuring
operating
system
in
scope
of
very
single
and
very
detailed
way,
also
for
broadsoft
installation
and
post-install
task.
We
also
use
ansible
here
with
some
tricky
part
for
license
delivery.
B
Nfm
has
a
rest
api
that
can
be
used,
so
we
also,
let's
say,
put
some
parts
of
code
that
simply
addresses
issues
and
it's
triggered
by
ansible
this
communication
and
in
at
the
end
we
should
get
a
software
license
properly
and
process
configuration.
This
is
also
part
that
has
to
be,
let's
say
a
little
bit.
I'd
like
to
say
a
few
more
comments,
so
prosoft
browsers
applications
do
not
have
flat
config
files,
I
mean
it
have
they
they.
B
Let's
say
they
have
some
part,
but
in
general,
from
our
perspective,
to
come
properly
configure
board
bw
software
interface.
You
may
say
that
it's
kind
of
shall
and
being
in
front
of
of
the
shell.
You
may
simply,
you
know,
configure
all
all
required
changes
that
you
want
to
have
and
and
to
configure
properly
blush
of
applications.
B
So
if
you
are
not
able
to
provide
your
flat
files,
we
decided
to
use,
expect
right,
expect
script
and
this
excrypt
can
be
treated
as
a
config
file.
So
you
might
template
it.
You
might
you
know,
change
the
in,
let's
say
perform
all
required
changes
that
you
want
to
achieve
right
and
then
this
expects
which
is
delivered
to
that
to
the
server
and
executed
and
at
the
end
we
should
get
the
correct,
correct
configuration
inside
the
broadsoft
application.
B
I'm
not
sure
if,
if
everyone
is
let's
say,
if
everyone
know
what
what
expect
is
right,
so
maybe
we
could
say
a
few
words
about
expert
itself,
so
in
general,
expect
is,
is
a
tool
simply
that
allows
us
to
detect
what
is
let's
say:
output
right
and
depending
on
the
output
we
can.
B
We
can
define
some
input,
data
and
execute
them.
So
whenever
we
want
to,
let's
say,
put
some
put
some
script
that
simply,
let's
say
doing
a
tricks
like
we
would
be
in
front
of
the
shell
or
in
front
of
our
let's
say
computer.
B
B
So
in
general
approach
that
we'd
like
to
achieve
is
that
we
have
operator
with
ci
cd
tool
and
based
on
this
tool.
Ansible
or
terraform
is
triggered
with
proper
playbook
and
proper
template
inside
and
at
the
end,
we
should
achieve
opera,
let's
say
cisco,
broads
of
operation.
You
know
in
our
operational
style
state.
B
Additionally,
we
may
also,
as
you
can
see
here,
that
we
have
also
elasticsearch
to
you
know.
The
purpose
of
having
elastic
with
cisco
blossom
is
observable
observability.
B
So
today
we
mainly
focus
on
the
central
part
of
our
diagram.
So
we'll
show
you
how
you
might
simply
achieve
the
goal,
with
ansible
terraform,
to
build
a
cisco
bloodsoft
platform
and
ready
for
handling
traffic.
A
So
in
a
typical
project,
the
goal
that
we
want
to
achieve
is
to
have
the
deployment
of
broadworks
handled
in
the
same
way,
does
the
rest
of
the
code
and
the
rest
of
the
applications
so
trigger
from
the
cicd
and
then
handled
by
observability
tools.
But
for
the
purpose
of
this
demo,
we
will
deploy
the
platform
and
trigger
and
superscripts
by
by
hand,
basically
yeah
yeah.
B
Okay,
so
a
little
bit
more
about
the
architecture
here,
so,
as
you
can
see
on
the
top
of
the
screen,
we
have
a
two
application:
server
broadband
as
one
and
broadbox
as2
that
combined
they
let's
say
that
glued
together
as
a
cluster
in
the
center
of
our
diagram.
We
have
also
broad
works
network
server,
one
and
two
and
those
two
tools.
Those
two
servers
are
also
clustered.
B
B
We
won't
deliver
nfm
because
we
have
already
installed
on
fm
and
why
we
do
that
in
general.
Nfm
is
a
licensed
broker,
as
I,
as
I
mentioned
before,
so
after
nfl
installation,
you
have
to
provide
a
fingerprint
to
cisco
and
based
on
this
fingerprint
license
is
generated
for
you
and
before
you
proceed
with
other
tasks,
you
have
to
have
this
license
already
installed
on
an
fm,
because,
without
that
you
won't
be
able
to,
you
know,
even
to
start
blocks
of
applications.
B
So
that's
what
we
decided
for
for
for
today's
demo
to
have
already
nfm
provided
with
license
installed,
and
this
the
next
step
is
to
provide
rest
of
infrastructure.
We
want
to
have
in
our
setup,
okay
guys.
So
I
think
we
can
also
discuss
some
sequence
flow.
How
we
want
to
achieve
it
before
we
make
any
code
review
so,
first
of
all,
we
have
a
ansible,
as
I
mentioned
before.
B
Perhaps
I
haven't
in
general,
ansible
and
terraform
can
be
a
combined
together
and
depending
on
your
needs,
you
may
even
trigger
ansible
from
terraform
or
doing
let's
say
vice
versa.
I
mean
the
ansible
may
trigger
a
terraform
to
build
in
some
infrastructure.
For
us
today
we
decided
to
have
ansible
and
ansible
will
trigger
terraform
right
and
telephone
will
build
infrastructure
on
proxmox
and
at
the
end
we
should
get
linux
servers
ready
for
communication.
B
For
us,
then,
as
I
mentioned,
we
have
to
configure
and
prepare
linux
servers
accordingly
to
blocks
of
requirements.
So
ansible
is
used
to
is
used
to
configure
operating
system
properly
for
us,
so
you
can
see
it
in
the
center
of
the
screen
and
then
we
will
also
trigger
ansible
to
deliver
binaries
and
config
files
and
patches
to
to
the
let's
say:
targeted
servers
perform
installation
and
when
installation
is
ready
and
post
task
is
done,
we
may
provide
license.
B
C
B
It's
built
in
the
we'll
see
in
the
code
review,
but
it's
built
in
general
in
the
single
play
book,
but
the
single
playbook
contains
roles
right
so,
depending
on,
depending
on
the
step
you
I'd
like
to
achieve
right,
I'm
simply
executing
role
that
was
built.
You
know
to
let's
say
to
to
address
some
specific
parts
of
configuration
steps.
B
Moreover,
we
also
use
attacks
because
you
know
using
roles
also
may
let's
say,
contains
a
lot
of
additional
functionalities
for
our
demo.
We
don't
need
to
do
it
all
the
stuff
or
preparation
like
like
we
do
on.
You
know,
example
on
production
sites,
so
we'll
limit
some
parts
of
our
of
our
roles
to
single
tags,
just
to
make
sure
that
it
contains,
let's
say
basic
configuration
required
for
for
our
demo.
A
B
Let's
say,
let's
say
it
depends
on
if
you
know
a
little
bit
broad
soft
right,
if
you
are
familiar
with
browsof
and
you
let's
say,
get
used
to
installations
and
so
on
you,
you
know
what
is
inside,
then
you
need
to
simply,
let's
say,
think
about
how
you
would
perform
financial
way
right.
So
there
are
some
tricky
parts,
in
example,
that,
depending
on
the
brush
of
release,
some
files
are
in
different
places.
So
you
need
to
be
aware
of
that
and
put
some
statements
that
simply
address
it
properly.
B
Depending
on
the
blocks
of
release,
you
also
may
have
some,
let's
say,
different
behavior
an
example.
After
browser
binary
is
installed
right
and
again,
depending
on
release
that
you're,
installing
you
may
have
spontaneously
boots,
have
a
reboot
or
not
right,
because
at
the
end
some
binary
installation.
It
requires
some
server
reboot
and
it
performs
for
you
and
an
example.
Ansible
doesn't
like
it
right
it
we
need
to.
You
know,
handle
this.
Let's
say
in
some
order
that
it's
not
a
failure.
We
know
about
it.
B
So
if
you,
if
you
let's
say,
are
familiar
with
answer
with
ansible
and
you
are
familiar
with
with
blogsoft-
it's
rather
say
some
way
that
you
may
simply
address
it
properly
and
because
we
are,
you
know
that
is
not
error,
something
that
that
simply
occurs
right,
especially
for
example,
post-install
task,
because,
depending
on
the
release
and
depending
on
the
type
of
server,
a
post-install
task,
script
might
be
in
different
places,
in
example,
so
need
to
detect
it,
detect
it
properly
and
execute
proper,
proper
script.
C
B
Yeah,
you
should
be
familiar
with
some
gears
that
are
inside
the
russo
yeah.
A
So
knowledge
of
the
tools
and
the
experience
with
the
with
the
platform
and
these
problems
can
be
overcome,
that's
correct,
so
we
have
talked
about
some
difficulties
that
we
might
have
when
deploying
this
cisco
broadworks
platform.
A
We
know
that
there
is
prerequisites
to
be
addressed
on
the
os
level
before
we
can
proceed
with
the
installation.
We
know
there's
a.
There
are
some
difficult
parts
we
have
which
have
to
be
addressed
by
ansible
like
like
interactive
and
post,
install
behaviors
and
scripts.
We
know
there's
some
not
a
very
friendly
for
automation,
cli,
there's
licensing
involved
as
well,
so
show
us
slavic
how
how
you
have
how
you
have
overcome
all
these
all
these
points
and
show
us
show
us
the
demo.
B
Okay,
so
I
suppose
that
first
of
all,
we
would
make
some
short
code
review
right
to
to
you
know
to
our
to
get
our
to
get
everyone
a
family,
familiar
with
what
we,
what
we
did
and
how
we
did
it,
and
then
we
can
simply
execute
the
the
playbook
and
see
how
the
installation
goes.
Okay,.
B
Everything
yeah,
I
hope,
surely,
is
up
and
running,
keep
keeping
across
that
yeah
and
after
after
this
execution
of
the
ansible
playbook,
we
should
get
a
platform
fully
operational
and
ready
for
to
handle
calls,
and
you
know
to
to
create
users
and
so
on
exciting.
Let's
go
okay.
So
let's
do
that
all
right
guys.
So
let's
go
through
our
code
that
we
built
for
to
for
our
setup.
B
So,
first
of
all,
as
I
said,
we
can
ask
a
terraform
to
be
true
to
to
be
triggered,
let's
say
by
ansible,
and
this
is
a
part,
so
we
have
already
terraform
template
and
those
are
simply
executed
by
ansible.
So,
instead
of
doing
you
know,
terraform
apply
right.
We
have
this
part
of
code
and
at
the
end
we
should
have
our
our
infrastructure
delivered.
B
Later
I
can
show
you
in
general,
before
we
start
brought
birth
of
installation,
I
can
show
you
more
or
less
how
it
looks
like
if
we
let's
say
if
you
would
do
it
from
terraform
perspective,
so
I
can
apply
some
telephone
plan
and
you
will
see
that
how
many,
how
many
servers
will
be
built
and
and
what
the
details
more
or
less
will
be
introduced
by
the
telephone.
B
B
Centos
operating
system
to
bring
us
brings
our
lean
loops
upon
ready
and
ready
for
a
browser
installation,
but
before
we
we
do
that,
let's
go
to
terraform,
so
we
have
tf
files
here
defined.
As
you
can
see
here
we
are
using
proxmox
provider.
B
As
a
as
a
provider
of
our
solution,
then
we
need
to
also
define
some
servers.
As
an
example,
I'd
like
to
show
you
how
application
server
looks
like
so
we
have.
You
know
some
target
nodes
in
our
cluster.
We
have
some
disk
requirements
network.
Even
we
have
some
cloud
in
script
that
is
executed
later
on.
That's
why
we
are
also
giving
some
additional
time,
and,
moreover,
we
we
have
also
we
have
all
we
have
also
some
happy
already
assigned
for
the
network
for
the
server.
B
Let
me
let
me
at
the
at
the
beginning
we
are
providing
some
proxy
information
for
yam
to
be
updated.
Then
we
checking
if
we
have
all
packages
installed,
that
simply
blots
off
requires,
and
then
we
also
design
sr
linux,
because
this
is
one
of
the
recommended
parts
of
our
setup
in
the
series
we
also
introduced
some
ntp.
B
We
also
make
some
dns
setup.
What
we
also
do
is
that
we
need
to
prepare,
etc,
host
all
allow
deny
and
the
host
itself.
We
are
using
templates
for
that,
and
also
what
is
important
at
the
end,
we're
also
introducing
locus,
depending
on
the
host
name,
that
we
execute
this
playbook
right
so,
depending
on
the
host,
we
need
to
add
log
cost
information,
because
this
is
this
is
what
broadsoft
requires
as
well.
B
B
So
whenever
we
be,
let's
say
whenever
we
will
be
executing
our
our
playbook,
I
will
add
all
required
tags
that
should
be
executed.
You
will
see
later
on
why
we
need
that.
B
So
let's
go
back
to
our
installation,
webinar
here
playbook.
So,
as
I
said,
we
are
introducing
some
centers
with
the
role.
Then
we
have
a
role.
That's
simply
build
for
us
application
server.
Let's
take
a
smaller
view.
I
will
not
be
showing
you
each
server,
because
the
idea
more
or
less
is
the
same.
So
we
have
a
we
need
to
create
a
directory
for
installation.
B
Next
topic
is
that
we
also
deliver
installation
config
file,
so
you
may
install
it.
You
may
install
block
soft
in
in
active
mode
or
deliver
already
a
pre-configured
file
that
contains
some
configuration
and
you
simply
execute
it
with
the
config
file
or
application
with
the
patches.
So,
as
you
can
see
later
on
is
that
we
are
installing
application
server
binary
with
initial
pass
patch
and
in
installation
com
file,
depending
on
our
server.
Okay,.
B
More
or
less
the
same
we
do
for
for
rest
of
the
servers
depending
if
we
have
the.
If
we,
if,
if
you
use
the
some,
is
this
release
based
or
it's
independent,
english
right
always
independently,
so
we
don't
use
initial
patch
packages.
C
C
B
Yeah
exactly
this
is
browser-specific
next
topic
is:
we
need
to
prepare
post-intel
post-install
tasks,
so
whenever
you
install
broadsoft
later
on
as
a
bw
admin
user,
you
need
to
perform
post
install.
B
B
As
you
can
see,
we
have
introduced
raw
bw,
ks
post
install.
B
So
let's
see
what
we
have
here
so,
depending
on
the
under
our
release,
we
need
to
replace
flag
from
false
to
true,
then
what
we
need
to
do
is
we
are
checking,
because
it's
also
depending
on
price
of
release,
where
this
post-install
setup
file
is
located
so
in
release,
22,
23
or
24.
B
B
Then
what
we
need
to
do
we
are
installing
media
server.
Media
server
is
more
or
less
the
same
way.
Let's
say
the
same
idea
ads
we
had
for
application
server.
The
only
difference
is
that
I
created
a
different
role
for
the
for
for
this
for
this
type
of
server,
an
example.
If
we,
if
we
let's
say
start
thinking
that
we
need
to
also
add
something
for
media
server,
we
can
introduce
it
directly
to
all.
B
What
is
next
that
I
would
like
to
mention
it
here:
okay,
post,
install
task
execution.
So
whenever
you
have
cluster,
you
need
to
also
take
away
about
order
where
you
perform
this
post-install
task.
So
let's
say
the
general
idea
is
that
you
need
to
perform
positive
tasks
on
the
primary
first
then
on
secondary.
So
this
is
why
we
also
use
here
order
of
execution
from
from
as
a
different
task.
So
at
the
beginning
we
are
performing
posting
style
tasks
on
the
primary
one.
Then
we
perform
posing
star
task
on
secondary
server.
D
So
all
these
tasks
needs
to
be
done
in
sequence,
yeah,
and
you
have
to
explicitly
take
care
of
it
in
the
in
the
invincible
scripts.
Yes,.
C
And
what
I
see,
what
do
I
see
that
to
achieve
our
our
automated
automated
installed
platform?
We
we
need
to
have
a
deep
knowledge
of
automated
automation
tools,
but
not
not
only.
We
also
need
a
deep
knowledge
of
broadcast,
and
maybe
this
is
the
most
important
yeah
you
need
to
you.
B
Need
to
know
blow
soft,
let's
say
what
is
inside
what
gears
are
inside
and
how
they
are,
let's
say,
launched
quite
deeply
right
to
to
understand
why
we
have
a
as
a
good
example,
because
you
almost
mentioned
this
one.
You
can
also
see
here
that
I
have
a
statement
ignore
unreachable.
Yes,
why?
Because,
depending
on
the
release,
suddenly
your
after
installation
process,
your
server
may
be
rebooted.
B
So
if
you
are
aware
of
it-
and
you
know
that
it
may
happen-
and
it
happens
right
because
simply
at
the
end,
reboot
is
required
and
broad
applications
simply
perform.
This
reboot
ansible
would
stop
right,
because
something
wow
why
I
lost
my
connectivity
to
the
server
right.
So
that's
why
I
put
it
here.
You
know
unusable
yes,
so
only
if
we
reach
unreachable
statements.
So
if
we,
if
you
face
any
other
error,
let's
say
playbook
will
stop
and
we'll
simply
return
an
error
that
this
we
could
not
perform
some
steps.
B
But
if
we
reach
unreachable
state,
it
will
go
on
right.
So
this
is
what
you
mentioned
already
that
yeah
some
the
big
deal
is
not.
Let's
say
the
biggest
deal
is
not
to
prepare
a
playbook,
it's
rather
to
understand
how
broadsoft
installation
behaves
and
how
it
proceeds.
A
B
Okay,
so
let's
let's
go
to
the
some
positional
tasks,
so
I
already
introduced
your
the
role.
So
this
is
how
we
execute
post
install,
as
I
said,
primary
first
secondary
letter
and
nfm.
So
what
we?
How
we
do
it?
We
simply
use
a
crl
tool.
B
So
we
have
we
have
some
xml
associated,
then
what
we
do
is
we
are
trying
to
use
serial
command
right
and
we
use
a
network
function
manager
happy
to
to
simply
trigger
on
the
fm
and
perform
for
us
some
some
binding
and
also
we
are
asking
with
the
appi
to
perform
a
license
of
the
servers.
Okay,
I
know
probably
tomek
will
ask
for
that.
Why
we
don't
use
a
url
url
module
of
ansible.
B
I
decided
to
use
url
because
it
was
more
handy
for
me
in
general
right
because
we
have
we
use
here
a
body
and
in
general
you
know,
I
would
need
to
struggle
more,
let's
say
more
on
ansible,
while
we
simply
can
use
serial
with
handy
in
any
way.
So
I
decided
to
use
crl
here.
B
Okay,
guys
so
then
after
license
is
being
assigned.
So,
as
you
can
see
here,
I
will
have
a
loop
and
perform
perform
a
license
assignment.
B
B
C
B
Guys
so
this
is
how
we
do
it
in
general,
we
we
simply
checking
if
you
have
export,
expect
directory
right.
This
is
how
I
decided.
Then
I
deliver
with
the
template,
expect
script.
B
So
at
the
end,
we
should
get
some
some
expert
script
in
place
in
the
the
directory
that
that
we
created
here
then
we
are
executing
expect
with
the
case
with
the
shell
command
this
expert
sheet
after
execution
and
success
and
successful
execution.
We
are
stopping
and
starting
bubbles.
Why?
Because
in
mainly
in
the
initial
configuration,
you
need
to
do
a
lot
of
conflict
changes
that
requires
lots
of
free
stuff.
So
I'm
doing
that
way.
B
So
I'm
not
using
here
any
handlers,
because
I
would
need
to
define
services
and
it
was.
It
was
quite
handy
to
to
perform
the
start
and
stop
with
the
false
command.
B
B
Okay
guys,
so
we
are
ready
to
proceed
with
execute
executing
our
playbook.
As
you
can
see,
we
are
using
the
install
webinar
yaml
file
that
was
discussed
in
previous
section
with
following
tags.
The
basic
broadbox
install
post-install
license
broadcast
config
and
also
terraform.
Simply
this
those
tags
limit
our
actions
that
are
required
for
our
setup.
B
Let's
proceed:
let's
try
to
execute
it.
As
you
can
see,
the
first
task
is
the
terraform.
So
mainly
we
are
provision
we
are
providing
our
infrastructure
first,
it
might
take
up
to
five
minutes.
Even
so,
let's
fast
forward
this
section
and
we
will
we
will
slow
down
only
on
moments
when
any
comments
is
required.
So
let's
proceed
and
please
stay
with
us.
B
Okay.
So
after
five
minutes,
as
you
can
see,
our
infrastructure
has
been
provisioned
right
now,
we're
giving
some
extra
time
simply
to
those
servers
to
spin
up
and.
B
Then
we
will
start
linux
configuration
and
broad
works
and
broad
rock
installation.
So
let's
move
to
the
next
section.
B
Just
after
that
we
are
starting
right
now,
linux
configuration
as
you
can
see,
packages
are
being
checked.
If
I
installed
or
not,
and
after
this
section
our
linux
operating
system
should
be
ready
for
bloodsoft
software
installation.
B
B
Right
now
we
are
starting
post,
install
task
on
the
first
server
and
after
the
first
one
after
primary
server
is
done.
We
proceed
with
secondary
server,
so
let's
fast
forward
this
section
as
well.
Okay,
so,
as
you
can
see,
both
application
servers
are
done.
Also,
post
install
tasks
are
done
on
those
servers.
We've
started
with
media
server
installation
process
in
general.
It
will
look
very
similar
to
application
server
as
well,
so
we
will
have
a
binary
installation
and
then
we
will
proce.
We
will
proceed
with
post.
B
B
B
Application
on
each
server
is
started,
and
after
that
we
will
proceed
with
the
blocks
of
configuration
section.
It
looks
that
we've
done
all
tasks
as
you
can
see.
In
summary,
we
hit
three
unreachable
states
here.
As
I
mentioned
it
is
expected.
It
seems
that
application
process
application
has
been
configured
with
success.
B
Okay,
so,
as
playbook
is
done,
I'd
like
to
check
right
now
how
application
server
cluster
looks
like
what's
the
stage
there.
So
let
me
login
first.
B
Okay,
we
have
no
alarms
present,
that's
good,
so
right
now
I'm
checking
cluster
status.
As
you
can
see
application
server.
One
is
a
primary
one.
It's
in
unlocked
state
and
application
server
two
is
also
in
unlocked,
so
it
means
that
the
second
one
is
secondary
node.
So
let
me
check
the
timestamp
replication
status
now.
B
B
Okay,
it
asks
it
is
asking
me
to
change
my
password,
so
it's
it's
not
a
behavior,
so
let's
update
the
password
and
then
we
may
proceed
with
enterprise
group
and
user
creation.
So
let's
proceed
with
that.
First.
B
B
B
So
let
me
show
you
right
now
how
the
user
looks
like,
as
you
can
see,
it
has
line
port
assigned
also
it
has
authentication
because
we
will
register
our
user
through
application
server.
So
we
have
to
this.
We
have
to
have
this
authentication
service,
enabled
and
also
created
credentials
for
that
user.
B
Let
me
show
you
assign
services,
so
we
have
some
basic
services:
authentication,
external
and
internal
call
line
id
delivery.
So
that's
all
that's
what
we
what
is
required
to
proceed
our
test
call,
okay,
guys!
So
what
we
did
was
we
built
our
cluster.
We
built
a
fully
operational
broadsoft
and,
as
I
showed
you,
it
seems
that
it's
ready
to
handle
calls.
Moreover,
I
was
able
to
create
enterprise
groups
and
add
users.
I
already
passed
my
some
credentials
to
tomas.
B
C
B
Oh,
these
are
some
boys
okay,
so
it
works
great.
Thank
you,
okay,
so
so,
let's
try
to
to
make
a
call
to
some
unknown
or
not
existing
number.
So
we
could
see
if
you
have
a
media
have
a
triggered
and
we
should
have
some
announcement
that
call
cannot
be
completed.
So
let's
try
this
one.
E
B
Okay,
so
it
looks
that
media
server
is
being
triggered
and
it
plays
on
the
announcement
that
the
call
is
not
being
is
not
being
completed
right
now,
all
right
guys,
so
you
may
notice
that
I
also
installed
some
packet
bit
for
our
in
our
setup
and
while
I
did
it
in
general,
I
have
prepared
some
elasticsearch
and
just
those
two,
let's
say
dashboards
are
simply
show
to
show
us
how
to
show
you
and
that
you
can
easily
combine
with
some
bits
that
are
created
by
elastic
and
you
may,
let's
say,
bring
some
observer
observability
to
our
setup
here.
B
B
Heap
usage
right
now,
what
we
have
here
on
the
server,
mainly
this
one
are
achieved
by
by
logstash
with
snmp
agent
installed
plugin.
This
is
like,
let's
say,
kind
of
heads
up
for
you
guys
that
perhaps
in
the
next
webinar
we
may
show
you
how
you
might
introduce
elasticsearch
for
your
bloodsoft
platform.
A
D
B
Yes,
I
mean,
if
you
noticed,
on
our
let's
see:
playbook
we
had
a
part
where
a
packet
bit
was
installed
on
the
application
server.
A
Okay,
so
not
only
can
we
automatically
deploy
a
traditional
legacy
telco
platform.
We
can
also
use
modern
tools
for
observability,
like
elasticsearch,
to
interface
with
a
snmp
and
to
bring
and
take
out
and
bring
it
to
the
dashboards.
Some
interesting
information
from
from
within
the
platform.
B
Right
yeah,
but
it's
an
snp
is
just
just
a
part
with
packet
bit.
We
are
simply
taking
let's
say,
network
traffic
and
visual
visualize
it
here
right.
So
we
could
recognize
that
this
is
a
seat
message,
and
here
we
we
can
inside
check
what
is
inside
the
packet
and
recognize
that
is
invite.
You
know
the
method
inside
the
sip.
So
on
the
top
we
have
a
packet
bit,
let's
say:
output,
let's
say:
output.
We
have
a
output
from
data
that
are
collected
by
packet
bit
to
elasticsearch
on
the
bottom.
B
We
have.
We
have
output
that
is
delivered
to
logstash
and
the
logstash
has
additionally
installed
a
snmp
agent
plugin.
That
allows
us
simply
to
query
our
blocks
of
setup
and
get
some
additional
information.
C
You
should
mention
that
packet
bit
is
supporting
now
natively
natively
seed
traffic,
so
this
is.
This
is
really
easy
to
integrate
yeah
platforms
into
elastic
so.
B
To
be
honest,
to
be
honest,
I
didn't
have
to
even
check
too
much
regarding
the
what's
inside.
Just
you
know,
taking
discovery
from
the
index,
we
we
started
collecting
we
started
collecting
and
you
know
it
was
easy
to
figure
out
how
to
build
such
er
such
dashboard.
For
us.
A
That's
correct.
Thank
you
for
joining
this
webinar.
I
hope
that
the
tricks,
the
challenges,
the
tools
that
we
have
showed
you
can
also
be
obvious
in
in
your
own
projects.
Thank
you.