Skip to content
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

Feat: Migrate Infra from Pagoda to Sig Network #918

Merged
merged 6 commits into from
Nov 6, 2024
Merged

Conversation

auto-mausx
Copy link
Collaborator

No description provided.

@auto-mausx auto-mausx requested review from volovyks and ppca November 4, 2024 23:18
@auto-mausx auto-mausx self-assigned this Nov 4, 2024
ppca
ppca previously approved these changes Nov 4, 2024
Copy link
Contributor

@ppca ppca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm except a couple comments

chain-signatures/contract/src/lib.rs Outdated Show resolved Hide resolved
@@ -11,7 +11,7 @@ resource "google_cloud_run_v2_service" "leader" {

vpc_access {
connector = var.connector_id
egress = "PRIVATE_RANGES_ONLY"
egress = "ALL_TRAFFIC"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we still want this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, since we want all traffic to leave our VPC.

@@ -13,7 +13,7 @@ resource "google_cloud_run_v2_service" "signer" {
for_each = var.connector_id == null ? [] : [1]
content {
connector = var.connector_id == null ? null : var.connector_id
egress = "PRIVATE_RANGES_ONLY"
egress = "ALL_TRAFFIC"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also yes since technically signers are available publicly for our leader node.

infra/mpc-recovery-prod/main.tf Outdated Show resolved Hide resolved
infra/mpc-recovery-testnet/main.tf Outdated Show resolved Hide resolved
scopes = ["cloud-platform"]
}
name_prefix = "multichain-${count.index}"
source_image_family = "cos-113-lts"
source_image_project = "cos-cloud"
machine_type = "n2-standard-2"
machine_type = "e2-medium"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this cheaper now compared with n2-standard-2?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considerably yes, we could probably do even cheaper.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think this is the reason, but our dev network is slower now. Let's keep the hardware in mind.

@auto-mausx auto-mausx merged commit 2cb54bc into develop Nov 6, 2024
@auto-mausx auto-mausx deleted the sig-migration branch November 6, 2024 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants