Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Paul Capestany
    @PaulCapestany
    oops, logs I'd posted above were from journalctl, here's the actual output from running the cluster kickoff commands: https://gist.github.com/PaulCapestany/35065c2fa242291a5015
    Traun Leyden
    @tleyden
    crap, it's not spitting out the sync gw fleet units.
    can you run fleetctl cat on the sync gateway units and paste the output? was this a "fresh cluster"? I wonder if the old unit files never got overwritten?
    could you try running https://github.com/tleyden/couchbase-cluster-go#destroying-the-cluster first and then trying again?
    btw it's possible to get into the container and see the couchbase-cluster-go commit id via:
    $ docker exec -ti <container_id> bash
# cd /opt/go/src/github.com/tleyden/couchbase-cluster-go
# git status
    Paul Capestany
    @PaulCapestany
    yeah i just came to same conclusion about fleet units
    they don't get updated it seems
    still show old ones
    (and yeah, it was a totally fresh cluster)
    Paul Capestany
    @PaulCapestany
    and yeah... git status shows that couchbase-cluster-go is on freshest commit. seems like fleet unit files just don't get swapped out with current enable-code-refresh implementation
    Traun Leyden
    @tleyden
    we need to have it spit out the sync gateway unit files into the logs so we can see that it's generating the correct unit files
    Paul Capestany
    @PaulCapestany
    would it make sense to use an automatic hook to deploy new docker images when there are commits to the couchbase-cluster-go repo? cuz that's what you're basically trying to do with enable-code-refresh, or no?
    Traun Leyden
    @tleyden
    yes and no, enable-code-refresh should have a much tighter loop since it doesn't have to wait for a docker image rebuilt (can take up to 30 mins)
    I'm making that logging change I mentioned right now
    Paul Capestany
    @PaulCapestany
    gotcha
    Traun Leyden
    @tleyden
    ok just pushed to master
    Paul Capestany
    @PaulCapestany
    yup, gonna try on new cluster
    Paul Capestany
    @PaulCapestany
    @tleyden the log statements you added don't even get called
    like, I see the code that does go get -u -v github.com/tleyden/couchbase-cluster-go/... ...which should install new binary, right? but for some reason the new binary isn't being used?
    Traun Leyden
    @tleyden

    you're gonna hate me for saying this, but "works on my computer"

    I just ran it and:

    https://gist.github.com/tleyden/005c62266ea5e87f7810

    that wasn't a "fresh cluster" .. I had a cluster running (CoreOS alpha 681.0.0 btw), and ran the commands under https://github.com/tleyden/couchbase-cluster-go#destroying-the-cluster to clean out previous fleet units and other residue (wiped /opt/couchbase/var)
    Paul Capestany
    @PaulCapestany
    ok, I've just been running as a fresh cluster each time
    Traun Leyden
    @tleyden
    hmm. I mean it should work there too.
    Paul Capestany
    @PaulCapestany
    ha. just realized I wasn't using the "update-wrapper" argument when trying to use enable-code-refresh. doh
    of course it was something really dumb
    Traun Leyden
    @tleyden
    ohhhh
    that would explain things
    Paul Capestany
    @PaulCapestany
    yeah
    trying again... with the actual proper args...
    Traun Leyden
    @tleyden
    the enable-code-refresh just sticks a value into etcd. but the command needs to be wrapped in update-wrapper to look at the value in etcd and act on it. (it rebuilds the code, then calls the actual stuff you want to call)
    Paul Capestany
    @PaulCapestany
    yeah, the sad thing is I knew that. just hadn't noticed i was missing the crucial "update-wrapper" part
    Traun Leyden
    @tleyden
    haha. well now you'll never forget :P
    Paul Capestany
    @PaulCapestany
    seriously.
    Patrick Heneise
    @PatrickHeneise
    @tleyden going to try the couchbase container on google cloud these days. Will let you know if it works.
    Traun Leyden
    @tleyden
    @PatrickHeneise glad to hear. You might want to check out https://github.com/couchbase/kubernetes which has been tested on GKE
    Patrick Heneise
    @PatrickHeneise
    great, going to have a look. Thanks!
    Traun Leyden
    @tleyden
    also, I'm planning to do a talk at CB Connect on Kubernetes, and apparently the talks will have live streaming
    and I believe another team is doing a joint talk with Google about performance testing Couchbase Server on Google Compute Engine
    Patrick Heneise
    @PatrickHeneise
    I've seen a repo on that, yes
    Traun Leyden
    @tleyden
    Couchbase now has an official docker repo on dockerhub! https://registry.hub.docker.com/u/library/couchbase/
    Patrick Heneise
    @PatrickHeneise
    couchbase/kubernetes#1
    finally something to give back ;)
    Patrick Heneise
    @PatrickHeneise
    just seen the 2nd server doesn't get recognised and there's a setup screen instead of user/pw
    Traun Leyden
    @tleyden
    thanks @PatrickHeneise, I will take a look after the conference
    I hope you are watching the live stream stuff
    at 1:45pm today Brian "redbeard" Harrington is giving a talk on couchbase + kubernetes
    Patrick Heneise
    @PatrickHeneise
    well, I'm in CEST, that's a bit complicated :/
    Traun Leyden
    @tleyden
    @PatrickHeneise ah, gotcha. well I'll let you know when the videos go online
    Patrick Heneise
    @PatrickHeneise
    thanks!
    something changed with google cloud ... the nodes aren't node-1 node-2 any more :(