I think this is a great idea. However 4.2 is closed for new features (as also 4.3).
On 12/2/13 3:23 AM, "Pradeep Cloudstack" <pradeepcloudst...@yahoo.com> wrote: >Hi, >my name is Pradeep HK and I am from Juniper Networks, Bangalore. > >I am leading an effort to implement Cloudstack(based on 4.2) >network-element plugin to orchestrate Juniper's switches. > >As a first-cut, we are focussing on L2 services and we have written a >NetworkGuru. As part of it's implement() method we will: >(1)Create the required logical interfaces on the Juniper switches (EX,QFX) >(2)Create the required VLANs on the Juniper switches (EX,QFX). >(3)Configure VLAN membership on the interfaces > > >Our customers need this plugin in Cloudstack deployments to automatically >orchestrate the Juniper switches to create Virtual Networks. >Without this plugin, there will be a manual intervention needed to >configure the switches (after figuring out the >current configuration of the switch). > >We have a Network Management Platform (called JUNOS SPACE) which is >heavily used by customers to orchestrate Juniper's networking devices. >It also exposes REST-ful APIs for integration with 3rdParty tools. >The proposed Juniper's Cloudstack network-element plugin leverages these >REST-ful APIs to appropriately orchestrate Juniper's switches to >create Virtual Networks > >In that direction, I need: >(1)Your comments/suggestions >(2)For existing deployments of Cloudstack, is there a standard means to >deploy the Plugin ? > >-Pradeep
