wilfred-s commented on a change in pull request #27:
URL:
https://github.com/apache/incubator-yunikorn-site/pull/27#discussion_r499960025
##########
File path: docs/user_guide/resource_quota_mgmt.md
##########
@@ -82,36 +106,33 @@ partitions:
vcore: 10000
```
-in this example, we are going to setup 3 queues under root, and each of them
has
-a specific min/max capacity set up.
-
-### Run workloads
-
-In order to run jobs in specific queues, you will need to set the following
label in all pods' spec:
+### Run a workload
+In order to run applications in specific queues, you will need to set the
following labels in all pod specs.
+All pods with the same `applicationID` label are considered ti be one
application.
+In the below example the application `my-test-app` will run in the queue
`root.sandbox`:
```yaml
labels:
app: my-test-app
- applicationId: " my-test-app-01"
+ applicationId: "my-test-app-01"
queue: root.sandbox
```
-## Option 2) 1:1 mapping from namespaces to queues
+## Namespace to queue mapping
### Goal
-
-User just needs to setup namespaces, YuniKorn automatically maps each
namespace to an internal resource queue (AKA dynamical queue).
-There is no additional steps to create YuniKorn queues, all queues will be
created dynamically,
-resource allocation and quotas will be managed by YuniKorn instead of the
namespace resource quota.
+Automatically map a Kubernetes `namespace` to a queue in YuniKorn.
+The user creates the required namespaces in Kubernetes.
+The YuniKorn k8-shim and core scheduler automatically pass the required
information and map the namespace to a queue, creating the queue if it does not
exist.
Review comment:
fixed all occurrences
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
