reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chenxi Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-2021) In AzureBatch Runtime, Enable REEF .NET Client Communication to Driver
Date Tue, 29 May 2018 18:46:00 GMT

    [ https://issues.apache.org/jira/browse/REEF-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494046#comment-16494046
] 

Chenxi Zhao commented on REEF-2021:
-----------------------------------

Decided to use Azure Batch InBoundNATPool feature [https://docs.microsoft.com/en-us/rest/api/batchservice/pool/add#inboundnatpool]
to enable the communication rather than using Azure Storage Queue to forward the request.

 

PR: https://github.com/apache/reef/pull/1468

 

> In AzureBatch Runtime, Enable REEF .NET Client Communication to Driver
> ----------------------------------------------------------------------
>
>                 Key: REEF-2021
>                 URL: https://issues.apache.org/jira/browse/REEF-2021
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET Client, REEF.NET Driver
>            Reporter: Chenxi Zhao
>            Assignee: Chenxi Zhao
>            Priority: Major
>
> After user submits task to Azure Batch runtime, client is not able to communicate REEF
HTTP server hosted on Driver, due to network configuration. We want to save the pain for user
of setting up VNET in Azure Batch Pool to enable the connection.
>  
> We will provide this capability by a HTTP connection proxy, which exchanges HTTP request
through Azure Storage Queue.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message