Subnet Management - brlsh (Application)

Governance NNS proposal discussions
, ,
1

This topic is intended to capture Subnet Management activities over time for the brlsh subnet, providing a place to ask questions and make observations about the management of this subnet.

At the time of creating this topic the current subnet configuration is as follows:

Expand 
{
  "version": 44473,
  "records": [
    {
      "key": "subnet_record_brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae",
      "version": 44473,
      "value": {
        "membership": [
          "2eqbk-www2z-qcopx-wujey-4frhx-cpstt-4ecyv-7wh64-qozmi-wwkpe-yqe",
          "5hni3-coaib-iuz4m-dxyvz-7bntg-hnwji-rghvw-sjvtj-nd2rd-jgjsn-jae",
          "gsvxv-tou7p-drlxw-rnldp-m7z3n-e42j4-nrsp4-dzsfc-7wuqr-2qwpf-pae",
          "qhfut-l6rgw-kkbjn-iglum-tgn5d-pb36h-rlus5-f6uhu-fgv5g-5nqyc-nqe",
          "6gl2o-2v73n-q65pc-nf6tv-avcbc-hzjxh-urwbq-vurvj-wj5og-3xmnk-tqe",
          "qbij2-wkp76-ewolj-xsyp5-flevz-5kvx2-4hvgg-q23hh-43hbe-bxntn-xqe",
          "icbco-xw6zg-wlhyp-juqf4-h5gbs-jjein-nmc6n-itoxd-o52q7-q7fjz-gae",
          "vqrj7-n4xxl-qbgb2-uudxw-mvmkt-d4irw-7ln7t-2m6w7-4ryfz-6pfaq-3qe",
          "ciujb-q722m-zr3kt-st4jb-pgo3f-sosku-t33vy-x3pxa-3swy5-gecvn-qqe",
          "jx6y5-u55cq-nwk3i-niahw-ogiah-vy46i-vq4oa-b7azf-27wgi-v7hhr-sqe",
          "mxan5-53r72-hkqtz-u6rcw-p7ptu-tx5bk-z5a3z-phhfg-q44od-cbf4s-zqe",
          "dg24y-beztc-a5hb5-24juk-rpqdv-iehwu-2mvyw-vw2ap-eajzr-s7kpc-fae",
          "vwdbg-uwo2y-ta6p2-mxwi2-6oztv-hzh4t-ugx3m-dkbbh-mgx7f-ifrah-6ae"
        ],
        "nodes": {},
        "max_ingress_bytes_per_message": 2097152,
        "max_ingress_messages_per_block": 1000,
        "max_block_payload_size": 4194304,
        "unit_delay_millis": 1000,
        "initial_notary_delay_millis": 600,
        "replica_version_id": "2c0b76cfc7e596d5c4304cff5222a2619294c8c1",
        "dkg_interval_length": 499,
        "start_as_nns": false,
        "subnet_type": "application",
        "features": {
          "canister_sandboxing": false,
          "http_requests": true,
          "sev_enabled": false
        },
        "max_number_of_canisters": 120000,
        "ssh_readonly_access": [],
        "ssh_backup_access": [],
        "ecdsa_config": null,
        "chain_key_config": null
      }
    }
  ]
}
2

There’s an open proposal for changing subnet membership - https://dashboard.internetcomputer.org/proposal/131424. This information is presented below:

  • red marker represents a removed node
  • green marker represents an added node
  • highlighted patches represent the country a node sits within

image
image1416Ă—437 76.8 KB

