please note setLegality has been deprecated since 4.1
On Wed, Apr 3, 2019 at 1:45 PM wrote:
>
> Thanks Liran, it worked perfectly.
>
> Regards.
>
> El 2019-04-03 11:33, Liran Rotenberg escribió:
> > I think the similar way to do it as you used to is:
> > $ vdsm-client Volume setLegality
you can put any UUID for the job, you can check it using the
generation with `Volume getInfo`
On Wed, Apr 3, 2019 at 1:06 PM wrote:
>
> Hi Benny,
>
> Thanks for the help.
>
> Could you please tell me what job_uuid and vol_gen should be replaced
> by? Should I just put any UUID for the job?
>
>
Thanks Liran, it worked perfectly.
Regards.
El 2019-04-03 11:33, Liran Rotenberg escribió:
I think the similar way to do it as you used to is:
$ vdsm-client Volume setLegality storagedomainID=sdUUID
storagepoolID=spUUID imageID=imgUUID legality=LEGAL volumeID=volUUID
Where the values you set
I think the similar way to do it as you used to is:
$ vdsm-client Volume setLegality storagedomainID=sdUUID
storagepoolID=spUUID imageID=imgUUID legality=LEGAL volumeID=volUUID
Where the values you set should be inside quotes for example 'LEGAL'.
On Wed, Apr 3, 2019 at 1:08 PM wrote:
>
> Hi
Hi Benny,
Thanks for the help.
Could you please tell me what job_uuid and vol_gen should be replaced
by? Should I just put any UUID for the job?
Thanks.
El 2019-04-03 09:52, Benny Zlotnik escribió:
it should be something like this:
$ cat update.json
{
"job_id":"",
it should be something like this:
$ cat update.json
{
"job_id":"",
"vol_info": {
"sd_id": "",
"img_id": "",
"vol_id": "",
"generation": ""
},
"legality": "LEGAL"
}
}
$ vdsm-client SDM update_volume -f update.json
On
6 matches
Mail list logo
