cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hugo Trippaers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-101) OVS support in KVM
Date Wed, 24 Apr 2013 08:43:15 GMT

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

Hugo Trippaers commented on CLOUDSTACK-101:
-------------------------------------------

Hey Angeline,

The name of the bridge is indeed the traffic label in KVM. So in your previous comment you
have br0 as name for the bridge interface. If this bridge is for management traffic you need
to configure the ip address on the bridge, so the typical configuration is as follows:

# The physical interface: eth1 
DEVICE=eth1
BOOTPROTO=none
HWADDR=BC:30:5B:D4:16:3C
IPV6INIT=no
#MTU=1500
NM_CONTROLLED=no
ONBOOT=yes
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br0


# The bridge interface: br0
DEVICE=br0
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR= 10.223.58.195
GATEWAY = 10.223.58.193
NETMASK=255.255.255.192
HOTPLUG=no


With this configurations you will have one bridge 'br0' with one connected port 'eth1'
                
> OVS support in KVM
> ------------------
>
>                 Key: CLOUDSTACK-101
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-101
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: pre-4.0.0, 4.0.0
>            Reporter: Prasanna Santhanam
>            Assignee: Hugo Trippaers
>              Labels: kvm, ovs
>             Fix For: Future
>
>         Attachments: agentlog513.doc, Apache_CloudStack-4 1 0-Installation_Guide-en-US.pdf,
cloudstack-agent-err.docx, cloudstack-agent-out.docx
>
>
> OVS support currently works for XenServer but not in KVM. This is to improve the KVM
agent to support OVS which has been part of the Linux kernel mainline for sometime now.
> Release Planning:
> Dev list discussion: http://markmail.org/thread/x2zncdgac52essxf
> Functional Spec:  unknown
> Feature Branch:  unknown

--
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