Table
Country Data Center Owner Node Provider Node
--- Germany Munich (mu1) q.beyond Staking Facilities dg24y-beztc-a5hb5-24juk-rpqdv-iehwu-2mvyw-vw2ap-eajzr-s7kpc-fae
+++ India New Delhi 1 (nd1) Marvelous Web3 DC Zenith Code LLC nj7re-dvkal-yq25a-opp2g-5y3qy-3ena4-opd5j-22uir-eaakx-ljk7k-6ae
Belgium Antwerp (an1) Datacenter United Allusion mxan5-53r72-hkqtz-u6rcw-p7ptu-tx5bk-z5a3z-phhfg-q44od-cbf4s-zqe
Canada Fremont (fm1) Hurricane Electric Boolean Bit, LLC 6gl2o-2v73n-q65pc-nf6tv-avcbc-hzjxh-urwbq-vurvj-wj5og-3xmnk-tqe
Switzerland Zurich 5 (zh5) Green.ch Sygnum Bank ciujb-q722m-zr3kt-st4jb-pgo3f-sosku-t33vy-x3pxa-3swy5-gecvn-qqe
China HongKong 1 (hk1) Unicom Wancloud limited gsvxv-tou7p-drlxw-rnldp-m7z3n-e42j4-nrsp4-dzsfc-7wuqr-2qwpf-pae
Japan Tokyo 2 (ty2) Equinix Starbase vwdbg-uwo2y-ta6p2-mxwi2-6oztv-hzh4t-ugx3m-dkbbh-mgx7f-ifrah-6ae
Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners 5hni3-coaib-iuz4m-dxyvz-7bntg-hnwji-rghvw-sjvtj-nd2rd-jgjsn-jae
Latvia Riga 1 (rg1) DEAC MB Patrankos šūvis qhfut-l6rgw-kkbjn-iglum-tgn5d-pb36h-rlus5-f6uhu-fgv5g-5nqyc-nqe
Singapore Singapore 3 (sg3) Racks Central OneSixtyTwo Digital Capital vqrj7-n4xxl-qbgb2-uudxw-mvmkt-d4irw-7ln7t-2m6w7-4ryfz-6pfaq-3qe
Slovenia Ljubljana (lj1) Posita.si Fractal Labs AG jx6y5-u55cq-nwk3i-niahw-ogiah-vy46i-vq4oa-b7azf-27wgi-v7hhr-sqe
Sweden Stockholm 1 (sh1) Digital Realty DFINITY Operations SA qbij2-wkp76-ewolj-xsyp5-flevz-5kvx2-4hvgg-q23hh-43hbe-bxntn-xqe
United States of America (the) Atlanta 2 (at2) Datasite BLP22, LLC icbco-xw6zg-wlhyp-juqf4-h5gbs-jjein-nmc6n-itoxd-o52q7-q7fjz-gae
United States of America (the) Vancouver (bc1) Cyxtera Blockchain Development Labs 2eqbk-www2z-qcopx-wujey-4frhx-cpstt-4ecyv-7wh64-qozmi-wwkpe-yqe

The removed node is replaced with a node based in India. I’ve verified that this node is currently unassigned.

The proposal mentions that his change is needed due to the Munich (mu1) data centre being due for decommissioning. See here for more discussion and references.

3

DFINITY will submit a proposal today to reduce the notarization delay on the subnet, brlsh, similar to what has happened on other subnets in recent weeks (you can find all details in this forum thread ).

1 Like
4

Thanks @dsharifi! Looks good, and the URL link has been super useful for jumping from the proposal, to the forum, and then from the forum to the subnet dashboard :+1:

1 Like
5

This subnet is being made public by → Expanding the list of Public Subnets on the Internet Computer - Governance / NNS proposal discussions - Internet Computer Developer Forum (dfinity.org)

6

Voted to adopt proposal 134041, as the reasoning is sound and the proposal description matches the payload.

This proposal is intended to replace one node with another, in order to gain insights into the stability of nodes of the node operator of the new node, given that this node operator does not yet have nodes in any subnet. As seen in the proposal (which I verified using the DRE tool), the proposed change leaves the target topology parameters unchanged and within the requirements.

2 Likes
7

Proposal 134041

TLDR I’ve vote to adopt. The proposal summary appears to be accurate, and the change seems reasonable.

… a node operator 5njak currently does not have nodes in any subnet. To get insights into the stability of the nodes of this node operator, we propose to add one of the operator’s nodes to subnet brlsh

Claims made in the proposal summary :point_up: can be validated via the IC API. Reviewing the returned JSON shows that the node operator 5njak operates a single node, which is indeed currently unassigned.

An UP node in the US is removed and replaced with this new US 5njak node. Relevant decentralisation metrics are unaffected by this change.

Decentralisation Stats

Subnet node distance stats (distance between any 2 nodes in the subnet) →

Smallest Distance Average Distance Largest Distance
EXISTING 443.007 km 7099.094 km 15062.77 km
PROPOSED 443.007 km 7124.993 km (+0.4%) 15939.092 km (+5.8%)

This proposal slightly increases decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical increase in localised disaster resilience). :+1:

Subnet characteristic counts →

Continents Countries Data Centers Owners Node Providers Node Operator
EXISTING 3 12 13 13 13 13
PROPOSED 3 12 13 13 13 13

Largest number of nodes with the same characteristic (e.g. continent, country, data center, etc.) →

Continent Country Data Center Owner Node Provider Node Operator
EXISTING 5 2 1 1 1 1
PROPOSED 5 2 1 1 1 1

See here for acceptable limits → Motion 132136

The above subnet information is illustrated below, followed by a node reference table:

Map Description
  • Red marker represents a removed node (transparent center for overlap visibility)
  • Green marker represents an added node
  • Blue marker represents an unchanged node
  • Highlighted patches represent the country the above nodes sit within (red if the country is removed, green if added, otherwise grey)
  • Light grey markers with yellow borders are examples of unassigned nodes that would be viable candidates for joining the subnet according to formal decentralisation coefficients (so this proposal can be viewed in the context of alternative solutions that are not being used)

image
image1007Ă—427 79.1 KB

Table
Continent Country Data Center Owner Node Provider Node Operator Node Status Performance
--- Americas United States of America (the) Atlanta 2 (at2) Datasite BLP22, LLC 5syyj icbco-xw6zg-wlhyp-juqf4-h5gbs-jjein-nmc6n-itoxd-o52q7-q7fjz-gae UP :bar_chart:
+++ Americas United States of America (the) Atlanta (at1) Flexential Rachel Dymecki 5njak qjcai-zojq5-ec46h-5jj3m-wtih3-ytunz-2crlp-a23c7-hgrky-ymmx5-aqe UNASSIGNED :bar_chart:
Europe Belgium Antwerp (an1) Datacenter United Allusion pgunx mxan5-53r72-hkqtz-u6rcw-p7ptu-tx5bk-z5a3z-phhfg-q44od-cbf4s-zqe UP :bar_chart:
Americas Canada Fremont (fm1) Hurricane Electric Boolean Bit, LLC jjymt 6gl2o-2v73n-q65pc-nf6tv-avcbc-hzjxh-urwbq-vurvj-wj5og-3xmnk-tqe UP :bar_chart:
Americas Canada Vancouver (bc1) Cyxtera Blockchain Development Labs feb2q 2eqbk-www2z-qcopx-wujey-4frhx-cpstt-4ecyv-7wh64-qozmi-wwkpe-yqe UP :bar_chart:
Europe Switzerland Zurich 5 (zh5) Green.ch Sygnum Bank 4ohfd ciujb-q722m-zr3kt-st4jb-pgo3f-sosku-t33vy-x3pxa-3swy5-gecvn-qqe UP :bar_chart:
Asia China HongKong 1 (hk1) Unicom Wancloud limited z6cfb gsvxv-tou7p-drlxw-rnldp-m7z3n-e42j4-nrsp4-dzsfc-7wuqr-2qwpf-pae UP :bar_chart:
Asia India New Delhi 1 (nd1) Marvelous Web3 DC Zenith Code LLC ihcmc nj7re-dvkal-yq25a-opp2g-5y3qy-3ena4-opd5j-22uir-eaakx-ljk7k-6ae UP :bar_chart:
Asia Japan Tokyo 2 (ty2) Equinix Starbase dpt4y vwdbg-uwo2y-ta6p2-mxwi2-6oztv-hzh4t-ugx3m-dkbbh-mgx7f-ifrah-6ae UP :bar_chart:
Asia Korea (the Republic of) Seoul 1 (sl1) Megazone Cloud Neptune Partners ukji3 5hni3-coaib-iuz4m-dxyvz-7bntg-hnwji-rghvw-sjvtj-nd2rd-jgjsn-jae UP :bar_chart:
Europe Latvia Riga 1 (rg1) DEAC MB Patrankos šūvis jptla qhfut-l6rgw-kkbjn-iglum-tgn5d-pb36h-rlus5-f6uhu-fgv5g-5nqyc-nqe UP :bar_chart:
Asia Singapore Singapore 3 (sg3) Racks Central OneSixtyTwo Digital Capital 5mhxl vqrj7-n4xxl-qbgb2-uudxw-mvmkt-d4irw-7ln7t-2m6w7-4ryfz-6pfaq-3qe UP :bar_chart:
Europe Slovenia Ljubljana (lj1) Posita.si Fractal Labs AG gl27f jx6y5-u55cq-nwk3i-niahw-ogiah-vy46i-vq4oa-b7azf-27wgi-v7hhr-sqe UP :bar_chart:
Europe Sweden Stockholm 1 (sh1) Digital Realty DFINITY Operations SA lgp6d qbij2-wkp76-ewolj-xsyp5-flevz-5kvx2-4hvgg-q23hh-43hbe-bxntn-xqe UP :bar_chart:
Known Neurons to follow if you're too busy to keep on top of things like this

If you found this analysis helpful and would like to follow the vote of the LORIMER known neuron in the future, consider configuring LORIMER as a followee for the Subnet Management topic.

Another good neuron to follow is Synapse (follows the LORIMER and CodeGov known neurons for Subnet Management, and is a generally well informed known neuron to follow on numerous other topics)

1 Like
8

Voted to adopt proposal 134041. The proposal replaces one node from subnet brlsh:
Removed Node: icbco, Added Node: qjcai.
The proposal was verified using the DRE tool to verify the metrics stated and there was no impact on decentralization. The motivation behind this proposal is to get insights into the stability of the nodes under the node operator 5njak. Using the ic-admin tool as follows:

image
image1265Ă—177 28.2 KB

I was able to verify the node_provider_principal_id, chnsu, which matches with the one from the proposal and currently has only the node added under it’s control.

1 Like
9

Voted to adopt proposal #134041.

The proposal makes sense in that it replaces one healthy node from Atlanta 2, US icbco , with Atlanta, US node poyg5 while not afecting decentralization in order “To get insights into the stability of the nodes of this node operator”. brlsh has a State of 61.19 GiB with 32,510 Canisters so it should be a good choice.