September 2012 - Core-students - mailman3.cels.anl.gov

Where's Tina
by Tina Stanton-Piersanti 13 Sep '12

13 Sep '12

I am going to work from home tomorrow. We need to take the dog to be put down. T. Sent from my iPad

1 0

Meeting Notes
by Ti Leggett 13 Sep '12

13 Sep '12

NetApp: - Dan to order Brocade rails - In the meantime, we'll get the Brocade configured and on net so we start to play around with things CryptoCard: - After a Open House, we will take one of the SC minis, install Snow Leopard and set up a central CC initializer console - ALCF will use ARD to remote to this machine to do token manips - Email ALCF user support to explain why this situation (laptop upgrades to unsupported OSes) Ubuntu 12: - Ken rollout to computes to 12.0.4 in the next few weeks Breadboard: - Narayan plans to stop supporting breadboard and make it solely systems, which means it goes to cryostasis as far as configurations Sasquatch boxes: - Hunter has concerns about if we can identify flaky disks adequately and deterministically

1 0

Today's user termination list
by stace＠mcs.anl.gov 13 Sep '12

13 Sep '12

Full list of people who no longer appear on the active employee list =========================================================================== 46351 PSC Adenwalla, Shireen 51059 PSC Moldovan, Nicolaie A. 82244 PSC Scott, James M. 84273 PSC Shandilya, Shivender Mohan Datt 88210 PSC Papandrew, Alexander B. 212967 HEW Arnold, Ashley 215918 CIS Faultersack, Liz 216197 PSC Kazmierczak, Katarzyna 221661 PSC Hevener, Kirk E. 221674 PSC Chakraborty, Rupak 221678 PSC Lightfoot, Malissa 225609 PSC Bodenhofer, Mona 225875 DIS Gallo, Giulia

1 0

Mountain Lion Solution
by John Roberts 12 Sep '12

12 Sep '12

All, Just wanted to see what others think a good solution would be. The first admin laptop with 10.8 came in today and it looks like all updates come through the app store now (requiring an apple id). I don't have 10.8 to experiment, but is there any way to avoid this or will we need to create one for them? Do we instead downgrade to Lion? thoughts? -- John Roberts Systems Administrator Jr. Argonne National Laboratory MCS Division roberts(a)mcs.anl.gov

1 0

Come get a cupcake....
by Tina Stanton-Piersanti 12 Sep '12

12 Sep '12

There are cupcakes at the Help Desk... come help yourself! Tina

1 0

git and puppet
by Ti Leggett 12 Sep '12

12 Sep '12

