<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 02/07/2018 05:28 AM, Thierry Carrez
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7d643a97-36f2-1852-5a49-b35bd7def714@openstack.org">
<pre wrap="">Lance Bragstad wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 02/05/2018 09:34 AM, Thierry Carrez wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Lance Bragstad wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Colleen started a thread asking if there was a need for a baremetal/vm
group session [0], which generated quite a bit of positive response. Is
there still a possibility of fitting that in on either Monday or
Tuesday? The group is usually pretty large.
[0]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2018-January/126743.html">http://lists.openstack.org/pipermail/openstack-dev/2018-January/126743.html</a>
</pre>
</blockquote>
<pre wrap="">Yes, we can still allocate a 80-people room or a 30-people one. Let me
know if you prefer Monday, Tuesday or both.
</pre>
</blockquote>
<pre wrap="">Awesome - we're collecting topics in an etherpad, but we're likely only
going to get to three or four of them [0] [1]. We can work those topics
into two sessions. One on Monday and one on Tuesday, just to break
things up in case other things are happening those days that people want
to get to.
</pre>
</blockquote>
<pre wrap="">
Looking at that etherpad, do you need the room allocated for all the day
on Monday/Tuesday ? It's doable, but if you already know you won't do
anything on Monday afternoon, we can make that room reservable then.</pre>
</blockquote>
I agree. I don't think we will need all of Monday and Tuesday. I
wanted to get a rough schedule put together so we wouldn't need to
reserve the entire room all day. So far we haven't received feedback
on the proposed schedule, so it's probably safe to mark the times
listed in the etherpad.<br>
<blockquote type="cite"
cite="mid:7d643a97-36f2-1852-5a49-b35bd7def714@openstack.org">
<pre wrap="">
What should the track name be ? Some people suggested "cross-project
identity integration" instead of baremetal-vm.</pre>
</blockquote>
I'm terrible with names. Since the topics are identity specific,
that would make sense, but I do feel as though we high-jacked the
session and the name =/<br>
<br>
I think John Garbutt came up with the original name. I'm sure he can
explain the reasoning for it better than I can.<br>
<blockquote type="cite"
cite="mid:7d643a97-36f2-1852-5a49-b35bd7def714@openstack.org">
<pre wrap="">
</pre>
<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>