cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angeline shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-101) OVS support in KVM
Date Tue, 23 Apr 2013 17:31:15 GMT

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

angeline shen commented on CLOUDSTACK-101:
------------------------------------------

Continuing from previous question.  Let me clarify question about line 89-98 due to some typos:

line 89 - 98:

 #create bridge file

   vi /etc/sysconfig/network-scripts/ifcfg-ovsbr1 ......

question: 
1. Does part of bridge filename after the '-' in ifcfg-ovsbr1 , that is 'ovsbr1' need to match
with physical interface used in ovs-vsctl commands which are to be executed later after 'service
openvswitch start' is executed?

2. Must bridge filename be 'ifcfg-ovsbr1'  or can it be named ifcfg-<anything>  as long
as cloudstack UI
     'KVM traffic label'    use the same <anything> as label?

For example, if bridge filename is 'ifcfg-ovsbr1',  then 'ovsbr1' is must  be used in cloudstack
UI 
 public network 'KVM traffic label',   guest network 'KVM traffic label',  management network
'KVM traffic label'  ?


For example if eth1 is physical nic, content of /etc/sysconfig/network-scripts/ifcfg-eth1
is:

DEVICE=eth1
BOOTPROTO=none
HWADDR=BC:30:5B:D4:16:3C
IPV6INIT=no
#MTU=1500
NM_CONTROLLED=yes
ONBOOT=yes
TYPE=Ethernet
UUID="0142ba15-de11-499c-a1ba-82837b30f890"
IPADDR=10.223.58.195
NETMASK=255.255.255.192
GATEWAY=10.223.58.193
DNS1=10.223.110.254
USERCTL=yes
IPV4_FAILURE_FATAL=yes
DEFROUTE=yes
NAME="System eth1"


> vi /etc/sysconfig/network-scripts/ifcfg-br0                ??? here if I use 'br0'  
instead of 'ovsbr1'
DEVICE=br0
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSPort                                                       ??? in document, TYPE=OVSBridge
OVS_BRIDGE=br0
BOOTPROTO=static
IPADDR= 10.223.58.195                                            ??? same as ifcfg-eth1 above
GATEWAY = 10.223.58.193                                       ??? same as ifcfg-eth1 above
NETMASK=255.255.255.192                                     ??? same as ifcfg-eth1 above
HOTPLUG=no


Then     'ovsbr1' is to be used in cloudstack UI  public network 'KVM traffic label', 
         guest network 'KVM traffic label',  management network 'KVM traffic label'    ?

                
> 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