[7.5][TBD] Better node management #1521

startailcoon · 2018-05-17T15:56:42Z

As we gain more and more nodes from both witnesses, businesses, regular joes and worker programs, the list has grown quite long. Nodes all around the globe is in one single list, and mixed with testnet nodes, just to make the matter worse.

I propose we make a UX for a better node management.
A user should be able to filter/find/sort nodes on flags like these, but not limited:

Country (UK, Sweden, US, China etc.)
Region (North America, Europe, Asia etc.)
Owner (Witness, Worker, Exchange etc)
Network (Main or Test for the moment)
Core version
Buckets and History sizes

The goal of this would be to make the list of nodes more manageable.

clockworkgr · 2018-05-17T18:45:33Z

Possibly amount of history & bucket sizes offered too? (although I have started a discussion in telegram to standardize bucket sizes offered for uniformity)

sschiessl-bcp · 2018-05-20T03:20:54Z

Totally agree, include with the ping all button that I somehow forgot in my last PR...

svk31 · 2018-05-20T06:29:56Z

Knowing bucket sizes requires us to make an api call to the node. The amount of history is not available AFAIK.

abitmore · 2018-05-20T12:14:59Z

Owner (Witness, Worker, Exchange etc)

This is useful especially when a node is having issues. Easier to contact the node admin.

- refactoring of SettingsStore and AccessSettings - prepare routerTransitioner to support a more sophistiaced node dictionary Signed-off-by: Stefan Schiessl <stefan.schiessl@blockchainprojectsbv.com>

sschiessl-bcp · 2018-07-18T13:16:24Z

During working on #1672 and refactoring I realized that this issue is probably gonna be solved on the. Can this be rated please? @startailcoon @wmbutler

sschiessl-bcp · 2018-07-19T10:43:35Z

During my work on this I found a bug in the SettingsStore. If any default values change (removing nodes, changing faucet), the user does not get those changes due to local storage having old values. Will include a fix for that as well

abitmore · 2018-07-19T12:04:05Z

Is there a way to not trigger chrome warning when one of the nodes has a bad SSL certificate?

sschiessl-bcp · 2018-07-19T12:11:14Z

Is there a way to not trigger chrome warning when one of the nodes has a bad SSL certificate?

No, that can only be deactivated by the user. Even if the UI wanted to evaluate certificates itself (and not connect if invalid) the user would still get a notification.

- second wholesome refactoring of AccessSettings. ApiNode has all the knowledge itself now - refactored SettingsStore. Next step: eliminate bug that defaults are not overwritten Signed-off-by: Stefan Schiessl <stefan.schiessl@blockchainprojectsbv.com>

sschiessl-bcp · 2018-07-20T12:14:49Z

Requesting feedback for visualization and configuration options @bitshares/ui-dev

Title is Region - Country - Location (Optional), Operator is right aligned. An entry in apiConfig.js looks like this then:

bitshares-ui/app/api/apiConfig.js

Lines 117 to 123 in 3412357

    
           { 
        
               url: "wss://eu.nodes.bitshares.ws", 
        
               region: "Central Europe", 
        
               country: "Germany", 
        
               operator: "Infrastructure Worker", 
        
               contact: "email:info@blockchainprojectsbv.com" 
        
           },

clockworkgr · 2018-07-20T12:20:54Z

I really like that @sschiessl-bcp !

sschiessl-bcp · 2018-07-20T14:28:42Z

Thanks @clockworkgr

I just commited a more extensive refactoring of SettingsStore and AccessSettings. Filtering I will add next week.

sschiessl-bcp · 2018-07-23T11:47:17Z

I am calling out to all node operators, please provide me with the additional information to be able to give the user a more sophisticated selection process and filtering options.

Please simply comment in here with your updated node configuration in the same style (so I can copy and paste). Use the old configuration like seen here and add the new configuration. Expectancy of a post:

Please update

        {
            url: "wss://eu.nodes.bitshares.ws",
            location: "Central Europe - BitShares Infrastructure Program"
        }

