jesta witness update - 2016-09-23steemCreated with Sketch.

in #witness-category4 years ago

Hardfork 14 went well, upgraded all the nodes I control, updates to the sites I run, and finished my last full week of 40hr/week contract work. Feels like a pretty accomplished week!

I also finished setting up my control center for my witness operations, which you can see below.

Imgur

The left side is both of my witness nodes, the right side contains my price feed, a script to watch every missed block as it happens, and my failover script to swap between witnesses in case of an outage. I can finally sleep a little easier knowing that if one of my witness nodes goes down, the other will come online automatically.

1. Accomplished the week of 2016-09-23:

  • Implemented and announced a update to steemdb.com, including updates for 0.14.2, new features, and new APIs that are being used in a number of projects by other people.
  • Created a how-to guide for securing your funds using the new savings feature.
  • Participated in hardfork 14 and the upgrade to 0.14.2, upgrading both of my witness nodes.
  • Upgraded the NA region of node.steem.ws to 0.14.2.
  • Upgraded steemstats.com to support new operation types in 0.14.2.
  • Finally finished setting up automatic failovers for my witness node (thanks to @furion for getting update_witness working in piston!). The script also sends me an SMS message upon failure so I know I need to investigate what's going on.
  • Setup #witness-blocks in steemit.chat which reports all missed blocks by all witnesses.
  • Adjusted my price feed to offset and assist in maintaining the SBD peg (as suggested by @dantheman earlier in the week).
  • Spent Sunday/Monday further developing/discussing future business plans within the steem ecosystem.
  • Finished my last full week of contract work! Freeeeeedom!

2. Upcoming projects/goals

  • I'm planning on actually taking a bit of time off over the next week. I really haven't taken a day/night off in the last few months. This week I think it'll be a bit lighter for me, unless something happens that requires my attention. I'm also a bit under the weather, so I feel it'll be a wise decision to do so.
  • October/November are shaping up to be 100% dedicated to steem related projects - excited to get some announcements out for what's to come.
  • I want to write a post about potential additional benefits of holding steem power. I've been gathering/brainstorming notes for weeks on how to make powering up more appealing, it's almost to a point where I have enough meat to write an article.
  • I just recently started recording custom_json operations on steemdb. I'd like to surface that information on steemdb in the near future. Hopefully it'll lead to seeing who followed who, and when.
  • Continue learning how reactjs works in evaluation for a potential steemstats revamp.
  • I'm on the search for a good asia/pacific region dedicated server (~32gb RAM) for a decent price. Also on the lookout for one in the EU region (screw heitzner and their verification lol). If anyone's got recommendations, I have a few more nodes I'd like to setup.

3. Thoughts from this week

There's been a lot of division in the community over the past couple weeks, specifically over voting patterns and content creation. I don't think that any of this is actually healthy for the growth of the platform and I question whether we should be supporting these efforts.

Right now there are two groups at odds, neither of which I fall into. We have a group of smaller accounts complaining about what content is getting voted upon, and we have a small group of larger accounts who are being targeted based on their activity. People are digging into each other and essentially attacking the actions of others, accusing people of things based on subjective opinions and limited knowledge.

I'd like to see this stop, it's not helping. Right now we are all playing by the same rules in the same game. Anyone can create small accounts, create content, and any account can become a whale with proper investment. In fighting between these groups solves nothing, and I'd encourage everyone participating in this activity to stop attacking each other and start looking for ways the system could be changed for the better.

The technology behind this platform is far too valuable to deface over stupid drama like this. Let's all try to be a bit more respectable towards each other and actually look for a solution :P

4. Previous week's update

Update for the week ending 2016-09-16

Finally, don't forget to vote for witnesses here.

Sort:  

To bad to see so much negativity lately on steemit. A lot of energy thrown away.

It really is, there's so much effort being poured into those efforts by people right now. I really don't think any of that effort is going to do much good :(

Thank you for posting. Principle....Confusion results in adversity.

Great post @jesta! I especially like how you are taking the server/node setup so seriously, and your comments about reducing the Steem drama :) I really look forward to more updates on the projects you are working on!

That's a great mission control! Which Linux distro is that? Looks nice

It's OSX, an iTerm2 window :)

Thanks for the update. I agree in-fighting doesn't help any of us.

Glad to see I vote for the right person. Thanks for taking Dans advice on the SBD peg.

Finished my last full week of contract work! Freeeeeedom!

Congrats!!!

I'd encourage everyone participating in this activity to stop attacking each other and start looking for ways the system could be changed for the better.

Well said. Thanks Jesta. My pride in this community comes from the work of people like you. I hope you get a nice break and get to feeling better right away.

Keep up the good work! You're a merit to the Steem community :)

What does the failover script do exactly to switch between nodes? What happens if there are two nodes, and one goes down, without the script?

There are 3 components to what I'm currently running:

  • Witness Server (Primary) - Uses Key 1
  • Witness Server (Backup) - Uses Key 2
  • Failover Script (Controller)

The failover script lives on a 3rd server (currently my laptop, which is always online). The script continually monitors the total_missed field on my witness account, and once it hits a certain threshold, triggers an update_witness command to update the signing key from Key 1 to Key 2.

So each of my witness servers all have unique keys, and to swap servers, I just need to issue that command on the blockchain.