[jira] [Commented] (CLOUDSTACK-6162) support OVS as connectivity service provider

["Jessica Wang (JIRA)" <ji...@apache.org>]

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

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

Murali,

I'll implement 2) and 3).

But about 1),
The Service Provider dropdown is generated automatically from listSupportedNetworkServices API response.
It's NOT hardcoding in UI code.
So, you need to change listSupportedNetworkServices API to include 'Ovs' in "provider" property in "Connectivity" service.

http://10.215.3.26:8080/client/api?command=listSupportedNetworkServices&response=json&sessionkey=wrKVUYCILGdhbWeSKfZRuOafDRU%3D&_=1393267914850

{
    "listsupportednetworkservicesresponse": {
        "count": 13,
        "networkservice": [            
            ~ ~ ~ 
            {
                "name": "Connectivity",
                "provider": [
                    {
                        "name": "StratosphereSsp",
                        "canenableindividualservice": true
                    },
                    {
                        "name": "MidoNet",
                        "canenableindividualservice": true
                    },
                    {
                        "name": "NiciraNvp",
                        "canenableindividualservice": true
                    }
                ],
                "capability": []
            },
            ~ ~ ~ 
        ]
    }
}

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
>             Fix For: 4.3.0
>
>
> 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)