incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <da...@gnsa.us>
Subject Re: CloudStack gathering around LinuxConNA?
Date Tue, 14 Aug 2012 01:50:01 GMT
On Mon, Aug 13, 2012 at 8:07 PM, Eric <epretorious@yahoo.com> wrote:
>> From: Eric <epretorious@yahoo.com>
>>To: "cloudstack-dev@incubator.apache.org" <cloudstack-dev@incubator.apache.org>
>>Sent: Thursday, August 9, 2012 11:00 AM
>>Subject: Re: CloudStack gathering around LinuxConNA?
>>
>>> From: David Nalley <david@gnsa.us>
>>
>>>>>>> On Fri, May 25, 2012 at 9:51 AM, David Nalley<david@gnsa.us>
   wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi folks,
>>>>>>>>
>>>>>>>> $dayjob has reserved some space in San Diego immediately
preceeding
>>>>>>>> LinuxConNA [1] (Aug 29-31) during which they plan to hold
XenSummit
>>>>>>>> [2] (Aug 27-28) - and they have some excess room space they
are not
>>>>>>>> going to use. Before deciding to release the space back to
the hotel
>>>>>>>> they asked if CloudStack could make use of it. So - is anyone
>>>>>>>> interested in a hackathon or bootcamp, or even a social event?
It
>>>>>>>> sounds interesting because of both Xen Summit and there is
a
>>>>>>>> co-located oVirt workshop, and the kernel summit, which draws
lots of
>>>>>>>> KVM folks - so should be plenty of virtualization folks present,
>>>>>>>> though obviously they might not be engaged directly with
us, but might
>>>>>>>> be helpful from an ability to build relationships standpoint.
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Just to follow up on this. I'll take the offer for the room on
the
>>>>>>> 27th and 28th. I've been told the room will seat around 30 classroom
>>>>>>> style. Any suggestions for what we should have as content? One
day
>>>>>>> hackathon, one day developer training? Two days of hackathon?
>>>>>>> Something else?
>>
>>I'd really like to see a comprehensive overview if that would be possible.
>
>
> Just to clarify: I propose a bootcamp-style overview with...
>
>  * an introduction - "this what CS does."
>  * some architecture review  - "these are all the pieces to CS."
>  * operational review - "this is how the different pieces of CS interact."
>  * best practices - "do this with CS. don't do that."
>
>
> Eric Pretorious
> Truckee, CA
>

Feel free to edit the wiki (it's a wiki, edit boldly!) to reflect what
you'd like to see.

--David

Mime
View raw message