knife-index(1)

Usage

knife index rebuild (options)

Overview

Rebuilds all the search indexes on the server. This is accomplished by deleting all objects from the search index, and then forwarding each item in the database to chef-expander(8) via rabbitmq-server(1). Depending on the number of objects in the database, it may take some time for all objects to be indexed and available for search.

Documentation

This manual page was written by Joshua Timberman [email protected]. Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.

Chef

Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home

knife-search(1) The man page for the knife search subcommand. Search indexes allow queries to be made for any type of data that is indexed by the Chef server, including data bags (and data bag items), environments, nodes, and roles. A defined query syntax is used to support search patterns like exact, wildcard, range, and fuzzy. A search is a full-text query that can be done from several locations, including from within a recipe, by using the search subcommand in knife, the search method in the Recipe DSL, and by using the /search or /search/INDEX endpoints in the Chef server API. The search engine is based on Apache Solr and is run from the Chef server. The knife search subcommand is used run a search query for information that is indexed on a Chef server. Syntax This subcommand has the following syntax: where INDEX is one of client, environment, node, role, or the name of a data bag and SEARCH_QUERY is the search query syntax for the query that will be executed. INDEX is implied if omitted, and will default to node. For example: will return something similar to: and is the same search as: If the SEARCH_QUERY does not contain a colon character (:), then the default query pattern is tags:*#{@query}* OR roles:*#{@query}* OR fqdn:*#{@query}* OR addresses:*#{@query}*, which means the following two search queries are effectively the same: or: Options This sub-command has the following options: Examples To search for the IDs of all nodes running on the Amazon EC2 platform, enter: to return something like: To search for the instance type (flavor) of all nodes running on the Amazon EC2 platform, enter: to return something like: To search for all nodes running Ubuntu, enter: To search for all nodes running CentOS in the production environment, enter: To find a nested attribute, use a pattern similar to the following: To build a search query to use more than one attribute, use an underscore (_) to separate each attribute. For example, the following query will search for all nodes running a specific version of Ruby: To build a search query that can find a nested attribute: To test a search query that will be used in a knife ssh command: where the query in the previous example will search all servers that have the web role, but not on the server named web03.

Mentioned on this page

chef-expander(8) rabbitmq-server(1) start RabbitMQ AMQP server

Usage

Overview

Documentation

Chef

See also

Mentioned on this page