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 013F910B53 for ; Thu, 6 Jun 2013 12:20:22 +0000 (UTC) Received: (qmail 31205 invoked by uid 500); 6 Jun 2013 12:20:21 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 31177 invoked by uid 500); 6 Jun 2013 12:20:21 -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 31051 invoked by uid 500); 6 Jun 2013 12:20:21 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 31044 invoked by uid 99); 6 Jun 2013 12:20:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2013 12:20:21 +0000 Date: Thu, 6 Jun 2013 12:20:20 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-2874) fix the upgrade for the deployment with F5/SRX combination prior to 3.0 release MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676951#comment-13676951 ] ASF subversion and git services commented on CLOUDSTACK-2874: ------------------------------------------------------------- Commit c0d894346a57e61626f332a9ef25efa9b5e77646 in branch refs/heads/master from [~murali.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c0d8943 ] CLOUDSTACK-2874: fix the upgrade for the deployment with F5/SRX combination prior to 3.0 release Fix does following: - add F5 network service provider into a physical network if there if F5 deployed in the zone - add instance of F5 network service provider - add SRX network service provider into a physical network if there if SRX deployed in the zone - add instance of SRX network service provider - upgrade all the guest networks to network offering '"Isolated with external providers" > fix the upgrade for the deployment with F5/SRX combination prior to 3.0 release > ------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2874 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2874 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: pre-4.0.0 > Reporter: Murali Reddy > Assignee: Murali Reddy > Fix For: 4.2.0 > > > Prior to 3.0, deployments had to have combination of F5 and SRX providing load balancing and firewall services if external devices need to be used. So the deployments were either using virtual router providing FW/LB services or F5/SRX combination. > 3.0 introduced notion of network offering and concept of service and service provider. On upgrade, deployments with F5 and SRX, needed to be fit into the network offering and network service and provider paradigm. > Fix should include following > - add F5 network service provider into a physical network if there if F5 deployed in the zone > - add instance of F5 network service provider > - add SRX network service provider into a physical network if there if SRX deployed in the zone > - add instance of SRX network service provider > - upgrade all the guest networks to network offering '"Isolated with external providers" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira