Hi Chiradeep, Appreciate your feedback. Sure I am ok with creating and running a seperate service. Just to ensure that I got you correctly, so you are saying that the "LogSearchAsAservice" would be queried when required to search for log messages related to a jobid and a seperate API is not called for. Also if the service requires reusing the systemvms, the ACS API layer would be used to start,scaleup,stop the systemvm instances. Also I understand that there are no objections around using the systemvms to host the elasticsearch instance?
Do let me know If there are any differences. Thanks Saurav On Sat, Dec 14, 2013 at 5:07 AM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > Hi Saurav, > It looks like the feature is a little orthogonal to ACS. It is more an > adjunct. The only reason to add an API to CloudStack is to re-use the > authentication layer. Otherwise, the feature does not interact with other > parts of ACS at all. > > If there was a way for a service to re-use the API layer, that would work? > So, the "LogSearchAsaService" service would be exposed on say a different > port, and run as a different app/service/servlet > > On 12/13/13 12:38 PM, "Saurav Lahiri" <saurav.lah...@sungard.com> wrote: > > >Thanks Dan. > > > >All, > >I have added the first draft of Design at the below location. > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/API+to+extract+the+ > >log+statements+by+jobid > > > > > >Thanks > >Saurav > > > > > >On Fri, Dec 13, 2013 at 3:18 PM, Daan Hoogland > ><daan.hoogl...@gmail.com>wrote: > > > >> On Fri, Dec 13, 2013 at 6:21 AM, Saurav Lahiri > >> <saurav.lah...@sungard.com> wrote: > >> > saurav.lahiri > >> > >> > >> is added > >> > >> > > >
