• Scripting Actions in ManageIQ
  • Updates to Rails and Ruby
    • Updates and Changes in Rails
    • Updates and Changes in Ruby
  • Understanding the Automate Model
    • Automate Model
    • Creating a Domain
    • Editing a Domain
    • Deleting a Domain
    • Importing a Domain from a Git Repository
    • Changing Priority Order of Domains
    • Creating a Namespace
    • Creating a Class
    • Creating a Schema for a Class
    • Editing a Field in a Schema
    • Editing Schema Sequence
    • Adding an Instance to a Class
    • Copying a Class or Instance
    • Relationships
    • Methods
      • Creating a Method
      • Creating a Dynamic Content Dialog
      • Creating a Playbook Automate Method
        • Passing variables between successive playbook methods
    • Expression Methods
      • Input Parameters
        • Optional Input Parameters
      • Creating an Expression Method
    • Simulation
      • Simulating an Automate Model
    • Importing, Exporting, and Resetting the Datastore
      • Exporting All Datastore Classes
      • Importing Datastore Classes
      • Resetting Datastores to the Default
  • Invoking Automate
    • Automate Examples
    • Invoking Automate using a Custom Button
    • Creating a Custom Button Group
    • Creating a Custom Button
    • Creating an Ansible Playbook Button
    • Editing a Custom Button
    • Deleting a Custom Button
    • Setting Enablement and Visibility for Custom Buttons
    • Using a Custom Button
    • Initiating Automate from an Event
    • Creating a Policy for Automate
    • Creating a Custom Automate Action
• Objects
  • Virtual Machine Properties
  • Methods for use in Ruby Scripts
  • Host Properties
  • Provider Properties
  • Storage Properties
• FAQs and Flows
  • Phase 1: Create Provision Request
  • Phase 2: Request Approval
  • Phase 3: Quota Validation
  • Phase 4: Provisioning
  • Phase 5: Retirement
• Inline Method to Create a Provision Request
  • Ruby method
• Migrating Custom Buttons
  • Migrating Custom Buttons

Scripting Actions in ManageIQ

The Automate model provides flexibility to not only change parts of the provisioning process, but also to allow you to automate other operational tasks. Below are some scenarios where the Automate model can help accomplish these tasks.

• Intelligent Workload Management - An enterprise had a requirement that when a virtual machine has reached a High CPU Percent Ready for a specified period of time, a vMotion should occur to a more suitable host. For this reason, VMware’s Distributed Resource Scheduler (DRS) was not practical, as the CPU Ready metric could not trigger DRS. The solution was to leverage ManageIQ Control and ManageIQ Automate to drive the management of this workflow.

• Power on only during business hours - An organization which gave a group of self-service users ManageIQ access had a requirement to only allow certain virtual machines to be powered during business hours. This was solved with ManageIQ Automate.

• Auto-Tagging virtual machines based on file contents - An IT organization needed a way to consume information from a text file on a virtual machine and dynamically populate vCenter. The data used to auto-tag virtual machines is also used to align unmanaged virtual machines to the business.

Updates to Rails and Ruby

Changes within Ruby and Rails versions can create issues for custom code and automation in ManageIQ environments.

Before proceeding with major upgrades that include changes to versions of Ruby and Rails, review the below resources.

Updates and Changes in Rails

See Rails Releases for information on each release of Rails. To compare versions of Rails, see Comparing changes in Rails.

Updates and Changes in Ruby

See Ruby Releases for information on each release of Ruby by version number. To compare versions of Ruby, see Comparing changes in Ruby.

Understanding the Automate Model

Automate enables real-time, bi-directional process integration. This provides users with a method to implement adaptive automation for management events and administrative or operational activities.

Automate Model

The Automate model is arranged to provide an object oriented hierarchy to control automation functions. The model uses the following organizational units arranged in a hierarchy:

• Datastore - The main organization unit that stores the entire model.

• Domains - Domains act as collection of automation functions. Functions are executed depending on the order of Domain priority, which means a function in a Domain with a higher priority overrides the same functions specified in a lower-priority Domain. This allows ManageIQ to specify a core Domain (ManageIQ) but allow users to override automate functions with custom Domains. Each Domain contains a set of Namespaces.

• Namespaces - Containers that organize and categorize functions of the model. Namespaces can contain child Namespaces as well as Classes.

