Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 20 Dec 2013 22:50:09 +0000 (UTC)
From: "Sheng Yang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12685705.1387496046368.75275.1387579809658@arcas>
In-Reply-To: <JIRA.12685705.1387496046368@arcas>
References: <JIRA.12685705.1387496046368@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-5577) Remote Access VPN and S2S VPN
 should be treated as two seperate services for Network Offering creation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang updated CLOUDSTACK-5577:
-----------------------------------

    Fix Version/s:     (was: 4.3.0)
                   4.4.0

> Remote Access VPN and S2S VPN should be treated as two seperate services for Network Offering creation
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5577
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5577
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Chandan Purushothama
>            Assignee: Sheng Yang
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> Currently we treat RemoteAccessVPN and S2S VPN Service as a single VPN Service on "Create Network Offering" UI box. A VPN Service Provider might not be in a position to support both services. We need to provide the two services in the VPN as two seperate capabilities of VPN Service 


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)