Systemd ulimits #56

.gitignore

@@ -1,14 +1,16 @@
-.DS_Store
+*.csr
+*.pem
+*.jks
+*.p12
+*.crt
+*.der
+*.key
+*.swp
 *.retry
-*.pyc
-*.idea
-security/*.crt
-security/*.csr
-security/*_creds
-security/*.jks
-security/*.srl
-security/*.key
-security/*.req
-security/*.pem
-security/*.der
-security/*.p12
+test*
+broker_sslkey_creds
+broker_truststore_creds
+client_keystore_creds
+client_sslkey_creds
+client_truststore_creds
+generated_ssl_files

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [support@confluent.io](mailto:support@confluent.io). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,115 @@
+# Contributing to CP-Ansible
+
+Thank you for your interest in contributing to the CP-Ansible project.
+
+Before contributing any changes, we would ask that you open an issue on github and discuss with the wider community the changes being made.
+
+While we appreciate all code changes submitted, please understand that some PR's may not be committed for a variety of reasons.  We will do our best to explain why a PR cannot be merged when closing the request.
+
+#### Table Of Contents
+
+[Code of Conduct](#code-of-conduct)
+
+[How to ask questions](#how-to-ask-questions)
+
+[How to file a bug](#how-to-file-a-bug)
+
+[How to file a feature request](#how-to-file-a-feature-request)
+
+[How to file a pull request](#how-to-file-a-pull-request) 
+
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [CP-Ansible Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [support@confluent.io](mailto:support@confluent.io).
+
+## How to ask questions
+
+You can ask questions via two methods:
+
+1. You can open an issue on the project itself, here on github, which will be answered on a best effort basis:
+
+    ```https://github.com/confluentinc/cp-ansible/issues/new```
+
+    Please be sure to tag the post as a `question`.
+
+
+2. For Confluent Enterprise Support customers, we would strongly adivse you to open a Support ticket which will be addressed within your Support contract SLA:
+
+    ```https://support.confluent.io```
+
+
+## How to file a bug
+
+You can file bugs via two methods:
+
+1. You can open an issue on the project itself, here on github, which will be answered on a best effort basis:
+
+    ```https://github.com/confluentinc/cp-ansible/issues/new```
+
+    Please be sure to tag the post as a `bug`.
+
+2. For Confluent Enterprise Support customers, we would strongly adivse you to open a Support ticket which will be addressed within your Support contract SLA:
+
+    ```https://support.confluent.io```
+
+    Please include the following on all bug reports:
+
+* Use a clear and descriptive title for the issue to identify the problem.
+
+* Describe the exact steps which reproduce the problem in as many details as possible. For example, run the Ansible playbook with the `-vvv` switch and pipe the output to a file.  Provide a link to the file 
+
+* Provide specific examples to demonstrate the steps. Include links to files or GitHub projects, or copy/pasteable snippets, which you use in those examples. If you're providing snippets in the issue, use Markdown code blocks.
+
+* Any changes which have been made to the playbooks or environments (please be as specific as possible).
+
+* Explain which behavior you expected to see instead and why.
+
+## How to file a feature request 
+
+1. You can open an issue on the project itself, here on github, which will be answered on a best effort basis:
+
+    ```https://github.com/confluentinc/cp-ansible/issues/new```
+
+Please be sure to tag the post as a `enhancement`.
+
+2. For Confluent Enterprise Support customers, we would strongly adivse you to open a Support ticket which will be addressed within your Support contract SLA:
+
+    ```https://support.confluent.io```
+
+Please include the following on all enhancement requests:
+
+* Use a clear and descriptive title for the issue to identify the problem.
+
+* Provide a step-by-step description of the suggested enhancement in as many details as possible.
+
+* Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
+
+* Describe the current behavior and explain which behavior you expected to see instead and why.
+
+## How to file a Pull Request
+
+The process described here has several goals:
+
+* Maintain CP-Ansible's quality
+* Fix problems that are important to users
+* Engage the community in working toward the best possible CP-Ansible
+* Enable a sustainable system for CP-Ansible's maintainers to review contributions
+
+Please follow these steps to have your contribution considered by the maintainers:
+
+1. Follow all instructions in [the template](PULL_REQUEST_TEMPLATE.md)
+2. Follow the styleguides
+3. After you submit your pull request, verify that all status checks are passing
+
+While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.
+
+
+## Style guide
+
+Git Commit Messages
+
+* Use the present tense ("Add feature" not "Added feature")
+* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+* Limit the first line to 72 characters or less
+* Reference issues and pull requests liberally after the first line

PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+# Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+
+Fixes # (issue)
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+# How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
+
+
+
+**Test Configuration**:
+
+
+# Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] Any dependent changes have been merged and published in downstream modules

README.md

@@ -1,12 +1,13 @@
-Please note that these playbooks are provided without support and are intended to be a guideline. Any issues encountered can be reported via the GitHub issues and will be addressed on a best effort basis. Pull requests are also encouraged.
 
-# Introduction
+# CP-Ansible
+
+## Introduction
 
 Ansible provides a simple way to deploy, manage, and configure the Confluent Platform services. This repository provides playbooks and templates to easily spin up a Confluent Platform installation. Specifically this repository:
 
-* Installs Confluent Platform packages
-* Starts services using systemd scripts
-* Provides configuration options for plaintext, SSL, and SASL_SSL communication amongst the services
+* Installs Confluent Platform packages.
+* Starts services using systemd scripts.
+* Provides configuration options for plaintext, SSL, SASL_SSL, and Kerberos.
 
 The services that can be installed from this repository are:
 
@@ -16,7 +17,16 @@ The services that can be installed from this repository are:
 * REST Proxy
 * Confluent Control Center
 * Kafka Connect (distributed mode)
+* KSQL Server
+
+## Documentation
+
+You can find the documentation for running CP-Ansible at https://docs.confluent.io/current/tutorials/cp-ansible/docs/index.html.
+
+## Contributing
+
+If you would like to contribute to the CP-Ansible project, please refer to the [CONTRIBUTE.md](https://github.com/confluentinc/cp-ansible/blob/5.3.0-post/CONTRIBUTING.md)
 
-# Documentation
+## License
 
-You can find the documentation for running this playbook at https://docs.confluent.io/current/tutorials/cp-ansible/docs/index.html.
+[Apache 2.0](https://github.com/confluentinc/cp-ansible/blob/5.1.x/LICENSE.md) 

all.yml

@@ -2,14 +2,6 @@
   tasks:
   - import_role:
       name: confluent.preflight
-    tags:
-      - pre-install
-- hosts: ssl_CA
-  tasks:
-  - import_role:
-      name: confluent.ssl_CA
-    tags:
-      - pre-install
 - hosts: zookeeper
   tasks:
   - import_role:
@@ -38,9 +30,3 @@
   tasks:
   - import_role:
       name: confluent.kafka-rest
-- hosts: tools
-  tasks:
-  - import_role:
-      name: confluent.tools
-    tags:
-      - post-install