<font size=2 face="sans-serif">Can you elaborate what is the purpose of
this database?</font>
<br><font size=2 face="sans-serif">If we compare it to KVM support, the
'primary' location of VMs' metadata is in libvirt internal store (outside
of Nova), and then it is cached in Nova DB, for Nova purposes.</font>
<br><font size=2 face="sans-serif">A similar approach might make for bare-metal
machines too -- keep 'primary' metadata store outside of Nova, and a cache
in Nova DB.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Alex</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">David Kang <dkang@isi.edu></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">OpenStack Development
Mailing List <openstack-dev@lists.openstack.org>, "openstack@lists.launchpad.net
(openstack@lists.launchpad.net)" <openstack@lists.launchpad.net>,
</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">15/08/2012 06:32 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Openstack]
Discussion about where to put database for bare-metal provisioning (review
10726)</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">openstack-bounces+glikson=il.ibm.com@lists.launchpad.net</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2><br>
<br>
Hi,<br>
<br>
This is call for discussion about the code review 10726.<br>
</font></tt><a href=https://review.openstack.org/#/c/10726/><tt><font size=2>https://review.openstack.org/#/c/10726/</font></tt></a><tt><font size=2><br>
Mark asked why we implemented a separata database for bare-metal provisioning.<br>
Here we describe our thought. <br>
We are open to discussion and to the changes that the community recommends.<br>
Please give us your thoughts.<br>
<br>
NTT Docomo and USC/ISI have developed bare-metal provisioning.<br>
We created separate database to describe bare-metal nodes, which consists
of 5 tables now.<br>
Our initial implementation assumes the database is not a part of nova database.<br>
In addition to the reasons described in the comments of the code review,<br>
here is another reason we decided a separate database for baremetal provisioning.<br>
<br>
Bare-metal database is mainly used by bare-metal nova-compute.<br>
Since bare-metal nova-compute manages multiple bare-metal machines, <br>
it needs to keep/update the information of bare-metal machines.<br>
If the bare-metal database is in the main nova db, accessing nova db remotely
by<br>
bare-metal nova-compute is inevitable.<br>
Once Vish told us that shared db access from nova-compute is not desirable.<br>
<br>
It is possible to make the scheduler do the job of bare-metal nova-compute.<br>
However, it would need a big changes in how the scheduler and a nova-compute<br>
communicates. For example, currently, the scheduler casts an instance to
a<br>
nova-compute. But for bare-metal node, the scheduler should cast an instance
<br>
to a bare-metal machine through bare-metal nova-compute.<br>
Bare-metal nova-compute should boot the machine, transfer kernel, fs, etc.<br>
So, bare-metal nova-compute should know the id of bare-metal node and other
information <br>
for booting (PXE ip address, ...) and more.<br>
That information should be sent to bare-metal nova-compute by the scheduler.<br>
<br>
If frequent access of bare-metal tables in nova db from bare-metal nova-compute<br>
is OK, we are OK to put the bare-metal tables into nova db.<br>
<br>
Please let us know your opinions.<br>
<br>
Thanks,<br>
David, Mikyung @ USC/ISI<br>
<br>
----------------------<br>
Dr. Dong-In "David" Kang<br>
Computer Scientist<br>
USC/ISI<br>
<br>
<br>
_______________________________________________<br>
Mailing list: </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2>https://launchpad.net/~openstack</font></tt></a><tt><font size=2><br>
Post to : openstack@lists.launchpad.net<br>
Unsubscribe : </font></tt><a href=https://launchpad.net/~openstack><tt><font size=2>https://launchpad.net/~openstack</font></tt></a><tt><font size=2><br>
More help : </font></tt><a href=https://help.launchpad.net/ListHelp><tt><font size=2>https://help.launchpad.net/ListHelp</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>