Voted to adopt proposal 133148. Replaces one dead node and another degraded node without changing the Nakamoto Coefficient.
DFINITY will submit an NNS proposal today to reduce the notarization delay on the NNS subnet, tdb26, similar to what has happened on other subnets in recent weeks (you can find all details in this forum thread ).
The NNS subnet is the last subnet left as part of the latency milestone to reduce its notarisation delay.
3 Likes
Voted to adopt proposal 133903, as the reasoning is sound and the payload matches the description. This proposal reduces the notarisation delay for subnet tdb26 from 1000ms to 300ms in order to improve network latency, in keeping with a similar change that has now been made to all of the other subnets.
2 Likes
Adopted proposal 133903 since the subnet id and the notarization delay value is correct in the payload and it matches the proposal summary.
2 Likes
Proposal 133903
This proposal sets the notarisation delay of the tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe subnet to 300ms, down from 1000ms. The change will increase the block rate of the subnet, aimed to reduce latency of update calls.
The proposal summary is consistent with the subnet configuration payload. This proposal has been expected, and conforms to the pattern of all of the other notarisation delay reductions that have occurred on every other subnet over the last month or so.
Once this proposal has executed, all subnets will have a notarisation delay of 300ms. Looks good, I’ve voted to adopt 
1 Like
Voted to adopt proposal 133903. Reduces the notarization delay of subnet tdb26 from 1000ms to 300ms in a sequence of changes to increase the block rate in a subnet. The payload matches the subnet and the new initial_notary_delay_millis aswell as the proposal summary
2 Likes
We just extended DRE tooling to allows it to automatically create forum posts for subnet management proposals. Here is the automatically created notification for the NNS subnet:
1 Like
Hey @sat, can I ask what the motivation for this is? What’s gained by each SM proposal having a dedicated forum topic? I think there are certain things that are lost with this approach, such as an easy to view chronology of changes that have been applied to a specific subnet (this alone has helped me to catch certain issues in the past)
1 Like
@Lorimer this was requested from us, let’s continue the discussion here
2 Likes
Proposal 134257
TLDR: I’ll vote to adopt. A down node in Australia is replaced with an unassigned node in Germany.
Motivation:
- replacing dead node onv2n-rm4ad-mgpnn-iiheu-6a76r-crgmo-wxpwt-dqf6y-n7gcf-5po4q-2qe
Decentralisation in terms of country diversity is improved, while it’s worsened in terms of the number of nodes in the same continent, and in terms of average geographic distance between nodes. The last two metrics are not part of the formal IC Target Topology.
Decentralisation Stats
Subnet node distance stats (distance between any 2 nodes in the subnet) →
| Smallest Distance | Average Distance | Largest Distance | |
|---|---|---|---|
| EXISTING | 0 km | 7559.677 km | 19448.574 km |
| PROPOSED | 0 km | 7153.41 km (-5.4%) | 19448.574 km |
This proposal slightly reduces decentralisation, considered purely in terms of geographic distance (and therefore there’s a slight theoretical reduction in localised disaster resilience). 
Subnet characteristic counts →
| Continents | Countries | Data Centers | Owners | Node Providers | Node Operator | |
|---|---|---|---|---|---|---|
| EXISTING | 5 | 27 | 39 | 38 | 37 | 40 |
| PROPOSED | 5 | 28 (+3.6%) | 39 | 38 | 37 | 40 |
This proposal slightly improves decentralisation in terms of jurisdiction diversity.
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 | 17 | 3 | 2 | 2 | 2 | 1 |
| PROPOSED | 18 (+5.88%) | 3 | 2 | 2 | 2 | 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)
Table
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
Here is my vote for the last proposal.
Voted to adopt proposal 134257.
This proposal replaces node onv2n which appeared in the dashboard as “Status: Offline”. As shown in the proposal and verified using the DRE tool, decentralisation is improved with respect to country but remains outside the requirements of the target topology as some node providers, data centre owners and a data centre owner still have 2 nodes.
1 Like
Voted to adopt proposal 134257. The proposal replaces one node from subnet tdb26:
Removed Node: onv2n, Dashboard Status Active. But as can been seen using the Node Provider Rewards tool the node currently has an AFR of 14% since October so it’s fair to say this node has been unstable and should be replaced.
Added Node: dbpb7
The proposal was verified using the DRE tool to verify the metrics stated. The country metric is improved reducing the number of nodes in the subnet from Australia from 2 to 1.
1 Like
A new proposal with id 134579 has been submitted, please take a look.
Click here to open proposal details
Replace nodes in subnet tdb26
Motivation:
The following nodes in subnet tdb26 have been cordoned and need to be removed from the subnet:
- fd5e4: offboarding BO1 DC after 48 months; DFINITY Gen-1 servers available for sale through silent auction
- mf3d3: offboarding SG3 DC after 48 months; New Node Provider Proposals - #581 by 162DC
Decentralization Nakamoto coefficient changes for subnet tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe:
node_provider: 11.00 -> 11.00 (+0%)
data_center: 13.00 -> 13.00 (+0%)
data_center_owner: 12.00 -> 11.00 (-8%)
area: 9.00 -> 10.00 (+11%)
country: 6.00 -> 6.00 (+0%)
Mean Nakamoto comparison: 10.83 → 10.83 (+0%)
Overall replacement impact: (gets better) the average log2 of Nakamoto Coefficients across all features increases from 3.3845 to 3.3889
Impact on business rules penalties: 30 → 40
Details
Nodes removed:
fd5e4-a2xzl-lxu7m-kjvn6-2arnt-jghro-rdrgx-zvvkd-j2hza-pbwl4-5qe[health: healthy]mf3d3-z5tww-ii4jn-zhy4f-ah3un-wpre7-edsb4-ktrb5-h7f3f-uz7rv-bqe[health: healthy]
Nodes added:
5gcqu-upr5b-ol3fj-vz273-3ov5j-s2dzp-d3n4o-c3rdz-rnhto-tovcx-zqe[health: healthy]ufciq-eduab-vwpdh-pfizy-jr6cj-xykuv-i3c64-b2odl-3nii3-b7r5f-jae[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae 1 ar1 1 Africa Data Centres 1 Barreiro 1 AR 1
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 ba1 1 Anonstake 1 British Columbia 1 AU 1
4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae 1 bc1 1 Baltneta 1 Brussels Capital 1 BE 1
4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae 1 bn1 1 Celeste 1 Bucuresti 1 CA 2
4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae 1 bo1 1 -> 0 Cloud9 1 CABA 1 CH 3
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 2 -> 1 br1 1 CyrusOne 1 Cape Town 1 CR 1
6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe 2 bt1 1 Cyxtera 1 Colombo 1 CZ 2
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 DataHouse 1 Florida 0 -> 1 DE 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 cm1 1 Datasite 0 -> 1 Gauteng 2 EE 1
7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe 1 cr1 1 Digital Realty 1 -> 2 Geneva 1 FR 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 2 -> 3 ct2 1 Equinix 2 Hesse 1 GE 1
cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe 1 fr2 1 Everyware 2 HongKong 2 HK 2
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 ge1 1 HighDC 1 Ljubljana 1 IL 1
diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe 1 hk3 1 INAP 1 -> 0 London 1 IN 2
efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe 1 hk4 1 InfonetDC 1 Maribor 1 JP 1
eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe 1 hu1 1 Interhost 1 Massachusetts 1 -> 0 KR 2
i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe 1 jb2 1 KT 1 Navi Mumbai 1 LK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb3 1 Latitude.sh 1 Panvel 1 LT 1
ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae 1 kr1 1 Leaseweb 1 Paris 1 LV 1
izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe 1 ld1 1 M247 1 Praha 1 PL 1
kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae 1 lj2 1 Master Internet 1 Quebec 1 PT 1
lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe 1 -> 0 mb1 1 MasterDC 1 Queensland 1 RO 1
mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae 1 mtl1 1 Megazone Cloud 1 Riga 1 SE 0 -> 1
nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae 1 nm1 1 NEXTDC 1 San Jose 1 SG 2 -> 1
py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe 1 or1 0 -> 1 Nano 1 Seoul 2 SI 2
qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae 1 pa1 1 Navegalo 1 Singapore 2 -> 1 UK 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 pl2 1 Online 1 South Moravian Region 1 US 3
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 pr1 1 OrionStellar 1 Stockholm 0 -> 1 ZA 3
s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae 1 rg3 1 Posita.si 1 Tallinn 1
sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae 1 sc1 1 Racks Central 1 -> 0 Tbilisi 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 sg1 1 Rivram 1 Tel Aviv 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 sg3 1 -> 0 SyT - Servicios y Telecomunicaciones S.A. 1 Texas 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 sh1 0 -> 1 TRG 1 Tokyo 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 sl1 1 Telin 1 Vilnius 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 st1 1 Teraco 1 Virginia 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 ta1 1 Xneelo 1 Warszawa 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 0 -> 1 tb1 1 Yotta 1 Zurich 2
zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae 1 tv1 1 hkcolo 1
ty3 1 hkntt 1
wa3 1
zh2 2
Business rules check results before the membership change:
- node_provider 6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- data_center_owner Equinix controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
Business rules check results after the membership change:
- node_provider bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe controls 3 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 20.
- data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- data_center_owner Digital Realty controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
1 Like
Note that the worsening in the “business rules” in the above proposal is due to DFINITY now owning only 2 DCs, and still having 3 nodes in the NNS subnet. We plant to submit a motion proposal after the holidays to add a change in the target topology to explicitly allow DFINITY to have 3 nodes in the NNS subnet, for fault tolerance and subnet recovery purposes in this subnet only, due to its importance.
3 Likes
Voted to reject proposal 134579 as this is part of a large batch of non-critical proposals timed such that the voting period clashes with national holidays, thereby allowing insufficient time for an appropriately detailed review to take place.
2 Likes
Rejected proposal 134579. There’s no time to review this and the 18 other proposals in the same batch properly over Xmas eve, Xmas and Boxing Day. This is a non-critical proposal.
More information and discussion on this thread.
1 Like
Proposal 134579
Vote: REJECT
Replaces cordoned nodes fd5e4 and mf3d3 with nodes 5gcqu and ufciq on subnet tdb26.
The reason for this proposal is to offboard BO1 and SG3 DCs consistent with forum posts made on the forum thread used for posts regarding the renovation/sell of Gen-1 node machines by NPs.
Both the NP and DC stated in the forum post and forum post match the ones from the node being removed in the proposal.
The business rules have worsened and a post was made by DFINITY in due time here explaining the situation but I don’t agree with the modus operandi in this situation since it assumes before hand that the next motion proposal will be adopted which we can’t say since the community hasn’t voted yet. Since this is a non critical proposal I would much prefer to see the other proposal adopted first and then this proposal.
Also there is a worsening in the decentralization coefficients regarding the data_center_owner metric seeing the DC owner Digital Realty having 2 nodes in the same subnet instead of the desired 1. This will not be solved even with the motion proposal from DFINITY
3 Likes
Voted to adopt proposal #134579.
The proposal replaces two cordoned nodes, one healthy Active status node fd5e4 from the BO1 Data Center in Massachusetts, and cordoned healthy Active status node mf3d3 from the SG3 Data Center in Singapore, with unassigned healthy Awaiting status node 5gcqu from Sweden and with unassigned healthy Awaiting status node ufciq from Florida, with a slight improvement overall to the decentralization of the subnet.
The motivation makes sense and the provided Forum link included in the summary provides further info, also it can be checked here.
*Keeping an eye out on the upcoming change in the target topology to explicitly allow DFINITY to have 3 nodes in the NNS subnet. Thanks Sasha for the heads up.
1 Like
Replace a node in subnet tdb26
Motivation:
The following nodes in subnet tdb26 have been cordoned and need to be removed from the subnet:
- dndht: offboarding the second rack of nodes in the GE1 DC after 48 months; Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #148 by Gwojda and Proposal: Update Interim Gen-1 Node Provider Remuneration After 48 months - #150 by katiep
Decentralization Nakamoto coefficient changes for subnet tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe:
node_provider: 11.00 -> 11.00 (+0%)
data_center: 13.00 -> 13.00 (+0%)
data_center_owner: 11.00 -> 11.00 (+0%)
area: 10.00 -> 10.00 (+0%)
country: 6.00 -> 6.00 (+0%)
Mean Nakamoto comparison: 10.83 → 10.83 (+0%)
Overall replacement impact: (gets better) the number of nodes controlled by dominant Country actors decreases from 15 to 14
Impact on business rules penalties: 40 → 40
Details
Nodes removed:
dndht-2fce7-aze7e-coa4j-yvyuw-ut4hw-gn5dj-xvxox-whdhg-txikb-yae[health: healthy]
Nodes added:
lh2af-66zso-76kqu-d57ag-jca5d-yvmfo-rcabh-ptlvj-ltfdf-kyg6q-lqe[health: healthy]
node_provider data_center data_center_owner area country
------------- ----------- ----------------- ---- -------
3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae 1 ar1 1 Africa Data Centres 1 Barreiro 1 AR 1
4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 ba1 1 Anonstake 1 British Columbia 1 AU 1
4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae 1 bc1 1 Baltneta 1 Brussels Capital 1 BE 1
4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae 1 bn1 1 Celeste 1 Bucuresti 1 CA 2
4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae 1 br1 1 Cloud9 1 CABA 1 CH 3 -> 2
6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bt1 1 CyrusOne 1 Cape Town 1 CR 1
6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe 2 bu1 1 Cyxtera 1 Colombo 1 CZ 2
7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 cm1 1 DataHouse 1 Florida 1 DE 1
7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 -> 0 cr1 1 Datasite 1 Gauteng 2 EE 1
7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe 1 ct2 1 Digital Realty 2 Geneva 1 -> 0 FR 1
bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 3 fr2 1 Edgoo Networks 0 -> 1 Hesse 1 GE 1
cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe 1 ge1 1 -> 0 Equinix 2 HongKong 2 HK 2
dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hk3 1 Everyware 2 Lisbon 0 -> 1 IL 1
diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe 1 hk4 1 HighDC 1 -> 0 Ljubljana 1 IN 2
efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe 1 hu1 1 InfonetDC 1 London 1 JP 1
eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe 1 jb2 1 Interhost 1 Maribor 1 KR 2
i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe 1 jb3 1 KT 1 Navi Mumbai 1 LK 1
i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 kr1 1 Latitude.sh 1 Panvel 1 LT 1
ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae 1 ld1 1 Leaseweb 1 Paris 1 LV 1
izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe 1 li2 0 -> 1 M247 1 Praha 1 PL 1
kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae 1 lj2 1 Master Internet 1 Quebec 1 PT 1 -> 2
mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe 0 -> 1 mb1 1 MasterDC 1 Queensland 1 RO 1
mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae 1 mtl1 1 Megazone Cloud 1 Riga 1 SE 1
nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae 1 nm1 1 NEXTDC 1 San Jose 1 SG 1
py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe 1 or1 1 Nano 1 Seoul 2 SI 2
qsdw4-ao5ye-6rtq4-y3zhm-icjbj-lutd2-sbejz-4ajqz-pcflr-xrhsg-jae 1 pa1 1 Navegalo 1 Singapore 1 UK 1
r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 pl2 1 Online 1 South Moravian Region 1 US 3
rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 pr1 1 OrionStellar 1 Stockholm 1 ZA 3
s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae 1 rg3 1 Posita.si 1 Tallinn 1
sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae 1 sc1 1 Rivram 1 Tbilisi 1
sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 sg1 1 SyT - Servicios y Telecomunicaciones S.A. 1 Tel Aviv 1
ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 sh1 1 TRG 1 Texas 1
unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 sl1 1 Telin 1 Tokyo 1
vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 st1 1 Teraco 1 Vilnius 1
wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 ta1 1 Xneelo 1 Virginia 1
wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 tb1 1 Yotta 1 Warszawa 1
wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 tv1 1 hkcolo 1 Zurich 2
zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae 1 ty3 1 hkntt 1
wa3 1
zh2 2
Business rules check results before the membership change:
- node_provider bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe controls 3 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 20.
- data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- data_center_owner Digital Realty controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
Business rules check results after the membership change:
- node_provider bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe controls 3 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 20.
- data_center zh2 controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
- data_center_owner Digital Realty controls 2 of nodes, which is higher than target of 1 for the subnet. Applying penalty of 10.
1 Like