kmacgugan/gist:45da9588c1c115851859

## gistfile1.txt
Expediters international. Older version in use.
-	Had chef for 3 years
-	10.16 in prod currently, hiring chef to do upgrade.
-	Clients 11.6 in production
-	Seen demos of analytics and delivery but have not used
-
Team is composed of “Configuration engineers” and a dev.

Sysadmins install packages, not these guys. SA would set up server and then give it to them. SA have seen chef and are not interested in it.
-	As a dev, use chef for porting to linux activities
-	Using chef to deploy application, jre
-	This team sets up run time environment
-	Not everyone is using chef to deploy their applications so there is a fracture within organization, politics involved and don’t have someone from above to lead change.
-	Previous world was managed by shell scripts
-	Behind the scenes work is low priority due to lower visibility

How chef is used
- Jenkins gets war file into nexus
- Cookbook pulls from nexus and deploys to machine where it runs on tomcat.
- Uses knife to check status on the nodes, see if they are converging.
	- Would be nice to have a dashboard that shows node status without having to do work.
	- Not have to converge to see status.
- Setting up cookbooks for applications
- Use a lot of shared servers, want to keep tomcat on the same version, can affect 7 different applications
- Predominately solaris 10 servers at this moment, moving to linux.

Pains
- Failover process is fairly manual.
- Have load balancer for central but not for branch sites.
- Branch sites have to have their own servers.
- Each server and vm is a snowflake hand crafted by the server team.
- When using windows, have linux vm but have to go back to windows to run knife. Can’t have a vm in vm with 64b
- UI is slow in private chef 10. Getting slower and slower with 800+ nodes

UI use
-	Do queries for version control.
-	Use UI do confirm changes made via UI have taken affect. Not always the case.
-	Add base cookbooks to nodes after chef client installed.
-	Most runlist use through the UI.
Wants
-Want to do a bare metal server spin up with chef but haven’t had time. Want a demo to show.
- Audit ability that new client provides (not yet on new client).
- Audit of deployments
- Want to know which boxes are “deviant” boxes.
- Delivery sounds promising, currently doing a lot of deployments manually
- Security uses splunk, seeing data from logs in analytics would be nice. Seeing what versions etc. 80k/500gb for splunk
	Expediters international. Older version in use.
	- Had chef for 3 years
	- 10.16 in prod currently, hiring chef to do upgrade.
	- Clients 11.6 in production
	- Seen demos of analytics and delivery but have not used
	-
	Team is composed of “Configuration engineers” and a dev.

	Sysadmins install packages, not these guys. SA would set up server and then give it to them. SA have seen chef and are not interested in it.
	- As a dev, use chef for porting to linux activities
	- Using chef to deploy application, jre
	- This team sets up run time environment
	- Not everyone is using chef to deploy their applications so there is a fracture within organization, politics involved and don’t have someone from above to lead change.
	- Previous world was managed by shell scripts
	- Behind the scenes work is low priority due to lower visibility

	How chef is used
	- Jenkins gets war file into nexus
	- Cookbook pulls from nexus and deploys to machine where it runs on tomcat.
	- Uses knife to check status on the nodes, see if they are converging.
	- Would be nice to have a dashboard that shows node status without having to do work.
	- Not have to converge to see status.
	- Setting up cookbooks for applications
	- Use a lot of shared servers, want to keep tomcat on the same version, can affect 7 different applications
	- Predominately solaris 10 servers at this moment, moving to linux.

	Pains
	- Failover process is fairly manual.
	- Have load balancer for central but not for branch sites.
	- Branch sites have to have their own servers.
	- Each server and vm is a snowflake hand crafted by the server team.
	- When using windows, have linux vm but have to go back to windows to run knife. Can’t have a vm in vm with 64b
	- UI is slow in private chef 10. Getting slower and slower with 800+ nodes

	UI use
	- Do queries for version control.
	- Use UI do confirm changes made via UI have taken affect. Not always the case.
	- Add base cookbooks to nodes after chef client installed.
	- Most runlist use through the UI.
	Wants
	-Want to do a bare metal server spin up with chef but haven’t had time. Want a demo to show.
	- Audit ability that new client provides (not yet on new client).
	- Audit of deployments
	- Want to know which boxes are “deviant” boxes.
	- Delivery sounds promising, currently doing a lot of deployments manually
	- Security uses splunk, seeing data from logs in analytics would be nice. Seeing what versions etc. 80k/500gb for splunk