2d44b2b36d
The new sphinx version introduces some changes that break build: * Warns if code cannot be parsed for highlighting. Fix the code so that it can be parsed, this includes uncommenting "..." lines. Note that not every config file is an ini-file. Also, the parser seems to have bugs and cannot parse all files. Fix mysql ini file and enable the parameter, see http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table * :option: works only with declared options, replace useage with simple ``. This change only handles a few files, more to come later. Change-Id: I7c7335e514581622dd562ee355f62d6ae1beaa18
1.1 KiB
1.1 KiB
Manage shares
A share is provided by file storage. You can give access to a share
to instances. To create and manage shares, use manila
client commands.
Migrate a share
As an administrator, you can migrate a share with its data from one location to another in a manner that is transparent to users and workloads.
Possible use cases for data migration include:
- Bring down a physical storage device for maintenance without disrupting workloads.
- Modify the properties of a share.
- Free up space in a thinly-provisioned back end.
Migrate a share with the manila migrate command, as shown in the following
example:
$ manila migrate shareID destinationHost --force-host-copy True|FalseIn this example, --force-host-copy True forces the
generic host-based migration mechanism and bypasses any driver
optimizations. destinationHost is in this format
host#pool which includes destination host and pool.
Note
If the user is not an administrator, the migration fails.