Shavi rebranding

Gemfile

@@ -1,7 +1,7 @@
 source "https://rubygems.org"
 
-gem 'jekyll', '~> 4.0', '>= 4.0.1'
-gem 'nokogiri', '~> 1.14.3'
+gem 'jekyll', '~> 4.3', '>= 4.3.3'
+gem 'nokogiri', '~> 1.16.2'
 group :jekyll_plugins do
   gem 'algoliasearch-jekyll', '~> 0.8.0'
 end

Gemfile.lock

@@ -1,9 +1,9 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    addressable (2.8.0)
-      public_suffix (>= 2.0.2, < 5.0)
-    algoliasearch (1.26.0)
+    addressable (2.8.6)
+      public_suffix (>= 2.0.2, < 6.0)
+    algoliasearch (1.27.5)
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
     algoliasearch-jekyll (0.8.2)
@@ -19,92 +19,99 @@ GEM
       thor (>= 0.14.0)
     awesome_print (1.9.2)
     colorator (1.1.0)
-    concurrent-ruby (1.1.8)
-    em-websocket (0.5.2)
+    concurrent-ruby (1.2.3)
+    em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
+      http_parser.rb (~> 0)
     eventmachine (1.2.7)
     eventmachine (1.2.7-x64-mingw32)
-    ffi (1.15.0)
-    ffi (1.15.0-x64-mingw32)
+    ffi (1.16.3)
     forwardable-extended (2.6.0)
-    http_parser.rb (0.6.0)
+    google-protobuf (3.25.3)
+    http_parser.rb (0.8.0)
     httpclient (2.8.3)
-    i18n (1.8.9)
+    i18n (1.14.1)
       concurrent-ruby (~> 1.0)
-    jekyll (4.2.0)
+    jekyll (4.3.3)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
       i18n (~> 1.0)
-      jekyll-sass-converter (~> 2.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 2.3)
+      kramdown (~> 2.3, >= 2.3.1)
       kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.4.0)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (~> 3.0)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-      terminal-table (~> 2.0)
-    jekyll-sass-converter (2.1.0)
-      sassc (> 2.0.1, < 3.0)
-    jekyll-sitemap (1.3.1)
+      terminal-table (>= 1.8, < 4.0)
+      webrick (~> 1.7)
+    jekyll-sass-converter (3.0.0)
+      sass-embedded (~> 1.54)
+    jekyll-sitemap (1.4.0)
       jekyll (>= 3.7, < 5.0)
-    jekyll-target-blank (2.0.0)
+    jekyll-target-blank (2.0.2)
       jekyll (>= 3.0, < 5.0)
       nokogiri (~> 1.10)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.3.1)
-    kramdown (2.3.1)
+    json (2.7.1)
+    kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
       kramdown (~> 2.0)