• Classes - Templates for a specific function of the model. Each Class uses a Schema to apply to Instances to populate with default values. Each class also can contain a set of methods.

• Instances - An instance is a version of a class populated with initial configuration data. An instance can include a collection of any number of attributes, calls to methods, and relationships.

• Methods - Methods are functions within the model. Methods use Ruby code to execute various operations needed for a Class.

ManageIQ contains a preconfigured Domain for users:

• ManageIQ - The core domain for ManageIQ Automate operations. This domain is locked with the following Namespaces:

  • Cloud - General cloud instance lifecycle from provisioning, retirement, methods, email.

  • Control - Control contains email alerts for policy controls.

  • Infrastructure - General infrastructure VM lifecycle from provisioning, retirement, methods, email.

  • Integration - Used to interface with systems outside of ManageIQ. Use this namespace to integrate with additional systems.

  • Service - Service lifecycle from provisioning, retirement, methods, email.

  • System - System contains classes that can provide the start points for all ManageIQ Automate activities.

You can copy classes and instances from locked Domains into your own custom domains.

Note:

Changing the existing classes or instances shipped with the product is not recommended because this may hinder the operation of ManageIQ. You can link to these methods using relationships.

To reset the Automate model to default settings, navigate to menu:Automate[Import/Export] and click the Reset option.

Creating a Domain

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Click (Configuration), then (Add a New Domain).

3. Type in a unique Name and Description. Choose if the Domain is Enabled.

4. Click Add.

The new domain is created.

Editing a Domain

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Select the Domain you want to edit.

3. Click (Configuration), then (Edit Selected Domain).

4. Make the required edits.

5. Click Save.

You have edited the selected domain.

Deleting a Domain

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Select the Domain that you want to delete.

3. Click (Configuration), then (Remove This Domain).

4. A window to confirm the removal of Domain appears.

5. Click OK.

The selected Domain is deleted.

Importing a Domain from a Git Repository

ManageIQ can import an Automate domain from a Git repository by specifying a repository and branch, along with user details. Currently, you can only add git domains via the Import/Export area of the user interface.

1. Navigate to menu:Automation[Automate > Import/Export].

2. In Import Datastore via git, enter the Git URL. Select the branch or tag to use.

3. Optionally, enter a Username and Password.

4. Select Verify Peer Certificate if desired.

5. Click Submit.

The new domain is imported via Git repository. Note that the domain is validated on import.

Changing Priority Order of Domains

Functions are executed depending on the order of Domain priority. Use this procedure to change the priority order of domains.

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Select the Domains you want to change the priority order for.

3. Click (Configuration), then (Edit Priority Order of Domains).

4. The list of Domains selected shows up. Note that you cannot change the priority of locked Domains and therefore locked Domains do not show up on the list.

5. Select one or more consecutive groups to move up or down to change their priority as required.

6. Click Save.

Creating a Namespace

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Navigate through the various Domains and Namespaces until you reach the desired location for your new Namespace.

3. Click (Configuration), then (Add a New Namespace).

4. Type in a unique Name and Description.

5. Click Add.

The new Namespace is created.

Creating a Class

1. Navigate to menu:Automation[Automate > Explorer], navigate to the namespace you want to add a class to.

2. Click (Configuration), then (Add a new Class).

3. Type in a unique Name and Description.

4. If you want to use the schema from a class that has already been created, select it from the Inherits From dropdown. If the class that the new class inherits from changes, the new class will also change.

5. Click Add.

The new class is created and you can create a schema, add instances and methods.

Note:

For each class, create a schema if you did not choose to inherit from an existing class. The schema can include attributes, methods, assertions, and relationships.

Creating a Schema for a Class

This procedure shows you how to create a schema.

1. Navigate to menu:Automation[Automate > Explorer], and click the class you want to define a schema for.

2. Click on the Schema tab.

3. Click (Configuration), then (Edit selected Schema).

4. Click (Click to add a new field) to create a new field.

5. Type in a Name for the new field.

6. From Type, select Assertion, Attribute, Method, Relationship, or State.

7. If applicable, select a Data Type and set a Default Value.

8. Type in a user friendly Display Name and Description.

9. Check Sub to enable the substitution syntax of ${}. Uncheck it if you want to use that syntax as a regular string.

