add support libvirt as provider. KAFKA-2183#62
Conversation
There was a problem hiding this comment.
These all appear to be spacing changes, can we clear these out of the diff?
|
should i squash commits right now ? |
|
Not sure about squashing commits, using Github PRs is new for Kafka. I think that happens as part of the commit process, which is not managed through Github. You'll need a committer to approve this anyway, I'm just reviewing since I helped with the Vagrantfile previously. I think @nehanarkhede was shepherding the new Github PR approach and might know the process better. |
|
any news ? |
|
The proposed documentation for the GitHub-based process (it's not official yet): https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes Regarding squashing of commits, it depends on whether it's useful to have separate commits or not (i.e. does each commit represent a self-contained change that makes sense on its own, compiles and passes the tests?). The merge script will squash the commits into one, but it will also include a reference to each individual commit. As such, commits that don't add any value should be squashed before the merge step. |
80ef4b0 to
8f59a82
Compare
|
squashed |
|
kafka-trunk-git-pr #215 FAILURE |
|
This updated version looks good to me, but I don't have a linux box handy to test on and don't think I have anything to test on that would support nested virtualization. |
|
It is mainly for avoid virtualbox on linux. And libvirt supported on macos
|
Pull latest commits from apache trunk to merge in streaming.
There was a problem hiding this comment.
I noticed the shebang line is in the wrong place, both here and in the other scripts in vagrant/. Wouldn't hurt to clean that up in this patch even though it wasn't introduced here. It looks like we're currently relying on bash being the default shell in the VMs because of this error.
|
@pronix Sorry for the slow follow up. I was never able to test this with libvirt on OS X. I think the vagrant-libvirt plugin doesn't support the vbox support in libvirt, so it's not easy to test there -- only on platforms where qemu or kvm are usable. I have a Linux box handy now that I can test on. The current patch had a few minor problems under that environment (Ubuntu trusty box with KVM, Vagrant 1.7.4). But once I cleaned up the bash scripts under |
[LOGBROKER-1780] NoSuchElementException fixed
|
@pronix Could you reply Ewen's comments so we can proceed the review process? |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
I'd like to help with this issue. I've test @pronix branch and looks like the box his referencing (http://citozin.com/fedora21.box) is not available. I would recommend to use a box that is already hosted in Atlas (Official Vagrant Box registry) https://atlas.hashicorp.com/ I've tested with this box: https://atlas.hashicorp.com/yk0/boxes/ubuntu-xenial. With this box we don't need to have scripts fedora and ubuntu distributions. Take a look to this commit: jeqo@ff2f58d |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
cc @ewencp |
|
@jeqo Is there an official ubuntu box that we can reference? It doesn't seem great to have references to individual user vagrant boxes rather than an official project image. |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
@ewencp yes, I agree but I cannot find any official Ubuntu image in Vagrant Atlas. I give a try to |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
…pache#62) TICKET = LI_DESCRIPTION = SslTransportLayer takes netBuffer/appBuffer full as buffer overflow and close the connection unnecessarily. EXIT_CRITERIA = MANUAL [""]
|
Hi @pronix , It seems like this PR stalled. I'll close it out for now, but if you or anyone else want to resume this work, please feel free to re-open it (or start a new one)! Thanks, |
…pache#62) TICKET = LI_DESCRIPTION = SslTransportLayer takes netBuffer/appBuffer full as buffer overflow and close the connection unnecessarily. EXIT_CRITERIA = MANUAL [""]
* [LI-HOTFIX] Add support to use BoringSSL for SSL/TLS. TICKET = KAFKA-2561 LI_DESCRIPTION = Make Kafka capable of using BoringSSL for encryption. EXIT_CRITERIA = TICKET [KAFKA-2561] * Removed unused imports * [LI-HOTFIX] Fix SSL channel close on fake buffer overflow/underflow (apache#62) TICKET = LI_DESCRIPTION = SslTransportLayer takes netBuffer/appBuffer full as buffer overflow and close the connection unnecessarily. EXIT_CRITERIA = MANUAL [""] * Fix failing unit tests. Co-authored-by: kun du <kdu@linkedin.com>
Cherry picked commit: * [LI-HOTFIX] Add support to use BoringSSL for SSL/TLS. TICKET = KAFKA-2561 LI_DESCRIPTION = Make Kafka capable of using BoringSSL for encryption. EXIT_CRITERIA = TICKET [KAFKA-2561] * Removed unused imports * [LI-HOTFIX] Fix SSL channel close on fake buffer overflow/underflow (apache#62) TICKET = LI_DESCRIPTION = SslTransportLayer takes netBuffer/appBuffer full as buffer overflow and close the connection unnecessarily. EXIT_CRITERIA = MANUAL [""] * Fix failing unit tests. Co-authored-by: kun du <kdu@linkedin.com>
Cherry picked commit: * [LI-HOTFIX] Add support to use BoringSSL for SSL/TLS. TICKET = KAFKA-2561 LI_DESCRIPTION = Make Kafka capable of using BoringSSL for encryption. EXIT_CRITERIA = TICKET [KAFKA-2561] * Removed unused imports * [LI-HOTFIX] Fix SSL channel close on fake buffer overflow/underflow (apache#62) TICKET = LI_DESCRIPTION = SslTransportLayer takes netBuffer/appBuffer full as buffer overflow and close the connection unnecessarily. EXIT_CRITERIA = MANUAL [""] * Fix failing unit tests. Co-authored-by: kun du <kdu@linkedin.com>
…apache#62) 0. Address comments from P1. 1. Add the DefaultTaskExecutor implementation class. 2. Related DefaultTaskExecutorTest. Pending in future PRs: a) exception handling, primarily to send them to polling thread, b) light-weight task flushing procedure. Co-authored-by: Guozhang Wang <wangguoz@gmail.com>
add state machine
…apache#3) Remediates 3 MINOR QA findings — all broken anchor fragments in docs/security-audit/findings/07-external-function-callback-misuse.md. The previous anchor fragments used MkDocs-style semantic IDs that do not resolve against GitHub-flavored markdown auto-generated heading slugs. This commit aligns each fragment to the GitHub-computed slug for the target heading. Fixes: * Line 197: #oauth -> apache#32-security--oauth Target: ### 3.2 Security - OAuth (accepted-mitigations.md:201) (double-hyphen comes from the two spaces around the em-dash; the em-dash itself is stripped by the GitHub slug algorithm) * Line 227: #oauth -> apache#32-security--oauth (both visible text and URL) Target: same as Line 197 (second occurrence in the 'Cross-References' section) * Line 232: apache#62-restclient-forwarding -> apache#42-connect-restclient- forwards-the-inbound-authorization-header-to-outbound-worker- peer-calls-062 Target: ### 4.2 Connect RestClient forwards the inbound Authorization header to outbound worker-peer calls (06.2) (findings/06-network-subprocess-access.md:90) (URL fragment updated; visible short identifier retained for readability per QA suggested-fix guidance) Validation: * Runtime re-verification: all 88 anchor-bearing links across the 24 audit markdown files now resolve (0 broken anchors). * File inventory unchanged: 25 files, surgical 6-line diff (3 insertions, 3 deletions). * Visual Architecture Documentation rule preserved: all 7 diagrams still referenced by name across findings and supporting docs. * Audit Only rule preserved: zero source-code modifications; only the audit deliverable under docs/security-audit/ is touched. QA report: QA Final Checkpoint apache#3 - Link Integrity + Cross-References + License Headers (Issues 1-3, all MINOR, all in findings/07).
https://issues.apache.org/jira/browse/KAFKA-2183