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 02:59:15 GMT

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

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

Hugo:
 questions Pertain to  http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
 :

1.  Preparing the host vefore adding to cloudstack:
  follow line 1  through line 87 of above link which include :
    starting libvirtd, get and install openvswitch, build & install openvswitch, copy
sysconfig files, 

line 89 - 98:

 #create bridge file

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

question:  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?

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 I used 'br0'
DEVICE=br0
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSPort                                                          ??? in the document,
TYPE=
OVS_BRIDGE=br0
BOOTPROTO=static
IPADDR= <Host IPaddress>
GATEWAY = <gateway IPAddress>
NETMASK=255.255.255.0
HOTPLUG=no

> rmmod bridge

> vi /etc/modprobe.d/blacklist.conf    & append following at end of file
blacklist bridge

>  service openvswitch start

>  iptables -A POSTROUTING -o eth0 -j MASQUERADE
> iptables -A INPUT -i ovsbr1 -j ACCEPT
> iptables -A FORWARD -i ovsbr1 -j ACCE
> iptables -I INPUT -p tcp -m tcp --dport 22 -j ACCEPT
> iptables -I INPUT -p tcp -m tcp --dport 1798 -j ACCEPT
> iptables -I INPUT -p tcp -m tcp --dport 16509 -j ACCEPT
> iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
> iptables -I INPUT -p tcp -m tcp --dport 49152:49216  -j ACCEPT
> iptables-save > /etc/sysconfig/iptables
> service iptables save

> vi  /etc/sysconfig/iptables & comment following line

#-A FORWARD -j REJECT --reject-with icmp-host-prohibited

> service iptables restart

> ovs-vsctl add-br   br0                   ???  br0  to match  /etc/sysconfig/network-scripts/ifcfg-br0
 ?

> ovs-vsctl add-port br0 eth1


question:  are above steps in correct order to prepare host before adding host to cloudstack?



2.  Add host to cloudstack



THANKS


   


                
> 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