dotnet/orleans

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

Open

#7,023 opened on 2021年3月11日

GitHub で見る
 (1 comment) (4 reactions) (1 assignee)C# (10,777 stars) (2,123 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.