<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Nov 27, 2016 at 4:00 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Sun, Nov 27, 2016 at 12:54 PM, Fabrice Bacchella<br>
<<a href="mailto:fabrice.bacchella@orange.fr">fabrice.bacchella@orange.fr</a>> wrote:<br>
> Looks like close to my own try :<br>
><br>
> <a href="https://github.com/fbacchella/ovirtcmd" rel="noreferrer" target="_blank">https://github.com/fbacchella/<wbr>ovirtcmd</a><br>
<br>
</span>Looks cool.<br>
<br>
But I think what we need is something like targetcli for ovirt.<br>
<a href="http://linux-iscsi.org/wiki/Targetcli#Display_the_object_tree" rel="noreferrer" target="_blank">http://linux-iscsi.org/wiki/<wbr>Targetcli#Display_the_object_<wbr>tree</a><br>
<br>
With such tool we can see the ovirt setup as a file system tree:<br>
<br>
/ovirt/vms/vm-id<br>
/ovirt/storage/domain-id<br>
...<br>
<br>
And be able to query and operate on the entities.<br></blockquote><div><br></div><div>I believe it is built on top of <a href="https://github.com/Datera/configshell">https://github.com/Datera/configshell</a> (or its fork - <a href="https://github.com/open-iscsi/configshell-fb">https://github.com/open-iscsi/configshell-fb</a>)</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Another crazy direction I discussed with Roy, is a fuse files system mapping<br>
ovirt setup to a file system - imagine:<br>
<br>
$ mount -t ovirtfs /ovirt<br>
<br>
$ ls /ovirt/vms<br>
vm-id-1<br>
vm-id-2<br>
...<br>
<br>
$ cat /ovirt/vms/vm-ids/running<br>
1<br>
<br>
$ echo 0 > /ovirt/vms/vm-id/running<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
><br>
><br>
>> Le 26 nov. 2016 à 22:10, Chris Cowley <<a href="mailto:chris@chriscowley.me.uk">chris@chriscowley.me.uk</a>> a écrit :<br>
>><br>
>> Hi all<br>
>><br>
>> I started hacking together something last night to use as a CLI to<br>
>> manage my oVirt clusters.<br>
>><br>
>> <a href="https://gogs.chriscowley.me.uk/chriscowley/ovirtmanage" rel="noreferrer" target="_blank">https://gogs.chriscowley.me.<wbr>uk/chriscowley/ovirtmanage</a><br>
>><br>
>> Currently it can create/delete a VM, list the VMS, and I started a<br>
>> function to show the details, but all that does for now is return the ID.<br>
>><br>
>> The plan is for it to evolve with my own needs, but I am open to<br>
>> ideas/PRs from the community.<br>
>><br>
>> Disclaimer #1: I am a SysAdmin, not a developer. If you a proper<br>
>> developer, what you see may cause you physical pain.<br>
>><br>
>> Disclaimer #2: My Gogs repo is behind my ADSL in rural France, be<br>
>> patient and I withold the right to not respect any sort of SLA :-)<br>
>><br>
>><br>
>> --<br>
>> Regards<br>
>><br>
>> Chris Cowley<br>
>> <a href="http://about.me/chriscowley" rel="noreferrer" target="_blank">http://about.me/chriscowley</a><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
>> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
><br>
> ______________________________<wbr>_________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>