Author Topic: [Worker Proposal] BitShares Global Infrastructure by APAsia.tech & Collaborators  (Read 1476 times)

0 Members and 1 Guest are viewing this topic.

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
Ladies and gents,

As many of you know, we've been running few nodes for a while (not listed in wallet most of them, but publicly shared and used through various channels). That Collaboration and Contribution will come to an end, unless we can keep those nodes and continue even more professional management through the agreement with BitShares DAC and approval of it's stake-holders through this offer as a Worker Proposal :

http://apasia.tech/bts-workers/bitshares-infra-worker-2018-APT.pdf

Worker is currently not on-chain and here is brought for initial discussion.

We will provide within 24 hours costs (invoices/receipts) that we have paid until now (~$14.800,00) as proof of contribution and ownership/existence of all nodes (even more), Premium SSL Certificates, Testing and Development servers, Current online status of servers (not bitshares api - as half of them requires an upgrade we can't finance), and whatever else is needed or requested by the stake-holders and respected proxies.


P.S. I've personally consider current Witness contribution, BBF active worker and this worker something that would greatly improved stability and performance on much greater global scale and enabled more users to join.

Thanks.
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline clockwork

  • Committee member
  • Full Member
  • *
  • Posts: 144
    • View Profile
  • BitShares: clockwork
About time!

APAsia.tech's financial contribution through infrastructure support as well as DL's personal time commitment to the BitShares community is definately worth reimbursement.

I consider the 3.5k USD monthly cost for 25 nodes w/ maintenance, combined with DL's proven commitment an excellent offer and will be voting for this as soon as available.

Offline JohnR

  • Committee member
  • Full Member
  • *
  • Posts: 64
    • View Profile
  • BitShares: johnr
This infrastructure production has been in the works for a few months now and DL has put in a lot of work getting things just right.  All while operating in a transparent manner and soliciting feedback from community and node admins along the way.

I see this as a very potent upgrade/addition to the BitShares network that will support the continued expansion of the DAC into more territories and users.  Investment in infrastructure aids every other initiative we discuss here.  I have full confidence in DL's ability to manage this architecture in the most professional manner.

To a more resilient distributed network and BitShares' future prosperity.
Active Committee
John Robert Conlin

Online Bangzi

  • Full Member
  • ***
  • Posts: 157
    • View Profile
    • Steemit: Bangzi
  • BitShares: bangzi
It is worth noting that DL provide API node for DEXBot market makers to increase liquidity of Bitshares DEX.

By the way, does this worker proposal going to cover maintenance of Bitshares.org or in separate worker proposal?
 
Please Vote for My Witness: Bangzi
My Blog: https://steemit.com/@bangzi
请投票支持比特股见证人: Bangzi

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
By the way, does this worker proposal going to cover maintenance of Bitshares.org or in separate worker proposal?

This is Collaboration Infrastructure Worker and it's not related with bitshares.org

bitshares.org development, management, team for the worker and corporate structure with unique content, legal, email services and additional hosting will come as separate proposal later today.
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4243
  • No Pain, No Gain
    • View Profile
  • BitShares: fav
do you plan to report on usage stats?
► How-to Buy BitShares: https://goo.gl/i9j2YZ

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
do you plan to report on usage stats?
Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).

For the uptime stats, latency and availability will be used status pages as mentioned in worker. One for all listed Public API's and one separate for just nodes listed in this worker.

When you already mentioned, maybe it would be good to make an offer:

In case that this worker gets approved/voted it would be nice as respect and support of BBF infrastructure worker, that we can wrap our nodes under their balancers, and add their balancers/nodes to separate status page (their proposal is having milestone for development, we have it using uptimerobot), to get more data from monitoring to be compared, improve bug tracking, add more transparency to the stake-holders, etc.

Personally, I do believe that such co-operation would be of great benefit for everyone.
« Last Edit: July 23, 2018, 03:54:49 pm by Digital Lucifer »
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4243
  • No Pain, No Gain
    • View Profile
  • BitShares: fav
do you plan to report on usage stats?
Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).

For the uptime stats, latency and availability will be used status pages as mentioned in worker. One for all listed Public API's and one separate for just nodes listed in this worker.

When you already mentioned, maybe it would be good to make an offer:

In case that this worker gets approved/voted it would be nice as respect and support of BBF infrastructure worker, that we can wrap our nodes under their balancers, and add their balancers/nodes to separate status page (their proposal is having milestone for development, we have it using uptimerobot), to get more data from monitoring to be compared, improve bug tracking, add more transparency to the stake-holders, etc.

