<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jan 18, 2017, at 10:48 AM, Mark Baker <<a href="mailto:mark.baker@canonical.com" class="">mark.baker@canonical.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">Hi Adrian,
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Let me know if you have similar questions or concerns about Ubuntu Core with Magnum.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">Mark</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Thanks Mark! Is there any chance you, or an Ubuntu Core representative could join us for a discussion at the PTG, and/or an upcoming IRC team meeting? The topic of supported operating system images for our cluster drivers is a current topic of team conversation,
and it would be helpful to have clarity on what (support/dev/test) resources upstream Linux packagers may be able to offer to help guide our conversation.</div>
<div><br class="">
</div>
<div>To give you a sense, we do have a Suse specific k8s driver that has been maturing during the Ocata release cycle, our Mesos driver uses Ubuntu Server, our Swarm and k8s drivers use Fedora Atomic, and another newer k8s driver uses Fedora. The topic of Operating
System (OS) support for cluster nodes (versus what OS containers are based on) is confusing for many cloud operators, so it would be helpful we worked on clarifying the options, and involve stakeholders from various OS distributions so that suitable options
are available for those who prefer to form Magnum clusters from OS images composed from one particular OS or another.</div>
<div><br class="">
</div>
<div>Ideally we could have this discussion at the PTG in Atlanta with participants like our core reviewers, Josh Berkus, you, our Suse contributors, and any other representatives from OS distribution organizations who may have an interest in cluster drivers
for their respective OS types. If that discussion proves productive, we could also engage our wider contributor base in a followup IRC team meeting with a dedicated agenda item to cover what’s possible, and summarize what various stakeholders provided to us
as input at the PTG. This might give us a chance to source further input from a wider audience than our PTG attendees.</div>
<div><br class="">
</div>
<div>Thoughts?</div>
<div><br class="">
</div>
<div>Thanks,</div>
<div><br class="">
</div>
<div>Adrian</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On 18 Jan 2017 8:36 p.m., "Adrian Otto" <<a href="mailto:adrian.otto@rackspace.com" class="">adrian.otto@rackspace.com</a>> wrote:<br type="attribution" class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Josh,<br class="">
<br class="">
> On Jan 18, 2017, at 10:18 AM, Josh Berkus <<a href="mailto:jberkus@redhat.com" class="">jberkus@redhat.com</a>> wrote:<br class="">
><br class="">
> Magnum Devs:<br class="">
><br class="">
> Is there going to be a magnum team meeting around OpenStack Summit in<br class="">
> Boston?<br class="">
><br class="">
> I'm the community manager for Atomic Host, so if you're going to have<br class="">
> Magnum meetings, I'd like to send you some Atomic engineers to field any<br class="">
> questions/issues at the Summit.<br class="">
<br class="">
Thanks for your question. We are planning to have our team design meetings at the upcoming PTG event in Atlanta. We are not currently planning to have any such meetings in Boston. With that said, we would very much like to involve you in an important Atomic
related design decision that has recently surfaced, and would like to welcome you to an upcoming Magnum IRC team meeting to meet you and explain our interests and concerns. I do expect to attend the Boston summit myself, so I’m willing to meet you and your
engineers on behalf of our team if you are unable to attend the PTG. I’ll reach out to you individually by email to explore our options for an Atomic Host meeting agenda item in the mean time.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Adrian<br class="">
______________________________<wbr class="">______________________________<wbr class="">______________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">
OpenStack-dev-request@lists.<wbr class="">openstack.org?subject:<wbr class="">unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/<wbr class="">cgi-bin/mailman/listinfo/<wbr class="">openstack-dev</a><br class="">
</blockquote>
</div>
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>