[Starlingx-discuss] Openstackclient will move to a container

[Rowsell, Brent]

Dean,

The openstack services are containerized and are decoupled from the host platform. 
Each time we move to a new openstack I do not think we want to put a dependency on the host platform to upgrade the OSC package and any dependencies, hence the container for local client access. 
Note this is a static container managed by k8s, not dynamically created on each OSC invocation. 

Brent 

-----Original Message-----
From: Dean Troyer [mailto:dtroyer at gmail.com] 
Sent: Wednesday, April 24, 2019 2:42 PM
To: Dinescu, Stefan <Stefan.Dinescu at windriver.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Openstackclient will move to a container

On Wed, Apr 24, 2019 at 12:59 PM Dinescu, Stefan <Stefan.Dinescu at windriver.com> wrote:
> As part of storyboard [0], openstackclients will move from a baremetal installation to being run inside a container.

Perhaps my understanding of the k8s architecture is lacking but I really do not understand exactly why you would want to put a CLI into a container to be called from outside the container.

OSC is already slow enough on startup, adding the overhead of a docker exec (how I am imagining you will actually use it) just makes that even worse.

dt

--
Dean Troyer
dtroyer at gmail.com

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss