Alright, tomorrow I’ll stop what I’m doing and switch to testing Lightsail installation with 6.1.0 – I think it’s fine but I have to check. After that I’ll update Express Plus (which works but needs feedback from AWS because of weird CFN deployment hitches).
After both of those are done (and while I’m waiting for feedback) I’m going to tackle Standard, since it’s broken right now, and get it updated to use t3 instances and Ubuntu 20. Express will be last.
Hopefully wrap up this weekend.
Okay, Lightsail 6.1.0 is cleared for use.
Isn’t there a way to download and pipe a script into bash as a one-shot, though? I want to do better than the twoliner I’ve got…
Now sitting down with Standard to integrate things.
Thanks for that work Asher!
Alright, first walkthrough of Standard has been completed (though nothing’s been built or tested, that’s for tomorrow).
Improvements:
If I’m fortunate I can have this built and submitted to AWS by Friday; do not anticipate it’ll be longer than the weekend.
Surprise special issue–
The problem with Express Plus deployment is resolved, and it can now be launched (from us-east-1, at least) from the magic index links as normal. ( https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=OpenEMR&templateURL=https://s3.amazonaws.com/openemr-cfn-useast1/OpenEMR-Express-Plus.json if you don’t remember those.)
I’ll get the other buckets later this week, although I’ll take requests if there’s one you want manually populated ahead of time.
Got Standard candidate built but won’t have time to test it tonight. Python is as usual the worst thing that ever happened to system administration.
I did realize something, though – all that trouble we went through to get the docker containers cross-compiling for ARMv8 and the Raspberry Pi? That does actually mean our containers are compatible with Amazon’s custom Graviton2 ARM instances, which are the lowest cost-per-hour they’ve got available.
I should do all the actual work first but I’m sorta tempted to put something together for it.
Please grant us poor souls an upgrade path to your new hotness before you tackle the ARM on AWS shiny! 
Huh, worked the first time. Did not expect that.
Alright! OpenEMR 6.1.0 Standard is now ready… toooooo be submitted to AWS Marketplace in several pieces which will require human review and oversight before release, which I’ll do today or tomorrow. In the meantime, however, I’ll make available this prerelease template that’s using an AMI served up from our own account instead of Marketplace, if anybody just absolutely has to get moving ASAP.
Just hand this template to CloudFormation (in us-east-1 only – sorry, them’s the breaks) and you should get going.
OpenEMR-Standard.json (39.5 KB)
Okay, Standard’s in the hopper. Now for Express…
Alright, so.
Express has a vaild image getting scanned at Marketplace now, but that’s only the first step of the process and I don’t know if it’ll be done tonight, so I expect to send Express in for review tomorrow.
Finally got some automation in place for Express image building though. Not /all/ of it but at least it’s a script without human steps now like it used to be.
Special late night update–
In the years since CloudFormation’s been a thing, AWS has finally cracked the problem of CF not being able to load templates from S3 buckets in different regions, which is why I had to have as many buckets as there /were/ regions which was very annoying thanks.
I’ve revised the Express Plus readme to be one link and a template URL instead of enumerating every region; Express Plus is now finished (though Jason’s not getting what he wants yet).
Okay, back and forth on some submission issues but I cleared those hurdles, Express has now been submitted to AWS for posting.
Current standing:
Lightsail (shared hosting): 6.1.0 OK
Express: In process at Marketplace
Express Plus: 6.1.0 OK
Standard: In process at Marketplace
Next steps:
Express Plus recovery pathing via specified parent’s S3/KMS
Graviton support for ARM (just as a proof of concept)
Is it finally time to retire Full Stack? I’m not sorry I built it, it was the foundations for everything else, but nobody uses it, I never got a request to update it to 6.0.0, and I’m not sure I would’ve honored it if I had, because Standard does 95% of what it does better – basically everything but the clustering.
Quick update:
Alright, Standard 6.1.0 is up in Marketplace. I don’t think I’ll get much on Express Plus recovery done today or tomorrow but I’d at least like to do some stack testing this weekend.
Okay, so lot of things coming, some of which nobody but me will care about, some of which nobody but me will care about in a very different way. (None of these are committed, they’re in a dev branch I’m working with.)
Oh my goodness but I can’t believe it all hooked together.
Express Plus recovery is in – seamless recovery from backups via child stack. I’ll do a longer writeup later; for now, you can verify by:
sudo bash and then /etc/cron.daily/duplicity-backups).Current project queue, let’s see how far we get this weekend:
Well, fancy that.
The Ubuntu 20.04 AMI I use for Lightsail supports EC2 Instance Connect out of the box – buuuut there’s a catch about security groups! If you’re properly careful, your ssh port is only open to your personal IP, and EIC sessions launched from the AWS Console don’t come from your browser, they come from IPs at the mothership. You need to identify the IP range the requests will come from* if you want the connection to go through, or you need to download the console Instant Connect application for your desktop.
You could also use the SSM stuff, but that’ll take an assigned IAM role and if you’re using Express Plus or Standard I’ve already got such a role in place, so you’ll need to add policies.
(*): Troubleshoot connecting with EC2 Instance Connect or just curl -s https://ip-ranges.amazonaws.com/ip-ranges.json| jq -r '.prefixes[] | select(.region=="us-east-1") | select(.service=="EC2_INSTANCE_CONNECT") | .ip_prefix' if you want to get on with things.
Oh god, I can’t believe this is a thing, I cannot believe this is a thing–
mkdir /tmp/backup-ingestion
cp /tmp/backup-ingestion
tar -xf ~/emr_backup.tar --no-same-owner
# restore site
mkdir webroot
tar -zxf openemr.tar.gz -C webroot
rm openemr.tar.gz
# still in progress
# restore database
gzip -d openemr.sql.gz
echo 'USE openemr;' | cat - openemr.sql | docker exec -i $(docker ps | grep _openemr | cut -f 1 -d " ") /bin/sh -c 'mysql -p"$MYSQL_ROOT_PASS"'
rm openemr.sql
Still a WIP, but I was 100% not aware that “piping a SQL log into a container” was a workable decision. I figured I’d end up doing a buncha file copies, but no.
Okay! First draft of a single-site OpenEMR backup file import into Lightsail.
This still can’t be used (hardcoded file names, bleah) but it’s what I’m thinking, if anybody finds it useful to read or correct. Cleanup and final testing are ongoing.
#!/bin/bash
# Some notes.
# One: We do not try to handle multisite, and we assume your openemr DB is named openemr. Will make that a parameter later.
# Two: Current I target only the sites directory, which may leave customization behind. You'll want to extend this recovery to
# pick up those changes (and maybe rerun composer?) but I'm not familiar with that part. I just know copying node_modules
*has* to be the wrong decision.
# Three: You'll want a /lot/ of room to unpack. An eight-gig instance won't cut it.
mkdir /tmp/backup-ingestion
cd /tmp/backup-ingestion
tar -xf ~/emr_backup.tar --no-same-owner
# retrieve site
mkdir webroot
tar -zxf openemr.tar.gz -C webroot
rm openemr.tar.gz
docker cp $(docker ps | grep _openemr | cut -f 1 -d " "):/var/www/localhost/htdocs/openemr/sites/default/sqlconf.php webroot/sites/default
docker cp webroot/sites/default $(docker ps | grep _openemr | cut -f 1 -d " "):/var/www/localhost/htdocs/openemr/sites/default-recovery
# straighten out internal permissions
docker exec -i $(docker ps | grep _openemr | cut -f 1 -d " ") /bin/sh -s << "EOF"
cd /var/www/localhost/htdocs/openemr/sites
chown -R apache:root default-recovery
chmod -R 400 default-recovery
chmod 500 default-recovery
chmod -R 500 default-recovery/LBF default-recovery/images
chmod -R 700 default-recovery/documents
mv default /root/default-old
mv default-recovery default
EOF
# restore database
gzip -d openemr.sql.gz
echo 'USE openemr;' | cat - openemr.sql | docker exec -i $(docker ps | grep _openemr | cut -f 1 -d " ") /bin/sh -c 'mysql -p"$MYSQL_ROOT_PASS"'
rm openemr.sql
# swift kick to PHP
docker restart $(docker ps | grep _openemr | cut -f 1 -d " ")
cd /
rm -rf /tmp/backup-ingestion
echo Restore operation complete!