Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

domain_type auto-detection documentation clarification #1

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

domain_type auto-detection documentation clarification #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c09e8b2
0.10.1 blogpost
msavy Mar 22, 2012
14a46df
Add warning about possible failure to detect KVM-capable CPUs and men…
verdurin Apr 4, 2012
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions _config/releases.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
- version: 0.10.1
- version: 0.10.0
- version: 0.9.8
- version: 0.9.7
Expand Down
66 changes: 66 additions & 0 deletions blog/2012-03-19-boxgrinder-build-0-10-1-released.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
title: "BoxGrinder 0.10.1 Released"
author: 'Marc Savy'
layout: blog
version: 0.10.1
timestamp: 2012-03-22t15:00:00.10+00:00
tags: [ boxgrinder_build ]
---

The long-awaited BoxGrinder Build 0.10.1 bugfix release is now available; with a variety of irritation eliminating alterations behaviour should be more consistent, and no longer prone to permissions errors.

## Permission denied, log shifting errors
If you have seen any errors akin to:

FATAL -- : Logger::ShiftingError: Shifting failed. Permission denied - log/boxgrinder.log.2 or log/boxgrinder.log.3

The problem was caused when BoxGrinder switched to a local user from root, but the log file could still be owned by root. The issue was only apparent on certain systems, and even then often only occasionally.

## Ruby 1.9
We've made some changes to ensure BoxGrinder runs correctly under Ruby 1.9, with a particular eye towards the forthcoming release of Fedora 17. You can see our earlier [musings](/blog/2012/02/29/preparing-for-fedora-17/) on the changes required.

## Scientific Linux EBS AMIs
OS constraints on the EBS plugin have been removed, so you can now create a Scientific Linux EBS AMIs. As the limitation is generally eliminated, any community OS plugin is also be able to use the EBS plugin.

## Bash tab completions
Basic bash tab completions have been sneaked into this release. Give it a try:

[root@localhost ~]# boxgrinder-build my.appl --
--backtrace --delivery-config --os-config --plugins
--debug --force --platform --trace
--delivery --help --platform-config --version

## Other
Snapshots with the S3 plugin are working correctly again, and some simple testing issues were fixed.

# Release notes

## Bug

* [[BGBUILD-337]] - In SL if default repos are disabled, /etc/yum.repos.d folder is not created
* [[BGBUILD-338]] - Weed out non-deterministic tests
* [[BGBUILD-344]] - Builds on some platforms impossible due to log (and/or other) files still being owned by root after boxgrinder switches to user
* [[BGBUILD-351]] - s3 plugin attempts to create bucket with whole pathname during snapshot

## Enhancement

* [[BGBUILD-349]] - Use RbConfig instead of obsolete and deprecated
Config deprecation warning with Ruby 1.9.3

## Task

* [[BGBUILD-332]] - Add support for bash completion
* [[BGBUILD-346]] - Confirm Ruby 1.9.3 support

# Sub-task

* [[BGBUILD-348]] - Simplecov coverage testing for Ruby >=1.9z

[BGBUILD-337]: https://issues.jboss.org/browse/BGBUILD-337
[BGBUILD-338]: https://issues.jboss.org/browse/BGBUILD-338
[BGBUILD-344]: https://issues.jboss.org/browse/BGBUILD-344
[BGBUILD-351]: https://issues.jboss.org/browse/BGBUILD-351
[BGBUILD-349]: https://issues.jboss.org/browse/BGBUILD-349
[BGBUILD-332]: https://issues.jboss.org/browse/BGBUILD-332
[BGBUILD-346]: https://issues.jboss.org/browse/BGBUILD-346
[BGBUILD-348]: https://issues.jboss.org/browse/BGBUILD-348
2 changes: 1 addition & 1 deletion tutorials/boxgrinder-build-plugins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -740,7 +740,7 @@ All operating systems are supported.
# Default: name-version-release-os_name-os_version-arch-platform
appliance_name: boxgrinder-f16-rocks

***domain_type (String)*** — Libvirt domain type. Default is a calculated value. Unless you are using xml_only the remote instance will be contacted and an attempt to determine the best value will be made. If xml_only is set then a safe pre-determined default is used. User-set values take precedence. See type: [Domain format](http://libvirt.org/formatdomain.html#elements).
***domain_type (String)*** — Libvirt domain type. Default is a calculated value. Unless you are using xml_only the remote instance will be contacted and an attempt to determine the best value will be made. If xml_only is set then a safe pre-determined default is used. User-set values take precedence. Owing to limitations in the library being used to discover hypervisor characteristics, in some cases KVM-capable CPUs may not be detected as such, with the result that the slower QEMU driver will be used. In this situation, users can override the auto-detected value and set it to KVM as shown in the example below. See type: [Domain format](http://libvirt.org/formatdomain.html#elements).
# Default: calculated value, as described above
# Examples:
domain_type: kvm
Expand Down