ganeshmaharaj · February 3, 2016 22:35
diff --git a/Doc Flow b/Doc Flow
 GENERAL
 - a reference diagram and how a general layout would look like? (I can draw out the one i have if that will help)
 - A bifrost deploy for dummies (step-by-step install guide) using the above layout. (What you want to configure, where, why, how)
  - Eg: if you use ubuntu, this is what you change
  - If you want to use your own DHCP server, this is what you change.
  - if you want to use static IPs, this is what you change/modify/add to get the machines the right data
 - Please correct me on this, if bifrost runs the DHCP server it is best to set dhcp_pool_start, end, static mask etc.. Would be nice to say that in the above guide.
 - Also i think the UUID we use in the baremetal.json is made up (random generated) and has nothing to do with the UUID of the machine you find the BIOS. Would be nice to state this as well in the document. :)
 - When an install is called, explain what happens. What the playbook does, what roles are called and what it the outcome of that.
 - various roles used, but READMEs arent linked. Would be great to have them all linked to a common top-level readme with a reading flow on them.
 W.r.t VAGRANT
 - What is the bridge network for? Some explanation around that. When we use vagrant for deploy, the bridge network is always the one where we deploy. Some additional comments to make sure various configs are set properly to get the right URL for qcow or configdrive download.

 Too much of a stretch goal. I would love to submit a patch for this.
 Pass the ansible.extra_vars from VagrantFile to the install.yml playbook. This way we can add more details to it, and that data will be passed to both the image create and the bifrost install playbooks.
	GENERAL
	- a reference diagram and how a general layout would look like? (I can draw out the one i have if that will help)
	- A bifrost deploy for dummies (step-by-step install guide) using the above layout. (What you want to configure, where, why, how)
	- Eg: if you use ubuntu, this is what you change
	- If you want to use your own DHCP server, this is what you change.
	- if you want to use static IPs, this is what you change/modify/add to get the machines the right data
	- Please correct me on this, if bifrost runs the DHCP server it is best to set dhcp_pool_start, end, static mask etc.. Would be nice to say that in the above guide.
	- Also i think the UUID we use in the baremetal.json is made up (random generated) and has nothing to do with the UUID of the machine you find the BIOS. Would be nice to state this as well in the document. :)
	- When an install is called, explain what happens. What the playbook does, what roles are called and what it the outcome of that.
	- various roles used, but READMEs arent linked. Would be great to have them all linked to a common top-level readme with a reading flow on them.
	W.r.t VAGRANT
	- What is the bridge network for? Some explanation around that. When we use vagrant for deploy, the bridge network is always the one where we deploy. Some additional comments to make sure various configs are set properly to get the right URL for qcow or configdrive download.

	Too much of a stretch goal. I would love to submit a patch for this.
	Pass the ansible.extra_vars from VagrantFile to the install.yml playbook. This way we can add more details to it, and that data will be passed to both the image create and the bifrost install playbooks.