Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of animesh.chaturvedi@citrix.com
 designates 66.165.176.63 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 18:04:34 -0800
Subject: Re: '[PROPOSAL]' Third party plugins
Thread-Topic: '[PROPOSAL]' Third party plugins
Thread-Index: Ac3Zn19bBIi9XxeCQd2Ip8bx4VMrBg==
Message-ID: <64D66868-B128-4B24-9FEF-E3A3DE948995@citrix.com>
References: 
 <7914B38A4445B34AA16EB9F1352942F1012F13CC8613@SJCPMAILBOX01.citrite.net>
 <BEAC6B533902CC4DA3D452E248D90613012DDF33DD30@SJCPMAILBOX01.citrite.net>
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F45E4@SJCPMAILBOX01.citrite.net>
 <BEAC6B533902CC4DA3D452E248D90613012DDF33DD85@SJCPMAILBOX01.citrite.net>
 <67EF18FDCA335F489B366120481AB6C5F6B38A352D@BANPMAILBOX01.citrite.net>
 <81A73678E76EA642801C8F2E4823AD21012F0D628F29@LONPMAILBOX01.citrite.net>
 <67EF18FDCA335F489B366120481AB6C5F6B38A3530@BANPMAILBOX01.citrite.net>
In-Reply-To: 
 <67EF18FDCA335F489B366120481AB6C5F6B38A3530@BANPMAILBOX01.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

Isn't there a use case for a plugin that has both server and  GUI component=
s? May be we should keep the name generic.=20

Thanks
Animesh

On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pranav.saxena@citrix.com> wro=
te:

> Yeah , we can pick  different names for each plugin . I am not sure if we=
'll keep a specific format for the naming . All what is required is mapping=
 to a  unique ID associated with that plugin which would take care of addin=
g a third party plugin to the cloudstack dashboard.
>=20
> Regards,
> Pranav
>=20
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]=20
> Sent: Thursday, December 13, 2012 3:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>=20
> I've a question on terminology.
>=20
> Are these 'GUI plugins' going to use the same component.xml class loader =
as existing plugins?  If not, can we pick different names for each approach=
 to providing a plugin?  E.g. 'GUI plugins' and 'driver plugins'?
>=20
> DL
>=20
>=20
> -----Original Message-----
> From: Pranav Saxena [mailto:pranav.saxena@citrix.com]
> Sent: 13 December 2012 10:22 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>=20
> Currently , we haven't discussed access based scenario for a plugin . But=
 yes , this won't be a tough thing to incorporate. We can enable /disable a=
 UI plugin based on admin or a normal user .
>=20
> Regards,
> Pranav
>=20
> -----Original Message-----
> From: Fang Wang [mailto:fang.wang@citrix.com]
> Sent: Thursday, December 13, 2012 11:46 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>=20
> This is a silly question, Do we allow all plugins to have same access rol=
e? =20
> OR some plugins have admin access, and some plugins for users only?=20
>=20
> Thanks,
> -Fang
>=20
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Thursday, December 13, 2012 10:52 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>=20
> Sonny
>=20
> How does administrator enable/ disable the plugin if it is misbehaving be=
cause of bug or let's say after upgrade?=20
>=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=20
>> next release of CloudStack. It is the ability to add third party=20
>> plugins into CloudStack while still utilizing the current ui. The=20
>> procedure in which this would occur is as follows:
>>=20
>>=20
>> 1.       The developer  will write a plugin that they would like to add =
into
>> CloudStack
>>=20
>> 2.        Using a predetermined file hierarchy we create, the developer =
will
>> place their plugin within the folder structure and fill out a=20
>> plugin.js file
>>=20
>> 3.       The admin will then place this folder into the existing CloudSt=
ack
>> "plugin"
>>=20
>> 4.       The admin will then add this new listing onto the plugin.js fil=
e that lies
>> within that folder
>>=20
>> 5.       The user then just has to refresh the browser and the plugin wi=
ll be
>> available to use.
>>=20
>> We will be toying with the idea of adding a plugin button to the=20
>> navigation so that the user can see what plugins have been installed=20
>> 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 -=20
>> CloudPlatform
>> 4988 Great America Parkway, Santa Clara, CA  95054, USA
>=20