cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4550) [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration work
Date Fri, 30 Aug 2013 16:53:51 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754891#comment-13754891
] 

Prasanna Santhanam commented on CLOUDSTACK-4550:
------------------------------------------------

from Edison via http://markmail.org/message/sh6tzjchlsgs3ojd

The main issue is related to guest network bridge name schema is changed, thus migrate vm,
create new vm will have problem after upgraded to 4.2.
If you are using basic network, then don't need to do the following steps.
The proposed upgrade paths are:
1. Stick to old network name in 4.2. You can set "network.bridge.name.schema=3.0" in /etc/cloudstack/agent/agent.properties
2. Upgrade to new network name schema, need to do the following 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.
      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
The potential issues if you are using above upgrade path 2:
1. If you are using multiple physical bridges, other than the one specified in "guest.network.device"
in /etc/cloudstack/agent/agent.properties, then the vm live migration may have problem.
2. Advanced zone with security group, wont' work.
3. may have old iptables rules left on kvm host, it shouldn't impact guest connectivity though.
                
> [DOC] When upgrading KVM agents to 4.2(.1?) perform bridge renaming to have migration
work
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4550
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4550
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc, KVM, Upgrade
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Assignee: Jessica Tomechak
>            Priority: Critical
>
> See CLOUDSTACK-4405 for the original bug. This is the doc to be prepared as
> part of upgrade in release notes once the fix for the bug is verified to work
> After network bridges being renamed from cloudVirBrVLAN to brem1-VLAN to support the
same VLAN on multiple physical networks the migration of VMs from hosts prior the upgrade
to the ones added after the upgrade will fail. 
> In order to fix this rename the bridges is required to allow migration to work.
> This can be done by running the cloudstack-agent-upgrade script. The original bug is
still undergoing testing, but these are the initial instructions

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message