imagemaster3000 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 44586ae5ff59b3b0fd2b69f3a68b10e986298e46
+  data.tar.gz: 4e031df88184d4fd4d683d2bbe42628a9afc0bb7
+SHA512:
+  metadata.gz: 69b7ec75eb226bdbb807fb093808fb62ee08034a4f0615561dcd08d4160bdb1e57a3b8526668827a5a4dd44af93ac04f8eaa6c2794f56b5078fa987fd2eea30c
+  data.tar.gz: afc4dc785509a3e9ecf5777eb07345bb18ad1914a963c9a94789694712530f5ff5c6aa42ae1f22cdb883a7247f2b646d296c01e983760dcc3376d279ef8ee254

data/.gitignore

@@ -0,0 +1,12 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+example
+/vendor/
+/coverage/

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.rubocop.yml

@@ -0,0 +1,38 @@
+require: rubocop-rspec
+
+AllCops:
+  TargetRubyVersion: 2.0
+  Exclude:
+    - 'vendor/**/*'
+
+Metrics/LineLength:
+  Max: 135
+
+Metrics/MethodLength:
+  Max: 15
+
+Metrics/AbcSize:
+  Max: 20
+
+Style/Documentation:
+  Enabled: false
+
+RSpec/MultipleExpectations:
+  Enabled: false
+
+RSpec/ExampleLength:
+  Enabled: false
+
+RSpec/NestedGroups:
+  Max: 3
+
+Metrics/ParameterLists:
+  Exclude:
+    - 'lib/imagemaster3000/entities/*.rb'
+
+Metrics/BlockLength:
+  Exclude:
+    - 'Rakefile'
+    - '**/*.rake'
+    - 'spec/**/*.rb'
+    - '*.gemspec'

data/.travis.yml

