Skip to main content

Managing Ethereum nodes using Ansible

Our friends as SlingNode have just released their first Open Source project. We know how much work goes into projects like this and wanted to share this on our blog.

The slingnode.ethereum Ansible role, can be used to deploy and configure Ethereum nodes. The role utilizes Docker Compose to deploy the Ethereum Clients. 

The first release supports the following clients:

Execution clients:

  • Geth
  • Nethermind
  • Besu
  • Erigon

Consensus clients:

  • Lighthouse
  • Prysm
  • Teku
  • Nimbus 

Validator clients:

  • Lighthouse
  • Prysm
  • Teku
  • Nimbus
From what we can tell this is the first and only Open Source project that allows for deploying Ethereum servers using Ansible with a focus towards DevOps Teams managing hundreds of servers. 

Check out the documentation:

https://docs.slingnode.com/slingnode.ethereum/

View the role on Ansible-Galaxy:

https://galaxy.ansible.com/slingnode/ethereum

Contribute on GitHub:

https://github.com/SlingNode/slingnode-ansible-ethereum

They have a comprehensive set of example playbooks showing how to deploy Ethereum nodes at scale:

https://github.com/SlingNode/slingnode-ethereum-examples

Good luck to SlingNode Team!

Labels:

Comments

Post a Comment

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier
Post a Comment
Read more

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"
Post a Comment
Read more

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 http://cdpurl.kp.local/crl.crl Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa
Post a Comment
Read more