1. 04 May, 2015 4 commits
  2. 16 Mar, 2015 2 commits
  3. 02 Mar, 2015 4 commits
  4. 27 Feb, 2015 2 commits
  5. 26 Feb, 2015 12 commits
  6. 12 Dec, 2014 4 commits
  7. 19 Nov, 2014 3 commits
  8. 17 Nov, 2014 1 commit
  9. 10 Nov, 2014 1 commit
  10. 07 Nov, 2014 6 commits
    • Stavros Sachtouris's avatar
    • Stavros Sachtouris's avatar
      Support old history files · 96b09136
      Stavros Sachtouris authored
      Fixes grnet/kamaki#80
      Kamaki history files must have an offset counter on the first line,
      since version 0.11.
      With this fix, kamaki supports older history files and adds the
      default offset counter at the first line.
    • Stavros Sachtouris's avatar
      Return volume metadata in "create_volume" · a26565ac
      Stavros Sachtouris authored
      The method used to return results in this format:
        {"volume": {"id": ..., "display_name" ..., ...}}
      It now returns the results in this form:
        {"id" ..., "display_name" ..., ...}
      as it is the case with every other creation command in kamaki library.
    • Stavros Sachtouris's avatar
      Write a set of short scripts using the kamaki lib · e3132145
      Stavros Sachtouris authored
      Fixes grnet/kamaki#49
    • Stavros Sachtouris's avatar
      Update general information and setup instructions · 28dd8a05
      Stavros Sachtouris authored
      Refs grnet/kamaki#49
    • Stavros Sachtouris's avatar
      Check server status before changing it · 19522a57
      Stavros Sachtouris authored
      Fixes grnet/kamaki#57
      This fix affects the CLI commands "server_start", "server_reboot"
      and "server_shutdown" which are specified in "kamaki.cli.cmds.cyclades".
      These are the operations that modify the status of a server.
      The problem was caused when the target status was the same as the current.
      In this case, the request for status modification would fail with a 400
      error code response. At this point, kamaki couldn't have adequate information
      to correctly evaluate the error.
      This problem is solved by checking the current status before attempting to
      modify it.  Also, the server ID is validated in advance, instead of waiting
      for a 400 server error.
  11. 06 Nov, 2014 1 commit
    • Stavros Sachtouris's avatar
      Escape logged HTTP data before token replacement · 26115ba5
      Stavros Sachtouris authored
      Problem: when LOG_DATA is on and LOG_TOKEN is off, kamaki logs HTTP
      data, replaces the token (if it is included in the data) and then
      escapes them to prepare for safe logging. If the data is non-ascii,
      replacing raises a unicode error.
      Solution: escape data before replacing the token.