stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Isuru Haththotuwa <isu...@apache.org>
Subject Re: Convention for including Puppet forge's modules in Stratos
Date Sun, 03 Aug 2014 16:24:01 GMT
On Sun, Aug 3, 2014 at 9:17 PM, Akila Ravihansa Perera <ravihansa@wso2.com>
wrote:

> Hi Imesh,
>
> > Not exactly. If required we can send the ports at the subscription time
> > using payload parameters (if the instance can configure them
> accordingly).
>
> Could you please explain how this can be done? I don't see any payload
> parameter field in current cartridge subscription request json
> structure in [1].
>
> >>
> >> Monitoring the health would also be difficult.
> >
> > What's problem we have here? We should be able to monitor the sockets I
> > guess.
>
> Currently we are not periodically monitoring the sockets in cartridge
> instances that are being opened by the application running on it.
> Cartridge agent will do a one-time check on specified ports in
> cartridge deployment json. This does not guarantee the health of the
> application running on cartridge instance.
>
> Also I don't think checking whether ports are active is a good method
> of measuring application health. IMHO, we should provide a agent
> extension for this since health checking logic depends on the nature
> of the application running on the instance.
>
Checking the whether the relevant ports are active is a very simple but a
useful way of health checking. IMHO this can be the default way, while it
should be extendable to support any other logic depending on the
application.

>
>
> [1]
> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Subscribing+to+a+Cartridge
>
> Thanks.
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>

Mime
View raw message