1. 24 Sep, 2013 17 commits
  2. 23 Sep, 2013 1 commit
  3. 18 Sep, 2013 6 commits
  4. 17 Sep, 2013 5 commits
    • Christos Stavrakakis's avatar
      Bump version to 0.14.6rc3 · 3fa28799
      Christos Stavrakakis authored
    • Kostas Papadimitriou's avatar
      helpdesk: Exclude nics of deleted vms · 2e66630b
      Kostas Papadimitriou authored
      when helpdesk users search using ip address
    • Christos Stavrakakis's avatar
      cyclades: Mock vm removal if creation fails · a2daae31
      Christos Stavrakakis authored
      In case creating a VM fails before the OP_INSTANCE_CREATE job is
      enqueued in Ganeti, the VM and its NICs must be deleted, and the
      resources must be released from Quotaholder, which is exactly what is
      done when a VM is deleted from Ganeti. Instead of duplicating the code,
      this commit uses the same function that is used by snf-dispatcher, by
      mocking an successfully OP_INSTANCE_REMOVE.
    • Christos Stavrakakis's avatar
      cyclades: Fix bug during server creation · baae8e7f
      Christos Stavrakakis authored
      Commit #32a0b85, modified server creation, by refetching the object from
      DB after issuing commission to quotaholder. However, the new object is
      not having the 'config_url' attributed, which is added to the vm object
      by the 'vmapi'. This commit, fixes this by moving the signal dispatching
      code after refetching the vm. Also, this commit makes more clear the
      exception handling code, when the creation job can not be enqueued to
    • Sofia Papagiannaki's avatar
      pithos: Fix pithos-manage-account command · 57328c5d
      Sofia Papagiannaki authored
      * Disable by default failure reports
        during container quota updates
  5. 16 Sep, 2013 9 commits
  6. 13 Sep, 2013 1 commit
  7. 12 Sep, 2013 1 commit
    • Giorgos Korfiatis's avatar
      cyclades: Do not save stale objects after a commit · 9b94fc30
      Giorgos Korfiatis authored
      Call to issue_and_accept_commission saves the resource object (eg a vm)
      and commits the transaction. This has the side-effect that the resource
      object becomes stale: its lock is released and another thread may acquire
      it and update the db record. It is thus not safe to further update and then
      save the stale object, since this would override others' changes. Instead,
      lock and fetch the object again, where needed.