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

Jessica Wang commented on CLOUDSTACK-6162:
------------------------------------------

Murali,

I've checked in UI change for 2) and 3).
(as in my attachment "jessica-2014-02-25")

However, I'm unable to test it because of lack of your server-side change (i.e. 
listNetworkServiceProviders API to return "OVS" provider.). As you can see in 
my attachment "jessica_2014-02-25B", detail view of OVS is empty because API 
doesn't return anything:
http://10.215.3.26:8080/client/api?command=listNetworkServiceProviders&physicalnetworkid=cead3415-8350-4f0f-a94b-4db5a60a9909&name=OVS&response=json&sessionkey=XhIpbU2eaiC47iml%2BHCTmZJA9vg%3D&_=1393360114012
{
    "listnetworkserviceprovidersresponse": {}
}

Jessica

> 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 
> default.) 
>    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 network 
> offering dialog box, expose Ovs as provider. And corresponding API call would 
> be:
> http://192.168.20.112:8080/client/api?command=createNetworkOffering&sessionkey=0YutiBb19VkXgepJYf/wq2Wii4Q=&name=ovs-connectivity-offering&displayText=ovs-connectivity-offering&guestIpType=Isolated&lbType=publicLb&servicecapabilitylist[0].service=SourceNat&servicecapabilitylist[0].capabilitytype=SupportedSourceNatTypes&servicecapabilitylist[0].capabilityvalue=peraccount&servicecapabilitylist[1].service=lb&servicecapabilitylist[1].capabilitytype=SupportedLbIsolation&servicecapabilitylist[1].capabilityvalue=dedicated&availability=Optional&egresspolicy=ALLOW&state=Creating&status=Creating&allocationstate=Creating&supportedServices=Dhcp,Dns,Firewall,Lb,SourceNat,StaticNat,PortForwarding,Connectivity&specifyIpRanges=false&specifyVlan=false&isPersistent=false&conservemode=false&serviceProviderList[0].service=Dhcp&serviceProviderList[0].provider=VirtualRouter&serviceProviderList[1].service=Dns&serviceProviderList[1].provider=VirtualRouter&serviceProviderList[2].service=Firewall&serviceProviderList[2].provider=VirtualRouter&serviceProviderList[3].service=Lb&serviceProviderList[3].provider=VirtualRouter&serviceProviderList[4].service=SourceNat&serviceProviderList[4].provider=VirtualRouter&serviceProviderList[5].service=StaticNat&serviceProviderList[5].provider=VirtualRouter&serviceProviderList[6].service=PortForwarding&serviceProviderList[6].provider=VirtualRouter&serviceProviderList[7].service=Connectivity&serviceProviderList[7].provider=Ovs&egressdefaultpolicy=true&traffictype=GUEST
> Notice 
> 'serviceProviderList[7].service=Connectivity&serviceProviderList[7].provider=Ovs&'
>  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)

Reply via email to