Skip to content
Snippets Groups Projects
  1. Sep 24, 2019
  2. Sep 23, 2019
  3. Sep 10, 2019
  4. Sep 06, 2019
  5. Sep 05, 2019
  6. Aug 30, 2019
  7. Aug 27, 2019
    • Camille Rodriguez's avatar
      Avoid pollution and false positives with tox.ini · 47d00b72
      Camille Rodriguez authored
      - removing sitepackages in tox.ini to avoid test env pollution
      - skip_missing_interpreters in tox.ini set to False to avoid false
      positives by skipping missing interpreters.
      
      Change-Id: I61f1ab26748ad9c2f008fb0d8f003fc2aa28d841
      47d00b72
  8. Aug 26, 2019
    • Camille Rodriguez's avatar
      Add disco-stein bundle to gate tests. · 1497395c
      Camille Rodriguez authored
      The bundle disco-stein was in the dev_bundles because
      a bug with the Python 3.7 syntax prevented the success of
      the deployment of HA clusters. This bug is fixed, we can
      reintegrate disco-stein in the gate_bundles.
      
      Other minor adds:
      - Changing naming convention for vip: 'Amulet' is deprecated.
      - Passing OS env vars
      
      LP Related-Bug: #1823719
      Change-Id: I787248ad2983858c6db2e5a838270a128dae717a
      1497395c
  9. Aug 23, 2019
  10. Aug 19, 2019
  11. Aug 17, 2019
  12. Aug 13, 2019
  13. Aug 08, 2019
  14. Aug 07, 2019
    • Alex Kavanagh's avatar
      Ensure that keystone service is paused if needed on series upgrade · 21d212cb
      Alex Kavanagh authored
      During series upgrade, the keystone packages get re-installed as the
      underlying Linux has been upgraded and new package sets are updated and
      then pulled in.  For trusty->xenial this means that keystone.service
      gets enabled which then breaks haproxy.  On install, on xenial+, the
      keystone.service is disabled in the install hook.  This just replicates
      this in the series-upgrade hook.
      
      Change-Id: Ic5ed6cf354d5545b9e554e205a048955a381e0f5
      Closed-Bug: #1839021
      21d212cb
  15. Jul 30, 2019
  16. Jul 17, 2019
  17. Jul 16, 2019
  18. Jul 08, 2019
  19. Jul 03, 2019
    • James Page's avatar
      Ensure federated identity backend are TLS aware · 15250435
      James Page authored
      When the certificates endpoint has completed TLS configuration
      via Vault, ensure that any federated identity backends are
      updated for the switch to TLS, other the generated SP data
      incorrectly used http:// instead of https://
      
      Closes-Bug: 1834442
      
      Change-Id: Ie160095789f5c34bc3509ffce4a7c5c0ec430632
      15250435
  20. Jun 20, 2019
  21. May 24, 2019
    • Chris MacNaughton's avatar
      Retarget Zaza to master now that split has landed · c765303a
      Chris MacNaughton authored
      This change is required as Zaza underwent a split of the openstack
      tests from the Zaza project, so we had to track the working branch
      until that change landed. As it has landed, it is now time to use
      Zaza from master again
      
      Change-Id: I74a7ba7bb75312d2c55eea0434bd7f68007972c4
      c765303a
  22. May 16, 2019
    • David Ames's avatar
      Use AuthMethod context · a103c15e
      David Ames authored
      Rather than use hard coded auth methods, use the protocal named passed
      over the keystone-fid-service-provider relation.
      
      Also, when using federation do not allow the "external" method as they
      are mutually exclusive.
      
      Change-Id: I08f0632630d7f0e8d2d7ddb057e02f9febf9ad6f
      Closes-Bug: #1828015
      Closes-Bug: #1828018
      a103c15e
  23. May 10, 2019
  24. May 09, 2019
    • Chris MacNaughton's avatar
      Migrate to split zaza - zaza.openstack · 7d444d9d
      Chris MacNaughton authored
      This change adds in zaza.openstack, as well as changing the
      branch target of zaza to a branch with zaza.openstack
      removed, allowing us to validate the new library
      
      Change-Id: Ie6deb30bc01afdc9bddfb91c975d031bfa4b0060
      7d444d9d
  25. May 07, 2019
  26. May 02, 2019
  27. May 01, 2019
  28. Apr 30, 2019
  29. Apr 26, 2019
  30. Apr 25, 2019
    • David Coronel's avatar
      Added status_set and logs to upgrade-charm hook · f01c34d7
      David Coronel authored
      When running an upgrade of the keystone charm in a large environment,
      the upgrade process can take more than 30 minutes.
      
      Prior to this change, the user would only see 'Installing apt packages'
      during most of the process.
      
      This change adds status_set and log messages to the upgrade charm hook
      so that end users can see what is the status of the upgrade.
      
      Change-Id: I1eade73fad551310ceec0bb8dcbccb777737faeb
      Closes-Bug: #1782004
      f01c34d7
  31. Apr 24, 2019
  32. Apr 19, 2019
  33. Apr 17, 2019
  34. Apr 16, 2019
Loading