-    liquid (4.0.3)
-    listen (3.5.0)
+    liquid (4.0.4)
+    listen (3.9.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
     mercenary (0.4.0)
-    mini_portile2 (2.8.1)
-    nokogiri (1.14.3)
-      mini_portile2 (~> 2.8.0)
+    mini_portile2 (2.8.5)
+    nokogiri (1.16.2)
+      mini_portile2 (~> 2.8.2)
       racc (~> 1.4)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (4.0.6)
-    racc (1.6.2)
-    rake (13.0.1)
-    rb-fsevent (0.10.4)
+    public_suffix (5.0.4)
+    racc (1.7.3)
+    rake (13.1.0)
+    rb-fsevent (0.11.2)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    rexml (3.2.5)
-    rouge (3.26.0)
+    rexml (3.2.6)
+    rouge (4.2.0)
     safe_yaml (1.0.5)
-    sassc (2.4.0)
-      ffi (~> 1.9)
-    sassc (2.4.0-x64-mingw32)
-      ffi (~> 1.9)
-    terminal-table (2.0.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    thor (0.20.3)
-    unicode-display_width (1.7.0)
+    sass-embedded (1.71.1)
+      google-protobuf (~> 3.25)
+      rake (>= 13.0.0)
+    sass-embedded (1.71.1-x64-mingw32)
+      google-protobuf (~> 3.25)
+    sass-embedded (1.71.1-x86_64-darwin)
+      google-protobuf (~> 3.25)
+    sass-embedded (1.71.1-x86_64-linux-gnu)
+      google-protobuf (~> 3.25)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    thor (1.3.1)
+    unicode-display_width (2.5.0)
     verbal_expressions (0.1.5)
     webrick (1.8.1)
 
 PLATFORMS
   x64-mingw32
   x64-unknown
   x86_64-darwin-20
+  x86_64-darwin-23
   x86_64-linux
 
 DEPENDENCIES
   algoliasearch-jekyll (~> 0.8.0)
-  jekyll (~> 4.0, >= 4.0.1)
+  jekyll (~> 4.3, >= 4.3.3)
   jekyll-sitemap
   jekyll-target-blank
   kramdown-parser-gfm
-  nokogiri (~> 1.14.3)
+  nokogiri (~> 1.16.2)
   webrick (~> 1.7)
 
 BUNDLED WITH

pages/doc/csp_invite-AoA-users_tutorial.md

@@ -4,20 +4,20 @@ keywords:
 tags: [tutorials]
 sidebar: doc_sidebar
 permalink: csp_new_users_tutorial.html
-summary: Learn how to invite new users to VMware Aria Operations for Applications through the VMware Cloud Services Console.
+summary: Learn how to invite new users to Tanzu Observability (formerly known as VMware Aria Operations for Applications) through the VMware Cloud Services Console.
 ---
 
-Starting July 3, 2023, Operations for Applications is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: 
-* Operations for Applications subscriptions **onboarded** to the VMware Cloud services platform.
+Starting July 3, 2023, Tanzu Observability is a service on the VMware Cloud services platform. After this date, we support two types of subscriptions: 
+* Tanzu Observability subscriptions **onboarded** to the VMware Cloud services platform.
 * **Original** subscriptions -- the existing ones which remain as is until they migrate to VMware Cloud services. 
 
-In this tutorial, you’ll learn how to invite new users to Operations for Applications through the VMware Cloud Services Console.
+In this tutorial, you’ll learn how to invite new users to Tanzu Observability through the VMware Cloud Services Console.
 
 ## Requirements
 
 When your service **is onboarded** to VMware Cloud services, all new users are invited through the VMware Cloud Services Console. 
 
-To invite users, you must have the VMware Cloud **Organization Owner** or **Organization Administrator** role. You can invite users to your organization and grant them access to the services associated with it - in this case, this is Operations for Applications. You can also track the invitations you send. Invitations are valid for up to seven days. If you have sent an invitation in error, you can revoke it.
+To invite users, you must have the VMware Cloud **Organization Owner** or **Organization Administrator** role. You can invite users to your organization and grant them access to the services associated with it - in this case, this is Tanzu Observability. You can also track the invitations you send. Invitations are valid for up to seven days. If you have sent an invitation in error, you can revoke it.
 
 
 ## Roles to Assign
@@ -28,7 +28,7 @@ When you invite new users, you must assign them:
 
   Note that you can assign the **Organization Owner** role to another user only if you have the **Organization Owner** role.
 
-* A role within the Operations for Applications service instance. 
+* A role within the Tanzu Observability service instance. 
 
 Optionally, you can also assign a custom role created in the VMware Cloud organization. Custom roles are composed of different service permissions.
 
@@ -42,10 +42,10 @@ Optionally, you can also assign a custom role created in the VMware Cloud organi
 
 ### Step 2: Navigate to Your Organization
 
-VMware Cloud uses organizations to provide controlled access to one or more services. As an enterprise using multiple cloud services, Organizations provide an easy way to map your business groups and processes to different organizations. If you belong to more organizations, you must navigate to the organization to which Operations for Applications is onboarded. 
+VMware Cloud uses organizations to provide controlled access to one or more services. As an enterprise using multiple cloud services, Organizations provide an easy way to map your business groups and processes to different organizations. If you belong to more organizations, you must navigate to the organization to which Tanzu Observability is onboarded. 
 
 1. Click your username and click **Change Organization**.
-2. Select the name of the organization to which Operations for Applications is **onboarded**. 
+2. Select the name of the organization to which Tanzu Observability is **onboarded**. 
 
 ### Step 3: Find Your Roles Within the Organization
 
@@ -56,12 +56,12 @@ If do not have the VMware Cloud **Organization Owner** or **Organization Adminis
 
 ## Invite a New User and Assign Service Roles Only
 
-We provide a number of built-in Operations for Applications service roles.
+We provide a number of built-in Tanzu Observability service roles.
 
 - A corresponding service role for each [permission](csp_permissions_overview.html#operations-for-applications-permissions).
 - Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service.
 
-For more information, see [Operations for Applications Service Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
+For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
 
 ### Step 1: Enter the New User Details
 
@@ -73,7 +73,7 @@ For more information, see [Operations for Applications Service Roles (Built-in)]
 
 ### Step 2: Assign Roles and Invite the User
 
-In a multi-tenant environment, you can assign different service roles for each Operations for Applications instance. Let's first assign the mandatory organization role and then we will assign different service roles for two Operations for Applications instances. 
+In a multi-tenant environment, you can assign different service roles for each Tanzu Observability instance. Let's first assign the mandatory organization role and then we will assign different service roles for two Tanzu Observability instances. 
 
 1. Select a mandatory organization role to assign.
 
@@ -83,12 +83,12 @@ In a multi-tenant environment, you can assign different service roles for each O
 
    ![A screenshot with the Organization Member role, selected by default and the Support user additional role selected.](images/csp-mandatory-roles.png)
 
-2. Assign Operations for Applications service roles for the first Operations for Applications instance.
+2. Assign Tanzu Observability service roles for the first Tanzu Observability instance.
    1. Click **Add a Service**.
-   1. From the drop-down menu, select **VMware Aria Operations for Applications**.
-      ![A screenshot with the Operations for Applications service selected.](images/csp-select-service.png)
+   1. From the drop-down menu, select **Tanzu Observability**.
+      ![A screenshot with the Tanzu Observability service selected.](images/csp-select-service.png)
    1. From the **in** drop-down menu, select the service instance to which you want to invite the new user.
-      ![A screenshot with the Operations for Applications service instance selected.](images/csp-select-aoa-service.png)
+      ![A screenshot with the Tanzu Observability service instance selected.](images/csp-select-aoa-service.png)
    1. Assign the service roles to the user.
 
       Let's say that the user you're inviting will:
@@ -100,17 +100,17 @@ In a multi-tenant environment, you can assign different service roles for each O
 
       For this purpose, select the following service roles: **Proxies**, **Integrations**, **Dashboards**, and **Alerts**.
 
-      ![A screenshot with the Operations for Applications roles selected.](images/csp-assign-service-roles.png)
+      ![A screenshot with the Tanzu Observability roles selected.](images/csp-assign-service-roles.png)
    1. Leave the never expires access field as is.
 
-3. Assign the **Super Admin** service role for another Operations for Applications instance.
+3. Assign the **Super Admin** service role for another Tanzu Observability instance.
 
    1. Click **+ Add an Instance**.
    1. From the **in** drop-down menu, select the other service instance to which you want to invite the new user.
-      ![A screenshot with the Operations for Applications service instance selected.](images/csp-select-another-service.png)
+      ![A screenshot with the Tanzu Observability service instance selected.](images/csp-select-another-service.png)
    1. Assign the **Super Admin** service role to the user.
 
-      ![A screenshot with the Operations for Applications roles selected.](images/csp-assign-superadmin-service-role.png)
+      ![A screenshot with the Tanzu Observability roles selected.](images/csp-assign-superadmin-service-role.png)
    1. Leave the never expires access field as is.
 4. Leave the **Send emails to all invited users notifying them of this role assignment** selected and click **Add**.
 
@@ -124,7 +124,7 @@ If you have created custom roles and want to assign custom roles to a user, you
 * At least one service role, for example **Viewer**
 * The custom roles of interest
 
-Custom roles work only in combination with service roles. The Operations for Applications permissions in a custom role apply to all service instances (tenants) for which the user has at least one Operations for Applications service role. 
+Custom roles work only in combination with service roles. The Tanzu Observability permissions in a custom role apply to all service instances (tenants) for which the user has at least one Tanzu Observability service role. 
 
 ### Step 1: Enter the New User Details
 
@@ -142,23 +142,23 @@ Let's assign **Organization Administrator** as a mandatory organization role, th
 
    ![A screenshot with the Organization Administrator role selected.](images/csp-assign-org-admin.png)
 
-2. Assign the **Viewer** service role for a specific Operations for Applications service instance.
+2. Assign the **Viewer** service role for a specific Tanzu Observability service instance.
    1. Click **Add a Service**.
-   1. From the drop-down menu, select **VMware Aria Operations for Applications**.
-      ![A screenshot with the Operations for Applications service selected.](images/csp-select-service.png)
+   1. From the drop-down menu, select **Tanzu Observability**.
+      ![A screenshot with the Tanzu Observability service selected.](images/csp-select-service.png)
    1. From the **in** drop-down menu, select the service instance to which you want to invite the new user and leave the **Viewer** service role selected so that you assign it to the user.
-      ![A screenshot with the Operations for Applications service instance  and the Viewer role selected.](images/csp-select-aoa-service-viewer.png)
+      ![A screenshot with the Tanzu Observability instance  and the Viewer role selected.](images/csp-select-aoa-service-viewer.png)
    1. Leave the never expires access field as is.
-3. Assign the **Ingestion Policies** service role for another Operations for Applications service instance.
+3. Assign the **Ingestion Policies** service role for another Tanzu Observability service instance.
    1. Click **+Add an Instance**.
    1. From the **in** drop-down menu, select the other service instance to which you want to invite the new user.
    1. Select the **Ingestion Policies** service role to assign it to the user.
-      ![A screenshot with the Operations for Applications service instance and the Viewer and the Ingestion Policies service roles selected.](images/csp-assign-two-service-roles.png)
+      ![A screenshot with the Tanzu Observability service instance and the Viewer and the Ingestion Policies service roles selected.](images/csp-assign-two-service-roles.png)
    1. Leave the never expires access field as is.
 
 3. Assign the custom role to the user.
 
-   The custom role is assigned for the already selected Operations for Applications service instances.
+   The custom role is assigned for the already selected Tanzu Observability service instances.
 
    1. Click **+ Add Custom Roles Access**.
    1. In the **Add custom role access** popup window, search for, select the custom role that you want to assign, and click **Add**.