[Starlingx-discuss] Containerizing the StarlingX Infrastructure

[Wang, Hai Tao]

Hi Miller,

Thanks for the minutes.

I missed the sync and have a question as below.
*        If trying to run an application, where will it run? Will it be possible to run apps in containers? Answer: Yes (Some limitations: eg: no high performance networking, multi-tenant limitation)
Does this limitation mean that we will not implement "privileged container", i.e., with full access to host,  for nova-compute, libvirt, and Neutron agents being containerized?

Thanks
Haitao

From: Miller, Frank [mailto:Frank.Miller at windriver.com]
Sent: Wednesday, October 03, 2018 3:27 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Containerizing the StarlingX Infrastructure

Folks:

I captured notes from this morning's presentation:

*        Brent presented this chart package for Containerization of StarlingX Infrastructure:  https://wiki.openstack.org/wiki/Containerizing_StarlingX_Infrastructure
*        Some questions/answers that came up during the presentation:
*        Which configs will move to this containerized infrastructure?  Answer: All configs will get the containerized configuration.
*        For 1 and 2 node configurations, CEPH will run on the controllers.
*        Where will RBD provisioner run?  Answer: it will run in the cube space.
*        If trying to run an application, where will it run? Will it be possible to run apps in containers? Answer: Yes (Some limitations: eg: no high performance networking, multi-tenant limitation)
*        Containerized OpenStack services will require us to build our own docker images and those images will be CentOS based.
*        Can we generate these docker images using other O/S's?  Answer: This will be a design consideration.
*        Will it be possible to put docker images on docker hub?  Answer: Where to put the images will be looked at as part of one of the StoryBoards for this initiative.
*        Does the customer network share the same physical network with cluster? Answer: Networks may be physically the same but a different logical network will be used for the cluster.
*        Will software update change?  Answer: Yes - we will be moving toward a k8s approach to update software/containers.
*        Can you provide some schedule info? Answer: Target is for the March release.  Specs are expected to be out in the next 1-2 weeks.
*        If community folks are interested in participating please contact Brent or Frank.
*        In future, to containerize the flock will the decoupling of the flock need to be completed?  Answer: No - there is no direct dependency on the decoupling work.

Frank


-----Original Appointment-----
From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com]
Sent: Saturday, September 29, 2018 10:38 AM
To: Rowsell, Brent; starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Containerizing the StarlingX Infrastructure
When: Tuesday, October 02, 2018 10:00 AM-11:00 AM (UTC-05:00) Eastern Time (US & Canada).
Where: https://zoom.us/j/342730236


Folks,

Setting up this call to give the community an overview of the StarlingX infrastructure containerization initiative.
Hope you can join.

Thanks,

Brent


  << File: ATT00001.txt >>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181003/9cb25e44/attachment-0001.html>