[ovirt-users] Guest VM Console Creation/Access using REST API and noVNC

Antoni Segura Puimedon asegurap at redhat.com
Wed Jul 16 09:51:18 UTC 2014



----- Original Message -----
> From: "Shanil S" <xielesshanil at gmail.com>
> To: "Sven Kieske" <S.Kieske at mittwald.de>
> Cc: users at ovirt.org, danken at redhat.com, asegurap at redhat.com
> Sent: Wednesday, July 16, 2014 11:30:32 AM
> Subject: Re: Guest VM Console Creation/Access using REST API and noVNC
> 
> Hi Sven,
> 
> Thanks for your reply..
> 
> There is no network errors found in the ovirt and we are able to access the
> console from the ovirt panel,the only problem is we are not abel to access
> from the other host via API….as we don't want to use the Ovirt panel for
> the end users…so we use our own portal and open the console with the help
> of API function call….so right now we can access the console from the ovirt
> panel but can not from our portal.
> 
> We will get the ticket details like host,port and password from the ticket
> api funcion call but didn't get the "path" value. Will it get it from the
> ticket details ? i couldn't find out any from the ticket details.
> 
> --
> Regards
> Shanil
> 
> 
> On Wed, Jul 16, 2014 at 12:34 PM, Sven Kieske <S.Kieske at mittwald.de> wrote:
> 
> > Okay, I can give you a short design overview
> > how you can make this work:
> >
> > a) client browser -> gets novnc from ovirt-engine
> > or any other host where you host it.
> > b) client browser(novnc) gets the ticket and path via rest api
> > c) client browser(novnc) -> connects to websocket-proxy
> > with the rest-api ticket and "path"
> > (destination host where the vm is hosted)
> >
> > please note, that websocket-proxy must be reachable from client browser
> >
> > d) websocket-proxy needs a connection to the cluster and host where
> > the vm runs, keep in mind you need to configure your display network
> > in ovirt accordingly.
> >
> > I guess you just have an error in your network setup.
> >
> > So you need to expose at least the websocket-proxy to the client browser
> > and this proxy must be able to reach the vm host.

Could it be that there is some iptables rule preventing the communication?

> > furthermore for passing the ticket you need a host example.com
> > which can connect to engine and can connect to the client browser, e.g.
> > the websocket proxy or any other machine you want to use for that.
> >
> > you could also expose the engine itself, but it depends on your client
> > browser if you want to do this (security)!
> >
> > HTH
> >
> >
> > --
> > Mit freundlichen Grüßen / Regards
> >
> > Sven Kieske
> >
> > Systemadministrator
> > Mittwald CM Service GmbH & Co. KG
> > Königsberger Straße 6
> > 32339 Espelkamp
> > T: +49-5772-293-100
> > F: +49-5772-293-333
> > https://www.mittwald.de
> > Geschäftsführer: Robert Meyer
> > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
> 



More information about the Users mailing list