[ovirt-devel] Cockpit-oVirt plugin

[Doron Fediuck]

On Tue, Feb 23, 2016 at 5:46 PM, Fabian Deutsch <fdeutsch at redhat.com> wrote:

> On Tue, Feb 23, 2016 at 1:23 PM, Marek Libra <mlibra at redhat.com> wrote:
> > I'm pleased to announce initial version of new oVirt plugin for Cockpit,
> which is recently a proposed feature for oVirt 4.0.
> >
> > The oVirt Wiki Feature can be found at [3].
> >
> > Sources and README file can be found on the github [1].
> > Up-to-date issue list is at [2] (includes planed enhancements)
> >
> > Please refer the README file for install instructions, so far tested on
> Centos 7 (minimal).
> >
> > The plugin will be distributed as an rpm in the future and is meant as
> an optional add-on to oVirt.
> >
> > Main focus is on
> > - troubleshooting when accessibility/functionality of webadmin is limited
> > - easy-to-use tool for VM-centric host monitoring/administration
> > - potential integration point with oVirt on UI level
> > - easy to use, so for small setups the preferred choice with an option
> to "upgrade" to full oVirt later
> >
> > The plugin or its parts can be used as standalone same as embedded into
> other UIs, like drill-down from webadmin or ManageIQ for more details or
> fine-tuning.
> >
> > The plugin has dependency on VDSM.
> > Please note, since there was a VDSM patch needed, recent master is
> required (see README in the source).
> >
> > Dependency on oVirt's engine is optional - when accessible then
> additional plugin functionality is available.
> > Please note, the plugin is in early development phase showing basic
> concept.
>
> Hey Marek,
>
> this work looks pretty promising!
>
> Do you already have rpm build which we could include in our nightly
> oVirt Node Next builds?
>
> Greetnigs
> fabian
>

Indeed looks very nice.
Please remember it will need to be integrated with other oVirt parts in
cockpit as it depends in vdsm, and a designated tab
makes sense here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20160223/88c875f5/attachment.html>