Effects on your local machine

Some of the commands we run here might edit some files, or change the state of some programs on your machine. To keep those effects clear, we documented them here by affected modules.

• /etc/hosts: Failure to update this file with the correct values will prevent you from accessing the devstack on your remote machine. This file will be automatically updated every time you:
  • Start an instance. (instance.start)
  • Stop an instance. (instance.stop)
  • Delete an instance. (instance.delete)
  • Setting up an instance. (instance.setup or instance.setup.image)
• ~/.ssh/config: Failure to update this file will prevent the toolkit from having an appropriate connection with the remote machine. This file will be automatically updated every time you:
  • Start an instance. (instance.start)
  • Setting up an instance. (instance.setup or instance.setup.image)
• ~/.ssh/known_hosts: Failure to update this file will complicate the process of connecting to your remote machine using SSH and will require you to manually keep editing the file. To make this easier on you, this file will be automatically updated every time you:
  • Start an instance. (instance.start)
  • Setting up an instance. (instance.setup or instance.setup.image)
• ssh-agent: Failure to add your $SSH_KEY to you the ssh-agent will prevent your remote machine from accessing private repos on your github account and will require you to manually setup private keys on the machine. We will make sure that the record exists every time you:
  • Start an instance. (instance.start)
  • Setting up an instance. (instance.setup or instance.setup.image)
• TMP_DIR: A new directory will be created for you in the place you define in your .env file. This directory will hold the mounts and and any other required data we need to keep track of. An interaction with this directory will happen every time you:
  • Mount your devstack. (devstack.mount)
  • Unmount your devstack. (devstack.unmount)