[x] Several weeks before: send out an email to the participants reminding them that they are signed up and to clear their calendars. You can find a template in FACILITATING.md.
[x] You will be communicating with / authing these folks a lot. I find it helpful to save a copy/pasteable list of their names here:
[x] The week before: send out an email to each of the participants. You can find a template in FACILITATING.md.
[x] Get a Zoom room setup for remote participants. {} (Make sure to include this on your calendar invites.)
Scheduling
[x] Schedule a welcome/orientation session (1hr at 9:30 Monday morning). Discuss the goals of the week and prime the participants to consider what they'd like to get out of Onboarding week.
[x] Schedule daily standup (15min at 9:15, starting Tuesday).
[x] Schedule any sessions that you know the group would be interested in -- for example, BOSH boxes and lines.
[x] In the past, non Engineers have appreciated it when we blocked out the entire days of onbaording. This is especially helpful if done a few weeks in advance; so, they have time to move meetings and avoid having new ones scheduled in the first place.
These are core CF topics, other topics are a bit more "extra credit".
[ ] BOSH {}
[ ] CF Overview {}
[ ] Concourse {}
As a helpful reminder, you can save the name of the speaker w/ checkbox.
[x] If your CF on-boarding will include the GCP track (gcp tracker label / the oss build) then ensure participants have access to the CF-Onboarding-dns project in GCP (for DNS propagation). IAM for DNS
Tracker Setup
[x] Make sure you have Tracker projects prepared.
[x] In SF, we use the following trackers projects:
[x] Add all participants as members to each of the tracker projects. (A list of emails works here.)
[x] Delete everything from the tracker projects.
[x] Build the tracker back log csv
[x] Run ./build oss from the onboarding project, this will generate onboarding-tracker.csv
Note: you need docker installed brew cask install docker
To get the command line tool to show up you may have to first start docker via Spotlight Search
If docker gives you this error: failed to dial gRPC: unable to upgrade to h2c, received 502 context canceled
In docker settings: enable experimental, restart docker, disable experiment and restart again.
[x] Import the CSV into each Tracker project (Taskbar > More > Import CSV > Choose File)
LastPass Setup
[x] Give all participants access to the shared LastPass folder:
LastPass > Sharing Center > Shared-CF SF Onboarding > Manage > Invite Users (A list of emails works here.)
Workstation Setup
Note: local IT departments can sometimes help with workstation setup. (Helpful for remote facilitation.)
[x] Make sure you have a workstation for each pair.
[x] Ensure ethernet cable is plugged into iMac, not monitor.
[x] Re-image each machine. Here are the steps:
[x] Run Startup Disk.
[x] Unlock with the workstation password (you may need to ask the previous facilitator for the machine's password).
[x] Select the network disk and click restart. It will likely be the rightmost start disk, and will definitely include the phrase "Network Disk." If you don't see that, try restarting the machine and try again.
[x] Select deployment option 2, "macOS Sierra" and click the play button. If you look in between the parens of the option name, you'll see the default password for the image. A terminal will open and you’ll see a lot of output, including a bunch of lines that say installer: PHASE: Running package scripts. Don’t worry, this is fine. The boot script will search for updates -- you’ll see output about OS X, iTunes, and Safari updates, for example -- and the machine will probably restart a few times as it downloads and installs the updates.
[x] Log into machine with the default password.
[x] Open the security preferences and change the password to something sane. Write this down so you can give it to the participants later.
[x] Open a terminal window and run
curl -LOk https://github.com/pivotal-cf-experimental/onboarding-week-construct/archive/master.zip
unzip master.zip
cd onboarding-week-construct-master
./construct
You'll need to babysit this process, as it will prompt you for the password several times.
Misc
[ ] Record any issues you have with this process so we can update this checklist.
Communication
sboyles@pivotal.io,nchandni@pivotal.io,anbrown@pivotal.io,driddle@pivotal.io,anelson@pivotal.io,wbrandon@pivotal.io,hnandiwada@pivotal.io,adidner@pivotal.ioScheduling
[x] In the past, non Engineers have appreciated it when we blocked out the entire days of onbaording. This is especially helpful if done a few weeks in advance; so, they have time to move meetings and avoid having new ones scheduled in the first place.
These are core CF topics, other topics are a bit more "extra credit".
As a helpful reminder, you can save the name of the speaker w/ checkbox.
IaaS Setup
gcptracker label / theossbuild) then ensure participants have access to theCF-Onboarding-dnsproject in GCP (for DNS propagation). IAM for DNSTracker Setup
./build ossfrom the onboarding project, this will generateonboarding-tracker.csvbrew cask install dockerfailed to dial gRPC: unable to upgrade to h2c, received 502 context canceledLastPass Setup
Workstation Setup
Note: local IT departments can sometimes help with workstation setup. (Helpful for remote facilitation.)
Startup Disk.installer: PHASE: Running package scripts. Don’t worry, this is fine. The boot script will search for updates -- you’ll see output about OS X, iTunes, and Safari updates, for example -- and the machine will probably restart a few times as it downloads and installs the updates.You'll need to babysit this process, as it will prompt you for the password several times.
Misc