partekflow
Version information
This version is compatible with:
- Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.7.0 < 6.0.0
- ,
Tasks:
- backupdb
Start using this module
Add this module to your Puppetfile:
mod 'millerjl1701-partekflow', '1.3.1'
Learn more about managing modules with a PuppetfileDocumentation
partekflow
Table of Contents
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with partekflow
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Module Description
The partekflow module installs, configures, and manages Partek Flow software package and service. Partek Flow is "designed specifically for the analysis needs of next generation sequencing applications including RNA, small RNA, and DNA sequencing" that includes a web interface for creation and utilization of custom pipelines. http://www.partek.com/partekflow
Setup
What partekflow affects
- User and Group: flow
- Group: flowuser
- RPM GPG Key: /etc/pki/rpm-gpg/partek-public.key
- Yumrepos for accessing partek flow RPM repositories. The stable repositories are enabled while the unstable ones are not.
- Package: partekflow
- File: /etc/partekflow.conf
- Catalina temp directory location
- Service: partekflowd
Beginning with partekflow
include partekflow
should be all that is needed to install, configure and start the partekflowd service. One can also pass parameters in to change the configuration:
class { 'partekflow':
config_catalina_tmpdir => '/home/flow/partek_flow/temp',
}
Usage
All parameters are passed to the main class via either puppet code or hiera. The other classes should not be called directly. Some usage examples are presented below.
Install and startup partekflowd service
include partekflow
Change the location of the CATALINA_TMPDIR setting in /etc/partekflow.conf
class { 'partekflow':
config_catalina_tmpdir => '/home/flow/partek_flow/temp',
}
or via hiera:
---
partekflow::config_catalina_tmpdir: '/home/flow/partek_flow/temp'
To use a different template for the partekflow.conf file
class { 'partekflow':
config_template => 'module_name/path/to/template.erb',
}
To disable the stable repsitory files but still have them present in /etc/yum.repos.d/
class { 'partekflow':
yumrepo_ensure_stable => true,
yumrepo_enabled_stable => false,
}
To use a local repository mirror instead of the Partek repositories
class { 'partekflow':
yumrepo_baseurl_server => 'http://yum.example.com',
yumrepo_baseurl_stablepath => '/path/to/stable',
yumrepo_baseurl_unstablepath => '/path/to/unstable',
}
To remove the unstable /etc/yum.repos.d/ files
class { 'partekflow':
yumrepo_ensure_unstable => false,
}
Reference
This module is setup for the use of Puppet Strings to generate class and parameter documentation. The Puppet Strings doumentation provides more details on what Puppet Strings provides and other ways of generating documentaiton output.
As a quick start, if you are using the gem version of puppet:
gem install puppet-strings
puppet strings generate manifests/*.pp
The puppet strings command should be run from the root of the module directory. The resulting documentation will by default be placed in a docs/ directory within the module.
If you are setup with the development environment as described in the CONTRIBUTING document :
bundle exec rake strings:generate manifests/*.pp
from within the module directory will generate the documentation as well.
Limitations
This module is written to work with Puppet 4.7 or higher. Hiera 5 data is embedded within the module as well for Puppet 4.9 or higher. The module depends on Puppet 4 data types provided by puppetlabs-stdlib as well as the treydock-gpg_key module.
Originally written for CentOS 6/7 systems, it could work on other osfamily RedHat distributions. While Partek Flow supports installation on Debian based distributions, this module does not at this time.
This module was written to reflect initial installation and configuration documentation provided by Partek. This is not an all inclusive module as there are configuration tasks that need to be done via the web UI to configure portions of the application. If you find some configuration option would be helpful for maintaining the software on your own servers, please submit an issue or pull request. The latest released version of Partek flow when this was written was: 6.0.17.0919.278-1 and serves as a start point for reference. It is possible that this module will work with prior partekflow versions; however, that condition has not been tested.
While the module maintainer supports the puppet code contained in the module, support for the application or performance of the Partek Flow software should be directed toward Partek. The module maintainer does not have a relationship with Partek.
Development
Please see the CONTRIBUTING document for information on how to get started developing code and submit a pull request for this module. While written in an opinionated fashion at the start, over time this can become less and less the case.
Contributors
To see who is involved with this module, see the GitHub list of contributors or the CONTRIBUTORS document.
What are tasks?
Modules can contain tasks that take action outside of a desired state managed by Puppet. It’s perfect for troubleshooting or deploying one-off changes, distributing scripts to run across your infrastructure, or automating changes that need to happen in a particular order as part of an application deployment.
Tasks in this module release
backupdb
Backup the partekflow database. Currently, this needs to be run as the flow account
Change Log
v1.3.1 2017-10-11
Merged pull requests:
- Added in yaml-lint support to Gemfile, Rakefile, and .travis.yml #4 (millerjl1701)
v1.3.0 (2017-10-11)
Merged pull requests:
- Added initial backupdb task. #3 (millerjl1701)
v1.2.0 (2017-10-08)
Merged pull requests:
- changes for supporting puppet 4.7 #2 (millerjl1701)
v1.1.0 (2017-10-06)
Implemented enhancements:
- Allow for class parameters for yumrepo resource management. #1 (millerjl1701)
v1.0.0 (2017-10-04)
v0.1.0 (2017-09-28)
2017-10-05 Release 1.1.0
- Added parameters to allow for more refined configuration of the yumrepo resources
2017-10-04 Release 1.0.0
- Changed files for use of hiera 5 and removed params.pp file
- Modified service_name parameter to partekflowd to reflect actual service name installed
- Added parameter data types and puppet strings documentation
- Added package_ensure parameter to manage the ensure parameter of the partekflow package resource.
- Added service_ensure parameter to manage the ensure parameter on the partekflowd service resource.
- Added service_enable parameter to enable or disable the partekflowd service on boot
- Added user and group for partekflowd service.
- Added RPM GPG public key installtion for partek-public.key
- Added yum repository management to match current partekflow.repo file.
- Added /etc/partekflow.conf file as puppet managed file.
- Added documentation of module using puppet strings methodology
- Added code coverage for both spec and acceptance tests
- Cleaned up directory structure to remove unneeded portions put in place by skeleton.
- Populated CONTRIBUTORS
- Updated README.markdown
2017-09-24 Release 0.1.0
- Initial commit of files from puppet module generate using millerjl1701/puppet-skeleton.
- Modified files after testing with the puppet-skeleton as there were some errors in the initial push.
* This Change Log was automatically generated by github_changelog_generator
Dependencies
- puppetlabs-stdlib (>=4.7.0 <5.0.0)
- treydock-gpg_key (>=0.0.4 < 1.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] 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.