10. Fill in Collect and Message as required. Collect is used to roll up values from resolved relationships. For example, a relationship can resolve to a large object tree. Use collect to specify how to pull out data from those child objects into the current object. If you give collect a name value, it will store the method result in an attribute of the current object with that name.

11. On Entry, On Exit, On Error, Max Retries, and Max Time are fields used mostly for state machines. Leave blank if not applicable.

12. Click (Add this entry) to confirm the fields values.

13. For each new field, repeat steps 4 through 10.

14. When you have created all of the fields, click Save.

The class schema is created, and you can now add instances to it.

Note:

You may need to edit a class schema to reorder, add, edit, or remove a field. Classes define the order in which fields are processed and you may need to process some items before others.

Editing a Field in a Schema

This procedure describes how to edit schema fields.

1. Navigate to menu:Automation[Automate > Explorer].

2. Click the class you want to define a schema for.

3. Click the Schema tab.

4. Click (Configuration), then (Edit selected Schema).

5. Make required changes to any of the definitions for the field.

6. To remove a field, click (Click to delete this field from the schema).

7. Click Save when you are finished editing the schema.

Once the schema is created, you can add instances and methods to the class.

Editing Schema Sequence

This procedure shows you how to change schema sequence.

1. Navigate to menu:Automation[Automate > Explorer].

2. Click the class you want to change the schema sequence for.

3. Click the Schema tab.

4. Click (Configuration), then (Edit Sequence).

5. In the Class Schema Sequencing area, click the field you want to change the sequence for.

   • To move a field up in the order of resolving an instance, click (Move selected field up).

   • To move a field down in the order of resolving an instance, click (Move selected field down).

6. Click Save when you are finished editing the sequence.

Adding an Instance to a Class

This procedure shows you how to create an instance.

1. Navigate to menu:Automation[Automate > Explorer].

2. Click the class you want to define a schema for.

3. Click the Instances tab.

4. Click (Configuration), then (Add a new Instance).

5. In the Main Info area, type in a Name, Display Name and Description.

6. In the Fields area, type in an appropriate value for each field, leave the field blank if no value is required, or use the default value.

7. Click Add.

Copying a Class or Instance

1. Navigate to menu:Automation[Automate > Explorer]. The default view is the Datastore.

2. Navigate through the various Domains and Namespaces until you reach the desired class or instance to copy.

3. Click (Configuration), then either (Copy this Class) or (Copy this Instance) depending on the object chosen.

4. Choose the target Domain in the To Domain drop-down menu.

5. The object retains the same path as the From Domain and overrides the class in From Domain if the To Domain has a high priority. You can also untick the Copy to same path option to specify a new Namespace.

6. Click Add.

Relationships

Relationships are used to connect to other instances in the Automation Datastore. Relationships are formed using URI syntax. The following can also be passed through a relationship:

• Use # to set the message to send to the item in the relationship.

• To pass an input to the method use ? followed by the item to pass.

• If you want to use a substitution, the syntax is $\{} with the substitution located between the brackets.

Methods

Methods are pieces of code associated with a class or object to perform a task. ManageIQ allows for Ruby methods or backing a method using an Ansible playbook. You can create your own methods or use relationships to link to pre-existing ones.

ManageIQ ships with a core set of Ruby gems used by the ManageIQ Rails Application. The Ruby gems in this set are subject to change. If you are calling gems using Automate that are no longer in this release, you can install them by using the gem install command.

While gems can be imported into automation methods using require, it is recommended that the authors of the automation methods clearly document the use of gems either in the core set or a custom set. It is the responsibility of the author of such custom automation to own the life cycle of any gem being referenced in those methods.

The Release Notes list Ruby gems that have been added, updated, or removed in the latest version of ManageIQ.

Creating a Method

This procedure shows you how to create a method.

1. Navigate to menu:Automation[Automate > Explorer], navigate to the class where you want to create a method.

2. Click the Methods tab.

3. Click (Configuration), (Add a New Method).

4. In the Main Info area, type in a Name and Display Name.

5. For Location, select inline. Once selected, you will be presented with a Data area in which to write or copy the script.

6. Click Validate to check the syntax.

7. Click Add.

Creating a Dynamic Content Dialog

The procedure describes the steps to create a dynamic content dialog.

