ubuntu@node-4:~/openstack$ cloud-publish-tarball ./ubuntu-12.04-beta1-server-cloudimg->amd64.tar.gz images
Mon Sep 30 09:18:20 UTC 2013: ====== extracting image ======
Warning: no ramdisk found, assuming '--ramdisk none'
kernel : precise-server-cloudimg-amd64-vmlinuz-virtual
ramdisk: none
image : precise-server-cloudimg-amd64.img
Mon Sep 30 09:18:36 UTC 2013: ====== bundle/upload kernel ======
failed to upload bundle to images/precise-server-cloudimg-amd64-vmlinuz-virtual.manifest.xml
failed: euca-upload-bundle --bucket images --manifest /tmp/cloud-publish-image.eRhmYU/precise-server-cloudimg-amd64-vmlinuz-virtual.manifest.xml
S3_URL not specified. Trying http://localhost:8773/services/Walrus
Checking bucket: images
[Errno 111] Connection refusedfailed to upload kernel
como consertar isso?
Eu nunca usei tarball de publicação na nuvem; Eu geralmente uso diretamente as ferramentas CLI para criar imagens no OpenStack:
glance image-create --name ubuntu-12.04 --file precise-server-cloudimg-amd64-disk1.img --is-public True --disk-format qcow2 --container-format bare --property architecture=x86_64
Os arquivos -disk1.img do cloud-images.ubuntu.com são inicializáveis no OpenStack sem fornecer um kernel / initrd separado, etc ...