proj-dept

yarongol · yarongol · commit c8dce94a540d · 2024-08-05T16:09:49.000+03:00
diff --git a/docs/Researcher/cli-reference/runai-submit-dist-TF.md b/docs/Researcher/cli-reference/runai-submit-dist-TF.md
@@ -342,7 +342,7 @@ runai submit-dist tf --name distributed-job --workers=2 -g 1 \
 #### --node-pools `<string>`
 
 > Instructs the scheduler to run this workload using specific set of nodes which are part of a [Node Pool](../../Researcher/scheduling/the-runai-scheduler.md#). You can specify one or more node pools to form a prioritized list of node pools that the scheduler will use to find one node pool that can provide the workload's specification. To use this feature your Administrator will need to label nodes as explained here: [Limit a Workload to a Specific Node Group](../../admin/researcher-setup/limit-to-node-group.md) or use existing node labels, then create a node-pool and assign the label to the node-pool.
-> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md).
+> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/aiinitiatives/org/projects.md).
 
 #### --node-type `<string>`
 
diff --git a/docs/Researcher/cli-reference/runai-submit-dist-mpi.md b/docs/Researcher/cli-reference/runai-submit-dist-mpi.md
@@ -341,7 +341,7 @@ You can start an unattended mpi training Job of name dist1, based on Project *te
 #### --node-pools `<string>`
 
 > Instructs the scheduler to run this workload using specific set of nodes which are part of a [Node Pool](../../Researcher/scheduling/the-runai-scheduler.md#). You can specify one or more node pools to form a prioritized list of node pools that the scheduler will use to find one node pool that can provide the workload's specification. To use this feature your Administrator will need to label nodes as explained here: [Limit a Workload to a Specific Node Group](../../admin/researcher-setup/limit-to-node-group.md) or use existing node labels, then create a node-pool and assign the label to the node-pool.
-> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md).
+> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/).
 
 #### --node-type `<string>`
 
diff --git a/docs/Researcher/cli-reference/runai-submit-dist-pytorch.md b/docs/Researcher/cli-reference/runai-submit-dist-pytorch.md
@@ -349,7 +349,7 @@ runai submit-dist pytorch --name distributed-job --workers=2 -g 1 \
 #### --node-pools `<string>`
 
 > Instructs the scheduler to run this workload using specific set of nodes which are part of a [Node Pool](../../Researcher/scheduling/the-runai-scheduler.md#). You can specify one or more node pools to form a prioritized list of node pools that the scheduler will use to find one node pool that can provide the workload's specification. To use this feature your Administrator will need to label nodes as explained here: [Limit a Workload to a Specific Node Group](../../admin/researcher-setup/limit-to-node-group.md) or use existing node labels, then create a node-pool and assign the label to the node-pool.
-> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md).
+> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/aiinitiatives/org/projects.md).
 
 #### --node-type `<string>`
 
diff --git a/docs/Researcher/cli-reference/runai-submit-dist-xgboost.md b/docs/Researcher/cli-reference/runai-submit-dist-xgboost.md
@@ -333,7 +333,7 @@ runai submit-dist xgboost --name distributed-job --workers=2 -g 1 \
 #### --node-pools `<string>`
 
 > Instructs the scheduler to run this workload using specific set of nodes which are part of a [Node Pool](../../Researcher/scheduling/the-runai-scheduler.md#). You can specify one or more node pools to form a prioritized list of node pools that the scheduler will use to find one node pool that can provide the workload's specification. To use this feature your Administrator will need to label nodes as explained here: [Limit a Workload to a Specific Node Group](../../admin/researcher-setup/limit-to-node-group.md) or use existing node labels, then create a node-pool and assign the label to the node-pool.
-> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md).
+> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/aiinitiatives/org/projects.md).
 
 #### --node-type `<string>`
 
diff --git a/docs/Researcher/cli-reference/runai-submit.md b/docs/Researcher/cli-reference/runai-submit.md
@@ -407,7 +407,7 @@ runai submit --job-name-prefix -i gcr.io/run-ai-demo/quickstart -g 1
 #### --node-pools `<string>`
 
 > Instructs the scheduler to run this workload using specific set of nodes which are part of a [Node Pool](../../Researcher/scheduling/the-runai-scheduler.md#). You can specify one or more node pools to form a prioritized list of node pools that the scheduler will use to find one node pool that can provide the workload's specification. To use this feature your Administrator will need to label nodes as explained here: [Limit a Workload to a Specific Node Group](../../admin/researcher-setup/limit-to-node-group.md) or use existing node labels, then create a node-pool and assign the label to the node-pool.
-> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md).
+> This flag can be used in conjunction with node-type and Project-based affinity. In this case, the flag is used to refine the list of allowable node groups set from a node-pool. For more information see: [Working with Projects](../../admin/aiinitiatives/org/projects.md).
 
 #### --node-type `<string>`
 
diff --git a/docs/Researcher/scheduling/the-runai-scheduler.md b/docs/Researcher/scheduling/the-runai-scheduler.md
@@ -22,13 +22,13 @@ Projects are quota entities that associate a Project name with a **deserved** GP
 
 A Researcher submitting a workload must associate a Project with any workload request. The Run:ai scheduler will then compare the request against the current allocations and the Project's deserved quota and determine whether the workload can be allocated with resources or whether it should remain in a pending state.
 
-For further information on Projects and how to configure them, see: [Working with Projects](../../admin/admin-ui-setup/project-setup.md)
+For further information on Projects and how to configure them, see: [Working with Projects](../../admin/aiinitiatives/org/projects.md)
 
 ### Departments
 
 A *Department* is the second hierarchy of resource allocation above *Project*. A Department quota supersedes a Project quota in the sense that if the sum of Project quotas for Department A exceeds the Department quota -- the scheduler will use the Department quota rather than the Projects' quota.  
 
-For further information on Departments and how to configure them, see: [Working with Departments](../../admin/admin-ui-setup/department-setup.md)
+For further information on Departments and how to configure them, see: [Working with Departments](../../admin/aiinitiatives/org/departments.md)
 
 ### Pods
 
diff --git a/docs/Researcher/user-interface/workspaces/create/workspace-v2.md b/docs/Researcher/user-interface/workspaces/create/workspace-v2.md
@@ -9,7 +9,7 @@ date: 2024-Jan-7
 A Workspace is assigned to a project and is affected by the project’s quota just like any other workload. A workspace is shared with all project members for collaboration.
 
 !!! Note
-      * You must have at least one project configured in the system. To configure a project, see [Creating a project](../../../../admin/admin-ui-setup/project-setup.md#create-a-project).
+      * You must have at least one project configured in the system. To configure a project, see [Creating a project](../../../../admin/aiinitiatives/org/projects.md#adding-a-new-project).
       * You must have at least 1 researcher assigned to the project.
 
 Use the *Jobs form* below if you have not enabled the *Workloads* feature.
diff --git a/docs/admin/admin-ui-setup/overview.md b/docs/admin/admin-ui-setup/overview.md
@@ -5,7 +5,6 @@ Run:ai provides a single user interface that, depending on your role, serves bot
 The control-plane part of the tool allows the administrator to:
 
 * Analyze cluster status using [dashboards](dashboard-analysis.md).
-* Manage Run:ai metadata such as [users](admin-ui-users.md), [departments](department-setup.md), and [projects](project-setup.md).
 * View Job details to be able to help researchers solve Job-related issues.
 
 The researcher workbench part of the tool allows Researchers to submit, delete and pause [Jobs](jobs.md), view Job logs etc.
diff --git a/docs/admin/researcher-setup/limit-to-node-group.md b/docs/admin/researcher-setup/limit-to-node-group.md
@@ -90,6 +90,6 @@ See the [runai submit](../../Researcher/cli-reference/runai-submit.md) documenta
 
 Node Pools are automatically assigned to all Projects and Departments with zero resource allocation as default. Allocating resources to a node pool can be done for each Project and Department. Submitting a workload to a node pool that has zero allocation for a specific project (or department) results in that workload running as an over-quota workload.
 
-To assign and configure specific node affinity groups or node pools to a Project see [working with Projects](../admin-ui-setup/project-setup.md).
+To assign and configure specific node affinity groups or node pools to a Project see [working with Projects](../aiinitiatives/org/projects.md).
 
 When the command-line interface flag is used in conjunction with Project-based affinity, the flag is used to refine the list of allowable node groups set in the Project.
diff --git a/docs/admin/researcher-setup/researcher-setup-intro.md b/docs/admin/researcher-setup/researcher-setup-intro.md
@@ -14,7 +14,7 @@ Run:ai CLI needs to be installed on the Researcher's machine. This [document](cl
 
 ## Provide the Researcher with a GPU Quota
 
-To submit workloads with Run:ai, the Researcher must be provided with a _Project_ that contains a GPU quota. Please see [Working with Projects](../admin-ui-setup/project-setup.md) document on how to create Projects and set a quota.
+To submit workloads with Run:ai, the Researcher must be provided with a _Project_ that contains a GPU quota. Please see [Working with Projects](../aiinitiatives/org/projects.md) document on how to create Projects and set a quota.
 
 ## Provide access to the Run:ai User Interface
 
diff --git a/docs/admin/runai-setup/cluster-setup/cluster-install.md b/docs/admin/runai-setup/cluster-setup/cluster-install.md
@@ -88,6 +88,6 @@ To perform these tasks. See [Set Node Roles](../config/node-roles.md).
 ## Next Steps
 
 * Set up Run:ai Users [Working with Users](../../admin-ui-setup/admin-ui-users.md).
-* Set up Projects for Researchers [Working with Projects](../../admin-ui-setup/project-setup.md).
+* Set up Projects for Researchers [Working with Projects](../../aiinitiatives/org/projects.md).
 * Set up Researchers to work with the Run:ai Command-line interface (CLI). See  [Installing the Run:ai Command-line Interface](../../researcher-setup/cli-install.md) on how to install the CLI for users.
 * Review [advanced setup and maintenance](../config/overview.md) scenarios.
diff --git a/docs/admin/runai-setup/cluster-setup/customize-cluster-install.md b/docs/admin/runai-setup/cluster-setup/customize-cluster-install.md
@@ -62,6 +62,6 @@ There are a couple of use cases that customers will want to disable this feature
 Follow these steps to achieve this:
 
 1. Disable the namespace creation functionality. See the  `runai-operator.config.project-controller.createNamespaces` flag above.
-2. [Create a Project](../../admin-ui-setup/project-setup.md#create-a-project) using the Run:ai User Interface.
+2. [Create a Project](../../aiinitiatives/org/projects.md#adding-a-new-project) using the Run:ai User Interface.
 3. Create the namespace if needed by running: `kubectl create ns <NAMESPACE>`. The suggested Run:ai default is `runai-<PROJECT-NAME>`.
 4. Label the namespace to connect it to the Run:ai Project by running `kubectl label ns <NAMESPACE>  runai/queue=<PROJECT_NAME>`, where `<PROJECT_NAME>` is the name of the project you have created in the Run:ai user interface above and `<NAMESPACE>` is the name you chose for your namespace.
diff --git a/docs/admin/runai-setup/cluster-setup/dgx-bundle.md b/docs/admin/runai-setup/cluster-setup/dgx-bundle.md
@@ -67,7 +67,7 @@ Post installation, you will want to:
 
 * (Mandatory) Set up [Researcher Access Control](../authentication/researcher-authentication.md). Without this, the Job Submit form will not work.
 * Set up Run:ai Users [Working with Users](../../admin-ui-setup/admin-ui-users.md).
-* Set up Projects for Researchers [Working with Projects](../../admin-ui-setup/project-setup.md).
+* Set up Projects for Researchers [Working with Projects](../../aiinitiatives/org/projects.md).
 
 ## Troubleshooting
 
diff --git a/docs/admin/runai-setup/config/node-affinity-with-cloud-node-pools.md b/docs/admin/runai-setup/config/node-affinity-with-cloud-node-pools.md
@@ -1,6 +1,6 @@
 # Node affinity with cloud node pools
 
-Run:ai allows for [node affinity](../../admin-ui-setup/project-setup.md#other-project-properties). Node affinity is the ability to assign a Project to run on specific nodes.
+Run:ai allows for [node affinity](../../aiinitiatives/org/projects.md). Node affinity is the ability to assign a Project to run on specific nodes.
 To use the node affinity feature, You will need to label the target nodes with the label  `run.ai/node-type`. Most cloud clusters allow configuring node labels for the node pools in the cluster. This guide shows how to apply this configuration to different cloud providers.
 
 To make the node affinity work with node pools on various cloud providers, we need to make sure the node pools are configured with the appropriate Kubernetes label (`run.ai/type=<TYPE_VALUE>`).
diff --git a/docs/admin/runai-setup/self-hosted/k8s/project-management.md b/docs/admin/runai-setup/self-hosted/k8s/project-management.md
@@ -3,7 +3,7 @@ title: Self Hosted installation over Kubernetes - Create Projects
 ---
 ## Introduction
 
-The Administrator creates Run:ai Projects via the [Run:ai user interface](../../../admin-ui-setup/project-setup.md#create-a-project). When enabling [Researcher Authentication](../../authentication/researcher-authentication.md) you also assign users to Projects.
+The Administrator creates Run:ai Projects via the [Run:ai user interface](../../../aiinitiatives/org/projects.md#adding-a-new-project). When enabling [Researcher Authentication](../../authentication/researcher-authentication.md) you also assign users to Projects.
 
 Run:ai Projects are implemented as Kubernetes namespaces. When creating a new Run:ai Project, Run:ai does the following automatically:
 
diff --git a/docs/admin/runai-setup/self-hosted/ocp/project-management.md b/docs/admin/runai-setup/self-hosted/ocp/project-management.md
@@ -3,7 +3,7 @@ title: Self Hosted installation over OpenShift - Create Projects
 ---
 ## Introduction
 
-The Administrator creates Run:ai Projects via the [Run:ai User Interface](../../../admin-ui-setup/project-setup.md#create-a-project). When enabling [Researcher Authentication](../../authentication/researcher-authentication.md) you also assign users to Projects.
+The Administrator creates Run:ai Projects via the [Run:ai User Interface](../../../aiinitiatives/org/projects.md#adding-a-new-project). When enabling [Researcher Authentication](../../authentication/researcher-authentication.md) you also assign users to Projects.
 
 Run:ai Projects are implemented as Kubernetes namespaces. When creating a new Run:ai Project, Run:ai does the following automatically:
 
diff --git a/docs/home/whats-new-2-13.md b/docs/home/whats-new-2-13.md
@@ -60,7 +60,7 @@ This version contains features and fixes from previous versions starting with 2.
 
 **Projects**
 <!-- RUN-9312/9313 Projects V2 -->
-* Improved the **Projects** UI for ease of use. **Projects** follows UI upgrades and changes that are designed to make setting up of components and assets easier for administrators and researchers. To configure a project, see [Projects](../admin/admin-ui-setup/project-setup.md).
+* Improved the **Projects** UI for ease of use. **Projects** follows UI upgrades and changes that are designed to make setting up of components and assets easier for administrators and researchers. To configure a project, see [Projects](../admin/aiinitiatives/org/projects.md).
 
 **Dashboards**
 
diff --git a/docs/home/whats-new-2-16.md b/docs/home/whats-new-2-16.md
@@ -14,7 +14,7 @@ date: 2023-Dec-4
 
 #### Jobs, Workloads, and Workspaces
 
-* <!-- DONE RUN-10859/RUN-10860 Presenting Policy in workloads creation forms (V2) -->Added the capability view and edit policies directly in the project submission form. Pressing on *Policy* will open a window that displays the effective policy. For more information, see [Viewing Project Policies](../admin/admin-ui-setup/project-setup.md#viewing-project-policies).
+* <!-- DONE RUN-10859/RUN-10860 Presenting Policy in workloads creation forms (V2) -->Added the capability view and edit policies directly in the project submission form. Pressing on *Policy* will open a window that displays the effective policy. For more information, see [Viewing Project Policies](../admin/aiinitiatives/org/projects.md#viewing-a-projects-policy).
 <!-- The URLs addresses only viewing policies and not editing policies, I guess it is still work in porogress (let's also be consistent with the terms here and use "edit" like we use in the product and not "change") -->
 
 * <!-- DONE RUN-12619/RUN-14041 Workloads - Reliable data in API and UI Workloads redesign-->Running machine learning workloads effectively on Kubernetes can be difficult, but Run:ai makes it easy. The new *Workloads* experience introduces a simpler and more efficient way to manage machine learning workloads, which will appeal to data scientists and engineers alike. The *Workloads* experience provides a fast, reliable, and easy to use unified interface.
@@ -60,7 +60,7 @@ date: 2023-Dec-4
 
 * <!--  DONE RUN-11125/RUN-11746	TW - Policy Sync - Catch all for the new policies pages and features. -->Added new *Policy Manager. The new *Policy Manager* provides administrators the ability to impose restrictions and default vaules on system resources. The new *Policy Manager* provides a YAML editor for configuration of the policies. Administrators can easily add both *Workspace* or *Training* policies. The editor makes it easy to see the configuration that has been applied and provides a quick and easy method to edit the policies. The new *Policy Editor* brings other important policy features such as the ability to see non-compliant resources in workloads. For more information, see [Policies](../admin/workloads/policies/README.md#policies).
 
-* <!-- DONE RUN-9808/RUN-9810 - Show effective project policy from the UI -->Added a new policy manager. Enabling the *New Policy Manager* provides new tools to discover how resources are not compliant. Non-compliant resources and will appear greyed out and cannot be selected. To see how a resource is not compliant, press on the clipboard icon in the upper right hand corner of the resource. Policies can also be applied to specific scopes within the Run:ai platform. For more information, see [Viewing Project Policies](../admin/admin-ui-setup/project-setup.md#viewing-project-policies).
+* <!-- DONE RUN-9808/RUN-9810 - Show effective project policy from the UI -->Added a new policy manager. Enabling the *New Policy Manager* provides new tools to discover how resources are not compliant. Non-compliant resources and will appear greyed out and cannot be selected. To see how a resource is not compliant, press on the clipboard icon in the upper right hand corner of the resource. Policies can also be applied to specific scopes within the Run:ai platform. For more information, see [Viewing Project Policies](../admin/aiinitiatives/org/projects.md#adding-a-new-project).
 
 ### Control and Visibility
 
diff --git a/docs/home/whats-new-2-17.md b/docs/home/whats-new-2-17.md
diff --git a/docs/snippets/common-submit-cli-commands.md b/docs/snippets/common-submit-cli-commands.md
