New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage Swap Devices using Ginger #23
Comments
@harche interesting feature, but please, send a RFC (Request For Comments) to ginger mailing list ginger-dev-list@nongnu.org (CC also the old ML ginger-dev@yahoogroups.com due to delivery issues on nongnu lists). There you will get more feedback than here. |
Is it possible to update an existing swap device? And what tools are you planning to use to implement this feature? On 10/01/2015 07:13 AM, harche wrote:
|
|
It is ok to start it 'small' with the first release in my opinion. I suggest to forward the first post of this issue to ginger-dev-list@googlegroups.com to get comments from the rest of the community. Thanks |
This feature is implemented at current master branch. Thanks! |
This patch fixes the issue by adjusting the width of columns of the table which displays SAN Adapters Signed-off-by: Harshal Patil <harshalp@linux.vnet.ibm.com>
Using the
Ginger
we would like to list/add/remove the swap devices used by the host. Here is the example of swap devices attached to the hostcat /proc/swaps
Here is the proposal for
Ginger
to do swap management on the host -Collection: Swap devices
URI: /plugins/ginger/swaps
Methods:
GET: Retrieve a summarized list of all swap devices
POST: Create a swap device
device
orfile
. Linux allows you to use either theblock device
or aregular file
as a swap device. We would like to have support for both types.file
. We need to know the size of the regular file that needs to be created which will act as a swap device.Resource: Swap Device
URI: /plugins/ginger/swaps/:device_name
Methods:
GET: Retrieve the full description of a Swap Device
partition
for the block device andfile
for the regular file.DELETE: Remove the Swap Device
The text was updated successfully, but these errors were encountered: