cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou" <>
Subject Re: Review Request 13992: (CLOUDSTACK-4405) additional patch for bridge name and firewall rules issues after KVM upgrade to 4.2
Date Mon, 09 Sep 2013 08:09:13 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Sept. 9, 2013, 8:09 a.m.)

Review request for cloudstack and edison su.


(3) change rpm and debian packaging to support automatic update (c1-c4)

Testing ok in CentOS and Ubuntu installation.


Repository: cloudstack-git


There still exist two issues after Edison's commits.
(1) Migration from new hosts to old hosts failed.
The bridge name on old host is set to cloudVirBr* if is set to
3.0 in /etc/cloudstack/agent/, but the actual bridge name is breth*-* after
running cloudstack-agent-upgrade.

(2) all ports of vms (Basic zone, or Advanced zone with security groups) on old hosts are
open, because the iptables rules are binding to device (bridge) name which is changed by cloudstack-agent-upgrade.

Diffs (updated)

  agent/bindir/ 4972d39 
  debian/cloudstack-agent.postinst 499ae6a 
  debian/rules 5e3d58c 
  packaging/centos63/cloud.spec 2b814f8 
  plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/ e3779a7

  scripts/vm/network/ 0ac8b74 



tested ok on my environment.

After this, the KVM upgrade steps :
a. Install 4.2 cloudstack agent on each kvm host 
b. Run "cloudstack-agent-upgrade". This script will upgrade all the existing bridge name to
new bridge name, and update related firewall rules.
       c. install a libvirt hook:
            c1. mkdir /etc/libvirt/hooks
            c2. cp /usr/share/cloudstack-agent/lib/libvirtqemuhook /etc/libvirt/hooks/qemu
            c3. chmod +x /etc/libvirt/hooks/qemu
            c4. service libvirtd restart
            c5. service cloudstack-agent restart


Wei Zhou

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message