reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (REEF-2021) In AzureBatch Runtime, Enable REEF .NET Client Communication to Driver
Date Mon, 04 Jun 2018 21:45:00 GMT


ASF GitHub Bot commented on REEF-2021:

homezcx commented on a change in pull request #1468: [REEF-2021]In AzureBatch Runtime, Enable
REEF .NET Client Communication to Driver

 File path: lang/cs/Org.Apache.REEF.Client/AzureBatch/AzureBatchDotNetClient.cs
 @@ -45,6 +47,12 @@ public sealed class AzureBatchDotNetClient : IREEFClient
         private readonly AzureBatchService _batchService;
         private readonly JobJarMaker _jobJarMaker;
         private readonly AzureBatchFileNames _azbatchFileNames;
+        private readonly string _azureBatchAccountName;
 Review comment:
   Definitely we can. I am kind not sure which one is better practice. Having a wrapper only
contains getters with no logic, or just like this. Since we are using injection here, no pain
to call new Instance(param1, param2, .....)
   Let's wait for another vote maybe?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> In AzureBatch Runtime, Enable REEF .NET Client Communication to Driver
> ----------------------------------------------------------------------
>                 Key: REEF-2021
>                 URL:
>             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

View raw message