Public bug reported: During the Mitaka release, Heat released new resources with an additional namespace. They are:
OS::Neutron::LBaaS::LoadBalancer OS::Neutron::LBaaS::Listener OS::Neutron::LBaaS::Pool OS::Neutron::LBaaS::PoolMember OS::Neutron::LBaaS::HealthMonitor The additional namespace is to differ these LBaaS v2 resources from their v1 counterparts. However in the Resource Types list display in Horizon, the LBaaS is displayed as the Resource rather than the resource name. From a Horizon perspective, we shouldn't care about the additional namespace, and just display the resource name. ** Affects: horizon Importance: Undecided Assignee: Bryan Jones (jonesbr) Status: New ** Changed in: horizon Assignee: (unassigned) => Bryan Jones (jonesbr) -- 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/1560219 Title: Orchestration Resource Types does not handle additional namespaces Status in OpenStack Dashboard (Horizon): New Bug description: During the Mitaka release, Heat released new resources with an additional namespace. They are: OS::Neutron::LBaaS::LoadBalancer OS::Neutron::LBaaS::Listener OS::Neutron::LBaaS::Pool OS::Neutron::LBaaS::PoolMember OS::Neutron::LBaaS::HealthMonitor The additional namespace is to differ these LBaaS v2 resources from their v1 counterparts. However in the Resource Types list display in Horizon, the LBaaS is displayed as the Resource rather than the resource name. From a Horizon perspective, we shouldn't care about the additional namespace, and just display the resource name. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1560219/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp