Section 5-BootstrapNode

Step10:-Get A Node

In Brief,

1. Operation Marked as 7 in system diagram, to verify that boot strap node is available.
2. Operation marked as 7 in system diagram, is from local to AWS workstation instance.
3. Verify connectivity in the to-be boot-strapped node.
4. Upload the starter kit to to-be boot-strapped node.

Notes,

1. Starter kit is nothing by SSL and SSH connection configuration to chef server.
2. Starter kit folder structure is self explanatory.

Step11:-Keys For Connecting To Bootstrap

In Brief,

1. Use the node to bootstrap.
2. By boot strap, we bootstrap/jump start a node with the needed cookbooks installed and running.
3. Bootstrapping is done by manually in this step from the AWS Workstation instance.
4. Step configured as 8 in system diagram.

Notes,

1. Basically bootstrapped a node.
2. Formed the bootstrap command, by referring the ssh command.
3. knife uses nothing but uses SSH internally.
4.[Hint] You may try by choosing separate ssh key pair for boot strap node and workstation instance.

Step12:-Bootstrap

In Brief,

1. The same keys we use in (7) as marked in system diagram is transferred to Workstation AWS instance.
2. Now the same keys are used to connect to boot strap node.
3. Step configured as 8 in system diagram.

Notes,

1. Simply color coded to avoid confusion in ssh keys.
2. Verified the managed nodes in chef server.
3. So basically from the work station instance we told the chef server to boot strap a node of given hostname.

Step13:-Verify Bootstrapped Node

In Brief,

1. Verify that cook book changes are deployed by chef server.
2. Checked by verifying the modified page is displayed on localhost (public dns).

Notes,

1. Did an update to cookbook.
2. Verified the result.
3. Note "ohai",the host displayed on page and host of the boot strapped node.

• <--Previous
• Next-->