vojtech - how about adding a very simple "samples-portals"
with it to
the repo?
I believe that Jenny is already working on a ovirt.js-based portal?
@Jenny: sounds like your work may be a good fit for our "Sample User
Portals" repository (more details in [1])?
[1]
http://www.ovirt.org/Sample_user_portals
> ----- Original Message -----
> From: "Itamar Heim" <iheim(a)redhat.com>
> Sent: Wednesday, November 12, 2014 5:03:37 PM
>
> On 11/06/2014 02:59 PM, Vojtech Szocs wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Itamar Heim" <iheim(a)redhat.com>
> >> To: "Nikita Kodkani" <nikita.kodkani(a)gmail.com>
> >> Cc: "users" <Users(a)ovirt.org>, "Vojtech Szocs"
<vszocs(a)redhat.com>
> >> Sent: Wednesday, November 5, 2014 12:37:21 AM
> >> Subject: Re: Fwd: [ovirt-users] Integration of ovirt-engine GUI with the
> >> CLI
> >>
> >> On 11/04/2014 01:54 PM, Nikita Kodkani wrote:
> >>> Hi,
> >>>
> >>> To add further...
> >>> I read it somewhere on google, that to execute the shell commands in
the
> >>> JavaScript we have to use node.js at the backend.
> >>>
> >>> We don't want to spend time on learning the technology in this time
> >>> frame.
> >>>
> >>> -Does ovirt-engine provide API's for executing the shell commands?
> >>
> >> its the other way around - the cli/shell commands are using the engine
> >> python-sdk, which uses the engine REST API.
> >>
> >> if your solution is html/javascript based, i think using ovirt.js (which
> >> wraps calling to the engine rest api 'nicely', vs. you doing it
yourself
> >> from your code) is the way to go.
> >
> > Exactly, the main use case for oVirtJS is to allow working with Engine
> > from within a JavaScript environment. HTML/JS web application is the
> > primary use case, we also plan to support "server-side JS code running
> > on Node.js" as another use case, so that people can potentially write
> > custom server-side JS to work with Engine.
>
vojtech - how about adding a very simple "samples-portals"
with it to
the repo?
>
> >
> >>
> >>
http://lists.ovirt.org/pipermail/users/2014-June/025198.html
> >>
http://www.ovirt.org/Features/Design/Using_REST_API_In_Web_UI
> >>
http://lists.ovirt.org/pipermail/devel/2014-August/008502.html
> >>
http://lists.ovirt.org/pipermail/devel/attachments/20140819/a35caa44/atta...
> >>
> >>
> >>>
> >>>
> >>> Thanks,
> >>> Nikita
> >>>
> >>> Nikita Kodkani
> >>>
> >>>
> >>> On Tue, Nov 4, 2014 at 4:20 PM, Itamar Heim <iheim(a)redhat.com
> >>> <mailto:iheim@redhat.com>> wrote:
> >>>
> >>> On 11/04/2014 11:47 AM, Nikita Kodkani wrote:
> >>>
> >>> It is designed in javascript/HTML. We had initially designed
> >>> some
> >>> feature using CLI. But now we just want to execute command
when
> >>> we hit
> >>> the button/tab.
> >>>
> >>>
> >>> vojtech - sounds like ovirt.js could be the best fit here?
> >>>
> >>> -Nikita
> >>>
> >>> i
> >>>
> >>>
> >>> On Tue, Nov 4, 2014 at 4:09 PM, Itamar Heim
<iheim(a)redhat.com
> >>> <mailto:iheim@redhat.com>
> >>> <mailto:iheim@redhat.com
<mailto:iheim@redhat.com>>> wrote:
> >>>
> >>> On 11/04/2014 06:30 AM, Nikita Kodkani wrote:
> >>>
> >>> Hi,
> >>>
> >>> I have the CLI designed for the RHEV-M. I have also
> >>> designed
> >>> some GUI in
> >>> ovirt-engine.
> >>> Now I am stuckup with the integration. Could you
> >>> suggest how to
> >>> connect
> >>> the ovirt-engine GUI with the backend CLI commands?
> >>>
> >>>
> >>> which language is your gui?
> >>> why use the CLI instead of the python or java SDKs
> >>> (or ruby or javascript ones)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>