[EDU-6790] Update-products-observe-reference

cicd/massive-redirect/en.json

@@ -1774,4 +1774,18 @@
     "from": "https://www.azion.com/en/documentation/products/build/edge-application/websocket/",
     "moved": "https://www.azion.com/en/documentation/products/build/applications/websocket/"
   }
+  ,
+  {
+    "from": "https://www.azion.com/en/documentation/products/deploy/edge-orchestrator/edge-node/",
+    "moved": "https://www.azion.com/en/documentation/products/deploy/orchestrator/edge-node/"
+  }
+  ,
+  {
+    "from": "https://www.azion.com/en/documentation/products/deploy/edge-orchestrator/",
+    "moved": "https://www.azion.com/en/documentation/products/deploy/orchestrator/"
+  },
+  {
+    "from": "https://www.azion.com/en/documentation/products/deploy/edge-orchestrator/edge-services/",
+    "moved": "https://www.azion.com/en/documentation/products/deploy/orchestrator/edge-services/"
+  }
 ]

cicd/massive-redirect/pt-br.json

@@ -1791,5 +1791,21 @@
   {
     "from": "https://www.azion.com/pt-br/documentacao/produtos/build/edge-application/websocket/",
     "moved": "https://www.azion.com/pt-br/documentacao/produtos/build/applications/websocket/"
+  },
+  {
+    "from": "https://www.azion.com/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-node/",
+    "moved": "https://www.azion.com/pt-br/documentacao/produtos/deploy/orchestrator/edge-node/"
+  },
+  {
+    "from": "https://www.azion.com/pt-br/documentacao/produtos/deploy/edge-orchestrator/",
+    "moved": "https://www.azion.com/pt-br/documentacao/produtos/deploy/orchestrator/"
+  },
+  {
+    "from": "https://www.azion.com/pt-br/documentacao/produtos/deploy/edge-orchestrator/",
+    "moved": "https://www.azion.com/pt-br/documentacao/produtos/deploy/orchestrator/"
+  },
+  {
+    "from": "https://www.azion.com/pt-br/documentacao/produtos/deploy/edge-orchestrator/edge-services/",
+    "moved": "https://www.azion.com/pt-br/documentacao/produtos/deploy/orchestrator/edge-services/"
   }
 ]

src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-node.mdx

@@ -1,11 +1,11 @@
 ---
-title: Edge Node
+title: Azion Edge Node
 description: >-
   Azion Edge Node enables you to create your own edge infrastructure, allowing
   you to install services and resources in real time.
 meta_tags: 'Azion Edge Node, Edge Computing'
 namespace: documentation_products_edge_orchestrator_edge_nodes
-permalink: /documentation/products/deploy/edge-orchestrator/edge-node/
+permalink: /documentation/products/deploy/orchestrator/edge-node/
 ---
 
 Azion **Edge Node** enables you to create your own edge infrastructure, allowing you to install services and resources in real time.
@@ -23,25 +23,25 @@ It's an open software that can be run on different types of microprocessor archi
 
 | Scope | Guide |
 | - | - | 
-| Edge Node | [Edge Node first steps](/en/documentation/products/guides/edge-node-first-steps/) |
+| Edge Node | [ Edge Node first steps](/en/documentation/products/guides/edge-node-first-steps/) |
 
 ---
 
 ## Agent commands and options
 
-The Edge Orchestrator agent has additional commands and options to make it easier to use.
+The Orchestrator agent has additional commands and options to make it easier to use.
 
 | Command | Description |
 | :--- | :--- |
 | --debug or -d | Sets the agent logs to debug mode. |
 | --help or -h | Helps with the commands that the agent can execute. |
