Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1287 times and has 1 reply Next Thread
sunk818
Advanced Cruncher
Joined: May 10, 2018
Post Count: 66
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Attaching persistent storage to a cloud spot instance (Ubuntu 16.0.4 LTS)

Hello, I'm not sure where to ask this question but perhaps this is the right place.

I'm interested in experimenting with spot instances to help contribute work units for WCG. My approach is to rent cloud spot instances. These are bare metal servers that I can pay a discount hourly price for, but have to relinquish the hardware if it is unavailable. All the data is erased when the server is relinquished. I was thinking of somehow attaching a persistent storage server/node using a cheap ARM baremetal server with a lot of storage.

I'm not sure how BOINC data is structured, but if I could have the BOINC data live on the ARM server, then I'd have a network drive I could point to whenever I create a new spot instance.

Any thoughts on this setup?
[Aug 21, 2018 6:31:13 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Attaching persistent storage to a cloud spot instance (Ubuntu 16.0.4 LTS)

The data directory is self-contained in /var/lib/boinc-client (older version) or if a newer client /var/lib/boinc ; all your CPID, configs, work units, graphics, etc. are all located there, so if you mount your persistent storage like that you should be OK.

Be careful though - I'm using Debian 9, the packagers attempt to make the client package more L-FHS compliant and use symlink tricks to push some of the configs over into /etc so you'd be wise to sort out how you'd like to manage that tidbit. For example, here are the symlinks they put into place on Debian 9:

$ sudo find /var/lib/boinc-client -type l | xargs ls -l

lrwxrwxrwx 1 root root 34 Apr 20 17:34 /var/lib/boinc-client/ca-bundle.crt -> /etc||ssl/certs/ca-certificates.crt
lrwxrwxrwx 1 root root 31 Apr 20 17:34 /var/lib/boinc-client/cc_config.xml -> /etc||boinc-client/cc_config.xml
lrwxrwxrwx 1 root root 43 Apr 20 17:34 /var/lib/boinc-client/global_prefs_override.xml -> /etc||boinc-client/global_prefs_override.xml
lrwxrwxrwx 1 root root 34 Apr 20 17:34 /var/lib/boinc-client/gui_rpc_auth.cfg -> /etc||boinc-client/gui_rpc_auth.cfg
lrwxrwxrwx 1 root root 34 Apr 20 17:34 /var/lib/boinc-client/remote_hosts.cfg -> /etc||boinc-client/remote_hosts.cfg

...so you have to figure out what you'd like to do to ensure you don't lose that (I for instance use custom global_prefs_override.xml tuning, so would ensure that's somehow on my persistent storage). Since they don't change all too often, a single backup of those /etc||boinc-client files should suffice - they're not runtime adjusted, just static.

NOTE: this forum seems to block "slash-etc-slash" (I can't even type it here) from all posts, I have changed it to "slash-etc-pipe-pipe" ( /etc|| ) in the above output, and stripped trailing slashes.
[Aug 26, 2018 1:26:47 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread