| | LCFG Annual Review 2018
On Thursday 6th December 2018 instead of our normal monthly Deployers Meeting we will be holding our traditional Annual Review session. This will start at 2pm and we aim to be finished by 5pm. This year it will be held in room 7.14 of the Appleton Tower. Refreshments will be provided including some seasonal treats. |
| |
- Pyngi - Python Components
- Work on building a framework for building LCFG components in Python is under way. The intent is to allow natural Python coding to be used while respecting the historic LCFG approach. Further work is needed, opinions, advice and coding effort are welcome. Subversion repository is: https://svn.lcfg.org/svn/source/trunk/pyngi
|
|
>
> |
- Logging
- IS have changed their LCFG managed servers to log closer to the native OS to reduce surprise and confusion for colleagues when they find
/var/log/messages and so on empty, and /etc/rsyslog.conf the one deployed by the original RPM. The LCFG components are instructed to log via syslog, and the results are all harvested by FileBeat and sent to LogStash for processing and storing in ElasticSearch and viewing in Kibana. It's not perfect but has proven useful already.
- Macos Support
- Going, going ... almost gone! The IS Devolved LCFG infrastructure refresh (almost complete) will not have any support for Macos - no building, no compiling profiles, no distributing packages.
- IS ITI Enterprise Services
- We are continuing to bring exciting new services managed by LCFG - all our mail relays, eddir/smsdir servers, maildata server, MariaDB Galera cluster for EASE and soon ... Sympa mailing lists and half of Staffmail. Still waiting for our Puppet efforts to bring similar levels of value as LCFG.
|
| |
- Bugs
- We really would like to see more bug reports! We all know about various bugs (whether trivial or important) or have features we would like to see. It would be very helpful if we could get these recorded. We can't promise they will get fixed but just having them in https://bugs.lcfg.org/ would be a great start. I propose that to make them more useful and improve response times at each monthly meeting we review all newly submitted bugs from the previous month.
--  squinney - 2018-10-31 |
Copyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.