1. Navigate to menu:Automation[Automate > Explorer].

2. From the accordion menu, click menu:DOMAIN[Cloud > VM > Operations > Methods].

   Note:

   DOMAIN must be a user-defined Domain and not the locked ManageIQ Domain. If necessary, you can copy the class from the ManageIQ domain into a custom domain.

   This example uses the Cloud Namespace but can also use the Infrastructure namespace.

3. Click (Configuration), then (Add a new Instance).

4. In the Main Info area, enter Name = dynamic_list, replacing dynamic_list with an appropriate name for the method.

5. Enter a Display Name and Description.

6. In the Fields area, enter Value = dynamic_list. Leave the other fields blank or use the default values.

7. Click Add.

8. Navigate to Methods tab.

9. In the Main Info area, enter Name = dynamic_list and populate the Data section with the example automate method below.

10. Click Add.

11. Set the automate entry point for the dialog control; use the new instance created in step four. You can create a new domain and copy the method to that domain.

    #  Automate Method
    
    dialog_field = $evm.object
    
    # sort_by: value / description / none
    dialog_field["sort_by"] = "value"
    
    # sort_order: ascending / descending
    #dialog_field["sort_order"] = "ascending"
    
    # data_type: string / integer
    dialog_field["data_type"] = "integer"
    
    # required: true / false
    # dialog_field["required"] = "true"
    
    dialog_field["values"] = {1 => "one", 2 => "two", 10 => "ten", 50 => "fifty"}
    dialog_field["default_value"] = 2
    

Creating a Playbook Automate Method

ManageIQ can choose an Ansible playbook from a repository and execute it as a method. Each playbook method can take additional input parameters specified by the user.

Important:

• You must first sync your playbook repositories before using them to create a method. See Adding a Playbook Repository in Managing Providers for information on initial playbook repository set-up.

• Using Ansible playbooks to populate dynamic dialog fields is not recommended due to delay times caused by the overhead of interaction between systems.

• Only users with administrator privileges can run a service dialog based on a playbook automate method.

To create a playbook automate method:

1. Navigate to menu:Automation[Automate > Explorer], then click on a domain under Datastore.

2. Under a namespace, select the class for which you want to create a new method.

3. Click the Methods tab.

4. Click (Configuration) then, (Add a New Method).

5. In the Main Info area, select Playbook from the Type dropdown menu.

6. Provide a Name and Display Name.

7. Select a playbook Repository from the list.

   1. Choose a Playbook to use.

   2. Select the Machine Credential the playbook will use when it runs.

   3. Select the Vault Credential to use.

   4. From the Cloud Type list, select a cloud provider.

   5. Choose the Cloud Credential that corresponds to the selected cloud type.

8. Specify the Hosts on which the playbook will run. Choose Localhost or provide unique values in the Specify host values field.

9. Set the Max TTL in minutes. The Time To Live (TTL) field allows you to set the maximum execution time for the playbook to run.

10. Select when to receive Logging Output from the options in the drop-down menu.

11. Use the Escalate Privilege toggle switch to enable user privilege escalation if credentials are called for during the playbook run.

12. Choose a Verbosity value to set the debug level for playbook execution.

13. Add required Input Parameters using the fields and values available. Click the to add additional input parameters.

    Note:

    Input parameters become extra vars, with substitution enabled. This overcomes the lack of a dialog which would normally allow for the input of additional information. For more information on extra vars, see the Ansible documentation.

14. Click Add when finished.

Once created, the domain including your playbook method can be exported to appliances in your testing or production environments or imported in appliances in multiple regions.

Important:

To import a domain with a playbook method, you must have an existing Ansible playbook on the destination environment with the same name or the import will fail.

See Exporting All Datastore Classes for information.

Passing variables between successive playbook methods

Automate designers can pass variables between successive Ansible playbook methods in a state machine using ManageIQ.

To pass variables between Ansible playbook methods, use the set_stats module in your playbooks.

Example.

---
# This playbook prints a simple debug message
- name: Echo Hello, Fred and Wilma
  hosts: localhost

  tasks:
  - name: "playbook1 - testing input vars"
    set_stats:
      data:
        pb_var1a: ""
        pb_var1b: ""

  - debug: msg="Hello,  and "

For more information on the set_stats module, see the Ansible documentation.

