All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

  1. 10 Mar, 2017 1 commit
  2. 08 Mar, 2017 2 commits
  3. 03 Mar, 2017 1 commit
  4. 01 Mar, 2017 5 commits
  5. 24 Feb, 2017 2 commits
  6. 17 Feb, 2017 4 commits
  7. 15 Feb, 2017 1 commit
  8. 07 Oct, 2016 1 commit
  9. 30 Sep, 2016 3 commits
  10. 28 Sep, 2016 1 commit
  11. 27 Sep, 2016 3 commits
  12. 22 Aug, 2016 1 commit
  13. 10 Jul, 2016 6 commits
    • David Johnson's avatar
      Another round of documentation. · 3f75620c
      David Johnson authored
    • David Johnson's avatar
      Minor bug fix. · 88de2a48
      David Johnson authored
    • David Johnson's avatar
      Many interrelated changes: exceptions, caching, managers. · 84a24fbf
      David Johnson authored
        * Move exceptions into common file.  Ok, this isn't interrelated, but
          it became so, sorry.
        * Move ensure_slice, ensure_sliver into core ElasticSliceManager
          "abstract" interface, from SimpleElasticSliceManager; refactor them
          to split out create_slice and create_sliver as separate methods; and
          expose all these things via ApplicableMethod.
        * Add a new interpretation of the cache-relevant force=(True|False)
          parameter: now if that value is an integer, take that as a max_age
          when querying the cache.  So now the caller can prevent the cache
          from returning non-expired values if the value is older than a
          caller-specified max age.
        * Improve _cache_add to use synchronous ctime/xtime if relevant.
        * Add ctime to CacheNotifier (.added).
        * Add get_sliver_credential().
        * Expose the manager should_add_nodes/add_nodes/delete_nodes methods
          via ApplicableMethod.
        * Change the manager.*add_nodes* methods to accept an additional
          count=N parameter.  If 0, should_add_nodes will make an estimate of
          how many nodes to add them, and add them.  If nonzero, it will see
          if it should add that number of nodes, and do so if allowed.  This
          allows, for instance, a CLI invocation to force multiple nodes to be
          added if possible, even if by default the manager would only add one
          at a time.
        * Add a force= param to ProtoGeniServer.get_wrapped_manifest().
    • David Johnson's avatar
      Manually handle a couple data deps in SimpleElasticSliceManager. · 740ae2c9
      David Johnson authored
      should_add_nodes and should_delete_nodes require that we have certain
      pieces of status and availability data... so make sure we do.
      (Of course this doesn't handle the case of data stale-ness yet...)
    • David Johnson's avatar
      Fix minor bug in should_delete_nodes. · d98a80cb
      David Johnson authored
    • David Johnson's avatar
      Sort the applicable methods. · 2cfe3e9c
      David Johnson authored
  14. 08 Jul, 2016 9 commits