published 24/05-18 by board
We assume you've heard about EU:s new GDPR initiative. The rules state that we have to give you clear informtaion about how we store and use your data. We at LUDD have therefore set up a Privacy Policy showing what data we store, how we store it and your options when you want to change your data.
The Privacy policy can be found at: http://ludd.se/privacy
Nothing has really changed regarding your data. But now we have everything in writing.
So here is the last bullet for GDPR!
published 09/01-18 by armedguy
We have finally migrated our first service over to the new compute cluster, and decided that physical member servers would be step one.
This means that our old (not very old though) member server discovery.ludd.ltu.se will be discontinued. It also means that if you were using taurus.ludd.ltu.se, luminous.ludd.ltu.se, or any of our other servers, they are gone too.
Our 4 new servers are as follows:
sarek.ludd.ltu.seabisko.ludd.ltu.semuddus.ludd.ltu.sepadjelanta.ludd.ltu.seEach server has the following specs: 2x Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz, 12-core CPUs totalling 48 threads 64GB DDR3 RAM @ 1800MHz
These servers are ThinLinc-enabled, which means you can download the ThinLinc client and access your desktop from anywhere. https://www.cendio.com/thinlinc/download
To use the servers with ThinLinc, please connect ThinLinc to echo.ludd.ltu.se, which serves as the master server (not a member server). Session life is set to never expire, so you can always disconnect from a session and come back later.
For people using best.ludd.ltu.se:
best will be updated to point to the new member servers in a while. Please
remember that load balancing on best is done purely by round-robin DNS, so
there is no guarantee that best will actually give you the best server, or any
working server at all for that matter.
If you have any issues with the servers, please contact the administrators.
published 05/11-15 by yugge
We recently upgraded our gitlab instance at buck.ludd.ltu.se.
Due to breaking changes on gitlabs side we cannot migrate the database along with the projects, so the migration needs to be done by the user.
Thankfully we have managed to make a program for this cause available on
taurus.
Sign into new buck ( http://buck.ludd.ltu.se )
Sign into taurus using ssh (putty is a good alternative for windows)
Make sure you have a public ssh key generated at taurus, it should
be located at .ssh/id\_rsa.pub
file .ssh/id_rsa.pubssh-keygenCopy the content of the file to the sshkey fields in both new buck and old buck
cat .ssh/id_rsa.pubGet the Private token from both old buck and new buck and note them down, you will need them later
On taurus run
buckmigration -oldKey [privateTokenFromOldBuck] -newKey [privateTokenFromNewBuck]The process could be pretty long, depending on the amount an size of your repos. But after completion the repos should be moved to the new buck.
Any Groups and/or Group projects will have to be created by hand, but that can be managed from the project settings. Sorry about this.
published 04/03-15 by axesun-3
The new card system is now in place. To unlock the door, swipe your card and enter your PIN.
published 23/02-15 by seblar-0
Det är för tillfället problem med våran disklagring orsakat av att sancontrollerns nätagg har dött. Det är bytt till en annan sancontroller och återläsning från backuper pågår.
published 13/02-15 by axesun-3
While the passcard authentication system is offline, the door will be open between 12:00-13:00, during weekends.