![]() |
Tim
These were accepted
Actions completed:
It was felt that the benefits of continuing our current practice outweighed the relatively risks involved.
The spread of skills across the computing staff is now complete. The remaining actions will be tracked at CEG
Actions added:
Reports from units.
Despite the new easier mechanism for requesting certificates, it was agreed that requests for new certificates should continue to be funneled through the Infrastructure unit. Certificates should only be requested if absolutely necessary due to the problem of managing large numbers of certificates. Wallet will make management of certificates easier.
The upgrade to SL5.4 will require the re-installation of many desktop machines as until recently, the default root partition size was not large enough to accommodate SL5.4 upgrade process. This only applies to machines which use the RAT set of packages. Machines which do not use these packages (e.g. servers) are fine. We will have to consider whether the effort involved in upgrading many machines, especially lab machines, is justified or whether it would be better for these machines to remain at SL5.3 with all the security issues that implies.
The MPU requested that all machines being brought back into service after spending some time in a cupboard should be re-installed to pick up the new partition size.
It was suggested that this might have been due to a lack of temp space on the server or client.
It was suggested that we should look at using AFS file space for the lab based exams.
It was suggested that some sort of hook, explaining that these commands were not available should be added to student.ssh
Neil asked where was the appropriate place for people to run their own long-running processes, for example web servers. After some discussion , it was agreed that the compute servers were not the right place for this though there was less agreement over where the right place actually was. One suggestion was that the login servers should be used for this.
The issues raised by Ian's documentation review were discussed at some length. It was agreed that the overwhelming need was to appoint an editor with overall responsibility for the documentation we produce and to agree on a workflow for producing documentation which works for us. With that accomplished, we can make a start on re-arranging and editing our documentation. It was suggested that a suitable first step might be to move our existing user-facing documentation to Plone.
AOCB
The next Operational meeting will be on Wednesday 13th January in IF-4.31 chaired by Alison Downie
Please contact us with any
comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh |
![]() |