Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11FFED0D4 for ; Thu, 13 Dec 2012 19:47:00 +0000 (UTC) Received: (qmail 46584 invoked by uid 500); 13 Dec 2012 19:46:59 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 46506 invoked by uid 500); 13 Dec 2012 19:46:59 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 46498 invoked by uid 99); 13 Dec 2012 19:46:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 19:46:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of fang.wang@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 19:46:51 +0000 X-IronPort-AV: E=Sophos;i="4.84,275,1355097600"; d="scan'208";a="599466" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Dec 2012 19:46:30 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Thu, 13 Dec 2012 11:46:29 -0800 From: Fang Wang To: "cloudstack-dev@incubator.apache.org" Date: Thu, 13 Dec 2012 11:46:28 -0800 Subject: RE: '[PROPOSAL]' Third party plugins Thread-Topic: '[PROPOSAL]' Third party plugins Thread-Index: Ac3YwzfRhRr4uQvPRfeTuYL+0tO8PAAmb5tAAAFszXAAAe0OkA== Message-ID: References: <7914B38A4445B34AA16EB9F1352942F1012F13CC8613@SJCPMAILBOX01.citrite.net> <7A92FF96DF135843B4B608FB576BFC3E012DA27F45E4@SJCPMAILBOX01.citrite.net> In-Reply-To: <7A92FF96DF135843B4B608FB576BFC3E012DA27F45E4@SJCPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org This is a silly question, Do we allow all plugins to have same access role?= =20 OR some plugins have admin access, and some plugins for users only?=20 Thanks, -Fang -----Original Message----- From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]=20 Sent: Thursday, December 13, 2012 10:52 AM To: cloudstack-dev@incubator.apache.org Subject: RE: '[PROPOSAL]' Third party plugins 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=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 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=20 > plugin.js file >=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=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