yahoo-eng-team team mailing list archive

[Radomir Dopieralski <1259458@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It's possible in Horizon to have the panels grouped into PanelGroups in
the menu, but unfortunately that is not reflected in the filesystem
structure of the panel source files. We found a way of grouping related
panels together into packages by using dot notation, like this:

class DeploymentOverview(horizon.Panel):
    name = _("Overview")
    slug = "deployment.overview"

class Deployment(horizon.PanelGroup):
    slug = "deployment"
    name = _("Deployment")
    panels = (
        'deployment.overview',
        'deployment.controller',
        'deployment.compute',
        'deployment.object_storage',
        'deployment.block_storage',
    )

This works fine with panel autodiscovery and would be a perfect solution
for this problem, if not for one detail -- the URL generated for such a
panel looks like: /infrastructure/deployment.overview/

This can be easily fixed by a small change in how the URLs of the panels
are generated.

** Affects: horizon
     Importance: Undecided
     Assignee: Radomir Dopieralski (thesheep)
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1259458

Title:
  Group related panels into packages

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  It's possible in Horizon to have the panels grouped into PanelGroups
  in the menu, but unfortunately that is not reflected in the filesystem
  structure of the panel source files. We found a way of grouping
  related panels together into packages by using dot notation, like
  this:

  class DeploymentOverview(horizon.Panel):
      name = _("Overview")
      slug = "deployment.overview"

  class Deployment(horizon.PanelGroup):
      slug = "deployment"
      name = _("Deployment")
      panels = (
          'deployment.overview',
          'deployment.controller',
          'deployment.compute',
          'deployment.object_storage',
          'deployment.block_storage',
      )

  This works fine with panel autodiscovery and would be a perfect
  solution for this problem, if not for one detail -- the URL generated
  for such a panel looks like: /infrastructure/deployment.overview/

  This can be easily fixed by a small change in how the URLs of the
  panels are generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1259458/+subscriptions