Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7780B200CC6 for ; Tue, 18 Jul 2017 19:23:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 761B216739E; Tue, 18 Jul 2017 17:23:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id BDC6616739B for ; Tue, 18 Jul 2017 19:23:03 +0200 (CEST) Received: (qmail 41974 invoked by uid 500); 18 Jul 2017 17:23:02 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 41962 invoked by uid 99); 18 Jul 2017 17:23:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jul 2017 17:23:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 84D5E1805AD for ; Tue, 18 Jul 2017 17:23:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 3r56fvBqdTKF for ; Tue, 18 Jul 2017 17:23:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 191885F6C8 for ; Tue, 18 Jul 2017 17:23:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 58E8DE07EA for ; Tue, 18 Jul 2017 17:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 175B221E95 for ; Tue, 18 Jul 2017 17:23:00 +0000 (UTC) Date: Tue, 18 Jul 2017 17:23:00 +0000 (UTC) From: "Jie Yu (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MESOS-7749) Support gRPC client MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Jul 2017 17:23:04 -0000 [ https://issues.apache.org/jira/browse/MESOS-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-7749: -------------------------- Description: CSI support requires gRPC client integration in Mesos. This epic captures the work that needs to be done for supporting that. 1. Bundle GRPC - CMake build system under Linux. - Setting up autotools under Linux. - Setting up CMake build system under Windows. - Testing on other supported OSes, e.g., macOS. 2. Build a GRPC client API in libprocess This should be a wrapper over the grpc client that integrate with libprocess's event loop so that caller will be much easier to consume. was: The CSI components in Mesos depends on gRPC, and we might also want to have APIs implemented in the future. Bundling tasks in gRPC includes the following tasks: 1. CMake build system under Linux. 2. Setting up autotools under Linux. 3. Setting up CMake build system under Windows. 4. Testing on other supported OSes, e.g., macOS. > Support gRPC client > ------------------- > > Key: MESOS-7749 > URL: https://issues.apache.org/jira/browse/MESOS-7749 > Project: Mesos > Issue Type: Epic > Components: build > Reporter: Chun-Hung Hsiao > Assignee: Chun-Hung Hsiao > Labels: build, features, storage > > CSI support requires gRPC client integration in Mesos. This epic captures the work that needs to be done for supporting that. > 1. Bundle GRPC > - CMake build system under Linux. > - Setting up autotools under Linux. > - Setting up CMake build system under Windows. > - Testing on other supported OSes, e.g., macOS. > 2. Build a GRPC client API in libprocess > This should be a wrapper over the grpc client that integrate with libprocess's event loop so that caller will be much easier to consume. -- This message was sent by Atlassian JIRA (v6.4.14#64029)