1. 01 Dec, 2016 2 commits
  2. 28 Nov, 2016 2 commits
  3. 17 Nov, 2016 4 commits
  4. 11 Nov, 2016 7 commits
  5. 07 Nov, 2016 1 commit
  6. 03 Nov, 2016 1 commit
  7. 01 Nov, 2016 3 commits
  8. 27 Oct, 2016 7 commits
  9. 26 Oct, 2016 2 commits
  10. 17 Oct, 2016 3 commits
    • Pedro Alvarez Piedehierro's avatar
      Fix morph upgrade command in trove-upgrade cluster · 24edb7cb
      Pedro Alvarez Piedehierro authored
      Change-Id: Ic4ec5c86e97637cee555bd4e9fffc40a6980ab53
    • Pedro Alvarez Piedehierro's avatar
      .gitlab-ci: Build trove · e150ffad
      Pedro Alvarez Piedehierro authored
      Change-Id: If2f3d130d713b72d67a0437450bec76a83f48e20
    • Pedro Alvarez Piedehierro's avatar
      Upgrade pbr to 0.11.1 to fix build error in python3-core · 1fafceaa
      Pedro Alvarez Piedehierro authored
          + python3 setup.py install --prefix /usr --root /pbr.inst
          Traceback (most recent call last):
            File "setup.py", line 22, in <module>
            File "/pbr.build/pbr/util.py", line 256, in cfg_to_args
            File "/pbr.build/pbr/util.py", line 477, in wrap_commands
              for cmd, _ in dist.get_command_list():
            File "/usr/lib/python3.5/site-packages/setuptools/dist.py", line 447, in get_command_list
              cmdclass = ep.resolve()
            File "/usr/lib/python3.5/site-packages/pkg_resources/__init__.py", line 2235, in resolve
              module = __import__(self.module_name, fromlist=['__name__'], level=0)
            File "/pbr.build/pbr/testr_command.py", line 47, in <module>
              from testrepository import commands
          ImportError: No module named 'testrepository'
      Upgraded also pbr in python2-core for consistency, and not upgraded to
      latest given that some components (like mox3) need pbr's version to be < 1
      Change-Id: I42c278c95e001729ab0b458097301a4be42d3d85
  11. 13 Oct, 2016 3 commits
  12. 12 Oct, 2016 2 commits
  13. 09 Oct, 2016 2 commits
  14. 07 Oct, 2016 1 commit
    • Sam Thursfield's avatar
      Add ostree.write deployment extension · 5bca5fc3
      Sam Thursfield authored
      This is a simple deployment extension to write the results of a Baserock
      build to an OSTree repo.
      See ostree.write.help for more information.
      The Baserock reference systems contain static device nodes, which are
      not supported by OSTree, and are obsolete on Linux systems. To work
      around this problem, I added a strip-device-nodes.configure extension.
      The systems should still work the same as devtmpfs will create the
      device nodes.
      I've tested this by deploying minimal-system-x86_64 to an OSTree repo,
      then checking it out into a temporary directory, creating a read-only
      bind-mount of the temporary directory and chrooting then into it.
      This is only going to be useful for containers systems and chroots for
      the time being. We would need to make some quite major changes to the
      Baserock reference systems to enable deployment to VMs or bare metal
      using OSTree.
      Change-Id: I8556139d118da759360cdc1ce998590b1f50b644