Fwd: Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call for Participation

2014-11-30 Thread Dave Lester
Today is the final day to submit FOSDEM proposals for both the IaaS and
Virtualization devrooms. Anyone else planning to submit a proposal? Talks
are 30min + 10min for questions.

Dave

-- Forwarded message --
From: Joe Brockmeier j...@redhat.com
Date: Fri, Oct 24, 2014 at 12:59 PM
Subject: Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call for
Participation
To: fos...@lists.fosdem.org
Cc: iaas-virt-devr...@lists.fosdem.org


FOSDEM '15 Infrastructure-as-a-Service devroom

Please forward to any list or individual that might be interested in
participating in this devroom!

-
Important Dates and Info!
-

Submission deadline: 1 December 2014
Acceptance notifications: 15 December 2014
Final schedule announcement: 9 January 2015
Devroom: 31 January 2015

-
Call for Participation
-

The open source IaaS devroom will host sessions around open source
Infrastructure-as-a-Service projects such as (but not limited to)
Apache CloudStack, OpenStack, oVirt, OpenNebula, and Ganeti.

This room will focus on collaboration between projects on common
problems and software, such as shared storage, virtualized networking,
interfacing with multiple hypervisors, and scaling across hundreds or
thousands of servers.

Organizers are seeking topics that are interesting to multiple projects,
and hope to encourage developers to share experience solving problems
with their own projects.

-
Call for Volunteers
-

We are also looking for volunteers to help run the devroom. We need
assistance watching time for the speakers, and helping with video
for the devroom. Please contact Joe Brockmeier (jzb at redhat.com) for
more information here.

-
Details: READ CAREFULLY
-

This year at FOSDEM there will be a one-day devroom to focus on IaaS
projects. If your project is related to IaaS, we would love to see
your submissions.

Please note that we expect more proposals than we can possibly accept,
so it is vitally important that you submit your proposal on or before
the deadline. Late submissions are unlikely to be considered.

All slots are 40 minutes, with 30 minutes planned for presentations, and
10 minutes for QA.

All presentations *will* be recorded and made available under Creative
Commons licenses. Please indicate when submitting your talk that your
presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0
license when submitting the talk and that you agree to have your
presentation recorded. For example:

  If my presentation is accepted for FOSDEM, I hereby agree to license
   all recordings, slides, and other associated materials under the
   Creative Commons Attribution Share-Alike 4.0 International License.
   Sincerely, NAME.

Also, in the notes field, please confirm tnat if your talk is accepted
that you *will* be able to attend FOSDEM and deliver your presentation.
We will not consider proposals from prospective speakers unsure whether
they will be able to secure funds for travel and lodging to attend
FOSDEM. (Sadly, we are not able to offer travel funding for prospective
speakers.)

-
How to Submit
-

All submissions are made via the Pentabarf event planning site:

https://penta.fosdem.org/submission/FOSDEM15

If you have not used Pentabarf before, you will need to create an account.

After creating the account, select Create Event and then be sure to
select Infrastructure as a service devroom from the options under
Track.

-
Questions
-

If you have any questions about this devroom, please send your questions
to:

iaas-virt-devr...@lists.fosdem.org

We will respond as quickly as possible. Thanks!
___
iaas-virt-devroom mailing list
iaas-virt-devr...@lists.fosdem.org
https://lists.fosdem.org/listinfo/iaas-virt-devroom



-- 
@davelester
Open Source Advocate | Twitter, Inc


Proposal: shared Mesos framework hosting and registry

2014-11-30 Thread Dave Lester
As the number of Mesos frameworks grows (and now, a module system), I think
it's time to create a community-maintained registry with the goal of making
frameworks and modules easier to discover, contribute to, and install.

There's already a JIRA ticket tracking this (MESOS-1759) and I've chatted
with several folks (thanks in particular Victor Vieux, Tom Arnfeld, Vinod
Kone, Timothy St Clair, and Joe Stein). I'd like to advance the
conversation by offering a proposal on the public mailing list.

I imagine two initiatives to achieve this:

1) Shared hosting via a GitHub org. I'm not sure if you're familiar with
how Jenkins maintains their plugins on GitHub [1], but they allow
individual plugins to have their own repo within their GH org. Plugins are
repos with a specific naming convention (in their case, they've appended
-plugin to the repo name but this isn't the same approach we'd need to
take). Having a shared GH org creates greater visibility to what people are
doing, and encourages community participation and ownership.

In the case of Mesos, not all frameworks will jump at the chance to have
community hosting which is fine. But particularly for smaller frameworks, I
think this is a good option given the success Jenkins has had. We could
potentially use the existing /mesos github org, or create a new org
/mesos-extensions or something of the like. It seems like the only
potential snag here is that we'll want to be explicit that these aren't
Apache-blessed plugins and instead maintained by the larger ecosystem, but
I believe we can achieve that by offering a notice in the GH org
description.

2) A registry that allows framework writers to publish new versions of
their frameworks to a central repository that could be programmatically
accessed and rendered online. The v1 could be incredibly simple, but I
think this is a foundational piece that can grow with the project in the
future. Since this is a little bit more-involved, I've created a separate
Google Doc [2] to begin drafting the scope for this:
https://docs.google.com/document/d/1sOoPtEyLlST5GTU5iSccqWUsAOlJhf4N9cHoylylYgY/edit?usp=sharing,
and have intentionally punted on some of the implementation details until
the scope is finalized and I gauge interest from users and potential
collaborators.

What do you think? If folks are on board I will assign the JIRA issue to
myself and get to work; I'd also welcome collaborators to help get this off
the ground since I think it will be a boost for the community. Feedback is
welcome!

Thanks,
Dave

[1] https://github.com/jenkinsci/
[2]
https://docs.google.com/document/d/1sOoPtEyLlST5GTU5iSccqWUsAOlJhf4N9cHoylylYgY/edit?usp=sharing