public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: libvirt-users@redhat.com, qemu-discuss@nongnu.org, kvm@vger.kernel.org
Subject: oVirt workshop coming up - January 22-24 2013
Date: Thu, 13 Dec 2012 18:46:18 +0100	[thread overview]
Message-ID: <50CA146A.1050504@redhat.com> (raw)

Hi everyone,

I thought that some of you might be interested to hear about an upcoming 
event I'm helping put together, an oVirt workshop in NetApp HQ in 
Sunnyvale, California on January 22-24.

oVirt is (as I'm sure most of you know) a management system for 
KVM-based virtualization - allowing you to easily handle VMs, network, 
storage and hosts in a virtual datacenter.

The workshop's three day agenda will cover installation and use of 
oVirt, integrating with oVirt though the platform's APIs, and 
contributing to development of the project. This is an excellent 
opportunity to find out what's coming in future versions of RHEV, and to 
meet users who are on the bleeding edge of what we will be shipping in 
future products.

Reserve your spot at this free event by registering at 
http://ovirtnetapp2013.eventbrite.com/, and see 
http://www.ovirt.org/NetApp_Workshop_January_2013 for more information.

We are actively seeking presenters who can talk about interesting ways 
in which they are using oVirt, or share integration stories. Please send 
proposals for talks to workshop-pc@ovirt.org - the official end of the 
call for content is Friday 14th of December, 23:59 PST, but since we 
will not be drafting the schedule until next week, any proposals 
received by Monday will also be considered.

Thanks!
Dave.

-- 
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13

                 reply	other threads:[~2012-12-13 17:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50CA146A.1050504@redhat.com \
    --to=dneary@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvirt-users@redhat.com \
    --cc=qemu-discuss@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox