Enable network services at Kub master

It's common practice
(https://github.com/kubernetes/kubernetes/tree/master/cluster) to run
network services (kube-proxy and flannel) at master. E.g. you can use
NodePort
(http://kubernetes.io/v1.0/docs/user-guide/services.html#type-nodeport)
for opening services to outside cluster. Flannel will be used later for
Kub services containerization (e.g.
https://review.openstack.org/#/c/240818)

Change-Id: I25b5f3c5931dab5d410702ab3737eea2f207ec35

magnum/templates/heat-kubernetes/fragments/enable-services-master.sh

@@ -4,7 +4,7 @@
 systemctl daemon-reload
 
 echo "starting services"
-for service in etcd kube-apiserver kube-scheduler kube-controller-manager; do
+for service in etcd kube-apiserver kube-scheduler kube-controller-manager kube-proxy; do
     echo "activating service $service"
     systemctl enable $service
     systemctl --no-block start $service

magnum/templates/heat-kubernetes/kubecluster.yaml

@@ -315,6 +315,9 @@ resources:
         - protocol: tcp
           port_range_min: 6443
           port_range_max: 6443
+        - protocol: tcp
+          port_range_min: 30000
+          port_range_max: 32767
 
   secgroup_kube_minion:
     type: OS::Neutron::SecurityGroup

magnum/templates/heat-kubernetes/kubemaster.yaml

@@ -251,6 +251,12 @@ resources:
       group: ungrouped
       config: {get_file: fragments/kube-examples.yaml}
 
+  network_service:
+    type: OS::Heat::SoftwareConfig
+    properties:
+      group: ungrouped
+      config: {get_file: fragments/network-service.sh}
+
   master_wc_notify:
     type: OS::Heat::SoftwareConfig
     properties:
@@ -290,6 +296,7 @@ resources:
         - config: {get_resource: enable_services}
         - config: {get_resource: write_network_config}
         - config: {get_resource: network_config_service}
+        - config: {get_resource: network_service}
         - config: {get_resource: kube_examples}
         - config: {get_resource: master_wc_notify}