Expression Methods

ManageIQ additionally provides support for Expression Methods, that allow you to use advance search filters as Automate Methods, substituting the user input from Automate Objects. Expression methods have several distinct advantages, including: running directly in the worker appliance; removing the overhead of forking a DRb process to run the Automate Methods; no Ruby code required; and prebuilt for Dynamic Dialogs.

Input Parameters

Expression methods allow for substitution of user input through input parameters,

Optional Input Parameters

Note:

If attributes and distinct are not specified we try to store the result in a variable called values with a hash consisting of id and name. This makes it compatible with our existing dynamic dialog result set.

Creating an Expression Method

Expression methods allow you to use advance search filters as automate methods, substituting user input at runtime, and making them ideal for dynamic dialogs.

To create an expression method:

1. Navigate to menu:Automation[Automate > Explorer], then click on a domain under Datastore.

2. Under a namespace, select the class for which you want to create a new method.

3. Click the Methods tab.

4. Click (Configuration) then, (Add a New Method).

5. In the Main Info area, select expression from the drop-down menu.

6. Provide a Name and Display Name.

7. Select an Expression Object from the drop-down menu.

8. In the Expression editor, create the expression by setting the controls and values used at runtime:

   1. Using the drop-down menu, select the value to use. Based on your selection, choose or input additional values from the drop-down menus or text fields that appear.

   2. In the Contains field, input a value or click User will input the value.

   3. Click to complete the expression.

9. Add Input Parameters for each of the user input fields required.

   1. Click to add a new parameter.

   2. Provide a Name, Default Value and select a Data Type for each parameter.

   3. Click to add the parameter.

      Note:

      If User will input the value is checked, arguments for each input parameter names using the prefix “arg”.

      For example, if there are 3 fields then the input parameter names should be arg1, arg2, and arg3. If there are two runtime parameters arg1 and arg2 must be defined in the input parameters. In the default value for these fields values can be substituted from other objects in the Automate Workspace.

10. Click Add.

Simulation

After your model is designed, use the simulate page to test it. It allows you to see the results in tree and XML view.

Simulating an Automate Model

This procedure shows you how to simulate an automate model.

1. Navigate to menu:Automation[Automate > Simulation].

2. In Object Details, select a type of object from /System/Process/ that will initiate the model. The Message should be create. Type in the name of the Request where you are starting from.

   

3. Select the Type of item you want to run the simulation on. Then, select a specific one to use as the example.

   

4. Check Execute Methods if you want to perform the model and not just simulate it.

   

5. Type in the Attribute/Value Pairs fields if applicable.

6. Click Submit.

Click on the Tree View or XML View tabs to see results.

Importing, Exporting, and Resetting the Datastore

The Automate Model can be exported and imported as a YAML file. ManageIQ allows you to back up your model by export. Red Hat may provide you with new or updated classes, and provides an import function for either a class or the entire model. Finally, you can reset the datastore to its default. Always be sure to export the current datastore before importing or resetting.

Note:

The datastores you are exporting or importing between must use the same ManageIQ version.

Exporting All Datastore Classes

This procedure shows you how export datastore classes as a YAML file.

1. Navigate to menu:Automation[Automate > Import/Export].

2. Click (Export all Datastore classes and instances to a file).

3. Follow your browser’s prompts to save the file.

The datastore is zipped and exported as a YAML file.

Importing Datastore Classes

This procedure shows you how to import datastore classes.

1. Navigate to menu:Automation[Automate > Import/Export].

2. Export the datastore so that you have a backup.

3. Click Choose file to navigate to the location of the *.zip file to import.

4. Click Upload.

5. After the file has uploaded, specify the following using the dropdown menus:

   • The domain to import into

   • The domain to import from

   • All namespaces you wish to import

6. Click Commit to finish importing the selected domain.

The datastore is imported from the uploaded YAML files.

Resetting Datastores to the Default

This procedure shows you how reset the datastores to the default.

1. Navigate to menu:Automation[Automate > Import/Export].

2. Export the datastore so that you have a backup.

3. Click (Reset all components in the built-in domains).

4. Click OK.

Invoking Automate

Automate Examples

This chapter describes the ways to invoke an Automate workflow. Automation can be initiated through an alert, an event, a ManageIQ application, or a custom button. The same automation process can be re-used across more than one of these. For example, using automation to remove orphaned virtual machines and instances could be initiated by:

