You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/06/14 08:04:38 UTC
[GitHub] [camel-k] barius opened a new issue, #3356: kamel local run support --build-property ?
barius opened a new issue, #3356:
URL: https://github.com/apache/camel-k/issues/3356
This may be a feature request :P
During fast prototyping on JDBC mysql connection, I have to try different combinations of `--property` and `--build-property`.
The `--build-property quarkus.datasource.camel.db-kind=mysql` is for quarkus to detect mysql stuff and have to be used with `-d mvn:io.quarkus:quarkus-jdbc-mysql`.
Building a kit via `kamel run` on my local k8s costs around ~2min, and `kamel local run` just takes seconds.
Also, local runs seems to be faster than k8s runs (which may be my problem because I'm just using my macbook to run docker desktop and there are other overheads such as istio etc.).
Is there any plan on adding `--build-property` to` kamel local run`?
As far as I have found out, passing `--build-property` to quarkus involves adding these properties to `src/main/resources/application.properties` file in the maven build directory.
I'm able to emulate the behavior by manually editing this file and run `mvn -q package` as a workaround.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] barius commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
barius commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1154952496
@tadayosi
> In many cases, building kits on a k8s cluster takes time because it downloads jars externally every time. Hosting a maven repo manager like Nexus in a cluster might mitigate the building time. While there's no good documentation for the technique, you could look at this in the meantime:
Thanks! I'm totally new to maven. I'll try nexus, and I will need to find a way to make nexus use another public mirror:
```
--maven-repository "https://maven.aliyun.com/repository/public@id=aliyunmaven@name=阿里云公共仓库@mirrorOf=central"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] barius closed issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
barius closed issue #3356: kamel local run support --build-property ?
URL: https://github.com/apache/camel-k/issues/3356
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1154967488
> btw any ideas on the strangely slow performance on k8s? Got ~3x slower when connecting to mysql via jdbc:// in k8s than local run.
Probably it's because the different layers of virtualization. However, a fine tuned cluster should behave as any local machine. I guess you need to investigate how to improve network performances in your cluster.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1154893593
The `local` command just execute a jvm locally on your machine and it is meant to be used for quick testing and local troubleshooting. I don't think it can be on parity with the cluster `run` which is in charge to arrange the project, look for dependencies, capabilities, etc... , build and store an IntegrationKit (incremental). Think of that as a very thin layer on top of a normal Camel Quarkus execution.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] barius commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
barius commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1155020576
> Probably it's because the different layers of virtualization. However, a fine tuned cluster should behave as any local machine. I guess you need to investigate how to improve network performances in your cluster.
Sure, I'll work on that. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] barius commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
barius commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1158376927
Closing this issue because `kamel run` is a better option.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] tadayosi commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
tadayosi commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1154909282
In many cases, building kits on a k8s cluster takes time because it downloads jars externally every time. Hosting a maven repo manager like Nexus might mitigate the building time. While there's no good documentation for the technique, you could look at this in the meantime:
https://camel.apache.org/camel-k/1.9.x/contributing/e2e.html#using-nexus
I believe you could do
```
kubectl apply -f https://raw.githubusercontent.com/apache/camel-k/main/e2e/support/files/nexus.yaml
```
then you could use the nexus with this install command:
```
kamel install --maven-repository=http://nexus.nexus/repository/maven-public/@id=nexus@mirrorOf=*
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] barius commented on issue #3356: kamel local run support --build-property ?
Posted by GitBox <gi...@apache.org>.
barius commented on issue #3356:
URL: https://github.com/apache/camel-k/issues/3356#issuecomment-1154947517
@squakez Thanks for the reply!
> I don't think it can be on parity with the cluster run which is in charge to arrange the project, look for dependencies, capabilities, etc... , build and store an IntegrationKit (incremental). Think of that as a very thin layer on top of a normal Camel Quarkus execution.
Yes, I totally agree with that. Took me a while to figure out the difference between `--build-property` and `--property` though :P
Anyway, `kamel run` is surely a better option in regards of log formatting, `--dev` mode with auto sync, .etc so I will stick with that :)
btw any ideas on the strangely slow performance on k8s? Got ~3x slower when connecting to mysql via `jdbc://` in k8s than local run.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org