Migrate volumes to a different volume store (local or san) or to enabled servers
/api/v1/vol/migrate?app=application&name=app-or-volume&vdc=controller-name
Name of the volume to migrate.
Name of the target virtual data center.
asynchronous
GET
Migrate an application volume MYAPP:data to a local store:
GET http://aux/api/v1/vol/migrate?name=MYAPP:data&store=local&vdc=mygrid
Migrate all volumes for application MYAPP to a san:
GET http://aux/api/v1/vol/migrate?name=MYAPP&store=san&vdc=mygrid
Migrate all volumes off disabled server(s), three at a time:
GET http://aux/api/v1/vol/migrate?&all&n=3&vdc=mygrid
<job>b88969ea-9264-40b2-ba08-29b7ecbcc150</job>
{
"job" : "b88969ea-9264-40b2-ba08-29b7ecbcc150"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
Missing required arguments (name). - Argument name=… missing in the request.
Volume 'MYAPP:data' does not exist. - Invalid volume specified in the request.
Failed to migrate volume 'MYAPP:data'. - Volume specified in the request is in-use.
Report on the state of ongoing volume migrations between two different grids
/api/v1/vol/migrate_status?&vdc=
controller-name
Name of the target virtual data center
asynchronous
GET
Check the progress of volume migrations on grid mygrid:
GET http://aux/api/v1/vol/migrate_status?&vdc=mygrid
<job>be805915-76b2-48c8-b8a0-b881cca66da6</job>
{
"job" : "be805915-76b2-48c8-b8a0-b881cca66da6"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
Missing required arguments (app). - Argument app=app missing in the request.
Missing required arguments (vol). - Argument vol=vol missing in the request.
Missing required arguments (volnew). - Argument volnew=new_vol missing in the request.
Note: To get the status of job, issue a /api/v1/job/info? request with the job_id returned above as the argument. For more information about how to obtain the job status, refer to the job object.
Verify the health of the filesystem on a volume
/api/v1/vol/fscheck?app=application&vol=volume&vdc=controller-name
Name of the application
Name of the volume
Name of the target virtual data center
asynchronous
GET
Verify the health of test:vol1 with fs=ext3.
GET http://192.168.123.200>/api/v1/vol/fscheck?app=test&vol=vol1&vdc=mygrid
<job>be805915-76b2-48c8-b8a0-b881cca66da6</job>
{
"job" : "be805915-76b2-48c8-b8a0-b881cca66da6"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
Missing required arguments (app). - Argument app=app missing in the request.
Missing required arguments (vol). - Argument vol=vol missing in the request.
Note: To get the status of job, issue a /api/v1/job/info? request with the job_id returned above as the argument. For more information about how to obtain the job status, refer to the job object.
Verify and repair the filesystem on a volume
/api/v1/vol/fsrepair?app=application&vol=volume&vdc=controller-name
Name of the application
Name of the volume
Name of the target virtual data center
asynchronous
GET
Verify and repair test:vol1.
GET http://192.168.123.200/api/v1/vol/fsrepair?app=test&vol=vol1&vdc=mygrid
<job>be805915-76b2-48c8-b8a0-b881cca66da6</job>
{
"job" : "be805915-76b2-48c8-b8a0-b881cca66da6"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
Missing required arguments (app). - Argument app=app missing in the request.
Missing required arguments (vol). - Argument vol=vol missing in the request.
Note: To get the status of job, issue a /api/v1/job/info? request with the job_id returned above as the argument. For more information about how to obtain the job status, refer to the job object.
Initiate background check for volumes that need repair
/api/v1/vol/check?vdc=controller-name
Name of the target virtual data center
asynchronous
GET
Initiate background volume check.
GET http://192.168.123.200/api/v1/vol/check?vdc=mygrid
<message>A background check for volumes that need repair has been initiated and may take a few minutes to complete. Execute 'vol repair --status' to retrieve the current state of the volumes that are being repaired.</message>
{
"message" : "A background check for volumes that need repair has been initiated and may take \na few minutes to complete. Execute 'vol repair --status' to retrieve the \ncurrent state of the volumes that are being repaired.\n"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
A background check for volumes that need repair is already in progress.
Repair degraded volume
/api/v1/vol/repair?app=application&vol=volume&vdc=controller-name
Name of the application
Name of the volume
Name of the target virtual data center
asynchronous
GET
Repair test:vol1.
GET http://192.168.123.200/api/v1/vol/repair?app=test&vol=vol1&vdc=mygrid
Repair all volumes
GET http://192.168.123.200/api/v1/vol/repair?&all&vdc=mygrid
<job>be805915-76b2-48c8-b8a0-b881cca66da6</job>
{
"job" : "be805915-76b2-48c8-b8a0-b881cca66da6"
}
Entity vdc mygrid not found - A VDC name was specified that is not configured in the WS_API application.
Note: The volume repairs start immediately if there are available servers to execute the repair, otherwise the volume is queued for repair and will start once there are available servers. To get the status of job, issue a /api/v1/job/info? request with the job_id returned above as the argument. For more information about how to obtain the job status, refer to the job object.
|
Copyright © 2012 CA.
All rights reserved.
|
|