Hi Brian,
"It would be fantastic if you could rework this topic into a lab. You do not need to
be present. Just put together a one or two page 'worksheet' that walks Lab
attendees through oVirt. If you like, you could also sign up for an 'office
hours' timeslot, where you could discuss oVirt with Lab attendees and assist them with
the worksheet."
So it sounds like it can be any length. This is something attendees will come into the lab
and try on their own time.
Greg
----- Original Message -----
From: "Brian Proffitt" <bproffit(a)redhat.com>
To: "Greg Sheremeta" <gshereme(a)redhat.com>
Cc: "users" <users(a)ovirt.org>
Sent: Monday, June 2, 2014 7:37:32 AM
Subject: Re: [ovirt-users] oVirt All-In-One instructions for presentation?
----- Original Message -----
> From: "Greg Sheremeta" <gshereme(a)redhat.com>
> To: "users" <users(a)ovirt.org>
> Sent: Friday, May 30, 2014 6:21:43 AM
> Subject: [ovirt-users] oVirt All-In-One instructions for presentation?
>
> Hi,
>
> I submitted a tutorial proposal to LISA '14 called "Hands-on with
oVirt,"
> but
> it was rejected. However, we can still get oVirt in front of people if we
> rework it as a "lab."
>
> Basically a lab is just a one or two sheet set of instructions that would
> describe to someone how to test out oVirt All-In-One in the LISA lab.
>
> I know there have been demos of oVirt all-in-one at other conferences. Does
> anyone have a list of presentation-friendly instructions that he/she could
> share?
>
> Thanks!
> Greg
>
> PS -- Actually -- the 'demo' doesn't have to be all-in-one, but I was
> thinking that would be easiest given the unknown lab hardware at LISA. If
> the lab is very powerful, I suppose attendees could try to setup separate
> nodes. I'll try to find out lab details.
>
> Greg Sheremeta
> Red Hat, Inc.
> Sr. Software Engineer, RHEV
> Cell: 919-807-1086
> gshereme(a)redhat.com
Greg: We still may be able to help. How long of a lab would this need to be?
I agree the all-in-one might be the best option; we could also use the
LiveUSB version to let oVirt run without a hard install.
BKP