Hi Evans, thanks for your post and contribution!
Digging into some of the problems is showing me that the problem is not only related to puppet rather to the packages itself. It is not absolutly clear to me what you meant by "removing" component: The puppet code related to that part of bigtop (for instance "hue" or remove both packaging and puppet deployment code ? I am ok to remove packages (both package and puppet) with no maintainer attached. We may need to have maintainers for platforms as well. To be more specific: For instance the breakage of zeppelin is due to a IMHO broken architecture of zeppelin itself. It runs maven and tries to download stuff from the internet a service start time. Sorry, I can only to propose to remove zeppelin altogether, since we cannot fix it. It looks like hue-packaging has gone havoc. Since I seem to be the only one who was interested in this in the past I am ok to remove "hue" altogether. If someone still likes to have it, I can look into this issue, it may not be that complicated to fix. Puppet Problems: kerberos on centos-7. I may look into this if I find time. zookeeper at ubuntu, but it seems you (Evans) are already working on it. Best, Olaf > Am 05.06.2017 um 06:32 schrieb Evans Ye <[email protected]>: > > Hi Bigtopers, > > I've shared this on my Apache Big Data talk, but haven't got a chance to > share with you yet. > This is a Jenkins matrix job to show the healthy status of our component > deployment code. > Each run deploys hdfs + Y on X, where X is the OS and Y is the component > shown on the matrix: > > https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-trunk-deployments/45/ > > Generally speaking, the status of our deployment code needs a lot of effort > to polish. > So, for 1.2.1 release, I think we should make some changes: > > 1). Remove unmaintained failing components > 2). Get maintained components fixed > > 1) might be easier to achieve, while 2) takes time. > In order to maintain a good code quality, I suggest proceed with 1). > > Any different thoughts?
signature.asc
Description: Message signed with OpenPGP
