1. 21 May, 2013 4 commits
  2. 20 May, 2013 5 commits
  3. 17 May, 2013 2 commits
  4. 16 May, 2013 6 commits
  5. 15 May, 2013 4 commits
  6. 14 May, 2013 12 commits
  7. 13 May, 2013 4 commits
    • Christos Stavrakakis's avatar
      cyclades: Update 'backend-add' for lazy networks · ac8cb634
      Christos Stavrakakis authored
      Do not create private networks when adding a new backend. Since,
      "lazy networks" this is no longer needed.
      ac8cb634
    • Christos Stavrakakis's avatar
      9283834d
    • Christos Stavrakakis's avatar
      cyclades: Implement lazy networks · 8aff3951
      Christos Stavrakakis authored
      Implement "lazy networks", which are not created to all Ganeti backends
      upon creation, but only when an instance that resides in a Ganeti is
      connected to that network.
      
      Update 'create_network' to create the Network object in DB without
      creating network in Ganeti, or correspoding BackendNetwork entries. The
      state of the Network becomes 'ACTIVE' upon creation, instead of
      'PENDING' that was until now. Also, update 'delete_network' function to
      delete the network only from the backends that it is not in 'DELETED'
      state. The state of the network will become 'DELETED' only when all
      corresponding backend networks become 'DELETED' (including offline
      backends).
      
      Extend code that connects a VM to a network to check if the network
      already exists and is in 'ACTIVE' state in the Ganeti backend that hosts
      the VM.  If not, it will create the network and then connect the VM
      (using Ganeti chained-jobs to ensure correct ordering of jobs).
      
      Update 'reconcile-networks' management command to work with lazy
      networks. Specifically, do not check if private networks exist in all
      backends.
      
      Update 'network-add' management command to create the network in the
      Ganeti, only if a backend is specified.
      
      Finally, when using Ganeti chained-jobs to impose ordering of jobs, do
      not depend only on 'success' of a job, but also on 'error' and 'cancel'.
      This is needed to cover case that a job fails (e.g. create network)
      because the resource already exists.
      8aff3951
    • Christos Stavrakakis's avatar
      cyclades: add commissioning to create/remove cmds · df89c0a7
      Christos Stavrakakis authored
      Update create/remove management commands to issue commission when
      needed.
      df89c0a7
  8. 10 May, 2013 1 commit
  9. 09 May, 2013 2 commits