to

        {
            url: "wss://eu.nodes.bitshares.ws",
            region: "Western Europe",
            country: "Germany",
            location: "Nuremberg",
            operator: "Infrastructure Worker",
            contact: "email:blockchainprojectsbv.com;info"
        }

If the url has not changed, mentioning the old config entry can be ommitted. Short explanation:

url: exact url of the node that allows a websocket connection
location: City of the node server (optional)
country: Country of the node server

region: Region of the node server, important for a more sophisticated geolocation-based connection strategy later on. One of the following options (please open the link to locate your own region)

bitshares-ui/app/api/apiConfig.js

Lines 71 to 95 in f9736a4

    
           // region of the node follows roughly https://en.wikipedia.org/wiki/Subregion#/media/File:United_Nations_geographical_subregions.png 
        
           "Northern Europe", 
        
           "Western Europe", 
        
           "Southern Europe", 
        
           "Eastern Europe", 
        
           "Northern Asia", 
        
           "Western Asia", 
        
           "Southern Asia", 
        
           "Eastern Asia", 
        
           "Central Asia", 
        
           "Southeastern Asia", 
        
           "Australia", 
        
           "New Zealand", 
        
           "Melanesia", 
        
           "Polynesia", 
        
           "Micronesia", 
        
           "Northern Africa", 
        
           "Western Africa", 
        
           "Middle Africa", 
        
           "Eastern Africa", 
        
           "Southern Africa", 
        
           "Northern America", 
        
           "Central America", 
        
           "Caribbean", 
        
           "South America"

If you have a dns based geolocation redirection enabled, please select "Worldwide" as region and fill in the different possibilties in location.

operator: Whatever entity is providing this server (can be Anonymous if really necessary)
contact: A string containing perefered contact method and details, i.e. "[email|telegram|github|...]:details". This information will not be displayed in the UI (yet), but it is essential that the UI team has some way of contacting all node operators. Examples:
- "github:sschiessl-bcp"
- "email:blockchainprojectsbv.com;info" You may mask your email in whatever way you please to avoid crawlers finding it, even ommi the keyword "email:" in it, as long as its reconstructable for the human reader. For our email the "info" would be the part before the "@"
- "telegram:sschiessl"

Failure to provide detailed information on your node will result to be listed as "Unknown" in the reference wallet. Unknown nodes might be removed later on.

clockworkgr · 2018-07-23T11:59:47Z

{
url: "wss://bts-seoul.clockwork.gr",
region: "Southeastern Asia",
country: "Korea",
location: "Seoul",
operator: "Witness: clockwork",
contact: "telegram:clockworkgr",
history_ops: "100"
}

dls-cipher · 2018-07-23T12:06:08Z

Listing emails in pages in their native structure mailbox@domain.com will end up in Search Engines, and eventually become just an open-invite for crawlers, bots, spam and unusual activity over https://wallet.bitshares.org so no, I don't agree with adding emails as contacts.

I would also added line entry that is saying is the node standard/full so we can end that endless question of users "is there any full node".

Rest is fine.

clockworkgr · 2018-07-23T12:18:51Z

After DL's comment I suggest a history_ops entry specifying amount of history. 0 for full node, or number for max ops held.

Updated my comment accordingly

abitmore · 2018-07-23T19:59:31Z

@clockworkgr 0 for mini node with no history.

startailcoon · 2018-07-23T20:08:24Z

{ 
     url: "wss://bitshares.crypto.fans/ws", 
     region: "Western Europe", 
     country: "Germany", 
     location: "Munich",
     operator: "Witness: sc-ol", 
     contact: "telegram:startail",
     history_ops: "100"
}

abitmore · 2018-07-23T20:49:32Z

{ 
     url: "wss://api.bts.mobi/ws",
     region: "Northern America",
     country: "USA",
     location: "VA",
     operator: "Witness: in.abit",
     contact: "telegram:abitmore",
     history_ops: "1000"
}

Actually I think UI can detect number of history_ops by itself.

