Folder: GENERAL From: denisovd@fnal.gov Subject: September 30 Date: 14-AUG-2011 21:58 Expires: 13-OCT-2011 21:58
Dear DZero Colleagues! This is to update everybody on plans for September 30, 2011 the last day of the Tevatron operation. The program will start at around 1:00pm with ending last data taking run at both CDF and DZero and turning the Tevatron off. Then the Laboratory wide party will proceed from 3:00pm to 5:00pm with parties by the experiments to follow in the evening. Formal celebration of the Tevatron legacy and results is planned at a special event in June 2012 at Fermilab. We plan to have collaboration picture taken sometime between 1pm and 3pm. We are inviting all present and past DZero collaborators to September 30th events. Please, be advised that Fermilab will not be able to provide financial support for travel, while we will have video streaming of the most exciting events. We will provide help with applications for US visas for those who needs them to come. Those planning to come should contact their IB reps (or former IB reps), so we have count of those who are coming. We are discussing Web registration as well. As a reminder during the week of September 26 to 30 we will have the DZero collaboration meeting at Fermilab and we plan a series of plenary talks on Friday, September 30 between 9am and noon in the Auditorium which all past and current collaboration members are invited to attend. Gregorio and Dmitri.
https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl # will already be pre-configured export do = "--dry-run=client -o yaml" # k get pod x $do export now = "--force --grace-period 0" # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section . Question 1 | Contexts Task weight: 1% You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...
Comments
Post a Comment
https://gengwg.blogspot.com/