Open Stack

Steve,actually Kub is moving to fully containerize model when you need only kublet running at the host (https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html) and all other services will come in containers (e.g. ui http://kubernetes.io/v1.0/docs/user-guide/ui.html). So we will have only etcd, flannel, kublet preinstalled and kublet will start all necessary containers (e.g. https://review.openstack.org/#/c/240818/).

Wanghua, we discussed concerns about curent Fedora Atomic images during the summit and there are some actions points:
1. Fix CoreOS template. I started working at it, but it will take some time because we need to coordinate it with template refactoring (https://review.openstack.org/#/c/211771/)
2. Try to minimize Fedora Atomic image (Ton, will take a look at it)
3. Build Ubuntu image/template (I or Ton will pickup it, feel free to join ;))

―
Egor

From: "Steven Dake (stdake)" <stdake at cisco.com<mailto:stdake at cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, November 2, 2015 at 06:37
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum]generate config files by magnum

The reason we don’t rely on cloudint more then we already do (sed is run via cloudiit) is because many modern distress like CentOS and Fedora Atomic have many parts of the host os as read-only.

I prefer the structure as it is.

Regards
-steve


From: 王华 <wanghua.humble at gmail.com<mailto:wanghua.humble at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, November 2, 2015 at 12:41 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [magnum]generate config files by magnum

Hi forks,

Magnum needs to prepare config files for k8s and docker and add these services to systemd. Now we use "sed" to replace some parameters in config files. The method has a disadvantage. Magnum code  depends on a specific image. Users may want to create images by themselves. The config files in their images may be different from ours. I think magnum shouldn't depends on the config files in the image. These config files should be generated by magnum. What magnum needs should be just the installation of k8s, docker, etc. Maybe we can use cloud-init to install the softwares automatically, so that we don't need to create images and what we needs is just a image with cloud-init.

Regards,
Wang Hua