vdloo

Hypernode | Full Stack Developer | Amsterdam, The Netherlands | Full-Time | ONSITE | https://www.hypernode.com Industry: Web Hosting, Web Technology | Company size: 11-50 people | Company type: Private Technologies: Python, Django, Vue.js, Linux (Debian) Hypernode by Byte is a software engineering company, developing a PaaS for e-commerce, recently released on the international market. We are looking for a Python developer to join our web team to help us take on the challenge of providing the best possible managed hosting experience for our customers.

Our stack consists of mostly Django, Django REST framework, Vue.js and Docker Compose but we utilize many different technologies. We value code quality, write automated tests (unit and integration), code review is standard, and we practice continuous development.

Your responsibilities would include development on our control panel, internal and customer facing APIs, command-line tooling and working with many different systems (from cloud automation to invoicing).

For more details check out: https://www.hypernode.com/career/full-stack-developer/ or apply via email at jobs[at]hypernode.com.

Hypernode | Full Stack Developer | Amsterdam, The Netherlands | Full-Time | ONSITE | https://www.hypernode.com Industry: Web Hosting, Web Technology | Company size: 11-50 people | Company type: Private Technologies: Python, Django, Vue.js, Linux (Debian)

Hypernode by Byte is a software engineering company, developing a PaaS for e-commerce, recently released on the international market. We are looking for a Python developer to join our web team to help us take on the challenge of providing the best possible managed hosting experience for our customers.

Our stack consists of mostly Django, Django REST framework, Vue.js and Docker Compose but we utilize many different technologies. We value code quality, write automated tests (unit and integration), code review is standard, and we practice continuous development.

Your responsibilities would include development on our control panel, internal and customer facing APIs, command-line tooling and working with many different systems (from domain registration to invoicing).

For more details check out: https://www.hypernode.com/career/full-stack-developer/ or apply via email at jobs[at]hypernode.com.

Hypernode | Full Stack Developer | Amsterdam, The Netherlands | Full-Time | ONSITE | https://www.hypernode.com Industry: Web Hosting, Web Technology | Company size: 11-50 people | Company type: Private

Technologies: Python, Django, Vue.js, Linux (Debian)

Hypernode by Byte is a software engineering company, developing a PaaS for e-commerce, recently released on the international market. We are looking for a Python developer to join our web team to help us take on the challenge of providing the best possible managed hosting experience for our customers.

Our stack consists of mostly Django, Django REST framework, Vue.js and Docker Compose but we utilize many different technologies. We value code quality, write automated tests (unit and integration), code review is standard, and we practice continuous development.

Your responsibilities would include development on our control panel, internal and customer facing APIs, command-line tooling and working with many different systems (from domain registration to invoicing).

For more details check out: https://www.hypernode.com/career/full-stack-developer/ or apply via email at jobs[at]hypernode.com.

Hypernode | Python developer with Linux experience | Amsterdam, The Netherlands | Full-Time | ONSITE | https://www.hypernode.com

Industry: Web Hosting, Web Technology | Company size: 11-50 people | Company type: Private

Technologies: Python, Ansible, SaltStack, Linux (Debian), Django

Hypernode by Byte is a software engineering company, developing a PaaS for e-commerce, recently released on the international market. We are looking for a Python developer that knows his/her way around the command-line to help us take on the challenge of providing the best possible managed hosting experience for our customers.

Our stack consists of mostly Python, Ansible, SaltStack, Linux (Debian) and Django but we utilize many different technologies. We value code quality, write automated tests (unit and integration), code review is standard, and we practice continuous delivery. We operate a whole spectrum of different services from Docker and Debian repositories to a fairly large ELK-stack and our systems integrate with multiple cloud APIs like AWS, Digitalocean and our in-house OpenStack

Your responsibilities would include development on our cloud-automation system, internal and customer facing APIs, command-line tooling and working with many different systems (from DNS to invoicing) managed by various configuration-management environments.

For more details check out: https://www.hypernode.com/careers/python-developer-linux-exp... or apply via email at jobs[at]hypernode.com.

We upgraded a whole fleet of AWS / Digitalocean instances without floating IPs from Ubuntu Precise to Xenial based on this method back in the summer of 2017. While obviously not having to do crazy stuff like this would be better, it's nice to know that it is possible if you really need it.

https://www.reddit.com/r/programming/comments/6o7i8p/dont_ru...

Recently we ran into another use-case for this in production actually, we needed to wipe a lot of servers in our datacenter remotely and we figured one of the options would be to install some OS in memory with the relevant wiping tools, pivot_root to that, unmount all disks and then perform the wipe. In the end we went a different route and opted for a custom PXE-boot image instead that the servers would boot into that scripted the whole thing.

This is very cool. I'm wondering if decentralized overlay 'mesh' networks will become more prevalent in the future. Overlays have obvious benefits for multi-cloud setups if latency isn't an issue for the services you run through the network. I can imagine this becoming a more popular technique in the future as cloud instances become cheaper and more people are willing to make the performance trade-off for convenience. Additionally it can be a great pattern to fight vendor lock-in.

I run a similar concoction for my 'home network' which consists of various mobile devices like my Android phone and some cloud servers, but instead of ZeroTier and I use CJDNS in combination with Consul. The code for it is on github in the vdloo/raptiformica repo. I ran into various issues with the difference in latency between nodes. I think most people run Consul in a very homogeneous environment (like in one datacenter), but maybe perhaps the differences between using it cross-cloud is not enough to cause problems. I'm wondering if there were some Consul settings that the author had to tweak (and how) for stability and if there were any unexpected issues.

One thing that caused me problems with Consul on overlay networks was an ARP cache overflow. DigitalOcean also ran into that running Consul at scale in their DC if I recall correctly: http://youtu.be/LUgE-sM5L4A I noticed that if I put enough Dockers on one host (like 50 - 100) in an overlay network and tried to run Consul on top of that things would start to overflow, presumably because of all the network abstraction and redundancy. I'm wondering how many machines the author had in one Consul cluster and if they tested to what amount of nodes this setup could scale.

you can also use the API for this https://developers.digitalocean.com/documentation/v2/#change...

for example for precise the kernel ID is 7515 for the "DigitalOcean GrubLoader v0.2 (20160714) Ubuntu" kernel. If you do this be sure to double-check the id by listing the kernels using the API though. You can also do this with libcloud using 'ex_change_kernel' from the 'DigitalOcean_v2_NodeDriver'

cjdns is amazing. I've been using it for a while now as a decentralized vpn. It is really powerful to just be able to link machines together in a network where each node can reach each node as long as at least one other node can connect to that node. For example, I have two machines behind one router and two machines behind another router. Only one in each zone is approachable from the internet, and not always both (due to dynamic residential IPs for example). With cjdns all machines can access all machines as long as there is at least one path that can be traversed from the source machine to the destination, transparently hopping through intermediary machines if necessary. Even if the source machine can not reach the destination machine, but the destination can reach the source there is no problem because of the UDP tunneling.

This is really cool, I recently finished chapter 1 and this really puts in perspective how much there is left to explore.