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@gmail.com] Sent: Wednesday, April 24, 2019 2:42 PM To: Dinescu, Stefan <Stefan.Dinescu@windriver.com> Cc: starlingx-discuss@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@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@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Hello, Due to the below commits causing sanity to fail, we will be reverting all 3 commits. Work on containerized clients will resume once stx3.0 branch is open. Once the revert commits have been merged please rebase your code to pick up these changes so you can again openstack commands. Thanks, Stefan ________________________________ From: Dinescu, Stefan Sent: Monday, June 10, 2019 5:23 PM To: starlingx-discuss@lists.starlingx.io Subject: RE: Openstackclient will move to a container Hi all, Just a heads-up, the plan is to merge this feature this week. The 3 reviews that are to be merged are [1], [2] and [3]. For now, the baremetal clients will remain installed, so if you encounter any issues with the containerized clients, you can workaround those by using the "platform-openstack" alias. Make sure you update your workflow to take into account this change. As always, if you have any questions, feel free to ask me. Thanks, Stefan [1]: https://review.opendev.org/#/c/654423/16 [2]: https://review.opendev.org/#/c/654424/19 [3]: https://review.opendev.org/#/c/655118/11 ________________________________ From: Dinescu, Stefan Sent: Wednesday, April 24, 2019 8:58 PM To: starlingx-discuss@lists.starlingx.io Subject: Openstackclient will move to a container Hi everyone, As part of storyboard [0], openstackclients will move from a baremetal installation to being run inside a container. The platform openstackclient will only be able to be used for platform services (keystone, barbican). For all other services (nova, glance, cinder etc) the containerized clients must be used. To ensure a smooth transition, the submitted code will include a wrapper so that openstack commands will function as normal. The "openstack" command is aliased to this wrapper and will only be able to be used for the container services. The clients pod will be configured automatically with the correct "clouds.yaml" auth file, so no extra steps are needed to configure the pod. In order to use the platform openstack command, another alias is provided for it: "platform-openstack". You can also access the platform openstack by using the full path of the executable: "/usr/bin/openstack" For the first batch of commits, the platform clients will not be removed, but they are expected to be removed in the following weeks, so please update any automation scripts you might have for this new behavior. If you have any questions regarding this feature/change, feel free to ask me. Thanks, Stefan [0] Storyboard: https://storyboard.openstack.org/#!/story/2005312