Difference between revisions of "Image handling in edge environment"
(Created page with "= Architecture options for Glance = This page contains a summary of the Vancouver Forum discussions. Full notes of the discussion are in [https://etherpad.openstack.org/p/yvr-...") |
|||
| Line 2: | Line 2: | ||
This page contains a summary of the Vancouver Forum discussions. Full notes of the discussion are in [https://etherpad.openstack.org/p/yvr-edge-cloud-images here]. | This page contains a summary of the Vancouver Forum discussions. Full notes of the discussion are in [https://etherpad.openstack.org/p/yvr-edge-cloud-images here]. | ||
== One Glance with multiple backends == | == One Glance with multiple backends == | ||
| − | There is one central Glance what is capable to handle multiple backends. Every edge cloud instance is represented by a backend. The syncronisation of the image data is the responsibility of the backend (eg.: Ceph). OpenStack services in the edge cloud instances are using the images in the Glance backend directly. | + | There is one central Glance what is capable to handle multiple backends. Every edge cloud instance is represented by a backend. The syncronisation of the image data is the responsibility of the backend (eg.: Ceph). OpenStack services in the edge cloud instances are using the images in the Glance backend directly. <br/> |
| + | [[Glance-edge-architecture-multiple-backends.PNG]] | ||
Revision as of 23:11, 22 May 2018
Architecture options for Glance
This page contains a summary of the Vancouver Forum discussions. Full notes of the discussion are in here.
One Glance with multiple backends
There is one central Glance what is capable to handle multiple backends. Every edge cloud instance is represented by a backend. The syncronisation of the image data is the responsibility of the backend (eg.: Ceph). OpenStack services in the edge cloud instances are using the images in the Glance backend directly.
Glance-edge-architecture-multiple-backends.PNG
