1. 02 May, 2014 4 commits
    • Dimitris Aragiorgis's avatar
      deploy: Add new component GanetiDev · e330e80a
      Dimitris Aragiorgis authored
      
      
      This is used to create a development environment for Ganeti.
      It clones the official repo, installs all packages needed,
      and adds a qa-sample.json file that reflects to the
      Ganeti cluster found in the configuration.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      e330e80a
    • Dimitris Aragiorgis's avatar
      deploy: Add ganeti-qa command · 9093eb07
      Dimitris Aragiorgis authored
      
      
      To install a minimal Ganeti cluster for QA run:
      
       snf-deploy ganeti-qa
      
      This will create a ganeti cluster. The test instances will resolve on
      the local nameserver. On the client node it clones the official repo
      and installs all required packages required for ganeti development.
      A sample qa json file is uploaded under /tmp.
      
      To run the qa go to the client node and run:
      
       # cd ganeti
       # python ganeti-qa.py /tmp/qa-sample.json --yes-do-it
      
      Note that the installed version in the qa cluster should be the same
      used in the qa source.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      9093eb07
    • Dimitris Aragiorgis's avatar
      deploy/ci: Setup lvm in case extra disk exists · 79707d0e
      Dimitris Aragiorgis authored
      
      
      Ganeti needs a VG in order to support plain/drbd disk templates.
      In case an extra disk exists, deploy will create a PV and a VG
      on this disk.
      
      Use options `extra_disk` in nodes.conf and `vg` in ganeti.conf for
      this purpose.
      
      VMs spawned currently during ci do not have extra disks. Update the
      corresponding schema.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      79707d0e
    • Dimitris Aragiorgis's avatar
      deploy: Extract synnefo's components from ganeti · de81d118
      Dimitris Aragiorgis authored
      
      
      The components PithosBackend, Image, GTools, and GanetiCollectd
      are related to Ganeti but used only by Synnefo.
      
      Define new role, named 'snf-ganeti' to include those components and use
      it with the `snf-deploy ganeti` command.
      
      Install ganeti-instance-debootstrap so that we have a working os
      provider.
      
      snf-image takes a lot of time to be configured (curl,
      snf-image-update-helper, wget debian-base image) and is not needed
      for a simple Ganeti cluster (i.e. QA cluster).
      
      Move wget of debian base image to Image component and not nfs.
      In order not to download many times check if it already exists
      in the proper path.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      de81d118
  2. 28 Apr, 2014 3 commits
  3. 14 Apr, 2014 1 commit
    • Vangelis Koukis's avatar
      Switch license to GPLv3 · 02071b96
      Vangelis Koukis authored
      According to the decision of the GRNET Board of Directors,
      switch license to GPLv3.
      
      This commit will be propagated to the release
      and master branches based on git flow, and the next
      release will be licensed as GPLv3.
      02071b96
  4. 31 Mar, 2014 7 commits
  5. 12 Mar, 2014 4 commits
    • Dimitris Aragiorgis's avatar
      deploy: Remove old fabfile · 6f9c1490
      Dimitris Aragiorgis authored
      
      
      ..and replace it with the `fabfile2.py`.
      
      Update Copyright dates.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      6f9c1490
    • Dimitris Aragiorgis's avatar
      deploy/ci: Small refactor regarding ssh/ddns keys · f1efbb09
      Dimitris Aragiorgis authored
      
      
      In case `keygen` founds the keys it does nothing. If `--force` is
      passed then it re-creates the keys.
      
      Currently ci installs the deploy package during `build` command.
      Move keygen action from ci's `deploy_synnefo` phase to the
      `build_synnefo` phase.
      
      Do not use the `--force` flag so that deploy can be re-entrant on
      any level.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      f1efbb09
    • Dimitris Aragiorgis's avatar
      deploy: Add state dir and use it for status · 19fa4790
      Dimitris Aragiorgis authored
      
      
      Introduce new setting in [dirs] section of deploy.conf: `state`.
      Override this setting with `--state-dir` option (useful when running
      deploy from source).
      
      This dir is currently used to store snf-deploy's `snf_deploy_status`
      file, that shows which components on which nodes have been
      installed. Do not update this file if `--dry-run` is used.
      
      Additionally introduce `--templates-dir` option that overrides
      `template` setting in [dirs] section of `deploy.conf`.
      
      Note that override options do not modify the configuration files.
      Changes are performed in the execution context of each snf-deploy
      command.
      
      To run snf-deploy from source use:
      
      $ python setup.py develop
      $ snf-deploy keygen -c conf -t files -s /tmp
      $ snf-deploy all --autoconf -c conf -t files -s /tmp
      
      Add the above setting to snf-ci's schema files.
      
      Update Copyright dates.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      19fa4790
    • Dimitris Aragiorgis's avatar
      deploy: Create the ddns and .ssh dirs · e329c2be
      Dimitris Aragiorgis authored
      
      
      These dirs are needed to store the ddns and .ssh files created by
      snf-deploy keygen. All these files should reside in the template dir
      since are going to be moved to target nodes.
      
      Add those dirs in .gitignore since we don't want to track any temp
      files created if we run snf-deploy from source.
      
      Update Copyright dates.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      e329c2be
  6. 28 Feb, 2014 2 commits
  7. 13 Feb, 2014 3 commits
  8. 03 Feb, 2014 1 commit
  9. 29 Jan, 2014 3 commits
  10. 27 Jan, 2014 1 commit
  11. 21 Jan, 2014 1 commit
  12. 16 Jan, 2014 1 commit
  13. 09 Jan, 2014 3 commits
  14. 08 Jan, 2014 4 commits
    • Dimitris Aragiorgis's avatar
      More pep8 fixes related to snf-deploy · f8c8467d
      Dimitris Aragiorgis authored
      
      
      Those fixes concern errors that are introduced in latest
      pep8 version (and not the wheezy's one).
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      f8c8467d
    • Dimitris Aragiorgis's avatar
      d7dfc73e
    • Dimitris Aragiorgis's avatar
      Huuuuge snf-deploy refactor · df284363
      Dimitris Aragiorgis authored
      
      
      Introduce the concept of Roles and Components.
      
      Roles are ns, mq, db, nfs, astakos, cyclades, pithos, cms, stats,
      ganeti, master, and client.
      
      Each role consists of various SynnefoComponents which  should define:
      
      * commands to check installation prerequisites (check)
      * packages to install (REQUIRED_PACKAGES)
      * commands to prepare installation (prepare)
      * configuration templates (configure)
      * reload commands (restart)
      * initialization commands (initialize)
      * test commands (test)
      
      SynnefoComponents are unaware of fabric environment. They
      get initialized with a Host object and a Env object.
      
      Host includes all the necessary info for the installation node
      (ip, hostname, alias, fqdn..) and Env includes all the configuration info
      (created after parsing config files)
      
      After defining components, fabfile should just do the following:
      
      @roles("somerole")
      def setup_somerole_role():
        SetupSynnefoRole("SomeRole")
      
      In case you want to run a component's specific method just run
      
      RunComponentMethod(SomeComponent, "method_name", *args, **kwargs)
      
      During a role setup you might have to retrieve info from other
      components already installed (user token, backend id, etc.) Use
      'execute' fabric method and fill env object with required info.
      
      Make deployment re-entrant.
      
      Check if specific component is already installed and if yes then skip it.
      
      Currently this is done on node/component level. The component's
      status on a target node is either ok or nothing.
      
      Introduce conflicting components.
      
      Two components might not be able/or should not coexist in the same
      node, e.g. NFS and Mount. These conflicts are defined in CONFLICTS
      dict in roles.py.
      
      Sync ci and deploy conf files.
      
      ci: Change node's password in nodes.conf
      
      Always enable CSRF. Install CMS only if it resides on different
      node than pithos, cyclades and astakos.
      
      Add copyright headers.
      Signed-off-by: default avatarDimitris Aragiorgis <dimara@grnet.gr>
      df284363
    • Dimitris Aragiorgis's avatar
      66fdbb73
  15. 18 Dec, 2013 1 commit
  16. 17 Dec, 2013 1 commit