On 06/06/2017 05:17 PM, Peter wrote:
> On 06/06/2017 08:11 AM, Peter Krempa wrote:
>> On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
>>> On 05/26/2017 02:11 AM, Martin Kletzander wrote:
On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
>>
>> [...]
>>
If we standardize
On 07.06.2017 11:02, Daniel P. Berrange wrote:
> On Wed, Jun 07, 2017 at 10:47:25AM +0200, Stef Walter wrote:
>> On 07.06.2017 07:49, Martin Pitt wrote:
>>> Hello Richard,
>>>
>>> Richard W.M. Jones [2017-05-31 18:00 +0100]:
I agree with others that as things stand you will need a REST or
Stef Walter [2017-06-07 10:47 +0200]:
> On 07.06.2017 07:49, Martin Pitt wrote:
> > C/GI interfaces also don't map well to D-Bus, i. e. it's not practical to
> > autogenerate a D-Bus interface for a given GI API. This still works for the
> > most simple methods that only accept primitive data
Hello Richard,
Richard W.M. Jones [2017-05-31 18:00 +0100]:
> I agree with others that as things stand you will need a REST or DBus
> or similar API added to libvirt.
>
> However have you considered using gobject-introspection to generate
> new "Payload" types automatically?
This doesn't
On Wed, Jun 07, 2017 at 10:47:25AM +0200, Stef Walter wrote:
> On 07.06.2017 07:49, Martin Pitt wrote:
> > Hello Richard,
> >
> > Richard W.M. Jones [2017-05-31 18:00 +0100]:
> >> I agree with others that as things stand you will need a REST or DBus
> >> or similar API added to libvirt.
> >>
> >>
On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
> Hi Everyone,
>
> We are working towards building on the virtualization management
> functionality in cockpit (http://cockpit-project.org/) and wanted to get
> some feedback on the best way to integrate with libvirt.
Another thing to
On 07.06.2017 07:49, Martin Pitt wrote:
> Hello Richard,
>
> Richard W.M. Jones [2017-05-31 18:00 +0100]:
>> I agree with others that as things stand you will need a REST or DBus
>> or similar API added to libvirt.
>>
>> However have you considered using gobject-introspection to generate
>> new
On Tue, Jun 06, 2017 at 01:25:08PM -0400, Stef Walter wrote:
> On 06.06.2017 12:13, Daniel P. Berrange wrote:
> > On Tue, Jun 06, 2017 at 06:07:21PM +0200, Stef Walter wrote:
> >> So to summarize what I'm hearing here:
> >>
> >> * There is no libvirt remotable API today.
> >
> > Libvirt drivers
On 06.06.2017 12:13, Daniel P. Berrange wrote:
> On Tue, Jun 06, 2017 at 06:07:21PM +0200, Stef Walter wrote:
>> On 06.06.2017 17:17, Daniel P. Berrange wrote:
>>> On Tue, Jun 06, 2017 at 05:11:55PM +0200, Peter Krempa wrote:
On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
> On
On Tue, Jun 06, 2017 at 06:07:21PM +0200, Stef Walter wrote:
> On 06.06.2017 17:17, Daniel P. Berrange wrote:
> > On Tue, Jun 06, 2017 at 05:11:55PM +0200, Peter Krempa wrote:
> >> On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
> >>> On 05/26/2017 02:11 AM, Martin Kletzander wrote:
> On
On 06.06.2017 17:17, Daniel P. Berrange wrote:
> On Tue, Jun 06, 2017 at 05:11:55PM +0200, Peter Krempa wrote:
>> On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
>>> On 05/26/2017 02:11 AM, Martin Kletzander wrote:
On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
>>
>> [...]
On Tue, Jun 06, 2017 at 05:11:55PM +0200, Peter Krempa wrote:
> On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
> > On 05/26/2017 02:11 AM, Martin Kletzander wrote:
> > > On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
>
> [...]
>
> > > If we standardize even the smallest part
On 06/06/2017 08:11 AM, Peter Krempa wrote:
On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
On 05/26/2017 02:11 AM, Martin Kletzander wrote:
On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
[...]
If we standardize even the smallest part of the RPC, then it might screw
us
On Tue, Jun 06, 2017 at 07:45:10 -0700, Peter wrote:
> On 05/26/2017 02:11 AM, Martin Kletzander wrote:
> > On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
[...]
> > If we standardize even the smallest part of the RPC, then it might screw
> > us immediately. We are keeping it
On 05/26/2017 02:11 AM, Martin Kletzander wrote:
On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
Hi Everyone,
We are working towards building on the virtualization management
functionality in cockpit (http://cockpit-project.org/) and wanted to get
some feedback on the best way to
On 05/31/2017 01:00 PM, Richard W.M. Jones wrote:
> On Wed, May 31, 2017 at 09:22:41AM -0700, Peter wrote:
>> The javascript is always run in the users browser. The dbus calls or
>> system commands are sent by the javascript via a websocket to
>> cockpit-ws. It then forwards those messages on to
On Wed, May 31, 2017 at 09:22:41AM -0700, Peter wrote:
> The javascript is always run in the users browser. The dbus calls or
> system commands are sent by the javascript via a websocket to
> cockpit-ws. It then forwards those messages on to the correct
> cockpit-bridge. Based on the payload the
On 05/31/2017 08:52 AM, Richard W.M. Jones wrote:
On Wed, May 31, 2017 at 04:02:42PM +0100, Daniel P. Berrange wrote:
On Wed, May 31, 2017 at 03:59:10PM +0100, Richard W.M. Jones wrote:
On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
The majority of cockpit is implemented in
On Wed, May 31, 2017 at 04:02:42PM +0100, Daniel P. Berrange wrote:
> On Wed, May 31, 2017 at 03:59:10PM +0100, Richard W.M. Jones wrote:
> > On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
> > > The majority of cockpit is implemented in
> > > javascript.
> >
> > How about using the
On Wed, May 31, 2017 at 03:59:10PM +0100, Richard W.M. Jones wrote:
> On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
> > The majority of cockpit is implemented in
> > javascript.
>
> How about using the gobject libvirt bindings?
>
> https://libvirt.org/git/?p=libvirt-glib.git;a=summary
On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
> The majority of cockpit is implemented in
> javascript.
How about using the gobject libvirt bindings?
https://libvirt.org/git/?p=libvirt-glib.git;a=summary
They should be usable from Javascript directly, as in the .js example
here:
On Thu, May 25, 2017 at 10:16:26AM -0700, Peter Volpe wrote:
Hi Everyone,
We are working towards building on the virtualization management
functionality in cockpit (http://cockpit-project.org/) and wanted to get
some feedback on the best way to integrate with libvirt.
As a quick overview,
On Thu, May 25, 2017 at 10:26:47AM -0700, Peter wrote:
> As far as I know libvirt doesn't currently have a remoteable API. It does
> have a daemon that communicates with clients via a XDR RPC.
> (https://libvirt.org/internals/rpc.html) However from what I'm hearing the
> RPC is considered an
Hi Everyone,
We are working towards building on the virtualization management
functionality in cockpit (http://cockpit-project.org/) and wanted to get
some feedback on the best way to integrate with libvirt.
As a quick overview, cockpit aims to talk to existing remotable system
APIs.
Hi Everyone,
We are working towards building on the virtualization management
functionality in cockpit (http://cockpit-project.org/) and wanted to get
some feedback on the best way to integrate with libvirt.
As a quick overview, cockpit aims to talk to existing remotable system
APIs.
25 matches
Mail list logo
