<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Helvetica, Arial, sans-serif">Hi all,<br>
<br>
This is related to the following blueprint:<br>
<a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/nova/+spec/pxe-boot-instance">https://blueprints.launchpad.net/nova/+spec/pxe-boot-instance</a><br>
<br>
I would like to discuss here </font><font face="Helvetica, Arial,
sans-serif"><font face="Helvetica, Arial, sans-serif">briefly </font>
an implementation detail and collect some feedback.<br>
<br>
With this new feature, the boot option "boot from network" will be
added to the existing options "boot from disk" and "boot from
volume". The first approach to implement this was to define a
specific IMAGE_ID_TOKEN which will be used to handle the "boot
from network" option as a special case of "boot from disk" option.
This is a simple solution and has the advantage of avoiding
changes to the Nova REST API. <br>
<br>
The second option would be to </font><font face="Helvetica,
Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">introduce</font>
the new "boot from network" option in the Nova REST API with all
the consequences of an API change (test, documentation, etc).<br>
<br>
Any thoughts on these two alternatives? This is a preliminary
investigation in order to avoid wasting time on an implementation
which would be rejected during review due to wrong design
decisions.<br>
<br>
Ondrej<br>
<br>
<br>
</font>
</body>
</html>