CSC/ECE 517 Spring 2015/ch1a 2 WA - Revision history

Abhanda3 at 03:55, 17 February 2015

2015-02-17T03:55:26Z

← Older revision		Revision as of 03:55, 17 February 2015
Line 26:		Line 26:
	Basically, the chef command tool deals with the actual chef installation wherever it is, either a local installation and on the server. It deals only with itself. Knife, however, deals with the setup of all the communication and objects between the chef server and a chef client node. In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.		Basically, the chef command tool deals with the actual chef installation wherever it is, either a local installation and on the server. It deals only with itself. Knife, however, deals with the setup of all the communication and objects between the chef server and a chef client node. In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.

	~~<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">~~ [[File:chef_knife server.png~~]] <ref>[~~http://dev.classmethod.jp/server-side/chef-server-install~~/ Chef Server~~]~~</ref></div>~~		[[File:chef_knife server.png\|frame\|Source: http://dev.classmethod.jp/server-side/chef-server-install\|center]]

	== Using Knife ==		== Using Knife ==

Abhanda3: /* What is Knife? */

2015-02-17T03:49:48Z

What is Knife?

← Older revision		Revision as of 03:49, 17 February 2015
Line 24:		Line 24:
	* chef-clients installations on management workstations		* chef-clients installations on management workstations

	Basically, the chef command tool deals with the actual chef installation wherever it is, either a local installation and on the server. It deals only with itself. Knife, however, deals with the setup of all the communication and objects between the chef server and a chef client node.		Basically, the chef command tool deals with the actual chef installation wherever it is, either a local installation and on the server. It deals only with itself. Knife, however, deals with the setup of all the communication and objects between the chef server and a chef client node. In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.

	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>

	~~In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.~~

	== Using Knife ==		== Using Knife ==

Wpgallih at 22:25, 16 February 2015

2015-02-16T22:25:16Z

