Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Feb 13 09:52
    chchrist commented #1
  • Apr 13 2018 16:09

    richarddli on master

    add ns (compare)

  • Apr 13 2018 15:26

    richarddli on master

    add ordering (compare)

  • Apr 11 2018 20:09

    richarddli on master

    add monitoring (compare)

  • Mar 21 2018 13:30
    youyongsong commented #24
  • Mar 21 2018 13:03
    plombardi89 commented #24
  • Mar 21 2018 13:02
    plombardi89 commented #24
  • Mar 21 2018 05:55
    youyongsong edited #24
  • Mar 21 2018 05:55
    youyongsong opened #24
Richard Li
@richarddli
okay, and when you edit App.py and hit save nothing happens?
Gaultier Boniface
@wysow
exactly, just another GET line when I refresh the browser
Richard Li
@richarddli
very strange
here is what I see
`$ docker run --rm -i -t -v $(pwd):/service python-api-dev
  • Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
  • Restarting with stat
  • Debugger is active!
  • Debugger PIN: 311-740-042
  • Detected change in '/service/app.py', reloading
  • Restarting with stat
  • Debugger is active!
  • Debugger PIN: 311-740-042`
$ docker run --rm -i -t -v $(pwd):/service python-api-dev
 * Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 311-740-042
 * Detected change in '/service/app.py', reloading
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 311-740-042
See how it says detected change
?
Gaultier Boniface
@wysow
sure
Richard Li
@richarddli
for some reason, the filesystem change thing isn't being detected
i'm not sure what's going on. my only thought is google around? or you can try to create a different test case where you mount your local fs into a container.
Gaultier Boniface
@wysow
I'm going to investigate now that I know where is the problem
Ho! Just retried with telepresence and got this:
→ telepresence --namespace datawire --swap-deployment python-api-stable --docker-run --rm -i -t -v $(pwd)/service python-api-dev
Volumes are rooted at $TELEPRESENCE_ROOT. See https://telepresence.io/howto/volumes.html for details.


Looks like there's a bug in our code. Sorry about that!

Here's the traceback:

Traceback (most recent call last):
  File "/usr/local/Cellar/telepresence/0.75/libexec/lib/python3.6/site-packages/telepresence/cli.py", line 73, in call_f
    return f(*args, **kwargs)
  File "/usr/local/Cellar/telepresence/0.75/libexec/lib/python3.6/site-packages/telepresence/main.py", line 480, in go
    runner, args
  File "/usr/local/Cellar/telepresence/0.75/libexec/lib/python3.6/site-packages/telepresence/main.py", line 297, in start_proxy
    run_id=run_id,
  File "/usr/local/Cellar/telepresence/0.75/libexec/lib/python3.6/site-packages/telepresence/remote.py", line 215, in get_remote_info
    format(deployment_name)
RuntimeError: Telepresence pod not found for Deployment 'python-api-stable'.


And here are the last few lines of the logfile (see ./telepresence.log for the complete logs):

 127.7 TL | Checking {'app': 'java-spring-api-dev-my-first-change', 'pod-template-hash': '276245224'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'java-spring-api-stable', 'pod-template-hash': '183238707'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'nodejs-api-canary', 'pod-template-hash': '4228027386'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'nodejs-api-dev-my-first-change', 'pod-template-hash': '639365808'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'nodejs-api-stable', 'pod-template-hash': '3193690162'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'python-api-canary', 'pod-template-hash': '1090225005'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'python-api-dev-my-first-change', 'pod-template-hash': '2807928737'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'ui-canary', 'pod-template-hash': '1545198763'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'ui-dev-my-first-change', 'pod-template-hash': '1132952065'} (phase Running)...
 127.7 TL | Labels don't match.
 127.7 TL | Checking {'app': 'ui-stable', 'pod-template-hash': '1149097933'} (phase Running)...
 127.7 TL | Labels don't match.

