Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 25 Feb 2014 20:32:21 +0000 (UTC)
From: "Jessica Wang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12696903.1393243180523.103252.1393360341458@arcas>
In-Reply-To: <JIRA.12696903.1393243180523@arcas>
References: <JIRA.12696903.1393243180523@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-6162) support OVS as connectivity
 service provider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6162?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jessica Wang updated CLOUDSTACK-6162:
-------------------------------------

    Attachment: jessica-2014-02-25B.PNG

> support OVS as connectivity service provider
> --------------------------------------------
>
>                 Key: CLOUDSTACK-6162
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-616=
2
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.3.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.3.0
>
>         Attachments: jessica-2014-02-25.PNG, jessica-2014-02-25B.PNG
>
>
> Below UI changes are needed to enable OVS as connectivity provider while =
creating network offering.
> Below changes are required:
> 1) In the drop down box for 'Connectivity' service provider in the networ=
k offering dialog box, expose Ovs as provider. And corresponding API call w=
ould be:
> http://192.168.20.112:8080/client/api?command=3DcreateNetworkOffering&ses=
sionkey=3D0YutiBb19VkXgepJYf/wq2Wii4Q=3D&name=3Dovs-connectivity-offering&d=
isplayText=3Dovs-connectivity-offering&guestIpType=3DIsolated&lbType=3Dpubl=
icLb&servicecapabilitylist[0].service=3DSourceNat&servicecapabilitylist[0].=
capabilitytype=3DSupportedSourceNatTypes&servicecapabilitylist[0].capabilit=
yvalue=3Dperaccount&servicecapabilitylist[1].service=3Dlb&servicecapability=
list[1].capabilitytype=3DSupportedLbIsolation&servicecapabilitylist[1].capa=
bilityvalue=3Ddedicated&availability=3DOptional&egresspolicy=3DALLOW&state=
=3DCreating&status=3DCreating&allocationstate=3DCreating&supportedServices=
=3DDhcp,Dns,Firewall,Lb,SourceNat,StaticNat,PortForwarding,Connectivity&spe=
cifyIpRanges=3Dfalse&specifyVlan=3Dfalse&isPersistent=3Dfalse&conservemode=
=3Dfalse&serviceProviderList[0].service=3DDhcp&serviceProviderList[0].provi=
der=3DVirtualRouter&serviceProviderList[1].service=3DDns&serviceProviderLis=
t[1].provider=3DVirtualRouter&serviceProviderList[2].service=3DFirewall&ser=
viceProviderList[2].provider=3DVirtualRouter&serviceProviderList[3].service=
=3DLb&serviceProviderList[3].provider=3DVirtualRouter&serviceProviderList[4=
].service=3DSourceNat&serviceProviderList[4].provider=3DVirtualRouter&servi=
ceProviderList[5].service=3DStaticNat&serviceProviderList[5].provider=3DVir=
tualRouter&serviceProviderList[6].service=3DPortForwarding&serviceProviderL=
ist[6].provider=3DVirtualRouter&serviceProviderList[7].service=3DConnectivi=
ty&serviceProviderList[7].provider=3DOvs&egressdefaultpolicy=3Dtrue&traffic=
type=3DGUEST
> Notice 'serviceProviderList[7].service=3DConnectivity&serviceProviderList=
[7].provider=3DOvs&' in the api fired.
> 2) in the list of network service providers on a physical network display=
 OVS
> 3) enable OVS provider


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)