Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 86db202

Browse files
authored
Merge pull request #9545 from rothja/bdcctp24new
Big data cluster udpates for CTP 2.4
2 parents 476713e + bcf3429 commit 86db202

13 files changed

Lines changed: 153 additions & 42 deletions

docs/big-data-cluster/big-data-cluster-create-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ The following types of apps are supported:
3737

3838
## Capabilities
3939

40-
In SQL Server 2019 (preview) CTP 2.3 you can create, delete, describe, initialize, list run and update your application. The following table describes the application deployment commands that you can use with **mssqlctl**.
40+
In SQL Server 2019 (preview) CTP 2.4 you can create, delete, describe, initialize, list run and update your application. The following table describes the application deployment commands that you can use with **mssqlctl**.
4141

4242
|Command |Description |
4343
|:---|:---|

docs/big-data-cluster/cluster-admin-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Follow the [quickstart to deploy your big data cluster](quickstart-big-data-clus
3030
Once the controller pod is running, you can use the cluster administration portal to monitor the deployment. You can access the portal using the external IP address and port number for the `endpoint-service-proxy` (for example: **https://\<ip-address\>:30777/portal**). Credentials for accessing the admin portal are the values of `CONTROLLER_USERNAME` and `CONTROLLER_PASSWORD` environment variables provided above.
3131

3232
> [!NOTE]
33-
> For CTP 2.3, There is a security warning when accessing the web page since it is using auto-generated SSL certificates.
33+
> For CTP 2.4, There is a security warning when accessing the web page since it is using auto-generated SSL certificates.
3434
3535
## Overview
3636

docs/big-data-cluster/concept-controller.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ The controller service provides the following core functionality:
2424
- Expose monitoring tools to observe the state of the cluster
2525
- Expose troubleshooting tools to detect and repair unexpected issues
2626
- Manage cluster security: ensure secure cluster endpoints, manage users and roles, configure credentials for intra-cluster communication
27-
- Manage the workflow of upgrades so that they are implemented safely (not available in CTP 2.3)
28-
- Manage high availability and DR for statefull services in the cluster (not available in CTP 2.3)
27+
- Manage the workflow of upgrades so that they are implemented safely (not available in CTP 2.4)
28+
- Manage high availability and DR for statefull services in the cluster (not available in CTP 2.4)
2929

3030
## Deploying the controller service
3131

docs/big-data-cluster/concept-data-persistence.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ ms.custom: seodec18
2121
The way SQL Server big data cluster consumes these persistent volumes is by using [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/). You can create different storage classes for different kind of storage and specify them at the big data cluster deployment time. You can configure which storage class to use for which purpose (pool). SQL Server big data cluster creates [persistent volume claims](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims) with the specified storage class name for each pod that requires persistent volumes. It then mounts the corresponding persistent volume(s) in the pod.
2222

2323
> [!NOTE]
24-
> For CTP 2.3, only `ReadWriteOnce` access mode for the whole cluster is supported.
24+
> For CTP 2.4, only `ReadWriteOnce` access mode for the whole cluster is supported.
2525
2626
## Deployment settings
2727

docs/big-data-cluster/deploy-install-mssqlctl.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -32,18 +32,21 @@ This article describes how to install the **mssqlctl** tool on Windows or Linux.
3232
1. If you have any previous releases of **mssqlctl** installed, it is important to uninstall **mssqlctl** first before installing the latest version.
3333

3434
If you are unisntalling mssqlctl corresponding to CTP version 2.2 or lower run:
35+
3536
```powershell
3637
pip3 uninstall mssqlctl
3738
```
38-
39-
For CTP2.3 or higher run:
39+
40+
For CTP2.3 or higher run (replace `ctp-2.3` in the command with the version of mssqlctl you are uninstalling):
41+
4042
```powershell
4143
pip3 uninstall -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt
4244
```
45+
4346
1. Install **mssqlctl** with the following command:
4447

4548
```powershell
46-
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt
49+
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.4/mssqlctl/requirements.txt
4750
```
4851

4952
## <a id="linux"></a> Linux mssqlctl installation
@@ -67,19 +70,21 @@ On Linux, you must install Python 3.5 and then upgrade pip. The following exampl
6770
1. If you have any previous releases of **mssqlctl** installed, it is important to uninstall **mssqlctl** first before installing the latest version.
6871

6972
If you are unisntalling mssqlctl corresponding to CTP version 2.2 or lower run:
73+
7074
```bash
7175
pip3 uninstall mssqlctl
7276
```
73-
74-
For CTP2.3 or higher run:
77+
78+
For CTP2.3 or higher run (replace `ctp-2.3` in the command with the version of mssqlctl you are uninstalling):
79+
7580
```bash
7681
pip3 uninstall -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt
7782
```
7883

7984
1. Install **mssqlctl** with the following command:
8085

8186
```bash
82-
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt --user
87+
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.4/mssqlctl/requirements.txt --user
8388
```
8489

8590
> [!NOTE]

docs/big-data-cluster/deployment-guidance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ The cluster configuration can be customized using a set of environment variables
8282
| **ACCEPT_EULA** | Yes | N/A | Accept the SQL Server license agreement (for example, 'Yes'). |
8383
| **CLUSTER_NAME** | Yes | N/A | The name of the Kubernetes namespace to deploy SQLServer big data cluster into. |
8484
| **CLUSTER_PLATFORM** | Yes | N/A | The platform the Kubernetes cluster is deployed. Can be `aks`, `minikube`, `kubernetes`|
85-
| **CLUSTER_COMPUTE_POOL_REPLICAS** | No | 1 | The number of compute pool replicas to build out. In CTP 2.3 only valued allowed is 1. |
85+
| **CLUSTER_COMPUTE_POOL_REPLICAS** | No | 1 | The number of compute pool replicas to build out. In CTP 2.4 only valued allowed is 1. |
8686
| **CLUSTER_DATA_POOL_REPLICAS** | No | 2 | The number of data pool replicas to build out. |
8787
| **CLUSTER_STORAGE_POOL_REPLICAS** | No | 2 | The number of storage pool replicas to build out. |
8888
| **DOCKER_REGISTRY** | Yes | TBD | The private registry where the images used to deploy the cluster are stored. |
@@ -273,13 +273,13 @@ Currently, the only way to upgrade a big data cluster to a new release is to man
273273
**Windows:**
274274

275275
```powershell
276-
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt
276+
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.4/mssqlctl/requirements.txt
277277
```
278278

279279
**Linux:**
280280

281281
```bash
282-
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.3/mssqlctl/requirements.txt --user
282+
pip3 install -r https://private-repo.microsoft.com/python/ctp-2.4/mssqlctl/requirements.txt --user
283283
```
284284

285285
> [!IMPORTANT]

docs/big-data-cluster/hdfs-tiering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.technology: big-data-cluster
1414

1515
# Configure HDFS tiering on SQL Server 2019 big data clusters
1616

17-
HDFS Tiering provides the ability to mount external, HDFS-compatible file system in HDFS. This article explains how to configure HDFS tiering for SQL Server 2019 big data clusters (preview). At this time, CTP 2.3 only supports connecting to Azure Data Lake Storage Gen2, which is the focus of this article.
17+
HDFS Tiering provides the ability to mount external, HDFS-compatible file system in HDFS. This article explains how to configure HDFS tiering for SQL Server 2019 big data clusters (preview). At this time, CTP 2.4 only supports connecting to Azure Data Lake Storage Gen2, which is the focus of this article.
1818

1919
## HDFS tiering overview
2020

docs/big-data-cluster/quickstart-big-data-cluster-deploy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ kubectl get svc endpoint-service-proxy -n <your-cluster-name>
154154
```
155155

156156
> [!NOTE]
157-
> In CTP 2.3, you will see a security warning when accessing the web page, because big data clusters is currently using auto-generated SSL certificates.
157+
> In CTP 2.4, you will see a security warning when accessing the web page, because big data clusters is currently using auto-generated SSL certificates.
158158
159159
## Connect to the cluster
160160

0 commit comments

Comments
 (0)