news

LUDD Downtime 23/6 - 1/7

published 30/05-19 by armedguy

On the evening of 23rd of June, ALL LUDD services will be shut down for power maintenance as well as maintenance of OpenStack and member services. This includes all LUDD services, LUDD DUSTcloud services, LUDD DUST HPC services, as well as virtual and physical LCNet offerings.

Mail services will also be down, so the primary point of contact with LUDD administrators will be via #ludd @ irc.freenode.net or LUDD:s Telegram channel. Any questions prior to the downtime, or if you are interested to help or curious about what will be done, contact us.

We reserve for all services to be down until the 1st of July, but hopefully they will be restored as soon as possible.

LUDD Downtime 25/3

published 21/03-19 by armedguy

On the 25th of March, all systems and networks on LUDD and LCnet will be down during the whole day. This downtime might extend to the 26th as well.

Systems will be shut down on the 24th at 23:00. (LCNet users, please shut down beforehand, as we will only cut the power to the racks).

LUDD DUSTcloud services will also be down during this time, including all users machines.

The reason is due to electrical work in the datacenter.

Intressekoll CCLan 2019

published 29/10-18 by augeri

NOTE: This is an old migrated article. Information here may not be relevant and is only here for reference.

Vi på LUDD tänker hålla i ett större LAN efter jul och behöver lite feedback på vad folk är intresserade av för spel till turneringar och dylikt. Om du är intresserad av ett sådant evenemang uppskattas det stort om du svarar på vår enkät nedan.

https://goo.gl/forms/GCCeE2BdpvOks9t72

Det finns även möjlighet för den som är intresserad att vara medverkande och hjälpa till att anordna LAN:et och därigenom få gratis inträde plus lite annat.

LUDDs Privacy Policy

published 24/05-18 by board

NOTE: This is an old migrated article. Information here may not be relevant and is only here for reference.

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!

New Member Servers

published 09/01-18 by armedguy

NOTE: This is an old migrated article. Information here may not be relevant and is only here for reference.

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.se
abisko.ludd.ltu.se
muddus.ludd.ltu.se
padjelanta.ludd.ltu.se

Each 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.

How To Migrate Your Work To New Buck

published 05/11-15 by yugge

NOTE: This is an article migrated from the old mediawiki-site. Information here is probably not relevant and is only here for reference.

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
1. You can verify that the file exist by running
```
file .ssh/id_rsa.pub
```
2. If the file doesn't exist, please create it by running
```
ssh-keygen
```
Copy the content of the file to the sshkey fields in both new buck and old buck
1. You can see the content of the file in ssh by running
```
cat .ssh/id_rsa.pub
```
2. You can add keys for new buck here: http://buck.ludd.ltu.se/profile/keys
3. You can add keys for old buck here: http://buck.ludd.ltu.se:8889/profile/keys
Get the Private token from both old buck and new buck and note them down, you will need them later
1. You can get the token from new buck here: http://buck.ludd.ltu.se/profile/account
2. You can get the token from old buck here: http://buck.ludd.ltu.se:8889/profile/account

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.

View Newer

List all news

View Older