[
https://issues.apache.org/jira/browse/CLOUDSTACK-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747038#comment-14747038
]
ASF subversion and git services commented on CLOUDSTACK-8625:
-------------------------------------------------------------
Commit 612c7ebf403cdafd3355d8b30f03885cb0f340d6 in cloudstack's branch
refs/heads/master from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=612c7eb ]
CLOUDSTACK-8625: Systemd profile for CloudStack Agent
With CentOS 7 and Ubuntu 16.04 (to be released) using systemd
it is preferred that CloudStack's Agent is also being started using
systemd.
This commit includes a service file for the CloudStack Agent with
a wrapper script which actually executes Java
It no longer uses jsvc for daemonizing and thus this requirement
has also been dropped for CentOS 7 packaging.
The Agent log output to stdout has also been modified to no longer
include the timestamp as this is done by journalctl.
This has been tested on a CentOS 7.1 machine and the Agent starts,
stops and restarts properly.
> Systemd profile for KVM Agent
> -----------------------------
>
> Key: CLOUDSTACK-8625
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8625
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Environment: Ubuntu 16.04, CentOS 7.X
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Labels: agent, kvm, systemd
> Fix For: Future
>
>
> We currently only support sysvinit, but with CentOS and Ubuntu both moving to
> Systemd we should support systemd.
> To do this we can:
> - Loose JSVC
> - Log to stdout and let systemd / journalctl handling the logging
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
