Merge pull request #217626 from MicrosoftDocs/release-arc-data

huypub · web-flow · commit f8b43a894795 · 2022-11-11T12:09:12.000-08:00
Publish November 2022 release
diff --git a/articles/azure-arc/data/backup-restore-postgresql.md b/articles/azure-arc/data/backup-restore-postgresql.md
@@ -13,6 +13,6 @@ ms.topic: how-to
 
 # Back up and restore Azure Arc-enabled PostgreSQL servers
 
-Backup and restore of Azure Arc-enabled PostgreSQL server is not supported in the current preview release.
+Automated backups can be enabled by including the `--storage-class-backups` argument when creating an Azure Arc-enabled PostgreSQL server. Restore is not supported in the current preview release.
 
 - Read about [scaling up or down (increasing/decreasing memory/vcores)](scale-up-down-postgresql-server-using-cli.md) your server.
diff --git a/articles/azure-arc/data/create-postgresql-server.md b/articles/azure-arc/data/create-postgresql-server.md
@@ -55,9 +55,9 @@ The main parameters should consider are:
 - **the name of the server** you want to deploy. Indicate either `--name` or `-n` followed by a name whose length must not exceed 11 characters.
 
 - **The storage classes** you want your server to use. It is important you set the storage class right at the time you deploy a server as this setting cannot be changed after you deploy. You may specify the storage classes to use for the data, logs and the backups. By default, if you do not indicate storage classes, the storage classes of the data controller will be used.
-    - To set the storage class for the data, indicate the parameter `--storage-class-data` or `-scd` followed by the name of the storage class.
-    - To set the storage class for the logs, indicate the parameter `--storage-class-logs` or `-scl` followed by the name of the storage class.
-    - The support of setting storage classes for the backups has been temporarily removed as we temporarily removed the backup/restore functionalities as we finalize designs and experiences.
+    - To set the storage class for the backups, indicate the parameter `--storage-class-backups` followed by the name of the storage class. Excluding this parameter disables automated backups
+    - To set the storage class for the data, indicate the parameter `--storage-class-data` followed by the name of the storage class.
+    - To set the storage class for the logs, indicate the parameter `--storage-class-logs` followed by the name of the storage class.
 
    > [!IMPORTANT]
    > If you need to change the storage class after deployment, extract the data, delete your server, create a new server, and import the data. 
diff --git a/articles/azure-arc/data/includes/azure-arc-data-preview-release.md b/articles/azure-arc/data/includes/azure-arc-data-preview-release.md
@@ -7,7 +7,9 @@ ms.date: 08/02/2022
 ---
 
 
-The current preview release published on November 1, 2022.
+At this time, a test or preview build is not available for the next release.
+
+<!---
 
 |Component|Value|
 |-----------|-----------|
@@ -25,12 +27,12 @@ New for this release:
 - Azure Arc data controller
   - Support database as resource in Azure Arc data resource provider 
 
-<!--
 - Arc-enabled SQL managed instance
--->
+
 
 - Arc-enabled PostgreSQL server
   - Add support for automated backups
 
 - `arcdata` Azure CLI extension
   - CLI support for automated backups: Setting the `--storage-class-backups` parameter for the create command will enable automated backups
