<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Project: Cinder</p>
<p>Attendees: Approximately 30</p>
<p>I was really pleased by the number of people that attended the
Cinder session and the fact that they people in the room seemed
engaged with the presentation and asked good questions showing
interest in the project. I think having the on-boardings rooms
was beneficial and hopefully something that we can continue. <br>
</p>
<p>Given the number of people in the room we didn't go around and
introduce everyone. I did have the Sean McGinnis introduce
himself as PTL and had the other Cinder Core members introduce
themselves so that the attendees could put faces with our names.</p>
<p>From there we kicked off the presentation [1] which covered the
following high level topics:</p>
<ul>
<li>Introduction of Cinder's Repos and components</li>
<li>Quick overview of Cinder's architecture/organization</li>
<li>Pointers to the Upstream Institute education (Might have done
a bit of a sales pitch for the next session here ;-))</li>
<li>Expanded upon the Upstream Institute education to explain how
what was taught there specifically applied to Cinder</li>
<li>Walked through the main Cinder code tree</li>
<li>Described how to test changes to Cinder</li>
</ul>
My presentation was designed to assume that attendees had been
through Upstream Institute. I had coverage in the slides in case
they had not been through the education. Unfortunately most of the
class had not been through the education so I did spend a portion of
time re-iterating those concepts and less time was able to be spent
at the end going through real world examples of working with changes
in Cinder. I got feedback from a few people that having some real
hands on coding examples would have been helpful.<br>
<br>
One way we could possible handle this is to split the on-boarding to
a introduction section and then a more advanced second session. The
other option is that we require people who are attending the
on-boarding to have been through Upstream Institute. Something to
think about.<br>
<br>
I think it was unfortunate that the session wasn't recorded. We
shared a lot of good information (between good questions and having
a good representation of Cinder's Core team in the room) that it
would have been nice to capture. Given this I am planning at some
point in the near future to work with Walt Boring to record a
version of the presentation that can be uploaded to our Cinder
YouTube channel and include some coding examples.<br>
<br>
In summary, I think the on-boarding rooms were a great addition and
the Cinder team is pleased with how we used the time. I think it is
something we would like to continue to invest time into developing
and improving.<br>
<br>
Jay<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://www.slideshare.net/JayBryant2/openstack-cinder-onboarding-education-boston-summit-2017">https://www.slideshare.net/JayBryant2/openstack-cinder-onboarding-education-boston-summit-2017</a><br>
<br>
<div class="moz-cite-prefix">On 5/19/2017 3:43 PM, Lance Bragstad
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAE6oFcGis4k3f3RDbSaoHK4-Wq=_ohZE6qJzebiJrBiSx55VbQ@mail.gmail.com">
<div dir="ltr">Project: Keystone
<div>Attendees: 12 - 15</div>
<div><br>
</div>
<div>We conflicted with one of the Baremetal/VM sessions </div>
<div><br>
</div>
<div>I attempted to document most of the session in my recap
[0].</div>
<div><br>
</div>
<div>We started out by doing a round-the-room of introductions
so that folks could put IRC nicks to faces (we also didn't
have a packed room so this went pretty quick). After that we
cruised through a summary of keystone, the format of the
projects, and the various processes we use. All of this took
*maybe* 30 minutes.</div>
<div><br>
</div>
<div>From there we had an open discussion and things evolved
organically. We ended up going through:</div>
<div>
<ul>
<li>the differences between the v2.0 and v3 APIs</li>
<li>keystonemiddleware architecture, how it aids services,
and how it interacts with keystone</li>
<ul>
<li>we essentially followed an API call for creating a
instance from keystone -> nova -> glance</li>
</ul>
<li>how authentication scoping works and why it works that
way</li>
<li>how federation works and why it's setup the way it is</li>
<li>how federated authentication works (<a
href="https://goo.gl/NfY3mr" moz-do-not-send="true">https://goo.gl/NfY3mr</a>)</li>
</ul>
</div>
<div>All of this was pretty well-received and generated a lot of
productive discussion. We also had several seasoned keystone
contributors in the room, which helped a lot. Most of the
attendees were all curious about similar topics, which was
great, but we totally could have split into separate groups
given the experience we had in the room (we'll save that in
our back pocket for next time).</div>
<div><br>
</div>
<div>[0] <a
href="https://www.lbragstad.com/blog/openstack-boston-summit-recap"
moz-do-not-send="true">https://www.lbragstad.com/blog/openstack-boston-summit-recap</a></div>
<div>[1] <a
href="https://www.slideshare.net/LanceBragstad/keystone-project-onboarding"
moz-do-not-send="true">https://www.slideshare.net/LanceBragstad/keystone-project-onboarding</a></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 19, 2017 at 10:37 AM,
Michał Jastrzębski <span dir="ltr"><<a
href="mailto:inc007@gmail.com" target="_blank"
moz-do-not-send="true">inc007@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Kolla:<br>
Attendees - full room (20-30?)<br>
Notes - Conflict with kolla-k8s demo probably didn't help<br>
<br>
While we didn't have etherpad, slides, recording (and video
dongle<br>
that could fit my laptop), we had great session with analog
tools<br>
(whiteboard and my voice chords). We walked through
architecture of<br>
each Kolla project, how they relate to each other and so on.<br>
<br>
Couple things to take out from our onboarding:<br>
1. Bring dongles<br>
2. We could've used bigger room - people were leaving
because we had<br>
no chairs left<br>
3. Recording would be awesome<br>
4. Low tech is not a bad tech<br>
<br>
All and all, when we started session I didn't know what to
expect or<br>
what people will expect so we just...rolled with it, and
people seemed<br>
to be happy with it:) I think onboarding rooms were great
idea (kudos<br>
to whoever came up with it)! I'll be happy to run it again
in Sydney.<br>
<br>
Cheers,<br>
Michal<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 19 May 2017 at 08:12, Julien Danjou <<a
href="mailto:julien@danjou.info"
moz-do-not-send="true">julien@danjou.info</a>>
wrote:<br>
> On Fri, May 19 2017, Sean Dague wrote:<br>
><br>
>> If you ran a room, please post the project,
what you did in the room,<br>
>> what you think worked, what you would have done
differently. If you<br>
>> attended a room you didn't run, please provide
feedback about which one<br>
>> it was, and what you thought worked / didn't
work from the other side of<br>
>> the table.<br>
><br>
> We shared a room for Telemetry and CloudKitty for
90 minutes.<br>
> I was there with Gordon Chung for Telemetry.<br>
> Christophe Sauthier was there for CloudKitty.<br>
><br>
> We only had 3 people showing up in the session. One
wanted to read his<br>
> emails in a quiet room, the two others had a couple
of question on<br>
> Telemetry – though it was not really related to
contribution as far as I<br>
> can recall.<br>
><br>
> I had to leave after 45 minutes because they was an
overlap with a talk<br>
> I was doing and rescheduling did not seem possible.
And everybody left a<br>
> few minutes after I left apparently.<br>
><br>
> --<br>
> Julien Danjou<br>
> -- Free Software hacker<br>
> -- <a href="https://julien.danjou.info"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://julien.danjou.info</a><br>
><br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage
questions)<br>
> Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>