<div dir="ltr"><div>Thanks Ruby for bringing this up!</div><div><br></div><div>There would be a collision if nova and mogan consume the same ironic nodes cluster, as both of them will see all the available node resources. So if someone wants to choose mogan for baremetal compute management, the recommended deployment is Mogan+Ironic for baremetals and Nova+Libvirt for VMs, this way we treat baremetals and vms as different compute resources. In a cloud with both vms and baremetals, it's more clear to have different set of APIs to manage them if users really care about what resources they got instead of just the performance. We also create a mogan horizon plugin which adds separated baremetal servers panel[1].</div><div><br></div><div>But for users who don't care whether it's a vm or baremetal server, they just want to ask OpenStack for a specific flavor of compute resource to run the workloads, it's definitely no need to deploy Mogan to separate baremetals to a different compute resource to expose full baremetal capabilities.</div><div><br></div><div><br></div><div>[1] <a href="https://pasteboard.co/cJ889Y7IA.png">https://pasteboard.co/cJ889Y7IA.png</a></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 29, 2017 at 9:55 PM, Loo, Ruby <span dir="ltr"><<a href="mailto:ruby.loo@intel.com" target="_blank">ruby.loo@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="white" lang="EN-US">
<div class="gmail-m_3663137975345778890WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri">Hi Zhenguo (and others),<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri">is there a description/email thread/documentation about how mogan and nova co-exists in the same cloud? In particular, will it be possible for mogan and nova (with ironic driver) to run?
Is this something that we will recommend or not recommend or not mention? Because I don't see how the end user will know to issue a mogan command to get a baremetal server, vs a nova-boot command to get a baremetal server. And/or does anyone envison that horizon
will hide all that from the user somehow?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri">--ruby<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal" style="margin-left:36pt"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black">Zhenguo Niu <<a href="mailto:niu.zglinux@gmail.com" target="_blank">niu.zglinux@gmail.com</a>><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<wbr>openstack.org</a>><br>
<b>Date: </b>Thursday, May 25, 2017 at 10:41 PM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.<wbr>openstack.org</a>><br>
<b>Subject: </b>Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><snip><u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:36pt">As I understand, baremetal instance in nova is a 'specical virtual machine'(raw performance). Users claim the instance by specifying a flavor with 'vcpus', 'memory', "root_gb" instead of real hardware specs like
(cpu model/cores, hard drives type/amount, nics type/amount), then he get an instance with properties like 'vm_state' and other 'virtual' stuff. As baremetal in nova use the same model and same set of API that designed for vms, so even for end users, it's
not that easy to know which instance is a baremetal server, so maybe it's good to call that baremetal server a special vm instance.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt">So, yes the end user actually know that there is a difference between getting a bremetal instance via mogan or via nova :)<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<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">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">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Best Regards,<br></div>Zhenguo Niu<br></div></div>
</div></div>