cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giebner, Sascha" <Sascha.Gieb...@bautzen-it.de>
Subject RE: distribution of Cloudstack API plugins
Date Thu, 12 Nov 2015 09:34:36 GMT
thx a lot Mika and Marcus, I will check that out.

________________________________________
From: Mike Tutkowski [mike.tutkowski@solidfire.com]
Sent: Wednesday, November 11, 2015 9:18 PM
To: dev@cloudstack.apache.org
Subject: Re: distribution of Cloudstack API plugins

The fact that that annotation can be used instead of commands.properties is
not included in my video, as I had learned about that after that
presentation, so it's great you pointed it out as it does make the work of
installing an API plug-in easier. :)

On Wed, Nov 11, 2015 at 1:15 PM, Marcus <shadowsor@gmail.com> wrote:

> I have found managing commands.properties pretty painful, so figuring that
> out was a huge relief.
>
> On Wed, Nov 11, 2015 at 11:32 AM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
> > Good point, Marcus - thanks!
> >
> > On Wed, Nov 11, 2015 at 12:30 PM, Marcus <shadowsor@gmail.com> wrote:
> >
> > > Note you don't have to edit commands.properties if your API command has
> > the
> > > APICommand annotation:
> > >
> > > @APICommand(name = "getTimeOfDay",
> > >
> > >             description = "get time of day",
> > >
> > >             responseView = ResponseView.Restricted,
> > >
> > >             responseObject = GetTimeOfDayResponse.class,
> > >
> > >             authorized = {RoleType.Admin})
> > >
> > > On Wed, Nov 11, 2015 at 11:26 AM, Mike Tutkowski <
> > > mike.tutkowski@solidfire.com> wrote:
> > >
> > > > It sounds like you've already developed your API plug-in, so perhaps
> > this
> > > > video won't be super useful to you, but - just in case - here's my
> > > > presentation on this topic from the CloudStack Collaboration
> Conference
> > > in
> > > > Dublin, which took place last month:
> > > >
> > > >
> > > >
> > >
> >
> https://www.youtube.com/watch?v=J6N1sf43psw&list=PLGeM09tlguZSeNyOyQKJHNX4pxgK-yoTA&index=8
> > > >
> > > > On Wed, Nov 11, 2015 at 12:23 PM, Mike Tutkowski <
> > > > mike.tutkowski@solidfire.com> wrote:
> > > >
> > > > > No problem. There's actually very little for the customer to do:
> > > > >
> > > > > *Add to commands.properties (located in
> > > > > /usr/share/cloudstack-management/webapps/client/WEB-INF/classes).
> > (The
> > > > > vendor can provide these lines (API command = permission level) to
> > > you.)*
> > > > >
> > > > > *Place the new JAR file in
> > > > > /usr/share/cloudstack-management/webapps/client/WEB-INF/lib.*
> > > > >
> > > > > *Reboot the management server.*
> > > > >
> > > > > On Wed, Nov 11, 2015 at 8:56 AM, Giebner, Sascha <
> > > > > Sascha.Giebner@bautzen-it.de> wrote:
> > > > >
> > > > >> Hey Mike,
> > > > >>
> > > > >> thanks for the hint. Would you mind sharing these instructions
> with
> > > me?
> > > > ;)
> > > > >>
> > > > >> Thx and best regards,
> > > > >> Sascha
> > > > >> ________________________________________
> > > > >> From: Mike Tutkowski [mike.tutkowski@solidfire.com]
> > > > >> Sent: Wednesday, November 11, 2015 3:25 PM
> > > > >> To: dev@cloudstack.apache.org
> > > > >> Subject: Re: distribution of Cloudstack API plugins
> > > > >>
> > > > >> What I have always done is build the JAR file myself and then
> > provide
> > > to
> > > > >> the third party instructions on where it goes (and that to make
> use
> > of
> > > > it,
> > > > >> it does require a reboot of the management server).
> > > > >>
> > > > >> On Wed, Nov 11, 2015 at 6:54 AM, Giebner, Sascha <
> > > > >> Sascha.Giebner@bautzen-it.de> wrote:
> > > > >>
> > > > >> > Hello everyone,
> > > > >> >
> > > > >> > I have a question: After successfully implementing a Cloudstack
> > API
> > > > >> plugin
> > > > >> > (no UI plugin), how would one go about sharing the results
with
> a
> > > > third
> > > > >> > party?
> > > > >> >
> > > > >> > Is the only way to add the changes and rebuild cloudstack?
> > > > >> >
> > > > >> > Or is there a possibility to somehow package a plugin and
add it
> > > > >> > dynamically to a running cloudstack instance?
> > > > >> >
> > > > >> > Or in general what would be the easiest way to prepare a
plugin
> > for
> > > a
> > > > >> > simple end-user-installation?
> > > > >> >
> > > > >> > Thx a bunch,
> > > > >> > Sascha Giebner
> > > > >> >
> > > > >> > --
> > > > >> > This email was Virus checked by UTM 9. http://www.sophos.com
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> *Mike Tutkowski*
> > > > >> *Senior CloudStack Developer, SolidFire Inc.*
> > > > >> e: mike.tutkowski@solidfire.com
> > > > >> o: 303.746.7302
> > > > >> Advancing the way the world uses the cloud
> > > > >> <http://solidfire.com/solution/overview/?video=play>*™*
> > > > >>
> > > > >> --
> > > > >> This email was Virus checked by UTM 9. http://www.sophos.com
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > *Mike Tutkowski*
> > > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > > e: mike.tutkowski@solidfire.com
> > > > > o: 303.746.7302
> > > > > Advancing the way the world uses the cloud
> > > > > <http://solidfire.com/solution/overview/?video=play>*™*
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutkowski*
> > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > e: mike.tutkowski@solidfire.com
> > > > o: 303.746.7302
> > > > Advancing the way the world uses the cloud
> > > > <http://solidfire.com/solution/overview/?video=play>*™*
> > > >
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=play>*™*
> >
>



--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*

Mime
View raw message