Feature #51
Enable customers to customise and upgrade disk layout
| Status: | New | Start: | 2010-12-30 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
The standard disk layout of a BitFolk VPS has changed several times based on the demands of the various operating system installers and vendor utilities. Having so many different styles of disk layout in service makes providing robust self-service install features quite challenging due to all the corner cases. It would be useful to support only one standard disk layout and provide a means for customers to transition to that layout at the point they wish to perform a reinstall, if necessary.
Whilst the majority of customers are content to accept the most simple disk layout, some do require multiple disk/block devices. Since the above work requires developing code to manipulate the disks exported to a customer's VPS anyway, it makes sense to expose some of this to the Xen Shell so that customers can optionally define extra disks.
History
Updated by admin over 14 years ago
I now have a development version of xen-shell which allows customers to:
- Add extra disk devices
- Delete disk devices
- Reset disk layout to the current standard layout
The customer's current disk layout is parsed and checked against the current standard. If it's found to be non-standard then the xen-shell's "install" feature is not available.
Almost all customers will currently have a non-standard disk layout, but this only matters when they come to reinstall. By this means they will be able to standardise their disk layout themselves.
I now need to:
- go through the installers that have already been made available and remove any incorrect assumptions about disk layout
- document the new xen-shell disk features and how they interact with the install feature
- document any peculiarites of install
Updated by admin over 14 years ago
This has been deployed now. It still needs documenting, along with the rest of Xen Shell..