Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Application Release Automation1.81

Use > Create Designs > Topology designs

Topology designs

Topology designs are typically used for Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) deployments that are enabled via Chef, Puppet, Server Automation and Operations Orchestration flow-based components.

Topology designs are declarative in nature and do not include explicit actions or sequencing. The provisioning sequence is inferred by the relationships that exist between components in a topology design.

A topology design is composed of components. Each component can have a relationship with other components. For example, you might define a relationship between a server component and a networking interface component. Each component can also have properties, such as an IP address, password, or name. See Components .

When a topology design is associated with a release pipeline process, it is referred to as an application design. When it is associated to microservices, it is referred to as a service design.

Component types

A component represents one service design element that is required to deploy a service. A topology design can include concrete components and capabilities.

A concrete component is defined in the design as a specific service, such as a vCenter server.

A concrete component is deployed as defined and does not require composition.
A capability is a component that can be fulfilled by any service that meets its criteria, such as a web server that could be fulfilled by either Apache HTTP Server or Apache Tomcat. Capabilities are identified in the designer by angled brackets, such as <<Server>>.

A capability must be matched to an service design or a microservice to be fulfilled.

See Topology composition

Topology design versions

A version of a topology design is where you add components, define relationships, and enter property values for a design. Each version can be edited and configured as needed. Throughout the topology designs area, the version identifier is shown at the top of the window under the display name.

See Topology design versions

Send Help Center feedback