Re: [ovirt-users] Query on VM Clone
Den 29 mars 2018 14:15 skrev Alexander Wels :On Thursday, March 29, 2018 7:59:36 AM EDT Ondra Machacek wrote:> On 03/29/2018 01:02 PM, Karli Sjöberg wrote:> > On Thu, 2018-03-29 at 11:21 +0200, Ondra Machacek wrote:> >> On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:> >>> Hi Team,> >>> > >>> 1) I perform the VM clone using the following API> >>> > >>> api/vms/{vmId}/clone> >>> > >>> 2) The above API is returning the job id> >>> 3) Using the job Id, we continuously query the oVirt to get the> >>> status> >>> of the clone operation.> >>> /api/jobs/${vmCloneJobId}> >>> > >>> We are able to successfully get the status of the clone> >>> > >>> operation.> >>> > >>> But the problem is, we are not able to identify the newly created> >>> VM> >>> (created using clone).> >>> > >>> AFAIK, The only way to get the newly created VM is to get all the> >>> VM> >>> list from oVirt. Is there an easy way to identify the newly created> >>> VM> >>> using the jobId?> >> > >> In order to run the clone operation you must pas the VM name, so you> >> know the name, so later to fetch the VM you can just run:> >> > >> api/vms?search=name=thenameofclonnedvm> > > > Hijacking this a little, because I got curious about something:)> > > > Is it possible to do regex searches? Because I remember working on> > something different, the searches could potentially end up with> > multiple matched objects, like "thenameofclonnedvm",> > "thenameofclonnedvm-berta", "thenameofclonnedvm3" and so on. So I was> > always forced to treat the result as a potential array, loop the> > objects (this was with Python) and test for an exact match, even if it> > was just one object. So it would be nicer if you could go like:> > > > api/vms?search=name='^thenameofclonnedvm$'> > > > And be sure to have an exact match every time. Is that possible?> > You can read more about search engine here:> > > https://www.ovirt.org/documentation/admin-guide/appe-Using_Search_Bookmarks_> and_Tags/> > So if you have for example following VMs in system:> > vm> vm1> vm2> vm3> > And you do search like:> >api/vms?search=name=vm> > It will return only single Vm called 'vm', but it always return a> collection, but with just single item.> > And you do search like:> > api/vms?search=name=vm*> > It will return all VMs starting on 'vm' string. So it's collection of> vm, vm1, vm2 and vm3.> > So by default it search for exact string, but you may use wildcards to> improve the search.> You can also 'and' and 'or' different parameters, for instanceapi/vms?search=name%3DVM1+or+name%3DVM2which will return VM1 and VM2 if they exist. Note that you will need to URL encode your search string to replace all the '=' with %3D and space with +, etc. The _only_ = that shouldn't be encoded is the = after search.For an easy way to find what is available to search on for a particular entity, if you go into the webadmin in the search bar you can start typing and it will auto complete the different available options. AFAIC those match exactly to the search in the REST api.OK, cool, so that's changed since when I did it (admittedly a while ago now), good to know! Thanks for the explanation!/K> > TIA> > > > /K> > > >> Is this approach OK for you?> >> > >>> Thanks,> >>> Hari> >>> > >>> DISCLAIMER> >>> > >>> The information in this e-mail is confidential and may be subject> >>> to> >>> legal privilege. It is intended solely for the addressee. Access to> >>> this> >>> e-mail by anyone else is unauthorized. If you have received this> >>> communication in error, please address with the subject heading> >>> "Received in error," send to i...@msystechnologies.com> >>> , then delete the e-mail and> >>> destroy> >>> any copies of it. If you are not the intended recipient, any> >>> disclosure,> >>> copying, distribution or any action taken or omitted to be taken> >>> in> >>> reliance on it, is prohibited and may be unlawful. The views,> >>> opinions,> >>> conclusions and other information expressed in this electronic mail> >>> and> >>> any attachments are not given or endorsed by the company unless> >>> otherwise indicated by an authorized representative independent of> >>> this> >>> message.> >>> > >>> MSys cannot guarantee that e-mail communications are secure or> >>> error-free, as information could be intercepted, corrupted,> >>> amended,> >>> lost, destroyed, arrive late or incomplete, or contain viruses,> >>> though> >>> all reasonable precautions have been taken to ensure no viruses> >>> are> >>> present in this e-mail. As our company cannot accept responsibility> >>> for> >>> any loss or damage arising from the use of this e-mail or> >>> attachments we> >>> recommend that you subject these to your virus checking procedures> >>> prior> >>> to use> >>> > >>> > >>> ___> >>> Users mailing list> >>> Users@ovirt.org> >>> http://lists.ovirt.org/mailman/listinfo/users> >> > >> ___> >> Users mailing list> >>
Re: [ovirt-users] Query on VM Clone
Thanks, Ondra. Appreciated.
On Thu, Mar 29, 2018 at 2:51 PM, Ondra Machacek wrote:
> On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:
>
>> Hi Team,
>>
>> 1) I perform the VM clone using the following API
>>
>> api/vms/{vmId}/clone
>>
>> 2) The above API is returning the job id
>> 3) Using the job Id, we continuously query the oVirt to get the status of
>> the clone operation.
>> /api/jobs/${vmCloneJobId}
>> We are able to successfully get the status of the clone operation.
>>
>> But the problem is, we are not able to identify the newly created VM
>> (created using clone).
>>
>> AFAIK, The only way to get the newly created VM is to get all the VM list
>> from oVirt. Is there an easy way to identify the newly created VM using the
>> jobId?
>>
>
> In order to run the clone operation you must pas the VM name, so you know
> the name, so later to fetch the VM you can just run:
>
> api/vms?search=name=thenameofclonnedvm
>
> Is this approach OK for you?
>
>
>> Thanks,
>> Hari
>>
>> DISCLAIMER
>>
>> The information in this e-mail is confidential and may be subject to
>> legal privilege. It is intended solely for the addressee. Access to this
>> e-mail by anyone else is unauthorized. If you have received this
>> communication in error, please address with the subject heading "Received
>> in error," send to i...@msystechnologies.com > m>, then delete the e-mail and destroy any copies of it. If you are not
>> the intended recipient, any disclosure, copying, distribution or any action
>> taken or omitted to be taken in reliance on it, is prohibited and may be
>> unlawful. The views, opinions, conclusions and other information expressed
>> in this electronic mail and any attachments are not given or endorsed by
>> the company unless otherwise indicated by an authorized representative
>> independent of this message.
>>
>> MSys cannot guarantee that e-mail communications are secure or
>> error-free, as information could be intercepted, corrupted, amended, lost,
>> destroyed, arrive late or incomplete, or contain viruses, though all
>> reasonable precautions have been taken to ensure no viruses are present in
>> this e-mail. As our company cannot accept responsibility for any loss or
>> damage arising from the use of this e-mail or attachments we recommend that
>> you subject these to your virus checking procedures prior to use
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
--
DISCLAIMER
The information in this e-mail is confidential and may be subject to legal
privilege. It is intended solely for the addressee. Access to this e-mail
by anyone else is unauthorized. If you have received this communication in
error, please address with the subject heading "Received in error," send to
i...@msystechnologies.com, then delete the e-mail and destroy any copies of
it. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful. The views, opinions, conclusions and
other information expressed in this electronic mail and any attachments are
not given or endorsed by the company unless otherwise indicated by an
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free,
as information could be intercepted, corrupted, amended, lost, destroyed,
arrive late or incomplete, or contain viruses, though all reasonable
precautions have been taken to ensure no viruses are present in this e-mail.
As our company cannot accept responsibility for any loss or damage arising
from the use of this e-mail or attachments we recommend that you subject
these to your virus checking procedures prior to use
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Query on VM Clone
On Thursday, March 29, 2018 7:59:36 AM EDT Ondra Machacek wrote:
> On 03/29/2018 01:02 PM, Karli Sjöberg wrote:
> > On Thu, 2018-03-29 at 11:21 +0200, Ondra Machacek wrote:
> >> On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:
> >>> Hi Team,
> >>>
> >>> 1) I perform the VM clone using the following API
> >>>
> >>> api/vms/{vmId}/clone
> >>>
> >>> 2) The above API is returning the job id
> >>> 3) Using the job Id, we continuously query the oVirt to get the
> >>> status
> >>> of the clone operation.
> >>> /api/jobs/${vmCloneJobId}
> >>>
> >>> We are able to successfully get the status of the clone
> >>>
> >>> operation.
> >>>
> >>> But the problem is, we are not able to identify the newly created
> >>> VM
> >>> (created using clone).
> >>>
> >>> AFAIK, The only way to get the newly created VM is to get all the
> >>> VM
> >>> list from oVirt. Is there an easy way to identify the newly created
> >>> VM
> >>> using the jobId?
> >>
> >> In order to run the clone operation you must pas the VM name, so you
> >> know the name, so later to fetch the VM you can just run:
> >>
> >> api/vms?search=name=thenameofclonnedvm
> >
> > Hijacking this a little, because I got curious about something:)
> >
> > Is it possible to do regex searches? Because I remember working on
> > something different, the searches could potentially end up with
> > multiple matched objects, like "thenameofclonnedvm",
> > "thenameofclonnedvm-berta", "thenameofclonnedvm3" and so on. So I was
> > always forced to treat the result as a potential array, loop the
> > objects (this was with Python) and test for an exact match, even if it
> > was just one object. So it would be nicer if you could go like:
> >
> > api/vms?search=name='^thenameofclonnedvm$'
> >
> > And be sure to have an exact match every time. Is that possible?
>
> You can read more about search engine here:
>
>
> https://www.ovirt.org/documentation/admin-guide/appe-Using_Search_Bookmarks_
> and_Tags/
>
> So if you have for example following VMs in system:
>
> vm
> vm1
> vm2
> vm3
>
> And you do search like:
>
>api/vms?search=name=vm
>
> It will return only single Vm called 'vm', but it always return a
> collection, but with just single item.
>
> And you do search like:
>
> api/vms?search=name=vm*
>
> It will return all VMs starting on 'vm' string. So it's collection of
> vm, vm1, vm2 and vm3.
>
> So by default it search for exact string, but you may use wildcards to
> improve the search.
>
You can also 'and' and 'or' different parameters, for instance
api/vms?search=name%3DVM1+or+name%3DVM2
which will return VM1 and VM2 if they exist. Note that you will need to URL
encode your search string to replace all the '=' with %3D and space with +,
etc. The only = that shouldn't be encoded is the = after search.
For an easy way to find what is available to search on for a particular
entity, if you go into the webadmin in the search bar you can start typing and
it will auto complete the different available options. AFAIC those match
exactly to the search in the REST api.
> > TIA
> >
> > /K
> >
> >> Is this approach OK for you?
> >>
> >>> Thanks,
> >>> Hari
> >>>
> >>> DISCLAIMER
> >>>
> >>> The information in this e-mail is confidential and may be subject
> >>> to
> >>> legal privilege. It is intended solely for the addressee. Access to
> >>> this
> >>> e-mail by anyone else is unauthorized. If you have received this
> >>> communication in error, please address with the subject heading
> >>> "Received in error," send to i...@msystechnologies.com
> >>> , then delete the e-mail and
> >>> destroy
> >>> any copies of it. If you are not the intended recipient, any
> >>> disclosure,
> >>> copying, distribution or any action taken or omitted to be taken
> >>> in
> >>> reliance on it, is prohibited and may be unlawful. The views,
> >>> opinions,
> >>> conclusions and other information expressed in this electronic mail
> >>> and
> >>> any attachments are not given or endorsed by the company unless
> >>> otherwise indicated by an authorized representative independent of
> >>> this
> >>> message.
> >>>
> >>> MSys cannot guarantee that e-mail communications are secure or
> >>> error-free, as information could be intercepted, corrupted,
> >>> amended,
> >>> lost, destroyed, arrive late or incomplete, or contain viruses,
> >>> though
> >>> all reasonable precautions have been taken to ensure no viruses
> >>> are
> >>> present in this e-mail. As our company cannot accept responsibility
> >>> for
> >>> any loss or damage arising from the use of this e-mail or
> >>> attachments we
> >>> recommend that you subject these to your virus checking procedures
> >>> prior
> >>> to use
> >>>
> >>>
> >>> ___
> >>> Users mailing list
> >>> Users@ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >> ___
> >> Users mai
Re: [ovirt-users] Query on VM Clone
On 03/29/2018 01:02 PM, Karli Sjöberg wrote:
On Thu, 2018-03-29 at 11:21 +0200, Ondra Machacek wrote:
On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:
Hi Team,
1) I perform the VM clone using the following API
api/vms/{vmId}/clone
2) The above API is returning the job id
3) Using the job Id, we continuously query the oVirt to get the
status
of the clone operation.
/api/jobs/${vmCloneJobId}
We are able to successfully get the status of the clone
operation.
But the problem is, we are not able to identify the newly created
VM
(created using clone).
AFAIK, The only way to get the newly created VM is to get all the
VM
list from oVirt. Is there an easy way to identify the newly created
VM
using the jobId?
In order to run the clone operation you must pas the VM name, so you
know the name, so later to fetch the VM you can just run:
api/vms?search=name=thenameofclonnedvm
Hijacking this a little, because I got curious about something:)
Is it possible to do regex searches? Because I remember working on
something different, the searches could potentially end up with
multiple matched objects, like "thenameofclonnedvm",
"thenameofclonnedvm-berta", "thenameofclonnedvm3" and so on. So I was
always forced to treat the result as a potential array, loop the
objects (this was with Python) and test for an exact match, even if it
was just one object. So it would be nicer if you could go like:
api/vms?search=name='^thenameofclonnedvm$'
And be sure to have an exact match every time. Is that possible?
You can read more about search engine here:
https://www.ovirt.org/documentation/admin-guide/appe-Using_Search_Bookmarks_and_Tags/
So if you have for example following VMs in system:
vm
vm1
vm2
vm3
And you do search like:
api/vms?search=name=vm
It will return only single Vm called 'vm', but it always return a
collection, but with just single item.
And you do search like:
api/vms?search=name=vm*
It will return all VMs starting on 'vm' string. So it's collection of
vm, vm1, vm2 and vm3.
So by default it search for exact string, but you may use wildcards to
improve the search.
TIA
/K
Is this approach OK for you?
Thanks,
Hari
DISCLAIMER
The information in this e-mail is confidential and may be subject
to
legal privilege. It is intended solely for the addressee. Access to
this
e-mail by anyone else is unauthorized. If you have received this
communication in error, please address with the subject heading
"Received in error," send to i...@msystechnologies.com
, then delete the e-mail and
destroy
any copies of it. If you are not the intended recipient, any
disclosure,
copying, distribution or any action taken or omitted to be taken
in
reliance on it, is prohibited and may be unlawful. The views,
opinions,
conclusions and other information expressed in this electronic mail
and
any attachments are not given or endorsed by the company unless
otherwise indicated by an authorized representative independent of
this
message.
MSys cannot guarantee that e-mail communications are secure or
error-free, as information could be intercepted, corrupted,
amended,
lost, destroyed, arrive late or incomplete, or contain viruses,
though
all reasonable precautions have been taken to ensure no viruses
are
present in this e-mail. As our company cannot accept responsibility
for
any loss or damage arising from the use of this e-mail or
attachments we
recommend that you subject these to your virus checking procedures
prior
to use
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Query on VM Clone
On Thu, 2018-03-29 at 11:21 +0200, Ondra Machacek wrote:
> On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:
> > Hi Team,
> >
> > 1) I perform the VM clone using the following API
> >
> > api/vms/{vmId}/clone
> >
> > 2) The above API is returning the job id
> > 3) Using the job Id, we continuously query the oVirt to get the
> > status
> > of the clone operation.
> > /api/jobs/${vmCloneJobId}
> > We are able to successfully get the status of the clone
> > operation.
> >
> > But the problem is, we are not able to identify the newly created
> > VM
> > (created using clone).
> >
> > AFAIK, The only way to get the newly created VM is to get all the
> > VM
> > list from oVirt. Is there an easy way to identify the newly created
> > VM
> > using the jobId?
>
> In order to run the clone operation you must pas the VM name, so you
> know the name, so later to fetch the VM you can just run:
>
> api/vms?search=name=thenameofclonnedvm
Hijacking this a little, because I got curious about something:)
Is it possible to do regex searches? Because I remember working on
something different, the searches could potentially end up with
multiple matched objects, like "thenameofclonnedvm",
"thenameofclonnedvm-berta", "thenameofclonnedvm3" and so on. So I was
always forced to treat the result as a potential array, loop the
objects (this was with Python) and test for an exact match, even if it
was just one object. So it would be nicer if you could go like:
api/vms?search=name='^thenameofclonnedvm$'
And be sure to have an exact match every time. Is that possible?
TIA
/K
>
> Is this approach OK for you?
>
> >
> > Thanks,
> > Hari
> >
> > DISCLAIMER
> >
> > The information in this e-mail is confidential and may be subject
> > to
> > legal privilege. It is intended solely for the addressee. Access to
> > this
> > e-mail by anyone else is unauthorized. If you have received this
> > communication in error, please address with the subject heading
> > "Received in error," send to i...@msystechnologies.com
> > , then delete the e-mail and
> > destroy
> > any copies of it. If you are not the intended recipient, any
> > disclosure,
> > copying, distribution or any action taken or omitted to be taken
> > in
> > reliance on it, is prohibited and may be unlawful. The views,
> > opinions,
> > conclusions and other information expressed in this electronic mail
> > and
> > any attachments are not given or endorsed by the company unless
> > otherwise indicated by an authorized representative independent of
> > this
> > message.
> >
> > MSys cannot guarantee that e-mail communications are secure or
> > error-free, as information could be intercepted, corrupted,
> > amended,
> > lost, destroyed, arrive late or incomplete, or contain viruses,
> > though
> > all reasonable precautions have been taken to ensure no viruses
> > are
> > present in this e-mail. As our company cannot accept responsibility
> > for
> > any loss or damage arising from the use of this e-mail or
> > attachments we
> > recommend that you subject these to your virus checking procedures
> > prior
> > to use
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
signature.asc
Description: This is a digitally signed message part
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Query on VM Clone
On 03/29/2018 11:09 AM, Hari Prasanth Loganathan wrote:
Hi Team,
1) I perform the VM clone using the following API
api/vms/{vmId}/clone
2) The above API is returning the job id
3) Using the job Id, we continuously query the oVirt to get the status
of the clone operation.
/api/jobs/${vmCloneJobId}
We are able to successfully get the status of the clone operation.
But the problem is, we are not able to identify the newly created VM
(created using clone).
AFAIK, The only way to get the newly created VM is to get all the VM
list from oVirt. Is there an easy way to identify the newly created VM
using the jobId?
In order to run the clone operation you must pas the VM name, so you
know the name, so later to fetch the VM you can just run:
api/vms?search=name=thenameofclonnedvm
Is this approach OK for you?
Thanks,
Hari
DISCLAIMER
The information in this e-mail is confidential and may be subject to
legal privilege. It is intended solely for the addressee. Access to this
e-mail by anyone else is unauthorized. If you have received this
communication in error, please address with the subject heading
"Received in error," send to i...@msystechnologies.com
, then delete the e-mail and destroy
any copies of it. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. The views, opinions,
conclusions and other information expressed in this electronic mail and
any attachments are not given or endorsed by the company unless
otherwise indicated by an authorized representative independent of this
message.
MSys cannot guarantee that e-mail communications are secure or
error-free, as information could be intercepted, corrupted, amended,
lost, destroyed, arrive late or incomplete, or contain viruses, though
all reasonable precautions have been taken to ensure no viruses are
present in this e-mail. As our company cannot accept responsibility for
any loss or damage arising from the use of this e-mail or attachments we
recommend that you subject these to your virus checking procedures prior
to use
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
