[openstack-dev] baremetal provisioning
Hi I have noticed that if i generate a baremetal image of 8G, it takes around 20-25 minutes for the deployment. And, the entire disk image is built in the openstack server and then copied over. Isnt this a waste of time and space? Should the image with the 8G (or 30G or 100G, whatever i want) be created in the openstack server, and the whole image copied? Is there any other way, or is there a fix for this? Can we not specify the image size and the image not be created, but /dev/sdx be created during boot time? Thanks Ravi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] baremetal provisioning - issue with image and boot
Hi I am new to baremetal provisioning with openstack. I have followed this link for the setup: https://wiki.openstack.org/wiki/Baremetal I have followed instructions from the above link and generated the vmlinuz and ramdisk images. I loaded these vmlinuz and ramdisk into the baremetal node (server) through dnsmasq and PXE. Few questions: 1 The baremetal node has initramfs but the interfaces are not up and does not have any ip address for the interfaces. Does this mean, the kernel and ramdisk that i extracted using disk-image-create as specified from the above link is wrong? What should is see as the image that boots up? 2 The baremetal agent does not seem to be present in the filesystem on the baremetal node. How should this get loaded/downloaded into the node? Then i ran this command on the openstack controller: nova boot --flavor my-baremetal-flavor --image my-image my-baremetal-node This produces the following error: ERROR: Quota exceeded for instances: Requested 1, but already used 10 of 10 instances (HTTP 413) (Request-ID: req-xxx) Questions: 1 What should i do to get this working? 2 Is the image that is currently present in the baremetal server correct? Greatly appreciate any help and pointers. Thanks Ravi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] baremetal provisioning - issue with image and boot
Hi I am past the quota issue, i increased the quota for the project. Where should i get the kernel and ramdisk for tinycore bootstrap? And how do i download the baremetal agent to the baremetal node? Now when i do nova boot i see the following issue: All nova services are up and working. Thanks Ravi On Fri, Oct 11, 2013 at 3:23 PM, Ravikanth Samprathi rsamp...@gmail.comwrote: Hi I am new to baremetal provisioning with openstack. I have followed this link for the setup: https://wiki.openstack.org/wiki/Baremetal I have followed instructions from the above link and generated the vmlinuz and ramdisk images. I loaded these vmlinuz and ramdisk into the baremetal node (server) through dnsmasq and PXE. Few questions: 1 The baremetal node has initramfs but the interfaces are not up and does not have any ip address for the interfaces. Does this mean, the kernel and ramdisk that i extracted using disk-image-create as specified from the above link is wrong? What should is see as the image that boots up? 2 The baremetal agent does not seem to be present in the filesystem on the baremetal node. How should this get loaded/downloaded into the node? Then i ran this command on the openstack controller: nova boot --flavor my-baremetal-flavor --image my-image my-baremetal-node This produces the following error: ERROR: Quota exceeded for instances: Requested 1, but already used 10 of 10 instances (HTTP 413) (Request-ID: req-xxx) Questions: 1 What should i do to get this working? 2 Is the image that is currently present in the baremetal server correct? Greatly appreciate any help and pointers. Thanks Ravi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
