Revision 32fcee13
b/docs/plankton.rst | ||
---|---|---|
8 | 8 |
|
9 | 9 |
Plankton is the synnefo Image Registry Service. It is implemented as a very thin |
10 | 10 |
layer on top of Pithos+; every Image on Plankton is a file on a Pithos+ backend, |
11 |
with special metadata. At the frontend, Plankton implements the OpenStack Glance |
|
12 |
API; at the backend it queries an existing Pithos+ backend. In the current |
|
13 |
implementation the service runs Plankton and Pithos+ on a single, unified |
|
14 |
backend: users may synchronize their Images, using the Pithos+ clients, then |
|
15 |
register them with Plankton, with zero data movement. Then spaw new VMs from |
|
16 |
those images with Cyclades. |
|
11 |
with special metadata. At the frontend, Plankton implements the OpenStack |
|
12 |
Glance API; at the backend it queries an existing Pithos+ backend. In the |
|
13 |
current implementation the service runs Plankton and Pithos+ on a single, |
|
14 |
unified backend: users may synchronize their Images, using the Pithos+ clients, |
|
15 |
then register them with Plankton, with zero data movement. Then spawn new VMs |
|
16 |
from those images with Cyclades. |
|
17 |
|
|
18 |
Let's see below: |
|
19 |
|
|
17 | 20 |
|
18 | 21 |
.. image:: images/synnefo-clonepath.png |
19 | 22 |
|
23 |
The figure shows a sailor bundling his physical machine with the |
|
24 |
``snf-image-creator`` tool, uploading the file to pithos+, registering the file |
|
25 |
as a new image with plankton and then spawning two new VMs with Cyclades from |
|
26 |
this image. |
|
27 |
|
|
20 | 28 |
The :ref:`Plankton API <plankton-api-guide>` is implemented inside Cyclades, so please consult the |
21 | 29 |
:ref:`Cyclades Documentation <cyclades>` for more details. |
22 | 30 |
|
Also available in: Unified diff