Personally, I do believe that such co-operation would be of great benefit for everyone.

yeah, I'd like to know whether nodes are actually used (by users), to make sure none of us wastes time and money.
► How-to Buy BitShares: https://goo.gl/i9j2YZ

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
do you plan to report on usage stats?
Such as bandwidth or average/total connections/ddos attempts, etc? If yes, its built-in in both AWS and Vultr and for Sweden and Slovenia there can be done local traffic monitor. As example, one time it was posted re discussion of Public API abuse on the github (i believe england.bitshares.apasia.tech was on the screenshot).

For the uptime stats, latency and availability will be used status pages as mentioned in worker. One for all listed Public API's and one separate for just nodes listed in this worker.

When you already mentioned, maybe it would be good to make an offer:

In case that this worker gets approved/voted it would be nice as respect and support of BBF infrastructure worker, that we can wrap our nodes under their balancers, and add their balancers/nodes to separate status page (their proposal is having milestone for development, we have it using uptimerobot), to get more data from monitoring to be compared, improve bug tracking, add more transparency to the stake-holders, etc.

Personally, I do believe that such co-operation would be of great benefit for everyone.

yeah, I'd like to know whether nodes are actually used (by users), to make sure none of us wastes time and money.

Yes, bandwidth reports will be included in monthly/invoice reports.

From the technical point of view, there is no node that can be listed in wallet and unused (if its available), since on 30k active accounts world wide (that we expect to grow), all the time some of the nodes are unreachable to someone. With this 25 Public APIs as addition to the current list of nodes and their availability, we would still have place/demand for more.

This proposal was actually postponed for 3 months to pass all the HFs and additional scale tests due to unexpected raise of the blockchain database starting with bits.farm, dexbot and other activity influence.
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4243
  • No Pain, No Gain
    • View Profile
  • BitShares: fav
okay thanks, will vote for it.
► How-to Buy BitShares: https://goo.gl/i9j2YZ

Offline oxarbitrage

i like the idea of having more infrastructure with official worldwide nodes as proposed.

a few points to consider:
- there is no node in south america. i understand blockchain usage in general is not so popular here as other continents, still i think a node in Brazil or Argentina can bring some value.
- will you consider on hosting 1 elasticsearch node ? i think that if the wallet start using the feature we might need 1 more official node available(there is already 1 up from the BBF infrastructure worker rest is community members aka @clockwork).

price looks reasonable and APAsia already have a reputation in the community, i think it will go throw.

pd: also no node in Africa where the usage is probably even less than South America. Node in Hong Kong ?

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
i like the idea of having more infrastructure with official worldwide nodes as proposed.

a few points to consider:
- there is no node in south america. i understand blockchain usage in general is not so popular here as other continents, still i think a node in Brazil or Argentina can bring some value.
- will you consider on hosting 1 elasticsearch node ? i think that if the wallet start using the feature we might need 1 more official node available(there is already 1 up from the BBF infrastructure worker rest is community members aka @clockwork).

price looks reasonable and APAsia already have a reputation in the community, i think it will go throw.

pd: also no node in Africa where the usage is probably even less than South America. Node in Hong Kong ?

Aflredo,

1) Elasticsearch, as proven in the past few months with help from Alex and other participants, is something really needed for the infra and probably only scalable future of it. We didn't deployed in past 2 months any ES node, as explained came to financial limits where ES node is quite demanding (re costs/system specification). Currently status200 is full node in our list and its being used by DEXBot, which could be only setup as ES from our current list.

Another thing we discussed not long ago in Telegram, I would be deploying one physical server in Thailand with raid setup of 2x1TB or SSD higher iops (Samsung EVO series) with max ram i can fit in some of intel boxes i have and one dedicated IP for the purpose of outside testing and most important - proper introduction of ES to myself. I also do believe I said I would be willing to share ssh with you, Alex, Fabian or whoever is interested to gets the most of it.

Eventually even if above attempt fails, we can remove few nodes to get available funds for ES node through this proposal.

2) Geological and logical demand for Public API such as South America or Africa is obvious - yes. On our last Steem post re infrastructure we even deployed a map with BTS pins for current infra and missing parts. So, as per your request explained:

Hong Kong - BitShares has a lot of investors, 3rd party businesses and Witnesses around China/Hong Kong that can provide such API (already OL and one more are having HK in wallet) - they can and should handle it.

