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 32299EDFB for ; Thu, 13 Dec 2012 19:16:41 +0000 (UTC) Received: (qmail 36016 invoked by uid 500); 13 Dec 2012 19:16:40 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 35979 invoked by uid 500); 13 Dec 2012 19:16:40 -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 35971 invoked by uid 99); 13 Dec 2012 19:16:40 -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:16:40 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pranav.saxena@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 19:16:32 +0000 X-IronPort-AV: E=Sophos;i="4.84,275,1355097600"; d="scan'208";a="68150" Received: from banpmailmx01.citrite.net ([10.103.128.73]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 13 Dec 2012 19:16:10 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX01.citrite.net ([10.103.128.73]) with mapi; Fri, 14 Dec 2012 00:46:08 +0530 From: Pranav Saxena To: "cloudstack-dev@incubator.apache.org" Date: Fri, 14 Dec 2012 00:45:38 +0530 Subject: RE: '[PROPOSAL]' Third party plugins Thread-Topic: '[PROPOSAL]' Third party plugins Thread-Index: Ac3YwzfRhRr4uQvPRfeTuYL+0tO8PAAmb5tAAAFszXAAAMomgA== Message-ID: <67EF18FDCA335F489B366120481AB6C5F6B38A3525@BANPMAILBOX01.citrite.net> 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 Animesh ,=20 We have a config .js file for maintaining the list of plugin ID's . We us= e the plugin ID to load the plugin into the cloudstack UI . In case , a pl= ugin is misbehaving all one needs to do is comment out the plugin ID in the= config.js file .This would not load the plugin on to the cloudstack dashbo= ard and it would seem as if the plugin does not exist at all.=20 Regards, Pranav -----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