Monitoring scheduling for home gateways

Abstract

Abstract-In simple and monolithic systems such as our current home gateways, monitoring is often overlooked: the home user can only reboot the gateway when there is a problem. In next-generation home gateways, more services will be available (pay-per-view TV, games. . . ) and different actors will provide them. When one service fails, it will be impossible to reboot the gateway without disturbing the other services. We propose a management framework that monitors remote gateways. The framework tests response times for various management activities on the gateway, and provides reference time/performance ratios. The values can be used to establish a management schedule that balances the rate at which queries can be performed with the resulting load that the query will induce locally on the gateway. This allows the manager to tune the ratio between the reactivity of monitoring and its intrusiveness on performance.

Various Extensions for the Ambient OSGi Framework

“…Its simplicity and pragmatism are keys to build efficient run-time systems. The INRIA Amazones team focuses on ambient environments and provides extensions that cope with ambient constraints 8 http://gentoo-wiki.com/Gentoo_on_NSLU2 9 http://www.apache.org/licenses/ 10 http://www.cecill.info/ Table 2: OSGi impacted elements such as limited memory size, remote access, dynamism, context awareness and energy efficiency. Our extensions depend on framework implementations, and as such, they are rather difficult to keep up-to-date with upstream codebase changes.…”

“…If the remote manager asks for the fridge temperature every tenth of a second the gateway can fall in some kind of Denial of Service state and not be able to do other things. We developed a monitoring scheduling process for gateway devices (Frénot et al, 2008) through which we wondered if we could anticipate the increase in CPU load when a new probe is inserted into the gateway. The provided approach is a specific bench generator that measures every installed JMX probe and stores its response time.…”

“…MOSGi Management (Royon & Frénot, 2007;Fleury & Frénot, 2003;Frénot et al, 2008) POSGi Management (Frénot & Royon, 2005) VOSGi Runtime (Royon et al, 2006) Suspend & Resume Runtime (Dunklau & Frénot, 2009) iJVM Runtime (Geoffray et al, 2009) ROCS Runtime (Frénot et al, 2010) AxSel Runtime (Ben Hamida et al, 2008) SFelix Security (Parrend & Frénot, 2006, 2007b Unsecured Bundle Catalog Security (Parrend & Frénot, 2007a, 2008a, 2008c Hardened OSGi Security Geoffray et al, 2009) CBAC Security (Parrend & Frénot, 2008b) Specification implementation. Since iJVM impacts the underlying virtual machine it does not directly concern the OSGi framework.…”