[
https://issues.apache.org/jira/browse/CLOUDSTACK-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559386#comment-13559386
]
Murali Reddy commented on CLOUDSTACK-655:
-----------------------------------------
moved to 4.2.
> framework for CloudStack to orchestrate virtual network appliances to provide
> network services
> ----------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-655
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-655
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
>
> With the availability of virtual network appliances that can provide L2-L7
> network services from multiple vendors its desirable to have a framework
> through which support for virtual network appliances can be integrated.
> Main requirement would be to orchestrate provisioning the network appliance
> as VM from the template. Current Virtual Network appliance manager which
> actually orchestrates spinning up virtual router, can be generalised to
> provide abstract implementation of virtual network appliance provisioning.
> Then specific implementation for virtual router, Vyatta, NetScaler VPX etc
> can be extended out of abstract implementation.
> Also, CloudStack will need a driver model for server resources that
> implements hypervisor support, so that network appliance specific logic to
> add nic's, bridge, configure IP address etc can be plugged-in to hypervisor
> specific resource layer.
> Apart from providing framework, I would like use this framework and add
> support for provisioning NetScaler VPX as network appliance providing EIP/ELB
> service to the guest network in the advanced zone.
> Release Planning:
> Dev list discussion: http://markmail.org/message/lx6tyikvmvd6wix4
> Functional spec: unknown
> Feature branch: unknown
--
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