• An administrator request from the ManageIQ console (from a custom button)

• An alert indicating the datastore has less than 20% free-space

• A virtual machine or instance unregistered event is detected

All invocations of an automate model must enter through the /System/Process namespace.

Invoking Automate using a Custom Button

Invoke an Automate model by mapping an Ansible playbook or instance from the /System/Process/Request class to a custom button. Before creating the button, you need to have an Ansible playbook service catalog item or an instance in the /System/Process/Request class to map to it and a button group to assign it to.

Create buttons for a cluster, host, datastore, provider, virtual machines or cloud instances. When the button is clicked, the model or playbook will be invoked for the selected item. For each of these, you can have up to 15 buttons.

Creating a Custom Button Group

This procedure shows you how to create a custom button group.

1. Browse to menu: Automation > Automate > Customization.

2. Click the Buttons accordion.

3. From the Object Types tree, select the type of object you want to create the button group for.

4. Click Configuration, Add a new Button Group.

5. Type in a Button Group Text and Button Group Hover Text, and select the Button Group Image that you want to use.

6. If custom buttons have already been created, assign them to the button group. If not, see Creating a Custom Button.

7. Click Add.

The button group will show in the object type you added the button to.

Creating a Custom Button

This procedure shows you how to create a custom button.

Note:

Custom buttons can be migrated to other ManageIQ appliances. See Migrating Custom Buttons for guidance on migrating custom buttons to a new ManageIQ appliance.

1. Browse to menu: Automation > Automate > Customization.

2. Click the Buttons accordion.

3. From the Object Types tree, select the type of object you want to create the button for.

4. Click Unassigned Buttons.

5. Click Configuration, then Add a new Button.

   Note:

   If Add a new Button is not available, that means you have not created a button group for that object. To continue, create a button group first. See Creating a Custom Button.

6. Under the Options tab:

   1. Select the Button type from the list.

   2. Enter button Text and Hover Text, and select the Icon and Icon Color to use.

   3. Select a Dialog if applicable.

   4. Check Open URL to open a browser window for the custom URL returned when the button is executed.

   5. Choose a Display For option for the button.

   6. Select a Submit parameter to choose how to submit objects to automate. Selecting Submit All will pass all objects at once when the button is executed, while choosing One by one will run execute the button action each time per object.

7. Under the Advanced tab:

   1. Set button Enablement. Click Define Expression to access the expression editor tool. Enter Disabled Button Text to display when the custom button is disabled.

   2. Use Visibility to determine button appearance based on a custom expression. Click Define Expression to access the expression editor tool.

      Note:

      For more about setting visibility and enablement for a custom button, see Filtering.

   3. In Object Details, select Request from the /System/Process/ dropdown. By default, the message is create. Do not change it.

   4. Enter a Request name for the /System/Process/Request instance.

   5. Enter the Attribute/Value Pairs fields if applicable.

   6. Set Role Access. Selecting <By Role> will display available roles. Check applicable roles.

8. Click Add when you have confirmed that the button accomplishes the task you want.

The button will show in the object type you added the button to.

Please note that there are two ways of creating custom buttons, and creation through the “Automation > Automate > Generic Objects” screen will necessitate adding an attribute/value pair that is not required when adding through the “Automation > Customization > Buttons” screen.

Creating an Ansible Playbook Button

ManageIQ includes an option to create an Ansible Playbook custom button. This feature allows users to select a playbook to run as well as an inventory target to run it against. An Ansible playbook type button can be defined for any object type available.

Note:

An Ansible Playbook catalog item must exist in order to create an Ansible Playbook custom button. For more information, see Creating an Ansible Playbook Service Catalog Item in the Provisioning Virtual Machines and Hosts guide.

1. Navigate to menu:Automation[Automate > Customization].

2. Click the Buttons accordion.

3. From the Object Types tree, select the type of object you want to create the button for.

4. Click Unassigned Buttons.

5. Click (Configuration), then (Add a new Button).

   Note:

   If (Add a new Button) is not available, that means you have not created a button group for that object. To continue, see Creating a Custom Button Group.

6. Select Ansible Playbook from the Button Type drop-down menu.

