Skip to content

Commit bc7d8be

Browse files
committed
Update quickstart page
1 parent f42a2bf commit bc7d8be

File tree

2 files changed

+43
-38
lines changed

2 files changed

+43
-38
lines changed

modules/ROOT/pages/getting_started.adoc

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,23 @@ One of the best ways of getting started with a new platform is to try it out. An
44

55
== About this guide
66

7-
Firstly, lets cover whether this *Getting Started* guide is right for you. This is intended as a learning tool to discover more about Stackable, its deployment and architecture.
7+
Firstly, let#s cover whether this *Getting Started* guide is right for you. This is intended as a learning tool to discover more about Stackable, its deployment and architecture.
88

99
* If you want to build a production cluster then this is not for you. This tutorial is to familiarize you with the Stackable architecture and is not a guide for building robust clusters.
1010
* This is intended for use in a private network or lab; it doesn't enable many security features such as authentication or encryption and should not be directly connected to the Internet. Be careful if you're deploying in the cloud as your instances may default to using public IPs.
1111

1212
== Overview
13+
1314
Stackable is based on Kubernetes and uses this as the control plane to manage clusters. In this guide we will build a simple cluster with 3 services; Apache ZooKeeper, Apache Kafka and Apache NiFi.
1415

1516
== Installing Kubernetes and kubectl
17+
1618
Stackable’s control plane is built around Kubernetes. Follow the xref:kubernetes.adoc#local-installation[instructions] on how to set up a local Kubernetes instance if you do not have access to a cluster and install kubectl.
1719

1820
If you already have kubectl installed, and have access to a Kubernetes cluster, you can skip this step.
1921

2022
== Installing Stackable
23+
2124
=== Install stackablectl
2225

2326
Install the Stackable command line utility xref:management:stackablectl:index.adoc[stackablectl] by following the installation steps for your platform on the xref:management:stackablectl:installation.adoc[installation] page.
@@ -68,9 +71,11 @@ zookeeper 23.7.0 default deployed
6871
----
6972

7073
== Deploying Stackable Services
71-
At this point you’ve successfully deployed Kubernetes and the Stackable operators we need and are ready to deploy services to the cluster. To do this we provide service descriptions to Kubernetes for each of the services we wish to deploy.
74+
75+
At this point you've successfully deployed Kubernetes and the Stackable operators we need and are ready to deploy services to the cluster. To do this we provide service descriptions to Kubernetes for each of the services we wish to deploy.
7276

7377
=== Apache ZooKeeper
78+
7479
We will deploy an Apache ZooKeeper instance to our cluster.
7580

7681
[source,bash]
@@ -105,6 +110,7 @@ EOF
105110
----
106111

107112
=== Apache Kafka
113+
108114
We will deploy an Apache Kafka broker that depends on the ZooKeeper service we just deployed. The zookeeperReference property below points to the namespace and name we gave to the ZooKeeper service deployed previously.
109115

110116
[source,bash]
@@ -139,6 +145,7 @@ EOF
139145
----
140146

141147
=== Apache NiFi
148+
142149
We will next deploy an Apache NiFi server.
143150

144151
[source,bash]
@@ -203,9 +210,11 @@ zookeeper-operator-deployment-64fcccc797-pckhf 1/1 Running 0
203210
Since this is the first time that each of these services has been deployed to these nodes, it will take some time to download the software from the Stackable repository and deploy the services. Once all the pods are in the running state your cluster is ready to use.
204211

205212
== Testing your cluster
213+
206214
If all has gone well then you will have successfully deployed a Stackable cluster and used it to start three services that should now be ready for you.
207215

208216
=== Apache ZooKeeper
217+
209218
We can test ZooKeeper by running the ZooKeeper CLI shell. The easiest way to do this is to run the CLI shell on the pod that is running ZooKeeper.
210219

211220
[source,bash]
@@ -221,6 +230,7 @@ The shell should connect automatically to the ZooKeeper server running on the po
221230
----
222231

223232
=== Apache Kafka
233+
224234
To test Kafka we'll create a topic, and verify that it was created.
225235
First create the topic with the following command:
226236

@@ -239,6 +249,7 @@ kubectl exec -i -t simple-kafka-broker-brokers-0 -c kafka -- \
239249
----
240250

241251
=== Apache NiFi
252+
242253
Apache NiFi provides a web interface and the easiest way to test it is to view this in a web browser.
243254
To access the web interface we first need to get the ip address and port Nifi is listening on.
244255
To get the IP address we need to connect to (in this case `172.18.0.2`), run:

modules/ROOT/pages/quickstart.adoc

Lines changed: 30 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
= Quickstart
22

