Homeproj: Redmine for CESNET: Issueshttps://homeproj.cesnet.cz/https://homeproj.cesnet.cz/httpauth-login/favicon.ico?16194486082018-11-18T15:02:32ZHomeproj: Redmine for CESNET
Redmine Mentat - Feature #4447 (New): System status monitor should also report on warden-filer statushttps://homeproj.cesnet.cz/issues/44472018-11-18T15:02:32ZRadko Krkoškrkos@cesnet.cz
<p>As was detected during the recent PostgreSQL upgrade to 11.x on <code>mentat-hub</code>, Mentat system-status monitor does not take the warden_filer_{receiver,sender} status into consideration.<br />At least the receiver is a critical system component in current system architecture and should be monitored in my opinion.</p>
<p>(The actual problem was caused by missing write rights for the mentat user on <code>/var/run/warden_filer/</code>, so the <code>.pid</code> files could not have been created - the directory was owned by <code>root</code> instead of <code>mentat</code>).</p> Mentat - Feature #4386 (New): PGP signing of reportshttps://homeproj.cesnet.cz/issues/43862018-10-19T13:00:21ZPavel Káchaph@cesnet.cz
<p>There should be a possibility for report mails to be signed by verifiable PGP key.</p>
<p>(Issue from Dubovice.)</p> Mentat - Feature #4273 (New): Consider/choose/implement different communication protocolhttps://homeproj.cesnet.cz/issues/42732018-08-21T09:20:38ZPavel Káchaph@cesnet.cz
<p>Filer communication protocol serves well and is simple enough. However it has its limitations and might make sense to pursue different direction, so this issue is meant for review/discussion. Also, this need not necessarily mean complete replacement, Mentat can happily support multiple protocols for different situations if that makes sense.</p>
<p>Filer protocol deficiencies:</p>
<ul>
<li>too big or too many events may hit disk and cause trashing because of interference between different daemon queues and db disk access</li>
<li>does not support inter-machine communication (ok, not easily)</li>
<li>although easy, is nonstandard</li>
</ul>
<p>New chosen protocol(s) should:</p>
<ul>
<li>be memory based to prevent potential disk trashing</li>
<li>support both efficient local and network communication</li>
<li>be at least somewhat standard</li>
<li>be comparatively performing to current solution</li>
<li>broker (if applicable/used) should be small and lightweight, based on sane language/platform</li>
</ul> Mentat - Task #4241 (New): Improve documentation for Mentat modules/daemonshttps://homeproj.cesnet.cz/issues/42412018-08-02T07:59:58ZJan Machjan.mach@cesnet.cz
<p>Current documentation of Mentat`s real-time and post-processing modules could be improved. Not much work went into that so far, so any improvement will be a big step forward.</p> Mentat - Feature #4218 (Waiting): Hawat: Improve system status view modulehttps://homeproj.cesnet.cz/issues/42182018-07-27T14:29:29ZJan Machjan.mach@cesnet.cz
<p>There is a lot of potential in system status module in Hawat and a lot of room for improvements. Start with displaying processing statistics of real-time message processing modules and then consider another possibilities for improvements.</p> Mentat - Task #3392 (In Progress): Revision of JPath libraryhttps://homeproj.cesnet.cz/issues/33922017-03-25T08:58:28ZJan Machjan.mach@cesnet.cz
<p>Because <strong>mentat-inspector.py</strong> is currently being heavily used and expectations are getting bigger, it would be wise to perform revision of the library and finish the implementation, so that everything works as expected and <strong>mentat-inspector.py</strong> delivers.</p>
<p>JPath is simplified version of JSONPath and can be used to addressing nodes within arbitrary data structure composed of dict-like and list-like objects. Basically it can be used for any data structure of objects implementing Python list and/or dict interface.</p>
<p>The motivation for implementing this module were following two use cases:</p>
<ol>
<li>Writing of simple rules in filtering expressions, for example:</li>
</ol>
<pre>
Source.IP4 in [192.168.0.0/24, 192.168.0.0/24]
</pre>
# Simple message modifications based on the key => value rules, for example:
<pre>
"Source[1].Type[*]" = "source type tag"
</pre>
<p>The obvious first choice as a solution was the <strong>jsonpath-rw</strong> library. The full JSONPath however seems to be too big of a gun for our needs and in some cases it could even enable users to cut branch they are sitting on. For this reason we have designed this simplified version with only basic features.</p>
<p>Documentation must contain examples for common use cases.</p> BEESIP - Feature #499 (New): Use Copy-On-Write filesystem support where applicablehttps://homeproj.cesnet.cz/issues/4992012-06-15T21:12:29ZLukáš Macuramacura@opf.slu.cz
<p>Try to optimize build process to use COW where possible (like in btrfs). Many openwrt trees can use same data until change is made. So we will reduce disk usage.</p> BEESIP - Task #493 (New): Resolve dependencies in prereq by clean wayhttps://homeproj.cesnet.cz/issues/4932012-06-12T20:25:10ZLukáš Macuramacura@opf.slu.cz
<p>We should definitively solve prereq target. It should report which commands are missing and maybe it should echo some system specific hint how to install missing packages. But it should not be focused only to one distribution.</p> BEESIP - Task #487 (New): Interconnect BESIP with accountinghttps://homeproj.cesnet.cz/issues/4872012-06-10T13:26:27ZLukáš Macuramacura@opf.slu.cz
<p>BESIP should be internaly glued with accounting inside. Each direction should be costed internaly and price per minute of each call should be known before starting call. <br />After this, BESIP will be much more secure and cost limits can be created easily.</p> BEESIP - Task #486 (New): Add support of basic PBX functions for userhttps://homeproj.cesnet.cz/issues/4862012-06-10T13:23:39ZLukáš Macuramacura@opf.slu.cz
<p>BESIP should be fully configurable for common user functions in PBX.</p>
<p>- Call forwarding on busy<br />- Call forwardinf on unreachable<br />- Call forwarding per caller number<br />- Call redirection<br />- Call blocking<br />- AntiSPIT</p> AC Login - Task #456 (New): Prozkoumat moznosti bezpecnejsiho predavani breeze sessionhttps://homeproj.cesnet.cz/issues/4562012-05-24T05:03:03ZIvan Novakovivan.novakov@cesnet.cz
V soucasne dobe je AC Login nachylny k odcizeni session, protoze:
<ul>
<li>session se predava jako GET parametr</li>
<li>neni tam zadne omezeni, napr. session neni vazana na IP adresu</li>
</ul> AC Login - Task #455 (New): Odstranit moznost nastaveni target GET parametruhttps://homeproj.cesnet.cz/issues/4552012-05-24T05:02:41ZIvan Novakovivan.novakov@cesnet.cz
<p>Target parametr umoznuje dynamicky nastavit, na jake URL presmerovat po prihlaseni. Toto URL by melo byt natvrdo nastavene pro danou instanci, jinak lze snadno nekomu podstrcit link s upravenym targetem a zjistit tak session.</p> BEESIP - Task #393 (In Progress): Improve wiki pagehttps://homeproj.cesnet.cz/issues/3932012-03-31T17:43:06ZLukáš Macuramacura@opf.slu.cz
<p>It is needed to improve wiki page of BESIP<br />Especialy, it would be good to explain our build process and target creation.<br />Next, general usage of global Makefile</p> BEESIP - Task #390 (In Progress): Prepare yang module for BESIPhttps://homeproj.cesnet.cz/issues/3902012-03-24T19:33:09ZLukáš Macuramacura@opf.slu.czBEESIP - Task #180 (New): Prepare lua extensionshttps://homeproj.cesnet.cz/issues/1802011-08-03T12:26:22ZLukáš Macuramacura@opf.slu.cz
<p>Please prepare asterisk lua extensions with basic functionality. Create switch besip, which will be called for all calls.<br />This script should do at first:<br />- Look into sqlite3, if calling user/number is local user (if call is originated from us)<br />- If destination is local <br />- Look into db for user parameters (please prepare function getuserparms() for it)<br />- Look into db for line parameters (please prepare function getlineparms() for it)<br />- If needed from user or line parameters, do or not this:<br /> - enable debug<br /> - enable call quality monitoring (tcpdump)<br /> - look into local tariftable, if given user can call this number<br /> - if so, get price for this direction (getprice(user,src,dst)<br /> - compute maximum number of seconds to call (credit/price)<br /> - set maximum call length<br /> - after call, update credit and quality monitoring</p>