c1f7d4edcc
Having a Rakefile will allow us to change the actual test commands on our side rather than relying on changes to the openstack-infra repository. This should make it a lot faster to change things, but also easier to test since the jenkins jobs are actually run in this repository, not the openstack-infra one. This commit defines the jobs we previously had defined in Jenkins and uses 'high-level' naming consistently (i.e. lint, style vs. foodcritic, rubocop). There is also a :clean task to help with deleting the files generated by the other jobs. Also changed foodcritic to run on the source cookbook rather than the one installed by berks, see e.g. https://github.com/berkshelf/berkshelf/issues/931#issuecomment-29668369 Change-Id: If76f6fca62c7cff719e9a631c968a252cf30f10a blueprint: rakefile |
||
|---|---|---|
| attributes | ||
| recipes | ||
| spec | ||
| templates/default | ||
| .gitignore | ||
| .gitreview | ||
| .rubocop.yml | ||
| Berksfile | ||
| CHANGELOG.md | ||
| Gemfile | ||
| README.md | ||
| Rakefile | ||
| TESTING.md | ||
| metadata.rb | ||
README.md
Description
Installs the OpenStack Metering service Ceilometer as part of the OpenStack reference deployment Chef for OpenStack. Ceilometer is currently installed from packages.
https://wiki.openstack.org/wiki/Ceilometer
Requirements
Cookbooks
Usage
agent-central
- Installs agent central service.
agent-compute
- Installs agent compute service.
agent-notification
- Installs agent notification service.
alarm-evaluator
- Installs alarm evaluator service.
alarm-notifier
- Installs alarm notifier service.
api
- Installs API service.
client
- Install the client packages
collector
- Installs collector package and service. If the NoSQL database is used for metering service, ceilometer-dbsync will not be executed.
common
- Common metering configuration.
identity_registration
- Registers the endpoints, tenant and user for metering service with Keystone.
Attributes
openstack['telemetry']['api']['auth']['version']- Select v2.0 or v3.0. Default v2.0. The auth API version used to interact with identity service.openstack['telemetry']['sample_source']- The source name of emitted samples, default value is openstack.openstack['telemetry']['api']['auth']['memcached_servers']- A list of memcached server(s) to use for cachingopenstack['telemetry']['api']['auth']['memcache_security_strategy']- Whether token data should be authenticated or authenticated and encrypted. Acceptable values are MAC or ENCRYPTopenstack['telemetry']['api']['auth']['memcache_secret_key']- This string is used for key derivationopenstack['telemetry']['api']['auth']['hash_algorithms']- Hash algorithms to use for hashing PKI tokensopenstack['telemetry']['api']['auth']['cafile']- A PEM encoded Certificate Authority to use when verifying HTTPs connectionsopenstack['telemetry']['api']['auth']['insecure']- Set whether to verify HTTPS connectionsopenstack['telemetry']['service-credentials']['cafile']- A PEM encoded Certificate Authority to use when verifying HTTPs connections (for service polling authentication)openstack['telemetry']['service-credentials']['insecure']- Set whether to verify HTTPS connections (for service polling authentication)
The following attributes are defined in attributes/default.rb of the common cookbook, but are documented here due to their relevance:
openstack['endpoints']['telemetry-api-bind']['host']- The IP address to bind the api service toopenstack['endpoints']['telemetry-api-bind']['port']- The port to bind the api service toopenstack['endpoints']['telemetry-api-bind']['bind_interface']- The interface name to bind the api service to
If the value of the 'bind_interface' attribute is non-nil, then the telemetry service will be bound to the first IP address on that interface. If the value of the 'bind_interface' attribute is nil, then the telemetry service will be bound to the IP address specifie
Testing
Please refer to the TESTING.md for instructions for testing the cookbook.
Berkshelf
Berks will resolve version requirements and dependencies on first run and
store these in Berksfile.lock. If new cookbooks become available you can run
berks update to update the references in Berksfile.lock. Berksfile.lock will
be included in stable branches to provide a known good set of dependencies.
Berksfile.lock will not be included in development branches to encourage
development against the latest cookbooks.
License and Author
| Author | Matt Ray (matt@opscode.com) |
| Author | John Dewey (jdewey@att.com) |
| Author | Justin Shepherd (jshepher@rackspace.com) |
| Author | Salman Baset (sabaset@us.ibm.com) |
| Author | Ionut Artarisi (iartarisi@suse.cz) |
| Author | Eric Zhou (zyouzhou@cn.ibm.com) |
| Author | Chen Zhiwei (zhiwchen@cn.ibm.com) |
| Author | David Geng (gengjh@cn.ibm.com) |
| Copyright | Copyright (c) 2013, Opscode, Inc. |
| Copyright | Copyright (c) 2013, AT&T Services, Inc. |
| Copyright | Copyright (c) 2013, Rackspace US, Inc. |
| Copyright | Copyright (c) 2013-2014, IBM, Corp. |
| Copyright | Copyright (c) 2013-2014, SUSE Linux GmbH |
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.