@@ -0,0 +1,22 @@
+sudo: false
+
+language: ruby
+rvm:
+  - ruby-head
+  - 2.2.6
+  - 2.3.3
+  - 2.4.0
+
+matrix:
+  allow_failures:
+    - rvm: ruby-head
+
+fast_finish: true
+
+branches:
+  only:
+    - master
+
+before_install: 'gem install bundler -v 1.15.0'
+
+script: 'bundle exec rake acceptance'

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at kimle.michal@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in imagemaster3000.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,13 @@
+Copyright 2017 Michal Kimle
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,60 @@
+# imagemaster3000
+
+Downloads and slightly modifies cloud images so they can be used in our extraordinary cloud. Simple as that.
+
+## Installation
+
+### From source (dev)
+**Installation from source should never be your first choice! Especially, if you are not
+familiar with RVM, Bundler, Rake and other dev tools for Ruby!**
+
+**However, if you wish to contribute to our project, this is the right way to start.**
+
+To build and install the bleeding edge version from master
+
+```bash
+git clone git://github.com/Misenko/imagemaster3000.git
+cd imagemaster3000
+gem install bundler
+bundle install
+bundle exec rake spec
+```
+
+## Usage
+
+```bash
+Usage:
+  imagemaster3000 start --binaries-guestfish=BINARIES-GUESTFISH --binaries-virt-copy-in=BINARIES-VIRT-COPY-IN --certificate=CERTIFICATE --endpoint=ENDPOINT --group=GROUP --image-dir=IMAGE-DIR --image-list=IMAGE-LIST --key=KEY
+
+Options:
+  [--definitions-dir=DEFINITIONS-DIR]            # If set, definitions in this direcotry are used to download and modify images
+  --image-dir=IMAGE-DIR                          # Directory where to temporarily store images
+                                                 # Default: /var/spool/imagemaster3000/images/
+  --group=GROUP                                  # Group, images will be uploaded to
+                                                 # Default: imagemaster3000
+  --image-list=IMAGE-LIST                        # Name and path of generated image list
+                                                 # Default: /var/spool/imagemaster3000/image-list/imagemaster3000.list
+  --endpoint=ENDPOINT                            # Endpoint where image list will be available
+                                                 # Default: http://localhost/
+  --certificate=CERTIFICATE                      # Certificate to sign image list with
+                                                 # Default: /etc/grid-security/cert.pem
+  --key=KEY                                      # Key to sign image list with
+                                                 # Default: /etc/grid-security/key.pem
+  --binaries-virt-copy-in=BINARIES-VIRT-COPY-IN  # Path to binary needed for 'copy' action
+                                                 # Default: /usr/bin/virt-copy-in
+  --binaries-guestfish=BINARIES-GUESTFISH        # Path to binary needed for 'remove' action
+                                                 # Default: /usr/bin/guestfish
+  --logging-level=LOGGING-LEVEL
+                                                 # Default: ERROR
+                                                 # Possible values: DEBUG, INFO, WARN, ERROR, FATAL, UNKNOWN
+  [--logging-file=LOGGING-FILE]                  # File to write logs to
+                                                 # Default: /var/log/imagemaster3000/imagemaster3000.log
+  [--debug], [--no-debug]                        # Runs in debug mode
+```
+
+## Contributing
+1. Fork it ( https://github.com/Misenko/imagemaster3000/fork )
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request

data/Rakefile

@@ -0,0 +1,17 @@
+require 'rspec/core/rake_task'
+require 'rubocop/rake_task'
+require 'bundler/gem_tasks'
+
+RSpec::Core::RakeTask.new(:spec)
+RuboCop::RakeTask.new
+
+task default: :spec
+
+desc 'Run acceptance tests (RSpec + Rubocop)'
+task test: 'acceptance'
+
+desc 'Run acceptance tests (RSpec + Rubocop)'
+task :acceptance do |_t|
+  Rake::Task['spec'].invoke
+  Rake::Task['rubocop'].invoke
+end

data/bin/imagemaster3000

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require 'imagemaster3000'
+
+Imagemaster3000::CLI.start(ARGV)

data/config/definitions/centos-7.json

@@ -0,0 +1,29 @@
+{
+  "name":"METACLOUD-CentOS-7.3-1704-x86_64@metacloud-dukan",
+  "url":"http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud-1704.qcow2",
+  "verification":{
+    "signature":{
+      "clearsign":{
+        "file":"http://cloud.centos.org/centos/7/images/sha256sum.txt.asc"
+      }
+    },
+    "hash":{
+      "function":"SHA256"
+    }
+  },
+  "distribution":"CentOS",
+  "version":"7.3-1704",
+  "actions":{
+    "copy":[
+      {
+        "source":"centos-cloud.cfg",
+        "target":"/etc/cloud/",
+        "name":"cloud.cfg"
+      },
+      {
+        "source":"serial-getty@ttyS0.service",
+        "target":"/etc/systemd/system/getty.target.wants/"
+      }
+    ]
+  }
+}

data/config/definitions/debian-8.json

@@ -0,0 +1,33 @@
+{
+  "name":"METACLOUD-Debian-8.7.1-x86_64@metacloud-dukan",
+  "url":"https://cdimage.debian.org/cdimage/openstack/current/debian-8.8.1-20170521-openstack-amd64.qcow2",
+  "verification":{
+      "signature":{
+        "detached":{
+          "signature": "https://cdimage.debian.org/cdimage/openstack/current/SHA256SUMS.sign",
+          "data": "https://cdimage.debian.org/cdimage/openstack/current/SHA256SUMS"
+        }
+      },
+      "hash":{
+        "function":"SHA256"
+      }
+  },
+  "distribution":"Debian",
+  "version":"8.8.1",
+  "actions":{
+    "remove":[
+      "/etc/cloud/cloud.cfg.d/90_dpkg.cfg"
+    ],
+    "copy":[
+      {
+        "source":"debian-cloud.cfg",
+        "target":"/etc/cloud/",
+        "name":"cloud.cfg"
+      },
+      {
+        "source":"serial-getty@ttyS0.service",
+        "target":"/etc/systemd/system/getty.target.wants/"
+      }
+    ]
+  }
+}

data/config/definitions/files/centos-cloud.cfg

@@ -0,0 +1,95 @@
+# If this is set, 'root' will not be able to ssh in and they
+# will get a message to login instead as the above $user (ubuntu)
+disable_root: False
+user: root
+ssh_pwauth: False
+ssh_deletekeys: True
+ssh_genkeytypes: ['rsa', 'dsa']
+ssh_svcname: sshd
+
+# This will cause the set+update hostname module to not operate (if true)
+preserve_hostname: false
+cc_ready_cmd: ['/bin/true']
+mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2']
+syslog_fix_perms: ~
+manage_etc_hosts: True
+
+# Update and upgrade system on first boot
+apt_preserve_sources_list: True
+package_update: True
+package_upgrade: True
+package_reboot_if_required: True
+
+# work only with OpenNebula, use network based datasource,
+# so that we can successfully resolve IPv4 based hostname
+disable_ec2_metadata: True
+datasource_list: ['OpenNebula']
+datasource:
+  OpenNebula:
+    dsmode: net
+
+# The modules that run in the 'init' stage
+cloud_init_modules:
+ - migrator
+ - seed_random
+ - bootcmd
+ - write-files
+ - growpart
+ - resizefs
+ - set_hostname
+ - update_hostname
+ - update_etc_hosts
+ - ca-certs
+ - rsyslog
+ - users-groups
+ - ssh
+
+# The modules that run in the 'config' stage
+cloud_config_modules:
+# Emit the cloud config ready event
+# this can be used by upstart jobs for 'start on cloud-config'.
+ - emit_upstart
+ - disk_setup
+ - mounts
+ - ssh-import-id
+ - locale
+ - set-passwords
+ - grub-dpkg
+ - apt-pipelining
+ - apt-configure
+ - package-update-upgrade-install
+ - landscape
+ - timezone
+ - puppet
+ - chef
+ - salt-minion
+ - mcollective
+ - disable-ec2-metadata
+ - runcmd
+ - byobu
+
+# The modules that run in the 'final' stage
+cloud_final_modules:
+ - rightscale_userdata
+ - scripts-per-once
+ - scripts-per-boot
+ - scripts-per-instance
+ - scripts-user
+ - ssh-authkey-fingerprints
+ - keys-to-console
+ - phone-home
+ - final-message
+ - power-state-change
+
+# System and/or distro specific settings
+# (not accessible to handlers/transforms)
+system_info:
+   # This will affect which distro class gets used
+   distro: rhel
+   # Other config here will be given to the distro class and/or path classes
+   paths:
+      cloud_dir: /var/lib/cloud/
+      templates_dir: /etc/cloud/templates/
+   ssh_svcname: sshd
+
+# vim:syntax=yaml

data/config/definitions/files/debian-cloud.cfg

@@ -0,0 +1,101 @@
+# If this is set, 'root' will not be able to ssh in and they
+# will get a message to login instead as the above $user (ubuntu)
+disable_root: False
+user: root
+ssh_pwauth: False
+ssh_deletekeys: True
+ssh_genkeytypes: ['rsa', 'dsa']
+ssh_svcname: sshd
+
+# This will cause the set+update hostname module to not operate (if true)
+preserve_hostname: false
+cc_ready_cmd: ['/bin/true']
+mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2']
+syslog_fix_perms: ~
+manage_etc_hosts: True
+
+# Update and upgrade system on first boot
+apt_preserve_sources_list: True
+package_update: True
+package_upgrade: True
+package_reboot_if_required: True
+
+# work only with OpenNebula, use network based datasource,
+# so that we can successfully resolve IPv4 based hostname
+disable_ec2_metadata: True
+datasource_list: ['OpenNebula']
+datasource:
+  OpenNebula:
+    dsmode: net
+
+# The modules that run in the 'init' stage
+cloud_init_modules:
+ - migrator
+ - seed_random
+ - bootcmd
+ - write-files
+ - growpart
+ - resizefs
+ - set_hostname
+ - update_hostname
+ - update_etc_hosts
+ - ca-certs
+ - rsyslog
+ - users-groups
+ - ssh
+
+# The modules that run in the 'config' stage
+cloud_config_modules:
+# Emit the cloud config ready event
+# this can be used by upstart jobs for 'start on cloud-config'.
+ - emit_upstart
+ - disk_setup
+ - mounts
+ - ssh-import-id
+ - locale
+ - set-passwords
+ - grub-dpkg
+ - apt-pipelining
+ - apt-configure
+ - package-update-upgrade-install
+ - landscape
+ - timezone
+ - puppet
+ - chef
+ - salt-minion
+ - mcollective
+ - disable-ec2-metadata
+ - runcmd
+ - byobu
+
+# The modules that run in the 'final' stage
+cloud_final_modules:
+ - rightscale_userdata
+ - scripts-per-once
+ - scripts-per-boot
+ - scripts-per-instance
+ - scripts-user
+ - ssh-authkey-fingerprints
+ - keys-to-console
+ - phone-home
+ - final-message
+ - power-state-change
+
+# System and/or distro specific settings
+# (not accessible to handlers/transforms)
+system_info:
+   # This will affect which distro class gets used
+   distro: debian
+   # Other config here will be given to the distro class and/or path classes
+   paths:
+      cloud_dir: /var/lib/cloud/
+      templates_dir: /etc/cloud/templates/
+      upstart_dir: /etc/init/
+   package_mirrors:
+     - arches: [default]
+       failsafe:
+         primary: http://ftp.debian.org/debian
+mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2']
+manage_etc_hosts: true
+
+# vim:syntax=yaml