[openstack-dev] [ironic workflow question]
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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 https://twitter.com/yanchao727* *My Weibo：http://weibo.com/herewearenow http://weibo.com/herewearenow--* ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? *Best Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 https://twitter.com/yanchao727* *My Weibo：http://weibo.com/herewearenow http://weibo.com/herewearenow--* 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 how to know image is really available when reboot? I don't quite understand your question, what do you mean by available? Anyway, before deploying Ironic downloads image from Glance, caches it and just copies to a mounted iSCSI partition (using dd or so). And, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? We have 2 sets of kernel+ramdisk: 1. Deploy k+r: these are used only for deploy process itself to provide iSCSI volume and call back to Ironic. There's ongoing effort to create smarted ramdisk, called Ironic Python Agent, but it's WIP. 2. Your k+r as stated in Glance metadata for an image - they will be used for booting after deployment. Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 stored in flavor metadata, will be stored in node metadata later. And than you have production images that are whatever you want to deploy and they are stored in Glance metadata for the instance image. TFTP configuration should be created automatically, I doubt you should change it anyway. 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 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 21:00 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 how to know image is really available when reboot? I don't quite understand your question, what do you mean by available? Anyway, before deploying Ironic downloads image from Glance, caches it and just copies to a mounted iSCSI partition (using dd or so). And, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? We have 2 sets of kernel+ramdisk: 1. Deploy k+r: these are used only for deploy process itself to provide iSCSI volume and call back to Ironic. There's ongoing effort to create smarted ramdisk, called Ironic Python Agent, but it's WIP. 2. Your k+r as stated in Glance metadata for an image - they will be used for booting after deployment. Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org
Re: [openstack-dev] [ironic workflow question]
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 https://twitter.com/yanchao727* *My Weibo：http://weibo.com/herewearenow http://weibo.com/herewearenow--* 2014-06-04 21:00 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 how to know image is really available when reboot? I don't quite understand your question, what do you mean by available? Anyway, before deploying Ironic downloads image from Glance, caches it and just copies to a mounted iSCSI partition (using dd or so). And, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? We have 2 sets of kernel+ramdisk: 1. Deploy k+r: these are used only for deploy process itself to provide iSCSI volume and call back to Ironic. There's ongoing effort to create smarted ramdisk, called Ironic Python Agent, but it's WIP. 2. Your k+r as stated in Glance metadata for an image - they will be used for booting after deployment. Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 Regards！* *Chao Yan--**My twitter：Andy Yan @yanchao727 https://twitter.com/yanchao727* *My Weibo：http://weibo.com/herewearenow http://weibo.com/herewearenow--* 2014-06-04 21:27 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 stored in flavor metadata, will be stored in node metadata later. And than you have production images that are whatever you want to deploy and they are stored in Glance metadata for the instance image. TFTP configuration should be created automatically, I doubt you should change it anyway. 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 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 21:00 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 how to know image is really available when reboot? I don't quite understand your question, what do you mean by available? Anyway, before deploying Ironic downloads image from Glance, caches it and just copies to a mounted iSCSI partition (using dd or so). And, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? We have 2 sets of kernel+ramdisk: 1. Deploy k+r: these are used only for deploy process itself to provide iSCSI volume and call back to Ironic. There's ongoing effort to create smarted ramdisk, called Ironic Python Agent, but it's WIP. 2. Your k+r as stated in Glance metadata for an image - they will be used for booting after deployment. Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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, 严超 wrote: 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 image to kick start. But in ironic there is no ks.conf pointed in tftp. How do bare metal know which image to install ? Is there any clear workflow where I can read ? Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- ___ OpenStack-dev mailing list
Re: [openstack-dev] [ironic workflow question]
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 boot`, kr are fetched from it's metadata. Deploy kr are currently taken from flavor provided by --flavor argument (this will change eventually). If you're using e.g. DevStack, you don't even touch deploy kr, they're bound to flavor baremetal. Please see quick start guide for hints on this: http://docs.openstack.org/developer/ironic/dev/dev-quickstart.html 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 Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 21:27 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 stored in flavor metadata, will be stored in node metadata later. And than you have production images that are whatever you want to deploy and they are stored in Glance metadata for the instance image. TFTP configuration should be created automatically, I doubt you should change it anyway. 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 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 21:00 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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 how to know image is really available when reboot? I don't quite understand your question, what do you mean by available? Anyway, before deploying Ironic downloads image from Glance, caches it and just copies to a mounted iSCSI partition (using dd or so). And, what are the differences between final kernel (ramdisk) and original kernel (ramdisk) ? We have 2 sets of kernel+ramdisk: 1. Deploy k+r: these are used only for deploy process itself to provide iSCSI volume and call back to Ironic. There's ongoing effort to create smarted ramdisk, called Ironic Python Agent, but it's WIP. 2. Your k+r as stated in Glance metadata for an image - they will be used for booting after deployment. Best Regards！ Chao Yan -- My twitter：Andy Yan @yanchao727 My Weibo：http://weibo.com/herewearenow -- 2014-06-04 19:36 GMT+08:00 Dmitry Tantsur dtant...@redhat.com: 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
Re: [openstack-dev] [ironic workflow question]
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 me if the two sets of r + k should be the same ? The deploy kernel ramdisk are created by diskimage-builder, and contain a small agent used by Ironic when provisioning the node. The user kernel ramdisk must be separate. These should be the same kernel ramdisk contained in the user-specified image, eg. the image you are requesting when issuing nova boot --image $UUID. -Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 me if the two sets of r + k should be the same ? No it should _not_ be the same kernel and ramdisk, the deploy ramdisk is a special ramdisk with a modified init script to help with the deployment of the node[1]. For the image you're deploying you should use it's own ramdisk and kernel, you can take a look at how the load-image script[2] from TripleO extracts the kernel and ramdisk from the image and register everything with Glance. [1] https://github.com/openstack/diskimage-builder/tree/master/elements/deploy-ironic [2] https://github.com/openstack/tripleo-incubator/blob/master/scripts/load-image ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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--* 2014-06-04 22:53 GMT+08:00 Devananda van der Veen devananda@gmail.com: 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 me if the two sets of r + k should be the same ? The deploy kernel ramdisk are created by diskimage-builder, and contain a small agent used by Ironic when provisioning the node. The user kernel ramdisk must be separate. These should be the same kernel ramdisk contained in the user-specified image, eg. the image you are requesting when issuing nova boot --image $UUID. -Devananda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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--* 2014-06-04 23:00 GMT+08:00 Lucas Alvares Gomes lucasago...@gmail.com: 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 me if the two sets of r + k should be the same ? No it should _not_ be the same kernel and ramdisk, the deploy ramdisk is a special ramdisk with a modified init script to help with the deployment of the node[1]. For the image you're deploying you should use it's own ramdisk and kernel, you can take a look at how the load-image script[2] from TripleO extracts the kernel and ramdisk from the image and register everything with Glance. [1] https://github.com/openstack/diskimage-builder/tree/master/elements/deploy-ironic [2] https://github.com/openstack/tripleo-incubator/blob/master/scripts/load-image ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 Weibo：http://weibo.com/herewearenow http://weibo.com/herewearenow--* 2014-06-04 23:00 GMT+08:00 Lucas Alvares Gomes lucasago...@gmail.com: 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 me if the two sets of r + k should be the same ? No it should _not_ be the same kernel and ramdisk, the deploy ramdisk is a special ramdisk with a modified init script to help with the deployment of the node[1]. For the image you're deploying you should use it's own ramdisk and kernel, you can take a look at how the load-image script[2] from TripleO extracts the kernel and ramdisk from the image and register everything with Glance. [1] https://github.com/openstack/diskimage-builder/tree/master/elements/deploy-ironic [2] https://github.com/openstack/tripleo-incubator/blob/master/scripts/load-image ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 backdoor user. Otherwise, just use nova's SSH keypair capability when you deploy your image onto boxes. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ironic workflow question]
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 *disk-image-create *command. Something like *disk-image-create fedora* As Clint said, there is root login from console is disabled. Another alternative is you can use the local-config element while running disk-image-create so that you can do a root login from the system where you build the deploy image. The local-config will add the ssh keys of the current user building the image to the root user on the cloud image. On Thu, Jun 5, 2014 at 10:22 AM, Clint Byrum cl...@fewbar.com wrote: 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 backdoor user. Otherwise, just use nova's SSH keypair capability when you deploy your image onto boxes. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Ramesh ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
