Skip to content
Snippets Groups Projects
  1. Feb 24, 2011
  2. Feb 23, 2011
  3. Feb 22, 2011
  4. Feb 18, 2011
  5. Feb 17, 2011
    • Iustin Pop's avatar
      NodeQuery: mark live fields as UNAVAIL for non-vm_capable nodes · effab4ca
      Iustin Pop authored
      
      Since we don't have the data per design, UNAVAIL is appropriate here,
      while NODATA is not.
      
      The patch also adds a comment: if we extend the live fields list to
      contain other data in the future, we need to reevaluate this solution.
      
      This should fix issue 143. The listing now shows (node2==ofline,
      node3==not vm_capable):
      
        Node     DTotal     DFree    MTotal     MNode     MFree Pinst Sinst
        node1    698.6G    630.5G     32.0G      1.0G     30.0G     8     7
        node2 (offline) (offline) (offline) (offline) (offline)     9     4
        node3 (unavail) (unavail) (unavail) (unavail) (unavail)     0     0
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      effab4ca
  6. Feb 15, 2011
  7. Feb 04, 2011
  8. Feb 02, 2011
  9. Jan 31, 2011
  10. Jan 28, 2011
  11. Jan 27, 2011
  12. Jan 21, 2011
  13. Jan 20, 2011
  14. Jan 18, 2011
    • Iustin Pop's avatar
      query: Change internal result computation · e2d188cc
      Iustin Pop authored
      
      While looking at the query library, I realized that while we have five
      field statuses, making this a 5-dimensional space, four of them are
      shrunk to a single possible value (None). Hence it should be possible to
      convert this into a single value space plus extra 4 special constants.
      
      This patch implements this, making (IMHO) the return value of normal
      functions much simpler: you simply return the desired value, instead of
      (QRFS_NORMAL, value); for the special results, you simply return
      _FS_UNAVAIL, instead of (QRFS_UNAVAIL, None). This I believe does
      simplify the code.
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      e2d188cc
    • Apollon Oikonomopoulos's avatar
      KVM: Perform network configuration in Ganeti · 5d9bfd87
      Apollon Oikonomopoulos authored
      
      This patch introduces network configuration for KVM in Ganeti.
      
      There are three problems with having KVM perform network configuration via ifup
      scripts:
        a) Ganeti never gets to know the tap interface that is associated with an
           instance's NIC
        b) Migration of routed instances will cause network problems because the
           incoming KVM side configures the network as soon as it is spawned and not
           as soon as the migration finishes. This means that all routing
           configuration will be present in both, primary and secondary, nodes at the
           same time, possibly causing network disruption during the migration.
        c) We never get to know if the network configuration succeeded or not.
      
      This patch moves network configuration from KVM to Ganeti, using KVM's ability
      to receive already open tap devices as file descriptors.
      
      _WriteNetScript is removed from hv_kvm.py, together with its unit tests.
      
      Minor modifications are made to _ExecKVMRuntime to handle tap device
      initialization. NIC <-> tap associations are stored under a new directory,
      _ROOT_DIR/nic in a file-per-nic fashion.
      
      The end-user semantics remain the same: The user can override the network
      configuration by providing _KVM_NET_SCRIPT. If this is not present or
      executable, the default constants.KVM_IFUP script is run.
      
      Signed-off-by: default avatarApollon Oikonomopoulos <apollon@noc.grnet.gr>
      Signed-off-by: default avatarGuido Trotter <ultrotter@google.com>
      Reviewed-by: default avatarGuido Trotter <ultrotter@google.com>
      5d9bfd87
    • Iustin Pop's avatar
      Check consistency of the class names and OP_ID · ff0d18e6
      Iustin Pop authored
      
      As the class names should be now consistent with the OP_IDs, we add a
      check for wrongly-defined OP_IDs.
      
      However, the future removal of the hand-coded OP_IDs will render this
      obsolete, so this check is introduced just to make sure that the
      previous renaming patches did the right job, and it will then be
      removed.
      
      The consistency checks require renaming the test opcodes, which were
      using arbitrary names, depending on test author. They are now all
      standardized on OpTest (local scope).
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      ff0d18e6
    • Iustin Pop's avatar
      b469eb4d
    • Iustin Pop's avatar
      Rename OpGetTags and LUGetTags · c6afb1ca
      Iustin Pop authored
      
      Signed-off-by: default avatarIustin Pop <iustin@google.com>
      Reviewed-by: default avatarRené Nussbaumer <rn@google.com>
      Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
      c6afb1ca
Loading