Right now, I don’t have a clear forecast for when these changes (stx-gui) will land into a build since new workarounds are tested and implemented as more “incompatibilities” are being found with upstream (horizon/pike). Good news is that, the most tedious longest task, which is packing all of WRS customizations done to horizon framework, the API layer and other utility functions for quotas, etc. is being exhaustively tested and documented<https://etherpad.openstack.org/p/stx-gui> for future reference. We will continue sending incoming changes to two different repos for some time: stx-gui and the stx-horizon<https://github.com/starlingx-staging/stx-horizon>. I will review them and make necessary adjustments to make them work on stx-gui as several LoCs and files are being moved around. From: "Rowsell, Brent" <Brent.Rowsell@windriver.com> Date: Friday, July 13, 2018 at 6:04 PM To: "Ramirez, Eddie" <eddie.ramirez@intel.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] Plan for stx-gui Thanks Eddie. Do you have a forecast when your changes will be done ? Reason I am asking is we have some changes that will need to go into stx-gui. Thanks, Brent From: Ramirez, Eddie [mailto:eddie.ramirez@intel.com] Sent: Thursday, July 12, 2018 5:56 PM To: Rowsell, Brent <Brent.Rowsell@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Plan for stx-gui Hi Brent, sorry I missed this email last week. Short answer: No, it’s not currently being pulled into the building pipeline just yet. I’m trying workarounds to get it working with the last version of Pike. Most of problems I run into are related to changes done to non-panels files like core classes, functions and settings that make STX specific functionality possible. I’m few steps away from trying these changes in the build process as I’m working on a dev environment and following the standard installation process of installing a Horizon plugin, that is, using the upstream horizon release and importing the package stx-gui into the namespace. From: "Rowsell, Brent" <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>> Date: Thursday, July 12, 2018 at 2:29 PM To: "starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>" <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Re: [Starlingx-discuss] Plan for stx-gui Reposting. Does anyone have this on their to do list ? Brent From: Rowsell, Brent Sent: Wednesday, July 4, 2018 3:43 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Plan for stx-gui What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent

I share your concerns of proposing big changes, however there will be an initial “big one” that packs deep changes to the structure of the project. Subsequent patches should be smaller and focused on functionality or theme. Patch on gerrit: https://review.openstack.org/#/584201/ On 7/19/18, 12:18 PM, "Dean Troyer" <dtroyer@gmail.com> wrote: On Thu, Jul 19, 2018 at 1:37 PM, Ramirez, Eddie <eddie.ramirez@intel.com> wrote: > We will continue sending incoming changes to two different repos for some > time: stx-gui and the stx-horizon. I will review them and make necessary > adjustments to make them work on stx-gui as several LoCs and files are being > moved around. I don't see any activity in either repo, where is this being done? I think it will be better to roll it out in reviewable chunks rather than drop the whole thing at once, is this possible? dt -- Dean Troyer dtroyer@gmail.com