From mjbaysek at cs.cmu.edu Fri Oct 8 13:37:55 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Fri, 08 Oct 2010 13:37:55 -0400 Subject: [auton-users] Auton Compute System Downtime Required: Mon Oct 11 04:00 - 08:00 AM Message-ID: <4CAF56F3.2030007@cs.cmu.edu> Hi Lab. Monday, Oct 11, from 04:00 to 08:00 AM the compute system will be unavailable as I perform maintenance outlined below. - Re-installation of primary file server (after repairs were made while it was off-line) - Re-installation of LOT2 compute node. - Installation of new 48 core compute node, LOU1, time permitting. How this will affect you: - You will be unable to log in to any compute nodes during this time. - CVS, Subversion, and MySQL on LYRE will not be available. - Even though I am switching out the actual file server machine, the system is configured in such a way that you will not lose any jobs in progress on the compute system. Any I/O will just hang, until the primary server comes online. Then, the I/O will continue as if nothing ever happened. You won't have to restart any processes... except in the case of unanticipated problems, which... are not anticipated, of course. :) From mjbaysek at cs.cmu.edu Fri Oct 8 19:20:38 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Fri, 08 Oct 2010 19:20:38 -0400 Subject: [auton-users] Auton Compute System Downtime Required: TUE Oct 12 04:00 - 08:00 AM In-Reply-To: <4CAF56F3.2030007@cs.cmu.edu> References: <4CAF56F3.2030007@cs.cmu.edu> Message-ID: <4CAFA746.80904@cs.cmu.edu> Hi Lab, My apologies. The maintenance will occur TUESDAY at 04:00 - 08:00, not Monday, as mentioned previously. All other details remain the same. Happy Weekend - Mike On 10/8/10 1:37 PM, Michael J. Baysek wrote: > Hi Lab. > > Monday, Oct 11, from 04:00 to 08:00 AM the compute system will be > unavailable as I perform maintenance outlined below. > > - Re-installation of primary file server (after repairs were made while > it was off-line) > > - Re-installation of LOT2 compute node. > > - Installation of new 48 core compute node, LOU1, time permitting. > > How this will affect you: > > - You will be unable to log in to any compute nodes during this time. > > - CVS, Subversion, and MySQL on LYRE will not be available. > > - Even though I am switching out the actual file server machine, the > system > is configured in such a way that you will not lose any jobs in progress > on the compute system. Any I/O will just hang, until the primary > server comes online. Then, the I/O will continue as if nothing ever > happened. You won't have to restart any processes... except in the > case of unanticipated problems, which... are not anticipated, of > course. :) > > From mjbaysek at cs.cmu.edu Mon Oct 11 15:50:42 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Mon, 11 Oct 2010 15:50:42 -0400 Subject: [auton-users] Auton System Downtime Postponed Message-ID: <4CB36A92.9020703@cs.cmu.edu> The scheduled downtime for 04:00 to 08:00 on Tuesday is temporarily postponed. The new date and time is still to be determined. From mjbaysek at cs.cmu.edu Mon Oct 18 18:22:38 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Mon, 18 Oct 2010 18:22:38 -0400 Subject: [auton-users] New Compute NodeL LOU1 Message-ID: <4CBCC8AE.8080009@cs.cmu.edu> Hi Lab, A new compute node is available. LOU1 has 48 K10 Opteron Processor cores @2.3 GHz and a total of 128 GB RAM. The new node will be incorporated into the status page soon. To access the new node, first ssh into cpu.autonlab.org, then simply "ssh lou1" (or ssh -Y lou1 if you need X11 graphics). Enjoy, Mike P.S. If you don't already know, the naming scheme of our servers actually means something: L = Lab O = Opteron P = 4 GB RAM Q = 8 GB R = 16 GB S = 32 GB T = 64 GB U = 128 GB So LOU1 is the first Opteron machine with 128 GB of RAM. From mjbaysek at cs.cmu.edu Tue Oct 19 10:13:56 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Tue, 19 Oct 2010 10:13:56 -0400 Subject: [auton-users] Some Compute Nodes Decommissioned Message-ID: <4CBDA7A4.3050207@cs.cmu.edu> Hi Lab. With the addition of the new 128 GB / 48 core LOU1 node, the following obsolete machines are hereby decommissioned. Removed: 8 cores, and 16 GB of memory, total. LOP5 (2 cores, 4GB) LOP6 (2 cores, 4GB) LINA (2 32 bit cores, 3.5 GB) LIRA (2 32 bit cores, 3.5 GB) Added: 48 cores, 128 GB memory, total. LOU1 (48 cores, 128 GB) Net gain of 40 cores and 112 GB memory. From mjbaysek at cs.cmu.edu Wed Oct 20 17:40:42 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Wed, 20 Oct 2010 17:40:42 -0400 Subject: [auton-users] Data Security Message-ID: <4CBF61DA.6010604@cs.cmu.edu> Lab, This mail is coming as a reminder of some basic security principles that you all should follow. Remember that the lab works on a variety of projects from many different sponsors, and that security of the data that we are entrusted with is an important concern for all of us. Please keep the following in mind at all times when using a computer that contains or has access to any project data. 1) Keep a secure password on ALL ACCOUNTS at all times. Server accounts, local laptop accounts, etc. http://www.lockdown.co.uk/?pg=password_guide . Look at this guide. If you password sucks, change it NOW. Don't wait! 2) Never enable any file sharing or guest accounts on your workstation or laptop. If you think need to do this, _ Please run it by me first _. 3) Limit physical access to the computer whenever possible. Lock your office. Don't let your fathers, brothers, nephews, cousins, or roommates*, use the computer or laptop you use for work. Their computing habits (like browsing for free lolcat or Jessica Alba screen savers online) could put your computer at risk for keyloggers, trojan horse viruses, or spyware - all of which could compromise the data on your machine or release it to a 3rd party. 3b) Don't visit seedy sites yourself using the computer you use for work (for the same reasons above). If you think that the site you are thinking of right now could be seedy, it probably is! Are you pirating any good software or movies lately? Don't go there on a computer with sensitive data on it. 4) For personal machines, and laptops, be sure to have a firewall running on your machine at all times. This is very important when you join untrusted networks such as CMU's wireless network (no, we don't trust a network with thousands of mobile and/or untraceable computers on it), or the network at any airport or coffee shop. 5) Run anti-virus software (Windows machines especially) 6) Keep your computer up to date with security updates from Microsoft, Apple, Ubuntu, Adobe, etc. 7) On Laptops, boot time encryption such as TrueCrypt, or MacOS FileVault is _ highly recommended _. This guards your personal data and your identity, not to mention any sensitive data files if the computer is stolen, misplaced, or lost in transit. If you want to secure your laptop, and are concerned that you might mess something up, it's ok. I'll gladly set this up for you, even on your personal laptop. If you need to share or transmit sensitive data inside the lab and have any question on how to do this, please don't hesitate to contact me. Additionally, if you need to send (or receive) sensitive data outside the lab, do not send it by Email. We have various other ways of doing this securely. We should be accepting sensitive data from sponsors by Email. We have a both a secure FTP server, and a secure HTTPS file transfer for this. Thanks for your time. Please contact me with any questions. Mike * From #3, in all seriousness, I think it is wise to include former roommates, as well. From mjbaysek at cs.cmu.edu Wed Oct 20 18:12:47 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Wed, 20 Oct 2010 18:12:47 -0400 Subject: [auton-users] Data Security In-Reply-To: <4CBF61DA.6010604@cs.cmu.edu> References: <4CBF61DA.6010604@cs.cmu.edu> Message-ID: <4CBF695F.1000904@cs.cmu.edu> It's been pointed out to me that I made a typo in the final paragraph. The corrected paragraph is here, with the correction called out in asterisks: Additionally, if you need to send (or receive) sensitive data outside the lab, do not send it by Email. We have various other ways of doing this securely. We should *NOT* be accepting sensitive data from sponsors by Email. We have a both a secure FTP server, and a secure HTTPS file transfer for this. Mike On 10/20/2010 05:40 PM, Michael J. Baysek wrote: > Lab, > > This mail is coming as a reminder of some basic security principles > that you all should follow. Remember that the lab works on a variety > of projects from many different sponsors, and that security of the > data that we are entrusted with is an important concern for all of us. > > Please keep the following in mind at all times when using a computer > that contains or has access to any project data. > > 1) Keep a secure password on ALL ACCOUNTS at all times. Server > accounts, local laptop accounts, etc. > http://www.lockdown.co.uk/?pg=password_guide . Look at this guide. > If you password sucks, change it NOW. Don't wait! > > 2) Never enable any file sharing or guest accounts on your workstation > or laptop. If you think need to do this, _ Please run it by me first _. > > 3) Limit physical access to the computer whenever possible. Lock your > office. Don't let your fathers, brothers, nephews, cousins, or > roommates*, use the computer or laptop you use for work. Their > computing habits (like browsing for free lolcat or Jessica Alba screen > savers online) could put your computer at risk for keyloggers, trojan > horse viruses, or spyware - all of which could compromise the data on > your machine or release it to a 3rd party. > > 3b) Don't visit seedy sites yourself using the computer you use for > work (for the same reasons above). If you think that the site you are > thinking of right now could be seedy, it probably is! Are you > pirating any good software or movies lately? Don't go there on a > computer with sensitive data on it. > > 4) For personal machines, and laptops, be sure to have a firewall > running on your machine at all times. This is very important when you > join untrusted networks such as CMU's wireless network (no, we don't > trust a network with thousands of mobile and/or untraceable computers > on it), or the network at any airport or coffee shop. > > 5) Run anti-virus software (Windows machines especially) > > 6) Keep your computer up to date with security updates from Microsoft, > Apple, Ubuntu, Adobe, etc. > > 7) On Laptops, boot time encryption such as TrueCrypt, or MacOS > FileVault is _ highly recommended _. This guards your personal data > and your identity, not to mention any sensitive data files if the > computer is stolen, misplaced, or lost in transit. If you want to > secure your laptop, and are concerned that you might mess something > up, it's ok. I'll gladly set this up for you, even on your personal > laptop. > > If you need to share or transmit sensitive data inside the lab and > have any question on how to do this, please don't hesitate to contact me. > > Additionally, if you need to send (or receive) sensitive data outside > the lab, do not send it by Email. We have various other ways of doing > this securely. We should be accepting sensitive data from sponsors by > Email. We have a both a secure FTP server, and a secure HTTPS file > transfer for this. > > Thanks for your time. Please contact me with any questions. > > Mike > > * From #3, in all seriousness, I think it is wise to include former > roommates, as well. > From mjbaysek at cs.cmu.edu Fri Oct 22 12:01:47 2010 From: mjbaysek at cs.cmu.edu (Michael J. Baysek) Date: Fri, 22 Oct 2010 12:01:47 -0400 Subject: [auton-users] LOU1 is back up Message-ID: <4CC1B56B.606@cs.cmu.edu> The LOU1 compute node is back up. From yizhang1 at cs.cmu.edu Fri Oct 22 15:47:31 2010 From: yizhang1 at cs.cmu.edu (Yi Zhang) Date: Fri, 22 Oct 2010 15:47:31 -0400 Subject: [auton-users] Control over matlab parallel computing? In-Reply-To: <4CC1B56B.606@cs.cmu.edu> References: <4CC1B56B.606@cs.cmu.edu> Message-ID: <4CC1EA53.7020308@cs.cmu.edu> Hi guys, I wonder if any of you is familiar with Matlab's parallel computing? I wrote some code without any explicit parallel component, but once I started running the code, it splits into many threads ... I think it might be the case that Matlab is automatically parallelizing some of the code. Is there a way to control that? BTW, I'm not using Matlab's Parallel Computing Toolbox. All I wrote are normal Matlab code ... Yi From yizhang1 at cs.cmu.edu Tue Oct 26 00:03:31 2010 From: yizhang1 at cs.cmu.edu (Yi Zhang) Date: Tue, 26 Oct 2010 00:03:31 -0400 Subject: [auton-users] Control over matlab parallel computing? In-Reply-To: References: <4CC1B56B.606@cs.cmu.edu> <4CC1EA53.7020308@cs.cmu.edu> Message-ID: <4CC65313.7090608@cs.cmu.edu> Both Liang and Matthew have suggested this: http://www.mathworks.com/support/solutions/en/data/1-BYXN3A/?1-BYXN3A According to the link, I currently use maxNumCompThreads to control multi-threading. Works fine. Cheers, Yi On 10/25/2010 10:06 PM, Anqi Cui wrote: > I got this problem now. My Matlab codes are also very simple. On LORs > or LOQs, it only splits into 3 to 5, while on this LOU it generates > tens of tasks with low CPU usages. Although Yi and I are both from the > hometown of the Monkey King, who is able to clone thousands of himself > by transforming each of his hairs, this Matlab issue may somehow slow > down the calculation and I want to avoid it. > > Some friends told me in the Intel Math Kernel Library, many > calculations are already parallelized. Is this a possible reason? > Anyway, if it doesn't affect other's nor my calculation speed, it > would be fine. > > David > > 2010/10/23 Yi Zhang : >> Hi guys, >> >> I wonder if any of you is familiar with Matlab's parallel computing? I >> wrote some code without any explicit parallel component, but once I >> started running the code, it splits into many threads ... I think it >> might be the case that Matlab is automatically parallelizing some of the >> code. Is there a way to control that? >> >> BTW, >> I'm not using Matlab's Parallel Computing Toolbox. All I wrote are >> normal Matlab code ... >> >> Yi >>