Github user asfgit closed the pull request at:
https://github.com/apache/bigtop/pull/252
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/bigtop/pull/246
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/244
Hey @evans-ye, I see this has been committed upstream. Just FYI, if you
included a "Closes #244" in the upstream commit message, the github bot would
have automatically closed this PR.
This is a good example [1] of what we were referring to.
Thanks,
Cos
[1] https://issues.apache.org/jira/browse/BIGTOP-2283
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do
Cos, RJ, thanks for the response/advice..what I hear is that opening a JIRA
ticket on the crail integration would be a good starting point..we'll do so
and take it from it there..
On Jul 5, 2017 8:06 PM, "Konstantin Boudnik" wrote:
Thanks for bringing this to the table,
Github user johnsca commented on the issue:
https://github.com/apache/bigtop/pull/252
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user c0s commented on the issue:
https://github.com/apache/bigtop/pull/252
wow, an interesting approach indeed. Looks legit, though
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/252
BIGTOP-2836: charm metric collector race condition
Ensure `echo 0` is the last thing to run so that the metric hook does not
cause a failed deployment. Works in all tested scenarios:
Kevin W Monroe created BIGTOP-2836:
--
Summary: charm metric collector race condition
Key: BIGTOP-2836
URL: https://issues.apache.org/jira/browse/BIGTOP-2836
Project: Bigtop
Issue Type: Bug
Github user c0s commented on the issue:
https://github.com/apache/bigtop/pull/251
Looks logical and elegant. +1 (w/o any testing_
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/251
BIGTOP-2835: puppet fails when bigtop::jdk_preinstalled is true
Many modules require `Package["jdk"]`. Ensure it is available regardless of
the `bigtop::jdk_preinstalled` option. Modify the jdk
GitHub user nareshgbhat opened a pull request:
https://github.com/apache/bigtop/pull/250
BIGTOP-2824: Add centos 7 aarch64 sandbox support
This patch will add the CentOS 7 AArch64 support for sandbox.
Signed-off-by: Naresh Bhat
You can merge this
GitHub user nareshgbhat opened a pull request:
https://github.com/apache/bigtop/pull/249
BIGTOP-2787: Add centos 7 aarch64 bigtop slaves
Add centos-7 bigtop slave support for ARM64 architecture.
Signed-off-by: Naresh Bhat
You can merge this pull
GitHub user nareshgbhat opened a pull request:
https://github.com/apache/bigtop/pull/248
BIGTOP-2833: Fix puppetize issue for AArch64
The patch fix the execution issue of puppetize.sh
on AArch64 architecture
Signed-off-by: Naresh Bhat
You can
GitHub user nareshgbhat opened a pull request:
https://github.com/apache/bigtop/pull/247
BIGTOP-2794: Add centos 7 aarch64 docker puppet
Add CentOS 7 docker-puppet for AArch64 architecture. The base image is
pulled from https://hub.docker.com/r/centos/aarch64/ which has 7 as
15 matches
Mail list logo