Would you like to file an issue in our issue tracker? We'd really appreciate the help improving our product. [Y/n]:
I think a previous try break something
should restart from scratch right?
Richard Li
@richarddli
yes, it's possible that telepresence did not shut down cleanly and left something in your cluster
i would delete your deployment and redeploy with forge deploy
and i would try to figure out why volume mounts don't work in docker, independent of our software
(also if you're not planning on coding in python, you might end up with a different strategy for live coding)
Gaultier Boniface
@wysow
sure I see your point, just to be sure on my mac I'm on Docker Version 17.12.0-ce-mac55 (23011)
what is your version?
Richard Li
@richarddli
I'm on Docker Edge, although we've tested this pretty extensively on different versions of Docker (Version 18.03.0-ce-rc4-mac57 (23360))
The config you're using is pretty close to our default Telepresence howto, and it's pretty popular
Gaultier Boniface
@wysow
Oh you're using Docker edge, can I ask if it's working well? Is there some cool new features? Is the new VM filesystem more reliable?
Richard Li
@richarddli
@wysow it's because I need to test some of our software with docker mac for kubernetes. it uses considerably more battery than stable.
Nenad Ilic
@nenadilic84
Hi there :smile: I just started looking into the datawire opensource projects. Quite interesting stuff there
I like the ideas behind the ambassador, forge and telepresence
Richard Li
@richarddli
@nenadilic84 awesome :) would love to hear your feedback, or if you have any questions, ask us!
Nenad Ilic
@nenadilic84
currently I'm trying to setup the monitoring described here: https://github.com/datawire/blackbird/blob/master/monitoring/README.md
and facing an issue
error: unable to recognize "prom-cluster.yaml": no matches for monitoring.coreos.com/, Kind=Prometheus
while executing the kubectl apply -f prom-cluster.yaml
Richard Li
@richarddli
did you create the operator yet?
the cause of that issue is the operator hasn't properly deployed
so you want to do kubectl get pods and see if the operator properly deployed
Nenad Ilic
@nenadilic84
yup I did kubectl apply -f prom-operator.yaml but when I do kubectl -n datawire get all I see this:
NAME                         AGE
deploy/ambassador            5h
deploy/prometheus-operator   5m

NAME                                AGE
rs/ambassador-745cbc9cf            5h
rs/prometheus-operator-55567c449   5m

NAME                             READY     STATUS    RESTARTS   AGE
po/ambassador-745cbc9cf-xg5ns   2/2       Running   0          5h

NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
svc/ambassador         NodePort    10.109.163.105   <none>        80:32235/TCP   5h
svc/ambassador-admin   ClusterIP   10.96.84.211     <none>        8877/TCP       5h
so no prometheus-operator pod is coming up
I will continue to investigate why...
Nenad Ilic
@nenadilic84
but just wanted to let you know :smile:
Nenad Ilic
@nenadilic84
here is why the pod is not created: Warning FailedCreate 43s (x21 over 55m) replicaset-controller Error creating: pods "prometheus-operator-855567c449-" is forbidden: error looking up service account datawire/prometheus-operator: serviceaccount "prometheus-operator" not found
Richard Li
@richarddli
ah,
so there are still some bugs in the monitoring YAML at the moment
you may need to futz with the namespace in the rbac files
(i used kns and forge to set it up because I was in a hurry)
sorry about that :-D
Nenad Ilic
@nenadilic84
all good, I'll try to fix it :wink:
Bruno Amaral
@bamaralf
Hi
I need a help configuring ambassador to expose a secure websocket (wss)
Did anyone here perform this before?
Sergio Bilello
@SergioBilello_twitter
Hi guys!
minikube start --kubernetes-version=v1.7.0 --extra-config=apiserver.Authorization.Mode=RBAC from https://gist.github.com/F21/08bfc2e3592bed1e931ec40b8d2ab6f5
Could this help to install https://github.com/datawire/blackbird/ on minikube?
Richard Li
@richarddli
@SergioBilello_twitter yes, you probably need RBAC enabled, yes. also, we're mostly on slack these days, https://d6e.co/slack