►
From YouTube: OpenShift Commons .EDU SIG #1: OpenShift @ UNC.EDU
Description
OpenShift Commons .EDU SIG Chair, Stephen Braswell will kick-off the .EDU conversation with a presentation on the OpenShift use case(s) at UNC/Chapel Hill and talk about their experiences migrating from V2 to V3 as well as their future plans for utilizing the platform.
We are planning on bi-monthly meetings depending on the group’s schedules and interests.
For the latest information on OpenShift 3.1 and available briefings, please visit http://commons.openshift.org or subscribe to the OpenShift Blog (https://blog.openshift.com).
The OpenShift Commons exists to provide a platform for customers, partners, developers and other open source technology initiatives to collaborate, share and accelerate the pace of innovation and adoption of OpenShift globally.
The OpenShift Commons represents a new open collaborative community model designed to facilitate communication and sharing of best practices, feedback and development across the many open source initiatives that integrate with OpenShift. The best way to get involved is to join the conversation today at http://commons.openshift.org
A
A
So
hello
and
welcome
everybody
to
the
dot
edu
special
interest
group
I'm
Diane
Mueller
I
am
the
director
of
community
development
at
Red,
Hat
for
open
shift
and
the
open
shift
ecosystem,
and
today
we
have
with
us
our
new
chair
for
the
evening
special
interest
group,
Steven
braswell
from
unc-chapel
Hill,
who
was
voluntold
or
von
coerced
into
chairing
this
see.
So
we're
really
pleased
to
have
him
with
us.
A
We
have
a
bunch
of
other
folks
who
are
on
the
mailing
lists
on
the
main
mailing
list
for
open
shift,
a
lot
of
other
Edu's.
Besides
UNC,
these
are
just
a
few
of
the
ones
who
accepted
today's
invitation
to
talk
on
that
right
out.
Where
have
linux
and
all
kinds
of
other
products
and
lots
of
other
edu
situations,
but
really
we're
trying
to
focus
this
specific
interest
group
on
things
like
open
shift.
A
One
of
the
things
I'm
going
to
ask
you
to
think
about
is
whether
you
like
to
use
or
willing
to
use
or
able
to
use
slack
or
are
avid
users
of
IRC
in
different
ways
that
we
can
communicate
with
each
other
and
that's
kind
of
what
I'm
trying
to
figure
out
how
what
the
best
way
to
engage
in
these
conversations
will
be.
And
so
that
would
be
helpful
to
know
for
me,
but
for
today's
agenda.
A
What
we're
thinking
we're
going
to
do
together
and
you
can
change
the
mission
and
the
goals
of
this
as
you
want,
as
the
edu
folks
is,
to
discuss
and
develop
and
disseminate
best
practices
for
administering,
managing
and
operating
open
shift
in
and
ed.
You
said
it
I
find
that
can
mean
lots
of
things.
A
There's
a
web
page
set
up
here
with
the
URL
for
the
sig
off
of
the
common
site
and
we've,
as
I
said,
coerced
Stephen
braswell
at
UNC
to
chair
this
this
session
and
so
I'm
going
to
stop
sharing
my
screen
and
let's
Steven
talk
a
little
bit
about
his
experience,
because
my
university
days
are
long
behind
me,
but
I'm
very
grateful
to
have
Steven
here
with
us.
Even
if
you
want
to
share
your
screen,
I
hi.
B
The
first
a
little
bit
about
me,
I've,
been
working
for
a
little
more
than
16
years.
I
work
in
our
middleware
services
group,
which
is
in
the
central
idea
group
and
the
things
that
we
do
is
we
manage
basically
applications
infrastructure
which
torical
system
administrator
type
people
that
we
still
work
some
with
systems.
But
we
have
a
separate
group
that
manages
the
operating
system
and
hardware
level
for
us.
We
manage
basically
everything
about
that
part
of
the
applications
on
that
includes
Sakai
for
learning
management
openshift.
B
We
have
a
big
wordpress
installation
or
two
big
work
person's
license
for
content
management.
We
still
have
legacy
apache
web
servers
that
host
various
static
content
and
programmatic
content
for
end
users.
At
the
university.
We
have
a
large
number
of
Java
applications.
Some
of
them
are
custom
applications
for
departments
that
a
house
and
tomcat
we
have
jboss
for
some
applications
specifically
are
supported
on
jboss,
and
then
we
still
have
our
use
glass
fish
for
some
custom.
B
Basically
erp,
like
systems
they're
things
that,
even
though
we
implemented
peoplesoft
their
functionality,
that
peoplesoft
doesn't
do
that's
custom
to
the
university.
So
we
have
java
applications
that
are
dedicated
for
that
where's,
a
runner
alone
of
log
aggregation
system.
When
you
spoke
for
that,
we
have
application
performance
monitoring
tools,
we
manage
collaboration
tools
for
university.
We
just
recently
took
on
helping
manage
reporting
systems
a
lot
of
other
base,
basically
web-based
services.
They
get
thrown
our
way
I'm.
So
our
group
does
a
lot
for
central
IT
and
so
that
other
chefs
are
like
part
of
that.
B
I
mean
to
it
this
way,
then
all
right,
so
one
of
the
things
that
my
group
really
tries
to
do
is
is
help
with
devolution,
IT.
So
outside
of
universities,
people
are
growing
with
the
industry.
Universities
can
be
a
little
slow,
particularly
where,
as
a
state
government
entity,
so
we
move
a
little
slower,
since
our
funding
depends
on
on
state
funding.
So
we've
been
we've
been
evaluating
the
okay.
What
do
you
run
them
fair
matter?
B
What
do
you
run
ambience
and
these
days,
what
is
more
appropriate
for
running
in
containers
and
we're
trying
to
lead
that
here
at
UNC,
Chapel
Hill
and
includes
things
like
implementing
open
shift
for
PA's
working
on
tools?
Why
puppet
and
ansible
for
automation,
and
so
on
and
so
on?
So
that's
that's
one
of
the
reasons
that
we're
really
big
into
pushing
up
the
shift
is
we're
trying
to
get
things
moving
forward.
B
B
We
have
a
self-service
sign
up
tool
so
that
people
go
and
sign
up
for
the
service.
The
primary
reason
for
that
was
we
wanted
to
lock
down
the
namespace
to
their
university
user
ID
and
there
was
an
easy
built-in
way
to
do
that.
With
version
2,
I've
opened
shift,
so
we
wrote
it.
We
locked
off
people
being
able
to
create
their
own
accounts
and
they
have
to
go
through
our
tools
sign
up.
So
that
was
just
a
namespace
thing.
B
Some
of
the
benefits
we
saw
was
a
the
the
basics
of
OS
management,
the
operating
system,
the
the
programming
languages
day
basis.
All
of
that
we
manage
that
for
them,
and
then
they
don't
have
to
so
they
can
focus
on
developing
their
code,
their
student
doing
it
for
a
class.
A
professional
program
are
doing
it
for
the
business
of
university
or
someone
just
wanting
to
learn
a
programming
language.
B
We
also
had
instances
where
someone
might
be
just
hosting
a
web
server
just
to
run
some
peach
peacoat
and
and
they
bought
a
desktop
machine
they're
running
under
their
desk,
but
it
wasn't
getting
patched
so
we
had
the
vulnerability
issues
we
didn't
want.
We
wanted
to
provide
a
mechanism
so
that
people
aren't
doing
that
anymore.
We
also
have
some
internal
consolidation
needs,
as
I
mentioned
before,
we
have
a
lot
of
java
application
servers,
and
one
of
the
things
we
saw
was
a.
B
We
could
consolidate
that
onto
that
the
shift
platform
right
now
we
run
all
those
on
separate
beams
and
their
clusters
of
departments
and
and
other
units.
The
multiple
applications
might
live
in
the
same
java
container.
That
makes
tuning
the
JVM
very
difficult
because
all
the
applications
have
different
needs.
If
we
get
a
with
those
out
some
and
containers,
particularly
in
version
3
of
elven
shift,
we
could
tune
those
better
and
then
provide
some
autonomy
for
the
developers
do
to
manage
some
of
the
restarts
and
and
such
that
they
might
need
further
applications.
B
We
also
didn't
really
have
a
easy
way
for
a
lamp
functionality.
Basically,
if
you
wanted
that,
we
had
a
group
that
provides
you
with
a
virtual
machine,
but
then
you
had
to
manage
everything
yourself
and
not
bring
the
programming
languages.
Everything
patching
yet
managed
other
yourselves,
and
particularly
for
students
that
wasn't
provided
for
students
anyway,
and
we
want
to
provide
functionality
that
kind
of
functionality
but
make
it
easier
for
people.
B
We
also
had
some
departments
even
for
just
simple
services
like
drupal:
they
would
work
with
an
off-campus
vendor
and
that
vendor
would
host
it
for
them
or
provide
some
other
conservatives.
We
want
to
keep
that
spending
on
campus
and
even
though
we
provide
the
service
for
free,
you
know
it's
an
incentive
for
them
to
to
not
go
and
spin
it
off
campus
and
then
all
the
programming
and
content
resources
state
and
on
campus
network.
B
B
Our
initial
rollout
was
an
October
2014
at
first
we
created
we'd
set
up,
so
the
only
individuals
would
get
space
and
up
and
shift
after
we
do
that.
We
realized.
Oh,
that's,
we're
still
back
in
the
old
mentality
of
that's
tied
to
that
particular
user.
If
that
user
was
a
grad
student
or
an
employee
that
left,
the
university
is
still
tied
to
them
and
a
changing
ownership
of
that
was
the
Harper
to
exist.
B
The
namespace
was
tied
to
their
user
ID
and
then
that
was
internet
Ida
into
DNS,
so
to
work
with
the
departments
and
other
project
needs.
We
create
a
separate
admission
shift
environment
just
for
departments
and
projects
and
what
we
did
there
is
we
created
a
fake
user
ID
that
wouldn't
conflict
with
the
university
IDs
that
basically
owns
the
the
namespace.
B
Even
if
there's
only
one
application
in
the
namespace,
we
did
that
so
that
it's
not
tied
to
an
individual.
You
set
up
access,
controls
and
such
and
then
provides
a
mechanism
for
the
collaboration
stuff
to
be
to
be
easier.
We
fronted
the
hardware
and
software
costs
for
three
years,
so
we
could,
we
know
to
do.
We
had
time
to
work
on
getting
an
implemented
I'm
getting
people
used
to
using
the
system
without
having
to
worry
about.
Okay,
it's
been
year,
one.
B
We
need
to
need
to
fund
it
again
and
then
one
of
the
things
that
red
had
helped
us
with
was
we
did
a
training
session
of
about
or
something
people
that
was
an
interesting
learning
experience
trying
to
get
others
people
on
the
same
page.
We
start
started
from
scratch,
we're
basically
they
we
work
with
them
to
install
get
on
the
machine
if
a
dinner
exists
and
then
going
through
setting
up
on
a
simple
application
that
we
developed
and
setting
it
up
a
database
and
breaking
it
and
then
showing
them
how
to
fix
and
stuff.
B
For
the
most
part,
it
was
a
good
idea.
Probably
could
have
probably
should
have
done
it
with
a
smaller
group
of
people.
All
we've
done
instead
is
a
will,
go
out
and
work
with
departments
and
groups
101
and
re-evaluate
whether
a
training
session
is
a
as
a
good
idea
in
the
future
one
other
bit.
That's
not
on
this
slide
is
we
started
our
proof
of
concept
roughly
around
December
2013
january2014,
and
worked
on
that
for
a
couple
months.
B
We
were
ready
to
actually
go
live
between
august
and
sep
tember
of
that
year,
but
we
had
some
other
major
projects
that
we
can
go
live
at
the
same
time
and
we
were
asked
to
delay.
So
we
were
ready
to
start
a
little
bit
earlier,
but
just
well
didn't
have
the
opportunity
to
if
anyone
who's
already
deploying
upshift
on
site
and
that's
the
other
thing
that
I
briefly
skimmed
number
fours.
B
We
are
running
an
on-premise,
it
is
basic
architecture,
like
I
said
before
we
had
the
individual
space
and
then
we
set
up
a
departmental
one.
Under
the
departmental
section,
you'll
see
some
boxes
label
sensitive.
One
of
the
things
that
we
want
to
do
is
be
able
to
offer
sensitive
data
which
I'll
talk
about
love
it
later,
where
the
HIPAA
and
FERPA
and
day
I
that
and
just
so
that
we
need
a
duplicate,
that
we
share
support
nodes,
which
is
our
dns
server,
our
DB
and
activemq
for
evan
shift.
B
I
mentioned
the
leg
CFS
space,
our
old
web
servers
have
lots
of
programmatic
content
there
and
we're
helping
people
would
use
a
system
to
to
migrate
the
data
or
deny
great
those
applications
from
the
old
system
into
this,
where
it's
little
modern
and
they
have
a
little
more
control
and
and
information
like
logs
and
stuff
where
they
don't
have.
Access
to
that
today,
I
mentioned
that
we
have
a
big
wordpress
installation
or
we
provide
a
multi-site
wordpress
for
users
to
set
up
websites
with
a
common
set
of
plugins
and
themes
we
do
have.
B
They
do
run
into
some
problems
where
a
department
may
want
a
plug-in
or
theme
specifically
for
a
professor
that
no
one
else
wants
to
use
so
for
the
the
shared
environment
there.
The
team
that
manage
that
says
well
we're
not
going
to
install
that.
So
we
expect
two
people
would
want
to
run
their
own
WordPress
as
their
own
drupal's
and
produce
their
own
versions
of
plugins
and
such
and
the
shift
will
be
a
place
for
them
to
do
that,
so
that
still
campus
resources,
they
don't
to
manage
the
Vian's
and
such
we
are
university.
B
We
also
expected,
since
we
do
have
a
computer
science
department,
classroom
uses
particularly
there
and
that
hasn't
there's
a
minute's
much
use
of
that.
Yet
there
is
interest
interest
once
we
get
to
the
shift
version
3
where
we
are
working
with
a
computer
science.
Professor
was
interested
in
using
ipython
Jupiter
to
do
some
classroom
stuff
there
and
so
we're
working
off
and
on
with
him
on
his
needs.
There.
A
B
I
talked
to
Graham
at
summit
and,
and
we
and
he's
very,
very
willing
to
to
help
me
with
the
ipod
on
Jupiter
stuff.
What
I
needed
to
do
is
have
a
subsequent
meeting
with
the
professor
to
gather
some
more
information
about
how
the
professor
wanted
to
use
it.
And
then
Graham
could
have
better
write
up
a
use
case
for
me
and
how
to
deploy
that
in
v3.
B
Some
metal
use
cases
where
the
ones
we
expected
and
here's
some
that
were
people
actually
use
the
platform.
One
of
them
is
we
work
for
the
professor,
who
had
some
students
developing
some
mobile
applications
for
him,
though,
that
think
the
professor
was
in
some
biology
department.
So,
basically,
the
mobile
application
allowed
like
high
school
students
or
middle
school
students
go
out
into
the
field.
You
know,
there's
out
on
a
field
trip
and
they'll
use
the
mobile
application
to.
B
Identify
bugs
and
the
plants
to
their
own
and
such
while
that's
running
on
actually
on
Android
devices,
the
API
for
that
and
the
backend
database
was
running
on
up
the
shift.
We're
really
happy
to
work
for
them
on
that
and
continue
to
work
with
them,
and
they
seem
to
be
very
happy
with
the
platform
we
have
someone
who
wrote
some
kind
of
a
psychology
blind
study,
no
sensitive
data
there,
an
application
to
handle
that
people
using
it
for
digital
signage.
B
So
the
back
end
displays
for
for
the
content
of
the
digital
signs
on
their
dues.
In
that
the
bishop.
For
that
again
image
about
the
wordpress
stuff,
people
are
using
putting
up
their
own
Department
websites
and
various
either
CMS's,
either
WordPress
or
Drupal
them.
Then
we
didn't
even
know
until
we
start
seeing
the
traffic
coming
in
so
that
was
kinda
grade.
B
We
worked
with
the
researcher
who
was
writing
a
virology
web
application
on
that
the
application
will
actually
hosted
on
openshift,
but
then
it
would
interact
with
our
research
computing
cluster
through
an
API
and
on
submit
jobs,
get
information
about
jobs
and
such
and
then
our
help
desk,
which
we
caught
the
service
desk,
is
moving
a
lot
of
their
internal
applications
for
like
looking
at
call
volume
looking
at
a
other
help
desk
release,
it
just
exciton,
remember
all
of
their
applications.
At
this
point,
they've
been
living
so
many
moving.
B
Those
from
vm
said
that
had
been
posted
for
them
into
our
platform
and
they're
particularly
interested
once
we.
If
we
ever
get
into
evaluating
the
new
net
functionality,
they
have
some
net
applications.
They
run
on
Windows
servers
and
they're,
very
simple,
so
that
there's
no
reason
they
couldn't
run
them
on
FB
shift
in
the
future
and
we
hope
to
work
with
them.
On
that.
B
Oddly,
the
one
of
the
other
top
cartridges
for
v2
deployment
was
cron
sort
of
a
lot
of
people
join
scheduling
in
the
application
as
well.
So
that's
kind
of
nice
I've
hinted
before
about
sensitive
data
they're.
Currently,
our
information
security
office
has
an
approved,
are
appreciative,
version
2
for
sensitive
data,
and
we
really
and
we
have
been
working
with
them
for
a
little
over
a
year
to
that,
it's
not
technical
challenges
of
the
platform.
B
It's
more
policy
on
our
end,
we're
trying
to
be
play
nice
and
ask
them
for
permission
to
be
able
to
host
sensitive
data
or
not
every
group
at
the
University.
You
know
talks
to
them.
First,
they
talk
to
them
later,
go
talk
to
them
first,
and
so
we
got
more
down
and
then
deciding
that
they
need
to
punch
out
a
lot
more
of
the
policy.
We've
been
working
with
them
on
on
meeting
any
issues
that
they
have
with
the
platform
again,
and
it
was
never
really
loved.
B
The
shift
was
about
policy
of
how
are
you
doing
back
up
tight,
going
log
management,
aggregation
and
things
like
that,
so
we
working
with
them
to
get
that
we're
very
close
to
that.
Finally,
and
once
and
we
have
a
lot
of
people-
a
lot
of
departments,
particularly,
we
want
to
host
things
that
hope
that
have
sent
HIPAA
data
and
we
expect
that
once
that's
approved,
the
numbers
will
dramatically
start
increasing
online
usage
they've
installed
a
little
bit
at
this
point,
but
we
expect
that
a
dramatically
increase.
B
Some
of
the
challenges
we
had
was
historically,
we
were
behind
the
scenes
group
where
we
manage
the
system,
but
we
didn't
actually
directly
deal
with
on
campus
customers.
We
directly
to
quit
dealt
with
other
IT
people,
mostly
in
within
our
own
department
and
a
few
in
other
departments.
This
is
our
first
one
on
direct
directories
directing
directly
interacting
with
customers
and
helping
them
out
getting
their
application
to
deploy
and
such.
So
that
was
a
challenge
for
us
as
many
of
you
working
or
she's.
B
No,
you
have
varying
people
who
might
be
using
the
system
that
there
might
be
an
administrative
person
in
office.
Just
doing
some
things
with
WordPress,
it
might
be
a
student,
it
might
be
a
seasoned
developer,
so
the
varying
ranges
of
technical
skills
and
and
helping
those
people
was
initially
a
challenge
for
us
well,
which
kind
of
goes
along
with.
In
the
next
one
of
customer
documentation.
Allred
had
had
great
documentation
on
using
appreciate
platform.
We
wanted
to
have
some
custom
documentation
for
our
our
implementation
and.
B
Write
the
documentation
is
such
that
it
would
cover
everyone
from
their
varying
technical
skills,
so
that
why
we
understand
you
have
some
technical
knowledge
to
use
the
platform.
We
provide
the
commands
that
you
need
to
run
to
do
the
basic
operations
and
then,
for
example,
this
WordPress
that
you
just
interact
with
the
WordPress
interface
after
that
for
a
lot
of
our
developers.
They
are
particularly
our
professional
developers.
They
were
big
diversion
users,
so
is
the
workflow
change
for
them
to
use
git?
B
Instead,
they
weren't
big
into
necessarily
big
into
the
open
source
world,
so
they
hadn't
had
a
lot
familiarity
with
get,
and
we
saw
has
enchanted
with
that
today,
then,
the
workflow
of
of
pushing
in
to
get
and
then
it
automatically
getting
deployed
on
others
the
challenge
for
some,
our
customers
that
we
had
to
work
with,
and
since
we
really
wanted
people
to
start
using
the
platform,
so
marketing
was
a
big
challenge
for
us.
I'll
show
next
slide
that
we
we
work
with
our
communications
office.
B
That
was
a
big
thing
for
us
that
we
create
a
developer
liaisons
program,
which
is
just
people
in
my
group
who
will
go
out
and
work
with
customers
one-on-one
on.
Usually
it's
been
feeding
groups
that
are
helping
a
professor
or
departmental
programmers,
helping
them
get
used
to
the
way
the
platform
works
again.
The
developer
workflow
changes
that
we
mentioned
and
that's
been
really
successful.
B
B
We
working
with
our
team
that
runs
our
virtual
management
platform
and
and
make
sure
the
we're
all
in
the
same
page
so
that
when
we
give
our
disparate
presentations
around
campus,
we
can
correctly
direct
people
to
which
they
might
which,
whether
they
need
a
container
whether
the
UVM
degree.
Obviously
a
high
memory
high
CPU
applications.
B
You
prefer
on
a
bit
on
a
virtual
machine
and
then
on.
Another
challenge
that
continues
today
is
application
backups.
So,
while
we
do
system
level
backups
for
disaster
recovery
reasons,
we
documented
that
our
customers
needed
to
do
their
own
application
backups
using
the
commands
and
our
HC
tool
for
up
and
shift
and
who
is
also
the
challenge
of
our
one-time
backups,
are
system
wide
backups
aren't
going
to
capture
by
the
point
time
database
backup,
which
may
not
be
in
a
consistent
state
if
it
needs
to
be
restored.
B
So
that's
been
an
ongoing
challenge
for
us
as
how
to
do
that.
How
are
we
going
to
do
that?
Handle
that
in
the
future
and
and
work
with
our
customers
on
that
as
I'm
each
before
we
had
marketing?
So
we
have
posters
stickers,
some
little
business
cards
and
we
went
to
overboard
with
the
Philadelphia
way
there
just
one
it's
in
my
boss's
office,
but
again
we
really
wanted
to
get
people
to
use
the
system.
So
you
know
telling
people.
B
That's
there
tell
me
what's
free
and
getting
the
word
out
the
way
we
looking
at
the
future
again
the
sensitive
data
thing
I
mentioned
we're
close
to
getting
approval
for
appreciate
version
2.
They
want
to
start
the
process
over
with
version
3.
We
don't
expect
that
process
to
take
quite
as
long
but
again
it
since
version.
3
is
a
rewrite
our
information
security
office.
We
need
to
reevaluate
some
of
the
things
that
they
did
for
a
version
to
the
biggest
thing
for
the
future
is
moving
to
shift
version.
B
3
we've
been
working,
we
have
a
proof
of
concept
for
that.
We
don't
have.
We
haven't
set
up
our
production
platform
yet
and
that's
that's
one
of
the
biggest
things
around
up
shift
that
we're
working
on
these
days.
I
mentioned
before
the
GlassFish,
the
Tomcats,
the
job
applications
we'd
love
to
move
those
into
of
the
ship
version
3,
particularly
so
that
individual
applications
have
their
own
individual
containers.
The
JVM
can
be
tuned
for
those
applications.
The
developers
can
stop
and
restart
the
application
themselves.
I
haven't
involved
us
things
of
that.
B
We
toyed
around
with
the
idea
of
putting
sekalian
of
a
shift.
I
mean
it's
that
we
haven't
even
talked
to
our
learning
management
team,
about
that.
It's
just
an
idea
that
we
have
on
that.
We'd
like
to
do
because
again
it's
a
java
application,
so
it
could
fall
into
the
same
categories,
are
other
ones
when.
A
A
B
B
That
would
be
really
nice
for
us
to
able
to
do
and
and
even
for
other
applications
where
okay,
darn
student
registration,
we're
getting
hit
a
lot
so
will
temporarily
scale
things
up
to
twice
as
many
containers
and
then
once
that's
over
will
scale
them
back
down
and
and
not
having
to
have
a
full
operating
system
and
says
would
be
really
nice.
For
those
cases.
B
Another
thing
at
Summit:
we
saw
a
presentation
by
someone
at
Duke
University
who's,
just
down
to
read
from
us,
but
have
a
big,
their
multi-site,
wordpress
and
containerized
it
where
everyone's
have
being
part
of
them.
St.
multi-site
gets
their
own
container
of
WordPress,
and
then
they
can
kind
of
do
what
they
want.
That
was
an
interesting
idea
and,
and
what
would
eventually
talk
to
them?
They
aren't
using
up
and
shifted
on
it
with
native
docker
containers,
and
we
would
look
like
to
do
that
with
other
shift.
B
These
are
just
ideas
so
that
we've
been
tossing
around
in
version
3,
the
there's
a
log
aggregation
till
it
comes
in
the
elk
stack
just
using
flow
and
instead
of
log
stash
we're
heavily
invested
in
spunk.
So
big
thing
for
us
is
getting
the
logs
to
go
to
both
so
that
customers
inside
the
system
can
use
efk
to
look
at
their
logs,
but
we
get
a
copy
that
goes
to
spawn
far
information
security
office
to
look
at
particularly
for
departmental
applications
and
and
sensitive
applications.
B
We
didn't
do
a
five
load-balanced
integration
in
version
2
and
we'd
like
to
do
that
in
version
3.
There
were
some
challenges
in
version
2
because
you
had
to
have
some
ministry
of
excess
or
you
still
have
some
of
that
administrative
access
in
version
3.
But
we
worked
with
our
networking
team
who
manages
the
lib
bouncer
and
we
have
a
solution
for
that.
B
I
actually
have
some
ideas
about
how
to
basically
that
you
have
to
have
just
short
of
root
access
on
the
load
balancer
to
to
to
integrate
it,
and
it's
actually
a
limitation
by
f5
that
I
hope
to
submit
a
are
fe
to
have
them,
make
a
change,
and
then
you
still
need
some
privileged
access,
but
you
wouldn't
have
to
have
as
much
privilege
and
I'm
going
to
talk
to
the
open
shift
team
about
some
potential
workarounds
based
on
some
information.
I
gathered
from
f5
around
that
with
every
ship
version.
3.
B
We
get
a
right
to
run
license
for
cod
forms
just
for
the
shift
in
statistics
management
such
that
we're
evaluating
over.
We
had
that
installed
and
working
with
redhat
to
look
at
clot
forms
for
other
things,
but
the
in
the
new
version
of
coliforms
with
the
self-service
capabilities
and
then
the
charge
back,
schodack
abilities
for
containers
and
such
that
would
be
interesting
for
us
to
have
that
data.
Even
though
we
don't
charge
for
the
system
and
be
nice
to
be
able
to
have
that
kind
of
accounting
and
then
evaluation
in
mobile
platforms.
B
We've
again,
we've
worked
with
redhead
owner
on
posted
proof
of
concept
for
that
mobile
and
then,
with
the
new
rate
at
mobile,
you
can
host
some
components
of
it
on
site,
we're
not
a
reddit
mobile
customer,
but
we
are
allowing
the
product
just
to
see
if
there
is
interest
in
it
for
campus.
So
if
we
did
end
up
purchasing
it,
we
probably
hosted
on
Tanisha
platform.
A
B
A
B
B
B
The
v2
v3
migrations
made
the
big
thing.
We've
been
working
with
right
again
we're
not
far
from
the
Red
Hat
main
office.
So
we
do
get
the
value
add
of
being
able
to
work
for
them
closely
since
the
nearby
and
we've
got
some
information
about
some
initial
guides
on
migrating
applications.
We're
hoping
that
to
learn
from
what
they
do
for
the
shift
online,
that
they
have
millions
of
applications
who
are
hundreds
and
bringing
that
access
I'm
going
to
be
our
biggest
challenge
more
documentation.
B
So
we
wrote
a
lot
of
documentation
for
the
v2
there's
any
more
stuff.
Tickle
you
with
people,
some
basic
things
that
I
get
and
the
additions
of
components
with
darker
communities
means
that
there
are
just
more
things
we
need
to
tell
people
about,
though,
I
write
more
documentation
about
that
version.
2,
we
created
a
basic
Shibboleth
integration
for
just
a
few
languages
figuring
that
out
for
version.
3
has
been
a
challenge
and
that's
one
thing
that
we're
still
working
on
with
docker
troubleshooting
customer
applications
and
why
they
didn't
deploy
correctly.
B
We
already
see
that's
gonna,
be
a
challenge
will
be
do
it
with
our
very
simple
applications,
and
we
don't
have
good
ideas
on
that.
Yet
if
others
do
we'd
be
happy
to
hear
them
version
threes,
new
technology
challenges,
we
were
told
by
an
engineer
right
out
of
it.
We
we've
clicked
some
buttons
that
other
peoples
haven't,
and
so
we
find
some
bugs
that
they
haven't
so
just
getting
used
to
the
new
technology
and
inversion
3
you
again,
it
goes
back
to
even
the
familiarity
with
dr.
B
ku
bananas
that
we're
trying
to
get
through
again
application.
Backups,
there's
not
an
automatic
tool
like
there
was
in
v2,
since
you
have
persistent
storage
volumes,
the
backups
for
those
are
supposed
to
suffice
and
we
need
to
just
figure
out
a
policy
around
that
procedures
etc.
So
Pete,
our
customers
and
finally,
I
just
want
to
get
through
a
few
ideas
that
we
have
for
the
you
sig
and
then
I'll
hand
over
to
to
Diane
for
hanging
on,
for
what
she
has
biggest
thing
for
us
is
we're
very
open.
B
With
sharing
information
will
tell
you
everything
that
we
about
our
environment.
The
pain
points
that
we've
had
we'll
share
the
very
bad
tools
we
wrote.
You
know
things
like
that:
we're
hoping
that
others
will
be
the
same
way
for
their
implementations
goes.
You
know
for
profit.
Companies
and
ed
use
operate
very
differently
where
a
state
government
based
public
university.
So
we
have
some
challenges
that
may
be
private
universities.
Don't
they
need
that
kind
of
open
information
sharing
documentation?
B
Again
we
wrote
a
lot
of
internal
documentation
we've
given
that
to
universities,
we're
happy
to
give
it
to
other
universities.
We
have
ideas
about
maybe
coming
up
with
some
format
with
mark
down
and
storing
it
and
get,
and
then
you
can
substitute.
You
know
our
university
name
for
your
CV
name
on
a
business
ideas.
We
have
you.
A
B
B
Then
what
we
did
and
then
there's
our
contact
information.
The
email
addresses
for
everyone
in
our
cloud,
apps
team
and
then
our
website
just
shows
is
just
more
of
a
marketing
thing
in
our
sign
of
tool.
And
then
we
try
to
be
active
on
Twitter
we're
not
as
active
as
you'd
like
to
be,
but
those
are
ways
that
you
can
contact
us
and,
as
always,
you
can
contact
us
through
Diana
as
well,
and
that's
all
I
have
and
I'm.
A
A
I'm
also
gonna
ask
people
to
underneath
them
skills.
They
should
all
be
see
a
microphone
with
a
whole
red
slash
through
it
or
clock.
You
should
be
able
to
talk.
You
might
get
a
little
bit
of
an
echo
I.
Think
that's
one
of
the
problem
is
good
as
well.
Blue
jeans
sometimes,
but
thank
you
very
much
for
sharing
information,
would
love
to
maybe
even
a
guinea
pig
repo
on
github,
where
we
could
share
some
of
the
documentation.
A
Maybe
that's
something
we
can
set
up
I'm
going
to
share
my
screen
here,
just
to
drive
a
little
bit
more.
The
conversation
with
whom
I
have
questions
for
you.
The
first
question
I
have
is
well
I
should
ask.
Do
you
want
to
continue
meeting
as
a
cig
and
if
so,
how
often
would
you
like
to
meet
I,
have
a
time
slot
in
mine,
Wednesday
mornings,
this
time,
Pacific
I'm
on
the
west
coast,
but
that's
noon?
Eastern,
maybe
it's
your
lunch
break
is
what
I'm
hoping
and
I
know
most.
A
C
This
is
chris
from
the
University
of
Michigan
yeah.
This
time,
I
think,
would
generally
work
for
us.
This
is
noon,
so
it's
our
lunch,
break
and
wednesdays
tend
to
be
a
leading
light
day,
relatively
speaking,
monthly
seems
like
a
good
frequency
for
these
meetings,
at
least
to
start
with,
and
then,
if
they're
hurt,
seems
like
there's
a
more
content
or
less
than
we
can
address
from
there,
but
monthly
seems
like
a
good
initial
frequency.
One.
A
A
It
will
be
the
14th
so
I,
that's
what
I
was
going
to
propose
because
that'll
give
you
a
week
to
get
I'm,
not
how
your
school
start,
but
that'll
get
you
through
the
first
week
of
Labor
Day
and
everything,
but
that
was
what
I
was
thinking.
Any
objections
to
that
if
we
do
their
next
one
on
that
all
right
and
I'm
just
going
to
move
to
the
next
slide.
I'd
love
to
know
who
you
are
or
how
you
self-identify-
and
maybe,
if
I
spelled
administrators
right,
you'd,
admit
your
administrator
and.
C
No
I'm
sitting
here
with
two
other
guys:
I
am
a
business
analyst
with
our
teaching
and
learning
group,
and
the
guys
am
I
right
and
left.
Dave
and
Mark
are
both
system
administrators
there's
a
fourth
person,
that's
part
of
our
virtual
project
team,
who
is
analogous
to
what
the
way
that
Stephen
described
himself
he's.
Also
a
system
administrator,
but
more
working
with
client
focused
applications
as
opposed
to
underlying
systems.
Okay,.
A
Perfect,
so
that's
good
and
I
can
see
a
couple
other
folks,
but
they've
got
themselves
muted,
so
they're,
probably
in
places
where
they
can't
talk,
but
I'll
fought
back
here
and
so
I've
also
created
a
mailing
list
for
this.
So
I'll
send
the
same
questions
out
to
the
mailing
list.
There
were
a
number
of
topics
that
even
suggested
I
was
just
sort
of
taking
some
notes,
while
we're
going
through
there.
A
You
know
I,
probably
like
to
now
that
I
remember
they
did
that
presentation
on
multi-site
WordPerfect.
That
might
be
a
good
topic.
Two
things
do
not
have
to
be
exactly
openshift
specific
and
in
my
humble
opinion,
I,
don't
know
how
you
all
feel
about
that.
But
if
it's
things
like
get
fundamentals
or
containers
one
on
one,
we
do
OB.
There
is
another
cig
for
image
builders,
and
so
we
can
pull
some
of
the
content
from
that
and
talk
about
that
I
was
hoping.
A
But
this
is
about
sharing
across
different
massachusetts-based
educational
organizations
and
I've
kind
of
curious
to
hear
about
it,
but
Chris
I'm
wondering
if
on
the
next
one
on
the
fourteenth,
if
you
could
talk
a
little
bit
above,
what's
going
on
at
umich,
would
that
be
a
good
thing
or
is
there
a
specific
topic
that
everybody's
dying
for
like
the
elk
or
the
should
be
the
elf
or
the
EF
k
stack
or
something
like
that
is?
Is
this
kind
of
use
case
sharing
good
or
are
there
things
that
you'd
like
to
deep
dive
on?
A
A
So
we'll
do
something
similar
to
this
and
I'll
keep
reaching
out
and
bring
your
other
colleagues
to,
and
I
will
add
all
of
your
names
to
the
mailing
list
and
anyone
who's
listening
to
this
after
the
effect
after
after
that,
you
can
go
to
this
page
here.
That's
on
the
screen,
the
hashtag
interest
section
of
the
open
ship
commons
page
and
pick
the
edu
one
and
sign
up
for
the
edu
mailing
list,
and
that
will
get
you
on
there.
We're.
C
Going
to
try
a
couple
of
things
that
I
think
who
come
to
mind
for
me
in
terms
of
things
to
talk
about,
I
guess
I'd
be
interested
to
hear
the
other
people
on
the
line.
Other
people
online
are
interested
in
these
as
well,
but
one
is
near
the
model
that
people
are
using
to
provide
openshift
to
their
customer
base.
You
know,
is
it?
Is
it
pure
DevOps?
Is
it
more
standard
operations?
Is
it?
Is
it
something
in
between
or
is
it
a
development
group?
C
So
you
know
who,
who
is
it
that's
administering
openshift
and
how
they
are
working
with
their
customers?
Are
they
using
it
to
move
to
more
the
DevOps
model,
or
is
it
more
of
a
traditional
model?
So
that's
one,
and
the
second
thing
is:
is
there
kind
of
common
interest
in
some
of
the
enhancement
requests?
C
So
if
there
are
common
enhancement,
requests
across
multiple
schools
on
the
cig,
that
might
be
Dyan
useful
information
for
you
and
I
think,
probably
for
all
of
us
to
provide
a
red
hat
that
it's
not
just
an
individual
and
hands
burn
request.
But
there
are
multiple
schools
that
might
be
behind
some
of
the
requests
that
we
might
be
making
yeah.
A
That'd
probably
be
handy
for
people
who
haven't
done
that
yet
and
how
to
add
a
trial
card,
which
is
if
there
is
a
common
one
that
can
rise
up,
and
that
is
really
one
of
the
reasons
why
I'm
doing
this
sega's
so
that
you
guys
have
a
voice
and
make
that
make
those
kinds
of
collaborative
pushes
on
the
folks.
The
actual
people
who
are
writing
the
code
and
contributing
to
open
short,
openshift
origin.
So
that's
at
all,
but
I
also
think
that
we
can.
A
We
can
do
things
like
a
survey
about
your
question
about
what
models
people
are
doing
on
the
mailing
list
too.
That
is
a
long-standing
one
and
ask
people
those
questions
and
then
to
describe
their
their
their
model
and
how
they're
using
it,
or
maybe
the
evolution
of
that
and
then
coalesce
that
information
and
into
a
presentation
where
people
just
talk
about
that
and
what's
more
effective
for
them,
and
why
that's?
A
These
are
all
great
things,
I
think
once
a
month
it
will
work
very
nicely
so
that
we
don't
do
anything
and
what
I'm
going
to
encourage.
You
all
is
to
ask
all
of
those
questions
of
each
other
on
the
mailing
list,
and
you
should
get
invites
to
the
mailing
list
I
think
by
tomorrow
morning
I
will
add
everyone
who
was
invited
to
this
session
and,
if
there's
anyone
else
at
your
organization.
A
Those
there
anything
else.
Anyone
would
like
to
add,
because
we've
just
about
used
up
your
entire
hour
and
I,
really
want
to
thank
you
for
for
joining
us
today.
You
never
know
when
you,
when
you
kick
off
a
cig,
whether
tons
of
people
are
going
to
show
up,
and
it's
just
really
nice
to
have
all
of
you
here.
Sharing
these
your
best
practices
at
UNC
and
your
experiences
and
to
hear
from
you
also
thanks
and
I,
will
talk
to
you
all
on
the
mail
of
mailing
list
soon.