API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 5th, 2017
248
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.08 KB | None | 0 0
raw download clone embed print report
  1. ubuntu@k8s-controller:~$ juju status
  2. Model Controller Cloud/Region Version SLA
  3. default d3m-k8s manual 2.2.2 unsupported
  4.  
  5. App Version Status Scale Charm Store Rev OS Notes
  6. easyrsa 3.0.1 active 0/1 easyrsa jujucharms 15 ubuntu
  7. etcd 2.3.8 active 2/3 etcd jujucharms 48 ubuntu
  8. flannel 0.7.0 active 3/18 flannel jujucharms 26 ubuntu
  9. grafana active 0/1 grafana jujucharms 0 ubuntu
  10. haproxy unknown 0/1 haproxy jujucharms 41 ubuntu exposed
  11. kubeapi-load-balancer 1.10.3 active 0/1 kubeapi-load-balancer jujucharms 25 ubuntu exposed
  12. kubernetes-master 1.7.4 active 0/3 kubernetes-master jujucharms 47 ubuntu
  13. kubernetes-worker 1.7.4 error 10/15 kubernetes-worker jujucharms 52 ubuntu
  14. prometheus active 1 prometheus jujucharms 1 ubuntu exposed
  15. telegraf active 0/5 telegraf jujucharms 6 ubuntu
  16.  
  17. Unit Workload Agent Machine Public address Ports Message
  18. easyrsa/0 active failed 0 192.168.4.6 Certificate Authority connected.
  19. telegraf/3 active failed 192.168.4.6 9103/tcp Monitoring easyrsa/0
  20. etcd/0 active executing 0 192.168.4.6 2379/tcp (update-status) Healthy with 3 known peers
  21. etcd/1 active failed 4 192.168.4.24 2379/tcp Healthy with 3 known peers
  22. etcd/2 active idle 3 192.168.4.9 2379/tcp Healthy with 3 known peers
  23. grafana/0 active failed 21 192.168.4.27 3000/tcp Started grafana-server
  24. haproxy/0 unknown failed 21 192.168.4.27
  25. kubeapi-load-balancer/0 active failed 3 192.168.4.9 443/tcp Loadbalancer ready.
  26. telegraf/4 active failed 192.168.4.9 9103/tcp Monitoring kubeapi-load-balancer/0
  27. kubernetes-master/0 active failed 4 192.168.4.24 6443/tcp Kubernetes master running.
  28. flannel/2 active executing 192.168.4.24 (update-status) Flannel subnet 10.1.102.1/24
  29. telegraf/0 active failed 192.168.4.24 9103/tcp Monitoring kubernetes-master/0
  30. kubernetes-master/1 active failed 9 192.168.4.20 6443/tcp Kubernetes master running.
  31. flannel/0 active failed 192.168.4.20 Flannel subnet 10.1.7.1/24
  32. telegraf/2 active failed 192.168.4.20 9103/tcp Monitoring kubernetes-master/1
  33. kubernetes-master/2 active failed 8 192.168.4.21 6443/tcp Kubernetes master running.
  34. flannel/1 active failed 192.168.4.21 Flannel subnet 10.1.3.1/24
  35. telegraf/1 active failed 192.168.4.21 9103/tcp Monitoring kubernetes-master/2
  36. kubernetes-worker/15 active failed 22 192.168.4.5 80/tcp,443/tcp Kubernetes worker running.
  37. flannel/3 active failed 192.168.4.5 Flannel subnet 10.1.14.1/24
  38. kubernetes-worker/16 error idle 24 192.168.4.7 80/tcp,443/tcp hook failed: "update-status"
  39. flannel/4 active failed 192.168.4.7 Flannel subnet 10.1.26.1/24
  40. kubernetes-worker/17 active executing 23 192.168.4.13 80/tcp,443/tcp (update-status) Kubernetes worker running.
  41. flannel/5 active failed 192.168.4.13 Flannel subnet 10.1.85.1/24
  42. kubernetes-worker/18 active idle 26 192.168.4.8 80/tcp,443/tcp Kubernetes worker running.
  43. flannel/8 active failed 192.168.4.8 Flannel subnet 10.1.91.1/24
  44. kubernetes-worker/19 active idle 25 192.168.4.14 80/tcp,443/tcp Kubernetes worker running.
  45. flannel/6 active failed 192.168.4.14 Flannel subnet 10.1.99.1/24
  46. kubernetes-worker/20 error idle 27 192.168.4.15 80/tcp,443/tcp hook failed: "update-status"
  47. flannel/7 active failed 192.168.4.15 Flannel subnet 10.1.53.1/24
  48. kubernetes-worker/21 active idle 30 192.168.4.11 80/tcp,443/tcp Kubernetes worker running.
  49. flannel/9 active failed 192.168.4.11 Flannel subnet 10.1.11.1/24
  50. kubernetes-worker/22 active failed 29 192.168.4.17 80/tcp,443/tcp Kubernetes worker running.
  51. flannel/10 active idle 192.168.4.17 Flannel subnet 10.1.79.1/24
  52. kubernetes-worker/23 active idle 28 192.168.4.18 80/tcp,443/tcp Kubernetes worker running.
  53. flannel/11 active failed 192.168.4.18 Flannel subnet 10.1.57.1/24
  54. kubernetes-worker/24 active executing 33 192.168.4.22 80/tcp,443/tcp (update-status) Kubernetes worker running.
  55. flannel/13 active idle 192.168.4.22 Flannel subnet 10.1.108.1/24
  56. kubernetes-worker/25 active executing 32 192.168.4.19 80/tcp,443/tcp (update-status) Kubernetes worker running.
  57. flannel/12 active failed 192.168.4.19 Flannel subnet 10.1.6.1/24
  58. kubernetes-worker/26 active failed 31 192.168.4.10 80/tcp,443/tcp Kubernetes worker running.
  59. flannel/14 active failed 192.168.4.10 Flannel subnet 10.1.25.1/24
  60. kubernetes-worker/27 active failed 35 192.168.4.16 80/tcp,443/tcp Kubernetes worker running.
  61. flannel/15 active failed 192.168.4.16 Flannel subnet 10.1.67.1/24
  62. kubernetes-worker/28 active failed 36 192.168.4.12 80/tcp,443/tcp Kubernetes worker running.
  63. flannel/16 active failed 192.168.4.12 Flannel subnet 10.1.62.1/24
  64. kubernetes-worker/29 active idle 34 192.168.4.23 80/tcp,443/tcp Kubernetes worker running.
  65. flannel/17 active failed 192.168.4.23 Flannel subnet 10.1.47.1/24
  66. prometheus/0 active idle 21 192.168.4.27 9090/tcp,12321/tcp Ready
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!