metral / corekube

CoreOS + Kubernetes + OpenStack - The simplest way to deploy a POC Kubernetes cluster using a Heat template
Apache License 2.0
7 stars 0 forks source link

multiple networks in private openstack? #5

Closed tomsherrod closed 9 years ago

tomsherrod commented 9 years ago

Thank you for the blog post and this configuration.

When deploying this on a private openstack network, are 2 private networks necessary to create the additional ifaces? Could it all be done on one private network and public ip address accessing it?

Pointers welcome.

Best, Tom

metral commented 9 years ago

Hi Tom,

2 private networks are not necessary in a private openstack setup.

In this setup, which is intended for Rackspace's Public Cloud, there is a Cloud Network used for the sake of privately bridging VM's across different hosts. Flannel is then used as an overlay on top of the Cloud Network because Public Cloud does MAC-based filtering (this prevents the Docker bridge & its veth devices for the containers to communicate with the other Docker bridges / containers across the rest of hosts), so its a great way to get around it.

In a private openstack setup, it is assumed that the hosts are already privately bridged / capable of communicating with each other without any restrictions. Therefore, Cloud Network is not required and Flannel is the only network fabric you would have to use as each Docker container space needs its own individual subnet per Kubernetes requirements.

Hope this helps

metral commented 9 years ago

closing