- #XL DEPLOYIT HOW TO#
- #XL DEPLOYIT INSTALL#
- #XL DEPLOYIT SOFTWARE#
- #XL DEPLOYIT CODE#
The rule matches on deltas with the operations CREATE and MODIFY. The scope is deployed because this rule must contribute a step for every instance of example.ArtifactDeployed in the deployment. Use a descriptive name that includes the name of the plugin and the type and operation the rule responds to. The name _MODIFY identifies the rule in the system. 
example.ArtifactDeployed CREATE MODIFY scripts /deploy -artifact To define an XML rule for the CI in xl-rules.xml:
The generated deployable example.Artifact extends from udm.BaseDeployableFileArtifact. The deployed example.ArtifactDeployed extends from udm.BaseDeployedArtifact, which contains a file property that the step uses. example.Server extends from udm.BaseContainer and has a host property that refers to a CI of type overthere.Host. In synthetic.xml, add a type definition called example.ArtifactDeployed for the application and add a container type named example.Server: Runs a script that installs the artifact in the correct location. Start with an application that contains one artifact and deploy the artifact to a server. For more information about troubleshooting the rules configuration, refer to Best practices for rules. Mistakes in the definition of scripts or expressions usually appear in the server log when you execute a deployment. If you make a mistake in the definition of synthetic.xml or xl-rules.xml, the server will return an error and may fail to start. Use this when you are developing a plugin. You can configure Deploy to periodically rescan xl-rules.xml and the ext folder and apply any changes that it finds. The structure of the ext folder after you finish this tutorial:Īfter you change synthetic.xml, you must restart the Deploy server.īy default, you must also restart the Deploy server after you change xl-rules.xml and scripts in the ext folder. Place the additional scripts that you will define in the ext folder. xl-rules.xml, which contains the rules that are defined. synthetic.xml, which contains the configuration item (CI) types that are defined. To configure Deploy to use the examples in this tutorial, you must add or modify the following files in the ext folder of the Deploy server: To run the examples in this tutorial, no specific configuration or plugin is required. #XL DEPLOYIT CODE#
Tip: The code provided in this tutorial is available as a demo plugin in the samples directory of your Deploy installation. You are familiar with the objects and properties available in rules, as described in Objects and properties available in rules.Understand the concepts of Deploy planning, as described in Understanding Deploy architecture.
#XL DEPLOYIT HOW TO#
You must know how to create CI types, as described in Customizing the Deploy type system.Requirements for you to use this tutorial: Waits a specific interval to start the deployment.This tutorial describes the process of using rules to create an new Deploy plugin. You can use XML or Jython to specify the steps that belong in a deployment plan and how the steps are configured. This functionality depends on puppetdb.The rules system works with the Deploy planning phase. This module makes use of the puppetdbquery module to distribute sshkeys across the infrastructure (optional).This module makes use of exported resources (optional) if you descide to use this functionallity please configure this in your nf file on the master.installs compatible java version (optional).xldeploy repository configuration items.
installation/service/configuration files for XL Deploy. It can take care of installing XL Deploy servers as well as integrate middleware components elsewhere in your infrastructure. #XL DEPLOYIT SOFTWARE#
This module enables you to tie this deployment software into your puppet environment. XL Deploy is a kick-ass modular platform independant software deployment system.
#XL DEPLOYIT INSTALL#
The xldeploy module enables you to install and manage large XL Deploy enabled infrastructures. THIS CODE AND INFORMATION ARE NOT SUPPORTED BY XEBIALABS. IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESSįOR A PARTICULAR PURPOSE. THIS CODE AND INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR Reference - An under-the-hood peek at what the module is doing and howĭevelopment - Guide for contributing to the module Usage - Configuration options and additional functionality Setup - The basics of getting started with puppet-xldeploy Module Description - What the module does and why it is useful
0 kommentar(er)
