[GitHub] [bigtop] guyuqi edited a comment on pull request #669: BIGTOP-3376: Make Mpack as a standalone component in Bigtop
guyuqi edited a comment on pull request #669: URL: https://github.com/apache/bigtop/pull/669#issuecomment-1004490476 @hesamd108 Please build **Ambari RPMs** and Bigtop-Mpack from our Bigtop source code: docker run --rm -v `pwd`:/ws --workdir /ws bigtop/slaves:trunk-centos-7 bash -c '. /etc/profile.d/bigtop.sh; ./gradlew allclean bigtop-utils-pkg bigtop-groovy-pkg bigtop-jsvc-pkg ambari-pkg bigtop-ambari-mpack-pkg' The RPMs would be in BIGTOP_SOURCE/output. After installing Bigtop-Mpack rpm, the Mpack would be loacated on: `/usr/lib/bigtop-ambari-mpack` Then, Pls follow the deployment steps: https://github.com/apache/bigtop/pull/555#issuecomment-562415260. -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] guyuqi commented on pull request #669: BIGTOP-3376: Make Mpack as a standalone component in Bigtop
guyuqi commented on pull request #669: URL: https://github.com/apache/bigtop/pull/669#issuecomment-1004490476 @hesamd108 Please build Ambari RPMs from our Bigtop source code: docker run --rm -v `pwd`:/ws --workdir /ws bigtop/slaves:trunk-centos-7 bash -c '. /etc/profile.d/bigtop.sh; ./gradlew allclean bigtop-utils-pkg bigtop-groovy-pkg bigtop-jsvc-pkg ambari-pkg' The RPMs would be in BIGTOP_SOURCE/output. Then, Pls follow the deployment steps: https://github.com/apache/bigtop/pull/555#issuecomment-562415260. -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] iwasakims commented on pull request #848: BIGTOP-3626: Upgrade log4j dependencies for ycsb
iwasakims commented on pull request #848: URL: https://github.com/apache/bigtop/pull/848#issuecomment-1004470465 @elukey Yeah, it seems to be cleanly applicable to branch-3.0. I use command lines like following for cherry-picking. It would nice if you can build and test the artifacts before pushing the branch to GitHub/Gitbox. ``` $ git checkout branch-3.0 $ git pull origin branch-3.0 $ git log -1 --oneline master 265e891a (origin/master, origin/HEAD, master) BIGTOP-3626: Upgrade log4j dependencies for ycsb (#848) $ git cherry-pick -x 265e891a ... $ git push origin branch-3.0 ``` -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Docker arm-5 node not reachable by Jenkins
Hi Luca, Sorry for the late response. Yuqi and I are responsible for these Arm CI nodes. I'll check with this and update you later. Regards, Jun Luca Toscano 于2021年12月28日周二 16:48写道： > Hi everybody, > > I've set https://ci.bigtop.apache.org/computer/docker-slave-arm-5/ > temporarily offline in the Jenkins UI, it seems not reachable via ssh > from the Jenkin's perspective. > > What is the procedure to follow for these nodes? > > Luca >
[GitHub] [bigtop] iwasakims commented on pull request #851: BIGTOP-3614: allow to change the docker-compose cfg in the provisioner
iwasakims commented on pull request #851: URL: https://github.com/apache/bigtop/pull/851#issuecomment-1004464593 @elukey All invocation of `docker-compose` command should be replaced with `docker-compose -f $docker_compose_yamlconf`? I got following error since `docker-compose` without `-f` seeks the file named docker-compose.yml or docker-compose.yaml. ``` $ mv docker-compose.yml docker-compose-renamed.yml $ ./docker-hadoop.sh \ --docker-compose-yml docker-compose-renamed.yml \ --create 1 \ --image bigtop/puppet:trunk-centos-8 \ --memory 8g \ --repo file:///bigtop-home/output \ --disable-gpg-check \ --stack zookeeper Environment check... Check docker: Docker version 20.10.7, build f0df350 Check docker-compose: docker-compose version 1.26.2, build eefe0d31 Check ruby: ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux] Creating 20220104_011930_r8500_bigtop_1 ... done ERROR: Can't find a suitable configuration file in this directory or any parent. Are you in the right directory? Supported filenames: docker-compose.yml, docker-compose.yaml ... ``` -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] elukey opened a new pull request #851: BIGTOP-3614: allow to change the docker-compose cfg in the provisioner
elukey opened a new pull request #851: URL: https://github.com/apache/bigtop/pull/851 This is a simple change to allow docker-compose to use a different config file when creating instances. This is useful when testing new settings and also to keep multiple versions of docker-compose.yml (if the same version cannot be re-used across multiple OS etc..). For example, from my recent tests the actual docker-compose.yml config seems not to work with cgroup v2 and systemd on Debian 10/11. -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] elukey edited a comment on pull request #848: BIGTOP-3626: Upgrade log4j dependencies for ycsb
elukey edited a comment on pull request #848: URL: https://github.com/apache/bigtop/pull/848#issuecomment-1004130685 @iwasakims thanks a lot for the reply! Cherry picking to branch-3.0 is something that I didn't think of, probably this change should be ported as well? -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] elukey commented on pull request #848: BIGTOP-3626: Upgrade log4j dependencies for ycsb
elukey commented on pull request #848: URL: https://github.com/apache/bigtop/pull/848#issuecomment-1004130685 @iwasakims thanks a lot for the reply! -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [bigtop] vivostar opened a new pull request #850: BIGTOP-3627. Update the readme doc
vivostar opened a new pull request #850: URL: https://github.com/apache/bigtop/pull/850 When I deploy components according to the Readme doc, I find an error occur  Then, I find such a issue to discribe it https://issues.apache.org/jira/browse/BIGTOP-3088 The issue has been fixed, but the doc haven't updated, so I make this commit to fix the gap. -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (BIGTOP-3627) There will be an error if you deploy components according to the deploy Readme
Shuaipeng Lee created BIGTOP-3627: - Summary: There will be an error if you deploy components according to the deploy Readme Key: BIGTOP-3627 URL: https://issues.apache.org/jira/browse/BIGTOP-3627 Project: Bigtop Issue Type: Bug Components: deployment Reporter: Shuaipeng Lee Assignee: Shuaipeng Lee Attachments: image-2022-01-03-21-17-52-853.png [https://github.com/apache/bigtop/blob/master/bigtop-deploy/puppet/README.md] According to above Readme doc, when you deploy components by Puppet, there will be an error like this . !image-2022-01-03-21-17-52-853.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [bigtop] iwasakims commented on pull request #848: BIGTOP-3626: Upgrade log4j dependencies for ycsb
iwasakims commented on pull request #848: URL: https://github.com/apache/bigtop/pull/848#issuecomment-1004042225 @elukey Sorry for late reply. > I noticed on the Wiki that we have a procedure via Gitbox, but I am wondering if simply merging from the Github UI is fine as well for the project (and if so, if there are some gotchas before doing it). Merging PR on GitHub UI should be enough for updating master branch. I use Git CLI for cherry-picking the commit to older branches such as branch-3.0 and branch-1.5. I always use "squash and merge" for associating one commit to one JIRA issue. (Hadoop disabled other choises on GitHub site configuration.) You should be able to commit the patch to Gitbox too since changes are synced between GitHub and Gitbox. I usually use GitHub because almost all patches are submitted via GitHub PR these days. https://blogs.apache.org/foundation/entry/the-apache-software-foundation-expands -- 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: dev-unsubscr...@bigtop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