We talked about this at yesterday's core meeting, but I wanted to solicit wider input since there were a few absent. I think if we're to use puppet, we might as well use git for the version control. At first I thought it'd be beneficial because of the tight integration with the puppet modules github, but after using it that way I don't think adds or detracts anything (since I don't think we'll have the puppet forge modules as submodules - I can explain better in person why if you're interested). However, even without that, I think more people are learning git than anything else these days so that's a plus, and git has (what I think) is a unique way of dealing with branching/merging and how we can leverage that. After abusing git the last week, I think I've come up with a model that we can use git and puppet in a pretty distributed manner. First, puppet is configured to use dynamic environments, which means that every possible environment doesn't have to be pre-defined. Environments can be done on the fly and specified at puppet runtime. Environments are created by branching and referencing the branch as a submodule. The advantage here is that if someone has some significant changes (like integrating a new platform or re-tooling a module), they can branch, make their changes, test on a targeted node with a dyn. env., and all without affecting production configuration. Once things are tested appropriately, they merge their branch changes back in to production and done. The downside to this model is that it creates 2 different "views" of the repository - one for the puppet server, and one for how people edit and make changes - and there are a few extra steps to make changes to an environment/branch active on the server (though this can be more automated if we want). Let me see if I can explain the nitty gritty of how this all plays out: There is one repo for all things puppet, right now it's at [email protected]:puppet.git. With that repository there is the 'master' branch and it has the following contents: auth.conf environments/ fileserver.conf manifests/ modules/ puppet.conf The *.conf files are puppet server configuration and realistically shouldn't be changing much, if at all, after puppet is stabilized. The evironments/ directory is a stub that is used on the the puppet server's clone of the repo and the manifests/ and modules/ directories are empty stubs to be used by environment branches. Next, there is the 'production' branch. This branch is what will contain the default production puppet environment and configs. All subsequent environments should branch off of this and not 'master'. The 'production' branch looks like: manifests/ modules/ Where manifests/ contains the puppet manifests for what to manage and modules/ contains all the puppet modules that we use. For example: manifests/ sites.pp nodes.pp modules/ ldap/ ntp/ radius/ ssh/ Most everyone would interact with their local repository in the following way: git clone [email protected]:puppet.git cd puppet git checkout production git checkout -b ti_test [make your changes] git add ... git commit git push At this point you now have your very own branch that you can turn in to an environment to test out on a node. So let me explain how things look on the server side. The server has a clone just like anyone else. The difference is that environments are added by making a submodule of a branch of the same repository (that's right, I just got all recursive on your ass): git clone [email protected]:puppet.git cd puppet git submodule add -b production environments/production git submodule init git submodule update Now environments/production is a git submodule that's based of the 'production' branch of the git repo. If you want to update the production environment to whatever's recent: cd environment/production git pull origin production The upside to this is anyone can have access to the branch you're working on, so multiple people can all work on getting the new Ubuntu build working at the same time. The downside is that these environments don't automatically get updated on a top level pull (I couldn't get the post-merge hook to do anything useful) - although this may not necessarily be a downside. If we want all the environments updated on a top level pull I can certainly make a git alias to do that though. Ok. So with the extremely long email done, what do people think about this method?

3 6

Fwd: August Electrical Incidents
by Ti Leggett 12 Sep '12

12 Sep '12

Passing this on. I think we're pretty good about deferring our electrical work to the qualified people. > Hi, everyone. Attached are the summaries of electrical incidents occurring in August within the DOE-complex as derived from the initial ORPS reports. Lessons learned include: > > · Follow the procedure in LMS-PROC-152 when performing blind penetrations and follow the Dig Permit and other applicable procedures when performing excavations. Wearing electrical PPE reduces the hazard if an electrical line or raceway should be encountered. > · Electrical work must be performed in accordance with the NEC and manufacturer’s instructions. > · Modifications to electrical utilization equipment must be approved by a DEEI. > · Only qualified electrical workers may work on equipment with energized, exposed electrical parts >= 50 volts. > · Strictly follow Lockout/Tagout procedures, the general, simple procedure in LMS-PROC-185 or a complex, written procedure as described in LMS-ESH-7.1. Apply Lockout/Tagout before removing electrical equipment panels or any electrical work is performed. Check the integrity of the lockout devices and that they prevent energization. Zero voltage verification is required to confirm the circuit is de-energized. > · New electrical installations need to be inspected for conformance with the NEC in accordance with LMS-ESH-9.3, 9.3.10 to reduce the probability of installation problems that could result in electrical shorts or shock. > > When available from the initial reports, I am now starting to include the electrical severity score of each event. There is a tool available that allows the site’s electrical safety SME to calculate such a score based on a number of criteria regarding the incident and include it in the initial report. The SMEs have been involved in developing and using this tool. DOE is now urging us (and will likely soon require) the score to be calculated and reported. The score ranges are: > > Significance Level > Electrical Severity (ES) > High > ≥ 1750 > Medium > 31 – 1749 > Low > 1 - 30 > > I will be including the significance level with the score in the summary when available. Please note that in calculating the score, the person involved in the incident wearing the appropriate electrical PPE will usually dramatically reduce the severity and thus the score of an event. > > Let me know if you have any questions. > > Thanks, > Joe Kilar, CSP > Electrical Safety Engineer/SME/Trainer > ESQ Division > Bldg. 202/E140 > 630.252.3734 Office > 630.252.8862 Alt. Office (Bldg. 201/2J16) > 630.252.2942 Fax > Argonne National Laboratory >

1 0

Where's Tina (Wednesday 9/18, Afternoon)
by Tina Stanton-Piersanti 12 Sep '12

12 Sep '12

Next Wednesday I have to attend a mandatory orientation at School at Noon. I will leave after the sync and then head home after the 2 hour orientation and finish out my day from home and the practice field. Thanks! T.

1 0

Fwd: Your product is ready for pickup.
by Tina Stanton-Piersanti 12 Sep '12

12 Sep '12

I am going to Oak Brook again tomorrow after our sync to pick this up for Craig.. I will KEEP my keys in my hand the WHOLE time... T. Begin forwarded message: > From: Craig Stacey <stace(a)stace.com> > Date: September 10, 2012 11:33:48 AM CDT > To: Tina Stanton-Piersanti <tstanton(a)mcs.anl.gov> > Subject: Fwd: Your product is ready for pickup. > > Since i'm not allowed to lift anything over 10 lbs until sometime in October, I can't pick this up (it's my monitor from my office). Can you pick this up for me at the Apple Store in Oak Brook some time this week and leave it in my office? I left word with them to release it to you -- you'd just need to bring photo ID. > > Thanks! > > Begin forwarded message: > >> From: Apple Store Oakbrook <donotreply(a)apple.com> >> Subject: Your product is ready for pickup. >> Date: September 10, 2012 10:26:56 AM CDT >> To: stace(a)stace.com >> >> >> >> Your product is ready for pickup. >> >> >> Dear Craig Stacey, >> Repair Number: R73308808 >> >> Thank you for bringing your Apple product to the Apple Store Oakbrook for repair. >> >> Your product is ready. Please arrange for pickup in the next 7 days or contact the Apple Store Oakbrook at 630-573-7008, if you need to make other arrangements. >> >> Please remember to bring a photo ID. We look forward to seeing you. >> >> Thank you, >> Your Apple Store team, >> Apple Store Oakbrook >> >> See store hours and get directions >> >> >> TM and copyright © 2011 Apple Inc. 1 Infinite Loop, MS 96-DM, Cupertino, CA 95014. >> All Rights Reserved / Keep Informed / Privacy Policy / My Apple ID > > -- > Craig > > >

1 0

Today's user termination list
by stace＠mcs.anl.gov 12 Sep '12

12 Sep '12

Full list of people who no longer appear on the active employee list =========================================================================== 97216 ESQ Zeller, Shirley 207577 ESQ Devanney, John 210204 NE Chen, Wei-Ying 212836 ESQ Ryan, Phillip E. 212854 ESQ Raffel, Duane 212957 ESQ Popovich, Julie 218710 ESQ Johnson, Frederick 222384 PSC Dai, Zhou 227161 WSG Straub, Joseph D.

1 0