Hi Seif, I wonder if it would make sense for you to deploy this as a custom GUI plug-in. I believe the NetApp guys did something like this for their situation, as well.
David La Motta from NetApp might be able to say more (I've included him). Talk to you later, Mike On Tue, Jun 24, 2014 at 1:03 AM, Punith S <punit...@cloudbyte.com> wrote: > hi, > > I am in process of adding a new Add Primary Storage (specific to my > Storage plugin) form whose labels & certain values will be different than > the current Default Provider's Add Primary Storage form. > also looping the GSoC'14 > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Create+GUI+to+add+primary+storage+based+on+plug-ins > > it seems adding more checks and if-else clauses in system.js will make it > more fragile and unmanageable. > > use case: > since each vendor requires to use ui with their own specific params, > > for example with add primary storage: > referring the attachment, popup form will be dynamically changed to have > different params wrt the selected storage providers. > > hence instead of writing the vendor specific code inside system.js(common > file) > is it acceptable to modularize the code to different vendor specific js > files like in writing a third party UI plugin ? > ref - > https://cwiki.apache.org/confluence/display/CLOUDSTACK/UI+Plugin+Tutorial > > thanks > -- > regards, > > punith s > cloudbyte.com > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
