Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 23 12:39

    cezarsa on master

    provision/kubernetes: add team … provision/swarm: add team label… (compare)

  • Aug 23 12:39
    cezarsa closed #2333
  • Aug 23 12:17
    cezarsa synchronize #2333
  • Aug 23 11:44
    cezarsa opened #2333
  • Aug 15 20:01

    morpheu on master

    router/api: expand env var on c… router/api: use getstring for g… (compare)

  • Aug 15 20:01
    morpheu closed #2332
  • Aug 15 19:33

    morpheu on master

    iaas/dockermachine: fix custom … (compare)

  • Aug 15 19:33
    morpheu closed #2331
  • Aug 15 19:32
    morpheu synchronize #2332
  • Aug 15 19:25
    morpheu opened #2332
  • Aug 15 18:15
    morpheu opened #2331
  • Aug 12 17:59

    cezarsa on 1.7.4

    (compare)

  • Aug 12 17:58

    cezarsa on master

    app: marshall internalAddresses… read user quota permission + fi… Add Kasra Fakhari to contributo… and 2 more (compare)

  • Aug 12 17:57

    cezarsa on release-1.7.0

    bump version to 1.7.4 (compare)

  • Aug 12 17:56

    cezarsa on release-1.7.0

    app: marshall internalAddresses… read user quota permission + fi… Add Kasra Fakhari to contributo… (compare)

  • Aug 12 17:50

    cezarsa on master

    bump version to 1.7.0 app: add configurable rate limi… app: fix leaked log db connecti… and 18 more (compare)

  • Aug 08 13:43

    cezarsa on master

    provision/kubernetes: remove un… (compare)

  • Aug 02 18:12
    rodolfo3 synchronize #2330
  • Aug 02 15:25
    rodolfo3 edited #2330
  • Aug 02 15:25
    rodolfo3 edited #2330
Alex Whitt
@WhittlesJr
(outside of the installer script?)
Magno Torres
@magnotorres
Alex Whitt
@WhittlesJr
That's all imperative though (issuing commands), rather than declarative (config file driven).
Alex Whitt
@WhittlesJr
Whenever I restart tsurud, vboxnet1 goes down, and doesn't come back up. If I remove and re-add my dockermachine node, it comes back up. Anyone know what to do about that?
Alex Whitt
@WhittlesJr
Another problem I'm having is the same as this issue: tsuru/tsuru#1823. I tried running my own docker registry, but I get "connection refused" when I set docker:registry to "127.0.0.1:5000". (And the firewall was open).
Magno Torres
@magnotorres
With that address you will have connectivity if your registry is in the same VM
Alex Whitt
@WhittlesJr
@magnotorres : Ah, so the registry push is happening from inside the VM? I was thinking it was happening at the host level. The registry is on the host, so I guess I'll have to have it accessible to my host-only network?
I think the hardest part of my journey to understanding tsuru has been parsing out what is happening where... the documentation and config architecture seem to kind of fluidly switch semantic contexts between host and VMs.
Guilherme Rezende
@guilhermebr
@WhittlesJr registry will be used by all nodes(VMs) of your pools. the scheduler can choose any node to build the platform and app
Manuel Holtgrewe
@holtgrewe
Hi. I have the following use case. I'm running a Django app that should go behind a reverse proxy (e.g., planb). Almost everything should be forwarded to it. However, certain URLs (that can appear and go away while the app is running) should be forwarded to docker containers, e.g., /docker/uuid1/* should go to http://localhost:1025/* and /docker/uuid2/* should go to http://localhost:2345/*. Does planb support this?
Magno Torres
@magnotorres
@holtgrewe planb does not currently supports that. You can use an static app which that filters with a customized nginx.conf
Rômulo Férrer Filho
@romulofff

Hi everyone! Not sure this is where I should ask this, but here I go. I'm a Computer Engineering Student and I'm doing my homework on Open Source PaaS platforms. I found Tsuru very interesting. Therefore I have a few questions about the project that I couldn't find on the website.
1- Are there any organizations that provide support to the platform?
2- What is the story behind Tsuru? When and how was it created?

Sorry if this isn't the appropriate place for this. If anyone is willing to help me out, this is my e-mail: romulofffufc@gmail.com
Thank you!

Magno Torres
@magnotorres
Hi @romulofff , Globo.com is the sponsor of Tsuru PaaS, we don't provide enterprise support, but we are willing to help, as anyone in the community, and there are companies like Rivendel that provides enterprise support. Tsuru started in an epoch when we don't have a truly opensource PaaS (2012) ready for production. We were inspired by Heroku, and as we need to have a private PaaS our only option was to build one. We were the first PaaS to integrate with docker, before if was even opensource in 2013 deploying to production! At all that time we still see a great value in our platform, it is really powerful and simple to deploy, compared with our enterprise competitors, as we have an enterprise-level product, demanding little administrative infrastructure, easy to deploy and without vendor lock-in. At Globo we have 2 thousand apps(and growing fast) managed by Tsuru with products that demand huge amounts of infrastructure, attending millions of users - e.g.: Big Brother Brasil made more than 200 millions votes just in the last episode, demanding little support in the platform itself and transforming the way people work - with a culture of trust, autonomy, and ownership.
Rômulo Férrer Filho
@romulofff
Thank you @magnotorres, this is exactly what I needed!
Rodolfo Peixoto
@rodolfopeixoto
Hi, I'm trying to install tsuru with "tsuru install-create", this error: "Running pre-install checks...
Running pre-create checks...
Error: failed to provision components machines: failed to provision machines: error creating machine failed to create host: Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory""
I'm trying to install in ubuntu 18.04 , virtualbox 5.
Can someone help me?
Magno Torres
@magnotorres
@rodolfopeixoto sounds like your hardware is missing VT-X/AMD-v, which is necessary... you may need to enable it in BIOS. Or try to use docker directly via docker compose https://docs.tsuru.io/stable/contributing/compose.html
JohnAnt
@JohnAnt
Hello, I am doing a survey and I am looking the PC hardware requirments for Tsuru but I can't find anything in the website does anyone knows any link to check the requirements?
RhombusLabs
@LabsRhombus_twitter
How can we use swarm to add node
souzaxdr
@souzaxdr
Hi @LabsRhombus_twitter we will deprecate swarm with tsuru in the near future
RhombusLabs
@LabsRhombus_twitter

I am trying to add provisioned machine using tsuru node-add but its going in waiting status.

tsuru node-add docker pool=development --register address=http://xx.xx.xxx.xx:2375
tsuru node-update http://xx.xx.xxx.xx:2375 --enable

how can we add multiple machine to tsuru and rebalance the application or autoscale
souzaxdr
@souzaxdr
@LabsRhombus_twitter we recommend the use of kubernetes with the tsuru

@JohnAnt Today we have as example the Api of Tsuru running in 6 VMs of

CPU Cores 4
CPU (in MHz) 1530
Memory (in MB) 4096

We manage more than 2000 apps and more than 5000 docker containers

souzaxdr
@souzaxdr
@JohnAnt In this scenario the processing usually does not reach 50% of the CPU of the machines
shreeraman96
@shreeraman96

I am trying to integrate Gandalf with the Tsuru service for deploying apps through git

X - Tsuru dev environment with tsuru api, client and its components.
Y - git repository server in cloud 

Tsuru API - hosted as container in X
Gandalf container with webserver hosted as container in X
in the Gandalf container "GANDALF_HOST" is set as "Y"

When I create a new application from tsuru client -

I get this message - new repository created at git@y:<proj_name>.git
and there is also repository folder created at the bare location : /var/lib/gandalf/repository
But the repository is not being created in the Git remote server

How and where should we setup the gandalf? am I missing any step? and should gandalf be hosted in the same server as our git ?
and how should we set "repo-manager" and "git:api-server" in tsuru.conf?

Guilherme Rezende
@guilhermebr
@shreeraman96 gandalf is a git server, you don't need an extra git repository
repo-manager: gandalf
git:api-server: http://gandalf-host:port
Kasra Fakhari
@kasra73
Hi. Is there an implementation available for traefik router? I'd like to implement it using tsuru Router API specification. If someone knows about an implementation or intrested in contribution, let me know. I'll be happy to hear your idea.
Guilherme Rezende
@guilhermebr
@kasra73 Hi. I don't know any implementation of traefik router for tsuru, but looks like an amazing contribution.
Magno Torres
@magnotorres
@kasra73 the modern/better way to do that is using the router api: https://docs.tsuru.io/stable/reference/router-api.html
Chase Pierce
@syntaqx
:wave:
Kasra Fakhari
@kasra73
Hi. I have developed traefik router integration using cosul backend using koa and type script. Here is the repository on github:
https://github.com/kasra73/tsuru-traefik-router
It's tsuru ready! I mean you can simply deploy it using tsuru nodejs platform then add the url to your tsuru.conf
routers:
  hipache:
    type: hipache
    domain: example.com
    redis-server:127.0.0.1:6379
  traefik:
    type: api
    api-url: http://traefik-router.example.com
Kasra Fakhari
@kasra73
I also make some changes in swagger api specification based on the k8s router implementation.
https://app.swaggerhub.com/apis/kasra73/tsuru-router_api/1.1.0
Rodolfo Stangherlin
@rodolfo3
Hi. Is the https://hub.docker.com/r/tsuru/gandalf image ready for production? I am trying to use it, but I don't know why is it not working...
Emerson Rocha
@fititnt

@rodolfo3

Hi. Is the https://hub.docker.com/r/tsuru/gandalf image ready for production? I am trying to use it, but I don't know why is it not working...

Hi Rodolfo! I'm very new to Tsuru, just done a MVP some weeks ago, but I'm moving to create a 3 Node Tsuru cluster from scratch plus lots of documentation in Portuguese for end users.

Gandalf was one thing I skipped on MVP because turns out that I found tsuru-client very poweful to start. But if you want some help with this (and at least be able to test if I implement soon the Gandalf) I could try put Gandalf first on my priorities. And since I'm documenting everything in the open, could useful for you too.

If you still need help can private message me here on on Twitter.

Emerson Rocha
@fititnt

On tsuru version 1.7.0-rc1, I'm having some problem to log as admin immediately after the creation.

I will try a bit better to find if was not some mistake on configurations, etc, but if persist I will report on the main repository.

For now I have this issue here EticaAI/aguia-pescadora#6 (in portuguese, but google translate should work fine) to document my progress if someone interested to see it earlier. The same repository have all information.

Guilherme Rezende
@guilhermebr
@rodolfo3 yes the image is ready for production. What problem are you having?
Rodolfo Stangherlin
@rodolfo3
@guilhermebr I got it working - it was my fault configuring it...
but I'm having problems using logstash for metrics and logs. My logstash log says:
[2019-07-02T22:37:22,754][WARN ][logstash.outputs.elasticsearch] Could not index event to Elasticsearch. {:status=>400, :action=>["index", {:_id=>nil, :_index=>".measure-tsuru-2019.07.02", :_type=>"host_netrx", :routing=>nil}, #<LogStash::Event:0x2f0eda1b>], :response=>{"index"=>{"_index"=>".measure-tsuru-2019.07.02", "_type"=>"host_netrx", "_id"=>"t1nVtGsBR4vbPSvq22hZ", "status"=>400, "error"=>{"type"=>"illegal_argument_exception", "reason"=>"Rejecting mapping update to [.measure-tsuru-2019.07.02] as the final mapping would have more than 1 type: [host_cpu_wait, host_netrx]"}}}}
Rodolfo Stangherlin
@rodolfo3

my first error is:

[2019-07-03T18:40:33,840][ERROR][logstash.outputs.elasticsearch] Failed to install template. {:message=>"Got response code '400' contacting Elasticsearch at URL 'https://vpc-tsuru2-apps-gialqmcwk4rsjmg4adsylan7la.us-east-1.es.amazonaws.com:443/_template/tsuru-template'", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError", :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:80:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:291:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:278:in `block in perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:373:in `with_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:277:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:285:in `block in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:352:in `template_put'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/http_client.rb:86:in `template_install'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/template_manager.rb:28:in `install'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/template_manager.rb:16:in `install_template'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:129:in `install_template'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-9.4.0-java/lib/logstash/outputs/elasticsearch/common.rb:50:in `block in setup_after_successful_connection'"]

I'm trying with ES 5.6 and 6.0

Rodolfo Stangherlin
@rodolfo3
I removed the geoip section from the template and it works on ES 5.6. But the dashboard does not shows data for the node. It saves addr as 127.0.0.1, 10.0.3.227, 172.17.0.1, ::1, fe80::88b:edff:fe0a:6c88, fe80::42:d5ff:fe79:3d5d, fe80::2022:6cff:fe3a:4463. The dashboard searches for {'addr.keyword': [u'ip-10-0-3-227.ec2.internal']}}... is this a bug?
Rodolfo Stangherlin
@rodolfo3

also, when I trigger the autoscale (using tsuru node-autoscale-run), I get a rebalance from a host to the same host:

Moved unit 3dd(...)b7f -> 1d3(...)351 for "mobile-api-stg" from ip-10-0-3-63.ec2.internal -> ip-10-0-3-63.ec2.internal

Is there some config to avoid it?

should I stop to use docker and start to use kubernetes?
Gleicon Moraes
@gleicon
Hi does anyone have tried or can point to a write up on setting tsuru + k3s ?
Emerson Rocha
@fititnt

@gleicon Actually thats a great question! I'm not sure if someone else at least tried to replace Kubernetes with K3S to work with Tsuru, but this is something I personally would start testing.

One of my reasons to consider using Kubernetes (or if later is possible, k3s) is that seems to be much easier to deal with strategies to handle files (aka volumes) integrated with Kubernetes (or since is compatible, k3s) than with vanila docker. (even the first reference about k3s is my comment here, https://github.com/tsuru/tsuru/issues/2063#issuecomment-506250179, @gleicon ). I'm not saying that is bad use on vanila docker, just that maybe for usage with bigger setups, or different users, etc, kubernetes could be easier

I will take at least a few weeks to start test with k3s because I'm testing before with Kuberbetes (I'm new here, and also I'm new to Kubernetes), so I'm unable to give a fast response for you about if it works or not with k3s for now. I will leave for someone else that maybe already know Tsuru + Kubernetes to try replace with K3S.

Yehudi Brito
@yehudimikhael
How do I dynamically add auto scaling to the unit?
Magno Torres
@magnotorres
You can use the tsuru autoscale service: https://github.com/tsuru/tsuru-autoscale
Patrezze Alvarenga
@patrezze

Upgrade Tsuru Server from 1.6.2 to 1.7.4

Environment

Docker Version: 19.03.1
Linux Distribution: Ubuntu 16.04 LTS
Kubernetes Cluster: No

The result of tsurud migrate --dry is OK.

Opening config file: /etc/tsuru/tsuru.conf
Done reading config file: /etc/tsuru/tsuru.conf
Using "mongodb" database "tsuru" from the server "mongodb://######".
Running "migrate-apps-kubernetes-crd"... OK
Running "migrate-app-image-exposed-ports"... OK

tsurud migrate

Opening config file: /etc/tsuru/tsuru.conf
Done reading config file: /etc/tsuru/tsuru.conf
Using "mongodb" database "tsuru" from the server "mongodb://######".
Error: multiple errors reported (34):
error #0: no cluster
error #1: no cluster
error #2: no cluster
error #3: no cluster
error #4: no cluster
error #5: no cluster
error #6: no cluster
error #7: no cluster
error #8: no cluster
error #9: no cluster
error #10: no cluster
error #11: no cluster
error #12: no cluster
error #13: no cluster
error #14: no cluster
error #15: no cluster
error #16: no cluster
error #17: no cluster
error #18: no cluster
error #19: no cluster
error #20: no cluster
error #21: no cluster
error #22: no cluster
error #23: no cluster
error #24: no cluster
error #25: no cluster
error #26: no cluster
error #27: no cluster
error #28: no cluster
error #29: no cluster
error #30: no cluster
error #31: no cluster
error #32: no cluster
error #33: no cluster
Running "migrate-apps-kubernetes-crd"...

tsurud migrate-list

The migrate-apps-kubernetes-crd and migrate-app-image-exposed-ports appear as not executed.

+----------------------------------------+------------+-----------+
| Name                                   | Mandatory? | Executed? |
+----------------------------------------+------------+-----------+
| migrate-docker-images                  | true       | true      |
| migrate-pool                           | true       | true      |
| migrate-set-pool-to-app                | true       | true      |
| migrate-service-proxy-actions          | true       | true      |
| migrate-bs-envs                        | true       | true      |
| migrate-events-deploy                  | true       | true      |
| migrate-events-healer                  | true       | true      |
| migrate-rc-events                      | true       | true      |
| migrate-router-unique                  | true       | true      |
| migrate-app-plan-router-to-app-router  | true       | true      |
| migrate-pool-teams-to-pool-constraints | true       | true      |
| migrate-app-service-envs               | true       | true      |
| migrate-app-plan-id-to-plan-name       | true       | true      |
| migrate-roles                          | false      | true      |
| migrate-apps-kubernetes-crd            | true       | false     |
| migrate-app-image-exposed-ports        | true       | false     |
+----------------------------------------+------------+-----------+

I got errors with tsurud migrate. Is it necessary to fix? If I ignore them, does it have any impact?