You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Sonny Chhen <So...@citrix.com> on 2012/12/13 01:01:00 UTC
'[PROPOSAL]' Third party plugins
Hello All,
I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
1. The developer will write a plugin that they would like to add into CloudStack
2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
3. The admin will then place this folder into the existing CloudStack "plugin"
4. The admin will then add this new listing onto the plugin.js file that lies within that folder
5. The user then just has to refresh the browser and the plugin will be available to use.
We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
Please see the link below for more information.
https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
Thoughts, comments, suggestions?
Thanks You and Best Regards,
Sonny H. Chhen
Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
[Chip] For logistical reasons, I'd like to understand what we mean by "being worked on for the next release of CloudStack". Are you saying that you are planning to be code complete by the end of January for the 4.1 feature freeze? Is the coding in-progress? If so, which feature branch is it in?
[Pranav] - The implementation for this feature is just started . We were having some mock discussions between ourselves regarding the basic prototype . Brian is going to create a feature branch for this pretty soon and start the development on that branch. He has a basic prototype working which he's going to push on the feature branch soon and let the community review it and suggest any amendments , if required . This does not seem to be a very huge feature , so we are assuming that we shall be able to code complete it by Jan end for the 4.1 feature freeze.
Regards,
Pranav
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Wednesday, December 12, 2012 9:29 PM
To: cloudstack-dev@incubator.apache.org
Cc: Brian Federle; Pranav Saxena
Subject: Re: '[PROPOSAL]' Third party plugins
On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be available to use.
>
> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>
Thanks for sharing Sonny. I'm +1 on this concept!
For logistical reasons, I'd like to understand what we mean by "being worked on for the next release of CloudStack". Are you saying that you are planning to be code complete by the end of January for the 4.1 feature freeze? Is the coding in-progress? If so, which feature branch is it in?
Thanks!
-chip
Re: '[PROPOSAL]' Third party plugins
Posted by Chip Childers <ch...@sungard.com>.
On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be available to use.
>
> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>
Thanks for sharing Sonny. I'm +1 on this concept!
For logistical reasons, I'd like to understand what we mean by "being
worked on for the next release of CloudStack". Are you saying that
you are planning to be code complete by the end of January for the 4.1
feature freeze? Is the coding in-progress? If so, which feature
branch is it in?
Thanks!
-chip
RE: '[PROPOSAL]' Third party plugins
Posted by Donal Lafferty <do...@citrix.com>.
I should be a bit more clear. I'm talking about categories of plugin, not about whether there will be specific names for each.
Specifically, I'm concerned that the term 'plugin' will get overloaded. If it means too many things, it will be difficult to explain the CloudStack architecture to new comers.
-----Original Message-----
From: Pranav Saxena
Sent: 14 December 2012 1:01 AM
To: cloudstack-dev@incubator.apache.org
Cc: Donal Lafferty
Subject: RE: '[PROPOSAL]' Third party plugins
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 adding a third party plugin to the cloudstack dashboard.
Regards,
Pranav
-----Original Message-----
From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
Sent: Thursday, December 13, 2012 3:53 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: '[PROPOSAL]' Third party plugins
I've a question on terminology.
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'?
DL
-----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
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 .
Regards,
Pranav
-----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
This is a silly question, Do we allow all plugins to have same access role?
OR some plugins have admin access, and some plugins for users only?
Thanks,
-Fang
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
Re: '[PROPOSAL]' Third party plugins
Posted by "jerry jiang. 蒋维" <je...@tyxtech.com>.
I suggest the UI provides a config options for plugins.
like when the UI loaded a specific plugin, then UI would provide options to configure the plugin,
something like, enable/disable, or provide IP address if the plugin is requiring it.
Jerry
----- Original Message -----
From: "Hugo Trippaers" <HT...@schubergphilis.com>
To: cloudstack-dev@incubator.apache.org
Sent: 星期五, 2012年 12 月 14日 下午 9:18:43
Subject: RE: '[PROPOSAL]' Third party plugins
Heya Sonny,
What kind of plugins would this be? I like the idea of being able to extend the ui dynamically, but I fail to see the use case here. Could you give some examples of what kind of plugins would end up using this system?
Cheers,
Hugo
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> Sent: Friday, December 14, 2012 12:59 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> Okay, but I'd like a way of distinguishing in speech and text this new way of
> extending CloudStack from the existing way.
>
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: 14 December 2012 2:05 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: '[PROPOSAL]' Third party plugins
>
> Isn't there a use case for a plugin that has both server and GUI components?
> May be we should keep the name generic.
>
> Thanks
> Animesh
>
> On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pr...@citrix.com>
> wrote:
>
> > 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 adding a third
> party plugin to the cloudstack dashboard.
> >
> > Regards,
> > Pranav
> >
> > -----Original Message-----
> > From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> > Sent: Thursday, December 13, 2012 3:53 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: '[PROPOSAL]' Third party plugins
> >
> > I've a question on terminology.
> >
> > 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'?
> >
> > DL
> >
> >
> > -----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
> >
> > 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 .
> >
> > Regards,
> > Pranav
> >
> > -----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
> >
> > This is a silly question, Do we allow all plugins to have same access role?
> > OR some plugins have admin access, and some plugins for users only?
> >
> > Thanks,
> > -Fang
> >
> > -----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
> >
> > Sonny
> >
> > How does administrator enable/ disable the plugin if it is misbehaving
> because of bug or let's say after upgrade?
> >
> >> -----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
> >>
> >> I like the idea of the plugin button so users can see all the plugins.
> >>
> >> -----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
> >>
> >> Hello All,
> >>
> >> I would like to discuss a new feature that is being worked on for the
> >> next release of CloudStack. It is the ability to add third party
> >> plugins into CloudStack while still utilizing the current ui. The
> >> procedure in which this would occur is as follows:
> >>
> >>
> >> 1. The developer will write a plugin that they would like to add into
> >> CloudStack
> >>
> >> 2. Using a predetermined file hierarchy we create, the developer will
> >> place their plugin within the folder structure and fill out a
> >> plugin.js file
> >>
> >> 3. The admin will then place this folder into the existing CloudStack
> >> "plugin"
> >>
> >> 4. The admin will then add this new listing onto the plugin.js file that
> lies
> >> within that folder
> >>
> >> 5. The user then just has to refresh the browser and the plugin will be
> >> available to use.
> >>
> >> We will be toying with the idea of adding a plugin button to the
> >> navigation so that the user can see what plugins have been installed
> >> and click on them to access them.
> >>
> >> Please see the link below for more information.
> >>
> >>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plu
> >> g
> >> in.jpg
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plug
> >> i
> >> n
> >>
> >> Thoughts, comments, suggestions?
> >>
> >> Thanks You and Best Regards,
> >>
> >> Sonny H. Chhen
> >> Manager of User Interface & User Experience | Citrix Systems -
> >> CloudPlatform
> >> 4988 Great America Parkway, Santa Clara, CA 95054, USA
> >
RE: '[PROPOSAL]' Third party plugins
Posted by Hugo Trippaers <HT...@schubergphilis.com>.
Heya Sonny,
What kind of plugins would this be? I like the idea of being able to extend the ui dynamically, but I fail to see the use case here. Could you give some examples of what kind of plugins would end up using this system?
Cheers,
Hugo
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> Sent: Friday, December 14, 2012 12:59 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> Okay, but I'd like a way of distinguishing in speech and text this new way of
> extending CloudStack from the existing way.
>
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: 14 December 2012 2:05 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: '[PROPOSAL]' Third party plugins
>
> Isn't there a use case for a plugin that has both server and GUI components?
> May be we should keep the name generic.
>
> Thanks
> Animesh
>
> On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pr...@citrix.com>
> wrote:
>
> > 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 adding a third
> party plugin to the cloudstack dashboard.
> >
> > Regards,
> > Pranav
> >
> > -----Original Message-----
> > From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> > Sent: Thursday, December 13, 2012 3:53 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: '[PROPOSAL]' Third party plugins
> >
> > I've a question on terminology.
> >
> > 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'?
> >
> > DL
> >
> >
> > -----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
> >
> > 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 .
> >
> > Regards,
> > Pranav
> >
> > -----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
> >
> > This is a silly question, Do we allow all plugins to have same access role?
> > OR some plugins have admin access, and some plugins for users only?
> >
> > Thanks,
> > -Fang
> >
> > -----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
> >
> > Sonny
> >
> > How does administrator enable/ disable the plugin if it is misbehaving
> because of bug or let's say after upgrade?
> >
> >> -----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
> >>
> >> I like the idea of the plugin button so users can see all the plugins.
> >>
> >> -----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
> >>
> >> Hello All,
> >>
> >> I would like to discuss a new feature that is being worked on for the
> >> next release of CloudStack. It is the ability to add third party
> >> plugins into CloudStack while still utilizing the current ui. The
> >> procedure in which this would occur is as follows:
> >>
> >>
> >> 1. The developer will write a plugin that they would like to add into
> >> CloudStack
> >>
> >> 2. Using a predetermined file hierarchy we create, the developer will
> >> place their plugin within the folder structure and fill out a
> >> plugin.js file
> >>
> >> 3. The admin will then place this folder into the existing CloudStack
> >> "plugin"
> >>
> >> 4. The admin will then add this new listing onto the plugin.js file that
> lies
> >> within that folder
> >>
> >> 5. The user then just has to refresh the browser and the plugin will be
> >> available to use.
> >>
> >> We will be toying with the idea of adding a plugin button to the
> >> navigation so that the user can see what plugins have been installed
> >> and click on them to access them.
> >>
> >> Please see the link below for more information.
> >>
> >>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plu
> >> g
> >> in.jpg
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plug
> >> i
> >> n
> >>
> >> Thoughts, comments, suggestions?
> >>
> >> Thanks You and Best Regards,
> >>
> >> Sonny H. Chhen
> >> Manager of User Interface & User Experience | Citrix Systems -
> >> CloudPlatform
> >> 4988 Great America Parkway, Santa Clara, CA 95054, USA
> >
RE: '[PROPOSAL]' Third party plugins
Posted by Donal Lafferty <do...@citrix.com>.
Okay, but I'd like a way of distinguishing in speech and text this new way of extending CloudStack from the existing way.
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
Sent: 14 December 2012 2:05 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: '[PROPOSAL]' Third party plugins
Isn't there a use case for a plugin that has both server and GUI components? May be we should keep the name generic.
Thanks
Animesh
On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pr...@citrix.com> wrote:
> 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 adding a third party plugin to the cloudstack dashboard.
>
> Regards,
> Pranav
>
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> Sent: Thursday, December 13, 2012 3:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> I've a question on terminology.
>
> 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'?
>
> DL
>
>
> -----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
>
> 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 .
>
> Regards,
> Pranav
>
> -----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
>
> This is a silly question, Do we allow all plugins to have same access role?
> OR some plugins have admin access, and some plugins for users only?
>
> Thanks,
> -Fang
>
> -----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
>
> Sonny
>
> How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
>
>> -----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
>>
>> I like the idea of the plugin button so users can see all the plugins.
>>
>> -----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
>>
>> Hello All,
>>
>> I would like to discuss a new feature that is being worked on for the
>> next release of CloudStack. It is the ability to add third party
>> plugins into CloudStack while still utilizing the current ui. The
>> procedure in which this would occur is as follows:
>>
>>
>> 1. The developer will write a plugin that they would like to add into
>> CloudStack
>>
>> 2. Using a predetermined file hierarchy we create, the developer will
>> place their plugin within the folder structure and fill out a
>> plugin.js file
>>
>> 3. The admin will then place this folder into the existing CloudStack
>> "plugin"
>>
>> 4. The admin will then add this new listing onto the plugin.js file that lies
>> within that folder
>>
>> 5. The user then just has to refresh the browser and the plugin will be
>> available to use.
>>
>> We will be toying with the idea of adding a plugin button to the
>> navigation so that the user can see what plugins have been installed
>> and click on them to access them.
>>
>> Please see the link below for more information.
>>
>> https://cwiki.apache.org/confluence/download/attachments/30744936/plu
>> g
>> in.jpg
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plug
>> i
>> n
>>
>> Thoughts, comments, suggestions?
>>
>> Thanks You and Best Regards,
>>
>> Sonny H. Chhen
>> Manager of User Interface & User Experience | Citrix Systems -
>> CloudPlatform
>> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>
Re: '[PROPOSAL]' Third party plugins
Posted by Animesh Chaturvedi <an...@citrix.com>.
Isn't there a use case for a plugin that has both server and GUI components? May be we should keep the name generic.
Thanks
Animesh
On Dec 13, 2012, at 5:08 PM, "Pranav Saxena" <pr...@citrix.com> wrote:
> 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 adding a third party plugin to the cloudstack dashboard.
>
> Regards,
> Pranav
>
> -----Original Message-----
> From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
> Sent: Thursday, December 13, 2012 3:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> I've a question on terminology.
>
> 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'?
>
> DL
>
>
> -----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
>
> 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 .
>
> Regards,
> Pranav
>
> -----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
>
> This is a silly question, Do we allow all plugins to have same access role?
> OR some plugins have admin access, and some plugins for users only?
>
> Thanks,
> -Fang
>
> -----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
>
> Sonny
>
> How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
>
>> -----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
>>
>> I like the idea of the plugin button so users can see all the plugins.
>>
>> -----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
>>
>> Hello All,
>>
>> I would like to discuss a new feature that is being worked on for the
>> next release of CloudStack. It is the ability to add third party
>> plugins into CloudStack while still utilizing the current ui. The
>> procedure in which this would occur is as follows:
>>
>>
>> 1. The developer will write a plugin that they would like to add into
>> CloudStack
>>
>> 2. Using a predetermined file hierarchy we create, the developer will
>> place their plugin within the folder structure and fill out a
>> plugin.js file
>>
>> 3. The admin will then place this folder into the existing CloudStack
>> "plugin"
>>
>> 4. The admin will then add this new listing onto the plugin.js file that lies
>> within that folder
>>
>> 5. The user then just has to refresh the browser and the plugin will be
>> available to use.
>>
>> We will be toying with the idea of adding a plugin button to the
>> navigation so that the user can see what plugins have been installed
>> and click on them to access them.
>>
>> Please see the link below for more information.
>>
>> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
>> in.jpg
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
>> n
>>
>> Thoughts, comments, suggestions?
>>
>> Thanks You and Best Regards,
>>
>> Sonny H. Chhen
>> Manager of User Interface & User Experience | Citrix Systems -
>> CloudPlatform
>> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
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 adding a third party plugin to the cloudstack dashboard.
Regards,
Pranav
-----Original Message-----
From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
Sent: Thursday, December 13, 2012 3:53 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: '[PROPOSAL]' Third party plugins
I've a question on terminology.
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'?
DL
-----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
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 .
Regards,
Pranav
-----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
This is a silly question, Do we allow all plugins to have same access role?
OR some plugins have admin access, and some plugins for users only?
Thanks,
-Fang
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Donal Lafferty <do...@citrix.com>.
I've a question on terminology.
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'?
DL
-----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
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 .
Regards,
Pranav
-----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
This is a silly question, Do we allow all plugins to have same access role?
OR some plugins have admin access, and some plugins for users only?
Thanks,
-Fang
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
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 .
Regards,
Pranav
-----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
This is a silly question, Do we allow all plugins to have same access role?
OR some plugins have admin access, and some plugins for users only?
Thanks,
-Fang
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Fang Wang <fa...@citrix.com>.
This is a silly question, Do we allow all plugins to have same access role?
OR some plugins have admin access, and some plugins for users only?
Thanks,
-Fang
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
No , the UI just needs to be refreshed . There is no need to restart management server.
Regards,
Pranav
-----Original Message-----
From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
Sent: Thursday, December 13, 2012 11:39 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: '[PROPOSAL]' Third party plugins
Does this require reboot of the management server?
> -----Original Message-----
> From: Pranav Saxena [mailto:pranav.saxena@citrix.com]
> Sent: Thursday, December 13, 2012 11:16 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> Animesh ,
>
> We have a config .js file for maintaining the list of plugin ID's .
> We use the plugin ID to load the plugin into the cloudstack UI . In
> case , a plugin 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 dashboard and it would seem as if the plugin does not exist at all.
>
> Regards,
> Pranav
>
> -----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
>
> Sonny
>
> How does administrator enable/ disable the plugin if it is misbehaving
> because of bug or let's say after upgrade?
>
> > -----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
> >
> > I like the idea of the plugin button so users can see all the plugins.
> >
> > -----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
> >
> > Hello All,
> >
> > I would like to discuss a new feature that is being worked on for
> > the next release of CloudStack. It is the ability to add third party
> > plugins into CloudStack while still utilizing the current ui. The
> > procedure in which this would occur is as follows:
> >
> >
> > 1. The developer will write a plugin that they would like to add into
> > CloudStack
> >
> > 2. Using a predetermined file hierarchy we create, the developer will
> > place their plugin within the folder structure and fill out a
> > plugin.js file
> >
> > 3. The admin will then place this folder into the existing CloudStack
> > "plugin"
> >
> > 4. The admin will then add this new listing onto the plugin.js file that lies
> > within that folder
> >
> > 5. The user then just has to refresh the browser and the plugin will be
> > available to use.
> >
> > We will be toying with the idea of adding a plugin button to the
> > navigation so that the user can see what plugins have been installed
> > and click on them to access them.
> >
> > Please see the link below for more information.
> >
> >
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> > in.jpg
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> > n
> >
> > Thoughts, comments, suggestions?
> >
> > Thanks You and Best Regards,
> >
> > Sonny H. Chhen
> > Manager of User Interface & User Experience | Citrix Systems -
> > CloudPlatform
> > 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Animesh Chaturvedi <an...@citrix.com>.
Does this require reboot of the management server?
> -----Original Message-----
> From: Pranav Saxena [mailto:pranav.saxena@citrix.com]
> Sent: Thursday, December 13, 2012 11:16 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: '[PROPOSAL]' Third party plugins
>
> Animesh ,
>
> We have a config .js file for maintaining the list of plugin ID's . We use the
> plugin ID to load the plugin into the cloudstack UI . In case , a plugin 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 dashboard and it
> would seem as if the plugin does not exist at all.
>
> Regards,
> Pranav
>
> -----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
>
> Sonny
>
> How does administrator enable/ disable the plugin if it is misbehaving
> because of bug or let's say after upgrade?
>
> > -----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
> >
> > I like the idea of the plugin button so users can see all the plugins.
> >
> > -----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
> >
> > Hello All,
> >
> > I would like to discuss a new feature that is being worked on for the
> > next release of CloudStack. It is the ability to add third party
> > plugins into CloudStack while still utilizing the current ui. The
> > procedure in which this would occur is as follows:
> >
> >
> > 1. The developer will write a plugin that they would like to add into
> > CloudStack
> >
> > 2. Using a predetermined file hierarchy we create, the developer will
> > place their plugin within the folder structure and fill out a
> > plugin.js file
> >
> > 3. The admin will then place this folder into the existing CloudStack
> > "plugin"
> >
> > 4. The admin will then add this new listing onto the plugin.js file that lies
> > within that folder
> >
> > 5. The user then just has to refresh the browser and the plugin will be
> > available to use.
> >
> > We will be toying with the idea of adding a plugin button to the
> > navigation so that the user can see what plugins have been installed
> > and click on them to access them.
> >
> > Please see the link below for more information.
> >
> >
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> > in.jpg
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> > n
> >
> > Thoughts, comments, suggestions?
> >
> > Thanks You and Best Regards,
> >
> > Sonny H. Chhen
> > Manager of User Interface & User Experience | Citrix Systems -
> > CloudPlatform
> > 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
Animesh ,
We have a config .js file for maintaining the list of plugin ID's . We use the plugin ID to load the plugin into the cloudstack UI . In case , a plugin 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 dashboard and it would seem as if the plugin does not exist at all.
Regards,
Pranav
-----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
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the
> next release of CloudStack. It is the ability to add third party
> plugins into CloudStack while still utilizing the current ui. The
> procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a
> plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the
> navigation so that the user can see what plugins have been installed
> and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Animesh Chaturvedi <an...@citrix.com>.
Sonny
How does administrator enable/ disable the plugin if it is misbehaving because of bug or let's say after upgrade?
> -----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
>
> I like the idea of the plugin button so users can see all the plugins.
>
> -----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
>
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the next
> release of CloudStack. It is the ability to add third party plugins into
> CloudStack while still utilizing the current ui. The procedure in which this
> would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into
> CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will
> place their plugin within the folder structure and fill out a plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack
> "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies
> within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be
> available to use.
>
> We will be toying with the idea of adding a plugin button to the navigation so
> that the user can see what plugins have been installed and click on them to
> access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plug
> in.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugi
> n
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems -
> CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
RE: '[PROPOSAL]' Third party plugins
Posted by Fang Wang <fa...@citrix.com>.
I like the idea of the plugin button so users can see all the plugins.
-----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
Hello All,
I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
1. The developer will write a plugin that they would like to add into CloudStack
2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
3. The admin will then place this folder into the existing CloudStack "plugin"
4. The admin will then add this new listing onto the plugin.js file that lies within that folder
5. The user then just has to refresh the browser and the plugin will be available to use.
We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
Please see the link below for more information.
https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
Thoughts, comments, suggestions?
Thanks You and Best Regards,
Sonny H. Chhen
Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
4988 Great America Parkway, Santa Clara, CA 95054, USA
Re: '[PROPOSAL]' Third party plugins
Posted by Chip Childers <ch...@sungard.com>.
On Sun, Feb 10, 2013 at 01:02:57PM +0530, Pranav Saxena wrote:
> Moved both of them to 4.2.
Thanks, Pranav!
-chip
RE: '[PROPOSAL]' Third party plugins
Posted by Pranav Saxena <pr...@citrix.com>.
Moved both of them to 4.2.
Thanks,
Pranav
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Saturday, February 09, 2013 3:13 AM
To: Brian Federle
Cc: David Nalley; cloudstack-dev@incubator.apache.org; Sonny Chhen
Subject: Re: '[PROPOSAL]' Third party plugins
On Fri, Feb 08, 2013 at 01:31:36PM -0800, Brian Federle wrote:
> The code is pretty much ready, I am just doing preliminary testing of it before I merge down. I should have it complete and in master by beginning of next week, including a basic tutorial on how to implement/install UI plugins.
>
> Thanks,
> Brian
Hi Brian. I see that both the jira record and the design wiki page are listing 4.1 as the release. Can you move them to 4.2 please?
>
> On Feb 8, 2013, at 1:21 PM, David Nalley <da...@gnsa.us> wrote:
>
> > Sonny: et al:
> >
> > I see work going on in the ui-plugins feature branch that I assume
> > is where this work is happening for this. What is the current status
> > of this work?
> >
> > Thanks,
> >
> > --David
> >
> > On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
> >> Hello All,
> >>
> >> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
> >>
> >>
> >> 1. The developer will write a plugin that they would like to add into CloudStack
> >>
> >> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
> >>
> >> 3. The admin will then place this folder into the existing CloudStack "plugin"
> >>
> >> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
> >>
> >> 5. The user then just has to refresh the browser and the plugin will be available to use.
> >>
> >> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
> >>
> >> Please see the link below for more information.
> >>
> >> https://cwiki.apache.org/confluence/download/attachments/30744936/p
> >> lugin.jpg
> >>
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Pl
> >> ugin
> >>
> >> Thoughts, comments, suggestions?
> >>
> >> Thanks You and Best Regards,
> >>
> >> Sonny H. Chhen
> >> Manager of User Interface & User Experience | Citrix Systems -
> >> CloudPlatform
> >> 4988 Great America Parkway, Santa Clara, CA 95054, USA
> >>
>
>
Re: '[PROPOSAL]' Third party plugins
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Feb 08, 2013 at 01:31:36PM -0800, Brian Federle wrote:
> The code is pretty much ready, I am just doing preliminary testing of it before I merge down. I should have it complete and in master by beginning of next week, including a basic tutorial on how to implement/install UI plugins.
>
> Thanks,
> Brian
Hi Brian. I see that both the jira record and the design wiki page are
listing 4.1 as the release. Can you move them to 4.2 please?
>
> On Feb 8, 2013, at 1:21 PM, David Nalley <da...@gnsa.us> wrote:
>
> > Sonny: et al:
> >
> > I see work going on in the ui-plugins feature branch that I assume is
> > where this work is happening for this. What is the current status of
> > this work?
> >
> > Thanks,
> >
> > --David
> >
> > On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
> >> Hello All,
> >>
> >> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
> >>
> >>
> >> 1. The developer will write a plugin that they would like to add into CloudStack
> >>
> >> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
> >>
> >> 3. The admin will then place this folder into the existing CloudStack "plugin"
> >>
> >> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
> >>
> >> 5. The user then just has to refresh the browser and the plugin will be available to use.
> >>
> >> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
> >>
> >> Please see the link below for more information.
> >>
> >> https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
> >>
> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
> >>
> >> Thoughts, comments, suggestions?
> >>
> >> Thanks You and Best Regards,
> >>
> >> Sonny H. Chhen
> >> Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
> >> 4988 Great America Parkway, Santa Clara, CA 95054, USA
> >>
>
>
Re: '[PROPOSAL]' Third party plugins
Posted by Brian Federle <Br...@citrix.com>.
The code is pretty much ready, I am just doing preliminary testing of it before I merge down. I should have it complete and in master by beginning of next week, including a basic tutorial on how to implement/install UI plugins.
Thanks,
Brian
On Feb 8, 2013, at 1:21 PM, David Nalley <da...@gnsa.us> wrote:
> Sonny: et al:
>
> I see work going on in the ui-plugins feature branch that I assume is
> where this work is happening for this. What is the current status of
> this work?
>
> Thanks,
>
> --David
>
> On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
>> Hello All,
>>
>> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
>>
>>
>> 1. The developer will write a plugin that they would like to add into CloudStack
>>
>> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
>>
>> 3. The admin will then place this folder into the existing CloudStack "plugin"
>>
>> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
>>
>> 5. The user then just has to refresh the browser and the plugin will be available to use.
>>
>> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
>>
>> Please see the link below for more information.
>>
>> https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
>>
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
>>
>> Thoughts, comments, suggestions?
>>
>> Thanks You and Best Regards,
>>
>> Sonny H. Chhen
>> Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
>> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>>
Re: '[PROPOSAL]' Third party plugins
Posted by David Nalley <da...@gnsa.us>.
Sonny: et al:
I see work going on in the ui-plugins feature branch that I assume is
where this work is happening for this. What is the current status of
this work?
Thanks,
--David
On Wed, Dec 12, 2012 at 7:01 PM, Sonny Chhen <So...@citrix.com> wrote:
> Hello All,
>
> I would like to discuss a new feature that is being worked on for the next release of CloudStack. It is the ability to add third party plugins into CloudStack while still utilizing the current ui. The procedure in which this would occur is as follows:
>
>
> 1. The developer will write a plugin that they would like to add into CloudStack
>
> 2. Using a predetermined file hierarchy we create, the developer will place their plugin within the folder structure and fill out a plugin.js file
>
> 3. The admin will then place this folder into the existing CloudStack "plugin"
>
> 4. The admin will then add this new listing onto the plugin.js file that lies within that folder
>
> 5. The user then just has to refresh the browser and the plugin will be available to use.
>
> We will be toying with the idea of adding a plugin button to the navigation so that the user can see what plugins have been installed and click on them to access them.
>
> Please see the link below for more information.
>
> https://cwiki.apache.org/confluence/download/attachments/30744936/plugin.jpg
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/3rd+Party+Plugin
>
> Thoughts, comments, suggestions?
>
> Thanks You and Best Regards,
>
> Sonny H. Chhen
> Manager of User Interface & User Experience | Citrix Systems - CloudPlatform
> 4988 Great America Parkway, Santa Clara, CA 95054, USA
>