Ask Your Question

yHuKyM's profile - activity

2016-03-01 05:45:19 -0500 received badge  Nice Answer (source)
2015-12-07 10:06:58 -0500 received badge  Necromancer (source)
2015-06-12 01:32:00 -0500 received badge  Famous Question (source)
2015-06-12 01:32:00 -0500 received badge  Notable Question (source)
2015-01-20 18:41:32 -0500 received badge  Popular Question (source)
2015-01-20 08:41:29 -0500 asked a question Neutron router gateway interface is not shown in dashboard

Ubuntu 14.04 + Icehouse Latest neutron and dashboard from Ubuntu repos. Everything is working fine. Though, while looking at router details in the dashboard, the external (Gateway) interface of the router is not shown. image description image description

Router works fine, and the ports can be seen from neutron API:
altadmin@controller-1:~$ neutron router-port-list 51e00b9c-d2b6-40f0-9f24-c4def6459e45

| id  | name | mac_address | fixed_ips |
+--------------------------------------+
| 33d6c4d7-5398-4816-af45-04895764c69a |      | fa:16:3e:47:2a:08 | {"subnet_id": "a529f32c-17df-4a3b-8adf-599b5a603b5b", "ip_address": "1.1.1.1"} |

| 897563e9-55ea-4fad-bf30-3d14c6f17fac |      | fa:16:3e:0a:4e:42 | {"subnet_id": "920edfe4-ab10-4939-970c-19bb360009d2", "ip_address": "192.168.100.1"} |
+--------------------------------------+

It should show both interfaces in the dashboard. What am I missing?
2014-11-27 04:24:13 -0500 received badge  Notable Question (source)
2014-11-27 04:24:13 -0500 received badge  Famous Question (source)
2014-11-27 04:24:13 -0500 received badge  Popular Question (source)
2014-11-12 02:27:09 -0500 received badge  Famous Question (source)
2014-11-05 03:17:35 -0500 received badge  Student (source)
2014-11-05 03:17:19 -0500 received badge  Self-Learner (source)
2014-11-05 03:17:19 -0500 received badge  Teacher (source)
2014-11-04 02:00:15 -0500 received badge  Notable Question (source)
2014-11-04 01:53:35 -0500 commented answer Nova-compute does not work with docker "hypervisor".

That's not it either. Every time (first time included) the service was started with:

sudo service nova-compute restart
2014-11-03 21:20:31 -0500 received badge  Popular Question (source)
2014-11-03 09:03:49 -0500 commented answer Nova-compute does not work with docker "hypervisor".

Not a sollution. Nova-compute is not supposed to need access to libvirt socket, it shouldn't use libvirt at all.

2014-11-03 09:02:10 -0500 answered a question Nova-compute does not work with docker "hypervisor".

It turns out, that there is config file /etc/nova/nova-compute.conf which should also contain:

[DEFAULT]
compute_driver=novadocker.virt.docker.DockerDriver
#[libvirt]
#virt_type=kvm

This has fixed the issue.

2014-11-03 08:23:57 -0500 received badge  Editor (source)
2014-11-03 08:23:25 -0500 asked a question Nova-compute does not work with docker "hypervisor".

I have 2 node setup. One is controller, one is compute. On the compute node I have docker installed as hypervisor, with the appropriate driver. Followed the how-to from here: https://wiki.openstack.org/wiki/Docker I do not want to go the docker-heat way.

I am using Ubuntu 14.04 + Icehouse on both nodes.

This is my /etc/nova/nova.conf on the compute host:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges=True
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
enabled_apis=ec2,osapi_compute,metadata

auth_strategy = keystone
rpc_backend = rabbit
rabbit_host = sta-controller-1
rabbit_password = password
my_ip = 10.248.0.111
vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = 10.248.0.111
novncproxy_base_url = http://192.168.248.8:6080/vnc_auto.html
glance_host = sta-controller-1

compute_driver = novadocker.virt.docker.DockerDriver

scheduler_default_filters = ComputeFilter

[database]
connection = mysql://nova:password@sta-controller-1/nova

[keystone_authtoken]
auth_uri = http://sta-controller-1:5000
auth_host = sta-controller-1
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = nova
admin_password = password

I managed to start a container with "nova boot .....". Then I called it the day. I came back the next morning and was unable to start another container. The nova-compute service was dead, and does not want to start again. It complains about libvirt, and does not want to use docker any more. This is the log:

2014-11-03 15:50:46.644 26436 ERROR nova.virt.libvirt.driver [-] Connection to libvirt failed: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver Traceback (most recent call last):
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 789, in _connect
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver     libvirt.openAuth, uri, auth, flags)
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver   File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 139, in proxy_call
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver     rv = execute(f,*args,**kwargs)
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver   File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 77, in tworker
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver     rv = meth(*args,**kwargs)
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 105, in openAuth
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver     if ret is None:raise libvirtError('virConnectOpenAuth() failed')
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
2014-11-03 15:50:46.644 26436 TRACE nova.virt.libvirt.driver 
2014-11-03 15:50:46.731 26436 ERROR nova.openstack.common.threadgroup [-] Connection to the hypervisor is ...
(more)
2014-09-06 16:28:34 -0500 commented question Instances and 802.3ad layer3 4 link aggregation

Here from IBM, check the last section: http://pic.dhe.ibm.com/infocenter/storwize/unified_ic/index.jsp?topic=%2Fcom.ibm.storwize.v7000.unified.150.doc%2Fmng_t_pub_netw_bondingmodes2_4.html (http://pic.dhe.ibm.com/infocenter/sto...)

2014-09-06 16:20:09 -0500 commented question Instances and 802.3ad layer3 4 link aggregation

Only if there is heavy UDP traffic.

2014-08-28 01:33:57 -0500 received badge  Enthusiast
2014-08-26 02:13:53 -0500 asked a question Icehouse iPXE boot on KVM instances like in Grizzly?

I have two installations one is Grizzly, one is Icehouse. In Grizzly, every instance during boot asks you to optionally press Ctrl-B to boot from the network. In Icehouse, the instance boots straight from the hard drive, without asking for Ctrl-B. I use KVM on both.

How do I make Icehouse instances to ask me for Ctrl-B?