gregsloan / bjc

Chef Automate Demo Repository

---

Welcome to Project BJC

Here you will find instructions on how to spin up a standard Chef Demo environment in AWS or Azure, as well as instructions on how you can contribute to demo development. This document assumes you have basic familiarity with AWS, Azure, Cloudformation, ARM templates, and SSH keys. This project is maintained by the Solutions Architects team at Chef. Issues, pull requests and general feedback are all welcome. You may email us at saleseng [at] chef.io if you want to get in touch.

The talk track script for the risk demo is located here

A project changelog can be found in CHANGELOG.md.

---

What is BJC?

---

BJC stands for Blue Jean Committee. It's also the code name for the Chef Demo project.

---

How do I spin up a demo?

---

First, setup your environment:

1. Clone this repository: git clone https://github.com/chef-cft/bjc

2. Change into the bjc directory: cd bjc

3. Set environment variables for your SSH key name and path, like so. This must match one of the authorized ec2 ssh keys in your AWS account. This is still required when lauching on Azure, but the key is simply ignored.

   • Put these lines into your ~/.bashrc or ~/.zshrc if you want to make them permanent.

   export EC2_SSH_KEY_NAME=binamov-sa
   export EC2_SSH_KEY_PATH=~/.ssh/binamov-sa.pem

Next, follow these steps to spin up your own dev/test environment:

The demo environment will provision in AWS or Azure fairly quickly, usually within a few minutes. Once the environment is up there is a startup script you must run to prep the demo. This script can take 10 minutes or more to complete. Be sure to give yourself plenty of time prior to the start of your demo for the environment to spin up and for the startup script to run to completion. We generally recommend setting up at least 30 minutes before your demo to ensure you have enough time.

1. git pull to fetch the latest changes.

2. Use the build_demo.sh script in the ./bin directory to stand up a stack!

   • Your command will look something like the command below. If you get an error, please read the error message as changes are routinely made!

   ./bin/build_demo.sh <cloud_platform> <demo-version> <customer_name> <EC2 key pair name> <TTL> <your_name> <departmenet_name> <region>

For example:

./bin/build_demo.sh aws stable 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.sh azure stable 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.sh aws 4.6.1 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.sh azure 4.6.1 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.ps1 aws stable 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.ps1 azure stable 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.ps1 aws 4.6.1 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

./bin/build_demo.ps1 azure 4.6.1 'RobCo' rycar_sa 4 'Nick Rycar' 'Solutions Architects' 'NA-Central'

If you receive an error similar to the one below (even when spinning up on Azure), it means that you have selected a version of the demo that doesn't exist (or hasn't been fully published for consumption). HINT: stable always works as a version!

An error occurred (ValidationError) when calling the CreateStack operation: S3 error: The specified key does not exist.

3. Use the get_workstation_ip.sh script (Mac/Linux only for now) to get the IP of your workstation

./bin/get_workstation_ip.sh
StackName                                                    WorkstationIP
jmery-GMTest-Chef-Demo-20180530T162128Z                      34.212.179.198

4. Log onto your stack's workstation

   • Workstation credentials are pinned in #chef-demo-project slack channel.
   • If you are not a Chef employee please contact [email protected] to get the username and password.
   • Workstation now supports RDP over HTTPS to help with access where port 3389 may be blocked.

5. Optional: If you want to use Test Kitchen inside your demo environment, you'll need to go into the AWS control panel, select EC2, and then go into 'Key Pairs'. Choose "Import New Key Pair" and import the chef_demo.pub file stored in this repo into the us-west-2 region of your account. Alternatively you can simply edit the existing .kitchen.yml file inside the cookbook with any valid SSH key name in us-west-2 in your account.

6. Optional: To generate CCRs quickly, double-click the 'Generate_CCRs.ps1' link on the desktop. It will trigger client runs on all nodes until closed.

7. Optional: To start a DCA demo, run either the Start_DCA.ps1 or Start_CM.ps1 scripts located in C:\Users\chef\ . This will rebootstrap the environment to prepare for the DCA or Cloud MIgration demos respectively.

8. Report any issues you find here: https://waffle.io/chef-cft/bjc

---