+-->
diff --git a/articles/azure-arc/data/limitations-postgresql.md b/articles/azure-arc/data/limitations-postgresql.md
@@ -17,9 +17,9 @@ This article describes limitations of Azure Arc-enabled PostgreSQL.
 
 [!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
 
-## Back up and restore 
+## Backup and restore 
 
-Back up and restore have been temporarily removed as we finalize designs and experiences.
+Enable automated backups. Include the `--storage-class-backups` argument when you create an Azure Arc-enabled PostgreSQL server. Restore has been temporarily removed as we finalize designs and experiences.
 
 ## High availability
 
diff --git a/articles/azure-arc/data/release-notes.md b/articles/azure-arc/data/release-notes.md
@@ -1,6 +1,6 @@
 ---
 title: Azure Arc-enabled data services - Release notes
-description: Latest release notes
+description: This article provides highlights for the latest release, and a history of features introduced in previous releases.
 author: twright-msft
 ms.author: twright
 ms.reviewer: mikeray
@@ -12,10 +12,30 @@ ms.topic: conceptual
 ms.custom: references_regions, devx-track-azurecli, event-tier1-build-2022
 #Customer intent: As a data professional, I want to understand why my solutions would benefit from running with Azure Arc-enabled data services so that I can leverage the capability of the feature.
 ---
+
 # Release notes - Azure Arc-enabled data services
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## November 8, 2022
+
+### Image tag
+
+`v1.13.0_2022-11-08`
+
+For complete release version information, see [Version log](version-log.md#november-8-2022).
+
+New for this release:
+
+- Azure Arc data controller
+  - Support database as resource in Azure Arc data resource provider 
+
+- Arc-enabled PostgreSQL server
+  - Add support for automated backups
+
+- `arcdata` Azure CLI extension
+  - CLI support for automated backups: Setting the `--storage-class-backups` parameter for the create command will enable automated backups
+
 ## October 11, 2022
 
 ### Image tag
diff --git a/articles/azure-arc/data/using-extensions-in-postgresql-server.md b/articles/azure-arc/data/using-extensions-in-postgresql-server.md
@@ -14,210 +14,79 @@ ms.topic: how-to
 
 # Use PostgreSQL extensions in your Azure Arc-enabled PostgreSQL server
 
-PostgreSQL is at its best when you use it with extensions. In fact, a key element of our own Hyperscale functionality is the Microsoft-provided `citus` extension that is installed by default, which allows Postgres to transparently shard data across multiple nodes.
+PostgreSQL is at its best when you use it with extensions.
 
 [!INCLUDE [azure-arc-data-preview](../../../includes/azure-arc-data-preview.md)]
 
 ## Supported extensions
-The standard [`contrib`](https://www.postgresql.org/docs/12/contrib.html) extensions and the following extensions are already deployed in the containers of your Azure Arc-enabled PostgreSQL server:
-- [`citus`](https://github.com/citusdata/citus), v: 10.2. The Citus extension by [Citus Data](https://www.citusdata.com/) is loaded by default as it brings the Hyperscale capability to the PostgreSQL engine. Dropping the Citus extension from your Azure Arc PostgreSQL server is not supported.
-- [`pg_cron`](https://github.com/citusdata/pg_cron), v: 1.3
-- [`pgaudit`](https://www.pgaudit.org/), v: 1.4
-- plpgsql, v: 1.0
-- [`postgis`](https://postgis.net), v: 3.0.2
-- [`plv8`](https://plv8.github.io/), v: 2.3.14
-- [`pg_partman`](https://github.com/pgpartman/pg_partman), v: 4.4.1/
-- [`tdigest`](https://github.com/tvondra/tdigest), v: 1.0.1
+For this preview, the following standard [`contrib`](https://www.postgresql.org/docs/14/contrib.html) extensions are already deployed in the containers of your Azure Arc-enabled PostgreSQL server:
+- adminpack
+- amcheck
+- autoinc
+- bloombtree_gin
+- btree_gist
+- citext
+- cube
+- dblink
+- dict_int
+- dict_xsyn
+- earthdistance
+- file_fdw
+- fuzzystrmatch
+- hstore
+- insert_username
+- intagg
+- intarray
+- isn
+- lo
+- ltree
+- moddatetime
+- old_snapshot
+- pageinspect
+- pg_buffercache
+- pg_freespacemap
+- pg_prewarm
+- pg_stat_statements
+- pg_surgery
+- pg_trgm
+- pg_visibility
+- pgcrypto
+- pgrowlocks
+- pgstattuple
+- postgres_fdw
+- refint
+- seg
+- sslinfo
+- tablefunc
+- tcn
+- tsm_system_rows
+- tsm_system_time
+- unaccent
+- xml2
 
 Updates to this list will be posted as it evolves over time.
 
 > [!IMPORTANT]
-> While you may bring to your server group an extension other than those listed above, in this Preview, it will not be persisted to your system. It means that it will not be available after a restart of the system and you would need to bring it again.
-
-This guide will take in a scenario to use two of these extensions:
-- [`PostGIS`](https://postgis.net/)
-- [`pg_cron`](https://github.com/citusdata/pg_cron)
-
-## Which extensions need to be added to the shared_preload_libraries and created?
-
-|Extensions   |Requires to be added to shared_preload_libraries  |Requires to be created |
-|-------------|--------------------------------------------------|---------------------- |
-|`pg_cron`      |No       |Yes        |
-|`pg_audit`     |Yes       |Yes        |
-|`plpgsql`      |Yes       |Yes        |
-|`postgis`      |No       |Yes        |
-|`plv8`      |No       |Yes        |
-
-## Add extensions to the `shared_preload_libraries`
-For details about that are `shared_preload_libraries`, read the PostgreSQL documentation [here](https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-SHARED-PRELOAD-LIBRARIES):
-- This step isn't needed for the extensions that are part of `contrib`
-- this step isn't required for extensions that are not required to pre-load by shared_preload_libraries. For these extensions you may jump the next paragraph [Create extensions](#create-extensions).
-
-### Add an extension to an instance that already exists
-```azurecli
-az postgres server-arc server edit -n <postgresql server> --extensions <extension names> --k8s-namespace <namespace> --use-k8s
-```
-
-## Show the list of extensions added to shared_preload_libraries
-Run either of the following command.
-
-### With CLI command
-```azurecli
-az postgres server-arc show -n <server name> --k8s-namespace <namespace> --use-k8s
-```
-Scroll in the output and notice the engine\extensions sections in the specifications of your server group. For example:
-```console
-  "spec": {
-    "dev": false,
-    "engine": {
-      "extensions": [
-        {
-          "name": "citus"
-        }
-      ],
-```
-### With kubectl
-```console
-kubectl describe postgresqls/<server name> -n <namespace>
-```
-Scroll in the output and notice the engine\extensions sections in the specifications of your server group. For example:
-```console
-Spec:
-  Dev:  false
-  Engine:
-    Extensions:
-      Name:   citus
-```
+> While you may bring to your server an extension other than those listed above, in this Preview, it will not be persisted to your system. It means that it will not be available after a restart of the system and you would need to bring it again.
 
 
 ## Create extensions
-Connect to your server group with the client tool of your choice and run the standard PostgreSQL query:
+Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
 ```console
 CREATE EXTENSION <extension name>;
 ```
 
 ## Show the list of extensions created
-Connect to your server group with the client tool of your choice and run the standard PostgreSQL query:
+Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
 ```console
 select * from pg_extension;
 ```
 
 ## Drop an extension
-Connect to your server group with the client tool of your choice and run the standard PostgreSQL query:
+Connect to your server with the client tool of your choice and run the standard PostgreSQL query:
 ```console
 drop extension <extension name>;
 ```
 
-## The `PostGIS` extension
-You do not need to add the `PostGIS` extension to the `shared_preload_libraries`.
-Get [sample data](http://duspviz.mit.edu/tutorials/intro-postgis/) from the MIT’s Department of Urban Studies & Planning. Run `apt-get install unzip` to install unzip as needed.
-
-```console
-wget http://duspviz.mit.edu/_assets/data/intro-postgis-datasets.zip
-unzip intro-postgis-datasets.zip
-```
-
-Let's connect to our database, and create the `PostGIS` extension:
-
-```console
-CREATE EXTENSION postgis;
-```
-
-> [!NOTE]
-> If you would like to use one of the extensions in the `postgis` package (for example `postgis_raster`, `postgis_topology`, `postgis_sfcgal`, `fuzzystrmatch`...) you need to first create the postgis extension and then create the other extension. For instance: `CREATE EXTENSION postgis`; `CREATE EXTENSION postgis_raster`;
-
-And create the schema:
-
-```sql
-CREATE TABLE coffee_shops (
-  id serial NOT NULL,
-  name character varying(50),
-  address character varying(50),
-  city character varying(50),
-  state character varying(50),
-  zip character varying(10),
-  lat numeric,
-  lon numeric,
-  geom geometry(POINT,4326)
-);
-CREATE INDEX coffee_shops_gist ON coffee_shops USING gist (geom);
-```
-
-Now, we can combine `PostGIS` with the scale-out functionality, by making the coffee_shops table distributed:
-
-```sql
-SELECT create_distributed_table('coffee_shops', 'id');
-```
-
-Let's load some data:
-
-```console
-\copy coffee_shops(id,name,address,city,state,zip,lat,lon) from cambridge_coffee_shops.csv CSV HEADER;
-```
-
-And fill the `geom` field with the correctly encoded latitude and longitude in the `PostGIS` `geometry` data type:
-
-```sql
-UPDATE coffee_shops SET geom = ST_SetSRID(ST_MakePoint(lon,lat),4326);
-```
-
-Now we can list the coffee shops closest to MIT (77 Massachusetts Ave at 42.359055, -71.093500):
-
-```sql
-SELECT name, address FROM coffee_shops ORDER BY geom <-> ST_SetSRID(ST_MakePoint(-71.093500,42.359055),4326);
-```
-
-
-## The `pg_cron` extension
-
-Now, let's enable `pg_cron` on our PostgreSQL server group by adding it to the shared_preload_libraries:
-
-```azurecli
-az postgres server-arc update -n pg2 -ns arc --extensions pg_cron
-```
-
-Your server group will restart complete the installation of the  extensions. It may take 2 to 3 minutes.
-
-We can now connect again, and create the `pg_cron` extension:
-
-```sql
-CREATE EXTENSION pg_cron;
-```
-
-For test purposes, lets make a table `the_best_coffee_shop` that takes a random name from our earlier `coffee_shops` table, and inserts the table contents:
-
-```sql
-CREATE TABLE the_best_coffee_shop(name text);
-```
-
-We can use `cron.schedule` plus a few SQL statements, to get a random table name (notice the use of a temporary table to store a distributed query result), and store it in `the_best_coffee_shop`:
-
-```sql
-SELECT cron.schedule('* * * * *', $$
-  TRUNCATE the_best_coffee_shop;
-  CREATE TEMPORARY TABLE tmp AS SELECT name FROM coffee_shops ORDER BY random() LIMIT 1;
-  INSERT INTO the_best_coffee_shop SELECT * FROM tmp;
-  DROP TABLE tmp;
-$$);
-```
-
-And now, once a minute, we'll get a different name:
-
-```sql
-SELECT * FROM the_best_coffee_shop;
-```
-
-```console
-      name
------------------
- B & B Snack Bar
-(1 row)
-```
-
-See the [pg_cron README](https://github.com/citusdata/pg_cron) for full details on the syntax.
-
-
 ## Next steps
-- Read documentation on [`plv8`](https://plv8.github.io/)
-- Read documentation on [`PostGIS`](https://postgis.net/)
-- Read documentation on [`pg_cron`](https://github.com/citusdata/pg_cron)
+- **Try it out.** Get started quickly with [Azure Arc Jumpstart](https://github.com/microsoft/azure_arc#azure-arc-enabled-data-services) on Azure Kubernetes Service (AKS), AWS Elastic Kubernetes Service (EKS), Google Cloud Kubernetes Engine (GKE) or in an Azure VM. 
diff --git a/articles/azure-arc/data/version-log.md b/articles/azure-arc/data/version-log.md
@@ -17,6 +17,18 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+## November 8, 2022
+
+
+|Component|Value|
+|-----------|-----------|
+|Container images tag |`v1.13.0_2022-11-08`|
+|CRD names and version|`datacontrollers.arcdata.microsoft.com`: v1beta1, v1 through v6<br/>`exporttasks.tasks.arcdata.microsoft.com`: v1beta1, v1, v2<br/>`kafkas.arcdata.microsoft.com`: v1beta1, v1beta2<br/>`monitors.arcdata.microsoft.com`: v1beta1, v1, v2<br/>`sqlmanagedinstances.sql.arcdata.microsoft.com`: v1beta1, v1 through v7<br/>`postgresqls.arcdata.microsoft.com`: v1beta1, v1beta2, v1beta3<br/>`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`: v1beta1, v1<br/>`failovergroups.sql.arcdata.microsoft.com`: v1beta1, v1beta2, v1 through v2<br/>`activedirectoryconnectors.arcdata.microsoft.com`: v1beta1, v1beta2, v1<br/>`sqlmanagedinstancereprovisionreplicatask.tasks.sql.arcdata.microsoft.com`: v1beta1<br/>`telemetrycollectors.arcdata.microsoft.com`: v1beta1, v1beta2, v1beta3 *use to be otelcollectors*<br/>`telemetryrouters.arcdata.microsoft.com`: v1beta1, v1beta2<br/>|
+|Azure Resource Manager (ARM) API version|2022-06-15-preview|
+|`arcdata` Azure CLI extension version|1.4.8 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.13.0|
+|Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.7.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.7.0 ([Download](https://aka.ms/ads-azcli-ext))|
+
 ## October 11, 2022
 
 |Component|Value|