By the way, how about enabled plugins / apis? Version? Compile-time options(bitshares/bitshares-core#1099)? Will the UI code detect them automatically?

sschiessl-bcp · 2018-07-23T21:54:00Z

@abitmore Yes, after connecting to the node that could be evaluated, but the main spirit of this update is to give the user filtering before connecting. All meanwhile the user should not be able to discriminate on facts other than location and operator. Users like bigger numbers, running a full node is already more expensive and I want to avoid that traffic focuses there then. That's where ES come into sight.

After connection has been established I am hoping to get bitshares/bitshares-core#626 to provide more intel on the node. Also in the spirit of said issue I want to avoid putting down any hardcoded information that would be excluded in such a server info API due to security risks.

ghost · 2018-07-25T09:47:17Z

{ 
     url: "wss://api.fr.bitsharesdex.com",
     region: "Western Europe",
     country: "FRANCE",
     location: "Paris",
     operator: "delegate.ihashfury",
     contact: "telegram:ihashfury",
     history_ops: "1000"
     bucket-size: "60,300,900,1800,3600,14400,86400,604800"
}

{ 
     url: "wss://api.bitsharesdex.com",
     region: "Northern America",
     country: "USA",
     location: "Kansas City",
     operator: "delegate.ihashfury",
     contact: "telegram:ihashfury",
     history_ops: "1000"
     bucket-size: "60,300,900,1800,3600,14400,86400,604800"
}

- askToReconnectAfterSeconds in footer increased to 10 seconds - remove duplicate doQuickLatencyUpdate - beSatisfiedWith is now a map according to AccessSettings display - remove bug that you dont connect to your selected one if not autoselction Signed-off-by: Stefan Schiessl <stefan.schiessl@blockchainprojectsbv.com>

MikhailKavalenka · 2018-08-06T13:33:44Z

{
url: "wss://na.openledger.info/ws",
location: "Canada, Quebec",
operator: "Witness: openledger-dc",
contact: "telegram:mtopenledger",
history_ops: "100",
bucket-size : [15,60,300,3600,86400]
}

One more from Openledger

abitmore · 2018-08-06T15:21:18Z

Still remain:

api.btsxchng.com, elmato
btsza.co.za:8091
dex.rnglab.org, rnglab
node.btscharts.com

Just FYI I've pinged elmato,rnglab and owner of btscharts, all responded but no action here yet.

ghost · 2018-08-07T06:02:30Z

{
url: "wss://node.btscharts.com/ws",
region: "Eastern Asia",
country: "China",
location: "Beijing",
operator: "leo2017",
contact: "Wechat: wx8855221 , Email:8855221@qq.com",
history_ops: "1000",
bucket-size: "15,60,300,3600,86400"
}

sschiessl-bcp · 2018-08-07T08:48:15Z

Added

- askToReconnectAfterSeconds in footer increased to 10 seconds - remove duplicate doQuickLatencyUpdate - beSatisfiedWith is now a map according to AccessSettings display - remove bug that you dont connect to your selected one if not autoselction Signed-off-by: Stefan Schiessl <stefan.schiessl@blockchainprojectsbv.com>

elmato · 2018-08-11T07:47:12Z

{
url: "wss://api.btsxchng.com",
region: "Multiple",
country: "Worldwide",
location: "Singapore / N. Virginia / London",
operator: "Witness: elmato",
contact: "telegram:elmato",
history_ops: "300",
bucket-size: "60,300,900,1800,3600,14400,86400"
}

startailcoon · 2018-08-25T20:49:39Z

@sschiessl-bcp is all nodes updates so we can close this issue?

sschiessl-bcp · 2018-08-30T07:21:30Z

Nodes missing:

wss://bitshares.nu/ws
wss://dex.rnglab.org
wss://btsza.co.za:8091/ws
bts.proxyhosts.info/wss

dls-cipher · 2018-08-30T07:50:09Z

{
url: "wss://bitshares.nu/ws",
region: ""Northern Europe"",
country: "Sweden",
location: "Stockholm",
operator: "DAO Collaboration - Infrastructure Worker",
contact: "telegram:StaflunD",
history_ops: "100",
bucket-size: "60,300,900,1800,3600,14400,86400"
}

rngl4b · 2018-08-31T02:15:07Z

{
url: "wss://dex.rnglab.org",
region: "Northern Europe",
country: "Netherlands",
location: "Amsterdam",
operator: "Witness: rnglab",
contact: "keybase:rnglab",
history_ops: "100",
bucket-size: "60,300,900,1800,3600,14400,86400,604800"
}

ThomasFreedman · 2018-08-31T14:45:11Z

{
url: "wss://bts.proxyhosts.info/wss",
region: "",
country: "Germany",
location: "",
operator: "Witness: verbaltech2",
contact: "keybase:jgaltman",
history_ops: "300",
bucket-size: "60,300,900,1800,3600,14400,86400"
}

wmbutler · 2018-09-05T14:36:36Z

Is this ready to get closed out and paid?

barefootmouse · 2018-09-14T08:56:47Z

        {
            url: "wss://de.bts.dcn.cx/ws",
            region: "Western Europe",
            country: "Germany",
            location: "Nuremberg",
            operator: "Witness: fla01",
            contact: "telegram:Otherego, telegram:BarefootMouse",
            history_ops: "256",
            bucket-size: "60,300,900,1800,3600,14400,86400"
        }

        {
            url: "wss://fi.bts.dcn.cx/ws",
            region: "Northern Europe",
            country: "Finland",
            location: "Helsinki",
            operator: "Witness: fla01",
            contact: "telegram:Otherego, telegram:BarefootMouse",
            history_ops: "256",
            bucket-size: "60,300,900,1800,3600,14400,86400"
        }

And testnet

        {
            url: "wss://testnet.bts.dcn.cx/ws",
            region: "Europe",
            country: "Germany / Finland",
            location: "Nurenberg / Helsinki",
            operator: "Witness: fla-test",
            contact: "telegram:Otherego, telegram:BarefootMouse",
            history_ops: "100",
            bucket-size: "60,300,900,1800,3600,14400,86400"
        }

sschiessl-bcp · 2018-09-26T07:24:56Z

apiConfig has been updated, this issue is completed.

sschiessl-bcp · 2018-09-26T07:27:50Z

The next step is laid out in #1901, please evaluate

abitmore mentioned this issue May 20, 2018

Server Info API bitshares/bitshares-core#626

Closed

wmbutler added the [3] Enhancement Classification indicating a change to the functionality of the existing imlementation label May 20, 2018

startailcoon mentioned this issue Jun 4, 2018

User Management of Nodes - Hide #1570

Closed

sschiessl-bcp mentioned this issue Jul 20, 2018

[3] Advanced ping strategy on application init #1701

Closed

sschiessl-bcp mentioned this issue Jul 24, 2018

Better Node Management, Orders Api and Refactoring #1726

Merged

svk31 added this to the 180803 milestone Jul 26, 2018

svk31 changed the title ~~Better node management~~ [TBD] Better node management Jul 26, 2018

svk31 assigned sschiessl-bcp Jul 26, 2018

sschiessl-bcp changed the title ~~[4][TBD] Better node management~~ [7.5][TBD] Better node management Aug 6, 2018

sschiessl-bcp mentioned this issue Aug 6, 2018

More nodes and connectivity bugfix #1764

Merged

wmbutler modified the milestones: 180801, 180815 Aug 6, 2018

wmbutler modified the milestones: 180815, 180905 Aug 26, 2018

sschiessl-bcp mentioned this issue Sep 5, 2018

Added Citadel gateway #1695

Merged

wmbutler modified the milestones: 180905, 180919 Sep 13, 2018

wmbutler modified the milestones: 180919, 181003 Sep 25, 2018

sschiessl-bcp mentioned this issue Sep 26, 2018

[10] Sophisticated ping strategy and background pinging #1901

Closed

sschiessl-bcp closed this as completed Sep 26, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[7.5][TBD] Better node management #1521

[7.5][TBD] Better node management #1521

startailcoon commented May 17, 2018 •

edited

clockworkgr commented May 17, 2018

sschiessl-bcp commented May 20, 2018

svk31 commented May 20, 2018

abitmore commented May 20, 2018 •

edited

sschiessl-bcp commented Jul 18, 2018 •

edited

sschiessl-bcp commented Jul 19, 2018

abitmore commented Jul 19, 2018

sschiessl-bcp commented Jul 19, 2018 •

edited

sschiessl-bcp commented Jul 20, 2018 •

edited

clockworkgr commented Jul 20, 2018

sschiessl-bcp commented Jul 20, 2018

sschiessl-bcp commented Jul 23, 2018 •

edited

clockworkgr commented Jul 23, 2018 •

edited

dls-cipher commented Jul 23, 2018 •

edited

clockworkgr commented Jul 23, 2018

abitmore commented Jul 23, 2018

startailcoon commented Jul 23, 2018

abitmore commented Jul 23, 2018

sschiessl-bcp commented Jul 23, 2018 •

edited

ghost commented Jul 25, 2018

MikhailKavalenka commented Aug 6, 2018

abitmore commented Aug 6, 2018

ghost commented Aug 7, 2018

sschiessl-bcp commented Aug 7, 2018

elmato commented Aug 11, 2018

startailcoon commented Aug 25, 2018

sschiessl-bcp commented Aug 30, 2018

dls-cipher commented Aug 30, 2018

rngl4b commented Aug 31, 2018

ThomasFreedman commented Aug 31, 2018

wmbutler commented Sep 5, 2018

barefootmouse commented Sep 14, 2018 •

edited

sschiessl-bcp commented Sep 26, 2018

sschiessl-bcp commented Sep 26, 2018

[7.5][TBD] Better node management #1521

[7.5][TBD] Better node management #1521

Comments

startailcoon commented May 17, 2018 • edited

clockworkgr commented May 17, 2018

sschiessl-bcp commented May 20, 2018

svk31 commented May 20, 2018

abitmore commented May 20, 2018 • edited

sschiessl-bcp commented Jul 18, 2018 • edited

sschiessl-bcp commented Jul 19, 2018

abitmore commented Jul 19, 2018

sschiessl-bcp commented Jul 19, 2018 • edited

sschiessl-bcp commented Jul 20, 2018 • edited

clockworkgr commented Jul 20, 2018

sschiessl-bcp commented Jul 20, 2018

sschiessl-bcp commented Jul 23, 2018 • edited

clockworkgr commented Jul 23, 2018 • edited

dls-cipher commented Jul 23, 2018 • edited

clockworkgr commented Jul 23, 2018

abitmore commented Jul 23, 2018

startailcoon commented Jul 23, 2018

abitmore commented Jul 23, 2018

sschiessl-bcp commented Jul 23, 2018 • edited

ghost commented Jul 25, 2018

MikhailKavalenka commented Aug 6, 2018

abitmore commented Aug 6, 2018

ghost commented Aug 7, 2018

sschiessl-bcp commented Aug 7, 2018

elmato commented Aug 11, 2018

startailcoon commented Aug 25, 2018

sschiessl-bcp commented Aug 30, 2018

dls-cipher commented Aug 30, 2018

rngl4b commented Aug 31, 2018

ThomasFreedman commented Aug 31, 2018

wmbutler commented Sep 5, 2018

barefootmouse commented Sep 14, 2018 • edited

sschiessl-bcp commented Sep 26, 2018

sschiessl-bcp commented Sep 26, 2018

startailcoon commented May 17, 2018 •

edited

abitmore commented May 20, 2018 •

edited

sschiessl-bcp commented Jul 18, 2018 •

edited

sschiessl-bcp commented Jul 19, 2018 •

edited

sschiessl-bcp commented Jul 20, 2018 •

edited

sschiessl-bcp commented Jul 23, 2018 •

edited

clockworkgr commented Jul 23, 2018 •

edited

dls-cipher commented Jul 23, 2018 •

edited

sschiessl-bcp commented Jul 23, 2018 •

edited

barefootmouse commented Sep 14, 2018 •

edited