Finalizing open workshop schedule

Doron Fediuck dfediuck at redhat.com
Tue Mar 13 20:11:37 UTC 2012


On 13/03/12 20:28, Perry Myers wrote:
> On 03/13/2012 01:33 PM, Karsten 'quaid' Wade wrote:
>> Based on the below feedback I updated the agenda and posted it
>> here:
> 
>> http://www.ovirt.org/wiki/Workshop_March_2012#Agenda_for_workshop
> 
>> 09:30 - 11:00 :: oVirt intro & architecture (presented by Red Hat 
>> engineers) 11:00 - 11:15 :: MORNING TEA BREAK 11:15 - 12:00 ::
>> Engine core (presented by Red Hat engineers) 12:00 - 12:30 :: API
>> (presented by Red Hat engineers) 12:30 - 13:30 :: LUNCH 13:30 -
>> 14:15 :: oVirt Node Arch and details of oVirt node (presented by
>> Red Hat engineers)
> 
> Right now there are no engineers from the oVirt Node team that will be
> in Beijing for this workshop.  However, we will have a few folks from
> the Red Hat QE team that are primarily responsible for RHEVH/oVirt
> Node testing.
> 
> The QE folks should be able to interface for Q&A on oVirt Node/RHEVH,
> and we'll see if we can get them to do a brief overview as well, but
> that is not yet determined.  So we should keep this slot open for now
> and we'll see if we can get someone to give the talk on oVirt Node
> architecture.
> 
> Thanks,
> 
> Perry

Considering Perry's mail we can go for:

09:30 - 11:00 :: oVirt intro & architecture (presented by Red Hat engineers)

11:00 - 11:15 :: MORNING TEA BREAK

11:15 - 12:00 :: Engine core (presented by Red Hat engineers)
12:00 - 12:45 :: VDSM (presented by Red Hat engineers)

12:45 - 13:45 :: LUNCH

13:45 - 14:15 :: API (presented by Red Hat engineers)
14:15 - 15:00 :: Storage (presented by Red Hat engineers)
15:00 - 15:45 :: MOM integration  (presented by IBM engineers)

15:45 - 16:30 :: AFTERNOON TEA BREAK

16:30 - 17:15 :: *TBD* based on capabilities[1]
17:15 - 17:30 :: Wrap-up and finish

[1] One of:
* oVirt Node Arch and details of oVirt node (presented by Red Hat engineers)- depends on availability
* Setting up the Engine core (get me started)- depends on local networking availability.

Objections?



More information about the Arch mailing list