https://github.com/ryotarai/itamae/wiki/Node-Attributes

• current invalid sample code 🆖

$ itamae --node-json node.json recipe.rb
ERROR: "itamae help" was called with arguments ["--node-json", "node.json", "recipe.rb"]
Usage: "itamae help [COMMAND]"

• valid sample code 🆗

$ itamae local --node-json node.json recipe.rb

or

$ itamae ssh --node-json node.json recipe.rb

Using Docker backend, recipes and base image are inseparable in most cases.

from_image "ubuntu:14.04"

execute "some command"

If owner is set and group is not set, set group the same value as owner automatically.

And make delay deprecated.

http://qiita.com/toritori0318/items/00ea2a75c8321aaf9ef6

Now, Specinfra supports multiple backends: mizzy/specinfra#351

• package
• directory
• template
• remote_file (similar to cookbook_file in Chef)
• execute
• local_ruby_block
• service
• user

like https://docs.chef.io/resource_file.html#attributes

https://github.com/ryotarai/itamae/wiki/Ohai-Integration

• current invalid sample code 🆖

$ itamae --ohai local recipe.rb
ERROR: "itamae help" was called with arguments ["--ohai", "local", "recipe.rb"]
Usage: "itamae help [COMMAND]"

• valid sample code 🆗

$ itamae local --ohai recipe.rb

file "/path/to/file" do
  owner "user"
end

• If the file doesn't exist, create an empty new file.
• Otherwise, update attributes of the file without editing the content.

I want to define a resource method

define install_something version: 'release' do
  execute 'install somethiong' do
  command<<-"EOS"
  git clone -b #{params[:version]} https://github.com/user/something
  cd something
  make
  make install
  EOS
  end
end

and, want to run without name like

install_something do
  version 'master'
end

.

What do you think of it and requirement of name @ryotarai ?

reported by @winebarrel

only_if and not_if accept shell command. (Lightchef cannot support ruby block)

execute 'install_something' do
  not_if 'which something'
end

With CoreOS stable (607.0.0) and Itamae v1.2.12, applying remote_file resource causes following error message because CoreOS doesn't have diff(1).

> itamae ssh -h coreos-01 roles/aws/coreos/default.rb
 INFO : Starting Itamae...
 INFO : Recipe: /Users/mirakui/src/itamae_recipes/roles/aws/coreos/default.rb
 INFO :   diff:
 INFO :   /bin/sh: diff: command not found

recipe:

remote_file '/usr/share/oem/cloud-config.yml' do
  owner 'root'
  group 'root'
  mode '0644'
  source 'files/cloud-config.yml'
end

but the applying succeeded.

http://docs.getchef.com/essentials_cookbook_definitions.html

include_recipe "cookbooks/nginx"

If cookbooks/nginx is a directory and cookbooks/nginx/default.rb exists, default.rb will be included.

c.f. http://blog.afistfulofservers.net/post/2012/12/21/promises-lies-and-dryrun-mode/

I want to have provider attribute for service resource which chef has.

In the chef, writing service resource like below allows us to change the service command to upstart.

service "example_service" do
  action :start
  provider Chef::Provider::Service::Upstart
  notifies :restart, "service[nginx]", :immediately
end

Also, with writing a gem like https://github.com/hirose31/chef-provider-service-daemontools, we add a provider Chef::Provider::Service::Daemontools to change the service commands to one of daemontools.

I am willing to implement this, but I want to disscuss the implementation design beforehand.

1) under way

Specinfra has some of check_is_running_under_#{provider} methods already like this, so one way would be to change lib/itamae/resource/service.rb as this patch > https://gist.github.com/sonots/0b601f610b04d2c27cdd. And, add xxx_under_xxx methods to specinfra.

2) module way

Specinfra has Specinfra::Command::Module::Systemd at lib/specinfra/command/module/systemd.rb, so one way would be to support to specify a module with provider attribute, and mixin it on calling run_specinfra by some ways.

3) resource way

Giving up to provide provider attribute, and implement the feature as another resource like

daemontools_service "foo" do
  action :start
end

I think this design is heavily related with the implementation design in specinfra, so it is better to discuss with both @mizzy and @ryotarai.

EDIT: I also want to have provider attribute for package resource like chef > https://docs.chef.io/resource_package.html. Chef allows us to specify provider Chef::Provider::Package::Rpm, also chef provides rpm_package resource in this case.

Please let me know if there is a discussion already.

1. Copy target file to temp dir.
2. Set permission, owner and so on.
3. Move temp file to specific path.

To reduce time to build Docker image, cache images after each recipe provisioned.

remote_file

remote_file "/etc/nginx/conf.d/itamae.conf" do
  source :auto # This is default
end

Itamae will search files/etc/nginx/conf.d/itamae.conf, files/nginx/conf.d/itamae.conf, files/conf.d/itamae.conf and files/itamae.conf under the directory where the recipe exists and use the file found first.

template

template "/etc/nginx/conf.d/itamae.conf" do
  source :auto # This is default
end

Itamae will search templates/etc/nginx/conf.d/itamae.conf.erb, templates/nginx/conf.d/itamae.conf.erb, templates/conf.d/itamae.conf.erb and templates/itamae.conf.erb under the directory where the recipe exists and use the file found first.

action :stop is not work for postgresql-9.3 on Ubuntu 14.04.3.

service "postgresql" do
  action :stop
end

Because, service postgresql status not return "running"

$ sudo service postgresql status
9.3/main (port 5432): online

Temporary fix:

class Specinfra::Command::Ubuntu::Base::Service < Specinfra::Command::Debian::Base::Service
  class << self
    def check_is_running(service)
      "service #{escape(service)} status && service #{escape(service)} status | egrep 'running|online'"
    end
  end
end

Hi, Thank you great tool !

But I have a question with --ohai option.

When I execute itamae without --ohai option to centos 6.5 (virtualbox), node.platform return redhat.
But, I execute itamae with --ohai option to same host, node.platform return centos.

Do you expect this behavior ?

I wonder that I can not write codes depend on node.platform in plugin.

Thanks.

1. vagrant up
2. Configure the server by Lightchef
3. Check if the server is configured properly by Serverspec.

I tried run 'source' command using like this run_command(["source", "~/.bashrc"]), but I got the error below.

ERROR :     stdout | /bin/sh: 1: source: not found
ERROR :     Command `source \~/.bashrc` failed. (exit status: 127)

How can I solve this problem?

@ryotarai

Hi, I'm using drone-0.4-database (pre-release version of drone).

It has docker plugins for other systems such as slack for notification, docker for publish container image using Dockerfile.

and I want to create drone-itamae plugin for publish docker container.

Can I use itamae for drone-itamae?

Thank you.

In order to:

• Make faster
• Shrink log

like this:

node.validate do
  {
    profile: {
      name: required(String),
      age: optional(Integer),
      locations: optional(array_of(String)),
    },
  }
end

itamae init creates directories, template files and Gemfile.