Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of animesh.chaturvedi@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Animesh Chaturvedi <animesh.chaturvedi@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 13 Dec 2012 10:51:45 -0800
Subject: RE: '[PROPOSAL]' Third party plugins
Thread-Topic: '[PROPOSAL]' Third party plugins
Thread-Index: Ac3YwzfRhRr4uQvPRfeTuYL+0tO8PAAmb5tAAAFszXA=
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F45E4@SJCPMAILBOX01.citrite.net>
References: 
 <7914B38A4445B34AA16EB9F1352942F1012F13CC8613@SJCPMAILBOX01.citrite.net>
 <BEAC6B533902CC4DA3D452E248D90613012DDF33DD30@SJCPMAILBOX01.citrite.net>
In-Reply-To: 
 <BEAC6B533902CC4DA3D452E248D90613012DDF33DD30@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Sonny

How does administrator enable/ disable the plugin if it is misbehaving beca=
use of bug or let's say after upgrade?=20

> -----Original Message-----
> From: Fang Wang [mailto:fang.wang@citrix.com]
> Sent: Thursday, December 13, 2012 10:11 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>=20
> I like the idea of the plugin button so users can see all the plugins.
>=20
> -----Original Message-----
> From: Sonny Chhen [mailto:Sonny.Chhen@citrix.com]
> Sent: Wednesday, December 12, 2012 4:01 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Brian Federle; Pranav Saxena
> Subject: '[PROPOSAL]' Third party plugins
>=20
> Hello All,
>=20
> I would like to discuss a new feature that is being worked on for the nex=
t
> release of CloudStack. It is the ability to add third party plugins into
> CloudStack while still utilizing the current ui. The procedure in which t=
his
> would occur is as follows:
>=20
>=20
> 1.       The developer  will write a plugin that they would like to add i=
nto
> CloudStack
>=20
> 2.        Using a predetermined file hierarchy we create, the developer w=
ill
> place their plugin within the folder structure and fill out a plugin.js f=
ile
>=20
> 3.       The admin will then place this folder into the existing CloudSta=
ck
> "plugin"
>=20
> 4.       The admin will then add this new listing onto the plugin.js file=
 that lies
> within that folder
>=20
> 5.       The user then just has to refresh the browser and the plugin wil=
l be
> available to use.
>=20
> We will be toying with the idea of adding a plugin button to the navigati=
on so
> that the user can see what plugins have been installed and click on them =
to
> access them.
>=20
> Please see the link below for more information.
>=20
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>=20
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>=20
> Thoughts, comments, suggestions?
>=20
> Thanks You and Best Regards,
>=20
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA  95054, USA