1. 13 May, 2014 1 commit
  2. 12 May, 2014 1 commit
  3. 08 Apr, 2014 3 commits
  4. 05 Mar, 2014 1 commit
  5. 04 Mar, 2014 2 commits
  6. 28 Feb, 2014 1 commit
  7. 27 Feb, 2014 2 commits
  8. 19 Feb, 2014 2 commits
  9. 13 Feb, 2014 3 commits
    • Jose A. Lopes's avatar
      Connect new groups to the instance communication network · 39e27230
      Jose A. Lopes authored
      
      
      When a new group is added, if the instance communication network is
      enabled, then this group must also be connected to this network.
      
      * 'LUGroupAdd._AddInstanceCommunicationNetwork' connects the newly
        added group to the instance communication network by resorting to
        the 'OpNetworkConnect' opcode.
      
      * As a result of the previous change, the type of 'OpGroupAdd' changed
        and may optionally return a list of jobs.  Therefore, it is
        necessary to update the type of the opcode (in 'Ganeti.OpCodes') and
        the CLI for 'gnt-group add' must also be changed.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      39e27230
    • Jose A. Lopes's avatar
      'LUClusterSetParams' creates the instance communication net · d6a7518a
      Jose A. Lopes authored
      
      
      Extend 'LUClusterSetParams' to create the user-supplied instance
      communication network in case this network does not exist.  Note that
      if the user-supplied network already exists, nothing needs to be done
      as 'CheckPrereq' already checks this network's configuration.
      
      With this patch, Ganeti will be able to create the instance
      communication network automatically.  The following example shows the
      command line options that instruct Ganeti to enable the instance
      communication network and, if this network does not exist, then Ganeti
      creates it.
      
        gnt-cluster modify --instance-communication-network=mynetwork
      
      The instance communication network can be disabled by setting the
      parameter to the empty string, for example:
      
        gnt-cluster modify --instance-communication-network=
      
      This will not destroy the network itself or modify any running
      instances.  This will have to be done manually.
      
      In this patch:
      
      * 'LUClusterSetParams._EnsureInstanceCommunicationNetwork' creates and
        connects to all groups the instance communication network by
        resorting the 'OpNetworkAdd' and 'OpNetworkConnect'.
      
      * 'LUClusterSetParams.ModifyInstanceCommunicationNetwork' compares the
        previous configured 'instance_communication_network' with the
        user-supplied one and determines whether the opcodes is changing the
        configuration, which might require creating the instance
        communication network.
      
      * Extend 'LUClusterSetParams.Exec' to call
        'ModifyInstanceCommunicationNetwork' and handle the user-supplied
        'instance_communication_network'.
      
      * Because 'ClusterSetParams' now may return a list of jobs, the type
        of the opcode must be updated in 'Ganeti.OpCodes'.
      
      * Add network related constants to 'Ganeti.Constants'.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      d6a7518a
    • Jose A. Lopes's avatar
      Add 'instance_communication_network' to 'OpClusterSetParams' · 42fda604
      Jose A. Lopes authored
      
      
      ... and update the unit tests.
      Signed-off-by: default avatarJose A. Lopes <jabolopes@google.com>
      Reviewed-by: default avatarHelga Velroyen <helgav@google.com>
      42fda604
  10. 10 Feb, 2014 1 commit
  11. 07 Feb, 2014 4 commits
  12. 06 Feb, 2014 1 commit
  13. 16 Jan, 2014 1 commit
  14. 20 Dec, 2013 1 commit
    • Helga Velroyen's avatar
      Verify incoming RPCs against candidate map · b3cc1646
      Helga Velroyen authored
      
      
      From this patch on, incoming RPC calls are checked against
      the map of valid master candidate certificates. If no map
      is present, the cluster is assumed to be in
      bootstrap/upgrade mode and compares the incoming call
      against the server certificate. This is necessary, because
      neither at cluster initialization nor at upgrades from
      pre-2.11 versions a candidate map is established yet.
      
      After an upgrade, the cluster RPC communication continues
      to use the server certificate until the client certificates
      are created and the candidate map is populated using
      'gnt-cluster renew-crypto --new-node-certificates'.
      
      Note that for updating the master's certificate, a trick
      was necessary. The new certificate is first created under
      a temporary name, then it's digest is updated and
      distributed using the old certificate, because otherwise
      distribution will fail since the nodes don't know the
      new digest yet. Then the certificate is moved to its
      proper location.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      b3cc1646
  15. 17 Dec, 2013 1 commit
  16. 13 Dec, 2013 1 commit
  17. 29 Nov, 2013 1 commit
  18. 26 Nov, 2013 4 commits
  19. 21 Nov, 2013 1 commit
    • Dimitris Aragiorgis's avatar
      Introduce --hotplug-if-possible option · 96ed3a3e
      Dimitris Aragiorgis authored
      
      
      This will be useful for an external entity using RAPI that
      wants to modify devices of instances.
      
      The common use case for that is:
      "I want to add a NIC/disk to an instance. If it is running
      then try to hotplug the device. If not, then just add it to config."
      
      Another use case is that if we are unaware of the instance's
      hypervisor: "I want do add a NIC/disk to an instance and if
      its hypervisor is KVM try to hotplug it."
      
      For all those cases just print a warning in CheckPrereq() and
      disable any further hotplug related actions (and let
      modifications take place after reboot).
      
      Add NoHoplugSupport and HotplugIfPossible unittests an modify
      existing by explicitly creating successful RPC results for
      call_hotplug_supported.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      Signed-off-by: default avatarThomas Thrainer <thomasth@google.com>
      Reviewed-by: default avatarThomas Thrainer <thomasth@google.com>
      96ed3a3e
  20. 08 Nov, 2013 1 commit
  21. 29 Oct, 2013 4 commits
  22. 24 Oct, 2013 1 commit
  23. 15 Oct, 2013 1 commit
  24. 11 Oct, 2013 1 commit
    • Helga Velroyen's avatar
      Correct properties of the cluster's file storage dir · 5ce621ab
      Helga Velroyen authored
      
      
      This patch does:
      - Rename the haskell opcode parameter
        'pGlobalFileStorageDir' and 'pGlobalSharedfileStorageDir'
        to 'pClusterFileStorageDir' and
        'pClusterSharedfileStorageDir', respectively, because
        the old name was misleading.
      - The two parameters are made optional strings instead of
        non-empty strings. This actually used to be like this
        before, but was accidentally overriden by the switch to
        opcode generation from haskell to python.
      - The ClusterFileStorageDir parameter had to be renamed in
        Haskell to not clash with the FileStorageDir parameter
        of the OpInstanceCreate code.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarMichele Tartara <mtartara@google.com>
      5ce621ab