← Older revision		Revision as of 22:25, 16 February 2015
Line 8:		Line 8:
	== Background ==		== Background ==

	Chef streamlines the task of configuring and maintaining a company's servers, and can integrate with cloud-based platforms.		Chef streamlines the task of configuring and maintaining a company's servers, and can integrate with cloud-based platforms. Chef is an IT and environment distribution system, built to be robust and scalable. Imagine a large scale internet based company. Depending on the demands of the company, they may have a need for development workstations, servers for purchasing products, servers for hosting games, even clients for games or accessing databases. All of these different environments are called ''chef client nodes'', with each different setup as different ''environments''. For example, you might have ten chef client nodes set up with the development environment, and one hundred chef client nodes set up with the server environment. The chef server contains all of the ''recipes'', reusable code that may be needed both for use and setup of different chef client nodes, to set up all of the different environments that have been defined. In addition, the chef server works like other versioning software. This means you can roll out updates conveniently to all of the different chef client nodes with ease. This allows the entire collection of chef, the recipes, environments, and nodes, called the ''infrastructure'', to be managed simply and in defined, scalable versions.
	If you ~~are unfamiliar with~~ Chef ~~and how it works~~, check out the comparison between Chef and Puppet here: [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/ch1_1w10_ga] or take a look at the official Chef website here: <ref>[https://www.chef.io/ Chef]</ref>. ~~There~~, a ~~deeper understanding~~ of ~~Chef can~~ be ~~attained~~.		Chef is more complex and allows other little tricks and nuances. If you want to learn more about Chef itself, beyond the description found here, check out the comparison between Chef and Puppet here: [http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/ch1_1w10_ga] or take a look at the official Chef website here: <ref>[https://www.chef.io/ Chef]</ref>, which are the sources for the information in this background. This description just serves to introduce the concept of chef, so that knife's purpose can be understood. These other pages cover the ideas of Chef and how to use it effectively in more detail. In fact, the main site for Chef has an interactive tutorial in setting up a Chef server, without even having to use a personal server or computer. However, the rest of this article will be describing and covering knife.

			== What is Knife? ==

	Chef includes two important command-line tools.		Chef includes two important command-line tools.
Line 15:		Line 17:
	*Chef command-line tool		*Chef command-line tool

	knife is the command-line tool that provides an interface between a local chef~~-repo~~ and the Chef server. ~~Whereas,~~ Chef command-line tool is used while working with the chef repo. Knife helps us to manage the following.		knife is the command-line tool that provides an interface between a local chef client node and the Chef server. Where the Chef command-line tool is used while working with the chef server and repo, Knife helps us to manage the following:

	* Nodes		* Nodes
Line 21:		Line 23:
	* Environments		* Environments
	* chef-clients installations on management workstations		* chef-clients installations on management workstations

			Basically, the chef command tool deals with the actual chef installation wherever it is, either a local installation and on the server. It deals only with itself. Knife, however, deals with the setup of all the communication and objects between the chef server and a chef client node.

	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>

	In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.		In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.

	== Using Knife ==		== Using Knife ==

Wpgallih at 21:12, 9 February 2015

2015-02-09T21:12:49Z

← Older revision		Revision as of 21:12, 9 February 2015
Line 2:		Line 2:
	[[File:workstation.png\|frame\|Source: https://docs.chef.io/chef_quick_overview.html\|right]]		[[File:workstation.png\|frame\|Source: https://docs.chef.io/chef_quick_overview.html\|right]]
	Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.		Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.

			The topic writeup for this page can be found [https://docs.google.com/document/d/1TgBtp7flIPKJwkkShgtcIkt--mtHuwVHsQX6Tpzj1rc/edit here].

Wpgallih: /* Bootstrap Options and Knife Settings */

2015-02-09T21:03:58Z

Bootstrap Options and Knife Settings

@@ Line 95: / Line 95: @@
 '''--bootstrap-curl-options OPTIONS, --bootstrap-install-command COMMAND, --bootstrap-install-sh URL'''
-These commands allow customization of the installation bootstrap performs. They are all mutually exclusive, but allow different ways to perform this customization. The first, bootstap-curl-options, which allows additional cURL options to be performed alongside the bootstrap installation. To learn more about cURL, check out their main web page [http://curl.haxx.se/ here (cURL Home Page)].
+These commands allow customization of the installation bootstrap performs. They are all mutually exclusive, but allow different ways to perform this customization. The first, bootstap-curl-options, which allows additional cURL options to be performed alongside the bootstrap installation. To learn more about cURL, check out their main web page here: ([http://curl.haxx.se/ cURL Home Page]). The second, bootstrap-install-command, allows the execution of another install command on the target node alongside the bootstrap function. The final one, bootstrap-install-sh, allows a custom install script located at the designated URL to be run, following the bootstrap command.
 == References ==
 <references/>

Abhanda3: /* Examples */

2015-02-09T20:59:19Z

Examples

← Older revision		Revision as of 20:59, 9 February 2015
Line 24:		Line 24:
	In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.		In the figure, we can see that how knife provides an interface between local repository's and Chef server at the workstation.

	== ~~Examples~~ ==		== Using Knife ==

	Using Knife is fairly straightforward, with usage following this syntax:		Using Knife is fairly straightforward, with usage following this syntax:

Abhanda3 at 20:57, 9 February 2015

2015-02-09T20:57:52Z

← Older revision		Revision as of 20:57, 9 February 2015
Line 1:		Line 1:
	<font size="5"><b>Knife</b></font>		<font size="5"><b>Knife</b></font>
	[[File:workstation.png\|frame\|Source: https://docs.chef.io/chef_quick_overview.html/\|right]]		[[File:workstation.png\|frame\|Source: https://docs.chef.io/chef_quick_overview.html\|right]]
	Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.		Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.

Abhanda3 at 20:56, 9 February 2015

2015-02-09T20:56:59Z

← Older revision		Revision as of 20:56, 9 February 2015
Line 1:		Line 1:
	<font size="5"><b>Knife</b></font>		<font size="5"><b>Knife</b></font>
			[[File:workstation.png\|frame\|Source: https://docs.chef.io/chef_quick_overview.html/\|right]]
	Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.		Knife is the command line tool for managing Chef nodes. Simply, Chef allows the distribution of server environments between many different servers (called '''nodes'''). Any changes to the primary chef server (called the '''chef repo''' are distributed throughout all the other nodes, while different nodes can have other recipes and send them back to the chef repo. Knife, then, handles the communication between nodes and the chef repo. For example, let's say that there is an object on the chef repo that a node desires. Knife provides the tools to download that object to the node. Knife also allows setting up a node, installing necessary packages, management of users, and much more.

Wpgallih: /* Bootstrap Options and Knife Settings */

2015-02-09T20:49:32Z

Bootstrap Options and Knife Settings

← Older revision		Revision as of 20:49, 9 February 2015
Line 92:		Line 92:
	== Bootstrap Options and Knife Settings ==		== Bootstrap Options and Knife Settings ==
	As one of the most powerful tools knife has to offer, the bootstrap function has many different options available to it. The "Installing Bootstrap" section covered three such options (-x, -P, and --node-name), but there are many more available that are useful. Here are a few that stand out as being useful to someone using knife bootstrap for the first time, or for people who are dealing with something outside of the normal conditions for installing and using knife bootstrap. In addition, adding different settings to the knife.rb file will be covered, for people looking to expand the usage of knife and knife bootstrap. Most of this information is covered in higher detail in the main knife bootstrap page, as well as all the other options. You can check that page out using the reference here.<ref>[http://docs.chef.io/knife_bootstrap.html Knife Boostrap]</ref>		As one of the most powerful tools knife has to offer, the bootstrap function has many different options available to it. The "Installing Bootstrap" section covered three such options (-x, -P, and --node-name), but there are many more available that are useful. Here are a few that stand out as being useful to someone using knife bootstrap for the first time, or for people who are dealing with something outside of the normal conditions for installing and using knife bootstrap. In addition, adding different settings to the knife.rb file will be covered, for people looking to expand the usage of knife and knife bootstrap. Most of this information is covered in higher detail in the main knife bootstrap page, as well as all the other options. You can check that page out using the reference here.<ref>[http://docs.chef.io/knife_bootstrap.html Knife Boostrap]</ref>

			'''--bootstrap-curl-options OPTIONS, --bootstrap-install-command COMMAND, --bootstrap-install-sh URL'''

			These commands allow customization of the installation bootstrap performs. They are all mutually exclusive, but allow different ways to perform this customization. The first, bootstap-curl-options, which allows additional cURL options to be performed alongside the bootstrap installation. To learn more about cURL, check out their main web page [http://curl.haxx.se/ here (cURL Home Page)].

	== References ==		== References ==
	<references/>		<references/>

Abhanda3: /* Background */

2015-02-09T20:44:52Z

Background

← Older revision		Revision as of 20:44, 9 February 2015
Line 13:		Line 13:
	*Chef command-line tool		*Chef command-line tool

	knife is the command-line tool that provides an interface between a local chef-repo and the Chef server. Whereas, Chef command-line tool is used while working with the chef repo.		knife is the command-line tool that provides an interface between a local chef-repo and the Chef server. Whereas, Chef command-line tool is used while working with the chef repo. Knife helps us to manage the following.

			* Nodes
			* JSON data Stores
			* Environments
			* chef-clients installations on management workstations

	<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>		<div class="center" style="width: auto; margin-left: auto; margin-right: auto;"> [[File:chef_knife server.png]] <ref>[http://dev.classmethod.jp/server-side/chef-server-install/ Chef Server]</ref></div>