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/trial_getting_started/_index.md b/content/trial_getting_started/_index.md index 906bdcf49..298674bb3 100644 --- a/content/trial_getting_started/_index.md +++ b/content/trial_getting_started/_index.md @@ -1,6 +1,6 @@ +++ title = "Getting Started" -description = "Deploying Cloudify trial manager & walkthrough usage examples" +description = "Deploying trial manager & walkthrough usage examples" weight = 20 alwaysopen = false +++ diff --git a/content/trial_getting_started/examples/_index.md b/content/trial_getting_started/examples/_index.md index db06cf479..1f8bc24a7 100644 --- a/content/trial_getting_started/examples/_index.md +++ b/content/trial_getting_started/examples/_index.md @@ -1,6 +1,6 @@ +++ title = "Learn Through Examples" -description = "Deploy the Cloudify trial manager and walkthrough usage examples" +description = "Deploy the trial manager and walkthrough usage examples" weight = 97 alwaysopen = false +++ diff --git a/content/trial_getting_started/examples/automation_tools/aws_ansible_basics.md b/content/trial_getting_started/examples/automation_tools/aws_ansible_basics.md index c94ebb048..9c4ce25d9 100644 --- a/content/trial_getting_started/examples/automation_tools/aws_ansible_basics.md +++ b/content/trial_getting_started/examples/automation_tools/aws_ansible_basics.md @@ -72,7 +72,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -96,7 +96,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. diff --git a/content/trial_getting_started/examples/automation_tools/aws_cloudformation_basics.md b/content/trial_getting_started/examples/automation_tools/aws_cloudformation_basics.md index dd22f92e8..d569c2187 100644 --- a/content/trial_getting_started/examples/automation_tools/aws_cloudformation_basics.md +++ b/content/trial_getting_started/examples/automation_tools/aws_cloudformation_basics.md @@ -69,7 +69,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -93,7 +93,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-VM-Setup-using-CloudFormation blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-VM-Setup-using-CloudFormation blueprint. diff --git a/content/trial_getting_started/examples/automation_tools/aws_terraform_basics.md b/content/trial_getting_started/examples/automation_tools/aws_terraform_basics.md index a1baf4640..9f8383716 100644 --- a/content/trial_getting_started/examples/automation_tools/aws_terraform_basics.md +++ b/content/trial_getting_started/examples/automation_tools/aws_terraform_basics.md @@ -68,7 +68,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -92,7 +92,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy and Install diff --git a/content/trial_getting_started/examples/automation_tools/azure_arm_basics.md b/content/trial_getting_started/examples/automation_tools/azure_arm_basics.md index 92acf7291..937ad1872 100644 --- a/content/trial_getting_started/examples/automation_tools/azure_arm_basics.md +++ b/content/trial_getting_started/examples/automation_tools/azure_arm_basics.md @@ -76,7 +76,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -100,7 +100,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-VM-Setup-using-ARM blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-VM-Setup-using-ARM blueprint. ### Deploy & Install diff --git a/content/trial_getting_started/examples/automation_tools/azure_terraform_basics.md b/content/trial_getting_started/examples/automation_tools/azure_terraform_basics.md index 04018ce39..87110a4fd 100644 --- a/content/trial_getting_started/examples/automation_tools/azure_terraform_basics.md +++ b/content/trial_getting_started/examples/automation_tools/azure_terraform_basics.md @@ -75,7 +75,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -99,7 +99,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy and Install diff --git a/content/trial_getting_started/examples/automation_tools/gcp_terraform_basics.md b/content/trial_getting_started/examples/automation_tools/gcp_terraform_basics.md index ec4d4cbf5..659ddc24e 100644 --- a/content/trial_getting_started/examples/automation_tools/gcp_terraform_basics.md +++ b/content/trial_getting_started/examples/automation_tools/gcp_terraform_basics.md @@ -69,7 +69,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -93,7 +93,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy and Install diff --git a/content/trial_getting_started/examples/automation_tools/openstack_terraform_basics.md b/content/trial_getting_started/examples/automation_tools/openstack_terraform_basics.md index 7e612f5be..9c0ea09a3 100644 --- a/content/trial_getting_started/examples/automation_tools/openstack_terraform_basics.md +++ b/content/trial_getting_started/examples/automation_tools/openstack_terraform_basics.md @@ -71,7 +71,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -95,7 +95,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy and Install diff --git a/content/trial_getting_started/examples/basic/aws_basics.md b/content/trial_getting_started/examples/basic/aws_basics.md index bc665e6c7..8a495027d 100644 --- a/content/trial_getting_started/examples/basic/aws_basics.md +++ b/content/trial_getting_started/examples/basic/aws_basics.md @@ -68,7 +68,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -91,7 +91,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. diff --git a/content/trial_getting_started/examples/basic/azure_basics.md b/content/trial_getting_started/examples/basic/azure_basics.md index e0908ee37..c030778cc 100644 --- a/content/trial_getting_started/examples/basic/azure_basics.md +++ b/content/trial_getting_started/examples/basic/azure_basics.md @@ -75,7 +75,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -99,7 +99,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. diff --git a/content/trial_getting_started/examples/basic/gcp_basics.md b/content/trial_getting_started/examples/basic/gcp_basics.md index 16982a07c..8b9b02e71 100644 --- a/content/trial_getting_started/examples/basic/gcp_basics.md +++ b/content/trial_getting_started/examples/basic/gcp_basics.md @@ -67,7 +67,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -91,7 +91,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy & Install diff --git a/content/trial_getting_started/examples/basic/openstack_basics.md b/content/trial_getting_started/examples/basic/openstack_basics.md index dbf0f72f2..a3b15911b 100644 --- a/content/trial_getting_started/examples/basic/openstack_basics.md +++ b/content/trial_getting_started/examples/basic/openstack_basics.md @@ -57,7 +57,7 @@ Learn more about {{< param product_name >}} secrets [here]({{< relref "/working_ {{< param cloud >}} credentials can be downloaded by following the guide [here]({{< param cloud_auth_ui_link>}}). -To store the access keys as secrets in the Cloudify manager, login to the {{< param cfy_console_name >}} and select the **System Resources** page. Scroll to the **Secret Store Management** widget and use the **Create** button to add the following new secrets: +To store the access keys as secrets in the {{< param cfy_manager_name >}}, login to the {{< param cfy_console_name >}} and select the **System Resources** page. Scroll to the **Secret Store Management** widget and use the **Create** button to add the following new secrets: ```bash * openstack_username @@ -89,7 +89,7 @@ To store the access keys as secrets in the Cloudify manager, login to the {{< pa Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -112,7 +112,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-VM-Setup blueprint. ### Deploy & Install diff --git a/content/trial_getting_started/examples/discovery/_index.md b/content/trial_getting_started/examples/discovery/_index.md index 749186be0..7edb4f421 100644 --- a/content/trial_getting_started/examples/discovery/_index.md +++ b/content/trial_getting_started/examples/discovery/_index.md @@ -62,7 +62,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to AWS requires the AWS plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -92,7 +92,7 @@ For the Discovery and Batch Workload Management feature, the flow is: 1. Upload the blueprint that runs a Kubernetes workload on a Kubernetes Cluster managed in another Deployment {{< param cfy_manager_name >}}. 1. Create a deployment from the uploaded AWS Account blueprint. This generates a model of the service topology in the {{< param product_name >}} database and provides the "context" needed for running workflows. 1. Run the **install** workflow for the created deployment to apply the model to the infrastructure. -1. Run the **discover_and_deploy** workflow from the "account" deployment to discover Kubernetes Clusters and install existing cluster deployments for them on the Cloudify manager. +1. Run the **discover_and_deploy** workflow from the "account" deployment to discover Kubernetes Clusters and install existing cluster deployments for them on the {{< param cfy_manager_name >}}. 1. Run the **batch_deploy_and_install** workflow from the "account" deployment to install a Kubernetes workload on the discovered clusters. Let's run these one by one. @@ -187,7 +187,7 @@ Now, you should have deployments for all of the Kubernetes clusters in your clou Select the **Execute workflow** button. -This will open a drop down menu. Click on "Cloudify custom workflow", and then click on "batch deploy and install". +This will open a drop down menu. Click on "{{< param product_name >}} custom workflow", and then click on "batch deploy and install". ![Execute workflow drop down]( /images/trial_getting_started/discovery/discovery-drop-down2.png ) diff --git a/content/trial_getting_started/examples/first_service/aws_hello_world_example.md b/content/trial_getting_started/examples/first_service/aws_hello_world_example.md index 2445f3a77..b3d3c929b 100644 --- a/content/trial_getting_started/examples/first_service/aws_hello_world_example.md +++ b/content/trial_getting_started/examples/first_service/aws_hello_world_example.md @@ -66,7 +66,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples/first_service/azure_hello_world_example.md b/content/trial_getting_started/examples/first_service/azure_hello_world_example.md index 1726382dd..309e43328 100644 --- a/content/trial_getting_started/examples/first_service/azure_hello_world_example.md +++ b/content/trial_getting_started/examples/first_service/azure_hello_world_example.md @@ -74,7 +74,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples/first_service/gcp_hello_world_example.md b/content/trial_getting_started/examples/first_service/gcp_hello_world_example.md index 058ffab3a..d1cc43b42 100644 --- a/content/trial_getting_started/examples/first_service/gcp_hello_world_example.md +++ b/content/trial_getting_started/examples/first_service/gcp_hello_world_example.md @@ -66,7 +66,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples/first_service/openstack_hello_world_example.md b/content/trial_getting_started/examples/first_service/openstack_hello_world_example.md index 59b849d85..45baba561 100644 --- a/content/trial_getting_started/examples/first_service/openstack_hello_world_example.md +++ b/content/trial_getting_started/examples/first_service/openstack_hello_world_example.md @@ -86,7 +86,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -111,7 +111,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-Simple-Service-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-Simple-Service-Setup blueprint. ### Deploy & Install diff --git a/content/trial_getting_started/examples/first_service/terraform_hello_world_example.md b/content/trial_getting_started/examples/first_service/terraform_hello_world_example.md index 168fd74b3..5c6270889 100644 --- a/content/trial_getting_started/examples/first_service/terraform_hello_world_example.md +++ b/content/trial_getting_started/examples/first_service/terraform_hello_world_example.md @@ -66,7 +66,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to {{< param cloud >}} requires the {{< param cloud >}} plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -92,7 +92,7 @@ The flow required to setup a service consists of: Let's run these one by one. -To upload a blueprint to the {{< param cfy_manager_name >}}, select the **Cloudify Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-Simple-Service-Setup blueprint. +To upload a blueprint to the {{< param cfy_manager_name >}}, select the **{{< param product_name >}} Catalog** page, and use the **Upload blueprint** button next to the {{< param cloud >}}-Basics-Simple-Service-Setup blueprint. ### Deploy & Install diff --git a/content/trial_getting_started/examples/kubernetes/_index.md b/content/trial_getting_started/examples/kubernetes/_index.md index 0185e973c..50a690da8 100644 --- a/content/trial_getting_started/examples/kubernetes/_index.md +++ b/content/trial_getting_started/examples/kubernetes/_index.md @@ -34,7 +34,7 @@ Where ### Service Composition -The configuration indirection mentioned above helps with mapping simple identifiers (like 'dev-small') to complex configuration details (like image names/id, flavors, etc..). This is not sufficient to completely abstract away the different Kubernetes environments required. To do this requires [service composition](../../../working_with/service_composition). Service composition allows blueprint nodes to represent entire blueprints themselves, effectively nesting blueprints and enabling a building block approach. To make it possible to use components in the way required by this example, components of a similar kind (for example, blueprints that represent different kinds of database), all have a consistent interface. In Cloudify DSL, this interface is provided by the `capabilitites` section in the blueprint. This is analogous to the use of interfaces or protocols in an object oriented programming paradigm. +The configuration indirection mentioned above helps with mapping simple identifiers (like 'dev-small') to complex configuration details (like image names/id, flavors, etc..). This is not sufficient to completely abstract away the different Kubernetes environments required. To do this requires [service composition](../../../working_with/service_composition). Service composition allows blueprint nodes to represent entire blueprints themselves, effectively nesting blueprints and enabling a building block approach. To make it possible to use components in the way required by this example, components of a similar kind (for example, blueprints that represent different kinds of database), all have a consistent interface. In {{< param product_name >}} DSL, this interface is provided by the `capabilitites` section in the blueprint. This is analogous to the use of interfaces or protocols in an object oriented programming paradigm. Looking at the [multi-Kubernetes cluster example](https://github.com/cloudify-community/eaas-example), consider the object storage options [`minio`](https://github.com/cloudify-community/eaas-example/blob/master/infra/dev/minio/blueprint.yaml) and [`S3`](https://github.com/cloudify-community/eaas-example/blob/master/infra/prod/s3/aws-blueprint.yaml). Both of these are represented by a blueprint that exposes a single `capability`: `bucket_url`. Because of this standard "interface", the blueprints can be substituted for each other at deploy time. You will find the same pattern for other elements: [minikube](https://github.com/cloudify-community/eaas-example/blob/master/infra/dev/minikube/blueprint.yaml)/[EKS](https://github.com/cloudify-community/eaas-example/blob/master/infra/prod/eks/blueprint.yaml) (`endpoint`), [`psql`](https://github.com/cloudify-community/eaas-example/blob/master/infra/dev/psql/aws-blueprint.yaml)/[`RDS`](https://github.com/cloudify-community/eaas-example/blob/master/infra/prod/rds_psql/aws-blueprint.yaml) (`host`, `master_username`, `master_password`), and so on. diff --git a/content/trial_getting_started/examples/multi_cloud/multi-cloud_JBoss_example.md b/content/trial_getting_started/examples/multi_cloud/multi-cloud_JBoss_example.md index 5b3f2157a..ef8c36fd4 100644 --- a/content/trial_getting_started/examples/multi_cloud/multi-cloud_JBoss_example.md +++ b/content/trial_getting_started/examples/multi_cloud/multi-cloud_JBoss_example.md @@ -81,7 +81,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to AWS requires the AWS plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples/multi_cloud/multi-cloud_localstack_example.md b/content/trial_getting_started/examples/multi_cloud/multi-cloud_localstack_example.md index d4b5928cb..f357ad066 100644 --- a/content/trial_getting_started/examples/multi_cloud/multi-cloud_localstack_example.md +++ b/content/trial_getting_started/examples/multi_cloud/multi-cloud_localstack_example.md @@ -80,7 +80,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to AWS requires the AWS plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples/multi_cloud/multi-cloud_nodejs_example.md b/content/trial_getting_started/examples/multi_cloud/multi-cloud_nodejs_example.md index 60851268b..fd868d425 100644 --- a/content/trial_getting_started/examples/multi_cloud/multi-cloud_nodejs_example.md +++ b/content/trial_getting_started/examples/multi_cloud/multi-cloud_nodejs_example.md @@ -81,7 +81,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to AWS requires the AWS plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: diff --git a/content/trial_getting_started/examples_k8s/_index.md b/content/trial_getting_started/examples_k8s/_index.md index f4ba732d2..0c9ed7e52 100644 --- a/content/trial_getting_started/examples_k8s/_index.md +++ b/content/trial_getting_started/examples_k8s/_index.md @@ -1,6 +1,6 @@ +++ title = "Kubernetes Guides" -description = "Deploy the Cloudify trial manager and walkthrough usage examples for Kubernetes" +description = "Deploy the trial manager and walkthrough usage examples for Kubernetes" weight = 97 alwaysopen = false +++ diff --git a/content/trial_getting_started/examples_k8s/create_cluster/aws_eks_cluster.md b/content/trial_getting_started/examples_k8s/create_cluster/aws_eks_cluster.md index 7562b17c5..b90fa4c2a 100644 --- a/content/trial_getting_started/examples_k8s/create_cluster/aws_eks_cluster.md +++ b/content/trial_getting_started/examples_k8s/create_cluster/aws_eks_cluster.md @@ -54,7 +54,7 @@ The {{< param cfy_console_name >}} and {{< param cfy_cli_name >}} can be used in ### Import Plugins, Blueprints and Secrets -To connect to {{< param cloud >}}, credentials and Cloudify plugins are required. AWS credentials can be created by following the guide [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey). +To connect to {{< param cloud >}}, credentials and {{< param product_name >}} plugins are required. AWS credentials can be created by following the guide [here](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey). {{< param product_name >}} recommends storing such sensitive information in a {{< param product_name >}} secret. Secrets are kept encrypted in a secure way and used in run-time by the system. Learn more about {{< param product_name >}} secrets [here]({{< relref "/working_with/manager/using-secrets.md" >}}). diff --git a/content/trial_getting_started/examples_k8s/create_cluster/azure_aks_cluster.md b/content/trial_getting_started/examples_k8s/create_cluster/azure_aks_cluster.md index 5274d64ea..6629aaf03 100644 --- a/content/trial_getting_started/examples_k8s/create_cluster/azure_aks_cluster.md +++ b/content/trial_getting_started/examples_k8s/create_cluster/azure_aks_cluster.md @@ -53,7 +53,7 @@ The {{< param cfy_console_name >}} and {{< param cfy_cli_name >}} can be used in ### Import Plugins and Secrets -To connect to {{< param cloud >}}, credentials and Cloudify plugins are required. +To connect to {{< param cloud >}}, credentials and {{< param product_name >}} plugins are required. {{< param product_name >}} recommends storing such sensitive information in a {{< param product_name >}} secret. Secrets are kept encrypted in a secure way and used in run-time by the system. Learn more about {{< param product_name >}} secrets [here]({{< relref "/working_with/manager/using-secrets.md" >}}). diff --git a/content/trial_getting_started/examples_k8s/create_cluster/gcp_gke_cluster.md b/content/trial_getting_started/examples_k8s/create_cluster/gcp_gke_cluster.md index e1a4f3104..ff003903f 100644 --- a/content/trial_getting_started/examples_k8s/create_cluster/gcp_gke_cluster.md +++ b/content/trial_getting_started/examples_k8s/create_cluster/gcp_gke_cluster.md @@ -52,7 +52,7 @@ The {{< param cfy_console_name >}} and {{< param cfy_cli_name >}} can be used in ### Import Plugins and Secrets -To connect to {{< param cloud >}}, credentials and Cloudify plugins are required. +To connect to {{< param cloud >}}, credentials and {{< param product_name >}} plugins are required. {{< param product_name >}} recommends storing such sensitive information in a {{< param product_name >}} secret. Secrets are kept encrypted in a secure way and used in run-time by the system. Learn more about {{< param product_name >}} secrets [here]({{< relref "/working_with/manager/using-secrets.md" >}}). diff --git a/content/trial_getting_started/examples_k8s/discover_cluster/eks_discovery.md b/content/trial_getting_started/examples_k8s/discover_cluster/eks_discovery.md index 0167b07b9..c315ace42 100644 --- a/content/trial_getting_started/examples_k8s/discover_cluster/eks_discovery.md +++ b/content/trial_getting_started/examples_k8s/discover_cluster/eks_discovery.md @@ -61,7 +61,7 @@ To store the access keys as secrets in the {{< param cfy_manager_name >}}, login Plugins are {{< param product_name >}}'s extendable interfaces to services, cloud providers and automation tools. I.e., connecting to AWS requires the AWS plugin. -To upload the required plugins to your manager, select the **Cloudify Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. +To upload the required plugins to your manager, select the **{{< param product_name >}} Catalog** page, scroll to the **Plugins Catalog** widget and select the plugins you wish to upload. For this example, upload the following plugins: @@ -91,7 +91,7 @@ For the Discovery and Batch Workload Management feature, the flow is: 1. Upload the blueprint that runs a Kubernetes workload on a Kubernetes Cluster managed in another Deployment {{< param cfy_manager_name >}}. 1. Create a deployment from the uploaded AWS Account blueprint. This generates a model of the service topology in the {{< param product_name >}} database and provides the "context" needed for running workflows. 1. Run the **install** workflow for the created deployment to apply the model to the infrastructure. -1. Run the **discover_and_deploy** workflow from the "account" deployment to discover Kubernetes Clusters and install existing cluster deployments for them on the Cloudify manager. +1. Run the **discover_and_deploy** workflow from the "account" deployment to discover Kubernetes Clusters and install existing cluster deployments for them on the {{< param cfy_manager_name >}}. 1. Run the **batch_deploy_and_install** workflow from the "account" deployment to install a Kubernetes workload on the discovered clusters. Let's run these one by one. diff --git a/content/trial_getting_started/introduction_to_blueprints/_index.md b/content/trial_getting_started/introduction_to_blueprints/_index.md index ce1b5a520..ad9fd2de4 100644 --- a/content/trial_getting_started/introduction_to_blueprints/_index.md +++ b/content/trial_getting_started/introduction_to_blueprints/_index.md @@ -1,6 +1,6 @@ +++ title = "Introduction To Blueprints" -description = "Learn how to write your first Cloudify blueprint" +description = "Learn how to write your first blueprint" weight = 96 alwaysopen = false +++ diff --git a/content/trial_getting_started/set_trial_manager/_index.md b/content/trial_getting_started/set_trial_manager/_index.md index e1e06b54b..5e854e0ed 100644 --- a/content/trial_getting_started/set_trial_manager/_index.md +++ b/content/trial_getting_started/set_trial_manager/_index.md @@ -1,5 +1,5 @@ +++ -title = "Cloudify Manager Setup" +title = "Manager Setup" description = "Get started by setting up your hosted service trial or deploying your own trial server" weight = 95 alwaysopen = false diff --git a/content/trial_getting_started/set_trial_manager/download_community.md b/content/trial_getting_started/set_trial_manager/download_community.md index 10f137967..936b6f8de 100644 --- a/content/trial_getting_started/set_trial_manager/download_community.md +++ b/content/trial_getting_started/set_trial_manager/download_community.md @@ -1,5 +1,5 @@ +++ -title = "Cloudify Community" +title = "Community" description = "Deploy the community version of the manager using a Docker container" weight = 9 alwaysopen = false @@ -36,7 +36,7 @@ This will publish the web interface on port 8080. Then verify that the {{< param NOTE: Internet access is required to complete this step. {{% /note %}} -Once you log into the Community, you'll be asked to fill in your contact details. You need to fill in the form to access the Cloudify Manager. It's required only once on the first log in. +Once you log into the Community, you'll be asked to fill in your contact details. You need to fill in the form to access the {{< param cfy_manager_name >}}. It's required only once on the first log in. ![community-contact-details.png]( /images/ui/pages/community-contact-details.png ) diff --git a/content/trial_getting_started/set_trial_manager/getting-started-with-cloudify-docker-and-cli.md b/content/trial_getting_started/set_trial_manager/getting-started-with-cloudify-docker-and-cli.md index 13ccc8b90..cb85e68a1 100644 --- a/content/trial_getting_started/set_trial_manager/getting-started-with-cloudify-docker-and-cli.md +++ b/content/trial_getting_started/set_trial_manager/getting-started-with-cloudify-docker-and-cli.md @@ -1,5 +1,5 @@ +++ -title = "Cloudify CLI" +title = "CLI" description = "Install the CLI client using a Docker image" weight = 300 alwaysopen = false @@ -9,7 +9,7 @@ docker_install_command_prefix = "docker run --name cfy_manager_local -p 8080:80" {{%children style="h2" description="true"%}} -## Install Cloudify CLI +## Install {{< param product_name >}} CLI ### Linux & Mac (Binary) @@ -40,7 +40,7 @@ eval "$(_CFY_COMPLETE=source cfy)" ## Connect to a Remote Manager -By default CLI points to `localhost`. In case you've installed Cloudify CLI on a different machine or you are using Cloudify SaaS, you'll need to set up a new profile to redirect to a remote {{< param cfy_manager_name >}} +By default CLI points to `localhost`. In case you've installed {{< param product_name >}} CLI on a different machine or you are using {{< param product_name >}} SaaS, you'll need to set up a new profile to redirect to a remote {{< param cfy_manager_name >}} ```bash cfy init diff --git a/content/trial_getting_started/set_trial_manager/install_with_helm.md b/content/trial_getting_started/set_trial_manager/install_with_helm.md index 6063301b7..262610e34 100644 --- a/content/trial_getting_started/set_trial_manager/install_with_helm.md +++ b/content/trial_getting_started/set_trial_manager/install_with_helm.md @@ -1,6 +1,6 @@ +++ -title = "Cloudify Helm Chart" -description = "Deploy Cloudify to a Kubernetes cluster with our Helm chart" +title = "Helm Chart" +description = "Deploy to a Kubernetes cluster with our Helm chart" weight = 200 alwaysopen = false +++ @@ -10,7 +10,7 @@ alwaysopen = false The {{< param cfy_manager_name >}} may be installed on a Kubernetes cluster using the official [Helm chart](https://github.com/cloudify-cosmo/cloudify-helm). There are two options for installation: * All In One (AIO) chart -* Cloudify Manager Worker chart +* {{< param product_name >}} Manager Worker chart Each option is described in more detail below. @@ -24,7 +24,7 @@ To use the official Helm charts, you will need: The {{< param cfy_manager_name >}} AIO Helm chart is the preferred way to become familiar with {{< param company_name >}}. It is a very simple installation that can be deployed in minutes. -The chart has several limitations that you should be aware of, as this option is only suitable Cloudify basic trial: +The chart has several limitations that you should be aware of, as this option is only suitable {{< param product_name >}} basic trial: * No high availability: only a single replica is deployed. * No persistent volume is configured for data to persist across pod restarts or failures. @@ -40,9 +40,9 @@ helm repo add cloudify-helm https://cloudify-cosmo.github.io/cloudify-helm helm install cloudify-manager-aio cloudify-helm/cloudify-manager-aio ``` -To understand all available options AIO Cloudify Manager chart has, please read [Cloudify AIO Helm chart]({{< relref "cloudify_manager/premium/helm/installing-helm-aio.md" >}}). +To understand all available options AIO {{< param cfy_manager_name >}} chart has, please read [{{< param product_name >}} AIO Helm chart]({{< relref "cloudify_manager/premium/helm/installing-helm-aio.md" >}}). -To understand all available options for the AIO {{< param cfy_manager_name >}} chart, please see the [Cloudify AIO Helm chart documentation.]({{< relref "cloudify_manager/premium/helm/installing-helm-aio.md" >}}) +To understand all available options for the AIO {{< param cfy_manager_name >}} chart, please see the [{{< param product_name >}} AIO Helm chart documentation.]({{< relref "cloudify_manager/premium/helm/installing-helm-aio.md" >}}) ## {{< param company_name >}} Manager Worker Helm Chart (Premium Version) @@ -53,7 +53,7 @@ The {{< param company_name >}} Manager Worker Helm chart deploys a highly availa * External PostgreSQL database support. This can also be deployed into Kubernetes by using the [Bitnami PostgreSQL Helm chart](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) * External RabbitMQ Message Broker support. This can also be deployed into Kubernetes using the [Bitnami RabbitMQ Helm chart](https://github.com/bitnami/charts/tree/master/bitnami) -This is how the setup looks after it's deployed to 'cfy-example' namespace (it's possible to have multiple replicas (pods) of the Cloudify Manager): +This is how the setup looks after it's deployed to 'cfy-example' namespace (it's possible to have multiple replicas (pods) of the {{< param cfy_manager_name >}}): The diagram below shows an example architecture deployed to the `cfy-example` namespace. **Note**: It is possible to have multiple pod replicas of the {{< param cfy_manager_name >}}. diff --git a/content/trial_getting_started/tf_start/tf_geting_started.md b/content/trial_getting_started/tf_start/tf_geting_started.md index 6c8e17e44..b37a83132 100644 --- a/content/trial_getting_started/tf_start/tf_geting_started.md +++ b/content/trial_getting_started/tf_start/tf_geting_started.md @@ -58,7 +58,7 @@ There are a few things that you should know about the structure of Terraform mod * It is possible to use archive URLs that are generated by services like Github (as we do in this example). * For archives that contain multiple modules, you are able to choose the module you need by selecting the path in the dropdown. -In this example, we will use an example module from the [Cloudify Community GitHub repository](https://github.com/cloudify-community/tf-source). Provide the following information under the "Terraform module details" section: +In this example, we will use an example module from the [{{< param product_name >}} Community GitHub repository](https://github.com/cloudify-community/tf-source). Provide the following information under the "Terraform module details" section: * **Terraform module source:** Provide the following URL to the community example: https://github.com/cloudify-community/tf-source/archive/refs/heads/main.zip * **Terraform module folder:** Select `tf-source-main/template/modules/public_vm` from the dropdown menu. diff --git a/content/trial_getting_started/tf_start/tf_marketplace.md b/content/trial_getting_started/tf_start/tf_marketplace.md index 35f5b4e50..419e38a36 100644 --- a/content/trial_getting_started/tf_start/tf_marketplace.md +++ b/content/trial_getting_started/tf_start/tf_marketplace.md @@ -11,7 +11,7 @@ Getting Started guide to uploading and deploying Terraform based blueprints from This getting started guide introduces you to uploading and deploying Terraform-based blueprints from the {{< param company_name >}} Marketplace. ## Prerequisites -* Cloudify Manager Version 6.4 or later +* {{< param cfy_manager_name >}} Version 6.4 or later * Credentials to a cloud provider, such as AWS ## Overview