Ask Your Question

adriansmith's profile - activity

2015-08-05 18:35:11 -0500 received badge  Famous Question (source)
2015-08-05 18:35:11 -0500 received badge  Notable Question (source)
2015-08-05 18:35:11 -0500 received badge  Popular Question (source)
2013-04-05 20:03:50 -0500 answered a question Can't get an X-Storage-Url and X-Auth-Token

The "X-Storage-User" and "X-Storage-Pass" headers are applicable when you're using swauth or tempauth for authentication. It appears you're using Keystone. A request to authenticate to Keystone should look something like this,

curl -d '{ "auth":{ "passwordCredentials":{ "username":"admin", "password":"cloud" }, "tenantName":"admin" }}' -H "Content-type: application/json" http://192.168.224.248:35357/v2.0/tokens

2011-07-11 14:57:45 -0500 answered a question Error while launching RHEL 6 instance

This isn't a solution to your problem but as an alternative to euca-get-console-output you can access the console logs in the file /var/lib/nova/instances/instance-<instance id="">/console.log (on the machine where the instance is running). This might shed some light on what's causing the failure with euca-get-console-output.

2011-07-11 14:40:42 -0500 answered a question After rebooting machines service off and euca- commands don't work

Did you start the nova-api service?

2011-07-11 14:37:19 -0500 answered a question failed to parse error message from AWS EC2Response Error: 403 Forbidden

May be similar problem to question # 164223, i.e. the project file setting the various keys, etc may not have been source'd.

Another possibility is that euca is trying to go through a proxy. Do you have http_proxy and/or https_proxy set? If you do 'unset' them.

2011-07-11 14:33:44 -0500 answered a question 64-vmlinuz-virtual --kernel true i386 Invalid certfailed to upload kernel

Have your source'd your project's env file? e.g.

source /root/creds/novarc

2011-07-07 15:50:44 -0500 answered a question What listen-address should dnsmasq use?

Thanks Vish Ishaya, that solved my question.

2011-07-07 15:07:48 -0500 answered a question What listen-address should dnsmasq use?

That's exactly what I ended up doing Vish.

The machines IP, 192.168.110.10, was the first IP on br100. By deleting it and adding it back in it went to the bottom leaving the gateway address as the first.

ip addr d 192.168.110.10/16 dev br100 ip addr a 192.168.110.10/16 dev br100

The only problem is I need to do this each time I reboot. I'm letting nova do everything itself but it's still not setting up the order of the IPs correctly.

2011-07-07 11:57:52 -0500 answered a question What listen-address should dnsmasq use?

It's ttylinux taken from http://smoser.brickies.net/ubuntu/ttylinux-uec/ (http://smoser.brickies.net/ubuntu/tty...)

2011-06-27 14:43:26 -0500 asked a question What listen-address should dnsmasq use?

Looking at the code it appears that nova uses the network's gateway address as the 'listen-address' for dnsmasq. It get's this gateway address from the database.

In my setup the network is 192.168.42.0/24. This results in nova starting dnsmasq with the listen-address 192.168.42.1.

The dnsmasq processes look like this,

dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=192.168.42.1 --except-interface=lo --dhcp-range=192.168.42.2,static,120s --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro

Using this setup I can see DHCP requests coming in (using tcpdump) but there's no response going out. I'm not sure why dnsmasq doesn't see these packets but as an experiment I changed the 'gateway' in the database to the IP addres of the machine running dnsmasq, i.e. '192.168.110.10'.

After killing all the dnsmasq processes and restarting nova-network here's what dnsmasq looks like,

dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=192.168.110.10 --except-interface=lo --dhcp-range=192.168.42.2,static,120s --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro

Using this setup dnsmasq does return an ip address. Ot at least it appears to. Here's the output of 'tcpdump -i br100 port 67 or 68',

16:28:22.971744 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 02:16:3e:33:52:b8 (oui Unknown), length 280 16:28:22.972356 IP 192.168.42.1.bootps > 192.168.42.4.bootpc: BOOTP/DHCP, Reply, length 315

The problem is the compute node, and hence the VM, isn't receiving this response. I'm not sure is this is due to my messing about with dnsmasq or (more likely) a network issue. In either case I'm stumped.

Any ideas?