Ask Your Question

kesten's profile - activity

2014-04-15 05:57:50 -0600 answered a question compatible versions of centos for Icehouse

Please test the root resizing of your centos image. We found that none of the publically (googleable) centos images for openstack actually re-sized the root partition. Tested by doing a df and fdisk -l on the vms. The results show the same disk size as whatever the image had.

Ubuntu and fedora images did not have this problem.

The problem being that growpart and growroot are either absent, or not correctly working. This has to be done at boot time and can't be fixed up afterwards, so a bad image is basically useless if you want nova boot --flavor flav_id to actually resize the disk to the size specified in flav_id.

Post install you will see an error like this if you try to fix it up. [cloud-user@vm-test1 ~]$ growpart /dev/vda 1 FAILED: unable to determine partition type

Here is a list of all the images that we tested. In the end we had to get a custom image built by our openstack provider. Most of the centos image names are in the table.

root@node-8:~# nova image-list +--------------------------------------+-------------------------------------------------+--------+--------------------------------------+ | ID | Name | Status | Server | +--------------------------------------+-------------------------------------------------+--------+--------------------------------------+ | 13c6aba6956855a | CentOS 6.4 | ACTIVE | | | c68019ae4-8ea2-eb68fe2db306 | CentOS-6.4-x86_64-Minimal-OpenStack.image.qcow2 | ACTIVE | bunzip2 <image_file> | | 98af03df668d3 | Fedora-x86_64-20-20131211.1-sda.qcow2 | ACTIVE | disk resize works | | d7b4d7dbeeba7d | RHEL-6.5 | ACTIVE | | | e31c9bdd-8afc123 | TestVM | ACTIVE | | | ff5ac05b125eb202d | Ubuntu 12.04.3 LTS | ACTIVE | | | eea670ee6edbc4 | centos-6.5-20140117.0.x86_64 | ACTIVE | | | c6f9f78531c2 | centos-6_4-64-vanilla.qcow2 | ACTIVE | | | 1c7fe14cbb3d9e | centos60_x86_64.qcow2 | ACTIVE | | | d11521*31bfe7b | cirros-0.3.1-x86_64-disk.img | ACTIVE | In the official openstack docs |

2013-12-03 16:08:15 -0600 answered a question Openstack installation problem

I had the same error due to savanna.conf having host = 10.0.11.100

my ip address instead of localhost. When I commented out this line

# host = 10.0.11.100

It worked.

That's because a different interface is used (eth0 not loopback in my case) and the url is

echo $SAVANNA_URL

http://localhost:8386/v1.0/f51a9d1948db4940b21d362002761e66

as directed by the savanna quickstart guide.

To check this situation, try telnet localhost 8386 and telnet 10.0.11.100 # replacing with your ip

In my case, i could only connect to the ip not localhost, until I changed the config as mentioned above.

I believe you can either have all urls with your ip and host = ip or all urls localhost with host = localhost #by default or set explicitly

But you cannot mix the two.

2013-08-14 14:55:30 -0600 received badge  Editor (source)
2013-08-14 14:22:27 -0600 answered a question Why does nova-novncproxy blank screen and doesn't connect? - ignoring socket not ready

I have the same issue and, quite oddly, and when I click the "Send Ctrl+Alt+del" button, all of a sudden the console springs into action showing that it was sitting at the login prompt, and then going through the shutdown commands all of which are now visible in the vnc console.

I'm running a centOS6.4 vm spun up from a vmdk image hosted on glance. Openstack controller node is hosted on a dedicated vm server, connecting to it from my mac using firefox 23. The log tab shows "?"

With a cirros vm, the log also shows a correct bootup log, but the console still doesn't work.

It may be as simple as - click on the black console. Start typing. When i do this, the console starts displaying output. Cheeky monkey!

Spoke too soon. The horizon console wasn't working by itself. It needed help. Here's what worked for me.

Use the dashboard to view instances, click on yours. Summary tab. Get the id.
controller $ nova get-vnc-console 1cc5f95b-8793-4ab4-864b-d83b2d742bd7 novnc

+-------+---------------------------------------------------------------------------------+ | Type | Url | +-------+---------------------------------------------------------------------------------+ | novnc | http://10.0.9.170:6080/vnc_auto.html?token=1fc91adb-b20a-4083-9522-b1abcb38ce08 | +-------+---------------------------------------------------------------------------------+

Take the url, put it in a new tab in your browser. Now start typing and your console may work. If you go back to the horizon controlled console, it may now have started to work. If you kill the url from nova, the horizon console may die. Note that if your session dies you may have to go to the instances page, click edit or more. Soft or hard reboot the instance. Generate a new url via nova. Bit clunky.

kesten

2013-08-14 13:48:42 -0600 received badge  Supporter (source)