Africa - We had tries in Arusha, Cape Town and private hosting, and i do have real friend in Tanzania living for nearly 10 years. Africa hosts are slow, SSD is sometimes HDD, sometimes SSD but then it starts running slow, and system specifications are very limited per choice of size. We did investment and tests on various ISP's in Africa, for 2 consecutive months, and all of them failed to provide node that even can replay normal node (not full) within some normal eta of ~6 hours with up2date blockchain database locally downloaded. So big NO to Africa for now if we want to maintain stability and reputation when it comes to uptime and availability of the nodes listed in worker. Later today when i upload invoices, there can be also found those few attempts mentioned.

Community Member and Stake-holder who is also a trader of DEX - Trizle - was the reason why we started exploring Africa. In December that man suffered a lot only because no having available API and relying on localhost that sometimes fail to sync for hours.

S. America - Brazil (Sao Paolo) is only reasonable option. There is one host worth of trying for node that would cover requirements of max-ops 100 if that SSD is real, but cost is still - we can build ES on Privex for this price, and they still have decent ping to California and other souther parts of USA.

HostDime is having 4GB node with 80GB SSD for 150$ per month. My biggest concern is that is KVM VPS and probably SWAP are locked/limited and there will be not much use for it (as we had some fails in the past). We can in case that worker goes through replace one Paris from AWS with one Sao Paolo from HostDime and together with you and maybe Diogo Gomes, test the node privately is it worth of presenting it to public.

_____________________
- I've personally tried to use best of my networking knowledge and create a pattern on the globe to utilize maximum availability. We did first (and only) public node in Australia and Canada, covered from East to West Coast of USA (where last year was only Xeldal and broken Texas node - before movement of witnesses re bitcrab vote and requirement) and all i'm saying we really had careful picks not just random purchases. I intend to keep utilizing network and optimizing its costs.
- I would point out that ES node that we would be hosting through worker has only sense having home in USA and best ISP for it would be Privex.io - Alex (Clockwork - Witness) is hosting ES in Asia and Fabian (Xeroc - BBF) is hosting ES in Europe.

Thanks for original input and feedback and hope to read more from you on this. Very important topic indeed, since we got into the problem with finance from scalability issues.
« Last Edit: July 24, 2018, 04:42:10 am by Digital Lucifer »
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline clockwork

  • Committee member
  • Full Member
  • *
  • Posts: 144
    • View Profile
  • BitShares: clockwork
_____________________
- I've personally tried to use best of my networking knowledge and create a pattern on the globe to utilize maximum availability. We did first (and only) public node in Australia and Canada, covered from East to West Coast of USA (where last year was only Xeldal and broken Texas node - before movement of witnesses re bitcrab vote and requirement) and all i'm saying we really had careful picks not just random purchases. I intend to keep utilizing network and optimizing its costs.
- I would point out that ES node that we would be hosting through worker has only sense having home in USA and best ISP for it would be Privex.io - Alex (Clockwork - Witness) is hosting ES in Asia and Fabian (Xeroc - BBF) is hosting ES in Europe.

Thanks for original input and feedback and hope to read more from you on this. Very important topic indeed, since we got into the problem with finance from scalability issues.

Just to clarify...Asia is my API node (seoul)...my ES node is in Finland.

Would be willing to relocate it if I find appropriate host in Asia (or anywhere) if needed.

Offline Digital Lucifer

  • Global Moderator
  • Full Member
  • *****
  • Posts: 108
  • 13 years of being Slackware abUser
    • View Profile
    • Bitshares DEX Thailand
  • BitShares: steem-not
  • GitHub: dls-cipher
Just to clarify...Asia is my API node (seoul)...my ES node is in Finland.

Would be willing to relocate it if I find appropriate host in Asia (or anywhere) if needed.

Thanks, and sorry, my bad, from conversations we had I got wrong assumption it's in Asia, actually never asked you for actual location. Well if it comes to the point where that bare physical server is a go + result in utilizing requirements of ES in Thailand it would be solution - re Asia. Then it would have more sense to relocate your ES from Finland to somewhere in USA :)

Just a suggestion, def needs more feedback from Abit, Alfredo, Fabian, Ryan and others.

« Last Edit: July 24, 2018, 08:51:18 am by Digital Lucifer »
Milos (Mike) Preocanin - General Manager @ Syntek Solutions
TOANDI Co., LTD. (BOI Approved) - TAX ID: 0205549016913 - 95/5 Moo 4 Siam Country Club Rd.
Nong Prue, Bang Lamung, Chonburi 20250, Thailand.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12661
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I very much appreciate the time and resources people put behind improving the distribution and decentralization of the BitShares network, in particular when it comes to APIs.

+5% for this worker!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH