@dkayiwa, we probably need to update our release process to ensure that mdsbuilder (platform), qa/modules/uat/demo servers are regularly upgraded after a release. Where’s the best place to change the documentation?
We had yet another problem this week in our infrastructure due to those two unpatched instances. Our provider currently blocked our network partially due to that. To avoid that in the future, we really need to address security patches on those services.
@dkayiwa and @raff , I need your advice. To upgrade mdsbuilder instance, one needs:
Run a new manual build to deploy to docker hub bamboo
Deploy using the manual stage
The thing is: I don’t know if this is safe. Is this something we can ask to be done on every release?
If so, I’m fairly sure I can make the deployment easier.
@darius or @ball, what can we do about ebola environment? Do we have anyone who could make sure it has the security patch applied? I’m afraid I cannot maintain a public system running such a vulnerable code.
I really don’t understand our distributions or if there are breaking changes. If, for example, we need to upgrade those plugins, or if the release manager will be able to test the distribution locally before deploying.
Generally, i feel that this is a good place to start. We can update the release process to include these extra steps. I trust that given time, you can make it even easier.
Hopefully fixing the Ebola distro is as easy as changing the REST module version to 2.24.0.
Unfortunately I don’t have an OpenMRS dev environment set up now. I can probably test this within a week, but can’t guarantee when.
If someone else is able to clone the repo, make a one-line change to the distro properties file, run it with the SDK, and manually poke the UI to see if anything obvious broke, please do!
I rebuilt my local ebola from scratch with (old) rest 2.12. Created a patient; found patient record, ebola dashboard. However I don’t see how to add a patient to a ward. It does not show active patients – although
I created 2 patients and all privileges set for the user. Ward rounds looks like this (grayed out).
I changed the openmrs-distro.properties
omod.webservices.rest=2.24
It works the same, but I’m not able to test the uiframework pages. Not sure if this proves that the new rest module isn’t breaking anything.
Does the ops process for this demo require that I do a successful bamboo build? Or is it enough to have updated the distro.properties file?
I was not able to test this locally (got blocked because it requires Java 7), but I hope Ellen’s test is a bit indicative that it will work. And worst case, if this doesn’t work, we’ll find out when the demo is up.
So that’s related to the fact that we need to update JDK 7 to a most recent update, which supports letsencrypt.
I attempted to upgrade the java to 8 (keeping the compatibility mode to 6), but that seems to have failed important tests. I contacted the OpenJDK repository to see if they plan on offering the new updates, otherwise I’ll have to come up with another work around.
Anyway, I attempted to just use JDK 8, but there were test failures. I disabled to tests to see if the server would at least start when I deployed the new machine, without bitcoins miners.
But the provider blocked my access Anyway the applications are down now. I’m not even sure what they expect me to do.
Anyway the applications are down now. I’m not even sure what they expect me to do.