Some of you may know, we @apasia.tech were syncing with VPS Steem Blockchain since few days ago, and eventually gave up on complete VPS story in Thailand running a blockchain of a Steem!
What happened further more... Hehehehe :)
Announcing Physical Server for Full Node within reach of my hands
Yes! We've ordered Fiber 200/100 mbps just for this blockchain occassion, and i've setup a decent rig for running a blockchain. Until then we will be syncing and testing on 50/30 mbps.
CPU: AMD A8 Quad Core 3.2 Ghz
RAM: 2 x 16GB Samsung DDR3 2400 MHz OC
PSU: 650W Cooler Master
and the sweetest thing inside:
V-NAND Samsung SSD 850 EVO Drive
It was such a beautiful and sweet investment on the long term basis, I'm still amazed!
Storage: 250GB
MaxRandom 4K : Up to 97,000 IOPS/88,000 IOPS
Technology : Samsung MGX Controller
So, now according to @furion i'm deploying Ubuntu Xenial 16.04, custom swap and /dev/shm to compensate the missing RAM :)
Few more photos of this SSD beast and beauty...
And a cold beer with @britcoins
To celebrate new tech toy and patiently wait for Ubuntu deployment and configuration :)
Until next update!
Cheers
Are you running a witness node? If so, it would be useful for you to tell people who to vote for at the bottom of your witness related posts.
@timcliff - having your reply is a great honor for me!
Not yet. Building, syncing FULL RPC Node that will have a witness as well yes. I'm going through living hell with it for now with CPU utilization of only one core, but will fight way through!
Post is still not up, because node is still not up. If i can't write in #witness-category even announcement just say so, i will not go against Steem Rules definitely. Here only to help community grow :)
Have you read post entirely ? Have you look my other posts ? :)
I'll skip witness-category until node is done and stable. I know the rules about announcement post and promoting an active witness. But anyway @britcoins and @apasia.tech will be owner + witness so it's not gonna be my post :) I'm just an admin :D
Cheers
Luci
Yes, I have read them. You are welcome to use the tags for this type of post. It is witness related even if you are not a witness yet :) I was just offering the suggestion to add your witness name if you were a witness, since it might help you to get votes.
One thing for your node: Don't run your witness on the same server as a RPC node. The witness node should be it's own server, and the location and IP should be secret.
@timcliff - thanks for the seriously important headsup! And sorry for my stand up at first reply, i'm just having a really bad 24 hours as linux admin :)
From a technical point of view, should i leave witness account and wif empty on Full RPC then in config.ini (but then im getting error on start please configure witness) ? It's starting witness plugin as full node, or it's just configuration for running full node ?
That another IP might be a problem. Since Thai IDC are seriously limited on International Bandwidth, we've ordered fiber 200/100 but only one IP per fiber to our shop in Chonburi. Backup link is 70/50 and besides 2 steem blockchains only few pi 3 are running around for some clients on their own dongles :) Only one PI actually has internet from us as entry point for client :)
So, since witness shouldn't be accessible and rather private to public, is it OK if i run PureVPN with Fixed IP from SG example on witness node ? In that way i'll separate them completely even though they will be in the same rack still on same fiber.
Its been fight over a week. First VPS was having 5mbit limitations, then i've decided to go for dedicated, then i moved completely to private data center building just for graphene, since nothing in Thailand is meeting requirements, or by hardware specs or by bandwidth.
Do you know maybe that switch for MULTI CORE READ for cmake ? I've been scraping pages lite, i really didn't had proper time for more.
Thanks
Luci
Yes. It should give a warning, but it should not prevent it from proceeding.
If it is a full node, it should have all the plugins enabled, including witness.
Well the main thing is that if you move up the ranks for witness, your node could potentially become a target of attack for people wanting to disrupt the steem network. The less information they have, the better. If they would be able to DOS your witness server by knowing the IP of your RPC node - that would probably be bad.
I'm not familiar with that service, but hopefully my answer to the previous question should clarify what is needed.
I don't know the answer to this. If you join the steemit.chat #witness channel and explained what you are trying to do / why, and asked your question there - someone might be able to help.
@timcliff - Hopefully we can grab a beer someday in the future :) At least i own you few for this chit-chat today!
To clear up few things, so we can both sleep well with new node coming:
All instances are having weekly management ( local or co-location ).
Thanks for clarifying witness state and configuration for full RPC node. Will include it with mention in tutorial once chaos calms down.
For a witness node - PureVPN with unique static ip - will do the trick to completely move it somewhere where nobody can know where is it :) In a thin air :D
So, i need one more bright and shiny SSD with high IO :)
Will visit steemit.chat later today to ask for that MULTI CORE read string i know compiler is capable of.... I think it would be helping a lot in --replay-blockchain process :)
Sounds good, glad I could help.