[
https://issues.apache.org/jira/browse/YUNIKORN-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195963#comment-17195963
]
Weiwei Yang edited comment on YUNIKORN-406 at 9/15/20, 8:17 AM:
----------------------------------------------------------------
Hi [~akhilpb]
I think we need to fix the port-forwarding problem anyway. My question is if we
follow the option 2, do we still need to configure
{{assets/config/envconfig.json}}?
If this is not needed, then we should go with option 2. because this gives us
the most general setup. And we can leave the flexibility of enabling LB or
ingress to users' choice.
[~vbm] already provided a good example of how to configure the ingress rule,
unfortunately, we cannot use it as the default because not everyone will use
the nginx ingress. We can provide some tutorial doc so the user can do this
manually. I think we should do the following things
# fix the port-forwarding issue
# remove the load balance service type from the default helm install
# add further documents to explain how to expose UI via LB or ingress in [this
doc|http://yunikorn.apache.org/docs/next/#access-the-web-ui]
pls let me know if this makes sense to you. thanks
was (Author: wwei):
Hi [~akhilpb]
I think we need to fix the port-forwarding problem anyway. My question is if we
follow the option 2, do we still need to configure
{{assets/config/envconfig.json}}?
If this is not needed, then we should go with option 2. because this gives us
the most general setup. And we can leave the flexibility of enabling LB or
ingress to users' choice.
[~vbm] already provided a good example of how to configure the ingress rule,
unfortunately, we cannot use it as the default because not everyone will use
the nginx ingress. We can provide some tutorial doc so the user can do this
manually. I think we should do the following things
# fix the port-forwarding issue
# remove the load balance service type from the default helm install
# add further documents to explain how to expose UI via LB or ingress in [this
doc|http://yunikorn.apache.org/docs/next/#access-the-web-ui]
> Queue/apps is not getting displayed on yunikorn UI
> --------------------------------------------------
>
> Key: YUNIKORN-406
> URL: https://issues.apache.org/jira/browse/YUNIKORN-406
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler, webapp
> Reporter: Vishwas
> Assignee: Akhil PB
> Priority: Major
> Attachments: access_via_ingress.PNG, error_ui_console.PNG,
> error_ui_default_envconfig.PNG, image-2020-09-14-09-52-50-388.png,
> node_info.PNG, queue_info.PNG
>
>
> Hi,
> I am a newbie in to yunikorn. I am using the recently release 0.9.0 helm
> chart.
> I have disabled embedAdmissionController and below is the queue configuration
> in values.yaml
>
> {code:java}
> # Use this configuration to automatically map K8s namespaces to yunikorn
> queues
> configuration: |
> partitions:
> - name: default
> placementrules:
> - name: tag
> value: namespace
> create: true
> queues:
> - name: root
> submitacl: '*'
> queues:
> - name: tpcds
> {code}
>
>
> i am trying to launch a simple sleep pod just to see if the pod gets
> allocated to proper queue.
>
> {code:java}
> apiVersion: v1
> kind: Pod
> metadata:
> labels:
> app: sleep
> applicationId: "appli-sleepp-0001"
> #queue: "root"
> namespace: tpcds
> name: app-sleep-0
> spec:
> schedulerName: yunikorn
> containers:
> - name: sleep-30s
> image: "alpine:latest"
> command: ["sleep", "inf"]
> resources:
> requests:
> cpu: "100m"
> memory: "500M"
> ---
> {code}
>
>
> I see that the job i getting allocated properly to root.tpcds queue.I am able
> to confirm this only using rest api but I am not able to see anything in
> yunikorn-ui.
>
> With rest-api:
> {code:java}
> curl http://10.75.38.79:31165/ws/v1/apps
> [
> {
> "applicationID": "appli-sleepp-0001",
> "usedResource": "[memory:500 vcore:100]",
> "partition": "[mycluster]default",
> "queueName": "root.tpcds",
> "submissionTime": 1599644324773451800,
> "allocations": [
> {
> "allocationKey": "f095ab0f-cc25-40d2-8889-2dba31f51441",
> "allocationTags": null,
> "uuid": "83d6acbe-3242-4321-9207-fd6c6d4f38b5",
> "resource": "[memory:500 vcore:100]",
> "priority": "<nil>",
> "queueName": "root.tpcds",
> "nodeId": "vm-10-75-38-73",
> "applicationId": "appli-sleepp-0001",
> "partition": "default"
> }
> ],
> "applicationState": "Running"
> }
> ]
> {code}
>
> I do not see the same info in yunikorn-ui. I have attached the node-info and
> queue-info from UI.
> I have tried on firefox and chrome and the same issue is seen.
>
> kubernetes version: 1.17
> {code:java}
> [root@vm-10-75-38-79 vbm]# kubectl version
> Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4",
> GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean",
> BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc",
> Platform:"linux/amd64"}
> Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4",
> GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean",
> BuildDate:"2020-03-12T20:55:23Z", GoVersion:"go1.13.8", Compiler:"gc",
> Platform:"linux/amd64"}
> {code}
> {code:java}
> [root@vm-10-75-38-79 vbm]# kubectl get all -n yunikorn
> NAME READY STATUS RESTARTS AGE
> pod/yunikorn-scheduler-59c7657ccb-lktxp 2/2 Running 0
> 4h1mNAME TYPE CLUSTER-IP EXTERNAL-IP
> PORT(S) AGE
> service/yunikorn-service NodePort 10.254.242.166 <none>
> 9080:31165/TCP,9889:30840/TCP 4h1mNAME
> READY UP-TO-DATE AVAILABLE AGE
> deployment.apps/yunikorn-scheduler 1/1 1 1
> 4h1mNAME DESIRED CURRENT READY
> AGE
> replicaset.apps/yunikorn-scheduler-59c7657ccb 1 1 1
> 4h1m
> {code}
>
>
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
