I wanted to move to a text based changelog in our applications rather than a Notes form or even an XPage.The idea was that it would help make it easier to deal with merge conflicts in source control.
I eventually settled on using Markdown as I couldn’t get the formatting that I wanted with ascii. Continue reading “Displaying Markdown in an XPage using the showdown.js library”
Review Element 12: Management of Change and Project Management
I have just been reading an excellent guidance note from the Energy Institute entitled “Element 12: Management of Change and Project Management“. I think that it was authored mostly by Martin Ball and was published in September 2015.
It is part of a series of guidance notes that set out a 20 element framework for Process Safety. Continue reading “Review of the Energy Institute Element 12: Management of Change and Project Management Guidance”
PX / Sellafield PSM Management of Change for Process Safety Case Study
1. The Challenge
PX Ltd manage the operations and maintenance of the Fellside 188 MW CHP plant providing critical process steam and electricity to the adjacent Sellafield nuclear reprocessing facility.
PX Ltd approached FoCul for a browser based solution to manage engineering change at Fellside. The system needed to provide a controlled and auditable process for managing engineering change and needed to allow engineering changes to be managed efficiently within the organisation. Continue reading “PX / Sellafield PSM Management of Change for Process Safety Case Study”
We have been battling with one of 6 Domino XPage servers that is running a consistently higher load average than the other servers. The performance was OK from a customer point of view but differences in systems are always a worry.
We tried everything I could think of – probably spending 2 – 3 days on this overall. We checked the XPage application, we checked Domino configuration, we even moved it to a different host server and we even rebuilt it from a (new) standard image. Anyhow, the problem has been solved 🙂
We recently did a routine update to the linux OS and the issue went away. It seems that there was a bug in the linux release that we were using which –
“Due to prematurely decremented calc_load_task, the calculated load
average was off by up to the number of CPUs in the machine. As a
consequence, job scheduling worked improperly causing a drop in the system
performance – https://rhn.redhat.com/errata/RHSA-2016-0494.html“
So the morale of this story
- Do some monitoring, that way you can see how updates to the OS and other software are affecting performance. If you roll out an update look for improved or decreased performance – always being on the latest release is not necessarily the solution.
- Never build a standard recovery image and assume that it will run correctly in operation unless you have run it in production. This server was first based on our latest build template ( including a new OS version – which was broken ) and when we rebuilt it we used that image again ( still with the broken OS )
We are using the Opsview Atom monitoring suite which is based on the Nagios open source platform. It is fairy good ( and well priced ). I will be post some articles on it soon.
For some time I have been interested in setting up a development VMWare ESXi server on a laptop to help with testing etc. The problem in the past has been that the ESXi install only comes with drivers for high end network cards and the process of adding the required drivers is chewy
As of ESXi 5.5 update 3 and ESXi 6 the drivers for the Intel 82579LM network card have been included in the core product so as long as your laptop has > 4GB installed ( 4GB is not enough as it registers as 3.9 GB and the install fails ) you can install ESXi 5.5 or 6 on your laptop. I only found this out after doing all the chewy stuff first 🙂
The only other serious issue that I have found is that when you are creating hard disks they must be IDE drives and not SCSI drives otherwise they will not be visible to the guest Bios.
There is a bit of a niggly issue with VSphere whereby the console does not always display. Richt clicking on the menu selecting the pop up console seems to free this up.
ESXi is free for up to two physical CPUs