►
A
90
minutes
blocked
but
kind
of
I'm
sort
of
thinking.
Well,
we'll
do
both
presentations
will
be
like
25
to
30
minutes
each
and
then
I'll
just
leave
us
some
discussion
time
at
the
end
of
the
session
before
we
get
started
with
the
presentations
just
wanted
to
give
everyone
a
quick
opportunity
to
say
hello,
say
what
institution
you're
working
with
and
well
then
we'll
move
into
the
presentation,
so
I'm
Terry
radius,
software
developer
with
Georgetown.
We
run
these
base
5.8.
C
E
A
A
F
A
H
J
E
A
L
E
B
B
So
if
you
wanted
to
use
it
to
base
your
own
little
deployment
off
of
or
whatever
you're
welcome,
to
go
ahead
and
borrow
it
or
or
hack,
something
off
of
it
or
whatever
you
want
to
do
so.
I'm
going
to
show
this
actually
as
a
completely
live
demo.
I
don't
have
slides
or
anything
of
that
nature,
but
we're
going
to
talk
through
how
this
all
works
and
I
welcome
you
to
kind
of
like
ask
questions
as
we
go
and
we'll
kind
of
take
it
from
there.
B
B
But
what
we're
going
to
do
here
is
we're
going
to
launch
a
brand
new
instance
I'm
using
these
scripts
that
are
out
here
on
github
to
bring
up
a
copy
of
the
demo
site
and
then
we'll
talk
through
how
this
is
actually
working
and
what's
going
on
behind
the
scenes.
So
you
can
get
a
sense
of
how
you
could
potentially
use
this
for
other
cloud
deployments
of
dspace
or
other
products
altogether,
if
you
wanted
to,
but
in
any
case,
in
order
to
actually
make
this
work
within
a
lot
of
time.
B
I'm
going
to
kick
this
off
and
we're
going
to
talk
through
this.
While
we
wait
for
this
to
actually
boot
up,
we'll
talk
through
how
it
what's
happening
and
and
where
this
is
all
going
so
I'm
just
going
to
choose
a
generic
machine
image
here
for
Amazon,
so
Amazon
calls
each
of
their
servers
different
machine
image.
B
I
tend
to
use
a
bun
too
so
I'm
going
to
grab
this
a
bun
I'm
into
this
generic
one
and
select
that
for
the
new
server
that
we're
booting
up
right
now,
our
demo
site
is
using
a
sort
of
old
generation
instance
type,
which
is
a
little
bit
smaller
and
cheaper.
This
m3
medium.
You
really
could
go
with
anything,
but
this
has
about
almost
4
gigs
of
memory,
which
is
useful
to
be
able
to
run
Postgres,
Tomcat,
Apache
and
dspace
all
in
the
same
server.
B
You
probably
want
at
least
that,
if
not
more
so
we're
going
to
go
ahead
and
launch
from
that
I'm
going
to
go
ahead
and
configure
our
instance.
Details
not
a
whole
lot
here,
but
I
do
want
to
give
it
a
specific
role
and
I'll
I'll
talk
through
that
here,
a
little
bit
later
on
we're
not
going
to
worry
about
anything
else.
The
one
thing
that
is
of
interest
here
is
this
advanced
details.
B
User
data
is
stuff
that
you
can
pass
to
the
server
as
it's
actually
spinning
up,
and
so
what
we're
going
to
pass
in
here
is
we're
actually
going
to
pass
it
cloud,
init
script
to
to
boot
up
the
server
and
start
everything
up,
including
installing
everything
that
these
space
needs.
It'll
kick
off
an
installation
of
Tomcat,
Postgres,
Apache
and
D
space
itself
and
spin
everything
up
as
the
server
boots
up,
so
that
cloud
init
script
is
available
out
on
github.
B
B
This
includes
the
continent
scripts
and
the
puppet
scripts
that
allow
us
to
run
the
demo
site,
and
it's
this
cloud
in
it
yamo
file
and
we're
going
to
walk
through
this
after
I,
get
it
pasted
in
so
I'm
just
going
to
grab
it
real,
quick
copy
it
exactly,
as
is
I'm
going
to
go
over
to
our
other
window
here
and
paste
in
this
giant
yamo
file
into
our
user
data.
So
there's
a
ton
of
information
in
this
Jamo
file
which
will
go
through
a
lot
of
it
as
comments
which
help
you
understand.
B
What's
going
on
in
the
ml
file
and
we'll
walk
through
that
here
in
a
moment,
I'm
going
to
go
in
the
next
step
here
and
instead
of
an
8
gig
main
drive,
I'm
going
to
bump
it
up
to
75.
We
don't
really
need
another
drive
here
and
we
will
give
it
a
quick
tag,
get
a
server
name
and
we're
just
going
to
call
this
test.
B
E
space
deployment
and
then
I
have
a
security
group
already
set
up
which
basically
just
opens
up
certain
ports
for
this
server
by
default.
So
you'll
see
we
have
our
SSH
port
HTTP
HTTPS
stuff
for
the
handle
server,
all
that
sort
of
stuff
that
the
demo
site
itself
is
using
so
I'm,
just
selecting
that
same
security
group,
so
it'll
open
up
those
same
ports
for
me
as
the
server
boots
up.
So
now
we'll
go
ahead,
and
this
just
gives
us
a
review
of
everything
we
selected
the
server
type,
the
port's
that
are
open.
B
The
yamo
file
that
we
uploaded
is
under
this
instance
details.
It's
now
all
been
encrypted
in
this
really
strange
user
data
encryption
here,
I
bow,
go
ahead
and
launch
that
now
and
I
need
to
select
my
SSH
key,
that
I
have
locally,
which
will
allow
us
to
actually
monitor.
What's
going
on
here,
we'll
launch
this
okay.
So
while
this
is
getting
started,
this
is
going
to
take
about
15
minutes.
B
Let's
go
back
here
to
our
puppet
D
space
demo
repository,
so
one
thing
to
mention
is
this:
is
in
a
different
area
of
github.
If
you're
a
little
bit
newer
to
D
space,
we
actually
have
two
D
space
areas,
there's
the
main
D
space
repository
area,
which
is
all
the
production
level
stuff,
and
then
there's
also
this
labs
area,
which
is
stuff
that
some
of
it
may
be
production
writing.
Other
stuff
is
just
stuff.
B
People
are
playing
around
with
and
been
messing
with,
and
if
you
ever
want
to
actually
share
some
of
your
code
here,
get
in
touch
with
me
or
one
of
the
other
committers,
and
we
can
help
you
create
a
repository
here,
so
you
can
get
things
out
there
and
have
others
contribute
to
it,
so
that
that's
where
this
puppet
D
space
demo
code
sets
as
I
had
mentioned.
We
have
this
cloud
init
script
right
here
that
tells
cloud
in
it.
B
What
what
we're
going
to
be
doing
before
we
go
through
this
I'll
note
that
there's
some
pretty
good
cloud
init
documentation
over
on
cloud
in
it
I,
oh,
and
the
reason
why
I'm
using
cloud
init
in
this
situation
is
because
it
does
work
with
many
different
types
of
servers.
So
it's
not
abun
too
specific.
You
can
use
it
with
any
sort
of
your
favorite
server
flavor.
It
also
works
with
in
various
public
clouds.
B
So
it's
not
EWS
specific
in
any
way,
if
you're,
using
Google,
Cloud
or
Rackspace
or
whatever
else
you
can
use
cloud
in
it
there
as
well.
So
none
of
this
that
I'm,
showing
you
here
today
is
at
all
AWS
specific,
but
the
cloud
in
its
configuration
file
whoops
wrong
tab,
clarinet
configuration
file
is,
is
handled
in
this
llamó
file.
B
We're
telling
cloud
in
it
that
it
can
manage
our
etc'
hosts
in
order
to
configure
those
properly
we're
telling
cloud
in
it
that
we
want
to
add
some
new
app
sources,
and
some
of
these
are
commented
out,
because
it
was
testing
stuff
that
I
had
done,
but
we're
enabling
some
partner
repositories
and
apt-get
so
that
Ubuntu
has
access
to
certain
things.
We're
telling
it
that
the
first
time
it
boots
up.
It
should
run
our
update
and
our
upgrade,
which
just
says
to
make
sure
all
the
packages
are
up-to-date.
A
B
Just
sets
this
up
on
the
server:
it's
not
doing
anything
at
the
actual
DNS
level.
So
if
I
was
to
actually
want
to
enable
this
at
the
DNS
level,
yes,
it
would
show
up
as
a
collision,
but
you'll
see
the
server's
gonna
identify
itself
when
we
log
in
till,
when
SSH
into
it,
it'll
say
that
it's
called
demo,
but
the
DNS
doesn't
know
anything
about
it.
B
What's
going
to
get
set
up
the
DNS
level,
is
it's
just
going
to
be
a
generic
ec2
instance
domain,
which
we'll
see
in
a
minute
when
we
ask
this
H
into
it
and
see
how
it's
going
so
so
this
is
just
getting
the
basic
set
up.
We
can
tell
it,
then
we
want
certain
packages
installed
by
default.
We
want
W
get.
B
So
this
first
one
shows
up
as
sort
of
an
array
just
to
pass
several
commands
together
here,
so
we're
doing
an
SH
call
and
telling
it
to
do
I
set
up
some
SSH
forwarding
configuration
ssh
agent,
forwarding
configuration
just
for
easier,
SSH
access
and
we're
having
pip
upgrade
itself
to
make
sure
it's
in
the
latest
version
we're
having.
It
then
install
the
AWS
tools
to
make
sure
we
have
those
client
tools
available.
We
have
rubygems
upgrade
itself
and
here's
where
we
actually
get
into
stuff
related
to
D
space.
B
B
Ok
run
this
script
to
install
everything,
and
this
is
where
the
magic
happens.
It's
really
just
in
these
four
lines
in
terms
of
along
with
all
the
puppet
scripts,
of
course,
in
terms
of
actually
getting
everything
to
be
set
up
properly
in
AWS
or
in
any
cloud.
Your
cloud
services
of
choice,
the
other
things
down
here-
are
pretty
relatively
straightforward.
B
This
is
kind
of
firewall
firewalling,
some
to
information,
which
is
not
really
necessary
for
other
cloud
cloud
services,
but
it's
just
trying
to
make
sure
that
certain
stuff
is
only
available
to
to
root
on
the
machine.
It
sets
up.
Our
locale
sets
up
our
timezone
says:
okay
cloud
in
it.
We
want
everything
you
do
to
be
logged
to
this
log
file
and
we're
going
to
go.
Look
at
that
log
file
on
the
server
to
see
what
all
it's
performed
and
then
the
final
message
we
want
you
to
print
in
this
log
file.
B
Is
this
specific
message
once
you're
done
with
all
of
your
processing?
So
that's
the
gist
of
the
cloud
cloud
Anette
script
here
and
what
it's
doing
we're
going
to
go
through
a
little
bit
of
the
library
and
puppet
stuff
and
puppet
stuff
in
just
a
moment,
but
I
want
to
go
over
and
see.
Let's
take
a
look
at
how
our
servers
booting
up
and
we're
going
to
do
that
by
going
back
to
our
instance.
B
Here,
ok,
so
it's
running,
it's
probably
still
in
the
process
of
installing
everything,
because
the
actual
dspace
build
process
is
you're
all
probably
aware
it
takes
a
little
while,
but
we
have
a
public
DNS
that
it
is
reporting
as
down
here
so
I'm,
going
to
copy
that
to
my
clipboard
and
then
I
have
a
command
line
over
here.
I'm
going
to
pull
over.
This
is
just
an
ssh
command
using
the
ssh
key
that
I
had
configured
that
I
had
locally.
B
B
Started
to
do
some
things
because
we're
already
seeing
that
it's
responding
as
welcome
to
demo
D
space
org,
but
if
we
go
to
our
VAR
log
directory,
this
is
where
I
told
it
to
log
everything.
Let's
do
a
quick
tail,
the
cloud
on
it
to
see
how
far
along
we
are.
How
long
was
I
talking?
Ok,
so
it's
still
doing
some
puppet
installation
here
going
step-by-step
and
trying
to
get
things
installed
little
by
little
and
we'll
go
ahead
and
let
that
run.
So,
it's
still
installing
things
like
the
Postgres
server
setup,
apache.
B
Various
things
are
being
installed
on
the
server
using
those
puppet
scripts,
but
let's
jump
over
and
look
at
how
it's
doing
this
via
the
puppet
scripts
I
get
this
window
out
of
the
way.
Let
me
just
pull
this
over
to
the
side:
real,
quick,
okay,
so
I
had
mentioned
that
we
pull
down
this,
get
repository,
we're
using
library
and
puppet
to
install
dependencies
and
then
we're
calling
a
puppet
script.
These
things
are
all
within
this
github
repository
here.
So
let's
jump
over
and
look
at
that
a
little
bit
more
closely.
B
So
here's
our
puppet
dee
space
demo
repository
it's
a
very
small
amount
of
code
in
here,
because
it's
relying
on
a
lot
of
other
things
that
are
third-party
tools,
as
well
as
our
own
puppet
D
space
tools.
So
there's
not
a
whole
lot.
Here
we
had
our
cloud
init
script,
which
we
copied
in
to
actually
get
this
all
running.
B
We
have
another
thing
called
a
puppet
file,
which
is
what
library
and
puppet
uses
library
and
puppet
is
this
tool
from
library
and
puppet
comm
that
basically
allows
you
to
pull
in
dependencies
somewhat
dynamically
various
puppet
modules?
And
it's
relatively
straightforward.
It's
through
this
configuration
file,
so
you
can
see
different
puppet
modules
and
pulling
in
different
versions
of
them
so
I'm
pulling
in
some
puppet
unattended
upgrades.
This
just
ensures
the
the
server
gets
upgraded
automatically
on
a
regular
basis
and
I'm
pulling
in
a
specific
version
of
this
puppet
module.
B
We're
pulling
in
some
standard
libraries
that
puppet
labs
distributes.
That
makes
things
easier
to
work
with
in
puppet
and
here's
where
we
get
into
the
dependencies
so
we're
using
a
third-party
module,
called
puppet
labs,
Postgres
and
a
puppet
labs
Tomcat
and
a
puppet
labs
Apache.
So
these
are
all
third-party
modules
that
are
used
to
obviously
install
these
dependencies
and
I'm
grabbing
in
various
versions
of
these
modules
and
then
at
the
very
bottom
I'm
grabbing
in
a
custom
D
space
D
space
module
that
is
pointing
at
our
puppet
D
space
get
repository.
B
So
it's
basically
saying
now
we're
going
to
use
this
and
we're
gonna
call
it
D
space
D
space
that
the
name
of
this
module.
So
this
is
where
I'm
installing
all
that
all
of
my
dependencies
making
sure
they're
all
on
the
server
and
available
to
our
puppet
scripts.
And
then,
if
we
go
over
to
the
file
that
it
was
running,
if
you
remember
from
the
cloud
init
script,
it
was
running
a
site
PP
file.
B
This
is
the
entire
site
PP,
which
basically
is
a
puppet
script
that
will
then
call
all
those
dependencies
and
set
them
up
so
I'm
going
to
skip
some
of
this.
Just
for
the
essence
of
time,
I
don't
want
to
take
up
too
much
time
here,
but
but
I'm
welcome
to
I.
Welcome
any
questions
on
this
as
we
go
or
later
on
as
well.
B
So
we
have
a
dspace
module
class
that
you
can
see
I'm
setting
it
up
to
use
Java
8
I'm,
telling
it
I
want
this
specific
version
of
Postgres
and
Tomcat
I'm
going
to
set
up
a
an
OS
user
that
I
want
this
to
utilize
and
a
database
name
owner
some
dummy
passwords
here,
a
port
that
I
want
it
running
on
and
all
those
sort
of
things.
This
is
all
kind
of
configuring
this
this
Dees
based
puppet
module,
which
is
available
in
github
again,
which
will
glance
out
here
again
in
a
little
bit
that
I'm,
saying.
B
Okay
I
want
our
dspace
owner
to
be
set
up
as
the
owner
that
I
configured
in
this
above
module,
which
is
the
same
as
this
line
up
here
this
owner,
so
I
want
it
to
be
this
D
based
OS
account
is
going
to
be
our
owner
of
our
dspace
repository
and
it
we're
going
to
make
it
a
pseudo
user.
We're
going
to
set
up
some
other
things
here,
which
are
very
specific
to
the
demo
site,
where
this
is
usually
actually
pulling
down
our
committer
SSH
keys.
So
all
the
committers
have
access
to
this
demo
site.
B
B
But
here's
what
we
get
into
installing
prerequisites
so
I
have
a
wrapper
function
here
within
our
D
space
module
that
says:
okay
I'm,
going
to
set
up
a
Postgres
database
I'm
going
to
give
it
a
name
that
I
configured
above
again
and
I'm
going
to
require
that
it
happens
after
I've
installed
that
owner
account
and
that
that's
because
it's
going
to
be
installed
under
that
owner
user.
As
we'll
see
here
in
a
moment,
I've
get
it
PG
pass
file.
B
So
we
don't
have
to
authenticate
on
the
command
line,
I'm
setting
up
a
tomcat
instance
and
telling
it
where
I
wanted
to
install
that
under
that
owner
account
again
and
I
have
to
wait
for
that
owner
account
to
be
installed.
First,
we're
gonna
provide
a
symlink
here
just
to
sim
link
it
up
properly
we're
setting
up
a
pachi
site
on
this
server
and
telling
it
we
want
it
to
be
called
demo
dot,
DS
based
org,
so
it
can
respond
like
that.
It
can
have
SSL
and
it
requires
that
a
tomcat
instance
is
first
set
up.
B
The
rest
of
this
is
just
some
stuff
that
we
use
to
monitor
our
demo
site,
so
we
use
a
tool
called
psi
probe
to
do
Tomcat,
terrible
shooting
and
that's
installed
there,
and
then
we
use
your
kit
to
do
some
Java
profiling
and
that's
installed
here,
and
then
we
also
set
up
a
splash
page
to
look
at
make.
It
look
pretty
and
that's
installed
in
this
section
here
and
there's
some
other
scripts
to
actually
set
up
some
AIPS
to
install
initial
content
and
all
that
so
I'm
not
going
to
go
through
all
this.
But
this.
B
This
is
where
all
the
magic
happens
in
terms
of
actually
setting
up
the
server
and
getting
everything
installed
for
dspace
and
all
those
prerequisites
and,
as
you
saw,
it
relies
very
heavily
on
this
D
space
module.
All
these
d
space
install
commands,
D
space,
Apache
site
commands.
All
of
those
things
are
actually
over
in
our
puppet
dspace
module
here,
which
is
in
our
main
D
space
repository.
B
Those
are
all
scripts
within
this
module.
So
we
have
various
scripts
here.
There's
the
Apache
site
script
actually
setup
Apache
and
make
it
run,
Howdy's
based
sort
of
expects
it
to,
and
it
can
have
some
default
configurations
at
the
at
the
in
the
top
configuration
and
how
it's,
how
it
does
all
the
Apache
configuration
setup
is
all
within
this
script.
B
We
have
a
script
then,
to
install
a
Postgres
database,
which
sets
up
again
some
default
configurations
and
does
the
actual
Postgres
server
installation
and
a
Postgres
database
installation
by
calling
the
third-party
Postgres
module
that
we
had
pulled
in
from
library
and
puppet,
and
then
we
had
the
same
thing
for
tomcat
scripts.
To
actually
most
of
these
are
just
wrapper.
Scripts,
they're
really
just
kind
of
doing
some
basic
setup,
and
then
they
call
off
to
the
third-party
module
that
we've
installed
to
actually
do
most
of
the
setup.
B
So
a
lot
of
this
is
very
lightweight
code
that
wraps
the
third-party
modules
and
sets
up
everything
in
a
way
that
dspace
tends
to
accept
expect
everything
to
be
set
up.
So
it
ensures
that
the
tomcat
user
is
running
as
the
same
user
that
the
dspace
installation
is
and
things
of
that
nature
that
we
all
know
are
required
for
a
dspace
setup.
G
B
Puppet
librarian
here,
let
me
go
to
the
thing.
It
basically
allows
you
to
pull
in.
You,
don't
necessarily
need
to
use
it
I
just
find
it
an
easy
way
to
pull
in
various
modules
in
a
dynamic
fashion,
so
it
like
I,
said
it.
Has
this
simple
idea
of
a
puppet
file
that
lets
you
pull
in
things
from
what's
called
the
puppet
labs
Forge,
which
is
kind
of
where
all
these
libraries
are
are
registered?
B
It's
a
registry
of
puppet
libraries
and
you
can
just
refer
to
them
by
name
and
by
their
version
number
or
you
can
point
to
specific
at
a
github
repository.
So
it's
a
very
kind
of
easy
way
to
either
pull
in
modules
that
are
either
registered
with
puppet
Forge
or
just
available
out
there
on
github
and
so
I
find
it
useful
personally,
if
it's
not
necessarily
a
requirement
to
use
it.
If
you
wanted
to
use
puppet,
but
it's
just
the
way
that
I've
tended
to
do
things.
B
B
So
this
is
like
a
release
number
within
that
github
repository,
so
you
can
kind
of
limit
it
to
specific
branches
that
you
want
or
release
numbers,
and
it's
just
kind
of
does
this
all
in
a
much
more
dynamic
fashion,
and
we
can
show
how
these
all
get
installed
on
the
server
once
the
server
is
done.
Setting
up
go
ahead,
great.
G
B
B
If
you
want
to
use
that
as
well
as
for
setting
up
the
demo
site,
so
it's
used
in
both
of
those
two
situations
to
install
D
space
and
get
all
the
prerequisites
set
up,
so
it
installs
the
basic
prerequisites
and
then
it
allows
you
to
have
these
wrapper
scripts
that
if
you
want
to
install
Tomcat,
you
can
do
so.
You
just
have
to
also
include
that
puppet
labs
tomcat
third-party
dependency.
If
you
want
to
install
Postgres,
you
can
do
so.
B
E
B
Most
of
these
third-party
modules
are
built
by
puppet
labs,
which
are
the
people
who
actually
make
puppet,
and
they
make
a
ton
of
these
modules
for
puppet
for
major
tools
like
tomcat
apache
Postgres.
So
this
is
the
Tomcat
one
that
they
build.
I
mean
if
you
scroll
down
into
this
there's
somewhere
in
here.
Actually,
maybe
it's
easier
to
look
at
the
puppet
Forge.
They
also
have
this
Forge,
which
is
where
you
here's,
where
the
dependencies
are
so
puppet
labs.
Tomcat
works
on
RedHat,
Ubuntu
Debian.
All
these
various
OS
is.
B
It
does
require
certain
versions
of
tongue
of
puppet
to
be
installed,
and
then
there's
all
all
kinds
of
various
versions
of
this
that
that
that
you
can
utilize
as
well.
They
have
all
the
various
release
numbers
down
here
too.
So
each
of
these
modules
are
third-party
and
they
are
not
at
all
about
too
specific.
B
E
B
You
would
have
to
note
that
that
would
take
more
training
on
puppet.
You
could
look
at
how
they
do
it
within
these
various
puppet
labs
modules
so
that
they
have
like
I
mentioned
a
Tomcat.
There's
an
Apache
one,
all
of
their
modules
support
multiple
OSS,
so
and
I
admit
I
I,
don't
I,
don't
think
we
have
time
to
go
into
how
to
do
this
via
puppet
per
OS.
But,
yes,
you
could
at
a
basic
level.
B
If
you
wanted
to
create
a
Red
Hat
specific
one,
you
could
either
just
remove
the
stuff,
that's
a
bun
to
specific
and
stick
the
Red
Hat
stuff
in
or
yeah.
You
could
have
an
if
statement
that
looks
at
the
environment
and
instead
of
doing
app
sort
of
calls,
you
could
do
yum
or
other
sort
of
calls
right.
K
B
So
that's
the
basics
of
how
it
all
works,
so
we
go
back
over
to
the
command
line
and
I'm
running
out
of
time
here
it
is
almost
finished
installing
dspace
it's
running
through
all
of
the
build
and
installation
process
I'm
going
to
exit
out
of
this
looking
at
the
VAR
law.
But
we
can
go,
look
and
see
what
it
did
do
here.
So
an
et
Cie
puppet
is
where
everything
got
installed
and
if
we
look
here
closely,
we
have
this
manifest
directory,
which
is
what
we
brought
down.
B
If
we
look
at
what's
in
there,
that's
from
our
github
repository
just
has
that
site
PP,
but
there's
also
now
this
modules
directory,
which
did
not
exist
in
our
in
our
github
repository.
If
you
look
at
what's
in
there,
that's
where
it
pulled
down
all
these
dependencies
where
library
and
puppet
does
its
work,
so
pull
down
the
D
space
puppet
module,
the
Postgres
puppet
module,
the
Tomcat
one,
the
Apache
one
and
a
couple
other
ones
here
that
their
dependence
on,
because
puppet
modules
can
declare
certain
dependencies.
B
And
so
this
is
where
all
those
modules
got
pulled
down
by
librarian
puppet
and
installed.
Globally,
so
that
now
puppet
has
access
to
them
and
can
create
everything
and
I
know
this
is
still
installing,
but
what's
going
on
here
is.
If
we
look
there's
now
a
dspace
account
on
this
server
and
it's
still
in
progress
here,
but
we
can
see,
we
have
a
D
space
installation
directory.
We
have
our
D
space
source
code.
It
looks
like
it's
still
in
the
process
of
setting
up
some
of
these
other
things.
B
H
B
Like
a
server
in
the
cloud,
so
it's
not
at
all
containerize.
This
is
not
using
docx
or
anything
like
that
run
up
an
ec2
server
in
the
cloud.
Oh
and
it's
just
finished,
so
we
got
our
our
finish
complete.
You
can
see
it
took
over
a
thousand
seconds,
so
it
takes
a
while
to
get
everything
booted
up,
but
everything
was
successful
and
so
now,
if
we
go
back
to
our.
B
Dns
name,
let
me
copy
that
to
the
clipboard
and
let's
see
it
may
take
a
little
while
here
for
it
to
actually
become
responsive
but
momentarily
here
as
Tomcat
and
everything
boots
up.
We
will
actually
see
the
demo
site
the
dspace
demo
site
at
this
URL
and
that
everything
was
set
up
within
this
15
minute
span
by
cloud
in
it
and
and
the
puppet
scripts,
but
that's
the
gist
of
what
I
wanted
to
show
off
it's
not.
None
of
this
is
really
fancy
into
AWS
tools.
B
So
it's
not
using
a
lot
of
the
AWS
heavy
stuff,
but
it
allows
you
to
see
how
you
could
do
this
in
other
cloud
deployments
and
like
I
mentioned
a
lot
of
the
basis,
for
this
is
also
what
is
used
in
the
vagrant
dspace
vm
environment.
So
if
you
want
to
run
local
VMS,
look
at
vagrant,
D
space,
it
uses
these
same
puppet
tools
to
actually
set
up
D
space
and
all
its
prerequisites
on
a
local
virtual
machine.
B
It
depends
on
entirely
on
what
server
type
you
selected
so
I
selected,
a
medium
server
which
is
relatively
cheap,
I,
think
it's
about
10
cents,
an
hour
to
run
or
something
like
that,
but
it's
10
cents
an
hour.
So
you
got
to
add
that
out
and
then
it
also
depends
on
actual
activity
in
terms
of
numbers
of
downloads
and
things
of
that
nature.
So
if
it's
a
very
highly
active
site,
I
couldn't
really
give
you
numbers
for
for
that.
I.
B
It's
not
a
massive
cost.
I,
don't
know
what
the
exact
cost
is,
but
I
think
it's,
maybe
in
the
hundred
or
so
a
year
hundred
dollars
or
so
a
year
to
run.
Maybe
a
couple
hundred
a
year.
I
know
it's
not
unlike
the
thousands
per
year
but
I,
but
it's
somewhere
and
might
be
the
100
or
200
per
year
to
run
the
dspace
demo
site.
You.
A
B
Could
so
I
admit,
I
don't
tend
to
do
it,
use
AWS
as
much
for
that,
but
I
use
these
exact
same
tools
in
vagrant
D
space,
so
I
use
vagrant,
D
space
or
for
development
environment
locally,
so
that
I
can
have
a
local
virtual
machine.
But
you
very
well
could
just
as
soon
do
that
in
Amazon
you
will
be
occuring
a
little
bit
of
cost
there,
because
you'll
have
to
pay
per
hour
for
what
you're
running
in
Amazon.
B
E
On
that
note,
I
have
a
server
that
I
scheduled
with
the
lambda
Amazon
non-descript.
That
just
goes
down
at
the
end
of
the
workday
and
comes
up
the
next
day
and
I
have
another
one
with
the
same
scripts
and
they
set
up
it.
Just
never
comes
up.
It
automatically
comes
down
at
the
end
of
the
day,
but
if
I
needed
it
just
started
up
from
the
command
line,
so
that
would
be
way
like
I
and
the
way
I
use
B
space.
E
B
E
B
E
B
If
I
want
to
take
up
any
more
time,
it
looks
like
my
servers
taking
a
while
to
start
up
here.
Probably
Tomcat
is
still
messing
with
trying
to
get
D
spaced
fully
deployed.
It
seems
to
be
hanging
and
then
and
then
eventually,
timing
out
but
I
know
any
minute
here.
It
will
suddenly
pop
up
we'll
see
the
demo
site.
B
B
It'll
essentially
look
exactly
like
this
and
ulna
put
their
flash
page
and
all
of
that
and
it'll
look
exactly
like
the
current
demo
site,
but
but
right
now,
as
you
can
see,
it's
still
trying
to
to
do
its
thing.
I
think
Tomcats
just
working
hard
still
and
getting
it
all
running,
but
I'll
go
ahead
and
stop
sharing
here
so
I
can
hand
things
over
to
Patrick
and
we
can
look
back
at
this
later.
Yeah.
B
A
H
H
B
A
B
A
H
B
Yes,
yes,
I
was
just
I
was
saying:
I
was
showing
that
I
do
have
the
XML
UI
and
the
JSP
UI,
both
loaded
now
under
that
same
URL,
so
that
deployment
ended
up
being
successful.
So
I
figured
I'd
share
that
briefly
right
now.
There's
no
content
in
here,
because
the
demo
site
does
not
actually
add
the
content
during
the
deployment
process,
but
we
could
do
that
afterwards
and
then.
A
B
Up
and
running
yeah
correct,
yeah,
it's
just
like
rebooting
a
server.
It's
like
turning
the
power
button
off
on
your
server.
So
right
now
it's
running
but
yeah
I
could
stop
it.
There's
two
different
things
on
Amazon.
You
can
either
stop
a
server
which
is
just
like
pushing
the
power
button
and
you
can
bring
it
back
up
or
you
can
terminate,
which
means
that
actually
destroys
it.
So
if
you
terminate
it,
you'd
have
to
do
this
whole
process
again
of
launching
a
new
instance
using
a
cloud
in
its
crypt
and
all
that.
A
B
B
Yeah,
what
would
hit
this
is
created
is
okay,
so
it's
a
certain
instance
type.
It
also
has
created,
what's
called
a
volume
which
is
the
storage,
and
this
is
the
volume
it
created.
This
test,
D
space
deployment
volume,
it's
a
75,
gig
volume,
so
you
are
paying
some
amount
of
cost
to
maintain
this
volume
being
here.
It's
not
not
a
huge
cost,
but
but
it's
not
zero,
so
you
would
still
be
paying
a
small
cost.
Even
when
the
server
is
shut
down.
E
B
Right
yeah
so
for
for
Amazon
I,
don't
have
the
prices
off
the
top
of
my
head
here.
But
yes,
there
is
cost
for
network
traffic
and
I
find
that
the
costs
tend
to
be
more
on
the
downloading
side
than
the
getting
stuff
to
AWS.
That's
not
in
all
cases,
but
they
obviously
want
you
to
get
stuff
in
the
AWS,
so
you're
dependent
on
them.
Oh.
F
B
They
make
that
as
cheap
as
possible,
but
then
actually
downloading
stuff
from
AWS.
More
people
are
downloading
files
from
your
do
you
space
or
just
even
accessing
the
web
pages,
which
is
pretty
minimal,
but
it's
still
a
HTML
download.
That's
where
you
do
get
some
costs
depending
on
the
the
activity
on
the
server.
So
I,
don't
really
don't
have
good
numbers
for
what
those
are
in
AWS
off
the
top
of
my
head.
B
D
B
But
I've
done
this
a
little
bit
on
the
D
space
direct
service
side
of
things
which
I
have
not
been
able
to
to
make
fully
open
source
yet,
but
hoping
to
kind
of
move
it
over
to
that
just
whenever
I
can,
but
essentially
you
can
do
the
same
same
concept
that
you
would
normally
do
manually.
So
if
you
look
at
the
installation
process,
there's
an
in
the
installation
script
here,
you'll
see
that
a
lot
of
what's
happening
is
it's
calling
these
exact
commands,
which
for
puppet
is
really
just
kind
of
a
command
line,
CLI
stuff.
B
So
let's
see
and
actually
wait,
it
looks
like
some
of
that
is
in
here.
I
just
realized
install
D
space
via
int.
So
it's
saying
if
the
installation
directory
exists,
we're
gonna
do
an
ant
update,
otherwise
we're
gonna
run
an
ant
fresh
install.
So
some
of
that
is
in
here
I,
admit
I.
Don't
remember
adding
that.
Maybe
somebody
else
in
here's
this
since
I
did
that,
but
but
but
that's
the
gist
of
how
you
would
sort
of
do
this
sort
of
thing
as
you
would,
you
would
trigger
a
redeployment
and
you
with
puppet.
B
You
can
actually
have
it
watch
specific
files,
so
you
can
say
if
if
my
local
config
changed
the
next
time,
I
read
puppet,
rebuild
and
redo
everything,
and
that's
actually
what
it's
doing
here.
This
subscribe.
It's
subscribing
to
the
file,
that's
this
local
CFG
file.
So
if
there's
changes
to
that
file,
then
the
next
time
you
run
puppet,
it's
going
to
redo
this
build
and
then
it's
gonna
notify
the
exact
to
reinstall.
So
this
actually
may
work
for
updates.
So.
B
You'd
rerun
the
same
puppet
apply
command
with
the
same
passing
it
the
same
script.
The
way
puppet
works
is
it.
It
essentially
compares
your
current
server
state.
What
what
is
installed
on
the
server
with
what's
in
the
commands
that
it's
running
so
anything
that
it
finds
that
is
different.
It
corrects
essentially
so.
B
Does
have
you
been
checks?
It
doesn't
check
some
of
it,
so
it
checks
some
of
the
local
CFG
and
it
says:
okay,
this
local
CFG
has
changed
so
now.
I
know
that,
since
this
thing
subscribe
to
your
local
CFG,
I
got
a
rerun
this
command
and
then,
after
I
rerun
this
command.
This
triggers
a
notify.
It
says:
okay,
whatever
this
command
reruns,
you
also
rerun
this
command,
and
so
that
kind
of
that
triggers
that
process
does.
E
B
Yeah
that
that's
really
that's
gets
into
much
more
AWS
specific
tools,
so
what
Monica
is
talking
about
is
Amazon
has
a
RDS
service
which
is
kind
of
a
remote
database
service
I
think
it's
what
it
stands
for,
which
allows
you
to
run
the
database
separately
in
the
cloud,
so
you
don't
have
to
have
it
on
your
server.
You
could
also
store
files.
B
Excuse
me
separately
as
well,
using
other
Amazon
specific
tools.
So,
yes,
you
could
do
this
much
more
Amazon
specific,
but
right
now
these
tools
are
kind
of
specifically
meant
to
not
be
Amazon
specific,
just
to
allow
people
to
get
started
in
any
environment
they
choose
but
you're
correct,
there's,
lots
of
other
ways.
You
could
enhance
this
for
specific
services.
A
A
Yes,
I
wouldn't
wish
that
I've
had
is
that
somehow
there
could
be
just
a
clickable
environment
to
build
up
a
test,
deep-space
area.
So
often
one
of
the
things
I'll
find
is
I'm
testing
some
of
our
local
changes
on
our
test
servers
and
they
don't
really
want
to
destroy
that
environment
and
progress
to
test
something
out.
4D
space,
particularly
like
if
I
am
in
the
course
of
a
day,
testing
something
in
D
space.
Seven
men
in
D
space
six
then
we're
turning
back
to
D
space
five
and
it
would
be.
A
E
This
is
pretty
close
because
we're
trended
on
the
console
starting
a
server
with
certain
parameters
and
then
that
kicked
off
the
whole
process.
You
could
probably
ride
a
simple
Python
script
did
anything
you
can
do
under
console,
you
can
do.
We
are
calling
command
line
command
line
commands
basically,
and
so
you
could
develop
the
simple
script
that
just
does
whatever
he
did
clicking
away.
Where
is
the
simple
command.
B
E
B
E
E
B
E
B
Yeah,
it's
definitely
doable.
It's
not
something
I've
ever
written
myself,
but
I
would
encourage
others
to
kind
of
build
off.
Of
that.
That's
kind
of
what
this
whole
idea
of
these
developers,
Show
and
Tell
things
are-
is
to
try
and
share
what
we've
done
and
see
if
we
can
figure
out
ways
to
improve
upon
it
or
work
together
on
various
aspects.
A
Yeses
beats
figure
which
I'm
just
sharing
my
desktop
back
out
to
point
out
to
you
all
that
that
we
do
have
this
developer
show
until
the
meeting
page
on
the
wiki,
and
so
as
any
ideas
come
to
mind,
feel
free
to
log
them
here
also
just
kind
of
register
if
you're
interested
so
I.
Based
on
since
we
had
a
great
turnout
today,
I'll
I'll
plan
to
schedule
a
follow-up.
A
One
of
these
I'll
see,
if
Patrick's
available
to
present
at
the
next
one-
and
we
are
any
even
from
prior
brainstorming-
have
a
handful
of
other
potential
topics.
So
you
know
it's
as
long
as
we've
got
interest
and
we've
got
topics
I'm
happy
to
help.
You
know,
as
set
these
up
on
a
somewhat
regular
basis
and
I'll
also
kind
of
once
tim
has.
The
video
of
this
meeting
uploaded
will
link
it
out
to
the
individual
meeting
page
and
then
kind
of
start
start
a
planning
cycle
for
the
next
meeting,
probably.
L
A
B
A
K
Go
ahead.
I
was
wondering
about
your
specific
question
Terry,
but
Dale
having
different
instances
going
that
you
may
I'll
bring
up
and
down.
Do
you
really
need
a
whole
machine
for
it,
for
instance,
or
would
it
do
just
to
have
they?
You
know
Tom
kick
well
next,
a
you
know
database
on
the
instance
somewhere.
A
I'm
I'm
not
trying
it's
kind
of
like
my
like
between
what
Tim
showed
today
and
then
the
experimentation
I've
sort
of
done
on
my
own
with
doctor,
it's
kind
of
it's
it's
hard
for
me
to
wrap
my
head
around
all
the
possibilities
that
there
are
I
mean
a
a
nice
thing
with
these
full
instances
are
if
you
are
working
on
something
that
requires
some
conversation,
they're
easy
to
share
with
other
people
and
have
other
people
take
a
look
at
your
work.
So
I
think
it's
important.
Sometimes.
I
B
Yep
yeah
with
that
and
in
fact,
I
think
that
that's
where
it
gets
back
to
what
Monica
was
mentioning
about
different
AWS
tools
that
you
could
be
leaning
on
more
heavily
here.
So
if
you
use
something
like
Amazon
RDS,
the
remote
database
setup,
you
could
actually
have
three
databases
in
there:
one
for
D
space,
5
D
space
6
and,
like
the
latest
version
for
master
or
whatever,
and
then
you
could
do
this
all
in
one
server
potentially,
so
that's
just
there's
many
different
ways.
You
can
deploy
things
in
the
cloud.
B
A
That
I
floated
around
some
time
last
year.
Was
you
know
with?
Would
it
like
it's
it's
so
great
that
we
have
demo
D
space
or
give
ailable,
but
would
it
ever
be
possible
for
our
other
supported
versions
that
are
in
production
to
have
like
a
demo
D
space
org?
That
runs
the
latest
version,
5
and
I?
Guess
I!
Guess
since.
J
A
Is
still
supported,
one
that
could
run
the
latest
version
4,
so
we
just
always
be
able
to.
You
know:
click
in
and
see
the
I
actually
not
only
run
the
latest
release
but
run
the
latest
active
branch
for
each
of
the
the
maintain
branches
just
so
that
it's
always
accessible
without
needing
to
build
locally.
B
Yeah
I
mean
that's
a
good
point.
Teri
we
could
I
mean
with
these
tools
that
I
just
showed
off
today.
You
could
definitely
do
that.
I
think
the
hardest
parts
would
be
in
the
dependencies
areas,
just
making
sure
that
DSPs
4,
of
course,
has
different
Postgres
dependencies
than
D
space,
5
and
D
space
6,
so
you'd
have
to
kind
of
have
different,
potentially
different
versions
of
Postgres
installed
and
things
of
that
nature,
but
you
otherwise.
C
E
A
B
My
experience,
it
tends
to
be
the
the
server
itself,
is
a
little
bit
more
pricey
and
the
storage
like
in
volumes
the
number
of
all
units,
depending
on
how
big
that
the
storage
volumes
are
those
plus,
if
you're
doing
server
backups,
which
Amazon
calls
snapshots.
Those
can
add
up
a
little
bit
as
well
depend
on
how
frequently
you
snapshot
things
but
I.
Why.
E
B
B
Think
it's
really
a
matter
of
making
sure
we
get
the
right
prerequisites
installed.
I'm,
not
sure
these
same
scripts
would
work
for
all
the
way
back
to
D
space,
for
they
might
but
I'm
pulling
in
third-party
libraries,
as
I
mentioned,
to
install
Tomcat
and
Co
stress
and
all
that
sort
of
stuff
and
I
don't
know
what
versions
off
top
my
head.
Those
are
installing
in
all
situations
and
whether
those
versions
will
match
up
with
what
D
space
for
expects.
So
so
I
think
that's
one
thing
that
I've
not
looked
into
but
other
than
that
yeah.
C
C
A
G
B
Nothing
in
what
I
showed
off
today
is
Amazon
specific.
It's
there
are
things
that
I
mentioned,
which
were
a
bun,
2
or
Debian
specific,
mainly
that
puppet
D
space
module,
but
everything
else
is
generic
for
any
any
cloud
service
platform.
So
you
could
use
this
on
Google
cloud
or
whatever
other
one.
You
want
to
use.
B
I
kind
of
glanced
over
because
it
wasn't
something
to
really
point
out
too
much,
but
there
is
a
puppet
module
that
I
installed.
It
was
called
under
unattended
upgrades
or
updates,
which
is
a
puppet
module
that
basically
triggers
a
cron
job
to
do.
Apt-Get
upgrades
and
affricate
upgrade
updates
on
a
regular
basis,
so
that
does
get
set
up
on
this
server
automatically
great.
A
H
Can
hear
me
now
yeah,
okay,
yeah!
That's
fine!
Actually!
But
if
you
know
is
interested
if
you
just
visit
generative
technology
and
then
our
github
page
we're
working
a
bit
on
getting
that
set
up
and
almost
there
and
I'll
be
exciting
to
show
the
project
but
unfortunately
well
I
think
what
I'm
gonna
do:
I'm
gonna,
probably
boot
up
Windows
on
my
laptop
next
time,
because
there's
an
issue
with
the
graphics
driver
here,
so
apologize.