-| install | Installs the agent to the client’s device, copies the binary to the installation location; adds the Edge Orchestrator agent to the device's service manager (if any) and; sets up a personal token to authenticate the Edge Node. |
-| start \[--foreground\] | Initializes the Edge Orchestrator agent through the device's service manager.<br /> **Note**: the foreground option is used to run it in the foreground. |
-| start -g or --join-group | Enrolls your edge node with the specified groups through the command line while starting your node for the first time. You can use these flags followed by a list of group names separated by a comma. <br/>For example: `sudo edge-orchestrator start -g GROUP1,GROUP2,GROUP3 --foreground` |
-| start \[-n OR --set-name\] | Enrolls your edge node for the first time under the specified node’s name. If these flags are not used, `hostname` will be the default value. <br/>For example: `sudo edge-orchestrator start -n Edgenodename --foreground` |
-| status | Reports on the status of the execution of the Edge Orchestrator agent. |
-| stop | Stops the Edge Orchestrator agent through the device's service manager. |
-| uninstall | Uninstalls the agent from the client’s device; removes the binary from the installation location; removes the Edge Orchestrator agent from the device's service manager (if any).<br /> |
+| install | Installs the agent to the client’s device, copies the binary to the installation location; adds the Orchestrator agent to the device's service manager (if any) and; sets up a personal token to authenticate the Edge Node. |
+| start \[--foreground\] | Initializes the Orchestrator agent through the device's service manager.<br /> **Note**: the foreground option is used to run it in the foreground. |
+| start -g or --join-group | Enrolls your Edge Node with the specified groups through the command line while starting your node for the first time. You can use these flags followed by a list of group names separated by a comma. <br/>For example: `sudo edge-orchestrator start -g GROUP1,GROUP2,GROUP3 --foreground` |
+| start \[-n OR --set-name\] | Enrolls your Edge Node for the first time under the specified node’s name. If these flags are not used, `hostname` will be the default value. <br/>For example: `sudo edge-orchestrator start -n Edgenodename --foreground` |
+| status | Reports on the status of the execution of the Orchestrator agent. |
+| stop | Stops the Orchestrator agent through the device's service manager. |
+| uninstall | Uninstalls the agent from the client’s device; removes the binary from the installation location; removes the Orchestrator agent from the device's service manager (if any).<br /> |
 | --version or -v | It displays the installed version of the agent. |
 
 ---

src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-orchestrator.mdx

@@ -1,20 +1,20 @@
 ---
-title: Edge Orchestrator
+title: Orchestrator
 description: >-
-  Azion Edge Orchestrator is an end-to-end encrypted orchestration service with
+  Azion Orchestrator is an end-to-end encrypted orchestration service with
   cloud management and zero-touch provisioning, created for large-scale Edge
   networks. Manage and control resources on the edge in real time and
   orchestrate your services quickly and easily to meet your needs.
 meta_tags: 'Orchestrator, Edge Computing'
 namespace: documentation_products_edge_orchestrator
-permalink: /documentation/products/deploy/edge-orchestrator/
+permalink: /documentation/products/deploy/orchestrator/
 ---
 
-Azion **Edge Orchestrator** is an end-to-end encrypted orchestration service with cloud management and zero-touch provisioning, created for large-scale edge networks. You can manage and control resources on the edge in real time, as well as orchestrate your services quickly and easily to meet your needs.
+Azion **Orchestrator** is an end-to-end encrypted orchestration service with cloud management and zero-touch provisioning, created for large-scale edge networks. You can manage and control resources on the edge in real time, as well as orchestrate your services quickly and easily to meet your needs.
 
-With Edge Orchestrator, you can:
+With Orchestrator, you can:
 
-- Manage and control edge resources in real time, including provisioning, updating, and managing edge applications, edge firewalls, edge functions, digital certificates, edge nodes, edge services, and third-party services via Marketplace.
+- Manage and control edge resources in real time, including provisioning, updating, and managing edge applications, edge firewalls, edge functions, digital certificates, Nodes, Services, and third-party services via Marketplace.
 
 - Operate and run on different types of architecture: microprocessors, like x86 and ARM, and different sizes of equipment, including Raspberry PI, network equipment such as switches and SD-WAN routers, as well as corporate servers, because it was designed for it.
 
@@ -28,41 +28,41 @@ With Edge Orchestrator, you can:
 
 | Scope | Guide |
 | - | - | 
-| Edge Node | [Edge Node first steps](/en/documentation/products/guides/edge-node-first-steps/) |
-| Edge Services| [Creating an Edge Service](/en/documentation/products/guides/edge-services-first-steps/) |
+| Node | [Node first steps](/en/documentation/products/guides/edge-node-first-steps/) |
+| Services| [Creating an Edge Service](/en/documentation/products/guides/edge-services-first-steps/) |
 
 ---
 
