Hello all,
How can i exclude some IP's or some IP ranges from vmnet when creating the VM
network ? Because some IP's are using by some other hosts and gateway/DNS
servers.
# nova network-create vmnet --fixed-range-v4=192.168.11.0/24
--bridge-interface=br100 --multi-host=T --gateway=192.168.11.
Hello,
After adding the br100 bridge via the brctl command, and adding the bridge
interface information, the bridge br100 will disappear.
root@compute1:~# brctl addbr br100
root@compute1:~# cat /etc/network/interfaces|grep -v "#"
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Sorry, i mean the bridge will disappear after reboot.
发件人： 董建华
发送时间： 2013-10-24 14:53
收件人： Openstack >
主题： How to bring br100 up persistently?
Hello,
After adding the br100 bridge via the brctl command, and adding the bridge
interface information, the bridge br100 will disappear.
r
Hi Liu,
Thank you for your response, i'm installing the Havana release on Ubuntu 12.04
LTS, following the DOC "openstack-install-guide-apt-trunk.pdf"，i have not used
Neutron till now.
发件人： Liudong (G)
发送时间： 2013-10-24 17:48
收件人： 董建华; Openstack
主题： 答复: [Openstack] How to exclude
Hi,
i have one controller and two compute nodes, running nova-network, i have
created the following vmnet.
# nova network-create vmnet --fixed-range-v4=192.168.11.0/24
--bridge-interface=br100 --multi-host=T --
gateway=192.168.11.253 --dns1=192.168.11.36 --dns2=192.168.11.24
when i start the C
Hello,
I just installed and configured the cinder services on the controller node.
After attaching a volume to a instance, i clicked the link of the instance
name, the dashborad ceashed, i got the below error messages, however i can
click other instances without issue. Have anybody encountered
13] [error] File
"/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py",
line 637, in instance_volumes_list
[Fri Oct 25 08:02:37 2013] [error] volume_data =
cinderclient(request).volumes.get(volume.id)
[Fri Oct 25 08:02:37 2013] [error
Hello,
Issue resolved after restart appache2 service.
Dongjh
发件人： 董建华
发送时间： 2013-10-25 16:14
收件人： openstack
主题： 回复: The dashboard crash after attaching a volume to a VM
Adding comment.
This is the apache error log.
root@controller:/var/log/apache2# nova volume-attach test1
81554eb2-69c4-45c3
Hello,
I was trying to migrate one instance from the compute node compute2 to another
node compute1, but failed, the nova-compute.log said compute2 failed to connect
the 16509 port on compute1, i noticed that the 16509 port is not opened on
compute1, is there any additional configuration for Li
bvirt# cat /etc/libvirt/libvirtd.conf|grep -v "#"
listen_tcp = 1
tcp_port = "16509"
listen_addr = "10.10.10.182"
unix_sock_group = "libvirtd"
unix_sock_rw_perms = "0770"
auth_unix_ro = "none"
auth_unix_rw = "none"
Not
When doing Live-Migration, the error message said failed to connect
'compute1:16509', compute1 can be resolved to 10.10.10.182 on any node.
发件人： 止语
发送时间： 2013-10-28 16:55
收件人： 董建华; Openstack Milis
主题： 回复： 回复：[Openstack] Nova live-migration failed(libvirt Connection refused)
and I a
Thanks, as you suggested, i uncomment the following line, the daemon can start
now, going to test the Live-Migration.
#listen_tls = 0
发件人： menghuizhanguo
发送时间： 2013-10-28 17:10
收件人： 董建华; openstack
主题： Reply: Re：[Openstack] Nova live-migration failed(libvirt Connection refused)
disable the tls
= "libvirtd"
unix_sock_rw_perms = "0770"
auth_unix_ro = "none"
auth_unix_rw = "none"
Note:10.10.10.182 is the compute node's internal IP.
发件人： 止语
发送时间： 2013-10-28 16:29
收件人： 董建华; Openstack Milis
主题： 回复：[Openstack] Nova live-migration failed(libvirt
问题就是端口没侦听，libvirtd进程都莫有。
发件人： 董建华
发送时间： 2013-10-28 17:05
收件人： 止语; openstack
主题： Re: Re：[Openstack] Nova live-migration failed(libvirt Connection refused)
root@compute1:/etc/default# libvirtd -l -f /etc/libvirt/libvirtd.conf
2013-10-28 09:03:50.514+: 3777: info : libvirt version: 1.1.1
2013-10
directory
发件人： 董建华
发送时间： 2013-10-28 16:59
收件人： 止语; openstack
主题： Re: 回复：[Openstack] Nova live-migration failed(libvirt Connection refused)
When doing Live-Migration, the error message said failed to connect
'compute1:16509', compute1 can be resolved to 10.10.10.182 on any node.
发件人： 止语
failed: Failed to start SASL negotiation: -4 (SASL(-4): no
mechanism available: No worthy mechs found)
发件人： 董建华
发送时间： 2013-10-28 17:22
收件人： 止语; openstack
主题： Re: Reply: Re：[Openstack] Nova live-migration failed(libvirt Connection
refused)
Thanks, as you suggested, i uncomment the following line
Hi,
After VM Live-Migration, i failed to get console-log for the VM, is it normal ?
nova show 737c9b60-a701-4691-aaac-66faf6c2a637|grep hypervisor
| OS-EXT-SRV-ATTR:hypervisor_hostname | compute1
|
root@controller:~# nova console-log 737c9b60-a701
root 0 Oct 29 14:07 console.log
From: Razique Mahroua
Date: 2013-10-29 13:56
To: 董建华
CC: openstack
Subject: Re: [Openstack] Failed to get the VM console-log after Live-Migration
Ok
on the compute node, can you see the file being populated? (console.log within
the instance’ directory)
On Oct 28
: Razique Mahroua
Date: 2013-10-29 13:50
To: 董建华
CC: openstack
Subject: Re: [Openstack] Failed to get the VM console-log after Live-Migration
Hi,
isn’t related to the option « vncserver_proxyclient_address »? in your nova.conf
Not sure about that one…
On Oct 28, 2013, at 19:53, 董建华 wrote:
Hi
I just noticed that the file permission was changed from libvirt-qemu to root,
what caused this problem ?
**
系统服务部董建华
杭州新世纪信息技术股份有限公司
Hangzhou New Century Information Technology Co.,Ltd.
地址：杭州市滨江区南环路3766号
手机：13857132818
TEL：0571
20 matches
Mail list logo
