magnum

Author	SHA1	Message	Date
Hongbin Lu	44b2e77979	Enable SELinux in swarm bay SELinux is an important security features. We need to turn it on after cloud-init. This patch did that for swarm. Change-Id: I1862a63498613535741c3aae9c0378911ec21315 Partial-Bug: #1543308	7 years ago
Hongbin Lu	424ebb42ec	Revert "Turn selinux back on after cloud-init" This reverts commit `cf85c5ac03`. The kube-scheduler failed to spin up after that commit. As a result, the k8s bay is not functioning. I would suggest to revert that commit first if we cannot figure out a quick fix. Closes-Bug: #1551648 Change-Id: If7f8164368be3eec39f9a795a5e7748af68a6f48	7 years ago
Corey O'Brien	cf85c5ac03	Turn selinux back on after cloud-init After cloud-init has run configuration steps, turn on selinux again for security reasons. Change-Id: I12a5b2ff3e71be39aa84093fce8b1c2b1be9d473 Closes-Bug: 1543308	7 years ago
Hua Wang	37b731b510	Rename heat-kubernetes, heat-mesos, docker-swarm Rename heat-kubernetes to kubernetes, heat-mesos to mesos, docker-swarm to swarm in templates. We use heat templates and no other methods, so I think it is unnecessary to add heat before coe. kubernetes, mesos, swarm are better than heat-kubernetes, heat-mesos, docker-swarm. Change-Id: I257b35c1c4ef55d3172095736f550f2c55c8d81f Closes-Bug: #1514682	7 years ago