Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
#!/usr/bin/env python | |
def host_groups_to_knife(hosts_config, output_file="knife_commands.sh"): | |
"""Converts Nagios hosts config to knife role from file commands.""" | |
file = open(hosts_config, 'r') | |
output = "#!/bin/bash\n" | |
for line in file: |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats
Currently the kubeadm config and workflow is centered around a single control plane node and any number of worker nodes. This requires additional workarounds when trying to bootstrap and manage clusters with an HA control plane. I believe there is a path forward that would help streamline the effort required to stand up a fully managed HA control plane including etcd.