Add backup to cinder architecture page
Change-Id: Iedf0f5d36fbda8af95bc6e864bdaedef80a62df4
This commit is contained in:
parent
1eccae469c
commit
de5ec07077
@ -35,9 +35,9 @@ Below you will find a brief explanation of the different components.
|
||||
|
|
||||
|
|
||||
cinderclient |
|
||||
/ \ |
|
||||
[ Web Dashboard ]- -[ api ] -- < AMQP > -- [ scheduler ] -- [ volume ] -- ( iSCSI )
|
||||
\ / |
|
||||
/ \ | /- [ scheduler ] -- [ volume ] -- ( iSCSI )
|
||||
[ Web Dashboard ]- -[ api ] -- < AMQP > --
|
||||
\ / | \- [ backup ]
|
||||
novaclient |
|
||||
|
|
||||
|
|
||||
@ -51,3 +51,4 @@ Below you will find a brief explanation of the different components.
|
||||
* Auth Manager: component responsible for users/projects/and roles. Can backend to DB or LDAP. This is not a separate binary, but rather a python class that is used by most components in the system.
|
||||
* scheduler: decides which host gets each volume.
|
||||
* volume: manages dynamically attachable block devices.
|
||||
* backup: manages backups of block storage devices.
|
||||
|
Loading…
Reference in New Issue
Block a user