cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-2874) fix the upgrade for the deployment with F5/SRX combination prior to 3.0 release
Date Thu, 06 Jun 2013 12:22:19 GMT

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

Murali Reddy resolved CLOUDSTACK-2874.
--------------------------------------

    Resolution: Fixed
    
> 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

Mime
View raw message