[英]Vagrant & Puppet - Provisioning Failing
我正在利用我的第一次Foray使用Vagrant + Puppet Provisioning腳本來改進我的開發工作流程。
我目前正在嘗試為L4開發設置一個開發盒 - 我正在使用https://github.com/paolooo/vagrant-lamp和https://github.com/paolooo/puppet-laravel 。
按照說明:
克隆燈箱:
git clone git://github.com/paolooo/vagrant-lamp.git lamp
cd lamp
添加Puppet配置腳本:
git submodule add https://github.com/paolooo/puppet-laravel.git extras/modules/laravel
然后更新子模塊:
git submodule update --init --recursive
到目前為止很棒 - 簡單的東西......
所以現在准備好運行vagrant up
- 這似乎可以提供虛擬機,並啟動它。
然而,當init.pp腳本運行時,我的問題似乎就開始了。 當apt-get <<package>>
運行時,我得到了很多404。
我的第一個想法是網絡接口可能已關閉 - 但mysql-client
下載工作(我認為)查看日志。
我在OSX和Windows機器上試過這個。
任何幫助都會非常感激 - 我不想陷入第一道障礙。
我的Puppet腳本:
# Default path
Exec { path => ['/usr/bin', '/bin', '/usr/sbin', '/sbin', '/usr/local/bin', '/usr/local/sbin', '/opt/local/bin'] }
exec { 'apt-get update':
command => '/usr/bin/apt-get update --fix-missing',
require => Exec['add php54 apt-repo']
}
# Configuration
if $db_name == '' { $db_name = 'development' }
if $db_location == '' { $db_location = '/vagrant/db/development.sqlite' }
if $username == '' { $username = 'root' }
if $password == '' { $password = '123' }
if $host == '' { $host = 'localhost' }
# Setup
## PHP
include php54
class { 'php': version => latest, }
## APACHE2
include apache
class {'apache::mod::php': }
## PACKAGES
## 'vim','curl','unzip','git','php5-mysql','php5-sqlite','php5-mcrypt','php5-memcache',
## 'php5-suhosin','php5-xsl','php5-tidy','php5-dev','php5-pgsql','php5-odbc', 'php5-ldap','php5-xmlrpc','php5-intl','php5-fpm'
package { ['vim','curl','unzip','git','php5-mcrypt','php5-memcached']:
ensure => installed,
require => Exec['apt-get update'],
}
package { ['php5-mysql','php5-sqlite']:
ensure => installed,
require => Exec['apt-get update'],
}
include pear
include composer
### Apache
apache::vhost { $fqdn:
priority => '20',
port => '80',
docroot => $docroot,
logroot => $docroot, # access_log and error_log
configure_firewall => false,
}
a2mod { 'rewrite': ensure => present }
## Ruby
class { "ruby":
gems_version => "latest"
}
## Nodejs
class { "nodejs": }
## PHP MODULES
php::module { ['curl', 'gd']:
notify => [ Service['httpd'], ],
}
## PEAR
pear::package { "PEAR": }
pear::package { "PHPUnit":
version => "latest",
repository => "pear.phpunit.de",
require => Pear::Package["PEAR"],
}
pear::package { "Yaml":
version => "latest",
repository => "pear.symfony.com",
require => Pear::Package["PEAR"]
}
## DB
### MySQL
class { 'mysql::server':
config_hash => { 'root_password' => "${password}" }
}
class { 'mysql': }
mysql::db { "${db_name}":
user => "${username}",
password => "${password}",
host => "${host}",
grant => ['all'],
charset => 'utf8',
}
### PostgreSQL
class { 'postgresql':
version => 'latest',
}
class { 'postgresql::server': }
postgresql::db { "${db_name}":
owner => "${username}",
password => "${password}",
}
### SQLite Config
class { 'sqlite': }
define sqlite::db(
$location = '',
$owner = 'root',
$group = 0,
$mode = '755',
$ensure = present,
$sqlite_cmd = 'sqlite3'
) {
file { $safe_location:
ensure => $ensure,
owner => $owner,
group => $group,
notify => Exec['create_development_db']
}
exec { 'create_development_db':
command => "${sqlite_cmd} $db_location",
path => '/usr/bin:/usr/local/bin',
refreshonly => true,
}
}
## phpmyadmin
class { 'phpmyadmin': }
我的流浪文件:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant::Config.run do |config|
# All Vagrant configuration is done here. The most common configuration
# options are documented and commented below. For a complete reference,
# please see the online documentation at vagrantup.com.
# Every Vagrant virtual environment requires a box to build off of.
config.vm.box = "precise32"
# The url from where the 'config.vm.box' box will be fetched if it
# doesn't already exist on the user's system.
config.vm.box_url = "http://files.vagrantup.com/precise32.box"
# Boot with a GUI so you can see the screen. (Default is headless)
# config.vm.boot_mode = :gui
# Assign this VM to a host-only network IP, allowing you to access it
# via the IP. Host-only networks can talk to the host machine as well as
# any other machines on the same network, but cannot be accessed (through this
# network interface) by any external networks.
config.vm.network :hostonly, "192.168.33.10"
# Assign this VM to a bridged network, allowing you to connect directly to a
# network using the host's network device. This makes the VM appear as another
# physical device on your network.
# config.vm.network :bridged
# Forward a port from the guest to the host, which allows for outside
# computers to access the VM, whereas host only networking does not.
config.vm.forward_port 80, 8082
# Share an additional folder to the guest VM. The first argument is
# an identifier, the second is the path on the guest to mount the
# folder, and the third is the path on the host to the actual folder.
config.vm.share_folder "v-data", "/vagrant/db", "./db"
config.vm.share_folder "v-web", "/vagrant/www", "c:\\www"
# Enable provisioning with Puppet stand alone. Puppet manifests
# are contained in a directory path relative to this Vagrantfile.
# You will need to create the manifests directory and a manifest in
# the file base.pp in the manifests_path directory.
#
# An example Puppet manifest to provision the message of the day:
#
# # group { "puppet":
# # ensure => "present",
# # }
# #
# # File { owner => 0, group => 0, mode => 0644 }
# #
# # file { '/etc/motd':
# # content => "Welcome to your Vagrant-built virtual machine!
# # Managed by Puppet.\n"
# # }
#
config.vm.provision :puppet do |puppet|
puppet.facter = {
"fqdn" => "dev.lamp.mysql",
"hostname" => "www",
"docroot" => "/vagrant/www",
"host" => 'localhost',
"username" => 'root',
"password" => '123',
"db_name" => "development",
"db_location" => "/vagrant/db/development.sqlite"
}
puppet.manifests_path = "puppet/manifests"
puppet.module_path = ["puppet/modules", "extras/modules"]
puppet.manifest_file = "init.pp"
end
# Enable provisioning with chef solo, specifying a cookbooks path, roles
# path, and data_bags path (all relative to this Vagrantfile), and adding
# some recipes and/or roles.
#
# config.vm.provision :chef_solo do |chef|
# chef.cookbooks_path = "../my-recipes/cookbooks"
# chef.roles_path = "../my-recipes/roles"
# chef.data_bags_path = "../my-recipes/data_bags"
# chef.add_recipe "mysql"
# chef.add_role "web"
#
# # You may also specify custom JSON attributes:
# chef.json = { :mysql_password => "foo" }
# end
# Enable provisioning with chef server, specifying the chef server URL,
# and the path to the validation key (relative to this Vagrantfile).
#
# The Opscode Platform uses HTTPS. Substitute your organization for
# ORGNAME in the URL and validation key.
#
# If you have your own Chef Server, use the appropriate URL, which may be
# HTTP instead of HTTPS depending on your configuration. Also change the
# validation key to validation.pem.
#
# config.vm.provision :chef_client do |chef|
# chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
# chef.validation_key_path = "ORGNAME-validator.pem"
# end
#
# If you're using the Opscode platform, your validator client is
# ORGNAME-validator, replacing ORGNAME with your organization name.
#
# IF you have your own Chef Server, the default validation client name is
# chef-validator, unless you changed the configuration.
#
# chef.validation_client_name = "ORGNAME-validator"
end
似乎問題是正在執行的apt-get更新注釋,不確定為什么會出現這種情況,因為我的Puppet腳本似乎已正確配置以調用它...
但是 - 我能夠通過在我的Vagrant文件中添加以下行來解決此問題:
config.vm.provision :shell, :inline => "apt-get update --fix-missing"
很想知道木偶配置有什么問題,因為能夠避免將其放在Vagrant文件中會很好。
首先,您引用了一些未包含在帖子中的類,因此我無法對這些類進行評論。
看起來你有一個木偶訂購問題; 我建議再次運行它並確定哪些特定的軟件包部署失敗並確定它們屬於哪個類。 因此,例如,如果類y中的某些包x失敗,請在相關類的結束括號之前將以下內容添加到init腳本中 -
class y {
package { "x":
ensure => installed,
}
Exec["apt-get update"] -> Class["y"]
}
以上將確保apt-get update
在任何類'y'配置運行之前完成。
或者,對於包資源類型,您可以繼續添加 -
require => Exec ['apt-get update'],但我發現類訂購更整潔。
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.