Daan,
I see your point and do agree that it does have benefits. I will go ahead
with user template approach.
Thanks and wishing you and other cloudstackers a happy new year.
Thanks
Saurav
On Fri, Jan 3, 2014 at 2:21 PM, Daan Hoogland wrote:
> Saurav, I do not object against using the systemvm.
Saurav, I do not object against using the systemvm. It seems
inconvenient to me, that's all. If you have your own template you can
deploy your add-on recardless of the underlying ACS. Maybe I am being
over paranoid so don't take my reaction as -1 or such.
happy new year,
On Thu, Jan 2, 2014 at 2:
Daan,
Appreciate your feedback.
To clarify, yes the plans based on an earlier suggestion by chiradeep is to
go ahead
and provide a logsearch service which will be available to be used
optionally.
The service by itself would not require any changes to the cloudstack core
and
could be made available
Saurav,
I do appreciate the cause you are championing but is this to be part
of the cloudstack core? shouldn't this functionality be an add-on that
can be optionally installed (using it's own template)?
regards,
On Mon, Dec 30, 2013 at 8:38 AM, Saurav Lahiri
wrote:
> Hi,
> I am currently lookin
Hi,
I am currently looking into cloudstack-3471 , wiki link beolw.
(
https://cwiki.apache.org/confluence/display/CLOUDSTACK/API+to+extract+the+log+statements+by+jobid
).
As part of it I was was planning on deploying and using default system vms
to host
the logstash+elasticsearch indexing/searching
