#2452 closed task (fixed)
new VM for demo.pycsw.org
Reported by: | tomkralidis | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2020-I |
Component: | SysAdmin | Keywords: | pycsw demo |
Cc: | robe |
Description
http://demo.pycsw.org is running off the old adhoc machine.
We (pycsw) would like a new VM so we can setup an autodeploy via Docker, which will lessen the legacy footprint of AdhocVM.
Change History (12)
comment:1 by , 5 years ago
comment:3 by , 5 years ago
Specs are great. Yup I can login to https://monitor.osgeo.org/ just fine.
Thanks
comment:4 by , 5 years ago
VM is setup, I haven't added it to the monitor yet.
the container is called pycsw and I gave you sudo rights in it.
So you should be able to login with tomkralidis@osgeo7-pycsw and finish setting it up however you like. It's already got docker installed.
comment:5 by , 5 years ago
As discussed with Tom on IRC. proxying port 80 on nginx to domain https://staging.demo.pycsw.osgeo.org/
We'll flip it to demo.pycsw.org once he's done setting it off and shut off the demo.pycsw.org running on old-adhoc.
comment:6 by , 5 years ago
updates:
- I've deployed the setup to
/opt/demo.pycsw.org
- can we have a UNIX group
pycsw-demo
(which includestomkralidis
for starters)? - can we enable running docker without sudo for anyone in the
pycsw-demo
? See https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user for more info
comment:7 by , 5 years ago
Tom I can't figure out how to give a different user group access to docker. It seems docker is hardwired to accept only docker as a group. I'm sure it's buried somewhere and we can rename it, but not sure
So what I did instead is this -- which is pretty much following the directions you had above
sudo usermod -aG docker tomkralidis #add tom to docker group sudo usermod -aG docker robe # add regina to docker group
Then I exited out of pycsw and logged back in and tried doing this. Note logging out and logging back in is required for new permissions to take effect.
docker run hello-world
and it was successful. Before that it gave a permission error.
Is that okay, or you really need the group to be called pycsw-demo?
comment:8 by , 5 years ago
tomkralidis just one more note -- since you are an admin of this container you can do anything you want with it including adding new members to docker group.
The container is snapshotted nightly and 30 days of backup is kept, so if you screw it up badly we can always restore from a previous backup.
comment:9 by , 5 years ago
Thanks Regina, group name docker
is just fine, thanks.
I didn't realize it was ok for me to make admin changes, will do so in the future. As well, thanks for the note about backups. Excellent SAC services here!
comment:10 by , 5 years ago
I think we are ready for the switchover. Let's discuss on IRC (I am unsure on how HTTPS will work).
comment:11 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
As discussed on irc all set and switched over.
Committed the changes at https://git.osgeo.org/gitea/sac/osgeo7/commit/fabc16b4749039e3ace34de3a6f3029fa7d8e6eb
comment:12 by , 5 years ago
Milestone: | Unplanned → Sysadmin Contract 2020-I |
---|
I'll start off with 4G RAM, 4 CPU, 100 GB. Is that okay? We can go up if needed those are just soft-limits so easy to change without rebooting.
I've been slowly resetting up monitoring for all the servers.
Can you see if you can log into here -- https://monitoring.osgeo.org
Once I have the new server setup you'll see metrics for it on the OSGeo7 dashboard.