8:23 a.m.
----- Original Message -----
From: "Mike Burns" <mburns(a)redhat.com>
To: "Dan Yasny" <dyasny(a)redhat.com>
Cc: infra(a)ovirt.org
Sent: Monday, 20 August, 2012 3:19:29 PM
Subject: Re: vdsm hooks pages at ovirt.org
On Mon, 2012-08-20 at 07:03 -0400, Dan Yasny wrote:
> Hi all,
>
> I am working on a project to make the existing vdsm hooks more
> accessible and available.
>
> So in very short, for those who do not know, a vdsm hook is a
> script
> that can be placed on ovirt hosts, and which will do some custom
> actions, vdsm cannot do out of the box.
>
> We have quite a few already in the repositories at
>
http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=tree;f=vdsm_hooks;h=6f33db407...
> and the vdsm engineers are starting to turn these into proper RPMs
> and push them into fedora, and then EPEL repos, however, for these
> to be consumable, we also will need a description page for each
> hook, somewhere under ovirt.org/hooks or hooks.ovirt.org, where
> every hook can be downloaded, and have a description, version
> compatibility and a use case described.
>
> If you use gnome-shell, it would be something like
> extensions.gnome.org, but of course, not quite the same, as we tend
> to
> a different kind of user.
>
> I would like to find out what will be required to do this, as soon
> as
> possible
Cool stuff.
Creating ovirt.org/hooks is pretty easy, hooks.ovirt.org is slightly
more complex (but doable).
/hooks is good enough for me, as long as it's easy to find and manage
The big questions:
* Who is doing the original design and content seeding?
Myself, basing on the READMEs Shahar and other added to the hooks
* Who will own keeping things up to date going forward?
We'll need a maintainer of course, depending on the amount of load, initially that
will probably be me, but ultimately - someone dealing with hooks in vdsm devel, or someone
maintaining the rest of the website
It might make sense to initially put the content you want on a wiki
page, and then transition it to a static page long term.
I'd rather take it directly to a separate page - there's nothing more permanent
than the temporary
As for the backend yum repo, that is pretty easily accomplished. We
can
simply have a separate area in the releases for current vdsm hooks.
Can you elaborate please? Where will the actual RPMs be taken from?
I
would assume that we'll want to keep that relatively stable and only
update manually when new versions are released. We can also have
something like an "unstable" repo where nightly builds of the plugins
are uploaded.
That can stay with the fedora based vdsm repos, we want the real consumables here IMO
Mike
>
> Thanks,
> Dan Yasny
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
--
Regards,
Dan Yasny
Red Hat Israel
+972 9769 2280