Skip to content
Snippets Groups Projects
  1. Oct 24, 2018
  2. Oct 23, 2018
  3. Oct 21, 2018
  4. Oct 16, 2018
  5. Oct 12, 2018
  6. Oct 11, 2018
    • shutingm's avatar
      Workflow uses parameter "viewModel.ready" to do the repetitive work. · 35a718a5
      shutingm authored
      In workflow module, every item in navigation used
      'ng-show="viewModel.ready"' to determine whether it should
      be display, it makes no sense to do so, and should replace
      with the item parameter "step.ready" to control itself show
      or hide.
      
      Change-Id: Iadc5c90995022b2e0a13bcd46e4f2de64d1088b5
      Closes-bug: #1797309
      35a718a5
  7. Oct 10, 2018
  8. Oct 09, 2018
  9. Oct 08, 2018
    • Guang Yee's avatar
      support WEBSSO_KEYSTONE_URL · a53f012f
      Guang Yee authored
      Add a new optional WEBSSO_KEYSTONE_URL property to facilitate WEBSSO
      deployments where network segmentation is used per security requirement.
      In this case, the controllers are not reachable from public network.
      Therefore, user's browser will not be able to reach OPENSTACK_KEYSTONE_URL
      if it is set to the internal endpoint.
      
      If WEBSSO_KEYSTONE_URL is set, it will be used instead of
      OPENSTACK_KEYSTONE_URL.
      
      Change-Id: I05ea4227aa4c2cb0a73015ed7fd29cf1a96e696a
      Closes-bug: #1544703
      a53f012f
    • OpenStack Proposal Bot's avatar
      Imported Translations from Zanata · 781c05a7
      OpenStack Proposal Bot authored
      For more information about this automatic import see:
      https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
      
      Change-Id: I0f91c85ba1bf9d09346bb65c62404d6f349e9951
      781c05a7
  10. Oct 07, 2018
    • Gary Kotton's avatar
      Do not raise invalid message when port does not exist · 4ae8850d
      Gary Kotton authored
      The exception handling for port, floating IP's or networks
      is too broad. Add specific error handling and in a case when
      the resource is not found do not raise a invalid message.
      
      Change-Id: I98ee2ff816c03980645752eebb4e39d3ecd2e158
      Closes-bug: #1796565
      4ae8850d
  11. Oct 06, 2018
  12. Oct 05, 2018
  13. Oct 04, 2018
  14. Oct 03, 2018
  15. Oct 02, 2018
  16. Oct 01, 2018
  17. Sep 28, 2018
    • Tobias Urdin's avatar
      Add hide_create_volume to LAUNCH_INSTANCE_DEFAULTS · 13224318
      Tobias Urdin authored
      This adds a new option named hide_create_volume to the
      LAUNCH_INSTANCE_DEFAULTS dict.
      
      With this option you can select if you want to hide
      the "Create New Volume" option to your users and have
      it rely on the default value that is provide with the
      create_volume option.
      
      This is currently the only way to make sure the end-users
      utilizing the web interface is forced to spawn a volume-backed
      instance until Nova supports Cinder as a images backend.
      
      Change-Id: I3a78593ada0d39cc7f1e30fb0a6300887b7b1a00
      13224318
    • BubaVV's avatar
      Hide Swift network info in Horizon error message · 4d6a1b32
      BubaVV authored
      In case of error Swift API return some details about unsuccessful
      request, i.e. internal IP, full object pass, etc. This response is not
      processed by Horizon and presented to user as-is, which is potentially
      insecure. Proposed patch adds error processing striping network location
      from error message
      
      Change-Id: Ieef9669a1be3ed7bbc685a457eb1fe86b34c3c7e
      Closes-bug: #1794767
      4d6a1b32
    • Zuul's avatar
      7094da9a
  18. Sep 27, 2018
    • Edward Hope-Morley's avatar
      Add enabled check in Backups panel · 6c2225ba
      Edward Hope-Morley authored
      If enable_backup is False in OPENSTACK_CINDER_FEATURES
      then we should not display the backups panel.
      
      Change-Id: I276eebf0f11406bf354f5d8bbecef7b244d6d340
      Closes-Bug: #1778771
      6c2225ba
  19. Sep 26, 2018
  20. Sep 25, 2018
    • Radomir Dopieralski's avatar
      Replace @memoized_with_* with @memoized · 3acb2827
      Radomir Dopieralski authored
      Since @memoized now uses weakref to delete old cache entries, and no
      longer keeps the object passed as parameters alive indefinitely, we
      no longer need to treat the Request objects specially. In fact, if
      we stop doing it, it should improve memory use, because now all
      request-specific caches will be removed as soon as the request
      object dies.
      
      I also removed the memoized_with_argconv function, and replaced it
      with an explicit function for converting teh parameters in the one
      place where it was used.
      
      Change-Id: I710b96a170e429c6ffdf22ad3e552ee6e1c6b7e3
      3acb2827
  21. Sep 23, 2018
Loading