Automating Google Workspace (GWS) & more with Apps Script
OpenCloud - A Research Cloud
1. OpenCloud
–
A
Research
Cloud
–
Open
Network
Lab
PlanetLab
Consor5um
2. Goal
To
build
an
experimental
cloud
that
allows
the
research
community
to
both
use
and
influence
the
emerging
cloud
technology.
– Enable
research
into
new
cloud
architecture
– Enable
research
into
new
cloud
services
&
apps
– Accelerate
transi5on
of
scien5fic
community
to
the
cloud
3. OpenCloud
• OpenCloud
=
PlanetLab
x
ON.Lab
• Best
of
PlanetLab
– VM
Exper5se
+
Focus
on
the
Access
Networks
– Ac5ve
User
Community
• Best
of
Open
Network
Lab
– SDN
Exper5se
+
Focus
on
Data
Centers
&
WAN
– Ac5ve
Industry
Involvement
• In
Industry
Parlance…
– ON.Lab
x
PlanetLab
=
SDN
x
NFV
x
Cloud
4. Leverage
Open
Source
-‐
ON.Lab
-‐
PlanetLab
-‐
OpenStack
-‐
Open
Daylight
…
Commodity
Clouds
-‐
EC2
-‐
RackSpace
-‐
Google
App
Engine
-‐
MicrosoU
Azure
…
OpenCloud
-‐
Leverage
Open
Source
-‐
Opera5onal
System
-‐
Researcher
Access
-‐
End-‐to-‐End
Scope
5. ViCCI
(5
SDN-‐Capable
Data
Centers)
Internet2
(SDN-‐Capable
Backbone
+
ViNI)
PlanetLab/GENI
(200+
US
sites
w/
campus
SDN)
Pilot
Deployment
9. Node
Libvirt
(LXC)
OvS
Node
Libvirt
(LXC)
OvS
OpenCloud
v0.5
…
OpenCloud
CMS
New
API
Nova
Quantum
Dashboard
Keystone
Data
Model
Codifies
PlanetLab’s
value-‐add
and
provides
basis
for
extensions
10. Node
Libvirt
(LXC)
OvS
Node
Libvirt
(LXC)
OvS
OpenCloud
v1.0
…
OpenCloud
CMS
New
API
Nova
Quantum
Dashboard
Keystone
Data
Model
ONOS
NetVisor
11. Architectural
Challenges
• Unify
Resource
Management
– From
VM
Orchestra5on
to
Network
Management
– From
Data
Center
to
Network
Edge
• Define
User
Projec5ons
for
Diverse
Communi5es
– Scien5fic
Researchers
• want
n
VMs
and
a
predictable
interconnect
– Network
Service
Researchers
• want
to
control
VM
placement
and
network
configura5on
– Cloud
Researchers
• want
to
create
their
own
mul5-‐tenant
cloud
12. Architectural
Challenges
• Service
Orchestra5on
– Manage
Services,
not
Servers
– Fold
OpenCloud-‐enabled
innova5ons
back
into
OpenCloud
– Lower
the
barrier-‐to-‐entry
for
new
services
&
applica5ons
• Enable
“build
your
own
PaaS”
(thru
service
composi5on)
• Services
need
ops
too
(Management-‐as-‐a-‐Service)
• Rich
Service
Model
– Best-‐Effort
(with
and
without
admission
control)
– Guaranteed
capacity
with
ability
to
reserve
in
advance
– Guaranteed
capacity
with
a
long-‐term
commitment
13. Service
Orchestra5on
–
Exemplars
• Syndicate
–
Scalable
Storage
Service
– Composes
exis5ng
cloud
services
– Leverages
management
services
– Integrated
back
into
OpenCloud
(volume
per
slice)
• Na5veClick
–
Plug-‐n-‐Play
Control
Plane
– Used
to
configure
network
func5onality
on
end-‐hosts
– Used
for
service
chaining
&
middlebox
management
• OneBit
–
Wikipedia
for
Data
Analysis
– Used
to
monitor
and
diagnose
OpenCloud
health
– Distributed
data
collec5on,
analysis,
and
archiving
tool
– Mash-‐up
of
Storm,
Cassandra,
RabbitMQ,
and
ZooKeeper
14. Roadmap
PlanetLab
OpenCloud
OpenStack
Mechanisms
(LXC,
OvS)
OpenStack
Control
(Nova,
Quantum)
ViCCI
(Images
&
Service
Model)
New
Data
Model
API
&
GUI
ON.Lab
Tools
(NetVisor,
ONOS…)
You
are
Here
Not
to
Scale
15. SDN
x
NFV
• Goal
–
On-‐Demand
Customized
Virtual
Networks
– SDN
is
about
customizing
the
control
plane
– NFV
is
about
customizing
the
data
plane
• Alterna5ve
Means
to
the
Same
End
– OpenFlow:
Configure
the
VN;
ajach
VMs
to
the
edge
– Overlays:
Configure
tunnels
between
VMs
(proxies
&
edge)
– Hybrid:
Overlay-‐spec
with
SDN-‐enabled
hardware
assist
• Keep
interface
as
low-‐level
and
interoperable
as
possible
• Managing
Service
Composi5on
– Service
chaining
(interconnect
VMs
–
bump
in
the
wire)
– Controlled
touch-‐points
between
virtual
networks
16. Syndicate
S3
Local
NFS
SwiQ
Metadata
Service
(NoSQL
DB)
UG
UG
AG
RG
RG
RG
UG
Caches
+
Request
Routers
(CDN)
Data
Sets
Shared
Volume