config/puppet-modules-wrs/puppet-sysinv/src/sysinv
Mingyuan Qi 611a68a96a Allow user specified registries for config_controller
Currently docker images were pulled from public registries during
config_controller. For some users, the connection to the public
docker registry may be slow such that installing the containerized
services images may timeout or the system simply does not have
access to the public internet.

This change allows users to specify alternative public/private
registries to replace k8s.gcr.io, gcr.io, quay.io and docker.io.
Insecure registry is supported if all default registries were
replaced by one unified registry. It lowers the complexity for
those who build his own registry without internet access.

Docker doesn't support ipv6 addr as registry name, instead
hostname or domain name in ipv6 network is allowed.

Test:
AIO-SX/AIO-DX/Standard(2+2):
  Alternative public registry (ipv4/domain) with proxy
    - config_controller pass
  Private registry (ipv4/ipv6/domain) without internet
    - config_controller pass
  Default registry with/without proxy
    - config_controller pass

Story: 2004711
Task: 28742

Change-Id: I4fee3f4e0637863b9b5ef4ef556082ac75f62a1d
Signed-off-by: Mingyuan Qi <mingyuan.qi@intel.com>
2019-02-23 10:10:07 +08:00
..
lib/puppet StarlingX open source release updates 2018-05-31 07:35:52 -07:00
manifests Allow user specified registries for config_controller 2019-02-23 10:10:07 +08:00
spec StarlingX open source release updates 2018-05-31 07:35:52 -07:00
.fixtures.yml StarlingX open source release updates 2018-05-31 07:35:52 -07:00
Gemfile StarlingX open source release updates 2018-05-31 07:35:52 -07:00
LICENSE StarlingX open source release updates 2018-05-31 07:35:52 -07:00
Modulefile StarlingX open source release updates 2018-05-31 07:35:52 -07:00
README.md StarlingX open source release updates 2018-05-31 07:35:52 -07:00
Rakefile StarlingX open source release updates 2018-05-31 07:35:52 -07:00

README.md

sysinv

Table of Contents

  1. Overview - What is the sysinv module?
  2. Module Description - What does the module do?
  3. Setup - The basics of getting started with sysinv
  4. Implementation - An under-the-hood peek at what the module is doing
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Contributors - Those with commits
  8. Release Notes - Notes on the most recent updates to the module

Overview

The sysinv module is a part of Stackforge, an effort by the Openstack infrastructure team to provide continuous integration testing and code review for Openstack and Openstack community projects not part of the core software. The module its self is used to flexibly configure and manage the block storage service for Openstack.

Module Description

The sysinv module is a thorough attempt to make Puppet capable of managing the entirety of sysinv. This includes manifests to provision such things as keystone endpoints, RPC configurations specific to sysinv, and database connections. Types are shipped as part of the sysinv module to assist in manipulation of configuration files.

This module is tested in combination with other modules needed to build and leverage an entire Openstack software stack. These modules can be found, all pulled together in the openstack module.

Setup

What the sysinv module affects

  • sysinv, the block storage service for Openstack.

Installing sysinv

example% puppet module install puppetlabs/sysinv

Beginning with sysinv

To utilize the sysinv module's functionality you will need to declare multiple resources. The following is a modified excerpt from the openstack module. This is not an exhaustive list of all the components needed, we recommend you consult and understand the openstack module and the core openstack documentation.

Define a sysinv control node

class { '::sysinv':
  sql_connection      => 'mysql://sysinv:secret_block_password@openstack-controller.example.com/sysinv',
  rabbit_password     => 'secret_rpc_password_for_blocks',,
  rabbit_host         => 'openstack-controller.example.com',
  verbose             => true,
}

class { '::sysinv::api':
  keystone_password       => $keystone_password,
  keystone_enabled        => $keystone_enabled,
  keystone_user           => $keystone_user,
  keystone_auth_host      => $keystone_auth_host,
  keystone_auth_port      => $keystone_auth_port,
  keystone_auth_protocol  => $keystone_auth_protocol,
  service_port            => $keystone_service_port,
  package_ensure          => $sysinv_api_package_ensure,
  bind_host               => $sysinv_bind_host,
  enabled                 => $sysinv_api_enabled,
}

class { '::sysinv::scheduler': scheduler_driver => 'sysinv.scheduler.simple.SimpleScheduler', }

Define a sysinv storage node

class { '::sysinv':
  sql_connection      => 'mysql://sysinv:secret_block_password@openstack-controller.example.com/sysinv',
  rabbit_password     => 'secret_rpc_password_for_blocks',,
  rabbit_host         => 'openstack-controller.example.com',
  verbose             => true,
}

class { '::sysinv::volume': }

class { '::sysinv::volume::iscsi': iscsi_ip_address => '10.0.0.2', }

Implementation

sysinv

sysinv is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.

Limitations

  • Setup of storage nodes is limited to Linux and LVM, i.e. Puppet won't configure a Nexenta appliacne but nova can be configured to use the Nexenta driver with Class['sysinv::volume::nexenta'].

Development

Developer documentation for the entire puppet-openstack project.

Contributors

Release Notes

2.1.0

  • Added configuration of Sysinv quotas.
  • Added support for NetApp direct driver backend.
  • Added support for ceph backend.
  • Added support for SQL idle timeout.
  • Added support for RabbitMQ clustering with single IP.
  • Fixed allowed_hosts/database connection bug.
  • Fixed lvm2 setup failure for Ubuntu.
  • Removed unnecessary mysql::server dependency.
  • Pinned RabbitMQ and database module versions.
  • Various lint and bug fixes.

2.0.0

  • Upstream is now part of stackfoge.
  • Nexenta, NFS, and SAN support added as sysinv volume drivers.
  • Postgres support added.
  • The Apache Qpid and the RabbitMQ message brokers available as RPC backends.
  • Configurability of scheduler_driver.
  • Various cleanups and bug fixes.