diff --git a/content/about/_index.md b/content/about/_index.md index 905797412..3cf52e34f 100644 --- a/content/about/_index.md +++ b/content/about/_index.md @@ -1,6 +1,6 @@ --- -title: About Cloudify -description: Cloudify is an open-source cloud orchestration framework. which enables you to model applications and services and automate their entire life cycle +title: Overview +description: This product provides an open-source cloud orchestration framework enabling you to model applications and services, and automate their entire life cycle. canonical: xxx.yyy weight: 10 alwaysopen: false diff --git a/content/about/what-is-cloudify.md b/content/about/introduction.md similarity index 99% rename from content/about/what-is-cloudify.md rename to content/about/introduction.md index 39618ec1a..bc22af992 100644 --- a/content/about/what-is-cloudify.md +++ b/content/about/introduction.md @@ -1,9 +1,9 @@ --- -title: What Is Cloudify? +title: Introduction category: Introduction draft: false weight: 100 -aliases: /intro/what-is-cloudify/ +aliases: /intro/introduction/ --- {{< param product_name >}} is an open-source multi-cloud and edge orchestration platform. diff --git a/content/about/cloudify-manager.md b/content/about/manager-overview.md similarity index 77% rename from content/about/cloudify-manager.md rename to content/about/manager-overview.md index e09262dd8..84701aec9 100644 --- a/content/about/cloudify-manager.md +++ b/content/about/manager-overview.md @@ -1,5 +1,5 @@ --- -title: Cloudify Manager +title: Manager Overview category: Introduction draft: false weight: 200 @@ -28,6 +28,6 @@ In addition, the {{< param cfy_manager_name >}}: * Retains a history of metrics and events * Manages agents running on an application's host machines -Although you can use Cloudify to provision resources directly from the CLI, use Cloudify Manager to manage production-level applications. +Although you can use {{< param product_name >}} to provision resources directly from the CLI, use {{< param cfy_manager_name >}} to manage production-level applications. -For more information about Cloudify Manager, see the Cloudify Manager section later in this user's guide. +For more information about {{< param cfy_manager_name >}}, see the {{< param cfy_manager_name >}} section later in this user's guide. diff --git a/content/working_with/_index.md b/content/working_with/_index.md index cae14cb88..bd9437e3a 100644 --- a/content/working_with/_index.md +++ b/content/working_with/_index.md @@ -1,5 +1,5 @@ --- -title: Working with Cloudify +title: Working with Blueprints and Deployments description: Working with blueprints and deployments for orchestration weight: 50 alwaysopen: false diff --git a/content/working_with/console/_index.md b/content/working_with/console/_index.md index 89b8c3248..f490169ad 100644 --- a/content/working_with/console/_index.md +++ b/content/working_with/console/_index.md @@ -1,5 +1,5 @@ --- -title: Using the Cloudify Console +title: Using the Console description: weight: 60 alwaysopen: false diff --git a/content/working_with/integration/circleci.md b/content/working_with/integration/circleci.md index 3ccfba4ee..f4b1542f3 100644 --- a/content/working_with/integration/circleci.md +++ b/content/working_with/integration/circleci.md @@ -1,6 +1,6 @@ +++ title = "CircleCI" -description = "Introduction to Cloudify's CircleCI Integration" +description = "Introduction to the CircleCI Integration" weight = 26 alwaysopen = false +++ diff --git a/content/working_with/integration/github-actions.md b/content/working_with/integration/github-actions.md index c2ad00b30..b1324dfeb 100644 --- a/content/working_with/integration/github-actions.md +++ b/content/working_with/integration/github-actions.md @@ -1,6 +1,6 @@ +++ title = "GitHub Actions" -description = "Introduction to Cloudify's GitHub Actions" +description = "Introduction to GitHub Actions" weight = 25 alwaysopen = false +++ diff --git a/content/working_with/integration/gitlab-ci.md b/content/working_with/integration/gitlab-ci.md index 4b887982b..fb85b8190 100644 --- a/content/working_with/integration/gitlab-ci.md +++ b/content/working_with/integration/gitlab-ci.md @@ -1,6 +1,6 @@ +++ title = "GitLab CI/CD" -description = "Introduction to Cloudify's GitLab CI/CD integration" +description = "Introduction to GitLab CI/CD integration" weight = 25 alwaysopen = false +++ diff --git a/content/working_with/integration/jenkins-plugin.md b/content/working_with/integration/jenkins-plugin.md index 921a9c17c..a95c8946e 100644 --- a/content/working_with/integration/jenkins-plugin.md +++ b/content/working_with/integration/jenkins-plugin.md @@ -1,6 +1,6 @@ +++ title = "Jenkins Plugin" -description = "Introduction to Jenkins' Cloudify integration" +description = "Introduction to Jenkins' integration" weight = 24 alwaysopen = false +++ diff --git a/content/working_with/manager/_index.md b/content/working_with/manager/_index.md index e80dfe1c0..ab8e18b5f 100644 --- a/content/working_with/manager/_index.md +++ b/content/working_with/manager/_index.md @@ -1,5 +1,5 @@ --- -title: Using the Cloudify Manager +title: Using the Manager description: weight: 20 alwaysopen: false diff --git a/content/working_with/manager/okta_authentication.md b/content/working_with/manager/okta_authentication.md index 6eb986bc6..c7180e4d2 100644 --- a/content/working_with/manager/okta_authentication.md +++ b/content/working_with/manager/okta_authentication.md @@ -8,7 +8,7 @@ aliases: /manager/okta_authentication/ {{< param product_name >}} enables integration with your local Okta system to authenticate users and provide Role-Based Access Control. This guide describes the configuration steps required to enable Okta authentication. -Other SAML 2.0 authentication solutions can be integrated with Cloudify. However, only Okta is tested and officially supported. +Other SAML 2.0 authentication solutions can be integrated with {{< param product_name >}}. However, only Okta is tested and officially supported. {{% tip title="openssl version" %}} To enable Okta integration, the openssl package on {{< param cfy_manager_name >}} needs to be of version 1.0.2. If you are running a {{< param product_name >}} image this is already the case, however if you are installing {{< param product_name >}} make sure to update the openssl package prior to the Okta configuration. @@ -24,7 +24,7 @@ You'll need Okta administrator privileges and your {{< param product_name >}} IP 1. Open the Okta Admin dashboard 2. From the top menu, choose Applications > Applications > Create App Integration 3. In the Create a new app integration form, choose **SAML 2.0** as sign-in method -4. In the General Settings step, configure the application name, such as Cloudify Dev and add the logo. +4. In the General Settings step, configure the application name, such as {{< param product_name >}} Dev and add the logo. 5. In the Configure SAML step, configure the following in the **SAML Settings** section: * In General subsection: diff --git a/content/working_with/manager/user-management.md b/content/working_with/manager/user-management.md index dc9c6846e..240b1624a 100644 --- a/content/working_with/manager/user-management.md +++ b/content/working_with/manager/user-management.md @@ -1,6 +1,6 @@ --- title: Managing Users -description: Cloudify provides a user management mechanism, so you can define different users with different permissions, and upon login perform authentication and authorization to control the users’ access to resources. +description: A user management mechanism is provided, so you can define different users with different permissions, and upon login perform authentication and authorization to control the users’ access to resources. category: Manager draft: false weight: 1400 diff --git a/content/working_with/official_plugins/Configuration/ansible.md b/content/working_with/official_plugins/Configuration/ansible.md index edbbf6c98..2e0245e61 100644 --- a/content/working_with/official_plugins/Configuration/ansible.md +++ b/content/working_with/official_plugins/Configuration/ansible.md @@ -193,15 +193,15 @@ Similar to the Script Plugin and the Fabric Plugin, you do not have to use any s In addition, you can provide additional key-word args parameters to the AnsiblePlaybookFromFile class, such as `options_config`. -## Ansible Module for Cloudify +## Ansible Module for {{< param product_name >}} -You may use the ansible Cloudify module to store runtime properties inside of your Ansible playbooks. +You may use the ansible {{< param product_name >}} module to store runtime properties inside of your Ansible playbooks. **requirements** - * Cloudify Ansible Plugin 3.0.0, or higher. - * Cloudify Manager 6.4, or higher. - * A Cloudify Manager that supports SSL, or your Cloudify manager rest credentials. You must collect your {{< param product_name >}} manager credentials. The module will try to use environment variables to connect to {{< param product_name >}} Manager, however, if your manager is not configured for SSL or if your security does not permit, you must provide credentials directly in the playbook. The module will try to load the {{< param product_name >}} rest client from the management worker virtual env, i.e. `/opt/mgmtworker/env/lib/python3.6/site-packages/` in Cloudify 6.4. If this path does not contain `cloudify_rest_client` or if it doesn't exist at all, or if it's not valid anymore, then the module will not work. + * {{< param product_name >}} Ansible Plugin 3.0.0, or higher. + * {{< param product_name >}} Manager 6.4, or higher. + * A {{< param cfy_manager_name >}} that supports SSL, or your {{< param cfy_manager_name >}} rest credentials. You must collect your {{< param product_name >}} manager credentials. The module will try to use environment variables to connect to {{< param product_name >}} Manager, however, if your manager is not configured for SSL or if your security does not permit, you must provide credentials directly in the playbook. The module will try to load the {{< param product_name >}} rest client from the management worker virtual env, i.e. `/opt/mgmtworker/env/lib/python3.6/site-packages/` in Cloudify 6.4. If this path does not contain `cloudify_rest_client` or if it doesn't exist at all, or if it's not valid anymore, then the module will not work. * You must install the Ansible module in one of the appropriate paths for ansible modules, for example `/etc/cloudify/.ansible/plugins/modules.`. ## Using the module: diff --git a/content/working_with/official_plugins/Configuration/diamond.md b/content/working_with/official_plugins/Configuration/diamond.md index 03df0e3d1..308f8d53c 100644 --- a/content/working_with/official_plugins/Configuration/diamond.md +++ b/content/working_with/official_plugins/Configuration/diamond.md @@ -2,7 +2,7 @@ title: Diamond Plugin category: Official Plugins draft: false -abstract: "Cloudify diamond plugin description and configuration" +abstract: "Diamond plugin description and configuration" description: "DEPRECATED: The Diamond plugin is used to install & configure a Diamond monitoring agent (version 3.5) on hosts." weight: 120 aliases: diff --git a/content/working_with/official_plugins/Configuration/fabric.md b/content/working_with/official_plugins/Configuration/fabric.md index 822d7b956..52833edeb 100644 --- a/content/working_with/official_plugins/Configuration/fabric.md +++ b/content/working_with/official_plugins/Configuration/fabric.md @@ -2,7 +2,7 @@ title: Fabric (SSH) Plugin category: Official Plugins draft: false -abstract: "Cloudify Fabric plugin description and configuration" +abstract: "Fabric plugin description and configuration" description: You can use the Fabric plugin to map operations to SSH commands or Fabric tasks that are included in your blueprint. weight: 100 aliases: diff --git a/content/working_with/official_plugins/Configuration/script.md b/content/working_with/official_plugins/Configuration/script.md index 1457917a9..4cb2b0dce 100644 --- a/content/working_with/official_plugins/Configuration/script.md +++ b/content/working_with/official_plugins/Configuration/script.md @@ -2,7 +2,7 @@ title: Script Plugin category: Official Plugins draft: false -abstract: "Cloudify script plugin description and configuration" +abstract: "Script plugin description and configuration" description: "The Script plugin can be used to map node life-cycle operations and workflows to scripts that are included in your blueprint. Scripts can be written in Python, bash, ruby, and so on." weight: 100 aliases: @@ -45,7 +45,7 @@ imports: node_templates: example_web_server: # The web server type is only used for this example. The type used - # could be any valid cloudify type. + # could be any valid {{< param product_name >}} type. type: cloudify.nodes.WebServer interfaces: cloudify.interfaces.lifecycle: diff --git a/content/working_with/official_plugins/Infrastructure/aws.md b/content/working_with/official_plugins/Infrastructure/aws.md index ce1c95576..4adb692ac 100644 --- a/content/working_with/official_plugins/Infrastructure/aws.md +++ b/content/working_with/official_plugins/Infrastructure/aws.md @@ -1060,7 +1060,7 @@ For more information, and possible keyword arguments, see: [EC2:create_key_pair] * `log_create_response`: Boolean. Opt-in to storing the create API request. Not recommended, will log private key material. * `store_in_runtime_properties`: Boolean. Opt-in to save the KeyPair KeyMaterial in the node-instance runtime-properties. Not recommended. - * `create_secret`: Boolean. Opt-in to save the KeyPair KeyMaterial in the secret store. Only available in Cloudify Manager. + * `create_secret`: Boolean. Opt-in to save the KeyPair KeyMaterial in the secret store. Only available in {{< param cfy_manager_name >}}. * `secret_name`: String. The name of the secret if `create_secret` is `true`. * `update_existing_secret`: String. If `secret_name` already exists, overwrite the value. @@ -2913,11 +2913,11 @@ For more information, and possible keyword arguments, see: [CloudFormation:creat * `cloudify.interfaces.lifecycle.create`: Store `resource_config` in runtime properties. * `cloudify.interfaces.lifecycle.configure`: Executes the [CreateStack](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html) action. * `inputs`: - * `minimum_wait_time`: Sets the minimum time in seconds that Cloudify will wait for AWS to create the stack. + * `minimum_wait_time`: Sets the minimum time in seconds that {{< param product_name >}} will wait for AWS to create the stack. * `cloudify.interfaces.lifecycle.start`: Executes the same operations as `cloudify.interfaces.lifecycle.pull`. * `cloudify.interfaces.lifecycle.delete`: Executes the [DeleteStack](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DeleteStack.html) action. * `inputs`: - * `minimum_wait_time`: Sets the minimum time in seconds that Cloudify will wait for AWS to delete the stack. + * `minimum_wait_time`: Sets the minimum time in seconds that {{< param product_name >}} will wait for AWS to delete the stack. * `cloudify.interfaces.lifecycle.pull`: Executes: * [DetectStackDrift](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DetectStackDrift.html) action. * [ListStackResources](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_ListStackResources.html) action, and store the result under `state` runtime property . @@ -2974,7 +2974,7 @@ Outputs: ``` Also, the order of the outputs is not guaranteed. That makes it impossible to refer to output values -through Cloudify's intrinsic functions (such as `get_attribute`). +through {{< param product_name >}}'s intrinsic functions (such as `get_attribute`). In order to address this, the plugin sets a runtime property by the name `outputs_items`, which is a dictionary containing the output values. This runtime property is only set if the `Outputs` key exists diff --git a/content/working_with/official_plugins/Infrastructure/azure.md b/content/working_with/official_plugins/Infrastructure/azure.md index 0ad6d5dbd..416f50e30 100644 --- a/content/working_with/official_plugins/Infrastructure/azure.md +++ b/content/working_with/official_plugins/Infrastructure/azure.md @@ -1162,7 +1162,7 @@ You can use existing resources on Azure, regardless of whether they have been cr All {{< param product_name >}} Azure types have these properties that determine the behaviour: -* `use_external_resource` - Indicate whether the resource exists or if Cloudify should create the resource. +* `use_external_resource` - Indicate whether the resource exists or if {{< param product_name >}} should create the resource. * `create_if_missing` - If use_external_resource is true, and the resource does not exist, create it. * `use_if_exists`- If use_external_resource is false, but the resource does exist, use it. diff --git a/content/working_with/official_plugins/Infrastructure/host-pool.md b/content/working_with/official_plugins/Infrastructure/host-pool.md index 96da196fb..d0d16b2ea 100644 --- a/content/working_with/official_plugins/Infrastructure/host-pool.md +++ b/content/working_with/official_plugins/Infrastructure/host-pool.md @@ -1,9 +1,9 @@ --- title: Host-Pool Plugin category: Official Plugins -description: The Host-Pool plugin is an infrastrcture-provisioning plugin that is used in conjunction with the Cloudify Host-Pool Service to use hosts from a pool of existing hosts +description: The Host-Pool plugin is an infrastrcture-provisioning plugin that is used in conjunction with the Host-Pool Service to use hosts from a pool of existing hosts draft: false -abstract: "Cloudify Host-Pool plugin description and configuration" +abstract: "Host-Pool plugin description and configuration" weight: 180 aliases: - /plugins/host-pool/ diff --git a/content/working_with/official_plugins/Infrastructure/nsx-t.md b/content/working_with/official_plugins/Infrastructure/nsx-t.md index 08fbb58bb..8108b942e 100644 --- a/content/working_with/official_plugins/Infrastructure/nsx-t.md +++ b/content/working_with/official_plugins/Infrastructure/nsx-t.md @@ -1,7 +1,7 @@ --- title: NSX-T Plugin category: Official Plugins -description: Cloudify NSX-T Plugin enables users create NSX-T Resources in NSX-T manager +description: The NSX-T Plugin enables users create NSX-T Resources in NSX-T manager draft: false weight: 150 aliases: diff --git a/content/working_with/official_plugins/Infrastructure/openstack.md b/content/working_with/official_plugins/Infrastructure/openstack.md index 9e148b0ef..c0b0e82fb 100644 --- a/content/working_with/official_plugins/Infrastructure/openstack.md +++ b/content/working_with/official_plugins/Infrastructure/openstack.md @@ -1285,7 +1285,7 @@ my_volume: 1. Creates a server, with name `my_server`, and with name on OpenStack *the node's ID* (since no `name` parameter was supplied under the `server` property). The server is set with an image and flavor IDs. 2. Creates a volume. It is set with a relationship to the `my_server` node: This designated relationship type will take care of attaching the volume to OpenStack server node. -## Example IV: Using Windows server with a Cloudify agent +## Example IV: Using Windows server with a {{< param product_name >}} agent This example demonstrates how to use a Windows server on which a {{< param product_name >}} agent is deployed. diff --git a/content/working_with/official_plugins/Infrastructure/openstackv3.md b/content/working_with/official_plugins/Infrastructure/openstackv3.md index 61927bec1..097c0be87 100644 --- a/content/working_with/official_plugins/Infrastructure/openstackv3.md +++ b/content/working_with/official_plugins/Infrastructure/openstackv3.md @@ -870,7 +870,7 @@ For more information, and possible keyword arguments, see: [create_floating_ip]( project_name: { get_input: project_name } resource_config: name: { concat: [ { get_input: name_prefix }, 'security_group' ] } - description: 'A security group created by Cloudify OpenStack SDK plugin.' + description: 'A security group created by {{< param product_name >}} OpenStack SDK plugin.' example-security-group-rule: type: cloudify.nodes.openstack.SecurityGroupRule @@ -1052,7 +1052,7 @@ For more information, and possible keyword arguments, see: [create_floating_ip]( project_name: { get_input: project_name } resource_config: name: { concat: [ { get_input: name_prefix }, 'security_group' ] } - description: 'A security group created by Cloudify OpenStack SDK plugin.' + description: 'A security group created by {{< param product_name >}} OpenStack SDK plugin.' example-security-group-rule: type: cloudify.nodes.openstack.SecurityGroupRule @@ -1360,7 +1360,7 @@ For more information, and possible keyword arguments, see: [create_port](https:/ protocol: tcp resource_config: name: { concat: [ { get_input: name_prefix }, 'security-group' ] } - description: 'A security group created by Cloudify OpenStack SDK plugin.' + description: 'A security group created by {{< param product_name >}} OpenStack SDK plugin.' example-network: @@ -2358,7 +2358,7 @@ For more information, and possible keyword arguments, see: [create_security_grou project_name: { get_input: project_name } resource_config: name: example-security-group - description: 'A security group created by Cloudify OpenStack SDK plugin.' + description: 'A security group created by {{< param product_name >}} OpenStack SDK plugin.' security_group_rules: - remote_ip_prefix: 0.0.0.0/0 port_range_max: 22 @@ -2382,7 +2382,7 @@ For more information, and possible keyword arguments, see: [create_security_grou disable_default_egress_rules: true resource_config: name: example-security-group - description: 'A security group created by Cloudify OpenStack SDK plugin.' + description: 'A security group created by {{< param product_name >}} OpenStack SDK plugin.' security_group_rules: - remote_ip_prefix: 0.0.0.0/0 port_range_max: 22 diff --git a/content/working_with/official_plugins/Infrastructure/starlingx.md b/content/working_with/official_plugins/Infrastructure/starlingx.md index 17fdbdf97..fc02add18 100644 --- a/content/working_with/official_plugins/Infrastructure/starlingx.md +++ b/content/working_with/official_plugins/Infrastructure/starlingx.md @@ -43,7 +43,7 @@ The following are possible for a StarlingX system deployment: # Sites -During installation the plugin requests a system's location (latitude and longitude) from the StarlingX API, and creates a [Site]({{< relref "working_with/console/widgets/sites.md" >}}) in Cloudify. You can see sites' location on the map on the Dashboard screen. +During installation the plugin requests a system's location (latitude and longitude) from the StarlingX API, and creates a [Site]({{< relref "working_with/console/widgets/sites.md" >}}) in {{< param product_name >}}. You can see sites' location on the map on the Dashboard screen. # Node Types diff --git a/content/working_with/official_plugins/Infrastructure/vcloud.md b/content/working_with/official_plugins/Infrastructure/vcloud.md index ecec83ef3..d29f2c3ed 100644 --- a/content/working_with/official_plugins/Infrastructure/vcloud.md +++ b/content/working_with/official_plugins/Infrastructure/vcloud.md @@ -3,7 +3,7 @@ title: vCloud Plugin category: Official Plugins description: The vCloud Plugin 2 enables you to use a vCloud-based infrastructure for deploying services and applications draft: false -abstract: Cloudify vCloud plugin description and configuration +abstract: vCloud plugin description and configuration weight: 140 aliases: - /plugins/vcloud/ diff --git a/content/working_with/official_plugins/Infrastructure/vsphere.md b/content/working_with/official_plugins/Infrastructure/vsphere.md index acb52cd7b..82fed25ae 100644 --- a/content/working_with/official_plugins/Infrastructure/vsphere.md +++ b/content/working_with/official_plugins/Infrastructure/vsphere.md @@ -108,7 +108,7 @@ Each type has a `connection_config` property. It can be used to pass parameters * `cloudify.interfaces.host`: * `get_state`: - * `minimum_wait_time`: Sets the minimum time in seconds that Cloudify will wait before pulling the state info. + * `minimum_wait_time`: Sets the minimum time in seconds that {{< param product_name >}} will wait before pulling the state info. should be used when the os requires extra time to complete configuration and all the reported information to become available from vSphere. diff --git a/content/working_with/official_plugins/_index.md b/content/working_with/official_plugins/_index.md index 1fc62ec09..4f2448208 100644 --- a/content/working_with/official_plugins/_index.md +++ b/content/working_with/official_plugins/_index.md @@ -1,6 +1,6 @@ --- title: Official Plugins -description: Overview of Cloudify Plugins +description: Plugins Overview weight: 40 alwaysopen: false aliases: diff --git a/content/working_with/service_now/_index.md b/content/working_with/service_now/_index.md index 9deaead8f..b0e56bfb4 100644 --- a/content/working_with/service_now/_index.md +++ b/content/working_with/service_now/_index.md @@ -1,11 +1,11 @@ --- title: "Using ServiceNow" -description: "Get started with setting up your ServiceNow Application with Cloudify Manager" +description: "Get started with setting up your ServiceNow Application with the Manager" weight: 100 alwaysopen: false --- -The Cloudify App for ServiceNow, available from version 5.1, allows ServiceNow users to embed {{< param product_name >}} functions within a company service portal, simplifying the usage of the {{< param cfy_manager_name >}} through ServiceNow. +The {{< param product_name >}} App for ServiceNow, available from version 5.1, allows ServiceNow users to embed {{< param product_name >}} functions within a company service portal, simplifying the usage of the {{< param cfy_manager_name >}} through ServiceNow. {{%children style="h3" description="true"%}} diff --git a/content/working_with/service_now/about_app/_index.md b/content/working_with/service_now/about_app/_index.md index 1b9f3e3a9..92e95fa81 100644 --- a/content/working_with/service_now/about_app/_index.md +++ b/content/working_with/service_now/about_app/_index.md @@ -5,7 +5,7 @@ weight = 101 alwaysopen = false +++ -Cloudify Application is a scoped application that provides ServiceNow users an integration interface to Cloudify environments, using Catalog items that will be added to your default service portal under Cloudify Resources. +{{< param product_name >}} Application is a scoped application that provides ServiceNow users an integration interface to {{< param product_name >}} environments, using Catalog items that will be added to your default service portal under {{< param product_name >}} Resources. ## Application Contents @@ -33,14 +33,14 @@ ServiceNow version: >= Quebec Release The Application can be installed like any other Application - through the official ServiceNow Store : 1. Log into ServiceNow Store with ServiceNow HI credentials. -2. Search for Cloudify in the search box. Application information appears in the search results. -3. From the search results, click Cloudify. +2. Search for {{< param product_name >}} in the search box. Application information appears in the search results. +3. From the search results, click {{< param product_name >}}. Information about the application is displayed. 4. In the right pane of the application window, view the Compatibility section to ensure that the integration application is compatible with the version of ServiceNow that you require. 5. In the right pane of the application window, click the Get button. A notice appears. 6. At the bottom of the notice, click Continue. -7. On the Purchase of Cloudify page, choose the Make available on specific instances radio button and click the Select button. +7. On the Purchase of {{< param product_name >}} page, choose the Make available on specific instances radio button and click the Select button. A Select Instances dialog appears. 8. In the Available Instances pane, double-click the instance that you want the application to be available on and click OK. 9. Select the "I accept" check box (to accept terms of use and subscription terms and conditions) and click Get. @@ -49,8 +49,8 @@ A Select Instances dialog appears. The Applications list appears. 12. Click the Downloads tab. The Downloads list appears. -13. Scroll to the Cloudify application, and click the Install button. -The application now appears in the ServiceNow menu, displayed in the left-hand navigation panel as Cloudify. +13. Scroll to the {{< param product_name >}} application, and click the Install button. +The application now appears in the ServiceNow menu, displayed in the left-hand navigation panel as {{< param product_name >}}. You can refer to the ServiceNow official support video : diff --git a/content/working_with/service_now/developer_guide/_index.md b/content/working_with/service_now/developer_guide/_index.md index c548a17af..fbea70a0e 100644 --- a/content/working_with/service_now/developer_guide/_index.md +++ b/content/working_with/service_now/developer_guide/_index.md @@ -11,11 +11,11 @@ As a ServiceNow developer you can use the application exposed actions and sub-fl ![Flow Designer actions]( /images/service_now/actions.png ) -*NOTE* it will require the user to have Cloudify app roles to be able to select and provide config names from the configured configs, as it will be required in all of the actions and sub-flows as an input. +*NOTE* it will require the user to have {{< param product_name >}} app roles to be able to select and provide config names from the configured configs, as it will be required in all of the actions and sub-flows as an input. ## Create Environment Catalog Item explained -In the application we use catalog client scripts to handle most of the logic that is needed to communicate with Cloudify. Starting with config selection (which will be listed to the user) and if there is one it will be selected automatically based on the selected config. We fetch the blueprints and onChange values and fetch the blueprint inputs that don’t have default values. +In the application we use catalog client scripts to handle most of the logic that is needed to communicate with {{< param product_name >}}. Starting with config selection (which will be listed to the user) and if there is one it will be selected automatically based on the selected config. We fetch the blueprints and onChange values and fetch the blueprint inputs that don’t have default values. You can watch this video that explain the catalog item: diff --git a/content/working_with/service_now/getting_started_environments/_index.md b/content/working_with/service_now/getting_started_environments/_index.md index c55709311..7ea936405 100644 --- a/content/working_with/service_now/getting_started_environments/_index.md +++ b/content/working_with/service_now/getting_started_environments/_index.md @@ -5,7 +5,7 @@ weight = 104 alwaysopen = false +++ -Given that you have your Cloudify Environment configured (with version is 6.2 or above), we should be ready to go through certified environment example with the following next steps: +Given that you have your {{< param product_name >}} Environment configured (with version is 6.2 or above), we should be ready to go through certified environment example with the following next steps: 1. Create Cloud Account Setup -AWS/Azure- 2. Create a certified environment from the catalog which could be one of the following flavors: diff --git a/content/working_with/service_now/getting_started_helloworld/_index.md b/content/working_with/service_now/getting_started_helloworld/_index.md index d18a3e910..9557707cb 100644 --- a/content/working_with/service_now/getting_started_helloworld/_index.md +++ b/content/working_with/service_now/getting_started_helloworld/_index.md @@ -5,7 +5,7 @@ weight = 103 alwaysopen = false +++ -Given that you have your Cloudify Environment configured, you can start with Hello World Journey +Given that you have your {{< param product_name >}} Environment configured, you can start with Hello World Journey If you have x_clop2_cloudify.admin role you should be able to see the application menu - from the menu modules you can select Getting Started Setup diff --git a/content/working_with/service_now/itom_integration/_index.md b/content/working_with/service_now/itom_integration/_index.md index 91d5b4ce6..105b793ed 100644 --- a/content/working_with/service_now/itom_integration/_index.md +++ b/content/working_with/service_now/itom_integration/_index.md @@ -23,15 +23,15 @@ you should be able to define scan configurations and build custom policies and d Cloud Configuration Governance application contains a set of resource collectors [ AWS/Azure ] that will be triggered from the scan configuration setup, these collectors call specific REST apis based on the type of the resource to describe and fetch all the properties/settings that can be obtained and store the results inside servicenow tables, based on the stored settings you can build policies to report violations, then you can map each violation with remediation action [sub-flow] -## Cloudify Application Integration +## {{< param product_name >}} Application Integration -In Cloudify application v2.5 we introduced integration with CCG application in the form of sub-flows that leverage the inputs that we get from CCG application in order to remediate the violation that will be detected based on the policy definition. +In {{< param product_name >}} application v2.5 we introduced integration with CCG application in the form of sub-flows that leverage the inputs that we get from CCG application in order to remediate the violation that will be detected based on the policy definition. -When you install Cloudify application it will include a custom table (x_clop2_cloudify_remediation_setups) which will contain an initial setup for all of the sub-flows defined in the application, there you should be able to link the flow with a config_name to use a specific Cloudify manager tenant to carry out the remediation -some sub-flows takes a value you can also modify that-. +When you install {{< param product_name >}} application it will include a custom table (x_clop2_cloudify_remediation_setups) which will contain an initial setup for all of the sub-flows defined in the application, there you should be able to link the flow with a config_name to use a specific {{< param product_name >}} manager tenant to carry out the remediation -some sub-flows takes a value you can also modify that-. we offer a set of pre-defined most used remediations for various violation types: -### Remediation of resources that is not strictly provisioned by Cloudify: +### Remediation of resources that is not strictly provisioned by {{< param product_name >}}: * AWS EC2-Instances: @@ -56,9 +56,9 @@ we offer a set of pre-defined most used remediations for various violation types * Delete-User-Profile * Attach-Predefined-Policy -### Remediation of resources that is provisioned by Cloudify: +### Remediation of resources that is provisioned by {{< param product_name >}}: -You can leverage a sub-flow that can interact with Cloudify deployments where you can trigger cloudify-workflows on deployments that were deployed using Cloudify given that you have a tag that contains the deployment-id. +You can leverage a sub-flow that can interact with {{< param product_name >}} deployments where you can trigger cloudify-workflows on deployments that were deployed using {{< param product_name >}} given that you have a tag that contains the deployment-id. ## Videos diff --git a/content/working_with/service_now/setup_manager/_index.md b/content/working_with/service_now/setup_manager/_index.md index 7b797e5cd..aeaac62dd 100644 --- a/content/working_with/service_now/setup_manager/_index.md +++ b/content/working_with/service_now/setup_manager/_index.md @@ -1,25 +1,25 @@ +++ -title = "Cloudify Manager Setup" +title = "Manager Setup" description = "Get started with setting up your hosted service trial or deploying your own trial server" weight = 102 alwaysopen = false +++ -The first step in this journey is to setup your Cloudify Environment. +The first step in this journey is to setup your {{< param product_name >}} Environment. -If you have x_clop2_cloudify.admin role you should be able to see the application menu - from the menu modules you can select Getting Started Setup then you can get started with Cloudify Environment +If you have x_clop2_cloudify.admin role you should be able to see the application menu - from the menu modules you can select Getting Started Setup then you can get started with {{< param product_name >}} Environment -Cloudify Environment can be in many flavors : +{{< param product_name >}} Environment can be in many flavors : * As a Hosted Service * Installed on public network [SSL,Non-SSL] and in case of SSL with self-signed certificate {the certificate needs to be added to ServiceNow} * Installed on private network [mid-server needs to be configured] -For more details on how to setup Cloudify manager please refer to [{{< param cfy_manager_name >}} setup]({{< relref "/trial_getting_started/set_trial_manager/_index.md" >}}) before moving on. +For more details on how to setup {{< param product_name >}} manager please refer to [{{< param cfy_manager_name >}} setup]({{< relref "/trial_getting_started/set_trial_manager/_index.md" >}}) before moving on. -## Adding Cloudify Manager External Certificate *Self-Signed* +## Adding {{< param cfy_manager_name >}} External Certificate *Self-Signed* To add the certificate you will need to do the following: @@ -43,9 +43,9 @@ You can watch this video that shows the mid-server installation and configuratio -## Getting Started Cloudify Environment +## Getting Started {{< param product_name >}} Environment -This video demonstrates how to setup Cloudify as a service and configure various flavors of Cloudify environments: +This video demonstrates how to setup {{< param product_name >}} as a service and configure various flavors of {{< param product_name >}} environments: diff --git a/content/working_with/workflows/_index.md b/content/working_with/workflows/_index.md index f9f7edf2e..8d264c49d 100644 --- a/content/working_with/workflows/_index.md +++ b/content/working_with/workflows/_index.md @@ -51,7 +51,7 @@ Queued executions will begin automatically when possible. {{% /note %}} # Scheduling Executions -Cloudify allows the user to create schedules for running executions at specified times, both single-use and recurring. +{{< param product_name >}} allows the user to create schedules for running executions at specified times, both single-use and recurring. Execution schedules, also known as deployment schedules, belong to a specific deployment and can be created in two ways: 1. By using the dedicated CLI command: `cfy deployments schedule create` diff --git a/content/working_with/workflows/built-in-workflows.md b/content/working_with/workflows/built-in-workflows.md index a786107d8..b79ca9acb 100644 --- a/content/working_with/workflows/built-in-workflows.md +++ b/content/working_with/workflows/built-in-workflows.md @@ -2,7 +2,7 @@ title: Built-in Workflows category: Workflows draft: false -abstract: Description and details on Cloudify's built-in Workflows +abstract: Description and details on built-in Workflows weight: 600 aliases: /workflows/built-in-workflows/ diff --git a/content/working_with/workflows/creating-your-own-workflow.md b/content/working_with/workflows/creating-your-own-workflow.md index f39dc8d43..8779344f2 100644 --- a/content/working_with/workflows/creating-your-own-workflow.md +++ b/content/working_with/workflows/creating-your-own-workflow.md @@ -2,7 +2,7 @@ title: Creating Custom Workflows category: Workflows draft: false -abstract: A guide to authoring Cloudify Workflows +abstract: A guide to authoring Workflows weight: 700 aliases: /workflows/creating-your-own-workflow/ ---