Adding thread to starlingx-discuss@lists.starlingx.io.
From: Kumar, Sharath
Sent: Wednesday, August 12, 2020 10:02 AM
To: Smith, Tyler <tyler.smith@windriver.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>; Das, Ambarish <ambarish.das@intel.com>; Penney, Don <Don.Penney@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Sun, Austin <austin.sun@intel.com>; Eslimi, Dariush <Dariush.Eslimi@windriver.com>; Wold, Saul <saul.wold@intel.com>
Subject: RE: Fault Containerization: Enable FM panels in Openstack Dashboard
Thanks a lot Tyler, it really helps.
From: Smith, Tyler <tyler.smith@windriver.com>
Sent: Wednesday, August 12, 2020 2:18 AM
To: Kumar, Sharath <sharath.kumar@intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>; Das, Ambarish <ambarish.das@intel.com>;
Penney, Don <Don.Penney@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Sun, Austin <austin.sun@intel.com>; Eslimi,
Dariush <Dariush.Eslimi@windriver.com>; Wold, Saul <saul.wold@intel.com>
Subject: RE: Fault Containerization: Enable FM panels in Openstack Dashboard
Thanks Sarath,
Ok I misunderstood the question, to build the flock layer you can use “build-pkgs starlingx-dashboard” to build our existing plugin. “build-pkgs python-django-horizon” will build horizon, but there shouldn’t
need to be any modifications to that.
During development I tend to just copy over any altered files and restart horizon via “sm-restart service horizon”, or using the dev server as you mentioned should be fine too. As for your question from IRC,
the credentials to the dev server would be whatever is setup in keystone. Are you running the dev server on the controller? if not then you'll need to make sure your local_settings file is pointing to the controller via the openstack_host settings and others
as documented here:
https://docs.openstack.org/horizon/latest/contributor/quickstart.html
Tyler
From: Kumar, Sharath [mailto:sharath.kumar@intel.com]
Sent: Tuesday, August 11, 2020 10:47 AM
To: Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>; Smith, Tyler <tyler.smith@windriver.com>; Das, Ambarish <ambarish.das@intel.com>;
Penney, Don <Don.Penney@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Sun, Austin <austin.sun@intel.com>; Eslimi,
Dariush <Dariush.Eslimi@windriver.com>; Wold, Saul <saul.wold@intel.com>
Subject: RE: Fault Containerization: Enable FM panels in Openstack Dashboard
Hi Tyler,
Thank you for your time to let us present and review our approach document in the flock meeting.
As discussed , attaching the approach document we presented today.
To start with our approach, we need help on how to
build GUI package only in the flock layer. As an example, we can build fault using “build-pkg fault” command.
Other queries are highlighted in the approach document. Please let us know if you need any clarifications.
Regards,
Sharath
From: Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>
Sent: Monday, August 10, 2020 10:15 PM
To: Smith, Tyler <tyler.smith@windriver.com>; Das, Ambarish <ambarish.das@intel.com>; Penney, Don <Don.Penney@windriver.com>;
Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Sun, Austin <austin.sun@intel.com>; Eslimi,
Dariush <Dariush.Eslimi@windriver.com>; Kumar, Sharath <sharath.kumar@intel.com>; Wold, Saul <saul.wold@intel.com>
Subject: RE: Fault Containerization: Enable FM panels in Openstack Dashboard
Hello Tyler ,
Would like to give heads-up that Sanjay & Sharath wanted to present the updates on the 2nd approach mentioned in the below email in tomorrow’s community meeting .Hope you could be part of the meeting so that
we can align on the next steps
[Starlingx-discuss] StarlingX Config/DC/Flock/Upgrade Bi-weekly Meeting 6:30am UST/7pm BLR
Regards
Gopi
From: Smith, Tyler <tyler.smith@windriver.com>
Sent: Friday, May 15, 2020 1:35 AM
To: Das, Ambarish <ambarish.das@intel.com>; Penney, Don <Don.Penney@windriver.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>;
starlingx-discuss@lists.starlingx.io; Sun, Austin <austin.sun@intel.com>; Eslimi, Dariush <Dariush.Eslimi@windriver.com>
Subject: RE: Fault Containerization: Enable FM panels in Openstack Dashboard
Hi Ambarish & Sanjay
There were two approaches that were being looked at. The first was to use the same GUI plugin for both the platform horizon and containerized horizon, but only copy over the horizon 'enabled' files corresponding to the panels that we
want to enable (fault panels in the containerized case). This is the approach that was tried but it ended up not working and required lots of hacks during the docker image build step, such as modifying the code, which we really want to avoid. The reasons
it wasn't working weren't really clear to me, I didn't spend time debugging etc.
Attached is some background on what was being discussed then.
The decision was made to instead split our plugin into two, one for the platform panels, and one for just the fault panels. This will involve creating a new package next to starlingx-dashboard (in the same repo though) that has a similar
structure but only has the relevant fault components. Including:
Api/fm.py
Api/rest/fm.py
Dashboards/admin/active_alarms/
Static/dashboard/fault_management/
Enabled/ -> need the fm related enabled files in here, along with the banner view header section definition (see ADD_HEADER_SECTIONS). These files will get copied over in the docker image build step. The only other instruction in
this step should be the csrftoken customization command from the attached email, which I think unfortunately is required.
As for the settings for the containerized horizon, they are stored in the openstack helm application manifest here: openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml
My understanding is fault management will remain in the platform as well. A distributed cloud deployment will also have to be tested, as the dc_admin dashboard also queries fm.
There's decent documentation on the plugin structure upstream:
https://docs.openstack.org/horizon/latest/contributor/tutorials/plugin.html
Let me know if you need more details
Tyler
From: Das, Ambarish [mailto:ambarish.das@intel.com]
Sent: Wednesday, May 13, 2020 2:22 AM
To: Penney, Don <Don.Penney@windriver.com>; Smith, Tyler <tyler.smith@windriver.com>
Cc: Wold, Saul <saul.wold@intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; Bhat, Gopalkrishna <gopalkrishna.bhat@intel.com>;
starlingx-discuss@lists.starlingx.io; Mukherjee, Sanjay K <sanjay.k.mukherjee@intel.com>; Sun, Austin <austin.sun@intel.com>
Subject: Fault Containerization: Enable FM panels in Openstack Dashboard
Hello Tyler & Don,
We have started looking into the remaining work in Fault Containerization and looked into the earlier abandoned patch implementation (https://review.opendev.org/#/c/661423/).
As we have joined the team newly, we would like to understand GUI and Horizon implementation and next steps to move forward regarding this pending activity.
We had a initial discussion regarding this with Saul and Austin and based on their inputs, we would like to have a discussion. Please let me know if you need any clarification.
Thanks & regards,
Ambarish/Sanjay