Difference between revisions of "Trigger"
From Fixme.ch
| Line 1: | Line 1: | ||
[[Category:Services]] | [[Category:Services]] | ||
== Information == | == Information == | ||
| + | |||
git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api | git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api | ||
| + | |||
* Trigger for the space status, also controls the [[LED_Retrofit]] | * Trigger for the space status, also controls the [[LED_Retrofit]] | ||
| − | |||
* It uses the [https://github.com/fixme-lausanne/Twitter-Hackerspace-Status twitter.pl and spaceapi.py scripts] to retrieve the status and to change it, using javascript and XMLHttpRequest | * It uses the [https://github.com/fixme-lausanne/Twitter-Hackerspace-Status twitter.pl and spaceapi.py scripts] to retrieve the status and to change it, using javascript and XMLHttpRequest | ||
* It controls the LEDs over HTTP using | * It controls the LEDs over HTTP using | ||
| − | * It is deployed using a [[Gitolite#Deploy|gitolite hook]] | + | * It's deployed in [[Kubernetes]], the image is built locally. |
| + | |||
| + | <pre> | ||
| + | ubuntu@k8s:~$ kubectl get all --namespace ctrl | ||
| + | NAME READY STATUS RESTARTS AGE | ||
| + | pod/ledctrl-848f854c49-d6ljh 1/1 Running 0 12d | ||
| + | pod/trigger-579d7dd765-krfvk 1/1 Running 0 11d | ||
| + | |||
| + | NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE | ||
| + | service/ledctrl ClusterIP 10.109.61.229 <none> 5000/TCP 11d | ||
| + | service/trigger ClusterIP 10.106.107.197 <none> 80/TCP 11d | ||
| + | |||
| + | NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE | ||
| + | deployment.apps/ledctrl 1 1 1 1 12d | ||
| + | deployment.apps/trigger 1 1 1 1 12d | ||
| + | |||
| + | NAME DESIRED CURRENT READY AGE | ||
| + | replicaset.apps/ledctrl-5ccdccc764 0 0 0 12d | ||
| + | replicaset.apps/ledctrl-848f854c49 1 1 1 12d | ||
| + | replicaset.apps/trigger-579d7dd765 1 1 1 12d | ||
| + | replicaset.apps/trigger-7966796948 0 0 0 12d | ||
| + | </pre> | ||
| + | |||
| + | == How to push changes == | ||
| + | |||
| + | <pre> | ||
| + | $ ssh ubuntu@k8s.fixme.ch | ||
| + | |||
| + | # Update the local repository | ||
| + | cd led-ctrl-2018/ | ||
| + | git pull | ||
| + | |||
| + | # Build the docker image | ||
| + | sudo docker build -t trigger . | ||
| + | |||
| + | # Killthe pod and watch it come back | ||
| + | kubectl delete --namespace ctrl pod/trigger-579d7dd765-krfvk | ||
| + | kubectl get --namespace=ctrl pods | ||
| + | </pre> | ||
| + | |||
| + | == Archives == | ||
| + | * It was deployed using a [[Gitolite#Deploy|gitolite hook]] | ||
| + | * This was part of the [[Internal_Server]] | ||
Revision as of 20:11, 22 February 2019
Information
git clone ssh://gitolite@git.fixme.ch:1337/fixme-nice-api
- Trigger for the space status, also controls the LED_Retrofit
- It uses the twitter.pl and spaceapi.py scripts to retrieve the status and to change it, using javascript and XMLHttpRequest
- It controls the LEDs over HTTP using
- It's deployed in Kubernetes, the image is built locally.
ubuntu@k8s:~$ kubectl get all --namespace ctrl NAME READY STATUS RESTARTS AGE pod/ledctrl-848f854c49-d6ljh 1/1 Running 0 12d pod/trigger-579d7dd765-krfvk 1/1 Running 0 11d NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ledctrl ClusterIP 10.109.61.229 <none> 5000/TCP 11d service/trigger ClusterIP 10.106.107.197 <none> 80/TCP 11d NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deployment.apps/ledctrl 1 1 1 1 12d deployment.apps/trigger 1 1 1 1 12d NAME DESIRED CURRENT READY AGE replicaset.apps/ledctrl-5ccdccc764 0 0 0 12d replicaset.apps/ledctrl-848f854c49 1 1 1 12d replicaset.apps/trigger-579d7dd765 1 1 1 12d replicaset.apps/trigger-7966796948 0 0 0 12d
How to push changes
$ ssh ubuntu@k8s.fixme.ch # Update the local repository cd led-ctrl-2018/ git pull # Build the docker image sudo docker build -t trigger . # Killthe pod and watch it come back kubectl delete --namespace ctrl pod/trigger-579d7dd765-krfvk kubectl get --namespace=ctrl pods
Archives
- It was deployed using a gitolite hook
- This was part of the Internal_Server
