On 06/23/2011 07:14 PM, Mike Orazi wrote:
On 06/23/2011 11:44 AM, Mo Morsi wrote:
> ---
> recipes/aeolus/templates/deltacloud-core | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/aeolus/templates/deltacloud-core
b/recipes/aeolus/templates/deltacloud-core
> index 0f52b65..56ae9d5 100644
> --- a/recipes/aeolus/templates/deltacloud-core
> +++ b/recipes/aeolus/templates/deltacloud-core
> @@ -16,6 +16,7 @@ PORT="${PORT:-<%= port %>}"
> LOCKFILE="${LOCKFILE:-/var/lock/subsys/deltacloud-<%= name %>
}"
> LOGFILE="${LOGFILE:-/var/log/deltacloud-<%= name %>/$DRIVER.log}"
> PIDFILE="${THIN_PID:-/var/run/deltacloud-<%= name %>.pid}"
> +DELTACLOUD_USER="${DELTACLOUD_USER:-nobody}"
> export DELTACLOUD_MOCK_STORAGE=/usr/lib/ruby/gems/1.8/gems/deltacloud-<%= name
%>-0.3.0/lib/deltacloud/drivers/mock/data/
>
> PROG=/usr/bin/deltacloudd
> @@ -34,7 +35,7 @@ start() {
> exit 0
> fi
>
> - $PROG -i $DRIVER -e $ENV -p $PORT<%= "--provider #{endpoint}" unless
endpoint == "" %> >> $LOGFILE 2>&1&
> + daemon --user $DELTACLOUD_USER $PROG -i $DRIVER -e $ENV -p $PORT<%=
"--provider #{endpoint}" unless endpoint == "" %> >>
$LOGFILE 2>&1&
> RETVAL=$?
> echo $!> $PIDFILE
> if [ $RETVAL -eq 0 ] ; then
ACK. All services start as nobody and did some basic poking at the core
api to ensure it responds as expected. I did not do an end-to-end test
to interact with ec2, etc though.
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel
Actually... While investigating something unrelated, I discovered that
aeolus-cleanup no longer stops the deltacloud services correctly (and
worse yet doesn't report failure, so puppet continues along and actually
removes the templated service files leaving you in a bad spot).
Please fix stop and repost.
My apologies for the confusion.
Thanks,
Mike