vdsm hooks pages at ovirt.org

[Karsten 'quaid' Wade]

On 08/23/2012 06:52 AM, Andrew Cathrow wrote:
> 
> 
> ----- Original Message -----
>> From: "Dave Neary" <dneary at redhat.com>
>> 
>> Just to make it clear: the idea of VDSM hooks is that they're 
>> downloadable pieces of software (if I understand correctly,
>> they're usually shell or Python scripts), so in my mind a wiki
>> isn't really appropriate - you want users to be able to upload new
>> hooks, order search results based on ratings and/or download
>> statistics for hooks, and features like tagging, ratings, comments
>> on a hook and versioning are appropriate and useful.

... which sounds like a new web service. I can see that vision, just
figured the urgency meant we were going to take it in phases, e.g.:

1. Get up a webpage that explains each hook & links to it directly +
directions for setting up yum repo.
1.1 Do this quickly with WordPress, maybe get some design thoughts from
Garrett.
2. Based on what we learn in doing phase 1, we can figure out the
appropriate web service to grab, install, and run.
2.1 We definitely want to get UX and design help here.

What wasn't clear to me is if the hooks are specific to VDSM or generic
for oVirt. In other words, are we ordering up:

vdsm-hooks.ovirt.org => ovirt.org/VDSM-hooks

or

hooks.ovirt.org => ovirt.org/hooks

(We'll do the Apache config to make it whatever, but fundamentally we're
building a new tree at either /VDSM-hooks or /hooks as root, with a repo
tree underneath to start, and sporting an eventual web service.)

> The hooks are delivered as RPMs -they need to be in a yum repo (for
> fedora/EL) with web/wiki pages with help/docs/etc

OK, I can do the Apache work, create the directory tree, and order up
DNS as soon as $someone_who_knows confirms that the generic word 'hooks'
works, i.e. that we aren't tying up the incorrect namespace.

- Karsten
-- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org  .^\  http://community.redhat.com
@quaid (identi.ca/twitter/IRC)  \v'  gpg: AD0E0C41

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20120823/2155ca24/attachment.sig>