-## Azion Edge Orchestrator agent
+## Azion Orchestrator agent
 
-An Azion Edge Orchestrator agent is installed on the edge nodes and provides end-to-end encrypted remote node management from [Azion Console](https://console.azion.com). 
+An Azion Orchestrator agent is installed on the Nodes and provides end-to-end encrypted remote node management from [Azion Console](https://console.azion.com). 
 
 It can be deployed through:
 
-1. Manual installation on each edge node.
-2. Automatic installation along with the operating system: a Linux distro or the image of a client's OS or hardware supplier. For example: an SD-WAN router, a network switch, or a Linux server. Customers can use an automatic registration mode, which makes it simpler to deploy (for example: new node locations or using automatic node scaling), update, and manage a large number of scaling edge nodes.
+1. Manual installation on each Node.
+2. Automatic installation along with the operating system: a Linux distro or the image of a client's OS or hardware supplier. For example: an SD-WAN router, a network switch, or a Linux server. Customers can use an automatic registration mode, which makes it simpler to deploy (for example: new node locations or using automatic node scaling), update, and manage a large number of scaling Nodes.
 
-All services linked to edge nodes will be orchestrated and configured from the moment the device is authorized via the control panel.
+All services linked to Nodes will be orchestrated and configured from the moment the device is authorized via the control panel.
 
 The orchestration is done sequentially and respects the dependencies between resources and triggers needed for its configuration.
 
-Learn more about the [Azion Edge Orchestrator agent installation](/en/documentation/products/guides/edge-node-first-steps/#installing).
+Learn more about the [Azion Orchestrator agent installation](/en/documentation/products/guides/edge-node-first-steps/#installing).
 
 ---
 
-## Edge Node
+## Node
 
-**Edge Node** enables the creation and management of devices, as well as integration with Azion. You need to install our agent so that the Azion platform can orchestrate its settings and ensure secure communication between the devices and Azion.
+**Node** enables the creation and management of devices, as well as integration with Azion. You need to install our agent so that the Azion platform can orchestrate its settings and ensure secure communication between the devices and Azion.
 
-[Learn more about Edge Node](/en/documentation/products/deploy/edge-orchestrator/edge-node/).
+[Learn more about Node](/en/documentation/products/deploy/edge-orchestrator/edge-node/).
 
 ---
 
-## Edge Services
+## Services
 
-**Edge Services** enables you to create your own services. You can use your customized services and ensure your device is managed and orchestrated by [Azion Console](https://console.azion.com).
+**Services** enables you to create your own services. You can use your customized services and ensure your device is managed and orchestrated by [Azion Console](https://console.azion.com).
 
-[Learn more about Edge Services](/en/documentation/products/deploy/edge-orchestrator/edge-services/).
+[Learn more about Services](/en/documentation/products/deploy/edge-orchestrator/edge-services/).
 
 
 

src/content/docs/en/pages/main-menu/reference/deploy/edge-orchestrator/edge-services.mdx

@@ -1,14 +1,14 @@
 ---
-title: Edge Services
+title: Azion Edge Services
 description: >-
-  Azion Edge Services is a module for the Edge Orchestrator product that allows
+  Azion Edge Services is a module for the Orchestrator product that allows
   orchestrated services to be managed within your own edge infrastructure.
-meta_tags: 'Services, Edge Computing'
+meta_tags: 'Edge Services, Edge Computing'
 namespace: documentation_products_edge_orchestrator_edge_services
-permalink: /documentation/products/deploy/edge-orchestrator/edge-services/
+permalink: /documentation/products/deploy/orchestrator/edge-services/
 ---
 
-**Azion Edge Services** is an **Edge Orchestrator** product module that allows orchestrated services to be managed in your own nodes, enabling the resources registration and other configurations via [Azion Console](https://console.azion.com) and the services creation and customization so that they can be orchestrated on the defined Edge Nodes.
+**Azion Edge Services** is an **Orchestrator** product module that allows orchestrated services to be managed in your own Edge Nodes, enabling the resources registration and other configurations via [Azion Console](https://console.azion.com) and the services creation and customization so that they can be orchestrated on the defined Edge Nodes.
 
 You can configure the install, uninstall, and reload triggers and define the dependencies between the resources needed to run your service on your edge network.
 
@@ -18,13 +18,13 @@ You can configure the install, uninstall, and reload triggers and define the dep
 
 | Scope | Guide |
 | - | - | 
-| Edge Services| [Creating an Edge Service](/en/documentation/products/guides/edge-services-first-steps/) |
+| Edge Services| [Creating an Service](/en/documentation/products/guides/edge-services-first-steps/) |
 
 ---
 
 ## How it works
 
-By using Azion as your edge platform, you can create and customize services to run on private and hybrid edge networks. Azion **Edge Services** operates using triggers to install, uninstall, and reload. It defines dependencies between resources and natively implements a set of functions for Azion products, such as **Edge Application**, **Edge Firewall**, and **Edge Functions**, using **Azion Cells** technology from Azion as its basis.
+By using Azion as your edge platform, you can create and customize services to run on private and hybrid edge networks. Azion **Edge Services** operates using triggers to install, uninstall, and reload. It defines dependencies between resources and natively implements a set of functions for Azion products, such as **Applications**, **Firewall**, and **Functions**, using **Azion Cells** technology from Azion as its basis.
 
 This way, you can build edge applications for a wide variety of uses, such as hosting other applications, implementing AI, VR applications, and many others. To do so, you must activate Azion Cells and define the **Edge Nodes** that should host certain applications, all controlled by the Azion dashboard or APIs, in a centralized interface, and with different access controls.
 
@@ -36,7 +36,7 @@ To be able to orchestrate services on your device, you need to configure all the
 
 A **Text** type resource indicates that the content will be copied as plain text to the device. These resource types are typically used for configuration files.
 
-A **Shell Script** type resource indicates that the resource will be installed and ran according to the selected **trigger**. The Edge Orchestrator agent uses the sh-bang entered in the content header for script execution. In the absence of one, the POSIX-compliant **shell** on the device (`/bin/sh`) is used.
+A **Shell Script** type resource indicates that the resource will be installed and ran according to the selected **trigger**. The Orchestrator agent uses the sh-bang entered in the content header for script execution. In the absence of one, the POSIX-compliant **shell** on the device (`/bin/sh`) is used.
 
 Both resource types are compatible with the use of **variables** and **facts**, as long as the tag `{{ VARNAME }}` or `{{ FACT_NAME }}` is included.
 
@@ -63,13 +63,13 @@ There are some special predefined variables that, as facts, cannot be overwritte
 
 ## Facts
 
-In addition to the defined variables, you can also use **Facts** which are available technical information about your node, such as architecture, client version, operating system, and operating system version. You can use these if you're setting up multiple nodes.
+In addition to the defined variables, you can also use **Facts** which are available technical information about your node, such as architecture, client version, operating system, and operating system version. You can use these if you're setting up multiple Edge Nodes.
 
 These values cannot be overwritten and can be used in **resources** using the `{{ FACT_NAME }}` tag. For example:<br /> `{{CLIENT_VERSION}}`.
 
 | Facts | Description | Value | Notes |
 | :---: | :---: | :---: | :---: |
-| CLIENT_VERSION | Edge Orchestrator agent version | MAJOR.MINOR.PATCH | For example: 1.10.3, where 1 is MAJOR, 10 is MINOR and 3 is PATCH |
+| CLIENT_VERSION | Orchestrator agent version | MAJOR.MINOR.PATCH | For example: 1.10.3, where 1 is MAJOR, 10 is MINOR and 3 is PATCH |
 | ARCH | Processor architecture | ARM or; AMD (x86), both with 32 or 64 bits |  |
 | OS_NAME | Operating System distribution name | macOS; Linux; FreeBSD; OpenBSD; DragonFlyBSD; NetBSD; or Solaris |  |
 | OS_DISTRO | Operating System distribution name, only for systems based on Linux | NAME + RELEASE | NAME: Debian; Ubuntu; openSUSE; Mint Linux; Gentoo; Fedora; CentOS; Arch Linux or; Kali Linux <br /> <br /> RELEASE: first obtaining via LSB Release, if there is no search in /etc/os-release the value of VERSION_ID or DISTRIB_RELEASE <br /> <br /> In the case of other Operating Systems the value will always be empty. |