[
https://issues.apache.org/jira/browse/CLOUDSTACK-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594380#comment-13594380
]
Marcus Sorensen commented on CLOUDSTACK-1489:
---------------------------------------------
I'd actually defer to the guys who have been working on the packaging. It seems
like it would be distribution specific, and handled by the startup scripts. The
obvious solution to me would be to create a directory, say
/usr/share/cloudstack-agent/plugins, and append that to the classpath in the
init scripts so that the agent can see the plugins copied there. Maybe go a
step further and make a symlink /etc/cloudstack/agent/plugins; easier for
admins to find.
> cloudstack agent plugin classpath is missing
> --------------------------------------------
>
> Key: CLOUDSTACK-1489
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1489
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: pre-4.0.0, 4.0.0, 4.0.1, 4.0.2
> Environment: Linux kvm
> Reporter: Hiroaki Kawai
> Assignee: Marcus Sorensen
>
> There is no place to put plugin jar files for cloudstack agent program now,
> while management server program has default @PLUGINJAVADIR@ where plugin
> classes will be loaded into server at startup. We will need to load a class,
> for example when we try to use a custom "libvirt.vif.driver" which can be
> configured at agent.properties.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
