<div dir="ltr"><div><div><div><div><font size="4">Thank you !<br></font></div><font size="4">I noticed the two sets of k+r in tftp configuration of ironic.<br></font></div><font size="4">Should the two sets be the same k+r ?<br>
</font></div><font size="4">The first set is defined in the ironic node definition. <br></font></div><font size="4">How do we define the second set correctly ? </font><br><div><div><div><div><div><div><div><div><div class="gmail_extra">
<br clear="all"><div><div dir="ltr"><div><font face="comic sans ms, sans-serif" size="4"><b><i>Best Regards！</i></b></font></div><font face="comic sans ms, sans-serif" size="4"><b><i>Chao Yan<br><font>--------------<br></font></i></b></font><font face="comic sans ms, sans-serif" size="4"><b><i><font>My twitter：Andy Yan <a href="https://twitter.com/yanchao727" target="_blank">@yanchao727</a></font></i></b></font><br>
<font face="comic sans ms, sans-serif" size="4"><b><i><font>My Weibo：<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a><br>--------------</font><br></i></b></font></div></div>
<br><br><div class="gmail_quote">2014-06-04 21:00 GMT+08:00 Dmitry Tantsur <span dir="ltr"><<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="">On Wed, 2014-06-04 at 20:29 +0800, 严超 wrote:<br>
> Hi,<br>
><br>
> Thank you very much for your reply !<br>
><br>
> But there are still some questions for me. Now I've come to the step<br>
> where ironic partitions the disk as you replied.<br>
><br>
> Then, how does ironic copies an image ? I know the image comes from<br>
> glance. But how to know image is really available when reboot?<br>
</div>I don't quite understand your question, what do you mean by "available"?<br>
Anyway, before deploying Ironic downloads image from Glance, caches it<br>
and just copies to a mounted iSCSI partition (using dd or so).<br>
<div class=""><br>
><br>
> And, what are the differences between final kernel (ramdisk) and<br>
> original kernel (ramdisk) ?<br>
</div>We have 2 sets of kernel+ramdisk:<br>
1. Deploy k+r: these are used only for deploy process itself to provide<br>
iSCSI volume and call back to Ironic. There's ongoing effort to create<br>
smarted ramdisk, called Ironic Python Agent, but it's WIP.<br>
2. Your k+r as stated in Glance metadata for an image - they will be<br>
used for booting after deployment.<br>
<div class=""><div class="h5"><br>
><br>
> Best Regards！<br>
> Chao Yan<br>
> --------------<br>
> My twitter：Andy Yan @yanchao727<br>
> My Weibo：<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a><br>
> --------------<br>
><br>
><br>
><br>
> 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>>:<br>
> Hi!<br>
><br>
> Workflow is not entirely documented by now AFAIK. After PXE<br>
> boots deploy<br>
> kernel and ramdisk, it exposes hard drive via iSCSI and<br>
> notifies Ironic.<br>
> After that Ironic partitions the disk, copies an image and<br>
> reboots node<br>
> with final kernel and ramdisk.<br>
><br>
> On Wed, 2014-06-04 at 19:20 +0800, 严超 wrote:<br>
> > Hi, All:<br>
> ><br>
> > I searched a lot about how ironic automatically<br>
> install image<br>
> > on bare metal. But there seems to be no clear workflow out<br>
> there.<br>
> ><br>
> > What I know is, in traditional PXE, a bare metal<br>
> pull image<br>
> > from PXE server using tftp. In tftp root, there is a ks.conf<br>
> which<br>
> > tells tftp which image to kick start.<br>
> ><br>
> > But in ironic there is no ks.conf pointed in tftp.<br>
> How do bare<br>
> > metal know which image to install ? Is there any clear<br>
> workflow where<br>
> > I can read ?<br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Best Regards！<br>
> > Chao Yan<br>
> > --------------<br>
> > My twitter：Andy Yan @yanchao727<br>
> > My Weibo：<a href="http://weibo.com/herewearenow" target="_blank">http://weibo.com/herewearenow</a><br>
> > --------------<br>
> ><br>
><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> ><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div></div></div></div></div></div></div></div></div>