7. From the Playbook Catalog Item choose a playbook-backed catalog item to run.

8. Choose a host from the Inventory against which to run the playbook. If Specific Hosts is selected, input the IP address or DNS names for each host in the text field, separating each with a comma.

   Note:

   ManageIQ supports two configurations for host value input:

   • To allow user-provided host values, set the custom button to Specific Hosts and leave the associated text field blank.

   • To use admin-specified host values, remove the Hosts field when creating the dialog the service uses. In this configuration, the field will not appear to users. See Service Dialogs for information on generating a service dialog.

9. Type in a Text and Hover Text, and select the Icon you want to use.

10. Select an Icon Color from the color selection palette that pops up.

11. Check Open URL to open a browser window for the custom URL returned when the playbook is run.

12. Select display options for the Ansible Playbook button from the Display for drop-down menu. Choose for the button to display in the list view, for single entities, or both.

13. Choose how to submit objects to automate by selecting an option from the Submit drop-down menu. Selecting Submit all will pass all objects at once when the playbook is executed, while choosing One by one will run the the playbook each time per object.

14. Click Add when you have confirmed that the button accomplishes the task you want.

Editing a Custom Button

This procedure shows you how to edit a custom button.

1. Navigate to menu:Automation[Automate > Customization].

2. From the Object Types dropdown, select the type of object you want to edit the button for.

3. Click the button you want to edit.

4. Click (Configuration), (Edit this Button).

5. Modify as required.

6. Click Save.

Deleting a Custom Button

This procedure shows you how to delete a custom button.

1. Navigate to menu:Automation[Automate > Customization], then select the Buttons accordion.

2. From the Object Type tree in the accordion menu, select the type of object you want to remove the button from.

3. Click (Configuration). then click (Remove this button).

4. Click OK to confirm that you want to delete this button.

Setting Enablement and Visibility for Custom Buttons

ManageIQ adds methods for evaluating an expression to determine whether a custom button is visible and enabled. Each method has a target object, for example, a virtual machine or host, and expressions can set a custom button to visible, hidden, or disabled.

Note:

Filtering works on single objects and is not applicable to lists.

To apply filtering actions to a custom button:

1. Navigate to menu:Automation[Automate > Customization].

2. Click the Buttons accordion. Select the custom button to use.

3. Click (Configuration), then (Edit this Button).

4. Click the Advanced tab.

5. To set enablement filtering on a custom button:

   1. Under Enablement, click on Define Expression.

   2. Create a visibility expression using the expression editor tools.

   3. Click (Confirm) when finished defining the expression.

   4. Provide Disabled Button Text in the field.

6. To set visibility filtering on a custom button:

   1. Under Visibility, click on Define Expression.

   2. Create a visibility expression using the expression editor tools.

   3. Click (Confirm) when finished defining the expression.

7. Click Save.

Using a Custom Button

This procedure shows you how to use custom buttons to invoke a cluster, host, datastore, provider, virtual machine or instance.

1. Go to the page for the item that you created a button for.

2. Click the custom button group from the taskbar, and then your custom button.

The automate model is invoked for the specified item.

Initiating Automate from an Event

You can also use a ManageIQ Policy Event to initiate automation. You can either use the provided Raise Automation Event action or create a custom automation action. The first case will start in the /System/Process class, but then go to the Event that initiated the Automate model in the /System/Process/Event Class. If you create your own custom action, it will start from the /System/Process class and then go to the /System/Process/Request Class instead.

For example, suppose that you always want the same Automate model to occur when a virtual machine is created. You would use the Raise Automation Event Action. There are instances in the /System/Process/Event Class for the following Events that you can select as part of a Policy:

Creating a Policy for Automate

This procedure shows you how to create a policy for automate.

1. Navigate to menu:Control[Explorer].

2. Click the Policies accordion, and select Control Policies.

3. Select Vm Control Policies.

4. Click (Configuration), then (Add a New Control Vm Policy).

5. Type in a Description.

6. Uncheck Active if you do not want this policy processed even when assigned to a resource.

7. Click Add. You are brought to the page where you add conditions and events to your new policy.

8. Click (Configuration), then (Edit this Policy’s Event assignments).

   • Check the events you want to use to send to an Automate Model.

   • Click Save.

   • From the Events area, click on the Description of the Event you want to assign an action to.

   • Click (Edit Actions for this Policy Event).

9. Select Raise Automation Event, and click (Move selected Actions into this Event).

10. Click Save.

You can now assign this policy to a Policy Profile. Then, assign the policy profile to the virtual machines. Every time this event happens on the virtual machine the appropriate Automate Model will be initiated.

Note:

If you want the policy to initiate an Automate Model from the /System/Process/Request class, then you can create your own custom action. Be sure to have an instance in the /System/Process/Request class for it to map to.

Creating a Custom Automate Action

This procedure shows you how to create a custom Automate action.

1. Navigate to menu:Control[Explorer] accordion.

2. Click the Actions accordion.

3. Click (Configuration), then (Add a new Action).

4. Type in a Description for the Action.

5. Select Invoke a Custom Automation from Action Type.

6. In Custom Automation,

   • For Message, type create.

   • For Request, type in the name of the instance of the /System/Process/Request Class in the second.

7. Type in the Attribute/Value Pairs fields if applicable.

8. Click Add.

The action is created and can be added to a policy.

Objects

Virtual Machine Properties

When using these items in a method, prefix them with vm.. For example: vm.storage_id.

Virtual Machine Properties

Methods for use in Ruby Scripts

To use one of these in one of your own Ruby methods, use the syntax of vm.method. For example, to reboot the guest operating system, use vm.rebootGuest.

Host Properties

When using these items in a method, prefix them with host, such as host.ems_id.

Provider Properties

When using these items in a method, prefix them with ems, such as ems.ems_id.

Storage Properties

When using these items in a method, prefix them with storage, such as storage.name.

Storage Properties

FAQs and Flows

Phase 1: Create Provision Request

Phase 2: Request Approval

Phase 3: Quota Validation

Phase 4: Provisioning

Target Type: Cloning a Template to a Virtual Machine.

Target Type: Clone to Template.

Phase 5: Retirement

Inline Method to Create a Provision Request

Ruby method

# ManageIQ Automate Method
#
$evm.log("info", "ManageIQ Automate Method  Building VM Provisioning Request Started")
#
 
prov= $evm.root['miq_provision']

  # arg1 = version
  args = ['1.1']
  # arg2 = templateFields
  args << {'name' => 'App'}
  # arg3 = vmFields
  args << {'vm_name' => 'CRM_APP', 'request_type' => 'template'}
  # arg4 =  requester
  args << {'owner_email' => 'admin@asd.com', 'owner_last_name' => 'Admin', 'owner_first_name' => 'Admin', 'user_name' => 'admin'}
  # arg5 =  tags
  args << {'crm' => 'true'}
  # arg6 =  WS Values
  args << nil
  # arg7 = emsCustomAttributes
  args << nil
  # arg8 = miqCustomAttributes
  args << nil

$evm.log("info","Building provisioning request with the following arguments: <#{args.inspect}>")
result = $evm.execute('create_provision_request', *args)

Migrating Custom Buttons

Migrating Custom Buttons

This workflow demonstrates how to export custom buttons from one ManageIQ appliance and import them in another ManageIQ appliance.

1. Export custom buttons from the source ManageIQ appliance:

   1. SSH into the ManageIQ appliance as root.

   2. Create a temporary directory:

      # mkdir /tmp/custom_buttons
      

   3. Browse to the Virtual Management Database (VMDB) directory:

      # vmdb
      

   4. Export custom buttons using the following rake command:

      # rake evm:export:custom_buttons -- --directory /tmp/custom_buttons
      

   5. Confirm the yaml file was created by navigating to the new directory:

      # cd /tmp/custom_buttons
      

2. Copy the directory to the target ManageIQ appliance:

   scp -r /tmp/custom_buttons/ hostname:/tmp/custom_buttons
   

3. Import custom buttons on the target ManageIQ appliance:

   1. SSH to the target ManageIQ appliance as root.

   2. Browse to the VMDB directory:

      # vmdb
      

   3. Import custom buttons using the following rake command:

      # rake evm:import:custom_buttons -- --source /tmp/custom_buttons
      

To verify successful import of custom buttons:

1. Log in to the target ManageIQ appliance.

2. Browse to menu: Automation > Automate > Customization.

3. Click Buttons in the accordion menu.

Imported buttons will appear under the parent Object Type.