Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Virtualization may be your answer (Score 2) 98

We had a similar issue with our engineers. We had login servers which worked great as they were poorly advertised and woefully underused, but once we had a system in place for them to make efficient use of them, they started to randomly crash. Most times it was due to them trying to submit a job to our compute farm and end up running it on the login servers, but sometimes it was malicious and a deliberate attempt to get a few extra CPU cycles at the expense of others. For us, the solution was rolling our own virtual desktop farm. We used KVM for the hypervisor, python for the back end control, and php for the front end web interface. We used Active Directory for authentication and rights management. That way we could control precisely how much resources each engineer had rights to.

As you are working at a school, it is not without reason to believe that you can use the students to help develop a system to manage the virtual instances. With a bit of forethought and a limit to the specifications, you can have a simple VDI broker developed and tested in a month. And if you avoid my mistake and use the libvirt API, you will even have the ability to easily expand the system to using linux containers.

Comment: Re:Haven't cared in 5 years, don't care now (Score 1) 108

by Jailbrekr (#47469491) Attached to: KDE Releases Plasma 5

We officially rolled out centOS6 earlier this year, and we were hit hard by the transition from KDE3 to KDE4. In the end all we could do was either recommend that users either go to gnome, or switch to Trinity (KDE3 fork). I expect that we'll have similar challenges when transitioning to CentOS7 in 2 years unless KDE4 was fixed in CentOS7, except then we'll have challenges with both KDE4 and Gnome3.

Comment: BYOD means I/T loses some control over it (Score 5, Insightful) 377

by Jailbrekr (#43855429) Attached to: Why Everyone Gets It Wrong About BYOD

BYOD means you can no longer trust your own network because you no longer have the same level of control over the devices on it. And if you do not trust your own network, you need to increase your security costs substantially and provide other resources that you would otherwise not need to offer. So while you're saving around $1000 per year per user on hardware, you're spending more on licensing for NAC and VDI/RDP/ICA. You also need to amp up the local tier1/2 support because now without standards they're going to be spending more time dealing with more types of machines. Any gains made by standardization will be utterly destroyed.

BYOD is a short sighted, stupid idea thought up by someone who sure as hell has no experience with I/T support.

Have you ever noticed that the people who are always trying to tell you `there's a time for work and a time for play' never find the time for play?