DOC-5684: New product name (#204)

* new-product-name

* peer-review

* no-kaap

* fix-double-name

Author: mendonk

README.adoc

@@ -1,7 +1,7 @@
-= {company} {product} Docs
+= {product} Docs (formerly {company} Luna Streaming)
 // Variables:
 :company: DataStax
-:product: Luna Streaming
+:product: IBM Elite Support for Apache Pulsar
 :repo-name: pulsar-docs
 :github-org: datastax
 // Settings:
@@ -32,7 +32,7 @@ endif::[]
 // External URLs:
 :asciidoc-language: https://docs.asciidoctor.org/asciidoc/latest/
 
-This repository contains the source files for the {company} {product} documentation.
+This repository contains the source files for the {product} documentation.
 
 toc::[]
 

antora.yml

@@ -1,14 +1,14 @@
 name: 'luna-streaming'
 version: '2.10-3.x'
-title: 'Luna Streaming'
+title: 'IBM Elite Support for Apache Pulsar'
 start_page: 'index.adoc'
 
 nav:
 - modules/ROOT/nav.adoc
 
 asciidoc:
   attributes:
-    product: 'Luna Streaming'
+    product: 'IBM Elite Support for Apache Pulsar'
     luna-version: '2.10'
     pulsar-version: '2.10'
     admin-console-version: '2.0.4'

modules/ROOT/pages/faqs.adoc

@@ -1,40 +1,45 @@
 = {product} FAQs
 :navtitle: FAQs
 
-If you are new to {company} {product} and its {pulsar} enhancements, these FAQs are for you.
+If you are new to {product} and its {pulsar} enhancements, these FAQs are for you.
 
-== What is {company} {product}?
+== What is {product}?
 
-{company} {product} is a new Kubernetes-based distribution of {pulsar}, based on the technology that https://kesque.com/[Kesque] built to run its {pulsar-short}-as-a-service.
+{product} is a Kubernetes-based distribution of {pulsar}, based on the technology that https://kesque.com/[Kesque] built to run its {pulsar-short}-as-a-service.
 
-== What components and features are provided by {company} {product}?
+== Are {product} and {company} Luna Streaming the same offering?
 
-In addition to {pulsar} itself, {company} {product} provides:
+Yes.
+include::partial$luna-name.adoc[]
+
+== What components and features are provided by {product}?
+
+In addition to {pulsar} itself, {product} provides:
 
 * An installer that can stand up a dev or production cluster on bare metal or VMs without a pre-existing Kubernetes environment
 * A Helm chart that can deploy and manage {pulsar-short} on your current Kubernetes infrastructure
 * {cass-short}, Elastic, Kinesis, {kafka-reg}, and JDBC connectors
 * A management dashboard
 * A monitoring and alerting system
 
-== On which version of {pulsar} is {company} {product} based?
+== On which version of {pulsar} is {product} based?
 
-{company} {product} {luna-version} is based on its distribution of {pulsar} {pulsar-version}, plus features and additional enhancements from {company} contributors.
+{product} {luna-version} is based on its distribution of {pulsar} {pulsar-version}, plus features and additional enhancements from {company} contributors.
 
-== What does {company} {product} provide that I cannot get with open-source {pulsar}?
+== What does {product} provide that I cannot get with open-source {pulsar}?
 
-{company} {product} is a hardened version of {pulsar} that been run through additional testing to ensure it is ready for production use. It also includes additional tooling to help monitor your system, including an enhanced Admin Console and a Heartbeat service to monitor the system health.
+{product} is a hardened version of {pulsar} that been run through additional testing to ensure it is ready for production use. It also includes additional tooling to help monitor your system, including an enhanced Admin Console and a Heartbeat service to monitor the system health.
 
-== Is {company} {product} an open-source project?
+== Is {product} an open-source project?
 
-Yes, {company} {product} is open source. See the <<gitHubRepos,repos FAQ>>.
+Yes, {product} is open source. See the <<gitHubRepos,repos FAQ>>.
 
-== Which Kubernetes platforms are supported by {company} {product}?
+== Which Kubernetes platforms are supported by {product}?
 
 They include Minikube, K8d, Kind, Google Kubernetes Engine (GKE), Microsoft Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and other commonly used platforms.
 
 [#gitHubRepos]
-== Where are the {company} {product} public GitHub repos?
+== Where are the {product} public GitHub repos?
 
 There are several public repos, each with a different purpose. See:
 
@@ -45,25 +50,25 @@ There are several public repos, each with a different purpose. See:
 * {pulsar-sink-repo}[{pulsar-sink-repo}] : This is the {company} {pulsar} Connector (`pulsar-sink`) repo.
 * https://github.com/datastax/burnell[https://github.com/datastax/burnell] : This is a utility for {pulsar-short} that provides various functions, such as key initialization for authentication, and JWT token creation API.
 
-== Is there a prerequisite version of Java needed for the {company} {product} installation?
+== Is there a prerequisite version of Java needed for the {product} installation?
 
-The {company} {product} distribution is designed for Java 11. However, because the product releases Docker images, you do not need to install Java (8 or 11) in advance. Java 11 is bundled in the Docker image.
+The {product} distribution is designed for Java 17. However, because the product releases Docker images, you do not need to install Java 17 in advance. Java 17 is bundled in the Docker image.
 
-== What are the install options for {company} {product}?
+== What are the install options for {product}?
 
-* Use the Helm chart provided at {pulsar-helm-chart-repo}[{pulsar-helm-chart-repo}] to install {company} {product} in an existing Kubernetes cluster on your laptop or hosted by a cloud provider.
-* Use the tarball provided at {pulsar-repo}/releases[{pulsar-repo}/releases] to install {company} {product} on a server or VM.
-* Use the {company} Ansible scripts provided at {pulsar-ansible-repo}[{pulsar-ansible-repo}] to install {company} {product} on a server or VM with our provided playbooks.
+* **{product} Helm chart**: Use the Helm chart provided at {pulsar-helm-chart-repo}[{pulsar-helm-chart-repo}] to install {product} in an existing Kubernetes cluster on your laptop or hosted by a cloud provider.
+* **Tarball**: Use the tarball provided at {pulsar-repo}/releases[{pulsar-repo}/releases] to install {product} on a server or VM.
+* **Ansible**: Use the {company} Ansible scripts provided at {pulsar-ansible-repo}[{pulsar-ansible-repo}] to install {product} on a server or VM with our provided playbooks.
 
-== How do I install {company} {product} in my Kubernetes cluster?
+== How do I install {product} in my Kubernetes cluster?
 
 Follow the full instructions in xref:install-upgrade:quickstart-helm-installs.adoc[Quick Start for Helm Chart installs].
 
-== How do I install {company} {product} on my server or VM?
+== How do I install {product} on my server or VM?
 
 Follow the full instructions in xref:install-upgrade:quickstart-server-installs.adoc[Quick Start for Server/VM installs].
 
-== What task can I perform in the {company} {product} Admin Console?
+== What task can I perform in the {product} Admin Console?
 
 From the Admin Console, you can:
 
@@ -95,7 +100,7 @@ The {company} {pulsar} Connector allows single-record acknowledgement and negati
 
 There are two packages:
 
-* The `pulsar-sink` functionality of {company} {pulsar} Connector is included with {company} {product}. It's built in!
+* The `pulsar-sink` functionality of {company} {pulsar} Connector is included with {product}. It's built in!
 * You can optionally download the {company} {pulsar} Connector `.nar` file from the {pulsar-sink-repo}/releases[`pulsar-sink` repository], and then use it as its own product with your open-source {pulsar} install.
 
 If you're using open-source software (OSS) {pulsar}, you can use {company} {pulsar} Connector with the OSS to take advantage of this `pulsar-sink` for {cass-short}.
@@ -106,6 +111,6 @@ See the xref:pulsar-connector:ROOT:index.adoc[{company} {pulsar} Connector docum
 This source connector streams data changes from {cass-short} tables to {pulsar-short} topics.
 For more information, see the xref:cdc-for-cassandra:ROOT:index.adoc[{company} CDC for {cass-short} connector documentation].
 
-== What client APIs does {company} {product} provide?
+== What client APIs does {product} provide?
 
 The same as for {pulsar}. See https://pulsar.apache.org/docs/en/client-libraries/.

modules/ROOT/pages/index.adoc

@@ -1,17 +1,23 @@
-= Welcome to {company} {product}
+= Welcome to {product} (formerly {company} Luna Streaming)
 :navtitle: {product}
 
-{company} {product} is a production-ready distribution of {pulsar} built to run seamlessly on any CNCF conformant version of Kubernetes. {company} {product} provides all of the core capabilities included in the Apache Community version of {pulsar}, plus a number of additional tools and features to facilitate administration and operational tasks associated with running {pulsar} in production.
+{product} is a production-ready distribution of {pulsar} built to run seamlessly on any CNCF conformant version of Kubernetes.
+
+{product} provides all of the core capabilities included in the Apache Community version of {pulsar}, plus a number of additional tools and features to facilitate administration and operational tasks associated with running {pulsar} in production.
+
+include::partial$luna-name.adoc[]
 
 == Release notes
 
-The latest release of {company} {product} is {luna-version}, which matches the supported, distributed {pulsar-short} version numbers.
+The latest release of {product} is {luna-version}, which matches the supported, distributed {pulsar-short} version numbers.
+
+The prior {product} release (2.10.x) provided the {pulsar-short} 2.10.x distribution.
 
-Refer to the {company} {product} https://github.com/datastax/release-notes/blob/master/Luna_Streaming_2.10_Release_Notes.md[release notes], which are hosted in our public GitHub repo, for information & linked commit IDs that were implemented in the latest {product} {luna-version} release.
+Refer to the {product} https://github.com/datastax/release-notes/blob/master/Luna_Streaming_3.1_Release_Notes.md[release notes], which are hosted in our public GitHub repo, for information & linked commit IDs that were implemented in the latest {product} {luna-version} release.
 
 == Components
 
-In addition to the distribution of https://pulsar.apache.org/en/versions/[{pulsar} {pulsar-version}], {company} {product} provides:
+In addition to the distribution of https://pulsar.apache.org/en/versions/[{pulsar} {pulsar-version}], {product} provides:
 
 * A xref:install-upgrade:quickstart-helm-installs.adoc[Helm chart] that deploys and manages {pulsar-short} on your current CNCF-conformant Kubernetes infrastructure
 

modules/ROOT/partials/luna-name.adoc

@@ -0,0 +1,4 @@
+{product} is the new name for Luna Streaming after IBM acquired DataStax.
+In this documentation, {product} and Luna Streaming refer to the same product.
+
+For technical specifications, inclusions, and exclusions of the {product} offering, see the https://www.ibm.com/docs/en/supportforpulsar?topic=elite-support-pulsar[{product} page in the IBM documentation].

modules/components/pages/admin-console-tutorial.adoc

@@ -1,11 +1,11 @@
 = {pulsar-short} Admin Console
 
-The *{company} Admin Console for {pulsar-reg}* is a web-based UI from {company} that administers topics, namespaces, sources, sinks, and various aspects of {pulsar} features. 
+The *Admin Console for {pulsar-reg}* is a web-based UI from {company} that administers topics, namespaces, sources, sinks, and various aspects of {pulsar} features.
 
 [#getting-started]
 == Getting Started in {pulsar-short} Admin Console
 
-In the *{product} {pulsar-short} Admin Console*, you can use {pulsar-short} clients to send and receive pub/sub messages.
+In the *{pulsar-short} Admin Console*, you can use {pulsar-short} clients to send and receive pub/sub messages.
 
 If you installed the Admin console with the xref:install-upgrade:quickstart-helm-installs.adoc[{company} Helm chart], access the Admin console via the `pulsar-adminconsole` external load balancer endpoint in your cloud provider:
 

modules/components/pages/pulsar-beam.adoc

@@ -7,7 +7,12 @@ The {pulsar-beam-repo}[{pulsar-beam}] project is an HTTP-based streaming and que
 
 With {pulsar-beam}, you can send messages over HTTP, push messages to a webhook or cloud function, chain webhooks and functions together, or stream messages through server-sent events (SSE).
 
-In this guide, you'll install a minimal {company} {pulsar-short} Helm chart that includes {pulsar-beam}.
+[NOTE]
+====
+include::ROOT:partial$luna-name.adoc[]
+====
+
+In this guide, you'll install a minimal {product} Helm chart that includes {pulsar-beam}.
 
 == Prerequisites
 

modules/components/pages/pulsar-sql.adoc

@@ -9,7 +9,12 @@ Stream processing, real-time analytics, and highly customized dashboards are jus
 {pulsar-short} offers a pre-made plugin for Trino that is included in its distribution.
 Additionally, {pulsar-short} has built-in options to create Trino workers and automatically configure the communications between {pulsar-short}'s ledger and Trino.
 
-In this guide, we will use the {company} {pulsar-short} Helm Chart to install a {pulsar-short} cluster with {pulsar-short} SQL.
+[NOTE]
+====
+include::ROOT:partial$luna-name.adoc[]
+====
+
+In this guide, we will use the {product} Helm Chart to install a {pulsar-short} cluster with {pulsar-short} SQL.
 The Trino coordinator and desired number of workers will be created directly in the cluster.
 
 == Prerequisites

modules/connectors/pages/index.adoc

@@ -2,11 +2,16 @@
 :navtitle: {pulsar-short} I/O connectors reference
 :page-aliases: operations:io-connectors.adoc
 
+[NOTE]
+====
+include::ROOT:partial$luna-name.adoc[]
+====
+
 {product} offers fully-managed versions of https://pulsar.apache.org/docs/en/io-overview/[{pulsar-reg} sink and source connectors].
 
 [TIP]
 ====
-There are three versions of the {company} {product} distribution.
+There are three versions of the {product} distribution.
 The `lunastreaming-all` version includes all connectors.
 ====
 
@@ -135,13 +140,13 @@ They are considered experimental because they aren't fully supported or tested w
 
 You can use the {web-ui} and the `xref:components:admin-console-tutorial.adoc[pulsar-admin]` CLI to create, monitor, and manage sink and source connectors.
 
-Although you use the same base commands to create and update all {product} {pulsar-short} connectors, each connector has different configuration options.
+Although you use the same base commands to create and update all {pulsar-short} connectors, each connector has different configuration options.
 For example commands and configuration details, see the documentation for your preferred <<sink-connectors,sink connectors>> and <<source-connectors,source connectors>>.
 
 === `pulsar-admin` CLI sink operations
 
 Get available sink connectors::
-Get a list of sink connectors that are available in your {product} {pulsar-short} tenant:
+Get a list of sink connectors that are available in your {pulsar-short} tenant:
 +
 [source,shell]
 ----
@@ -226,7 +231,7 @@ Delete a sink connector::
 === `pulsar-admin` CLI source operations
 
 Get available source connectors::
-Get a list of source connectors that are available in your {product} {pulsar-short} tenant:
+Get a list of source connectors that are available in your {pulsar-short} tenant:
 +
 [source,shell]
 ----

modules/install-upgrade/pages/production-cluster-sizing.adoc

@@ -40,7 +40,7 @@ Scale bookies up on disc usage percentage. Scale down manually by making a booki
 [#recommended]
 === Recommended server components
 
-The {company} {product} Helm chart deployment includes optional but highly recommended server components for better {pulsar-short} cluster metrics monitoring and operation visibility.
+The {product} Helm chart deployment includes optional but highly recommended server components for better {pulsar-short} cluster metrics monitoring and operation visibility.
 
 * https://bookkeeper.apache.org/docs/admin/autorecovery[{bookkeeper-short} AutoRecovery] - This is a {pulsar-short} component that recovers {bookkeeper-short} data in the event of a bookie outage. While optional you will want the insurance of AutoRecovery working on your behalf.
 A single instance of AutoRecovery should be adequate - only in the most heavily-used clusters will you need more.