[openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Hi, All: I searched a lot about how ironic automatically install image on bare metal. But there seems to be no clear workflow out there. What I know is, in traditional PXE, a bare metal pull image from PXE server using tftp. In tftp root, there is a ks.conf which tells tftp which

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Dmitry Tantsur
Hi! Workflow is not entirely documented by now AFAIK. After PXE boots deploy kernel and ramdisk, it exposes hard drive via iSCSI and notifies Ironic. After that Ironic partitions the disk, copies an image and reboots node with final kernel and ramdisk. On Wed, 2014-06-04 at 19:20 +0800, 严超

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Hi, Thank you very much for your reply ! But there are still some questions for me. Now I've come to the step where ironic partitions the disk as you replied. Then, how does ironic copies an image ? I know the image comes from glance. But how to know image is really available when reboot? And,

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Dmitry Tantsur
On Wed, 2014-06-04 at 20:29 +0800, 严超 wrote: Hi, Thank you very much for your reply ! But there are still some questions for me. Now I've come to the step where ironic partitions the disk as you replied. Then, how does ironic copies an image ? I know the image comes from glance. But

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Dmitry Tantsur
On Wed, 2014-06-04 at 21:18 +0800, 严超 wrote: Thank you ! I noticed the two sets of k+r in tftp configuration of ironic. Should the two sets be the same k+r ? Deploy images are created for you by DevStack/whatever. If you do it by hand, you may use diskimage-builder. Currently they are

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Thank you ! I noticed the two sets of k+r in tftp configuration of ironic. Should the two sets be the same k+r ? The first set is defined in the ironic node definition. How do we define the second set correctly ? *Best Regards!* *Chao Yan--**My twitter:Andy Yan @yanchao727

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Yes, but when you assign a production image to an ironic bare metal node. You should provide *ramdisk_id and kernel_id. * Should the *ramdisk_id and kernel_id* be the same as deploy images (aka the first set of k+r) ? You didn't answer me if the two sets of r + k should be the same ? *Best

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Dmitry Tantsur
On Wed, 2014-06-04 at 21:51 +0800, 严超 wrote: Yes, but when you assign a production image to an ironic bare metal node. You should provide ramdisk_id and kernel_id. What do you mean by assign here? Could you quote some documentation? Instance image is assigned using --image argument to `nova

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Devananda van der Veen
On Wed, Jun 4, 2014 at 6:51 AM, 严超 yanchao...@gmail.com wrote: Yes, but when you assign a production image to an ironic bare metal node. You should provide ramdisk_id and kernel_id. Should the ramdisk_id and kernel_id be the same as deploy images (aka the first set of k+r) ? You didn't answer

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Lucas Alvares Gomes
On Wed, Jun 4, 2014 at 2:51 PM, 严超 yanchao...@gmail.com wrote: Yes, but when you assign a production image to an ironic bare metal node. You should provide ramdisk_id and kernel_id. Should the ramdisk_id and kernel_id be the same as deploy images (aka the first set of k+r) ? You didn't answer

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Thank you very much for your help and replies. It's much clearer and I've solved my problem. *Best Regards!* *Chao Yan--**My twitter:Andy Yan @yanchao727 https://twitter.com/yanchao727* *My Weibo:http://weibo.com/herewearenow http://weibo.com/herewearenow--*

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
Thank you very much for your help and replies. It's much clearer and I've solved my problem. *Best Regards!* *Chao Yan--**My twitter:Andy Yan @yanchao727 https://twitter.com/yanchao727* *My Weibo:http://weibo.com/herewearenow http://weibo.com/herewearenow--*

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread 严超
BTW, If I run sudo ./bin/disk-image-create -a amd64 ubuntu deploy-ironic -o /tmp/deploy-ramdisk-ubuntu, What is the username/password for image deploy-ramdisk-ubuntu ? *Best Regards!* *Chao Yan--**My twitter:Andy Yan @yanchao727 https://twitter.com/yanchao727* *My

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Clint Byrum
Excerpts from 严超's message of 2014-06-04 20:34:01 -0700: BTW, If I run sudo ./bin/disk-image-create -a amd64 ubuntu deploy-ironic -o /tmp/deploy-ramdisk-ubuntu, What is the username/password for image deploy-ramdisk-ubuntu ? There isn't one. You can write an element if you want to include a

Re: [openstack-dev] [ironic workflow question]

2014-06-04 Thread Ramakrishnan G
The deployment kernel/ramdisk is supposed to be built by ramdisk-image-create command. *ramdisk-image-create -a amd64 fedora deploy-ironic -o /tmp/deploy-ramdisk* The deployment kernel/ramdisk is used only for deployment and cannot give a full-fledged system. The deploy images are created by