Some thoughts...

[luxas]

cluster-lab

• What happens if the master goes down?
• Should this have port 8400 or 8500? docker run -ti --rm hypriot/rpi-consul members -rpc-addr=192.168.200.1:8400. Now, I saw that consul uses many ports, could you explain which port does what?
• It's more logical for the end user to run systemctl start cluster-lab than cluster-start, why don't start automatically from .deb pkg, where you only enable the services?
• Maybe have an .conf file somewhere, where you may specify e.g. network settings
• Could you combine the two systemd services into one? Or make a cluster-lab service with ExecStart and ExecStop pointing to your files. If required, you can also make a second service which is Before shutdown, which stops cluster-lab

Overall, this is a major step in the right direction After some month of tuning, this will be a very good starting point for enthusiasts like me

kubernetes-on-arm

Can you add my kubernetes-on-arm as a related project? It is very related This week, I'm probably going to release v0.6.2 of my repo, which will feature HypriotOS support. This makes Kubernetes this far away:

# Install
wget <deb file> from github
dpkg -i <deb file>
kube-config install

# After that, kubectl, hyperkube, etcdctl and all required binaries are in $PATH
kube-config enable-master

# Now Kubernetes is up and running...
kubectl get no,po,svc,rc,secrets,serviceAccounts --all-namespaces

# To connect a worker, just do this from another node
kube-config enable-worker [master-ip]

# Spin up dns and a registry as cluster addons
kube-config enable-addon dns
kube-config enable-addon registry

[firecyberice]

• Currently if the master goes down the swarm will crash because only the master node has the swarm manager running. Another master only service is the dhcp server. Do you have an idea how to improve this challenge?
• Yes consul uses many ports 8500 is for http and 8400 is for rpc calls 8301 is for the internal consul communication. It's better to look at the consul docs
• For the last three points please look at https://github.com/hypriot/cluster-lab/blob/master/README.md#roadmap. They are already planned. :-)

[luxas]

OK, what about Kubernetes? Are you guys familiar with it?

[DieterReuter]

@luxas I'm already started working with k8s a few months ago and I'd like to see an upstream ARM support as well.

We've planed to support k8s out-of-the-box or as an additional package to install with a simple apt-get install <k8s-package>. This being said, we will look into your provided package in detail later on.

[MathiasRenner]

@luxas:

• The link to your project in section Related projects is added now. I look forward to your upcoming release! As Dieter pointed out, we will have a closer look at your project as Kybernetes is one of the next steps in the cluster lab.
• There is a link to consul's documentation now, that explains why consul opens several ports.
• The download link to the auto-configuring-and-out-of-the-box-working-cluster-lab SD card image will be published tomorrow, when we release the dedicated blog post. If you cannot wait, here is the download link for you :-) http://downloads.hypriot.com/hypriot-rpi-20151128-152209-docker-swarm-cluster.img.zip

[luxas]

Thanks! @MathiasRenner I commented on some typos, I know it's very small details and everyone understands, but sometimes it just feels better if they are gone :)

BTW, is there any way to comment on a whole file on latest commit?

Another thing,

Swarm will distribute it on the cluster nodes according to a specific algorithm.

At some point in the future, you may explain which strategies you use by default. Is it spread?

@DieterReuter How about your networking consul and k8s? In theory at least, I think it would be possible to use consul instead of flannel

And yeah, we may look at k8s support later on. My project is now ~3 months (fully working). I am very excited to include k8s in here in cluster-lab

[MathiasRenner]

@luxas Thanks for your remarks, awesome! @firecyberice just fixed them. To be honest, I don't know how to comment on only the latest files... sorry. I added a link at the point where the Swarm strategies are mentioned. Yep, we left spread as the default.

[nsteinmetz]

Hey,

Glad to learn here that this "issue" is fixed soon https://github.com/luxas/kubernetes-on-arm/issues/1 :)

As said on blog post, happy to contribute with at least testing and reporting issues. My 2 RPI1 and 2 Cubietruck are available for testing :)

I enabled notification for both projects but don't hesitate to ping me too ;-)

[luxas]

@MathiasRenner @StefanScherer @DieterReuter Check out my v0.6.2 release which features OOTB HypriotOS support and a .deb file for easy k8s installing.

Test it out and comment on it :)