Skip to content

Commit c5a1893

Browse files
authored
luna name change (#34)
1 parent b0bfdad commit c5a1893

4 files changed

Lines changed: 19 additions & 17 deletions

File tree

antora.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ asciidoc:
1616
pulsar-reg: 'Apache Pulsar(TM)'
1717
pulsar: 'Apache Pulsar'
1818
pulsar-short: 'Pulsar'
19-
luna-streaming: 'Luna Streaming'
19+
luna-streaming: 'IBM Elite Support for Apache Pulsar'
2020
astra-stream: 'Astra Streaming'
2121
astra-streaming-examples-repo: 'https://github.com/datastax/astra-streaming-examples'
2222
zookeeper-reg: 'Apache ZooKeeper(TM)'

local-preview-playbook.yml

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -221,9 +221,6 @@ asciidoc:
221221
cr-short: 'CR'
222222
crd: 'custom resource definition (CRD)'
223223
crd-short: 'CRD'
224-
# Custom attributes only used in ragstack-ai
225-
astra_db: 'Astra DB'
226-
astra_ui: 'Astra Portal'
227224
# Antora Atlas
228225
primary-site-url: https://docs.datastax.com/en
229226
primary-site-manifest-url: https://docs.datastax.com/en/site-manifest.json

modules/ROOT/pages/faqs.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ It requires a compatible {pulsar-short} release to operate.
1818

1919
The following {pulsar-short} releases are supported:
2020

21-
* {luna-streaming} 2.8.0 or later
21+
* {luna-streaming} 2.8.0 or later (formerly DataStax Luna Streaming)
2222
* {pulsar} 2.9.0 or later
2323
* {astra-stream}
2424

@@ -33,7 +33,7 @@ Yes, {product} is open source using the Apache 2.0 license. You can find the sou
3333
=== Does {product} support Kubernetes?
3434

3535
Yes.
36-
You can run the {product} on {luna-streaming} or {pulsar-short} running on any Kubernetes platform, including Minikube, K8d, Kind, Google Kubernetes Engine (GKE), Microsoft Azure Kubernetes Service, Amazon Kubernetes Service (AKS), and other commonly used platforms.
36+
You can run the {product} on {luna-streaming} or self-managed {pulsar-short} running on any Kubernetes platform, including Minikube, K8d, Kind, Google Kubernetes Engine (GKE), Microsoft Azure Kubernetes Service, Amazon Kubernetes Service (AKS), and other commonly used platforms.
3737
For more information, see xref:installation:getting-started.adoc[].
3838

3939
=== How do I install {product}?

modules/installation/pages/getting-started.adoc

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -66,18 +66,23 @@ Continue to the next section to learn how to use these connection details in a R
6666
{luna-streaming}::
6767
+
6868
--
69+
[TIP]
70+
====
71+
{luna-streaming} was formerly DataStax Luna Streaming.
72+
====
73+
6974
[tabs]
7075
====
7176
Protocol handler (Helm chart)::
7277
+
73-
The {product} extension is included in the `luna-streaming-all` image used to deploy a Luna cluster.
74-
The Luna Helm chart simplifies deployment of {product} as a protocol handler.
78+
The {product} extension is included in the `luna-streaming-all` image used to deploy an {luna-streaming} cluster.
79+
The {company} {pulsar-short} Helm chart simplifies deployment of {product} as a protocol handler.
7580
+
76-
The following steps explain how to deploy a {luna-streaming} Helm chart to create a simple {pulsar-short} cluster with the {product} extension ready for use.
81+
The following steps explain how to deploy a {company} {pulsar-short} Helm chart to create a simple {pulsar-short} cluster with the {product} extension ready for use.
7782
+
7883
[IMPORTANT]
7984
=====
80-
The {company} Luna Helm chart used in this example is deprecated.
85+
The {company} {pulsar-short} Helm chart used in this example is deprecated.
8186
For Kubernetes deployments, {company} recommends xref:kaap-operator:ROOT:index.adoc[{kaap}].
8287
=====
8388
+
@@ -87,15 +92,15 @@ For Kubernetes deployments, {company} recommends xref:kaap-operator:ROOT:index.a
8792
* Install https://kubernetes.io/docs/tasks/tools/[kubectl CLI] version 1.23.4 or later.
8893
* Have access to a Kubernetes cluster with permission to create a namespace, deployments, and pods.
8994
+
90-
. Add the {company} Helm chart repo to your Helm store:
95+
. Add the {company} {pulsar-short} Helm chart repo to your Helm store:
9196
+
9297
[source,shell]
9398
----
9499
helm repo add datastax-pulsar https://datastax.github.io/pulsar-helm-chart
95100
----
96101
+
97102
. Install the Helm chart using a xref:installation:attachment$values.yaml[minimal values file].
98-
The following command creates a Helm release named `my-pulsar-cluster` using the {company} Luna Helm chart within a Kubernetes namespace named `datastax-pulsar`.
103+
The following command creates a Helm release named `my-pulsar-cluster` using the {company} {pulsar-short} Helm chart within a Kubernetes namespace named `datastax-pulsar`.
99104
This minimal configuration creates only the essential components and has no ingress or load balanced services.
100105
+
101106
[source,shell]
@@ -136,7 +141,7 @@ kubectl port-forward -n datastax-pulsar service/pulsar-broker 8080:8080
136141
kubectl port-forward -n datastax-pulsar service/pulsar-proxy 5672:5672
137142
----
138143
+
139-
The Luna Helm chart deployed {product} on the {pulsar-short} proxy and opened the correct port.
144+
The {company} {pulsar-short} Helm chart deployed {product} on the {pulsar-short} proxy and opened the correct port.
140145
The forwarded ports allow you to access {pulsar-short} and {product} services when running RabbitMQ client scripts and using CLI tools locally.
141146
Your applications can now communicate with {pulsar-short} as if it were a real RabbitMQ host, as explained in the next section.
142147

@@ -432,7 +437,7 @@ Additionally, the namespace's metrics should reflect that at least one message w
432437
{luna-streaming}::
433438
+
434439
--
435-
To use a RabbitMQ client with {product}, you use your {luna-streaming} {pulsar-short} tenant as the AMQP listener.
440+
To use a RabbitMQ client with {product}, you use your {luna-streaming} tenant as the AMQP listener.
436441
The following examples use a connection on `localhost:5672` with {product} as a protocol handler.
437442
For other connection methods, see the documentation for your preferred RabbitMQ client library.
438443
@@ -491,12 +496,12 @@ received message: test
491496
deleted test-queue queue
492497
----
493498
+
494-
. Use the {pulsar} admin CLI or the {luna-streaming} {pulsar-short} Admin Console to inspect your tenant's activity.
499+
. Use the {pulsar} admin CLI or the {luna-streaming} Admin Console to inspect your tenant's activity.
495500
Make sure the `test-queue` topic was created and a message was published and consumed.
496501

497502
Java client::
498503
+
499-
The following example uses a Java program to create a connection between RabbitMQ and your {luna-streaming} {pulsar-short} tenant, and then it establishes a message queue and sends a message.
504+
The following example uses a Java program to create a connection between RabbitMQ and your {luna-streaming} tenant, and then it establishes a message queue and sends a message.
500505
+
501506
. Create a new Maven project:
502507
+
@@ -620,7 +625,7 @@ Sent 'Hello World!'
620625
Received 'Hello World!'
621626
----
622627
+
623-
. Use the {pulsar-short} Admin CLI or the {luna-streaming} {pulsar-short} Admin Console to inspect your tenant's activity.
628+
. Use the {pulsar-short} Admin CLI or the {luna-streaming} Admin Console to inspect your tenant's activity.
624629
Make sure the `queuename` topic was created and a message was published and consumed.
625630
====
626631
--

0 commit comments

Comments
 (0)