[ARVADOS] updated: 2.1.0-1593-g54d36a634

[Git user]

Summary of changes:
 doc/admin/metadata-vocabulary.html.textile.liquid | 2 ++
 doc/admin/upgrading.html.textile.liquid           | 8 +++++++-
 2 files changed, 9 insertions(+), 1 deletion(-)

       via  54d36a634def086f5c3b16e897489ee84cbd27f4 (commit)
      from  617d783980943ac7cda84d94a5a43e06adeb838e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 54d36a634def086f5c3b16e897489ee84cbd27f4
Author: Lucas Di Pentima <lucas.dipentima at curii.com>
Date:   Wed Nov 10 17:48:50 2021 -0300

    17944: Adds upgrade notes.
    
    Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <lucas.dipentima at curii.com>

diff --git a/doc/admin/metadata-vocabulary.html.textile.liquid b/doc/admin/metadata-vocabulary.html.textile.liquid
index e615fa3c8..170699ab6 100644
--- a/doc/admin/metadata-vocabulary.html.textile.liquid
+++ b/doc/admin/metadata-vocabulary.html.textile.liquid
@@ -40,6 +40,8 @@ The following is an example of a vocabulary definition:
 {% include 'metadata_vocabulary_example' %}
 {% endcodeblock %}
 
+For clients to be able to query the vocabulary definition, a special endpoint is exposed on the @controller@ service: @/arvados/v1/vocabulary at . This endpoint doesn't require authentication and returns the vocabulary definition in JSON format.
+
 If the @strict_tags@ flag at the root level is @true@, it will restrict the users from saving property keys other than the ones defined in the vocabulary. This restriction is enforced at the backend level to ensure consistency across different clients.
 
 Inside the @tags@ member, IDs are defined (@IDTAGANIMALS@, @IDTAGCOMMENT@, @IDTAGIMPORTANCES@) and can have any format that the current application requires. Every key will declare at least a @labels@ list with zero or more label objects.
diff --git a/doc/admin/upgrading.html.textile.liquid b/doc/admin/upgrading.html.textile.liquid
index c4299746e..2248503dd 100644
--- a/doc/admin/upgrading.html.textile.liquid
+++ b/doc/admin/upgrading.html.textile.liquid
@@ -35,7 +35,7 @@ TODO: extract this information based on git commit messages and generate changel
 <div class="releasenotes">
 </notextile>
 
-h2(#main). development main (as of 2021-10-27)
+h2(#main). development main (as of 2021-11-10)
 
 "previous: Upgrading from 2.3.0":#v2_3_0
 
@@ -46,6 +46,12 @@ When Arvados runs a container via @arvados-dispatch-cloud@, the @crunch-run@ sup
 * If you already have a robust permanent keepstore infrastructure, you can set @Containers.LocalKeepBlobBuffersPerVCPU@ to 0 to disable this feature and preserve the previous behavior of sending container I/O traffic to your separately provisioned keepstore servers.
 * This feature is enabled only if no volumes use @AccessViaHosts@, and no volumes have underlying @Replication@ less than @Collections.DefaultReplication at . If the feature is configured but cannot be enabled due to an incompatible volume configuration, this will be noted in the @crunch-run.txt@ file in the container log.
 
+h3. Backend support for vocabulary checking
+
+If your installation uses the "vocabulary feature on Workbench2":{{site.baseurl}}/v2.2/admin/workbench2-vocabulary.html, you will need to update the cluster configuration by moving the vocabulary definition file to the node where @controller@ runs, and set the @API.VocabularyPath@ configuration parameter to the local path where the file was placed.
+This will enable the vocabulary checking cluster-wide, including Workbench2. The @Workbench.VocabularyURL@ configuration parameter is deprecated and will be removed in a future release.
+You can read more about how this feature works on the "admin page":{{site.baseurl}}/admin/metadata-vocabulary.html.
+
 h2(#v2_3_0). v2.3.0 (2021-10-27)
 
 "previous: Upgrading to 2.2.0":#v2_2_0

-----------------------------------------------------------------------


hooks/post-receive
--