-
Notifications
You must be signed in to change notification settings - Fork 83
[1/n] [sled-agent] split early networking into its own crate #10448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| [package] | ||
| name = "sled-agent-early-networking" | ||
| version = "0.1.0" | ||
| edition.workspace = true | ||
| license = "MPL-2.0" | ||
|
|
||
| [lints] | ||
| workspace = true | ||
|
|
||
| [dependencies] | ||
| anyhow.workspace = true | ||
| # XXX NOTE this is due to https://github.com/oxidecomputer/omicron/issues/9704 | ||
| # This is the R17 dpd client | ||
| # dpd-client.workspace = true | ||
| dpd-client = { git = "https://github.com/oxidecomputer/dendrite", rev = "cc8e02a0800034c431c8cf96b889ea638da3d194" } | ||
| futures.workspace = true | ||
| gateway-client.workspace = true | ||
| http.workspace = true | ||
| internal-dns-resolver.workspace = true | ||
| internal-dns-types.workspace = true | ||
| mg-admin-client.workspace = true | ||
| omicron-common.workspace = true | ||
| omicron-ddm-admin-client.workspace = true | ||
| omicron-workspace-hack.workspace = true | ||
| oxnet.workspace = true | ||
| rdb-types.workspace = true | ||
| sled-agent-types.workspace = true | ||
| slog.workspace = true | ||
| slog-error-chain.workspace = true | ||
| thiserror.workspace = true | ||
| tokio = { workspace = true, features = ["full"] } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -67,7 +67,6 @@ | |
| //! after a clean slate upon failure. | ||
| //! See <https://github.com/oxidecomputer/omicron/issues/7174> for details. | ||
|
|
||
| use crate::early_networking::EarlyNetworkSetupError; | ||
| use crate::plan::service::PlanError as ServicePlanError; | ||
| use crate::plan::service::ServicePlan; | ||
| use crate::plan::sled::SledPlan; | ||
|
|
@@ -265,11 +264,6 @@ pub enum SetupServiceError { | |
| #[error("Failed to construct valid set of service zone NAT entries")] | ||
| InvalidServiceZoneNatEntries(#[from] ServiceZoneNatEntriesError), | ||
|
|
||
| // We used transparent, because `EarlyNetworkSetupError` contains a subset | ||
| // of error variants already in this type | ||
| #[error(transparent)] | ||
| EarlyNetworkSetup(#[from] EarlyNetworkSetupError), | ||
|
Comment on lines
-268
to
-271
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe #10370 made this unused, meaning that the RSS crate no longer depends on the early networking crate.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh! I didn't realize that was the only RSS use; that's great. Should we move
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Mild preference for just leaving it separate. |
||
|
|
||
| #[error("Rack already initialized")] | ||
| RackAlreadyInitialized, | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still the status quo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically yes. I think we could bump it up to the R18 dpd client, now that R19 is shipping? But I don't know that there's a need to do that and test it.