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 <daan.hoogl...@gmail.com>wrote: > 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:48 PM, Saurav Lahiri <saurav.lah...@sungard.com> > wrote: > > 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 through a bunch of python scripts in addition to > > the required > > packages. > > > > Post the previous discussion I believed that there was no objection > against > > using the > > system vm template. But if there are concerns around this then we can > keep > > it open to > > any linux template or the default centOS template. > > > > I understand that hosting templates with all the packages prebuilt into > > would not be > > an option considering that cloudstack does not host templates (other than > > the > > default and systevm). Do let me know if thats not the case and > > download.cloud.com can > > indeed host different types of templates. > > > > Thanks > > Saurav > > > > > > > > > > On Tue, Dec 31, 2013 at 3:26 PM, Daan Hoogland <daan.hoogl...@gmail.com > >wrote: > > > >> 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 > >> <saurav.lah...@sungard.com> wrote: > >> > 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 layer. After a bit of > >> > investigation it > >> > appears that in cloudstack currently there is no way to deploy and > start > >> > default > >> > system vms. Is that correct. If thats the case I am proposing a root > >> admin > >> > API to > >> > deploy a default system vm. The idea is that this system vm can be > used > >> to > >> > host > >> > additional add on services by installing additional tools/packages as > >> > required. > >> > For eg: for the logsearchservice , the api should first deploy and > start > >> > default > >> > system vm , then additional configuration scripts will install and > >> > configure the > >> > (logstash and elasticsearch). This would be convenient for > >> admininstrators > >> > and > >> > they can start querying cloudstack logs by jobid without requiring to > >> > download > >> > additional templates or worry about other dependencies like java. . > The > >> > existing > >> > mechanism of using ssh port 3922 and link local ip address for > >> > communication > >> > with the system vm would still stand. > >> > > >> > Would greatly appreciate feedback/suggestions on this proposal. > >> > > >> > Thanks > >> > Saurav > >> > >> > >
