Skip to content
Manage Solaris Zones
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib/puppet
locales
readmes
spec
.fixtures.yml
.gitattributes
.gitignore
.gitlab-ci.yml
.pdkignore
.project
.puppet-lint.rc
.rspec
.rubocop.yml
.sync.yml
.travis.yml
.yardopts
CHANGELOG.md
CODEOWNERS
Gemfile
LICENSE
README.md
REFERENCE.md
Rakefile
appveyor.yml
metadata.json

README.md

zone

Table of Contents

  1. Description
  2. Setup - The basics of getting started with zone
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Description

The zone_core module is used to manage Solaris zone resources.

Setup

Setup Requirements

The zone_core module depends on the zfs_core module, as a zone may be associated in a zfs resource pool.

Usage

To create a zone resource with the name tstzone in the running state and the root of the zone filesystem in /tstzones/mnt, use the following code:

zone { 'tstzone' :
  ensure => running,
  path   => '/tstzones/mnt'
}

Reference

Please see REFERENCE.md for the reference documentation.

This module is documented using Puppet Strings.

For a quick primer on how Strings works, please see this blog post or the README.md for Puppet Strings.

To generate documentation locally, run the following command:

bundle install
bundle exec puppet strings generate ./lib/**/*.rb

This command will create a browsable \_index.html file in the doc directory. The references available here are all generated from YARD-style comments embedded in the code base. When any development happens on this module, the impacted documentation should also be updated.

Limitations

This module is only available on Solaris platforms.

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

For more information, see our module contribution guide.

You can’t perform that action at this time.