Re: 1.5.0 release update and concern about ppc64le
Thanks again, Jun! Kengo Seki On Fri, Nov 27, 2020 at 6:48 PM Jun HE wrote: > > Hi Kengo, > > It's back online now. Sorry for any inconvenience. > > Regards, > > Jun > > Jun HE 于2020年11月27日周五 下午1:45写道： > > > Hi Kengo, > > > > Let me have a look and get back to you then. > > > > Regards, > > > > Jun > > > > Kengo Seki 于2020年11月27日周五 下午12:49写道： > > > >> We should do so for now unfortunately. Once the PPC server is back, > >> I'm going to proceed the release process for ppc ASAP. > >> BTW, docker-slave-arm-5 is required to build packages for ARM but > >> seems to be down. Would you take a look, Jun and Yuqi? > >> > >> Kengo Seki > >> > >> > >> On Fri, Nov 27, 2020 at 10:03 AM Evans Ye wrote: > >> > > >> > Hi Kengo, > >> > > >> > Seems that there's no response from IBM. I guess we can only move on w/o > >> > PPC supported in 1.5. What do you say? > >> > > >> > Evans > >> > > >> > Evans Ye 於 2020年11月17日 週二 下午12:15寫道： > >> > > >> > > Let's wait for 2~3 days to see whether IBM guys respond. > >> > > If no, unfortunately we can only release w/o PPC supported. > >> > > > >> > > Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： > >> > > > >> > >> We've finally resolved all issues for the 1.5.0 release [1]. > >> > >> For a few components (e.g., Kibana (BIGTOP-3428), and maybe also > >> > >> Livy), their smoke tests didn't succeed with all platforms/distros on > >> > >> CI yet, but we confirmed that they worked on our local environment. > >> > >> So I think they are caused by a CI-specific environmental problem and > >> > >> not blockers for this release. > >> > >> > >> > >> I'm going to do the following items this week. > >> > >> > >> > >> * Recreate CI worker nodes following Evans' advice (thanks a lot!), > >> > >> because some hosts are frequently running short of disk capacity and > >> > >> going down. It makes the build unstable. > >> > >> * Run the packaging and deployment/smoke test CI jobs, and ensure the > >> > >> current status is as listed in [2]. > >> > >> * Then continue the release process from step 3 in the "How to > >> > >> release" document [3], and hopefully cut a release candidate within > >> > >> this week. > >> > >> > >> > >> My concern is about the ppc64le platform, because I can't build > >> > >> packages without that CI server. > >> > >> Is there any response from the IBM management, Amir? And if it seems > >> > >> difficult to get it back in the near future, is it OK that we publish > >> > >> this release without ppc64le (and do it later once the server comes > >> > >> back in the future)? > >> > >> > >> > >> [1]: > >> > >> > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 > >> > >> [2]: > >> > >> > >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 > >> > >> [3]: > >> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > >> > >> > >> > >> Kengo Seki > >> > >> > >> > > > >> > >
Re: 1.5.0 release update and concern about ppc64le
Hi Kengo, It's back online now. Sorry for any inconvenience. Regards, Jun Jun HE 于2020年11月27日周五 下午1:45写道： > Hi Kengo, > > Let me have a look and get back to you then. > > Regards, > > Jun > > Kengo Seki 于2020年11月27日周五 下午12:49写道： > >> We should do so for now unfortunately. Once the PPC server is back, >> I'm going to proceed the release process for ppc ASAP. >> BTW, docker-slave-arm-5 is required to build packages for ARM but >> seems to be down. Would you take a look, Jun and Yuqi? >> >> Kengo Seki >> >> >> On Fri, Nov 27, 2020 at 10:03 AM Evans Ye wrote: >> > >> > Hi Kengo, >> > >> > Seems that there's no response from IBM. I guess we can only move on w/o >> > PPC supported in 1.5. What do you say? >> > >> > Evans >> > >> > Evans Ye 於 2020年11月17日 週二 下午12:15寫道： >> > >> > > Let's wait for 2~3 days to see whether IBM guys respond. >> > > If no, unfortunately we can only release w/o PPC supported. >> > > >> > > Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： >> > > >> > >> We've finally resolved all issues for the 1.5.0 release [1]. >> > >> For a few components (e.g., Kibana (BIGTOP-3428), and maybe also >> > >> Livy), their smoke tests didn't succeed with all platforms/distros on >> > >> CI yet, but we confirmed that they worked on our local environment. >> > >> So I think they are caused by a CI-specific environmental problem and >> > >> not blockers for this release. >> > >> >> > >> I'm going to do the following items this week. >> > >> >> > >> * Recreate CI worker nodes following Evans' advice (thanks a lot!), >> > >> because some hosts are frequently running short of disk capacity and >> > >> going down. It makes the build unstable. >> > >> * Run the packaging and deployment/smoke test CI jobs, and ensure the >> > >> current status is as listed in [2]. >> > >> * Then continue the release process from step 3 in the "How to >> > >> release" document [3], and hopefully cut a release candidate within >> > >> this week. >> > >> >> > >> My concern is about the ppc64le platform, because I can't build >> > >> packages without that CI server. >> > >> Is there any response from the IBM management, Amir? And if it seems >> > >> difficult to get it back in the near future, is it OK that we publish >> > >> this release without ppc64le (and do it later once the server comes >> > >> back in the future)? >> > >> >> > >> [1]: >> > >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 >> > >> [2]: >> > >> >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 >> > >> [3]: >> https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release >> > >> >> > >> Kengo Seki >> > >> >> > > >> >
Re: 1.5.0 release update and concern about ppc64le
Hi Kengo, Let me have a look and get back to you then. Regards, Jun Kengo Seki 于2020年11月27日周五 下午12:49写道： > We should do so for now unfortunately. Once the PPC server is back, > I'm going to proceed the release process for ppc ASAP. > BTW, docker-slave-arm-5 is required to build packages for ARM but > seems to be down. Would you take a look, Jun and Yuqi? > > Kengo Seki > > > On Fri, Nov 27, 2020 at 10:03 AM Evans Ye wrote: > > > > Hi Kengo, > > > > Seems that there's no response from IBM. I guess we can only move on w/o > > PPC supported in 1.5. What do you say? > > > > Evans > > > > Evans Ye 於 2020年11月17日 週二 下午12:15寫道： > > > > > Let's wait for 2~3 days to see whether IBM guys respond. > > > If no, unfortunately we can only release w/o PPC supported. > > > > > > Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： > > > > > >> We've finally resolved all issues for the 1.5.0 release [1]. > > >> For a few components (e.g., Kibana (BIGTOP-3428), and maybe also > > >> Livy), their smoke tests didn't succeed with all platforms/distros on > > >> CI yet, but we confirmed that they worked on our local environment. > > >> So I think they are caused by a CI-specific environmental problem and > > >> not blockers for this release. > > >> > > >> I'm going to do the following items this week. > > >> > > >> * Recreate CI worker nodes following Evans' advice (thanks a lot!), > > >> because some hosts are frequently running short of disk capacity and > > >> going down. It makes the build unstable. > > >> * Run the packaging and deployment/smoke test CI jobs, and ensure the > > >> current status is as listed in [2]. > > >> * Then continue the release process from step 3 in the "How to > > >> release" document [3], and hopefully cut a release candidate within > > >> this week. > > >> > > >> My concern is about the ppc64le platform, because I can't build > > >> packages without that CI server. > > >> Is there any response from the IBM management, Amir? And if it seems > > >> difficult to get it back in the near future, is it OK that we publish > > >> this release without ppc64le (and do it later once the server comes > > >> back in the future)? > > >> > > >> [1]: > > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 > > >> [2]: > > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 > > >> [3]: > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > > >> > > >> Kengo Seki > > >> > > > >
Re: 1.5.0 release update and concern about ppc64le
We should do so for now unfortunately. Once the PPC server is back, I'm going to proceed the release process for ppc ASAP. BTW, docker-slave-arm-5 is required to build packages for ARM but seems to be down. Would you take a look, Jun and Yuqi? Kengo Seki On Fri, Nov 27, 2020 at 10:03 AM Evans Ye wrote: > > Hi Kengo, > > Seems that there's no response from IBM. I guess we can only move on w/o > PPC supported in 1.5. What do you say? > > Evans > > Evans Ye 於 2020年11月17日 週二 下午12:15寫道： > > > Let's wait for 2~3 days to see whether IBM guys respond. > > If no, unfortunately we can only release w/o PPC supported. > > > > Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： > > > >> We've finally resolved all issues for the 1.5.0 release [1]. > >> For a few components (e.g., Kibana (BIGTOP-3428), and maybe also > >> Livy), their smoke tests didn't succeed with all platforms/distros on > >> CI yet, but we confirmed that they worked on our local environment. > >> So I think they are caused by a CI-specific environmental problem and > >> not blockers for this release. > >> > >> I'm going to do the following items this week. > >> > >> * Recreate CI worker nodes following Evans' advice (thanks a lot!), > >> because some hosts are frequently running short of disk capacity and > >> going down. It makes the build unstable. > >> * Run the packaging and deployment/smoke test CI jobs, and ensure the > >> current status is as listed in [2]. > >> * Then continue the release process from step 3 in the "How to > >> release" document [3], and hopefully cut a release candidate within > >> this week. > >> > >> My concern is about the ppc64le platform, because I can't build > >> packages without that CI server. > >> Is there any response from the IBM management, Amir? And if it seems > >> difficult to get it back in the near future, is it OK that we publish > >> this release without ppc64le (and do it later once the server comes > >> back in the future)? > >> > >> [1]: > >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 > >> [2]: > >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 > >> [3]: https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > >> > >> Kengo Seki > >> > >
Re: 1.5.0 release update and concern about ppc64le
Hi Kengo, Seems that there's no response from IBM. I guess we can only move on w/o PPC supported in 1.5. What do you say? Evans Evans Ye 於 2020年11月17日 週二 下午12:15寫道： > Let's wait for 2~3 days to see whether IBM guys respond. > If no, unfortunately we can only release w/o PPC supported. > > Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： > >> We've finally resolved all issues for the 1.5.0 release [1]. >> For a few components (e.g., Kibana (BIGTOP-3428), and maybe also >> Livy), their smoke tests didn't succeed with all platforms/distros on >> CI yet, but we confirmed that they worked on our local environment. >> So I think they are caused by a CI-specific environmental problem and >> not blockers for this release. >> >> I'm going to do the following items this week. >> >> * Recreate CI worker nodes following Evans' advice (thanks a lot!), >> because some hosts are frequently running short of disk capacity and >> going down. It makes the build unstable. >> * Run the packaging and deployment/smoke test CI jobs, and ensure the >> current status is as listed in [2]. >> * Then continue the release process from step 3 in the "How to >> release" document [3], and hopefully cut a release candidate within >> this week. >> >> My concern is about the ppc64le platform, because I can't build >> packages without that CI server. >> Is there any response from the IBM management, Amir? And if it seems >> difficult to get it back in the near future, is it OK that we publish >> this release without ppc64le (and do it later once the server comes >> back in the future)? >> >> [1]: >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 >> [2]: >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 >> [3]: https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release >> >> Kengo Seki >> >
Re: 1.5.0 release update and concern about ppc64le
Let's wait for 2~3 days to see whether IBM guys respond. If no, unfortunately we can only release w/o PPC supported. Kengo Seki 於 2020年11月17日 週二 上午7:49寫道： > We've finally resolved all issues for the 1.5.0 release [1]. > For a few components (e.g., Kibana (BIGTOP-3428), and maybe also > Livy), their smoke tests didn't succeed with all platforms/distros on > CI yet, but we confirmed that they worked on our local environment. > So I think they are caused by a CI-specific environmental problem and > not blockers for this release. > > I'm going to do the following items this week. > > * Recreate CI worker nodes following Evans' advice (thanks a lot!), > because some hosts are frequently running short of disk capacity and > going down. It makes the build unstable. > * Run the packaging and deployment/smoke test CI jobs, and ensure the > current status is as listed in [2]. > * Then continue the release process from step 3 in the "How to > release" document [3], and hopefully cut a release candidate within > this week. > > My concern is about the ppc64le platform, because I can't build > packages without that CI server. > Is there any response from the IBM management, Amir? And if it seems > difficult to get it back in the near future, is it OK that we publish > this release without ppc64le (and do it later once the server comes > back in the future)? > > [1]: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 > [2]: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 > [3]: https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > > Kengo Seki >
1.5.0 release update and concern about ppc64le
We've finally resolved all issues for the 1.5.0 release [1]. For a few components (e.g., Kibana (BIGTOP-3428), and maybe also Livy), their smoke tests didn't succeed with all platforms/distros on CI yet, but we confirmed that they worked on our local environment. So I think they are caused by a CI-specific environmental problem and not blockers for this release. I'm going to do the following items this week. * Recreate CI worker nodes following Evans' advice (thanks a lot!), because some hosts are frequently running short of disk capacity and going down. It makes the build unstable. * Run the packaging and deployment/smoke test CI jobs, and ensure the current status is as listed in [2]. * Then continue the release process from step 3 in the "How to release" document [3], and hopefully cut a release candidate within this week. My concern is about the ppc64le platform, because I can't build packages without that CI server. Is there any response from the IBM management, Amir? And if it seems difficult to get it back in the near future, is it OK that we publish this release without ppc64le (and do it later once the server comes back in the future)? [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BIGTOP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.5.0 [2]: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165225375 [3]: https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release Kengo Seki
