Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added train-ticket. #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added train-ticket. #2

wants to merge 1 commit into from

Conversation

JacksonArthurClark
Copy link
Collaborator

Be sure to put our train-ticket in TargetMicroservices for testing.

],
"Helm Config": {
"release_name": "train-ticket",
"chart_path": "train-ticket",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does Helm find the chart of the train-ticket? (same question for the flight-tickect)
It seems that I do not see the train-ticket repo/chart path in this commit.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried it in the CloudLab and validated that the path cannot be found : )

(aiopslab-py3.11) yinfang@node0:~/AIOpsLab$ python3 -m aiopslab.service.apps.train_ticket
Namespace train-ticket not found. Creating namespace.
Namespace train-ticket created successfully: namespace/train-ticket created

Namespace 'train-ticket' already exists.
== Helm Install ==
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /users/yinfang/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /users/yinfang/.kube/config
Error: INSTALLATION FAILED: path "/users/yinfang/AIOpsLab/TargetMicroservices/train-ticket" not found

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you clone train ticket into TargetMicroservices?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which Train-Ticket shall I put? The train-ticket in https://github.com/xlab-uiuc/agent-ops-benchmarks?
I thought you might have some customized version somewhere.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OKay, got it. Let me try.

@yinfangchen
Copy link
Member

yinfang@node0:~$ kubectl describe pod nacosdb-mysql-0 -n train-ticket
Name:             nacosdb-mysql-0
Namespace:        train-ticket
Priority:         0
Service Account:  nacosdb-mysql
... ...
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  65s   default-scheduler  0/4 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling.

yinfang@node0:~$ kubectl describe pvc data-nacosdb-mysql-0 -n train-ticket
Name:          data-nacosdb-mysql-0
Namespace:     train-ticket
StorageClass:  
Status:        Pending
Capacity:      
Access Modes:  
VolumeMode:    Filesystem
Used By:       nacosdb-mysql-0
Events:
  Type    Reason         Age                  From                         Message
  ----    ------         ----                 ----                         -------
  Normal  FailedBinding  1s (x11 over 2m17s)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

Did you encounter this? It seems that there is no PV for the nacosdb.

@JacksonArthurClark
Copy link
Collaborator Author

@yinfangchen

kubectl apply -f https://openebs.github.io/charts/openebs-operator.yaml
kubectl patch storageclass openebs-hostpath -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

Similar setup with openebs that we use for other services.

@yinfangchen
Copy link
Member

Shall I run these two commands?

kubectl apply -f https://openebs.github.io/charts/openebs-operator.yaml
kubectl patch storageclass openebs-hostpath -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

@JacksonArthurClark
Copy link
Collaborator Author

@yinfangchen Yes, that will set up openebs so the PVCs will work.

@yinfangchen
Copy link
Member

@JacksonArthurClark, great I am able to see the running train-ticket on my side now! Shall we

  1. put the train-ticket (submodule?) in the correct position
  2. embed the two lines of kubectl script into the code if this is a universal problem

@JacksonArthurClark
Copy link
Collaborator Author

@yinfangchen Let's keep it as a submodule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants