Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Zoran Regvart
    @zregvart
    We need OpenShift to run Syndesis on, for that there's minishfit up to OpenShift 3.11 and Code ready containers (crc), from 4.x onwards...
    Zoran Regvart
    @zregvart
    That said, we're working on a standalone mode of installation, so it would only require OpenShift or Kubernetes to run the integrations, not to design them
    And we're trying to add Kubernetes support, which is kinda working at the moment if you're using Camel-K, but there might be some rough edges
    Zoran Regvart
    @zregvart
    We managed to get the release push some artifacts to GitHub (we have daily pre-releases https://github.com/syndesisio/syndesis/releases/tag/1.9.100-20191105), and with these I can see that the syndesis-extra-permissions ClusterRole has the changes I've made
    María Arias de Reyna
    @Delawen
    Thank you for all this background work :)
    I think @KurtStam was the one working on Kubernetes?
    Zoran Regvart
    @zregvart
    There's one tidbit that we have to update in the README when installing via the syndesis script, we should be doing syndesis minishift --install --nodev if we don't want to build the images locally, to test out on our local minishift
    Zoran Regvart
    @zregvart
    PR to add --nodev to the README: syndesisio/syndesis#7083
    Hmm, with --nodev I don't see the DeploymentConfig for the syndesis-db, odd
    I also don't see the deploymentconfig/finalizers resource in the syndesis-extra-permissions clusterrole...
    Zoran Regvart
    @zregvart
    I needed to remove the cached $HOME/.syndesis/bin/syndesisand fixed the script to re-download the operator binary (syndesisio/syndesis#7084)
    with those fixes syndesis minishift --install --nodev should install the latest version, I'll try now with the stable tag to be sure if that's okay
    Zoran Regvart
    @zregvart
    with the --tag I just get the latest version
    Arkadiusz Ryćkowski
    @ryckowski
    while waiting till stable vesion will be fixed I'd tried to build and run it locally. I run ./syndesis build --all-images -f -d. Bot not sure how to deploy the images. When I run syndesis minishift --install it complains about missing operator under my home/.syndesis/bin/syndesis. I'd built it: syndesis build -m operator --local --ensure but it looks I missed the point
    Zoran Regvart
    @zregvart
    it's the tools/bin/syndesis shell script that downloads the operator binary to $HOME/.syndesis/bin if you have the operator built you can install syndesis by copying it there and running syndesis minishift --install --nodev that will get you the latest version (--tag seems to be ignored at the moment)
    Zoran Regvart
    @zregvart
    if you have the minishift running, then you can also do what the tools/bin/syndesis script does:
    $ oc login -u admin
    $ install/operator/dist/linux-amd64/syndesis-operator install cluster
    $ oc login -u developer
    $ install/operator/dist/linux-amd64/syndesis-operator install app
    Arkadiusz Ryćkowski
    @ryckowski
    thanks, actually I've run but didn't notice it due to some errors in the console
    Amr Eldemerdash
    @aeldemerdash
    Hello Guy, I just want to try to install syndesis on my MAC laptop, when I follow the instruction of the quick start, the syndesis-server POD getting failed because of Caused "by: java.net.UnknownHostException: syndesis-db" error !
    I tried to create the syndesis-db POD manually but I getting many error, Does anyone face this problem before?
    Amr Eldemerdash
    @aeldemerdash
    I run the below commands to try to fix it but still getting the same error
    $ oc login -u admin
    $ oc edit clusterrole syndesis-extra-permissions
    adding deploymentconfig/finalizers to the list
    Amr Eldemerdash
    @aeldemerdash
    Worked after stopping the minishfit and start it again :D :D @zregvart Many Thanks :)
    Arkadiusz Ryćkowski
    @ryckowski
    Trying to start with ui development. Run postgresql, backend and BACKEND=http://localhost:8080 yarn watch:app:proxy but got error like Failed to compile. ../packages/apicurio-adapter/dist/apicurio-adapter.js Module not found: Can't resolve 'file-loader' in '/home/arek/w/projects/syndesis/app/ui-react/packages/apicurio-adapter/dist'
    María Arias de Reyna
    @Delawen

    Hi!

    We discussed about moving master branch to 2.x to start experimenting with the new camel dependencies. Is someone working on that to create that branch?

    Zoran Regvart
    @zregvart
    @ryckowski perhaps you need to run yarn install first to (re)fetch the dependencies
    @Delawen not that I'm aware of...
    María Arias de Reyna
    @Delawen
    I can simply change the version number but I remember someone ( @christophd ? @KurtStam ? ) experimenting with the change of the dependencies?
    Zoran Regvart
    @zregvart
    I think @christophd has a branch somewhere with Spring Boot 2.x and then (another one) with Camel 3
    Christoph Deppisch
    @christophd
    here is my work on updating Syndesis to Spring Boot 2.x: https://github.com/syndesisio/syndesis/tree/camel-fuse-2.23.x
    probably needs a rebase on latest master but should work in terms of green unit tests, integration tests and style checks
    @phantomjinx started to work on updating to Camel 3 based on that branch
    Amr Eldemerdash
    @aeldemerdash
    All my pods are working and minishift is working fine but when I am trying to reach the syndesis URL I get "This site can’t be reached" ?
    Andrej Smigala
    @asmigala
    what is the route you are accessing?
    Amr Eldemerdash
    @aeldemerdash
    How can I check? I am just using the quick start !
    Amr Eldemerdash
    @aeldemerdash
    When I changed the network it worked fine, I don't know what was the problem
    Amr Eldemerdash
    @aeldemerdash
    I want to create an AMQP connection and when specifying tcp://localhost:61616, I getting Provider scheme NOT recognized: [tcp]
    Error
    Amr Eldemerdash
    @aeldemerdash
    I connected using amqp://[the IP of the machine (localhost didn't work)]:5672
    Zoran Regvart
    @zregvart
    Yeah, seems like that error about tcp not recognized is when we're unable to connect to broker, I see the integration test we have uses tcp: https://github.com/syndesisio/syndesis/blob/89f9a49cdd34dc1c0f0ffb22413fd378ec0a10c1/app/test/integration-test/src/test/resources/io/syndesis/test/itest/amq/HttpToAMQ-export/model.json#L1822
    Arkadiusz Ryćkowski
    @ryckowski
    As I was faceing issues while building the project I've just started from clean I think more compatible dev environment: ubuntu 18.04 lts, go 1.13, docker 18.09, jdk 1.8 and getting error
    > github.com/syndesisio/syndesis/install/operator/tests/e2e tested by
    > github.com/syndesisio/syndesis/install/operator/tests/e2e.test imports
    > github.com/syndesisio/syndesis/install/operator/pkg/syndesis/template: module github.com/syndesisio/syndesis@latest found (v0.3.6), but does not contain package github.com/syndesisio/syndesis/install/operator/pkg/syndesis/template
    on master and even I derive my branch from stable 1.8.12
    Zoran Regvart
    @zregvart
    hmm, I think on master we have landed a large refactor in the operator, on 1.8.12 should build fine AFAIK; I'm running on Fedora 31 with go 1.13.3, docker 18.09.8, and 1.8.0_232; you've run syndesis build -m operator or something like that?
    phantomjinx
    @phantomjinx
    Yeah, looks like a small bug has worked its way into the operator build pkgs on master
    Zoran Regvart
    @zregvart
    hmm, there's no template in install/operator/pkg/syndesis (https://github.com/syndesisio/syndesis/tree/master/install/operator/pkg/syndesis) perhaps git clean would help?
    Thanks @phantomjinx for the PR to fix that: syndesisio/syndesis#7132
    Arkadiusz Ryćkowski
    @ryckowski
    on stable it's ok, my fault
    Arkadiusz Ryćkowski
    @ryckowski

    I'd like to start some dev based on 1.8.12 branch. I did build:

    syndesis --all-images -f -d
    syndesis minishift --install --local
    and the pod syndesis-server raised the error UnknownHostException: syndesis-db. I know it's been solved in master branch and it's not clear for me why stable is affected. I can see in the logs trequest to download the operator, might be this the reason the local one is not used

    Zoran Regvart
    @zregvart
    Yeah, not sure what's going on there, now I see the same issue we fixed: {"level":"error","ts":1573723238.364849,"logger":"kubebuilder.controller","msg":"Reconciler error","controller":"syndesis-controller","request":"myproject/app","error":"roles.rbac.authorization.k8s.io \"syndesis-editor\" is forbidden: attempt to grant extra privileges: [{[get] [] [deploymentconfigs/finalizers] [] []} {[list] [] [deploymentconfigs/finalizers] [] []} {[create] [] [deploymentconfigs/finalizers] [] []} that permission issue on deploymentconfigs/finalizers
    Zoran Regvart
    @zregvart
    (supposedly fixed)