Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B04510D55 for ; Mon, 24 Feb 2014 12:00:26 +0000 (UTC) Received: (qmail 31890 invoked by uid 500); 24 Feb 2014 12:00:25 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 31683 invoked by uid 500); 24 Feb 2014 12:00:24 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 31668 invoked by uid 500); 24 Feb 2014 12:00:23 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 31659 invoked by uid 99); 24 Feb 2014 12:00:23 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 12:00:23 +0000 Date: Mon, 24 Feb 2014 12:00:23 +0000 (UTC) From: "Murali Reddy (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-6162) support OVS as connectivity service provider MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Murali Reddy created CLOUDSTACK-6162: ---------------------------------------- Summary: support OVS as connectivity service provider Key: CLOUDSTACK-6162 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6162 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the defa= ult.) Affects Versions: 4.3.0 Reporter: Murali Reddy Fix For: 4.3.0 Below UI changes are needed to enable OVS as connectivity provider while cr= eating network offering. Below changes are required: 1) In the drop down box for 'Connectivity' service provider in the network = offering dialog box, expose Ovs as provider. And corresponding API call wou= ld be: http://192.168.20.112:8080/client/api?command=3DcreateNetworkOffering&sessi= onkey=3D0YutiBb19VkXgepJYf/wq2Wii4Q=3D&name=3Dovs-connectivity-offering&dis= playText=3Dovs-connectivity-offering&guestIpType=3DIsolated&lbType=3Dpublic= Lb&servicecapabilitylist[0].service=3DSourceNat&servicecapabilitylist[0].ca= pabilitytype=3DSupportedSourceNatTypes&servicecapabilitylist[0].capabilityv= alue=3Dperaccount&servicecapabilitylist[1].service=3Dlb&servicecapabilityli= st[1].capabilitytype=3DSupportedLbIsolation&servicecapabilitylist[1].capabi= lityvalue=3Ddedicated&availability=3DOptional&egresspolicy=3DALLOW&state=3D= Creating&status=3DCreating&allocationstate=3DCreating&supportedServices=3DD= hcp,Dns,Firewall,Lb,SourceNat,StaticNat,PortForwarding,Connectivity&specify= IpRanges=3Dfalse&specifyVlan=3Dfalse&isPersistent=3Dfalse&conservemode=3Dfa= lse&serviceProviderList[0].service=3DDhcp&serviceProviderList[0].provider= =3DVirtualRouter&serviceProviderList[1].service=3DDns&serviceProviderList[1= ].provider=3DVirtualRouter&serviceProviderList[2].service=3DFirewall&servic= eProviderList[2].provider=3DVirtualRouter&serviceProviderList[3].service=3D= Lb&serviceProviderList[3].provider=3DVirtualRouter&serviceProviderList[4].s= ervice=3DSourceNat&serviceProviderList[4].provider=3DVirtualRouter&serviceP= roviderList[5].service=3DStaticNat&serviceProviderList[5].provider=3DVirtua= lRouter&serviceProviderList[6].service=3DPortForwarding&serviceProviderList= [6].provider=3DVirtualRouter&serviceProviderList[7].service=3DConnectivity&= serviceProviderList[7].provider=3DOvs&egressdefaultpolicy=3Dtrue&traffictyp= e=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 O= VS 3) enable OVS provider -- This message was sent by Atlassian JIRA (v6.1.5#6160)