45. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 10/2/2017 1:40:04 PM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

45.1 Files compared

#	Location	File	Last Modified
1	chef-repo.zip\chef-repo\project_cookbooks\common	README.md	Thu Mar 23 16:44:18 2017 UTC
2	chef-repo.zip\chef-repo\project_cookbooks\common	README.md	Mon Oct 2 12:38:45 2017 UTC

45.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	2	126
Changed	1	2
Inserted	0	0
Removed	0	0

45.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

45.4 Active regular expressions

No regular expressions were active.

45.5 Comparison detail

	1	common Coo kbook
	2	========== =====
	3	cookbook f or common funtionali ty across the Automa ted Infras tructure D evelopment Kit
	4
	5	Attributes
	6	----------
	7
	8	find_nodes .rb librar y
	9	---------- ---------- -
	10	#### Descr iption
	11	This libra ry is used to provid e a helper method fo r searchin g for node s in the c urrent sta ck with a particular role.
	12
	13	#### Usage
	14	Find nodes with the role 'role _name' and in the cu rrent stac k:
	15	```ruby
	16	find_node_ by_role("r ole_name", node[:sta ck])
	17	```
	18
	19	Find nodes with the role 'role _name' and in the cu rrent stac k (where i f no node is found, an alterna te node ca n be used) :
	20	```ruby
	21	find_node_ by_role("r ole_name", node[:sta ck], "alt_ role_name" )
	22	```
	23
	24	Find optio nal nodes with the r ole 'role_ name' and in the cur rent stack (where th e node is not requir ed and the deploymen t can cont inue witho ut returni ng any nod e data):
	25	```ruby
	26	find_optio nal_node_b y_role("ro le_name", node[:stac k], "alt_r ole_name")
	27	```
	28
	29	#### Examp les
	30	1. when se arching fo r rdk, if no rdk nod es are fou nd we must exit the deployment because r dk is requ ired.
	31	```ruby
	32	find_node_ by_role("r dk", node[ :stack])
	33	```
	34
	35	2. when se arching fo r pjds, if no pjds n odes are f ound we ca n use the ip address of a jds node.
	36	```ruby
	37	find_node_ by_role("p jds", node [:stack], "pjds")
	38	```
	39
	40	3. when se arching fo r jbpm, if no jbpm n odes are f ound we ca n continue without a dding jbpm to the co nfiguratio n.
	41	```ruby
	42	find_node_ by_role("j bpm", node [:stack])
	43	```
	44
	45	#### Creat ing a data _bag to re present a chef node
	46	In product ion enviro nments, ma ny of the local/deve lopment mo cks will n ot exist a nd instead will be r eplaced by the actua l servers.
	47	In order t o allow ou r deployme nts to con nect to th e actual s ervers, th ere will n eed to be data_bag_i tems to re present th ese nodes.
	48	The find_n ode_by_rol e definiti on will se arch for a data bag with the n ame of nod e[:stack] and if fou nd, will a ttempt to find a dat a bag item with the name of th e role bei ng searche d.
	49
	50	Typically, the ipadd ress is th e target o f the node search, s o at the v ery least the data b ag item sh ould inclu de values for id, ip address, s tack and r oles.
	51
	52	```json
	53	{
	54	"id": "m achine",
	55	"ip_addres s": " IP ",
	56	"stack": "example- stack",
	57	"roles": [
	58	"examp le",
	59	"machi ne_role"
	60	]
	61	}
	62	```
	63
	64	Authors: t eam-milkyw ay@vistaco re.us