3+
:latest-release: https://github.com/stackabletech/stackable-cockpit/releases/tag/stackablectl-1.0.0-rc1
34
:cockpit-releases: https://github.com/stackabletech/stackable-cockpit/releases
45

56
This is the super-short getting started guide that should enable you to get something up and running in less than three
@@ -9,37 +10,30 @@ minutes (excluding download times).
910

1011
Install `stackablectl`, the Stackable CLI utility.
1112

12-
On Linux (Windows and MacOS instructions below):
13+
=== Installation on Linux
1314

14-
[source,console]
15-
----
16-
$ curl -L -o stackablectl https://github.com/stackabletech/stackable-cockpit/releases/latest/download/stackablectl-x86_64-unknown-linux-gnu
17-
----
18-
19-
and mark it as executable:
15+
Download the `stackablectl-x86_64-unknown-linux-gnu` binary file from the link:{latest-release}[latest release], then
16+
rename the file to `stackablectl`. You can also use the following command:
2017

2118
[source,console]
2219
----
23-
$ chmod +x stackablectl
20+
wget -O stackablectl https://github.com/stackabletech/stackable-cockpit/releases/download/stackablectl-1.0.0-rc1/stackablectl-x86_64-unknown-linux-gnu
21+
# or
22+
curl -L -o stackablectl https://github.com/stackabletech/stackable-cockpit/releases/download/stackablectl-1.0.0-rc1/stackablectl-x86_64-unknown-linux-gnu
2423
----
2524

26-
.Instruction for Windows and MacOS
27-
[%collapsible]
28-
====
29-
Download `stackablectl-x86_64-pc-windows-gnu.exe` (for Windows) or `stackablectl-x86_64-apple-darwin` (Mac OS Intel) or
30-
`stackablectl-aarch64-apple-darwin` (MacOS ARM) from the {cockpit-releases}[latest release] and save it as
31-
`stackablectl`. For Windows, you can simply execute it. For MacOS mark it as executable:
25+
Mark the binary as executable:
3226

3327
[source,console]
3428
----
35-
$ chmod +x stackablectl
29+
chmod +x stackablectl
3630
----
3731

38-
If you want to execute it from anywhere in your system, you need to add it to the system `PATH`.
32+
Then, make sure it is present in your `$PATH`, like `/usr/local/bin`.
33+
34+
=== Installation on macOS and Windows
3935

40-
NOTE: If macOS denies the execution of stackablectl go to `Settings` -> `Security & Privacy` -> `General`. Here you will
41-
see a pop up asking if you want to allow access for `stackablectl`. You must allow access.
42-
====
36+
See the xref:management:stackablectl:installation.adoc[guide] for detailed information about the installation process on macOS and Windows.
4337

4438
== Install the Taxi data demo
4539

@@ -60,29 +54,29 @@ To list the installed installed Stackable services run the following command:
6054

6155
[source,console]
6256
----
63-
./stackablectl services list --all-namespaces
57+
./stackablectl stacklet list
6458
----
6559

6660
It will output something like:
6761

6862
[source]
6963
----
70-
PRODUCT NAME NAMESPACE ENDPOINTS EXTRA INFOS
71-
72-
hive hive default hive 172.18.0.5:30298
73-
metrics 172.18.0.5:31633
74-
75-
opa opa default http http://172.18.0.5:30316
76-
77-
superset superset default external-superset http://172.18.0.4:32295 Admin user: admin, password: adminadmin
78-
79-
trino trino default coordinator-http http://172.18.0.3:30167
80-
coordinator-metrics 172.18.0.3:31818
81-
coordinator-https https://172.18.0.3:30141
82-
83-
minio minio-trino default http http://172.18.0.3:31062 Third party service
84-
console-http http://172.18.0.3:30503 Admin user: admin, password: adminadmin
64+
PRODUCT NAME NAMESPACE ENDPOINTS
65+
66+
hive hive default hive 172.18.0.5:30298
67+
metrics 172.18.0.5:31633
68+
69+
opa opa default http http://172.18.0.5:30316
70+
71+
superset superset default external-superset http://172.18.0.4:32295
72+
73+
trino trino default coordinator-http http://172.18.0.3:30167
74+
coordinator-metrics 172.18.0.3:31818
75+
coordinator-https https://172.18.0.3:3014
76+
77+
minio minio-trino default http http://172.18.0.3:31062
78+
console-http http://172.18.0.3:30503
8579
----
8680

8781
To connect to Superset, open the listed endpoint in your browser and log in with the username `admin` and the password
88-
`adminadmin`.
82+
`adminadmin`. Use the `stackablectl stacklet credentials` command to retrieve credentials for various stacklets.

0 commit comments

Comments
 (0)