[GitHub] bigtop pull request #358: BIGTOP-2101: ignite-hadoop contains an arch-depend...
GitHub user JunHe77 opened a pull request: https://github.com/apache/bigtop/pull/358 BIGTOP-2101: ignite-hadoop contains an arch-dependent shared lib ignite-shmem contains x86 binary only. A build step is added to create arch specific library for non-x86 platforms. Change-Id: I9f4f03ec61250da21c13a915dc7efd5303e95d5b Signed-off-by: Jun HeYou can merge this pull request into a Git repository by running: $ git pull https://github.com/JunHe77/bigtop BIGTOP-2101 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/358.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #358 commit 91a65820eef6a6b0ff88aa2a93938f8d3eaf3199 Author: Jun He Date: 2017-11-13T10:11:31Z BIGTOP-2101: ignite-hadoop contains an arch-dependent shared lib ignite-shmem contains x86 binary only. A build step is added to create arch specific library for non-x86 platforms. Change-Id: I9f4f03ec61250da21c13a915dc7efd5303e95d5b Signed-off-by: Jun He ---
[jira] [Created] (BIGTOP-3033) Spark build on OpenSUSE is failed
Jun He created BIGTOP-3033: -- Summary: Spark build on OpenSUSE is failed Key: BIGTOP-3033 URL: https://issues.apache.org/jira/browse/BIGTOP-3033 Project: Bigtop Issue Type: Bug Components: build, spark Affects Versions: 1.2.1 Reporter: Jun He Assignee: Jun He Spark building on OpenSUSE-42.3 has been failed for sometime. >From the >[log|https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/COMPONENTS=spark,OS=opensuse-42.3/354/console], > it should be some package missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: ASF Board Meeting Summary - May 16, 2018
Congrats, Peter! 2018-05-18 9:41 GMT+08:00 Evans Ye: > Congrats Peter! > > Peter Linnell 於 2018年5月17日 週四,下午11:49寫道: > > > On Wed, 16 May 2018 22:43:30 -0700 > > Roman Shaposhnik wrote: > > > > > Major congrats to Peter! Well deserved! > > > > > > Thanks, > > > Roman. > > > > > > > > > -- Forwarded message -- > > > From: Phil Steitz > > > Date: Wed, May 16, 2018 at 5:15 PM > > > Subject: ASF Board Meeting Summary - May 16, 2018 > > > To: committ...@apache.org > > > > > > > > > The May board meeting took place on the 16th. > > > > > > The April minutes were approved. > > > Minutes will be posted to > > > http://www.apache.org/foundation/records/minutes/ > > > > > > All of the received reports to the board were approved. > > > > > > The following resolutions were passed unanimously: > > > > > > A. Change the Apache MINA Project Chair (Guillaume Nodet, VP) > > > B. Change the Apache Bigtop Project Chair (Peter Linnell, VP) > > > C. Change the Apache Hadoop Project Chair (Vinod Kumar > > > Vavilapalli, VP) > > > D. Establish the Apache Traffic Control Project (David Neuman, VP) > > > E. Change the Apache Giraph Project Chair (Dionysios Logothetis, VP) > > > F. Change the Apache Camel Project Chair (Andrea Cosentino, VP) > > > G. Change the Apache Incubator Project Chair (Justin Mclean, VP) > > > > > > The next board meeting will be on the 20th of June. > > > > > > Hi all, > > > > Many thanks to Roman and Cos who convinced me to take this on, as well > > as proposing me as an Apache Foundation member. > > > > Luckily, we have a great team of folks on Bigtop, who, I am sure will > > make sure we have another successful year. > > > > Humbly, > > > > Peter > > > > >
Re: ASF Board Meeting Summary - May 16, 2018
Congrats Peter! Peter Linnell於 2018年5月17日 週四,下午11:49寫道: > On Wed, 16 May 2018 22:43:30 -0700 > Roman Shaposhnik wrote: > > > Major congrats to Peter! Well deserved! > > > > Thanks, > > Roman. > > > > > > -- Forwarded message -- > > From: Phil Steitz > > Date: Wed, May 16, 2018 at 5:15 PM > > Subject: ASF Board Meeting Summary - May 16, 2018 > > To: committ...@apache.org > > > > > > The May board meeting took place on the 16th. > > > > The April minutes were approved. > > Minutes will be posted to > > http://www.apache.org/foundation/records/minutes/ > > > > All of the received reports to the board were approved. > > > > The following resolutions were passed unanimously: > > > > A. Change the Apache MINA Project Chair (Guillaume Nodet, VP) > > B. Change the Apache Bigtop Project Chair (Peter Linnell, VP) > > C. Change the Apache Hadoop Project Chair (Vinod Kumar > > Vavilapalli, VP) > > D. Establish the Apache Traffic Control Project (David Neuman, VP) > > E. Change the Apache Giraph Project Chair (Dionysios Logothetis, VP) > > F. Change the Apache Camel Project Chair (Andrea Cosentino, VP) > > G. Change the Apache Incubator Project Chair (Justin Mclean, VP) > > > > The next board meeting will be on the 20th of June. > > > Hi all, > > Many thanks to Roman and Cos who convinced me to take this on, as well > as proposing me as an Apache Foundation member. > > Luckily, we have a great team of folks on Bigtop, who, I am sure will > make sure we have another successful year. > > Humbly, > > Peter > >
Settling in to the big chair :-)
Hello all, I just wanted thank everyone who has brought me on board to be the next chair. I'm hopeful I can meet up to the standards of our prior chairs. Given the project is healthy, active and IMO does not need any major changes, I do want to solicit some discussion on a couple of topics. 1. When do we want to think about the next release and a time frame. It would be nice to announce 1.3 before or at ApacheCon. Thoughts ? 2. We do have a Bigtop Group on LinkedIn. Please feel free to add yourself to the group. It is moderated, but that is to keep spammers away I'd love to see more visibility on social media. 3. Please chime in if there is anything else the PMC should be addressing. Cheers, Peter
Re: ASF Board Meeting Summary - May 16, 2018
On Wed, 16 May 2018 22:43:30 -0700 Roman Shaposhnikwrote: > Major congrats to Peter! Well deserved! > > Thanks, > Roman. > > > -- Forwarded message -- > From: Phil Steitz > Date: Wed, May 16, 2018 at 5:15 PM > Subject: ASF Board Meeting Summary - May 16, 2018 > To: committ...@apache.org > > > The May board meeting took place on the 16th. > > The April minutes were approved. > Minutes will be posted to > http://www.apache.org/foundation/records/minutes/ > > All of the received reports to the board were approved. > > The following resolutions were passed unanimously: > > A. Change the Apache MINA Project Chair (Guillaume Nodet, VP) > B. Change the Apache Bigtop Project Chair (Peter Linnell, VP) > C. Change the Apache Hadoop Project Chair (Vinod Kumar > Vavilapalli, VP) > D. Establish the Apache Traffic Control Project (David Neuman, VP) > E. Change the Apache Giraph Project Chair (Dionysios Logothetis, VP) > F. Change the Apache Camel Project Chair (Andrea Cosentino, VP) > G. Change the Apache Incubator Project Chair (Justin Mclean, VP) > > The next board meeting will be on the 20th of June. Hi all, Many thanks to Roman and Cos who convinced me to take this on, as well as proposing me as an Apache Foundation member. Luckily, we have a great team of folks on Bigtop, who, I am sure will make sure we have another successful year. Humbly, Peter
Re: Create multiarch docker images for bigtop-puppet/slaves
On 17 May 2018 at 13:21, Jun HEwrote: > Hi, guys, > > As bigtop has simplified the way to create docker images for distros, by > BIGTOP-2922, I'm thinking of multi-arch docker images support to ease > building/test/development. > > Multi-arch feature has been supported since 2017, you may check this link: > https://blog.docker.com/2017/11/multi-arch-all-the-things/ > In simple words, multi-arch is a virtual image which contains several > architecture dependent images. When user try to pull this virtual image > dockhub will send back the actual image based on the architecture he is > using. > > Use multi-arch will help: > * development: user don't have to issue different cmd to pull puppet/slaves > images, "docker pull bigtop/slaves:trunk-debian-9" is enough instead of > "docker > pull bigtop/slaves:trunk-debian-9-ppc64le" or "docker pull > bigtop/slaves:trunk-debian-9-aarch64" > * test: unified yaml file for same distro. refer example in > provisioner/docker/config_* > > So how do you think? :) Thanks Jun for initiating the thread. +1 this makes sense. Is there any reason why we have not consider for using multi-arch images ? If anybody explains advantage/disadvantage of using multi-arch docker image in bigtop, it will help us to understand in a better way. > > Regards, > > Jun
Re: Fwd: ASF Board Meeting Summary - May 16, 2018
God speed, Peter! -- Regards, Cos On May 17, 2018 8:43:30 AM GMT+03:00, Roman Shaposhnikwrote: >Major congrats to Peter! Well deserved! > >Thanks, >Roman. > > >-- Forwarded message -- >From: Phil Steitz >Date: Wed, May 16, 2018 at 5:15 PM >Subject: ASF Board Meeting Summary - May 16, 2018 >To: committ...@apache.org > > >The May board meeting took place on the 16th. > >The April minutes were approved. >Minutes will be posted to >http://www.apache.org/foundation/records/minutes/ > >All of the received reports to the board were approved. > >The following resolutions were passed unanimously: > > A. Change the Apache MINA Project Chair (Guillaume Nodet, VP) > B. Change the Apache Bigtop Project Chair (Peter Linnell, VP) > C. Change the Apache Hadoop Project Chair (Vinod Kumar >Vavilapalli, VP) > D. Establish the Apache Traffic Control Project (David Neuman, VP) > E. Change the Apache Giraph Project Chair (Dionysios Logothetis, VP) > F. Change the Apache Camel Project Chair (Andrea Cosentino, VP) > G. Change the Apache Incubator Project Chair (Justin Mclean, VP) > >The next board meeting will be on the 20th of June.
Create multiarch docker images for bigtop-puppet/slaves
Hi, guys, As bigtop has simplified the way to create docker images for distros, by BIGTOP-2922, I'm thinking of multi-arch docker images support to ease building/test/development. Multi-arch feature has been supported since 2017, you may check this link: https://blog.docker.com/2017/11/multi-arch-all-the-things/ In simple words, multi-arch is a virtual image which contains several architecture dependent images. When user try to pull this virtual image dockhub will send back the actual image based on the architecture he is using. Use multi-arch will help: * development: user don't have to issue different cmd to pull puppet/slaves images, "docker pull bigtop/slaves:trunk-debian-9" is enough instead of "docker pull bigtop/slaves:trunk-debian-9-ppc64le" or "docker pull bigtop/slaves:trunk-debian-9-aarch64" * test: unified yaml file for same distro. refer example in provisioner/docker/config_* So how do you think? :) Regards, Jun