dotnet/orleans

Avoid opening any ports for single instance ASP.NET Core co-hosted apps

Open

#7,023 建立於 2021年3月11日

在 GitHub 查看
 (1 留言) (4 反應) (1 負責人)C# (10,777 star) (2,123 fork)batch import
help wanted

描述

Company I work for has created many small apps using Orleans. All of them have had ASP.NET Core and Orleans running in same app and we have run them in same IIS. So they are all single instance apps. Currently there is no way to tell Orleans not to open any ports. I think currently Orleans opens ports 11111 and 30000. So what I'm asking is making Orleans little bit nicer for single instance setups by adding way to opt out from any distributed features.

PS @ReubenBond responded in Gitter that I should write issue about this.

貢獻者指南

技術棧
csharp
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic knowledge of Orleansfamiliarity with ASP.NET Core co hosting
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate the current port configuration in Orleans, specifically how ports 11111 and 30000 are opened. Look into the SiloOptions class and the startup process for co hosted ASP.NET Core apps. The goal is to add a configuration option (e.g., 'DisableDistributedFeatures' or 'NoPorts') that prevents port binding. Reference the Gitter conversation with @ReubenBond for additional context. Ensure the implementation does not break existing functionality for multi instance deployments.