diff --git a/CNAME b/CNAME new file mode 100644 index 00000000..5829576c --- /dev/null +++ b/CNAME @@ -0,0 +1 @@ +tackle-docs.konveyor.io diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..ddee4673 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +We as members, contributors, and leaders pledge to make participation in our +community a harassment-free experience for everyone, regardless of age, body +size, visible or invisible disability, ethnicity, sex characteristics, gender +identity and expression, level of experience, education, socio-economic status, +nationality, personal appearance, race, religion, or sexual identity +and orientation. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +Examples of behavior that contributes to a positive environment for our +community include: + +- Demonstrating empathy and kindness toward other people +- Being respectful of differing opinions, viewpoints, and experiences +- Giving and gracefully accepting constructive feedback +- Accepting responsibility and apologizing to those affected by our mistakes, + and learning from the experience +- Focusing on what is best not just for us as individuals, but for the + overall community + +Examples of unacceptable behavior include: + +- The use of sexualized language or imagery, and sexual attention or + advances of any kind +- Trolling, insulting or derogatory comments, and personal or political attacks +- Public or private harassment +- Publishing others' private information, such as a physical or email + address, without their explicit permission +- Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +This Code of Conduct applies within all community spaces, and also applies when +an individual is officially representing the community in public spaces. +Examples of representing our community include using an official e-mail address, +posting via an official social media account, or acting as an appointed +representative at an online or offline event. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement at +konveyor.io. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**Community Impact**: A violation through a single incident or series +of actions. + +**Consequence**: A warning with consequences for continued behavior. No +interaction with the people involved, including unsolicited interaction with +those enforcing the Code of Conduct, for a specified period of time. This +includes avoiding interactions in community spaces as well as external channels +like social media. Violating these terms may lead to a temporary or +permanent ban. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +standards, including sustained inappropriate behavior, harassment of an +individual, or aggression toward or disparagement of classes of individuals. + +**Consequence**: A permanent ban from any sort of public interaction within +the community. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.0, available at +https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see the FAQ at +https://www.contributor-covenant.org/faq. Translations are available at +https://www.contributor-covenant.org/translations. diff --git a/CONTRIBUTING/index.html b/CONTRIBUTING/index.html new file mode 100644 index 00000000..bb56ed05 --- /dev/null +++ b/CONTRIBUTING/index.html @@ -0,0 +1,194 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Contributors Guide

+
+
+
+

Improvements to Tackle documentation are welcome.

+
+
+

Read the [Guidelines for Red Hat Documentation](https://redhat-documentation.github.io/) before opening a pull request.

+
+
+

Use the following steps to create a pull request for the Tackle documentation repository.

+
+
+
    +
  1. +

    Fork the tackle-documentation GitHub repository.

    +
    +

    Click the Fork button in the top right corner of the page.

    +
    +
  2. +
  3. +

    Clone the forked repository locally.

    +
    +
    +
    $ git clone git@github.com:YOUR_USERNAME/tackle-documentation.git
    +
    +
    +
  4. +
  5. +

    Add the upstream repository.

    +
    +
    +
    git remote add -f upstream git@github.com:tackle-documentation.git
    +
    +
    +
  6. +
  7. +

    Get the latest changes.

    +
    +
    +
    $ git fetch upstream
    +
    +
    +
  8. +
  9. +

    Check out a topic branch.

    +
    +
    +
    $ git checkout -b BRANCH_NAME upstream/main
    +
    +
    +
  10. +
  11. +

    Make the desired edits.

    +
    +

    The documentation is written in AsciiDoc. Review the AsciiDoc Guidelines and Tips section of this guide before making changes.

    +
    +
  12. +
  13. +

    Build the guides to verify your changes.

    +
    +
      +
    1. +

      Navigate to the appropriate guide’s directory and issue the following command. Note that you must have Asciidoctor installed.

      +
      +
      +
      $ cd documentation/<document>
      +$ asciidoctor -t -dbook -a toc -o html master.adoc
      +
      +
      +
    2. +
    3. +

      View the generated HTML file in a browser.

      +
    4. +
    +
    +
  14. +
  15. +

    Add each new or updated file to git.

    +
    +
    +
    $ git add FILE_NAME.adoc
    +
    +
    +
  16. +
  17. +

    Commit the changes locally.

    +
    +
    +
    $ git commit -m "My commit message."
    +
    +
    +
  18. +
  19. +

    Push the changes to your forked repository.

    +
    +
    +
    $ git push origin HEAD
    +
    +
    +
  20. +
  21. +

    Open a pull request to merge your changes to the master branch.

    +
    +
      +
    1. +

      Navigate to your forked repository in a browser: https://github.com/YOUR_USERNAME/konveyor/tackle-documentation.

      +
    2. +
    3. +

      Open a new pull request. Be sure to review the diff before submitting.

      +
    4. +
    5. +

      A member of the Tackle documentation team will merge or provide feedback on your request.

      +
    6. +
    +
    +
  22. +
+
+
+
+
+

Building the Guides

+
+
+

Navigate to the appropriate guide’s directory and issue the following command. Note that you must have Asciidoctor installed.

+
+
+
+
$ cd documentation/<document>
+$ asciidoctor -t -dbook -a toc -o html master.adoc
+
+
+
+

View the generated HTML file in a browser.

+
+
+
+
+

Publishing the Guides

+
+
+

The Tackle guides are published downstream on the Red Hat Customer Portal.

+
+
+
+ + +
+ + diff --git a/Gemfile b/Gemfile new file mode 100644 index 00000000..5ecdab11 --- /dev/null +++ b/Gemfile @@ -0,0 +1,31 @@ +# frozen_string_literal: true +# Encoding.default_external = Encoding::UTF_8 +# Encoding.default_internal = Encoding::UTF_8 + +source "https://rubygems.org" + +# gem "asciidoctor-pdf" +gem "asciidoctor" +# gem "bundle" +# gem "html-proofer" +gem "jekyll-theme-minimal" +# gem "jekyll-feed" +gem "jekyll-paginate" +# gem "jekyll-redirect-from" +# gem "jekyll-sitemap" +# gem "jekyll-tagging" +# gem 'jekyll-seo-tag' +# gem "jekyll", ">= 3.5" +# gem "premonition", ">= 4.0.0" +# gem "pygments.rb" +# gem "rake" +# +# +gem "github-pages", group: :jekyll_plugins + +# ensures that jekyll-asciidoc is loaded first +group :jekyll_plugins do + gem 'jekyll-asciidoc' +end + +gemspec diff --git a/Gemfile.lock b/Gemfile.lock new file mode 100644 index 00000000..29dc8d8c --- /dev/null +++ b/Gemfile.lock @@ -0,0 +1,327 @@ +PATH + remote: . + specs: + jekyll-theme-cayman (0.1.1) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + +GEM + remote: https://rubygems.org/ + specs: + activesupport (7.2.2.1) + base64 + benchmark (>= 0.3) + bigdecimal + concurrent-ruby (~> 1.0, >= 1.3.1) + connection_pool (>= 2.2.5) + drb + i18n (>= 1.6, < 2) + logger (>= 1.4.2) + minitest (>= 5.1) + securerandom (>= 0.3) + tzinfo (~> 2.0, >= 2.0.5) + addressable (2.8.7) + public_suffix (>= 2.0.2, < 7.0) + asciidoctor (2.0.23) + ast (2.4.2) + base64 (0.2.0) + benchmark (0.4.0) + bigdecimal (3.1.9) + coffee-script (2.4.1) + coffee-script-source + execjs + coffee-script-source (1.12.2) + colorator (1.1.0) + commonmarker (0.23.11) + concurrent-ruby (1.3.5) + connection_pool (2.5.0) + csv (3.3.2) + dnsruby (1.72.3) + base64 (~> 0.2.0) + simpleidn (~> 0.2.1) + drb (2.2.1) + em-websocket (0.5.3) + eventmachine (>= 0.12.9) + http_parser.rb (~> 0) + ethon (0.16.0) + ffi (>= 1.15.0) + eventmachine (1.2.7) + execjs (2.10.0) + faraday (2.12.2) + faraday-net_http (>= 2.0, < 3.5) + json + logger + faraday-net_http (3.4.0) + net-http (>= 0.5.0) + ffi (1.17.1-x86_64-linux-musl) + forwardable-extended (2.6.0) + gemoji (4.1.0) + github-pages (232) + github-pages-health-check (= 1.18.2) + jekyll (= 3.10.0) + jekyll-avatar (= 0.8.0) + jekyll-coffeescript (= 1.2.2) + jekyll-commonmark-ghpages (= 0.5.1) + jekyll-default-layout (= 0.1.5) + jekyll-feed (= 0.17.0) + jekyll-gist (= 1.5.0) + jekyll-github-metadata (= 2.16.1) + jekyll-include-cache (= 0.2.1) + jekyll-mentions (= 1.6.0) + jekyll-optional-front-matter (= 0.3.2) + jekyll-paginate (= 1.1.0) + jekyll-readme-index (= 0.3.0) + jekyll-redirect-from (= 0.16.0) + jekyll-relative-links (= 0.6.1) + jekyll-remote-theme (= 0.4.3) + jekyll-sass-converter (= 1.5.2) + jekyll-seo-tag (= 2.8.0) + jekyll-sitemap (= 1.4.0) + jekyll-swiss (= 1.0.0) + jekyll-theme-architect (= 0.2.0) + jekyll-theme-cayman (= 0.2.0) + jekyll-theme-dinky (= 0.2.0) + jekyll-theme-hacker (= 0.2.0) + jekyll-theme-leap-day (= 0.2.0) + jekyll-theme-merlot (= 0.2.0) + jekyll-theme-midnight (= 0.2.0) + jekyll-theme-minimal (= 0.2.0) + jekyll-theme-modernist (= 0.2.0) + jekyll-theme-primer (= 0.6.0) + jekyll-theme-slate (= 0.2.0) + jekyll-theme-tactile (= 0.2.0) + jekyll-theme-time-machine (= 0.2.0) + jekyll-titles-from-headings (= 0.5.3) + jemoji (= 0.13.0) + kramdown (= 2.4.0) + kramdown-parser-gfm (= 1.1.0) + liquid (= 4.0.4) + mercenary (~> 0.3) + minima (= 2.5.1) + nokogiri (>= 1.16.2, < 2.0) + rouge (= 3.30.0) + terminal-table (~> 1.4) + webrick (~> 1.8) + github-pages-health-check (1.18.2) + addressable (~> 2.3) + dnsruby (~> 1.60) + octokit (>= 4, < 8) + public_suffix (>= 3.0, < 6.0) + typhoeus (~> 1.3) + html-pipeline (2.14.3) + activesupport (>= 2) + nokogiri (>= 1.4) + html-proofer (3.19.4) + addressable (~> 2.3) + mercenary (~> 0.3) + nokogiri (~> 1.13) + parallel (~> 1.10) + rainbow (~> 3.0) + typhoeus (~> 1.3) + yell (~> 2.0) + http_parser.rb (0.8.0) + i18n (1.14.7) + concurrent-ruby (~> 1.0) + jekyll (3.10.0) + addressable (~> 2.4) + colorator (~> 1.0) + csv (~> 3.0) + em-websocket (~> 0.5) + i18n (>= 0.7, < 2) + jekyll-sass-converter (~> 1.0) + jekyll-watch (~> 2.0) + kramdown (>= 1.17, < 3) + liquid (~> 4.0) + mercenary (~> 0.3.3) + pathutil (~> 0.9) + rouge (>= 1.7, < 4) + safe_yaml (~> 1.0) + webrick (>= 1.0) + jekyll-asciidoc (3.0.1) + asciidoctor (>= 1.5.0, < 3.0.0) + jekyll (>= 3.0.0) + jekyll-avatar (0.8.0) + jekyll (>= 3.0, < 5.0) + jekyll-coffeescript (1.2.2) + coffee-script (~> 2.2) + coffee-script-source (~> 1.12) + jekyll-commonmark (1.4.0) + commonmarker (~> 0.22) + jekyll-commonmark-ghpages (0.5.1) + commonmarker (>= 0.23.7, < 1.1.0) + jekyll (>= 3.9, < 4.0) + jekyll-commonmark (~> 1.4.0) + rouge (>= 2.0, < 5.0) + jekyll-default-layout (0.1.5) + jekyll (>= 3.0, < 5.0) + jekyll-feed (0.17.0) + jekyll (>= 3.7, < 5.0) + jekyll-gist (1.5.0) + octokit (~> 4.2) + jekyll-github-metadata (2.16.1) + jekyll (>= 3.4, < 5.0) + octokit (>= 4, < 7, != 4.4.0) + jekyll-include-cache (0.2.1) + jekyll (>= 3.7, < 5.0) + jekyll-mentions (1.6.0) + html-pipeline (~> 2.3) + jekyll (>= 3.7, < 5.0) + jekyll-optional-front-matter (0.3.2) + jekyll (>= 3.0, < 5.0) + jekyll-paginate (1.1.0) + jekyll-readme-index (0.3.0) + jekyll (>= 3.0, < 5.0) + jekyll-redirect-from (0.16.0) + jekyll (>= 3.3, < 5.0) + jekyll-relative-links (0.6.1) + jekyll (>= 3.3, < 5.0) + jekyll-remote-theme (0.4.3) + addressable (~> 2.0) + jekyll (>= 3.5, < 5.0) + jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0) + rubyzip (>= 1.3.0, < 3.0) + jekyll-sass-converter (1.5.2) + sass (~> 3.4) + jekyll-seo-tag (2.8.0) + jekyll (>= 3.8, < 5.0) + jekyll-sitemap (1.4.0) + jekyll (>= 3.7, < 5.0) + jekyll-swiss (1.0.0) + jekyll-theme-architect (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-dinky (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-hacker (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-leap-day (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-merlot (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-midnight (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-minimal (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-modernist (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-primer (0.6.0) + jekyll (> 3.5, < 5.0) + jekyll-github-metadata (~> 2.9) + jekyll-seo-tag (~> 2.0) + jekyll-theme-slate (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-tactile (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-time-machine (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-titles-from-headings (0.5.3) + jekyll (>= 3.3, < 5.0) + jekyll-watch (2.2.1) + listen (~> 3.0) + jemoji (0.13.0) + gemoji (>= 3, < 5) + html-pipeline (~> 2.2) + jekyll (>= 3.0, < 5.0) + json (2.9.1) + kramdown (2.4.0) + rexml + kramdown-parser-gfm (1.1.0) + kramdown (~> 2.0) + liquid (4.0.4) + listen (3.9.0) + rb-fsevent (~> 0.10, >= 0.10.3) + rb-inotify (~> 0.9, >= 0.9.10) + logger (1.6.5) + mercenary (0.3.6) + minima (2.5.1) + jekyll (>= 3.5, < 5.0) + jekyll-feed (~> 0.9) + jekyll-seo-tag (~> 2.1) + minitest (5.25.4) + net-http (0.6.0) + uri + nokogiri (1.18.2-x86_64-linux-musl) + racc (~> 1.4) + octokit (4.25.1) + faraday (>= 1, < 3) + sawyer (~> 0.9) + parallel (1.26.3) + parser (3.3.7.0) + ast (~> 2.4.1) + racc + pathutil (0.16.2) + forwardable-extended (~> 2.6) + public_suffix (5.1.1) + racc (1.8.1) + rainbow (3.1.1) + rb-fsevent (0.11.2) + rb-inotify (0.11.1) + ffi (~> 1.0) + regexp_parser (2.10.0) + rexml (3.4.0) + rouge (3.30.0) + rubocop (0.93.1) + parallel (~> 1.10) + parser (>= 2.7.1.5) + rainbow (>= 2.2.2, < 4.0) + regexp_parser (>= 1.8) + rexml + rubocop-ast (>= 0.6.0) + ruby-progressbar (~> 1.7) + unicode-display_width (>= 1.4.0, < 2.0) + rubocop-ast (1.37.0) + parser (>= 3.3.1.0) + ruby-progressbar (1.13.0) + rubyzip (2.4.1) + safe_yaml (1.0.5) + sass (3.7.4) + sass-listen (~> 4.0.0) + sass-listen (4.0.0) + rb-fsevent (~> 0.9, >= 0.9.4) + rb-inotify (~> 0.9, >= 0.9.7) + sawyer (0.9.2) + addressable (>= 2.3.5) + faraday (>= 0.17.3, < 3) + securerandom (0.4.1) + simpleidn (0.2.3) + terminal-table (1.8.0) + unicode-display_width (~> 1.1, >= 1.1.1) + typhoeus (1.4.1) + ethon (>= 0.9.0) + tzinfo (2.0.6) + concurrent-ruby (~> 1.0) + unicode-display_width (1.8.0) + uri (1.0.2) + w3c_validators (1.3.7) + json (>= 1.8) + nokogiri (~> 1.6) + rexml (~> 3.2) + webrick (1.9.1) + yell (2.2.2) + +PLATFORMS + x86_64-linux-musl + +DEPENDENCIES + asciidoctor + github-pages + html-proofer (~> 3.0) + jekyll-asciidoc + jekyll-paginate + jekyll-theme-cayman! + jekyll-theme-minimal + rubocop (~> 0.50) + w3c_validators (~> 1.3) + +BUNDLED WITH + 2.3.25 diff --git a/LICENSE b/LICENSE new file mode 100644 index 00000000..d6456956 --- /dev/null +++ b/LICENSE @@ -0,0 +1,202 @@ + + 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. diff --git a/assets/css/style.css b/assets/css/style.css new file mode 100644 index 00000000..7b5e6bb3 --- /dev/null +++ b/assets/css/style.css @@ -0,0 +1,329 @@ +/*! normalize.css v3.0.2 | MIT License | git.io/normalize */ +/** 1. Set default font family to sans-serif. 2. Prevent iOS text size adjust after orientation change, without disabling user zoom. */ +@import url("https://fonts.googleapis.com/css?family=Open+Sans:400,700"); +html { font-family: sans-serif; /* 1 */ -ms-text-size-adjust: 100%; /* 2 */ -webkit-text-size-adjust: 100%; /* 2 */ } + +/** Remove default margin. */ +body { margin: 0; } + +/* HTML5 display definitions ========================================================================== */ +/** Correct `block` display not defined for any HTML5 element in IE 8/9. Correct `block` display not defined for `details` or `summary` in IE 10/11 and Firefox. Correct `block` display not defined for `main` in IE 11. */ +article, aside, details, figcaption, figure, footer, header, hgroup, main, menu, nav, section, summary { display: block; } + +/** 1. Correct `inline-block` display not defined in IE 8/9. 2. Normalize vertical alignment of `progress` in Chrome, Firefox, and Opera. */ +audio, canvas, progress, video { display: inline-block; /* 1 */ vertical-align: baseline; /* 2 */ } + +/** Prevent modern browsers from displaying `audio` without controls. Remove excess height in iOS 5 devices. */ +audio:not([controls]) { display: none; height: 0; } + +/** Address `[hidden]` styling not present in IE 8/9/10. Hide the `template` element in IE 8/9/11, Safari, and Firefox < 22. */ +[hidden], template { display: none; } + +/* Links ========================================================================== */ +/** Remove the gray background color from active links in IE 10. */ +a { background-color: transparent; } + +/** Improve readability when focused and also mouse hovered in all browsers. */ +a:active, a:hover { outline: 0; } + +/* Text-level semantics ========================================================================== */ +/** Address styling not present in IE 8/9/10/11, Safari, and Chrome. */ +abbr[title] { border-bottom: 1px dotted; } + +/** Address style set to `bolder` in Firefox 4+, Safari, and Chrome. */ +b, strong { font-weight: bold; } + +/** Address styling not present in Safari and Chrome. */ +dfn { font-style: italic; } + +/** Address variable `h1` font-size and margin within `section` and `article` contexts in Firefox 4+, Safari, and Chrome. */ +h1 { font-size: 2em; margin: 0.67em 0; } + +/** Address styling not present in IE 8/9. */ +mark { background: #ff0; color: #000; } + +/** Address inconsistent and variable font size in all browsers. */ +small { font-size: 80%; } + +/** Prevent `sub` and `sup` affecting `line-height` in all browsers. */ +sub, sup { font-size: 75%; line-height: 0; position: relative; vertical-align: baseline; } + +sup { top: -0.5em; } + +sub { bottom: -0.25em; } + +/* Embedded content ========================================================================== */ +/** Remove border when inside `a` element in IE 8/9/10. */ +img { border: 0; } + +/** Correct overflow not hidden in IE 9/10/11. */ +svg:not(:root) { overflow: hidden; } + +/* Grouping content ========================================================================== */ +/** Address margin not present in IE 8/9 and Safari. */ +figure { margin: 1em 40px; } + +/** Address differences between Firefox and other browsers. */ +hr { box-sizing: content-box; height: 0; } + +/** Contain overflow in all browsers. */ +pre { overflow: auto; } + +/** Address odd `em`-unit font size rendering in all browsers. */ +code, kbd, pre, samp { font-family: monospace, monospace; font-size: 1em; } + +/* Forms ========================================================================== */ +/** Known limitation: by default, Chrome and Safari on OS X allow very limited styling of `select`, unless a `border` property is set. */ +/** 1. Correct color not being inherited. Known issue: affects color of disabled elements. 2. Correct font properties not being inherited. 3. Address margins set differently in Firefox 4+, Safari, and Chrome. */ +button, input, optgroup, select, textarea { color: inherit; /* 1 */ font: inherit; /* 2 */ margin: 0; /* 3 */ } + +/** Address `overflow` set to `hidden` in IE 8/9/10/11. */ +button { overflow: visible; } + +/** Address inconsistent `text-transform` inheritance for `button` and `select`. All other form control elements do not inherit `text-transform` values. Correct `button` style inheritance in Firefox, IE 8/9/10/11, and Opera. Correct `select` style inheritance in Firefox. */ +button, select { text-transform: none; } + +/** 1. Avoid the WebKit bug in Android 4.0.* where (2) destroys native `audio` and `video` controls. 2. Correct inability to style clickable `input` types in iOS. 3. Improve usability and consistency of cursor style between image-type `input` and others. */ +button, html input[type="button"], input[type="reset"], input[type="submit"] { -webkit-appearance: button; /* 2 */ cursor: pointer; /* 3 */ } + +/** Re-set default cursor for disabled elements. */ +button[disabled], html input[disabled] { cursor: default; } + +/** Remove inner padding and border in Firefox 4+. */ +button::-moz-focus-inner, input::-moz-focus-inner { border: 0; padding: 0; } + +/** Address Firefox 4+ setting `line-height` on `input` using `!important` in the UA stylesheet. */ +input { line-height: normal; } + +/** It's recommended that you don't attempt to style these elements. Firefox's implementation doesn't respect box-sizing, padding, or width. 1. Address box sizing set to `content-box` in IE 8/9/10. 2. Remove excess padding in IE 8/9/10. */ +input[type="checkbox"], input[type="radio"] { box-sizing: border-box; /* 1 */ padding: 0; /* 2 */ } + +/** Fix the cursor style for Chrome's increment/decrement buttons. For certain `font-size` values of the `input`, it causes the cursor style of the decrement button to change from `default` to `text`. */ +input[type="number"]::-webkit-inner-spin-button, input[type="number"]::-webkit-outer-spin-button { height: auto; } + +/** 1. Address `appearance` set to `searchfield` in Safari and Chrome. 2. Address `box-sizing` set to `border-box` in Safari and Chrome (include `-moz` to future-proof). */ +input[type="search"] { -webkit-appearance: textfield; /* 1 */ /* 2 */ box-sizing: content-box; } + +/** Remove inner padding and search cancel button in Safari and Chrome on OS X. Safari (but not Chrome) clips the cancel button when the search input has padding (and `textfield` appearance). */ +input[type="search"]::-webkit-search-cancel-button, input[type="search"]::-webkit-search-decoration { -webkit-appearance: none; } + +/** Define consistent border, margin, and padding. */ +fieldset { border: 1px solid #c0c0c0; margin: 0 2px; padding: 0.35em 0.625em 0.75em; } + +/** 1. Correct `color` not being inherited in IE 8/9/10/11. 2. Remove padding so people aren't caught out if they zero out fieldsets. */ +legend { border: 0; /* 1 */ padding: 0; /* 2 */ } + +/** Remove default vertical scrollbar in IE 8/9/10/11. */ +textarea { overflow: auto; } + +/** Don't inherit the `font-weight` (applied by a rule above). NOTE: the default cannot safely be changed in Chrome and Safari on OS X. */ +optgroup { font-weight: bold; } + +/* Tables ========================================================================== */ +/** Remove most spacing between table cells. */ +table { border-collapse: collapse; border-spacing: 0; } + +td, th { padding: 0; } + +.highlight table td { padding: 5px; } + +.highlight table pre { margin: 0; } + +.highlight .cm { color: #999988; font-style: italic; } + +.highlight .cp { color: #999999; font-weight: bold; } + +.highlight .c1 { color: #999988; font-style: italic; } + +.highlight .cs { color: #999999; font-weight: bold; font-style: italic; } + +.highlight .c, .highlight .cd { color: #999988; font-style: italic; } + +.highlight .err { color: #a61717; background-color: #e3d2d2; } + +.highlight .gd { color: #000000; background-color: #ffdddd; } + +.highlight .ge { color: #000000; font-style: italic; } + +.highlight .gr { color: #aa0000; } + +.highlight .gh { color: #999999; } + +.highlight .gi { color: #000000; background-color: #ddffdd; } + +.highlight .go { color: #888888; } + +.highlight .gp { color: #555555; } + +.highlight .gs { font-weight: bold; } + +.highlight .gu { color: #aaaaaa; } + +.highlight .gt { color: #aa0000; } + +.highlight .kc { color: #000000; font-weight: bold; } + +.highlight .kd { color: #000000; font-weight: bold; } + +.highlight .kn { color: #000000; font-weight: bold; } + +.highlight .kp { color: #000000; font-weight: bold; } + +.highlight .kr { color: #000000; font-weight: bold; } + +.highlight .kt { color: #445588; font-weight: bold; } + +.highlight .k, .highlight .kv { color: #000000; font-weight: bold; } + +.highlight .mf { color: #009999; } + +.highlight .mh { color: #009999; } + +.highlight .il { color: #009999; } + +.highlight .mi { color: #009999; } + +.highlight .mo { color: #009999; } + +.highlight .m, .highlight .mb, .highlight .mx { color: #009999; } + +.highlight .sb { color: #d14; } + +.highlight .sc { color: #d14; } + +.highlight .sd { color: #d14; } + +.highlight .s2 { color: #d14; } + +.highlight .se { color: #d14; } + +.highlight .sh { color: #d14; } + +.highlight .si { color: #d14; } + +.highlight .sx { color: #d14; } + +.highlight .sr { color: #009926; } + +.highlight .s1 { color: #d14; } + +.highlight .ss { color: #990073; } + +.highlight .s { color: #d14; } + +.highlight .na { color: #008080; } + +.highlight .bp { color: #999999; } + +.highlight .nb { color: #0086B3; } + +.highlight .nc { color: #445588; font-weight: bold; } + +.highlight .no { color: #008080; } + +.highlight .nd { color: #3c5d5d; font-weight: bold; } + +.highlight .ni { color: #800080; } + +.highlight .ne { color: #990000; font-weight: bold; } + +.highlight .nf { color: #990000; font-weight: bold; } + +.highlight .nl { color: #990000; font-weight: bold; } + +.highlight .nn { color: #555555; } + +.highlight .nt { color: #000080; } + +.highlight .vc { color: #008080; } + +.highlight .vg { color: #008080; } + +.highlight .vi { color: #008080; } + +.highlight .nv { color: #008080; } + +.highlight .ow { color: #000000; font-weight: bold; } + +.highlight .o { color: #000000; font-weight: bold; } + +.highlight .w { color: #bbbbbb; } + +.highlight { background-color: #f8f8f8; } + +* { box-sizing: border-box; } + +body { padding: 0; margin: 0; font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 16px; line-height: 1.5; color: #606c71; } + +#skip-to-content { height: 1px; width: 1px; position: absolute; overflow: hidden; top: -10px; } +#skip-to-content:focus { position: fixed; top: 10px; left: 10px; height: auto; width: auto; background: #e19447; outline: thick solid #e19447; } + +a { color: #1e6bb8; text-decoration: none; } +a:hover { text-decoration: underline; } + +.btn { display: inline-block; margin-bottom: 1rem; color: rgba(255, 255, 255, 0.7); background-color: rgba(255, 255, 255, 0.08); border-color: rgba(255, 255, 255, 0.2); border-style: solid; border-width: 1px; border-radius: 0.3rem; transition: color 0.2s, background-color 0.2s, border-color 0.2s; } +.btn:hover { color: rgba(255, 255, 255, 0.8); text-decoration: none; background-color: rgba(255, 255, 255, 0.2); border-color: rgba(255, 255, 255, 0.3); } +.btn + .btn { margin-left: 1rem; } +@media screen and (min-width: 64em) { .btn { padding: 0.75rem 1rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .btn { padding: 0.6rem 0.9rem; font-size: 0.9rem; } } +@media screen and (max-width: 42em) { .btn { display: block; width: 100%; padding: 0.75rem; font-size: 0.9rem; } + .btn + .btn { margin-top: 1rem; margin-left: 0; } } + +.page-header { color: #fff; text-align: center; background-color: #1f2067; background-image: linear-gradient(90deg, #3b3c93, #1f2067); } +@media screen and (min-width: 64em) { .page-header { padding: 5rem 6rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .page-header { padding: 3rem 4rem; } } +@media screen and (max-width: 42em) { .page-header { padding: 2rem 1rem; } } + +.project-name { margin-top: 0; margin-bottom: 0.1rem; } +@media screen and (min-width: 64em) { .project-name { font-size: 3.25rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .project-name { font-size: 2.25rem; } } +@media screen and (max-width: 42em) { .project-name { font-size: 1.75rem; } } + +.project-tagline { margin-bottom: 2rem; font-weight: normal; opacity: 0.7; } +@media screen and (min-width: 64em) { .project-tagline { font-size: 1.25rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .project-tagline { font-size: 1.15rem; } } +@media screen and (max-width: 42em) { .project-tagline { font-size: 1rem; } } + +.main-content { word-wrap: break-word; } +.main-content :first-child { margin-top: 0; } +@media screen and (min-width: 64em) { .main-content { max-width: 64rem; padding: 2rem 6rem; margin: 0 auto; font-size: 1.1rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .main-content { padding: 2rem 4rem; font-size: 1.1rem; } } +@media screen and (max-width: 42em) { .main-content { padding: 2rem 1rem; font-size: 1rem; } } +.main-content kbd { background-color: #fafbfc; border: 1px solid #c6cbd1; border-bottom-color: #959da5; border-radius: 3px; box-shadow: inset 0 -1px 0 #959da5; color: #444d56; display: inline-block; font-size: 11px; line-height: 10px; padding: 3px 5px; vertical-align: middle; } +.main-content img { max-width: 100%; } +.main-content h1, .main-content h2, .main-content h3, .main-content h4, .main-content h5, .main-content h6 { margin-top: 2rem; margin-bottom: 1rem; font-weight: normal; color: #3d3c93; } +.main-content p { margin-bottom: 1em; } +.main-content code { padding: 2px 4px; font-family: Consolas, "Liberation Mono", Menlo, Courier, monospace; font-size: 0.9rem; color: #567482; background-color: #f3f6fa; border-radius: 0.3rem; } +.main-content pre { padding: 0.8rem; margin-top: 0; margin-bottom: 1rem; font: 1rem Consolas, "Liberation Mono", Menlo, Courier, monospace; color: #567482; word-wrap: normal; background-color: #f3f6fa; border: solid 1px #dce6f0; border-radius: 0.3rem; } +.main-content pre > code { padding: 0; margin: 0; font-size: 0.9rem; color: #567482; word-break: normal; white-space: pre; background: transparent; border: 0; } +.main-content .highlight { margin-bottom: 1rem; } +.main-content .highlight pre { margin-bottom: 0; word-break: normal; } +.main-content .highlight pre, .main-content pre { padding: 0.8rem; overflow: auto; font-size: 0.9rem; line-height: 1.45; border-radius: 0.3rem; -webkit-overflow-scrolling: touch; } +.main-content pre code, .main-content pre tt { display: inline; max-width: initial; padding: 0; margin: 0; overflow: initial; line-height: inherit; word-wrap: normal; background-color: transparent; border: 0; } +.main-content pre code:before, .main-content pre code:after, .main-content pre tt:before, .main-content pre tt:after { content: normal; } +.main-content ul, .main-content ol { margin-top: 0; } +.main-content blockquote { padding: 0 1rem; margin-left: 0; color: #819198; border-left: 0.3rem solid #dce6f0; } +.main-content blockquote > :first-child { margin-top: 0; } +.main-content blockquote > :last-child { margin-bottom: 0; } +.main-content table { display: block; width: 100%; overflow: auto; word-break: normal; word-break: keep-all; -webkit-overflow-scrolling: touch; } +.main-content table th { font-weight: bold; } +.main-content table th, .main-content table td { padding: 0.5rem 1rem; border: 1px solid #e9ebec; } +.main-content dl { padding: 0; } +.main-content dl dt { padding: 0; margin-top: 1rem; font-size: 1rem; font-weight: bold; } +.main-content dl dd { padding: 0; margin-bottom: 1rem; } +.main-content hr { height: 2px; padding: 0; margin: 1rem 0; background-color: #eff0f1; border: 0; } + +.site-footer { padding-top: 2rem; margin-top: 2rem; border-top: solid 1px #eff0f1; } +@media screen and (min-width: 64em) { .site-footer { font-size: 1rem; } } +@media screen and (min-width: 42em) and (max-width: 64em) { .site-footer { font-size: 1rem; } } +@media screen and (max-width: 42em) { .site-footer { font-size: 0.9rem; } } + +.site-footer-owner { display: block; font-weight: bold; } + +.site-footer-credits { color: #819198; } + +h1#logo img { max-width: 100%; } + +h1#logo { margin-bottom: 0; } + +.main-logo { position: relative; z-index: 9; max-width: 70%; display: block; margin: 0 auto; margin-bottom: -5em; } diff --git a/assets/fonts/Noto-Sans-700/Noto-Sans-700.eot b/assets/fonts/Noto-Sans-700/Noto-Sans-700.eot new file mode 100644 index 00000000..03bf93fe Binary files /dev/null and b/assets/fonts/Noto-Sans-700/Noto-Sans-700.eot differ diff --git a/assets/fonts/Noto-Sans-700/Noto-Sans-700.svg b/assets/fonts/Noto-Sans-700/Noto-Sans-700.svg new file mode 100644 index 00000000..925fe474 --- /dev/null +++ b/assets/fonts/Noto-Sans-700/Noto-Sans-700.svg @@ -0,0 +1,336 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/fonts/Noto-Sans-700/Noto-Sans-700.ttf b/assets/fonts/Noto-Sans-700/Noto-Sans-700.ttf new file mode 100644 index 00000000..4599e3ca Binary files /dev/null and b/assets/fonts/Noto-Sans-700/Noto-Sans-700.ttf differ diff --git a/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff b/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff new file mode 100644 index 00000000..9d0b78df Binary files /dev/null and b/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff differ diff --git a/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff2 b/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff2 new file mode 100644 index 00000000..55fc44bc Binary files /dev/null and b/assets/fonts/Noto-Sans-700/Noto-Sans-700.woff2 differ diff --git a/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.eot b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.eot new file mode 100644 index 00000000..cb97b2b4 Binary files /dev/null and b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.eot differ diff --git a/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.svg b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.svg new file mode 100644 index 00000000..abdafc0f --- /dev/null +++ b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.svg @@ -0,0 +1,334 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.ttf b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.ttf new file mode 100644 index 00000000..6640dbeb Binary files /dev/null and b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.ttf differ diff --git a/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff new file mode 100644 index 00000000..209739ee Binary files /dev/null and b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff differ diff --git a/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff2 b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff2 new file mode 100644 index 00000000..f5525aa2 Binary files /dev/null and b/assets/fonts/Noto-Sans-700italic/Noto-Sans-700italic.woff2 differ diff --git a/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.eot b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.eot new file mode 100644 index 00000000..a9973499 Binary files /dev/null and b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.eot differ diff --git a/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.svg b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.svg new file mode 100644 index 00000000..dcd8fc89 --- /dev/null +++ b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.svg @@ -0,0 +1,337 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.ttf b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.ttf new file mode 100644 index 00000000..7f75a2d9 Binary files /dev/null and b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.ttf differ diff --git a/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff new file mode 100644 index 00000000..6dce67ce Binary files /dev/null and b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff differ diff --git a/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff2 b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff2 new file mode 100644 index 00000000..a9c14c49 Binary files /dev/null and b/assets/fonts/Noto-Sans-italic/Noto-Sans-italic.woff2 differ diff --git a/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.eot b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.eot new file mode 100644 index 00000000..15fc8bfc Binary files /dev/null and b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.eot differ diff --git a/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.svg b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.svg new file mode 100644 index 00000000..bd2894d6 --- /dev/null +++ b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.svg @@ -0,0 +1,335 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.ttf b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.ttf new file mode 100644 index 00000000..a83bbf9f Binary files /dev/null and b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.ttf differ diff --git a/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff new file mode 100644 index 00000000..17c85006 Binary files /dev/null and b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff differ diff --git a/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff2 b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff2 new file mode 100644 index 00000000..a87d9cd7 Binary files /dev/null and b/assets/fonts/Noto-Sans-regular/Noto-Sans-regular.woff2 differ diff --git a/assets/img/konveyor-logo-tackle.svg b/assets/img/konveyor-logo-tackle.svg new file mode 100644 index 00000000..4f21a7b4 --- /dev/null +++ b/assets/img/konveyor-logo-tackle.svg @@ -0,0 +1,189 @@ + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/assets/img/logo_location.txt b/assets/img/logo_location.txt new file mode 100644 index 00000000..2d6d6c6b --- /dev/null +++ b/assets/img/logo_location.txt @@ -0,0 +1 @@ +https://github.com/konveyor/community/tree/main/brand/logo diff --git a/assets/js/scale.fix.js b/assets/js/scale.fix.js new file mode 100644 index 00000000..2f4f8fd4 --- /dev/null +++ b/assets/js/scale.fix.js @@ -0,0 +1,30 @@ +(function (document) { + var metas = document.getElementsByTagName("meta"), + changeViewportContent = function (content) { + for (var i = 0; i < metas.length; i++) { + if (metas[i].name == "viewport") { + metas[i].content = content; + } + } + }, + initialize = function () { + changeViewportContent( + "width=device-width, minimum-scale=1.0, maximum-scale=1.0" + ); + }, + gestureStart = function () { + changeViewportContent( + "width=device-width, minimum-scale=0.25, maximum-scale=1.6" + ); + }, + gestureEnd = function () { + initialize(); + }; + + if (navigator.userAgent.match(/iPhone/i)) { + initialize(); + + document.addEventListener("touchstart", gestureStart, false); + document.addEventListener("touchend", gestureEnd, false); + } +})(document); diff --git a/documentation/doc-installing-and-using-tackle/docinfo.xml b/documentation/doc-installing-and-using-tackle/docinfo.xml new file mode 100644 index 00000000..1070f66e --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/docinfo.xml @@ -0,0 +1,15 @@ +{title} +{project-name} +{project-version} +{subtitle} + + {abstract} + + + + Red Hat Modernization and Migration + Documentation Team + migration-docs@redhat.com + + + diff --git a/documentation/doc-installing-and-using-tackle/master/index.html b/documentation/doc-installing-and-using-tackle/master/index.html new file mode 100644 index 00000000..20502be1 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/master/index.html @@ -0,0 +1,1637 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing and using Tackle

+ +
+

About Tackle

+
+
+

Tackle is a cloud-native application that assesses your applications to determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring. Tackle also helps you to plan the migration of your applications to an enterprise Kubernetes platform.

+
+
+

Tackle uses an interactive questionnaire for the assessment. The assessment process enables key stakeholders to gather information about applications, to discuss risks flagged by Tackle, and to reach a consensus in formulating recommendations for each application.

+
+
+
+
+

Installing Tackle

+
+
+

Installing the Tackle Operator

+
+

You download and install the Tackle Operator on an Enterprise Kubernetes Platform cluster.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Install the Tackle Operator:

    +
    +
    +
    $ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml
    +
    +
    +
    +

    The Tackle Operator is installed in the my-tackle-operator namespace by default.

    +
    +
  2. +
  3. +

    Verify the Tackle Operator installation by viewing its resources:

    +
    +
    +
    $ kubectl get all -n my-tackle-operator
    +
    +
    +
  4. +
+
+
+
+

Installing the Tackle application

+
+

You install Tackle in a namespace by creating an instance of the Tackle application.

+
+
+
Prerequisites
+
    +
  • +

    The Tackle Operator must be installed on the cluster.

    +
  • +
  • +

    You must have project-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Create an instance of the Tackle application, specifying its namespace:

    +
    +
    +
    $ kubectl apply -n <namespace> -f https://raw.githubusercontent.com/konveyor/tackle-operator/main/src/main/resources/k8s/tackle/tackle.yaml
    +
    +
    +
    + + + + + +
    + + +
    +

    You can create multiple instances of the Tackle application in the same namespace by specifying a unique name for each instance in the tackle.yaml file.

    +
    +
    +
    +
  2. +
  3. +

    In the Kubernetes dashboard, click WorkloadsDeployments to verify the installation.

    +
  4. +
+
+
+
+

Logging in to the Tackle web console

+
+

You can log in to the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    You must have the Tackle application installed.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Kubernetes dashboard, click ServicesIngresses.

    +
  2. +
  3. +

    Click the Endpoint of the tackle-sample ingress to launch the Tackle web console in a new browser window.

    +
  4. +
  5. +

    Enter tackle in the Username or email field, password in the Password field, and click Log in.

    +
  6. +
+
+
+ + + + + +
+ + +
+

You must change the default password of the tackle user.

+
+
+
+
+
+

Tackle web console services

+
+

Tackle web console provides the following services:

+
+
+
    +
  • +

    Application inventory

    +
  • +
  • +

    Assessments

    +
  • +
  • +

    Reviews

    +
  • +
  • +

    Reports

    +
  • +
  • +

    Controls

    +
  • +
+
+
+

Application inventory

+
+

The Application inventory page enables you to perform the following tasks:

+
+
+
    +
  • +

    Manage your application portfolio.

    +
  • +
  • +

    Define and manage application dependencies.

    +
  • +
  • +

    Link applications to the business services that they support.

    +
  • +
  • +

    Describe and categorize applications by using tags.

    +
  • +
+
+
+
+

Assessments

+
+

You can assess your applications on the Application inventory page.

+
+
+

The assessment helps you determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring.

+
+
+

The assessment is an interactive questionnaire that gathers information and identifies possible risks and their severity.

+
+
+
+

Reviews

+
+

You can review a completed assessment on the Application inventory page.

+
+
+

The following information is collected from each reviewer:

+
+
+
    +
  • +

    Proposed action: Proposed action for the application, for example, replatforming or rehosting.

    +
  • +
  • +

    Effort estimate: How much effort is involved in migrating the application, based on the proposed action and the identified risks.

    +
  • +
  • +

    Business criticality: How critical the application is to your business on a scale of 1 to 10.

    +
  • +
  • +

    Work priority: Your work priority estimate for the proposed action on a scale of 1 to 10.

    +
  • +
+
+
+

The Reports page displays the results of the reviews.

+
+
+
+

Reports

+
+

The Reports page displays the results of the application assessments and reviews and can help you to plan your migration.

+
+
+

The reports provide information about the following:

+
+
+
    +
  • +

    Suitability of applications for containerization.

    +
  • +
  • +

    Possible risks and severity.

    +
  • +
  • +

    Adoption plan based on estimated effort, work priority, and application dependencies.

    +
  • +
+
+
+
+

Controls

+
+

The Controls page enables you to manage the following entities:

+
+
+
    +
  • +

    Stakeholder: A stakeholder is an individual with an interest in an application or a subject matter expert.

    +
  • +
  • +

    Stakeholder group: A stakeholder group is a group of related stakeholders. A stakeholder can belong to one or more stakeholder groups. Stakeholder groups are used to assign multiple stakeholders to review an assessment.

    +
  • +
  • +

    Job function: A job function is an attribute of a stakeholder. You use a predefined job function or create a new job function.

    +
  • +
  • +

    Business service: A business service is an attribute of an application, for example, credit card service, transportation, or IT support. You can use a predefined business service or create a new business service.

    +
  • +
  • +

    Tag: A tag is an attribute of an application. Tags are an extensible and flexible way to add metadata to applications. Tags are grouped under a parent tag type. You can use a predefined tag or create a new tag.

    +
  • +
  • +

    Tag type: A tag type defines the rank and background color of a group of related tags.

    +
  • +
+
+
+
+
+
+
+

Managing users and credentials

+
+
+

You can manage Tackle users and passwords by using the Keycloak admin console.

+
+
+

Accessing the Keycloak admin console

+
+

When you install Tackle, a Keycloak admin user is created. You must obtain the admin user name and password to log in to the Keycloak admin console. The credentials are stored in the tackle-keycloak secret.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Run the following command to obtain the admin credentials:

    +
    +
    +
    $ kubectl get secret tackle-keycloak -o go-template='{{range $k,$v := .data}}{{printf "%s: " $k}}{{if not $v}}{{$v}}{{else}}{{$v | base64decode}}{{end}}{{"\n"}}{{end}}'
    +
    +
    +
    +
    Example output
    +
    +
    ADMIN_PASSWORD: <password>
    +ADMIN_USERNAME: admin
    +
    +
    +
  2. +
  3. +

    Launch a browser and navigate to https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  4. +
  5. +

    Log in to the Keycloak admin console with the admin user name and password.

    +
  6. +
+
+
+
+

Changing the default password

+
+

You must change the default password of the tackle user.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Locate the tackle user in the Tackle realm. See Searching for users in the Keycloak documentation.

    +
  4. +
  5. +

    Update the tackle user’s password. See User Credentials.

    +
  6. +
  7. +

    Log out of the Keycloak admin console.

    +
  8. +
  9. +

    Log in to the Tackle web console as the tackle user to verify the new password.

    +
  10. +
+
+
+
+

Adding users

+
+

You can add users by using the Keycloak admin console.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Create a new user in the Tackle realm. See Creating a new user in the Keycloak documentation.

    +
  4. +
  5. +

    Create a password for the new user. See Creating a password for the user.

    +
  6. +
  7. +

    Optional: Set attributes and permissions for the new user. See User profile.

    +
  8. +
+
+

Additional resources for Keycloak

+
+ +
+
+
+
+
+

Managing applications

+
+
+

You can create, import, tag, and modify your applications in the Application inventory page of the Tackle web console.

+
+
+

Creating an application

+
+

You can create an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory and then click Create new.

    +
  2. +
  3. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the application.

      +
    • +
    • +

      Description: Optional. Description of the application.

      +
    • +
    • +

      Business service: Optional. You can select a business service that describes the application.

      +
    • +
    • +

      Tags: Optional. You can select one or more tags.

      +
    • +
    • +

      Comments: Optional. Comments about the application.

      +
    • +
    +
    +
  4. +
  5. +

    Click Create.

    +
    +

    The new application is displayed on the Application inventory page.

    +
    +
  6. +
  7. +

    Expand the application to view its tags and comments.

    +
  8. +
+
+
+
+

Importing applications

+
+

You can import one or more applications into the Application inventory page of the Tackle web console by using a CSV file.

+
+
+ + + + + +
+ + +
+

You cannot create tags or business services by importing a CSV file. Specified tags or business services must exist in the web console before you import the applications.

+
+
+
+
+

The CSV file contains the following fields:

+
+
+

Record Type 1:

+
+
+
    +
  • +

    Describes an application or application dependencies.

    +
  • +
  • +

    Required for all records.

    +
  • +
+
+
+

The following values are allowed for Record Type 1:

+
+
+
    +
  • +

    1: Application: This option has the following fields:

    +
    +
      +
    • +

      Application Name: Required.

      +
    • +
    • +

      Description: Optional.

      +
    • +
    • +

      Comments: Optional.

      +
    • +
    • +

      Business Service: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag Type <1..20>: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag <1..20>: Optional. Must exist in the web console.

      +
      +

      You can import up to 20 Tag Type <x> and Tag <x> fields.

      +
      +
    • +
    +
    +
  • +
  • +

    2: Application dependencies: This option requires the following fields:

    +
    +
      +
    • +

      Application Name

      +
    • +
    • +

      Dependency: Must be the same as the Application Name of the dependency.

      +
    • +
    • +

      Dependency Direction: Allowed values are northbound and southbound.

      +
      +

      All other fields are empty.

      +
      +
    • +
    +
    +
  • +
+
+ + +++++++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1. CSV example
Record Type 1Application NameDependencyDependency DirectionDescriptionCommentsBusiness ServiceTag Type 1Tag 1Tag Type 2Tag 2Tag Type 3Tag 3

1

Imported-Purchasing

Vendor management

Required for purchase order processing and accounts payable

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

2

Imported-Purchasing

Tiller

northbound

1

Imported-PO

Requisitions, purchase orders, goods received

Requisition to receipt

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-Payroll

Payroll

To be retired at the end of the financial year

Finance and HR

Language

Java

Database

Oracle

Language

Java

2

Imported-Payroll

Imported-GL

northbound

2

Imported-Payroll

Imported-HR

southbound

1

Imported-GL

General Ledger

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-HR

Human Resources

Go live scheduled for Q3

Finance and HR

Operating System

RHEL 8

Database

PostgreSQL

Language

Python

+
+
Prerequisites
+
    +
  • +

    Valid CSV file.

    +
  • +
  • +

    Specified business services, tag types, and tags created in the web console.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Import.

    +
  4. +
  5. +

    Browse to the CSV file and click Open.

    +
  6. +
  7. +

    Click Import.

    +
    +

    The imported applications are displayed on the Application inventory page .

    +
    +
  8. +
+
+
+
+

Managing application imports

+
+

You can manage application imports on the Application import page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Manage imports.

    +
    +

    The Application import page displays a list of application imports.

    +
    +
  4. +
  5. +

    Click the Options menu kebab beside an application import and select one of the following options:

    +
    +
      +
    • +

      Delete deletes the application import.

      +
    • +
    • +

      View error report displays a table of application import errors.

      +
    • +
    • +

      Export errors enables you to save the application import errors as a CSV file.

      +
    • +
    +
    +
  6. +
+
+
+
+

Updating the tags assigned to an application

+
+

You can add or remove tags assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Add or delete tags and click Save.

    +
  6. +
  7. +

    Expand the application to view the updated tags.

    +
  8. +
+
+
+
+

Updating the business service assigned to an application

+
+

You can update the business service assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The business service must exist on the Controls page.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Select a business service and click Save.

    +
    +

    The updated business service is displayed in the Business service column of the application.

    +
    +
  6. +
+
+
+
+

Managing application dependencies

+
+

You can add, delete, and view application dependencies in the Manage dependencies window on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application and select Manage dependencies.

    +
  4. +
  5. +

    To add dependencies, select applications in the northbound or southbound dependencies fields.

    +
  6. +
  7. +

    To remove dependencies, delete selected applications in the northbound or southbound dependencies fields.

    +
  8. +
  9. +

    Click Close to save and close.

    +
  10. +
+
+
+
+
+
+

Managing assessments

+
+
+

You can start, edit, review, and delete application assessments in the Application inventory page of the Tackle web console.

+
+
+

Starting an assessment

+
+

You start an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application that does not have a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Select individual stakeholders or stakeholder groups and then click Next.

    +
  6. +
  7. +

    Select responses to questions on each page of the Application assessment wizard and then click Next.

    +
    + + + + + +
    + + +
    +

    All questions are mandatory.

    +
    +
    +
    +
  8. +
  9. +

    When you have completed all the responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
    +

    The Assessment status of each assessed application is Completed.

    +
    +
  10. +
+
+
+
+

Editing an assessment

+
+

You can make an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Click Continue to confirm that you want to edit the assessment.

    +
  6. +
  7. +

    After you have updated your responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
  8. +
+
+
+
+

Reviewing an assessment

+
+

You review an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status and a Not started review status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and a Not started review status and click the Review button in the toolbar.

    +
  4. +
  5. +

    Review the assessment in the Assessment summary section on the Review page.

    +
    +

    The Assessment summary table contains a Risk column that indicates the severity of the risk associated with each response.

    +
    +
  6. +
  7. +

    Select a Proposed action and an Effort estimate.

    +
  8. +
  9. +

    Set values for Business criticality and Work priority.

    +
  10. +
  11. +

    Optional: Enter comments in the Comments field.

    +
  12. +
  13. +

    Click Submit review.

    +
    +

    The Review status of each application is Completed.

    +
    +
  14. +
  15. +

    Expand the application to view the review results.

    +
  16. +
+
+
+
+

Copying and applying assessments and reviews

+
+

You copy an assessment or assessment and review from a single application and apply them to multiple applications on the Application inventory page of the Tackle web console.

+
+
+

You can apply assessments and reviews to groups of related applications, for example, applications written in Java or belonging to the same business service.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status or Completed assessment and review statuses, depending on whether you are copying an assessment or an assessment and review.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status or Completed assessment and review statuses.

    +
  4. +
  5. +

    Select Copy assessment or Copy assessment and review.

    +
  6. +
  7. +

    Optional: In the dialog box, click Name to select a filter, for example, Tag, and select a tag, for example, Java, to display a filtered list of applications.

    +
  8. +
  9. +

    Select the applications to which you want to apply the copied assessment or assessment and review.

    +
  10. +
  11. +

    If a selected application has an existing assessment or review, select the Yes, continue check box to confirm that existing assessments and reviews will be overwritten.

    +
  12. +
  13. +

    Click Copy.

    +
    +

    The selected applications display a Completed assessment status or Completed assessment and review statuses.

    +
    +
  14. +
+
+
+
+

Deleting an assessment

+
+

You delete an application assessment on the Application inventory page of the Tackle web console. Deleting an assessment deletes its review.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status and select Discard assessment.

    +
  4. +
  5. +

    Click Continue to confirm the deletion.

    +
    +

    The Assessment and Review status of the application are Not started.

    +
    +
  6. +
+
+
+
+
+
+

Managing controls

+
+
+

The Controls page of the Tackle web console enables you to manage stakeholders, stakeholder groups, job functions, business services, and tags.

+
+
+

Creating a stakeholder

+
+

You can create a stakeholder on the Controls page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The stakeholder must have a valid email address.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholders tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Email: Email address of the stakeholder.

      +
    • +
    • +

      Display name: Name of the stakeholder.

      +
    • +
    • +

      Job function: Optional. You can select a predefined job function or type a job function to create it.

      +
    • +
    • +

      Groups: Optional. You can select one or more stakeholder groups from a list of stakeholder groups that you have created.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder is displayed on the Stakeholders tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder to view the stakeholder groups to which the stakeholder belongs.

    +
  10. +
+
+
+
+

Creating a stakeholder group

+
+

You can create stakeholder groups on the Controls page of the Tackle web console. Stakeholder groups enable you to assign multiple stakeholders to review an assessment.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholder groups tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the stakeholder group.

      +
    • +
    • +

      Description: Optional. Description of the stakeholder group.

      +
    • +
    • +

      Member(s): Optional. You can select one or more stakeholders to add to the group.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder group is displayed on the Stakeholder groups tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder group to view the group members.

    +
  10. +
+
+
+
+

Creating a job function

+
+

A job function is an attribute of a stakeholder. You can use a predefined job function or create a new job function on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Job functions tab and then click Create new.

    +
  4. +
  5. +

    Enter the Name of the job function and click Create.

    +
    +

    The new job function is displayed on the Job functions tab.

    +
    +
  6. +
+
+
+
+

Creating a business service

+
+

A business service is an attribute of an application. You can create a business service on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Business services tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the business service.

      +
    • +
    • +

      Description: Optional: Description of the business service.

      +
    • +
    • +

      Owner: Optional: Select a stakeholder.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new business service is displayed on the Business services tab.

    +
    +
  8. +
+
+
+
+

Creating a tag type

+
+

You can create a tag type on the Controls page of the Tackle web console.

+
+
+

A tag type is the parent of a group of related tags. The tag type defines the rank and background color of the tags on the Application inventory page.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag type.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag type.

      +
    • +
    • +

      Rank: The rank determines the order in which the tags are displayed.

      +
    • +
    • +

      Color: The color is displayed as the background color for all tags associated with this tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag type is displayed on the Tags tab.

    +
    +
  8. +
+
+
+
+

Creating a tag

+
+

You can create a tag on the Controls page of the Tackle web console.

+
+
+

Tags are an extensible and flexible way to add metadata to applications. Tags are added to applications on the Application inventory page.

+
+
+

Tags belong to a parent tag type that determines the display order and color of the tags. You can use a predefined tag type or create a new tag type.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag.

      +
    • +
    • +

      Tag type: Select a tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag is displayed under its tag type on the Tags tab.

    +
    +
  8. +
+
+
+
+
+
+

About reports

+
+
+

You can view a report of the assessments and reviews on the Reports page of the Tackle web console.

+
+
+

The Reports page contains the following sections:

+
+
+
+
Current landscape
+
+

This section displays all applications according to their risk levels.

+
+
Adoption candidate distribution
+
+

This section lists the assessed applications with the following columns:

+
+
    +
  • +

    Criticality is based on the Business criticality value of the review.

    +
  • +
  • +

    Priority is based on the Work priority value of the review.

    +
  • +
  • +

    Effort is based on the Effort estimate value of the review.

    +
  • +
  • +

    Decision is based on the Proposed action value of the review.

    +
    +

    By default, all applications are selected. You can clear some of the application check boxes to filter the report.

    +
    +
  • +
+
+
+
Suggested adoption plan
+
+

This section displays a suggested adoption plan based on effort, priority, and dependencies.

+
+
Identified risks
+
+

This section lists the severe risks identified in the assessments for all applications.

+
+
+
+
+
+
+

Upgrading the Tackle application

+
+
+

You manually upgrade instances of the Tackle application.

+
+
+

Upgrading from version 1.1.0 to 1.2.0

+
+

You manually upgrade an instance of the Tackle application from 1.1.0 to 1.2.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-keycloak keycloak-theme=quay.io/konveyor/tackle-keycloak-init:1.2.0
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.2.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.2.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.2.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.2.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+

Upgrading from version 1.0.0 to 1.1.0

+
+

You manually upgrade an instance of the Tackle application from 1.0.0 to 1.1.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl -n <namespace> exec deployments/<tackle_instance>-keycloak \
    +  -c <tackle_instance>-keycloak -- bash -c '/opt/jboss/keycloak/bin/kcadm.sh \
    +  update realms/tackle -s internationalizationEnabled=true -s supportedLocales+=en \
    +  -s supportedLocales+=es -s defaultLocale=en --server http://localhost:8080/auth \
    +  --realm master --user $KEYCLOAK_USER --password $KEYCLOAK_PASSWORD'
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.1.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.1.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.1.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.1.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/about-pathfinder/index.html b/documentation/doc-installing-and-using-tackle/modules/about-pathfinder/index.html new file mode 100644 index 00000000..9c21aa22 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/about-pathfinder/index.html @@ -0,0 +1,55 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About Tackle

+
+

Tackle is a cloud-native application that assesses your applications to determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring. Tackle also helps you to plan the migration of your applications to an enterprise Kubernetes platform.

+
+
+

Tackle uses an interactive questionnaire for the assessment. The assessment process enables key stakeholders to gather information about applications, to discuss risks flagged by Tackle, and to reach a consensus in formulating recommendations for each application.

+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/about-reports/index.html b/documentation/doc-installing-and-using-tackle/modules/about-reports/index.html new file mode 100644 index 00000000..3baab721 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/about-reports/index.html @@ -0,0 +1,94 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About reports

+
+

You can view a report of the assessments and reviews on the Reports page of the Tackle web console.

+
+
+

The Reports page contains the following sections:

+
+
+
+
Current landscape
+
+

This section displays all applications according to their risk levels.

+
+
Adoption candidate distribution
+
+

This section lists the assessed applications with the following columns:

+
+
    +
  • +

    Criticality is based on the Business criticality value of the review.

    +
  • +
  • +

    Priority is based on the Work priority value of the review.

    +
  • +
  • +

    Effort is based on the Effort estimate value of the review.

    +
  • +
  • +

    Decision is based on the Proposed action value of the review.

    +
    +

    By default, all applications are selected. You can clear some of the application check boxes to filter the report.

    +
    +
  • +
+
+
+
Suggested adoption plan
+
+

This section displays a suggested adoption plan based on effort, priority, and dependencies.

+
+
Identified risks
+
+

This section lists the severe risks identified in the assessments for all applications.

+
+
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/accessing-console/index.html b/documentation/doc-installing-and-using-tackle/modules/accessing-console/index.html new file mode 100644 index 00000000..4ff79613 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/accessing-console/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Logging in to the Tackle web console

+
+

You can log in to the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    You must have the Tackle application installed.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Kubernetes dashboard, click ServicesIngresses.

    +
  2. +
  3. +

    Click the Endpoint of the tackle-sample ingress to launch the Tackle web console in a new browser window.

    +
  4. +
  5. +

    Enter tackle in the Username or email field, password in the Password field, and click Log in.

    +
  6. +
+
+
+ + + + + +
+
Important
+
+
+

You must change the default password of the tackle user.

+
+
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/accessing-keycloak-admin-console/index.html b/documentation/doc-installing-and-using-tackle/modules/accessing-keycloak-admin-console/index.html new file mode 100644 index 00000000..3d6ad88e --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/accessing-keycloak-admin-console/index.html @@ -0,0 +1,86 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Accessing the Keycloak admin console

+
+

When you install Tackle, a Keycloak admin user is created. You must obtain the admin user name and password to log in to the Keycloak admin console. The credentials are stored in the tackle-keycloak secret.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Run the following command to obtain the admin credentials:

    +
    +
    +
    $ kubectl get secret tackle-keycloak -o go-template='{{range $k,$v := .data}}{{printf "%s: " $k}}{{if not $v}}{{$v}}{{else}}{{$v | base64decode}}{{end}}{{"\n"}}{{end}}'
    +
    +
    +
    +
    Example output
    +
    +
    ADMIN_PASSWORD: <password>
    +ADMIN_USERNAME: admin
    +
    +
    +
  2. +
  3. +

    Launch a browser and navigate to https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  4. +
  5. +

    Log in to the Keycloak admin console with the admin user name and password.

    +
  6. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/adding-users/index.html b/documentation/doc-installing-and-using-tackle/modules/adding-users/index.html new file mode 100644 index 00000000..b828b894 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/adding-users/index.html @@ -0,0 +1,80 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Adding users

+
+

You can add users by using the Keycloak admin console.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Create a new user in the Tackle realm. See Creating a new user in the Keycloak documentation.

    +
  4. +
  5. +

    Create a password for the new user. See Creating a password for the user.

    +
  6. +
  7. +

    Optional: Set attributes and permissions for the new user. See User profile.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/changing-default-password/index.html b/documentation/doc-installing-and-using-tackle/modules/changing-default-password/index.html new file mode 100644 index 00000000..baab066e --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/changing-default-password/index.html @@ -0,0 +1,83 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Changing the default password

+
+

You must change the default password of the tackle user.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Locate the tackle user in the Tackle realm. See Searching for users in the Keycloak documentation.

    +
  4. +
  5. +

    Update the tackle user’s password. See User Credentials.

    +
  6. +
  7. +

    Log out of the Keycloak admin console.

    +
  8. +
  9. +

    Log in to the Tackle web console as the tackle user to verify the new password.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/common-attributes/index.html b/documentation/doc-installing-and-using-tackle/modules/common-attributes/index.html new file mode 100644 index 00000000..22860ea0 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/common-attributes/index.html @@ -0,0 +1,49 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+ + + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/console-services/index.html b/documentation/doc-installing-and-using-tackle/modules/console-services/index.html new file mode 100644 index 00000000..40b1a6aa --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/console-services/index.html @@ -0,0 +1,197 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Tackle web console services

+
+
+
+

Tackle web console provides the following services:

+
+
+
    +
  • +

    Application inventory

    +
  • +
  • +

    Assessments

    +
  • +
  • +

    Reviews

    +
  • +
  • +

    Reports

    +
  • +
  • +

    Controls

    +
  • +
+
+
+
+
+

Application inventory

+
+
+

The Application inventory page enables you to perform the following tasks:

+
+
+
    +
  • +

    Manage your application portfolio.

    +
  • +
  • +

    Define and manage application dependencies.

    +
  • +
  • +

    Link applications to the business services that they support.

    +
  • +
  • +

    Describe and categorize applications by using tags.

    +
  • +
+
+
+
+
+

Assessments

+
+
+

You can assess your applications on the Application inventory page.

+
+
+

The assessment helps you determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring.

+
+
+

The assessment is an interactive questionnaire that gathers information and identifies possible risks and their severity.

+
+
+
+
+

Reviews

+
+
+

You can review a completed assessment on the Application inventory page.

+
+
+

The following information is collected from each reviewer:

+
+
+
    +
  • +

    Proposed action: Proposed action for the application, for example, replatforming or rehosting.

    +
  • +
  • +

    Effort estimate: How much effort is involved in migrating the application, based on the proposed action and the identified risks.

    +
  • +
  • +

    Business criticality: How critical the application is to your business on a scale of 1 to 10.

    +
  • +
  • +

    Work priority: Your work priority estimate for the proposed action on a scale of 1 to 10.

    +
  • +
+
+
+

The Reports page displays the results of the reviews.

+
+
+
+
+

Reports

+
+
+

The Reports page displays the results of the application assessments and reviews and can help you to plan your migration.

+
+
+

The reports provide information about the following:

+
+
+
    +
  • +

    Suitability of applications for containerization.

    +
  • +
  • +

    Possible risks and severity.

    +
  • +
  • +

    Adoption plan based on estimated effort, work priority, and application dependencies.

    +
  • +
+
+
+
+
+

Controls

+
+
+

The Controls page enables you to manage the following entities:

+
+
+
    +
  • +

    Stakeholder: A stakeholder is an individual with an interest in an application or a subject matter expert.

    +
  • +
  • +

    Stakeholder group: A stakeholder group is a group of related stakeholders. A stakeholder can belong to one or more stakeholder groups. Stakeholder groups are used to assign multiple stakeholders to review an assessment.

    +
  • +
  • +

    Job function: A job function is an attribute of a stakeholder. You use a predefined job function or create a new job function.

    +
  • +
  • +

    Business service: A business service is an attribute of an application, for example, credit card service, transportation, or IT support. You can use a predefined business service or create a new business service.

    +
  • +
  • +

    Tag: A tag is an attribute of an application. Tags are an extensible and flexible way to add metadata to applications. Tags are grouped under a parent tag type. You can use a predefined tag or create a new tag.

    +
  • +
  • +

    Tag type: A tag type defines the rank and background color of a group of related tags.

    +
  • +
+
+
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/copying-assessments-and-reviews/index.html b/documentation/doc-installing-and-using-tackle/modules/copying-assessments-and-reviews/index.html new file mode 100644 index 00000000..fb72fe45 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/copying-assessments-and-reviews/index.html @@ -0,0 +1,92 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Copying and applying assessments and reviews

+
+

You copy an assessment or assessment and review from a single application and apply them to multiple applications on the Application inventory page of the Tackle web console.

+
+
+

You can apply assessments and reviews to groups of related applications, for example, applications written in Java or belonging to the same business service.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status or Completed assessment and review statuses, depending on whether you are copying an assessment or an assessment and review.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status or Completed assessment and review statuses.

    +
  4. +
  5. +

    Select Copy assessment or Copy assessment and review.

    +
  6. +
  7. +

    Optional: In the dialog box, click Name to select a filter, for example, Tag, and select a tag, for example, Java, to display a filtered list of applications.

    +
  8. +
  9. +

    Select the applications to which you want to apply the copied assessment or assessment and review.

    +
  10. +
  11. +

    If a selected application has an existing assessment or review, select the Yes, continue check box to confirm that existing assessments and reviews will be overwritten.

    +
  12. +
  13. +

    Click Copy.

    +
    +

    The selected applications display a Completed assessment status or Completed assessment and review statuses.

    +
    +
  14. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-application/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-application/index.html new file mode 100644 index 00000000..2f7fb340 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-application/index.html @@ -0,0 +1,91 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating an application

+
+

You can create an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory and then click Create new.

    +
  2. +
  3. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the application.

      +
    • +
    • +

      Description: Optional. Description of the application.

      +
    • +
    • +

      Business service: Optional. You can select a business service that describes the application.

      +
    • +
    • +

      Tags: Optional. You can select one or more tags.

      +
    • +
    • +

      Comments: Optional. Comments about the application.

      +
    • +
    +
    +
  4. +
  5. +

    Click Create.

    +
    +

    The new application is displayed on the Application inventory page.

    +
    +
  6. +
  7. +

    Expand the application to view its tags and comments.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-business-service/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-business-service/index.html new file mode 100644 index 00000000..ea37ad8b --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-business-service/index.html @@ -0,0 +1,85 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a business service

+
+

A business service is an attribute of an application. You can create a business service on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Business services tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the business service.

      +
    • +
    • +

      Description: Optional: Description of the business service.

      +
    • +
    • +

      Owner: Optional: Select a stakeholder.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new business service is displayed on the Business services tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-job-function/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-job-function/index.html new file mode 100644 index 00000000..dd19d711 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-job-function/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a job function

+
+

A job function is an attribute of a stakeholder. You can use a predefined job function or create a new job function on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Job functions tab and then click Create new.

    +
  4. +
  5. +

    Enter the Name of the job function and click Create.

    +
    +

    The new job function is displayed on the Job functions tab.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder-group/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder-group/index.html new file mode 100644 index 00000000..ffeea033 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder-group/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder group

+
+

You can create stakeholder groups on the Controls page of the Tackle web console. Stakeholder groups enable you to assign multiple stakeholders to review an assessment.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholder groups tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the stakeholder group.

      +
    • +
    • +

      Description: Optional. Description of the stakeholder group.

      +
    • +
    • +

      Member(s): Optional. You can select one or more stakeholders to add to the group.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder group is displayed on the Stakeholder groups tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder group to view the group members.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder/index.html new file mode 100644 index 00000000..878055de --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder/index.html @@ -0,0 +1,99 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder

+
+

You can create a stakeholder on the Controls page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The stakeholder must have a valid email address.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholders tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Email: Email address of the stakeholder.

      +
    • +
    • +

      Display name: Name of the stakeholder.

      +
    • +
    • +

      Job function: Optional. You can select a predefined job function or type a job function to create it.

      +
    • +
    • +

      Groups: Optional. You can select one or more stakeholder groups from a list of stakeholder groups that you have created.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder is displayed on the Stakeholders tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder to view the stakeholder groups to which the stakeholder belongs.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-tag-type/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-tag-type/index.html new file mode 100644 index 00000000..0cc3a417 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-tag-type/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag type

+
+

You can create a tag type on the Controls page of the Tackle web console.

+
+
+

A tag type is the parent of a group of related tags. The tag type defines the rank and background color of the tags on the Application inventory page.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag type.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag type.

      +
    • +
    • +

      Rank: The rank determines the order in which the tags are displayed.

      +
    • +
    • +

      Color: The color is displayed as the background color for all tags associated with this tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag type is displayed on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/creating-tag/index.html b/documentation/doc-installing-and-using-tackle/modules/creating-tag/index.html new file mode 100644 index 00000000..48d57c82 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/creating-tag/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag

+
+

You can create a tag on the Controls page of the Tackle web console.

+
+
+

Tags are an extensible and flexible way to add metadata to applications. Tags are added to applications on the Application inventory page.

+
+
+

Tags belong to a parent tag type that determines the display order and color of the tags. You can use a predefined tag type or create a new tag type.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag.

      +
    • +
    • +

      Tag type: Select a tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag is displayed under its tag type on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/deleting-assessment/index.html b/documentation/doc-installing-and-using-tackle/modules/deleting-assessment/index.html new file mode 100644 index 00000000..70d1cea6 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/deleting-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Deleting an assessment

+
+

You delete an application assessment on the Application inventory page of the Tackle web console. Deleting an assessment deletes its review.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status and select Discard assessment.

    +
  4. +
  5. +

    Click Continue to confirm the deletion.

    +
    +

    The Assessment and Review status of the application are Not started.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/editing-assessment/index.html b/documentation/doc-installing-and-using-tackle/modules/editing-assessment/index.html new file mode 100644 index 00000000..83ffd9b4 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/editing-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Editing an assessment

+
+

You can make an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Click Continue to confirm that you want to edit the assessment.

    +
  6. +
  7. +

    After you have updated your responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/images/kebab.png b/documentation/doc-installing-and-using-tackle/modules/images/kebab.png new file mode 100644 index 00000000..81893bd4 Binary files /dev/null and b/documentation/doc-installing-and-using-tackle/modules/images/kebab.png differ diff --git a/documentation/doc-installing-and-using-tackle/modules/images/konveyor-logo-tackle.svg b/documentation/doc-installing-and-using-tackle/modules/images/konveyor-logo-tackle.svg new file mode 100644 index 00000000..4f21a7b4 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/images/konveyor-logo-tackle.svg @@ -0,0 +1,189 @@ + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/documentation/doc-installing-and-using-tackle/modules/importing-applications/index.html b/documentation/doc-installing-and-using-tackle/modules/importing-applications/index.html new file mode 100644 index 00000000..5b1294fc --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/importing-applications/index.html @@ -0,0 +1,324 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Importing applications

+
+

You can import one or more applications into the Application inventory page of the Tackle web console by using a CSV file.

+
+
+ + + + + +
+
Note
+
+
+

You cannot create tags or business services by importing a CSV file. Specified tags or business services must exist in the web console before you import the applications.

+
+
+
+
+

The CSV file contains the following fields:

+
+
+

Record Type 1:

+
+
+
    +
  • +

    Describes an application or application dependencies.

    +
  • +
  • +

    Required for all records.

    +
  • +
+
+
+

The following values are allowed for Record Type 1:

+
+
+
    +
  • +

    1: Application: This option has the following fields:

    +
    +
      +
    • +

      Application Name: Required.

      +
    • +
    • +

      Description: Optional.

      +
    • +
    • +

      Comments: Optional.

      +
    • +
    • +

      Business Service: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag Type <1..20>: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag <1..20>: Optional. Must exist in the web console.

      +
      +

      You can import up to 20 Tag Type <x> and Tag <x> fields.

      +
      +
    • +
    +
    +
  • +
  • +

    2: Application dependencies: This option requires the following fields:

    +
    +
      +
    • +

      Application Name

      +
    • +
    • +

      Dependency: Must be the same as the Application Name of the dependency.

      +
    • +
    • +

      Dependency Direction: Allowed values are northbound and southbound.

      +
      +

      All other fields are empty.

      +
      +
    • +
    +
    +
  • +
+
+ + +++++++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1. CSV example
Record Type 1Application NameDependencyDependency DirectionDescriptionCommentsBusiness ServiceTag Type 1Tag 1Tag Type 2Tag 2Tag Type 3Tag 3

1

Imported-Purchasing

Vendor management

Required for purchase order processing and accounts payable

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

2

Imported-Purchasing

Tiller

northbound

1

Imported-PO

Requisitions, purchase orders, goods received

Requisition to receipt

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-Payroll

Payroll

To be retired at the end of the financial year

Finance and HR

Language

Java

Database

Oracle

Language

Java

2

Imported-Payroll

Imported-GL

northbound

2

Imported-Payroll

Imported-HR

southbound

1

Imported-GL

General Ledger

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-HR

Human Resources

Go live scheduled for Q3

Finance and HR

Operating System

RHEL 8

Database

PostgreSQL

Language

Python

+
+
Prerequisites
+
    +
  • +

    Valid CSV file.

    +
  • +
  • +

    Specified business services, tag types, and tags created in the web console.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Import.

    +
  4. +
  5. +

    Browse to the CSV file and click Open.

    +
  6. +
  7. +

    Click Import.

    +
    +

    The imported applications are displayed on the Application inventory page .

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/installing-operator/index.html b/documentation/doc-installing-and-using-tackle/modules/installing-operator/index.html new file mode 100644 index 00000000..0f325d00 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/installing-operator/index.html @@ -0,0 +1,84 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle Operator

+
+

You download and install the Tackle Operator on an Enterprise Kubernetes Platform cluster.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Install the Tackle Operator:

    +
    +
    +
    $ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml
    +
    +
    +
    +

    The Tackle Operator is installed in the {namespace} namespace by default.

    +
    +
  2. +
  3. +

    Verify the Tackle Operator installation by viewing its resources:

    +
    +
    +
    $ kubectl get all -n my-tackle-operator
    +
    +
    +
  4. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/installing-tackle-application/index.html b/documentation/doc-installing-and-using-tackle/modules/installing-tackle-application/index.html new file mode 100644 index 00000000..f705bdb7 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/installing-tackle-application/index.html @@ -0,0 +1,93 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle application

+
+

You install Tackle in a namespace by creating an instance of the Tackle application.

+
+
+
Prerequisites
+
    +
  • +

    The Tackle Operator must be installed on the cluster.

    +
  • +
  • +

    You must have project-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Create an instance of the Tackle application, specifying its namespace:

    +
    +
    +
    $ kubectl apply -n <namespace> -f https://raw.githubusercontent.com/konveyor/tackle-operator/main/src/main/resources/k8s/tackle/tackle.yaml
    +
    +
    +
    + + + + + +
    +
    Note
    +
    +
    +

    You can create multiple instances of the Tackle application in the same namespace by specifying a unique name for each instance in the tackle.yaml file.

    +
    +
    +
    +
  2. +
  3. +

    In the Kubernetes dashboard, click WorkloadsDeployments to verify the installation.

    +
  4. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/making-open-source-more-inclusive/index.html b/documentation/doc-installing-and-using-tackle/modules/making-open-source-more-inclusive/index.html new file mode 100644 index 00000000..e17c0771 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/making-open-source-more-inclusive/index.html @@ -0,0 +1,52 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Making open source more inclusive

+
+

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/managing-application-dependencies/index.html b/documentation/doc-installing-and-using-tackle/modules/managing-application-dependencies/index.html new file mode 100644 index 00000000..1d7f2422 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/managing-application-dependencies/index.html @@ -0,0 +1,72 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application dependencies

+
+

You can add, delete, and view application dependencies in the Manage dependencies window on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application and select Manage dependencies.

    +
  4. +
  5. +

    To add dependencies, select applications in the northbound or southbound dependencies fields.

    +
  6. +
  7. +

    To remove dependencies, delete selected applications in the northbound or southbound dependencies fields.

    +
  8. +
  9. +

    Click Close to save and close.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/managing-imports/index.html b/documentation/doc-installing-and-using-tackle/modules/managing-imports/index.html new file mode 100644 index 00000000..5947155c --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/managing-imports/index.html @@ -0,0 +1,82 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application imports

+
+

You can manage application imports on the Application import page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Manage imports.

    +
    +

    The Application import page displays a list of application imports.

    +
    +
  4. +
  5. +

    Click the Options menu kebab beside an application import and select one of the following options:

    +
    +
      +
    • +

      Delete deletes the application import.

      +
    • +
    • +

      View error report displays a table of application import errors.

      +
    • +
    • +

      Export errors enables you to save the application import errors as a CSV file.

      +
    • +
    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/reviewing-assessment/index.html b/documentation/doc-installing-and-using-tackle/modules/reviewing-assessment/index.html new file mode 100644 index 00000000..f3ce4355 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/reviewing-assessment/index.html @@ -0,0 +1,95 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Reviewing an assessment

+
+

You review an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status and a Not started review status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and a Not started review status and click the Review button in the toolbar.

    +
  4. +
  5. +

    Review the assessment in the Assessment summary section on the Review page.

    +
    +

    The Assessment summary table contains a Risk column that indicates the severity of the risk associated with each response.

    +
    +
  6. +
  7. +

    Select a Proposed action and an Effort estimate.

    +
  8. +
  9. +

    Set values for Business criticality and Work priority.

    +
  10. +
  11. +

    Optional: Enter comments in the Comments field.

    +
  12. +
  13. +

    Click Submit review.

    +
    +

    The Review status of each application is Completed.

    +
    +
  14. +
  15. +

    Expand the application to view the review results.

    +
  16. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/starting-assessment/index.html b/documentation/doc-installing-and-using-tackle/modules/starting-assessment/index.html new file mode 100644 index 00000000..4eb05c12 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/starting-assessment/index.html @@ -0,0 +1,89 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Starting an assessment

+
+

You start an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application that does not have a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Select individual stakeholders or stakeholder groups and then click Next.

    +
  6. +
  7. +

    Select responses to questions on each page of the Application assessment wizard and then click Next.

    +
    + + + + + +
    +
    Note
    +
    +
    +

    All questions are mandatory.

    +
    +
    +
    +
  8. +
  9. +

    When you have completed all the responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
    +

    The Assessment status of each assessed application is Completed.

    +
    +
  10. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/updating-business-service-of-application/index.html b/documentation/doc-installing-and-using-tackle/modules/updating-business-service-of-application/index.html new file mode 100644 index 00000000..7354b065 --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/updating-business-service-of-application/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the business service assigned to an application

+
+

You can update the business service assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The business service must exist on the Controls page.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Select a business service and click Save.

    +
    +

    The updated business service is displayed in the Business service column of the application.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/updating-tags-of-application/index.html b/documentation/doc-installing-and-using-tackle/modules/updating-tags-of-application/index.html new file mode 100644 index 00000000..e97a6c0b --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/updating-tags-of-application/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the tags assigned to an application

+
+

You can add or remove tags assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Add or delete tags and click Save.

    +
  6. +
  7. +

    Expand the application to view the updated tags.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/doc-installing-and-using-tackle/modules/upgrading/index.html b/documentation/doc-installing-and-using-tackle/modules/upgrading/index.html new file mode 100644 index 00000000..c506968d --- /dev/null +++ b/documentation/doc-installing-and-using-tackle/modules/upgrading/index.html @@ -0,0 +1,208 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Upgrading the Tackle application

+
+
+
+

You manually upgrade instances of the Tackle application.

+
+
+
+
+

Upgrading from version 1.1.0 to 1.2.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.1.0 to 1.2.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-keycloak keycloak-theme=quay.io/konveyor/tackle-keycloak-init:1.2.0
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.2.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.2.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.2.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.2.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+
+

Upgrading from version 1.0.0 to 1.1.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.0.0 to 1.1.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl -n <namespace> exec deployments/<tackle_instance>-keycloak \
    +  -c <tackle_instance>-keycloak -- bash -c '/opt/jboss/keycloak/bin/kcadm.sh \
    +  update realms/tackle -s internationalizationEnabled=true -s supportedLocales+=en \
    +  -s supportedLocales+=es -s defaultLocale=en --server http://localhost:8080/auth \
    +  --realm master --user $KEYCLOAK_USER --password $KEYCLOAK_PASSWORD'
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.1.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.1.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.1.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.1.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+ + +
+ + diff --git a/documentation/docinfo.html b/documentation/docinfo.html new file mode 100644 index 00000000..3d771454 --- /dev/null +++ b/documentation/docinfo.html @@ -0,0 +1,25 @@ + + + + + + + + + diff --git a/documentation/modules/about-pathfinder/index.html b/documentation/modules/about-pathfinder/index.html new file mode 100644 index 00000000..d5870165 --- /dev/null +++ b/documentation/modules/about-pathfinder/index.html @@ -0,0 +1,55 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About Tackle

+
+

Tackle is a cloud-native application that assesses your applications to determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring. Tackle also helps you to plan the migration of your applications to an enterprise Kubernetes platform.

+
+
+

Tackle uses an interactive questionnaire for the assessment. The assessment process enables key stakeholders to gather information about applications, to discuss risks flagged by Tackle, and to reach a consensus in formulating recommendations for each application.

+
+ + +
+ + diff --git a/documentation/modules/about-reports/index.html b/documentation/modules/about-reports/index.html new file mode 100644 index 00000000..acc98e85 --- /dev/null +++ b/documentation/modules/about-reports/index.html @@ -0,0 +1,94 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About reports

+
+

You can view a report of the assessments and reviews on the Reports page of the Tackle web console.

+
+
+

The Reports page contains the following sections:

+
+
+
+
Current landscape
+
+

This section displays all applications according to their risk levels.

+
+
Adoption candidate distribution
+
+

This section lists the assessed applications with the following columns:

+
+
    +
  • +

    Criticality is based on the Business criticality value of the review.

    +
  • +
  • +

    Priority is based on the Work priority value of the review.

    +
  • +
  • +

    Effort is based on the Effort estimate value of the review.

    +
  • +
  • +

    Decision is based on the Proposed action value of the review.

    +
    +

    By default, all applications are selected. You can clear some of the application check boxes to filter the report.

    +
    +
  • +
+
+
+
Suggested adoption plan
+
+

This section displays a suggested adoption plan based on effort, priority, and dependencies.

+
+
Identified risks
+
+

This section lists the severe risks identified in the assessments for all applications.

+
+
+
+ + +
+ + diff --git a/documentation/modules/accessing-console/index.html b/documentation/modules/accessing-console/index.html new file mode 100644 index 00000000..d8b18cdf --- /dev/null +++ b/documentation/modules/accessing-console/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Logging in to the Tackle web console

+
+

You can log in to the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    You must have the Tackle application installed.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Kubernetes dashboard, click ServicesIngresses.

    +
  2. +
  3. +

    Click the Endpoint of the tackle-sample ingress to launch the Tackle web console in a new browser window.

    +
  4. +
  5. +

    Enter tackle in the Username or email field, password in the Password field, and click Log in.

    +
  6. +
+
+
+ + + + + +
+
Important
+
+
+

You must change the default password of the tackle user.

+
+
+
+ + +
+ + diff --git a/documentation/modules/accessing-keycloak-admin-console/index.html b/documentation/modules/accessing-keycloak-admin-console/index.html new file mode 100644 index 00000000..506be79d --- /dev/null +++ b/documentation/modules/accessing-keycloak-admin-console/index.html @@ -0,0 +1,86 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Accessing the Keycloak admin console

+
+

When you install Tackle, a Keycloak admin user is created. You must obtain the admin user name and password to log in to the Keycloak admin console. The credentials are stored in the tackle-keycloak secret.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Run the following command to obtain the admin credentials:

    +
    +
    +
    $ kubectl get secret tackle-keycloak -o go-template='{{range $k,$v := .data}}{{printf "%s: " $k}}{{if not $v}}{{$v}}{{else}}{{$v | base64decode}}{{end}}{{"\n"}}{{end}}'
    +
    +
    +
    +
    Example output
    +
    +
    ADMIN_PASSWORD: <password>
    +ADMIN_USERNAME: admin
    +
    +
    +
  2. +
  3. +

    Launch a browser and navigate to https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  4. +
  5. +

    Log in to the Keycloak admin console with the admin user name and password.

    +
  6. +
+
+ + +
+ + diff --git a/documentation/modules/adding-users/index.html b/documentation/modules/adding-users/index.html new file mode 100644 index 00000000..69f88d1e --- /dev/null +++ b/documentation/modules/adding-users/index.html @@ -0,0 +1,80 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Adding users

+
+

You can add users by using the Keycloak admin console.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Create a new user in the Tackle realm. See Creating a new user in the Keycloak documentation.

    +
  4. +
  5. +

    Create a password for the new user. See Creating a password for the user.

    +
  6. +
  7. +

    Optional: Set attributes and permissions for the new user. See User profile.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/changing-default-password/index.html b/documentation/modules/changing-default-password/index.html new file mode 100644 index 00000000..366cf448 --- /dev/null +++ b/documentation/modules/changing-default-password/index.html @@ -0,0 +1,83 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Changing the default password

+
+

You must change the default password of the tackle user.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Locate the tackle user in the Tackle realm. See Searching for users in the Keycloak documentation.

    +
  4. +
  5. +

    Update the tackle user’s password. See User Credentials.

    +
  6. +
  7. +

    Log out of the Keycloak admin console.

    +
  8. +
  9. +

    Log in to the Tackle web console as the tackle user to verify the new password.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/modules/common-attributes/index.html b/documentation/modules/common-attributes/index.html new file mode 100644 index 00000000..a2b4e40a --- /dev/null +++ b/documentation/modules/common-attributes/index.html @@ -0,0 +1,49 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+ + + +
+ + diff --git a/documentation/modules/console-services/index.html b/documentation/modules/console-services/index.html new file mode 100644 index 00000000..9fb04a3d --- /dev/null +++ b/documentation/modules/console-services/index.html @@ -0,0 +1,197 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Tackle web console services

+
+
+
+

Tackle web console provides the following services:

+
+
+
    +
  • +

    Application inventory

    +
  • +
  • +

    Assessments

    +
  • +
  • +

    Reviews

    +
  • +
  • +

    Reports

    +
  • +
  • +

    Controls

    +
  • +
+
+
+
+
+

Application inventory

+
+
+

The Application inventory page enables you to perform the following tasks:

+
+
+
    +
  • +

    Manage your application portfolio.

    +
  • +
  • +

    Define and manage application dependencies.

    +
  • +
  • +

    Link applications to the business services that they support.

    +
  • +
  • +

    Describe and categorize applications by using tags.

    +
  • +
+
+
+
+
+

Assessments

+
+
+

You can assess your applications on the Application inventory page.

+
+
+

The assessment helps you determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring.

+
+
+

The assessment is an interactive questionnaire that gathers information and identifies possible risks and their severity.

+
+
+
+
+

Reviews

+
+
+

You can review a completed assessment on the Application inventory page.

+
+
+

The following information is collected from each reviewer:

+
+
+
    +
  • +

    Proposed action: Proposed action for the application, for example, replatforming or rehosting.

    +
  • +
  • +

    Effort estimate: How much effort is involved in migrating the application, based on the proposed action and the identified risks.

    +
  • +
  • +

    Business criticality: How critical the application is to your business on a scale of 1 to 10.

    +
  • +
  • +

    Work priority: Your work priority estimate for the proposed action on a scale of 1 to 10.

    +
  • +
+
+
+

The Reports page displays the results of the reviews.

+
+
+
+
+

Reports

+
+
+

The Reports page displays the results of the application assessments and reviews and can help you to plan your migration.

+
+
+

The reports provide information about the following:

+
+
+
    +
  • +

    Suitability of applications for containerization.

    +
  • +
  • +

    Possible risks and severity.

    +
  • +
  • +

    Adoption plan based on estimated effort, work priority, and application dependencies.

    +
  • +
+
+
+
+
+

Controls

+
+
+

The Controls page enables you to manage the following entities:

+
+
+
    +
  • +

    Stakeholder: A stakeholder is an individual with an interest in an application or a subject matter expert.

    +
  • +
  • +

    Stakeholder group: A stakeholder group is a group of related stakeholders. A stakeholder can belong to one or more stakeholder groups. Stakeholder groups are used to assign multiple stakeholders to review an assessment.

    +
  • +
  • +

    Job function: A job function is an attribute of a stakeholder. You use a predefined job function or create a new job function.

    +
  • +
  • +

    Business service: A business service is an attribute of an application, for example, credit card service, transportation, or IT support. You can use a predefined business service or create a new business service.

    +
  • +
  • +

    Tag: A tag is an attribute of an application. Tags are an extensible and flexible way to add metadata to applications. Tags are grouped under a parent tag type. You can use a predefined tag or create a new tag.

    +
  • +
  • +

    Tag type: A tag type defines the rank and background color of a group of related tags.

    +
  • +
+
+
+
+ + +
+ + diff --git a/documentation/modules/copying-assessments-and-reviews/index.html b/documentation/modules/copying-assessments-and-reviews/index.html new file mode 100644 index 00000000..1c54b658 --- /dev/null +++ b/documentation/modules/copying-assessments-and-reviews/index.html @@ -0,0 +1,92 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Copying and applying assessments and reviews

+
+

You copy an assessment or assessment and review from a single application and apply them to multiple applications on the Application inventory page of the Tackle web console.

+
+
+

You can apply assessments and reviews to groups of related applications, for example, applications written in Java or belonging to the same business service.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status or Completed assessment and review statuses, depending on whether you are copying an assessment or an assessment and review.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status or Completed assessment and review statuses.

    +
  4. +
  5. +

    Select Copy assessment or Copy assessment and review.

    +
  6. +
  7. +

    Optional: In the dialog box, click Name to select a filter, for example, Tag, and select a tag, for example, Java, to display a filtered list of applications.

    +
  8. +
  9. +

    Select the applications to which you want to apply the copied assessment or assessment and review.

    +
  10. +
  11. +

    If a selected application has an existing assessment or review, select the Yes, continue check box to confirm that existing assessments and reviews will be overwritten.

    +
  12. +
  13. +

    Click Copy.

    +
    +

    The selected applications display a Completed assessment status or Completed assessment and review statuses.

    +
    +
  14. +
+
+ + +
+ + diff --git a/documentation/modules/creating-application/index.html b/documentation/modules/creating-application/index.html new file mode 100644 index 00000000..d7f4b922 --- /dev/null +++ b/documentation/modules/creating-application/index.html @@ -0,0 +1,91 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating an application

+
+

You can create an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory and then click Create new.

    +
  2. +
  3. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the application.

      +
    • +
    • +

      Description: Optional. Description of the application.

      +
    • +
    • +

      Business service: Optional. You can select a business service that describes the application.

      +
    • +
    • +

      Tags: Optional. You can select one or more tags.

      +
    • +
    • +

      Comments: Optional. Comments about the application.

      +
    • +
    +
    +
  4. +
  5. +

    Click Create.

    +
    +

    The new application is displayed on the Application inventory page.

    +
    +
  6. +
  7. +

    Expand the application to view its tags and comments.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/creating-business-service/index.html b/documentation/modules/creating-business-service/index.html new file mode 100644 index 00000000..6f2f60a5 --- /dev/null +++ b/documentation/modules/creating-business-service/index.html @@ -0,0 +1,85 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a business service

+
+

A business service is an attribute of an application. You can create a business service on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Business services tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the business service.

      +
    • +
    • +

      Description: Optional: Description of the business service.

      +
    • +
    • +

      Owner: Optional: Select a stakeholder.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new business service is displayed on the Business services tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/creating-job-function/index.html b/documentation/modules/creating-job-function/index.html new file mode 100644 index 00000000..74002703 --- /dev/null +++ b/documentation/modules/creating-job-function/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a job function

+
+

A job function is an attribute of a stakeholder. You can use a predefined job function or create a new job function on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Job functions tab and then click Create new.

    +
  4. +
  5. +

    Enter the Name of the job function and click Create.

    +
    +

    The new job function is displayed on the Job functions tab.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/modules/creating-stakeholder-group/index.html b/documentation/modules/creating-stakeholder-group/index.html new file mode 100644 index 00000000..a372c423 --- /dev/null +++ b/documentation/modules/creating-stakeholder-group/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder group

+
+

You can create stakeholder groups on the Controls page of the Tackle web console. Stakeholder groups enable you to assign multiple stakeholders to review an assessment.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholder groups tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the stakeholder group.

      +
    • +
    • +

      Description: Optional. Description of the stakeholder group.

      +
    • +
    • +

      Member(s): Optional. You can select one or more stakeholders to add to the group.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder group is displayed on the Stakeholder groups tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder group to view the group members.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/modules/creating-stakeholder/index.html b/documentation/modules/creating-stakeholder/index.html new file mode 100644 index 00000000..5f7e8ff1 --- /dev/null +++ b/documentation/modules/creating-stakeholder/index.html @@ -0,0 +1,99 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder

+
+

You can create a stakeholder on the Controls page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The stakeholder must have a valid email address.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholders tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Email: Email address of the stakeholder.

      +
    • +
    • +

      Display name: Name of the stakeholder.

      +
    • +
    • +

      Job function: Optional. You can select a predefined job function or type a job function to create it.

      +
    • +
    • +

      Groups: Optional. You can select one or more stakeholder groups from a list of stakeholder groups that you have created.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder is displayed on the Stakeholders tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder to view the stakeholder groups to which the stakeholder belongs.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/modules/creating-tag-type/index.html b/documentation/modules/creating-tag-type/index.html new file mode 100644 index 00000000..13f9c117 --- /dev/null +++ b/documentation/modules/creating-tag-type/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag type

+
+

You can create a tag type on the Controls page of the Tackle web console.

+
+
+

A tag type is the parent of a group of related tags. The tag type defines the rank and background color of the tags on the Application inventory page.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag type.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag type.

      +
    • +
    • +

      Rank: The rank determines the order in which the tags are displayed.

      +
    • +
    • +

      Color: The color is displayed as the background color for all tags associated with this tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag type is displayed on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/creating-tag/index.html b/documentation/modules/creating-tag/index.html new file mode 100644 index 00000000..3c20ac5e --- /dev/null +++ b/documentation/modules/creating-tag/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag

+
+

You can create a tag on the Controls page of the Tackle web console.

+
+
+

Tags are an extensible and flexible way to add metadata to applications. Tags are added to applications on the Application inventory page.

+
+
+

Tags belong to a parent tag type that determines the display order and color of the tags. You can use a predefined tag type or create a new tag type.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag.

      +
    • +
    • +

      Tag type: Select a tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag is displayed under its tag type on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/deleting-assessment/index.html b/documentation/modules/deleting-assessment/index.html new file mode 100644 index 00000000..812a6e03 --- /dev/null +++ b/documentation/modules/deleting-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Deleting an assessment

+
+

You delete an application assessment on the Application inventory page of the Tackle web console. Deleting an assessment deletes its review.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status and select Discard assessment.

    +
  4. +
  5. +

    Click Continue to confirm the deletion.

    +
    +

    The Assessment and Review status of the application are Not started.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/modules/editing-assessment/index.html b/documentation/modules/editing-assessment/index.html new file mode 100644 index 00000000..974a6d00 --- /dev/null +++ b/documentation/modules/editing-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Editing an assessment

+
+

You can make an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Click Continue to confirm that you want to edit the assessment.

    +
  6. +
  7. +

    After you have updated your responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/images/kebab.png b/documentation/modules/images/kebab.png new file mode 100644 index 00000000..81893bd4 Binary files /dev/null and b/documentation/modules/images/kebab.png differ diff --git a/documentation/modules/images/konveyor-logo-tackle.svg b/documentation/modules/images/konveyor-logo-tackle.svg new file mode 100644 index 00000000..4f21a7b4 --- /dev/null +++ b/documentation/modules/images/konveyor-logo-tackle.svg @@ -0,0 +1,189 @@ + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/documentation/modules/importing-applications/index.html b/documentation/modules/importing-applications/index.html new file mode 100644 index 00000000..85c09219 --- /dev/null +++ b/documentation/modules/importing-applications/index.html @@ -0,0 +1,324 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Importing applications

+
+

You can import one or more applications into the Application inventory page of the Tackle web console by using a CSV file.

+
+
+ + + + + +
+
Note
+
+
+

You cannot create tags or business services by importing a CSV file. Specified tags or business services must exist in the web console before you import the applications.

+
+
+
+
+

The CSV file contains the following fields:

+
+
+

Record Type 1:

+
+
+
    +
  • +

    Describes an application or application dependencies.

    +
  • +
  • +

    Required for all records.

    +
  • +
+
+
+

The following values are allowed for Record Type 1:

+
+
+
    +
  • +

    1: Application: This option has the following fields:

    +
    +
      +
    • +

      Application Name: Required.

      +
    • +
    • +

      Description: Optional.

      +
    • +
    • +

      Comments: Optional.

      +
    • +
    • +

      Business Service: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag Type <1..20>: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag <1..20>: Optional. Must exist in the web console.

      +
      +

      You can import up to 20 Tag Type <x> and Tag <x> fields.

      +
      +
    • +
    +
    +
  • +
  • +

    2: Application dependencies: This option requires the following fields:

    +
    +
      +
    • +

      Application Name

      +
    • +
    • +

      Dependency: Must be the same as the Application Name of the dependency.

      +
    • +
    • +

      Dependency Direction: Allowed values are northbound and southbound.

      +
      +

      All other fields are empty.

      +
      +
    • +
    +
    +
  • +
+
+ + +++++++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1. CSV example
Record Type 1Application NameDependencyDependency DirectionDescriptionCommentsBusiness ServiceTag Type 1Tag 1Tag Type 2Tag 2Tag Type 3Tag 3

1

Imported-Purchasing

Vendor management

Required for purchase order processing and accounts payable

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

2

Imported-Purchasing

Tiller

northbound

1

Imported-PO

Requisitions, purchase orders, goods received

Requisition to receipt

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-Payroll

Payroll

To be retired at the end of the financial year

Finance and HR

Language

Java

Database

Oracle

Language

Java

2

Imported-Payroll

Imported-GL

northbound

2

Imported-Payroll

Imported-HR

southbound

1

Imported-GL

General Ledger

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-HR

Human Resources

Go live scheduled for Q3

Finance and HR

Operating System

RHEL 8

Database

PostgreSQL

Language

Python

+
+
Prerequisites
+
    +
  • +

    Valid CSV file.

    +
  • +
  • +

    Specified business services, tag types, and tags created in the web console.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Import.

    +
  4. +
  5. +

    Browse to the CSV file and click Open.

    +
  6. +
  7. +

    Click Import.

    +
    +

    The imported applications are displayed on the Application inventory page .

    +
    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/installing-operator/index.html b/documentation/modules/installing-operator/index.html new file mode 100644 index 00000000..c734f592 --- /dev/null +++ b/documentation/modules/installing-operator/index.html @@ -0,0 +1,84 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle Operator

+
+

You download and install the Tackle Operator on an Enterprise Kubernetes Platform cluster.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Install the Tackle Operator:

    +
    +
    +
    $ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml
    +
    +
    +
    +

    The Tackle Operator is installed in the {namespace} namespace by default.

    +
    +
  2. +
  3. +

    Verify the Tackle Operator installation by viewing its resources:

    +
    +
    +
    $ kubectl get all -n my-tackle-operator
    +
    +
    +
  4. +
+
+ + +
+ + diff --git a/documentation/modules/installing-tackle-application/index.html b/documentation/modules/installing-tackle-application/index.html new file mode 100644 index 00000000..db97c5b5 --- /dev/null +++ b/documentation/modules/installing-tackle-application/index.html @@ -0,0 +1,93 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle application

+
+

You install Tackle in a namespace by creating an instance of the Tackle application.

+
+
+
Prerequisites
+
    +
  • +

    The Tackle Operator must be installed on the cluster.

    +
  • +
  • +

    You must have project-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Create an instance of the Tackle application, specifying its namespace:

    +
    +
    +
    $ kubectl apply -n <namespace> -f https://raw.githubusercontent.com/konveyor/tackle-operator/main/src/main/resources/k8s/tackle/tackle.yaml
    +
    +
    +
    + + + + + +
    +
    Note
    +
    +
    +

    You can create multiple instances of the Tackle application in the same namespace by specifying a unique name for each instance in the tackle.yaml file.

    +
    +
    +
    +
  2. +
  3. +

    In the Kubernetes dashboard, click WorkloadsDeployments to verify the installation.

    +
  4. +
+
+ + +
+ + diff --git a/documentation/modules/making-open-source-more-inclusive/index.html b/documentation/modules/making-open-source-more-inclusive/index.html new file mode 100644 index 00000000..93958a8b --- /dev/null +++ b/documentation/modules/making-open-source-more-inclusive/index.html @@ -0,0 +1,52 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Making open source more inclusive

+
+

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

+
+ + +
+ + diff --git a/documentation/modules/managing-application-dependencies/index.html b/documentation/modules/managing-application-dependencies/index.html new file mode 100644 index 00000000..50eb7779 --- /dev/null +++ b/documentation/modules/managing-application-dependencies/index.html @@ -0,0 +1,72 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application dependencies

+
+

You can add, delete, and view application dependencies in the Manage dependencies window on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application and select Manage dependencies.

    +
  4. +
  5. +

    To add dependencies, select applications in the northbound or southbound dependencies fields.

    +
  6. +
  7. +

    To remove dependencies, delete selected applications in the northbound or southbound dependencies fields.

    +
  8. +
  9. +

    Click Close to save and close.

    +
  10. +
+
+ + +
+ + diff --git a/documentation/modules/managing-imports/index.html b/documentation/modules/managing-imports/index.html new file mode 100644 index 00000000..4c6221fa --- /dev/null +++ b/documentation/modules/managing-imports/index.html @@ -0,0 +1,82 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application imports

+
+

You can manage application imports on the Application import page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Manage imports.

    +
    +

    The Application import page displays a list of application imports.

    +
    +
  4. +
  5. +

    Click the Options menu kebab beside an application import and select one of the following options:

    +
    +
      +
    • +

      Delete deletes the application import.

      +
    • +
    • +

      View error report displays a table of application import errors.

      +
    • +
    • +

      Export errors enables you to save the application import errors as a CSV file.

      +
    • +
    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/modules/reviewing-assessment/index.html b/documentation/modules/reviewing-assessment/index.html new file mode 100644 index 00000000..8bec7927 --- /dev/null +++ b/documentation/modules/reviewing-assessment/index.html @@ -0,0 +1,95 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Reviewing an assessment

+
+

You review an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status and a Not started review status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and a Not started review status and click the Review button in the toolbar.

    +
  4. +
  5. +

    Review the assessment in the Assessment summary section on the Review page.

    +
    +

    The Assessment summary table contains a Risk column that indicates the severity of the risk associated with each response.

    +
    +
  6. +
  7. +

    Select a Proposed action and an Effort estimate.

    +
  8. +
  9. +

    Set values for Business criticality and Work priority.

    +
  10. +
  11. +

    Optional: Enter comments in the Comments field.

    +
  12. +
  13. +

    Click Submit review.

    +
    +

    The Review status of each application is Completed.

    +
    +
  14. +
  15. +

    Expand the application to view the review results.

    +
  16. +
+
+ + +
+ + diff --git a/documentation/modules/starting-assessment/index.html b/documentation/modules/starting-assessment/index.html new file mode 100644 index 00000000..494c4542 --- /dev/null +++ b/documentation/modules/starting-assessment/index.html @@ -0,0 +1,89 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Starting an assessment

+
+

You start an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application that does not have a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Select individual stakeholders or stakeholder groups and then click Next.

    +
  6. +
  7. +

    Select responses to questions on each page of the Application assessment wizard and then click Next.

    +
    + + + + + +
    +
    Note
    +
    +
    +

    All questions are mandatory.

    +
    +
    +
    +
  8. +
  9. +

    When you have completed all the responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
    +

    The Assessment status of each assessed application is Completed.

    +
    +
  10. +
+
+ + +
+ + diff --git a/documentation/modules/updating-business-service-of-application/index.html b/documentation/modules/updating-business-service-of-application/index.html new file mode 100644 index 00000000..f3771ac6 --- /dev/null +++ b/documentation/modules/updating-business-service-of-application/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the business service assigned to an application

+
+

You can update the business service assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The business service must exist on the Controls page.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Select a business service and click Save.

    +
    +

    The updated business service is displayed in the Business service column of the application.

    +
    +
  6. +
+
+ + +
+ + diff --git a/documentation/modules/updating-tags-of-application/index.html b/documentation/modules/updating-tags-of-application/index.html new file mode 100644 index 00000000..c6a4b733 --- /dev/null +++ b/documentation/modules/updating-tags-of-application/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the tags assigned to an application

+
+

You can add or remove tags assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Add or delete tags and click Save.

    +
  6. +
  7. +

    Expand the application to view the updated tags.

    +
  8. +
+
+ + +
+ + diff --git a/documentation/modules/upgrading/index.html b/documentation/modules/upgrading/index.html new file mode 100644 index 00000000..01475986 --- /dev/null +++ b/documentation/modules/upgrading/index.html @@ -0,0 +1,208 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Upgrading the Tackle application

+
+
+
+

You manually upgrade instances of the Tackle application.

+
+
+
+
+

Upgrading from version 1.1.0 to 1.2.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.1.0 to 1.2.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-keycloak keycloak-theme=quay.io/konveyor/tackle-keycloak-init:1.2.0
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.2.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.2.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.2.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.2.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+
+

Upgrading from version 1.0.0 to 1.1.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.0.0 to 1.1.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl -n <namespace> exec deployments/<tackle_instance>-keycloak \
    +  -c <tackle_instance>-keycloak -- bash -c '/opt/jboss/keycloak/bin/kcadm.sh \
    +  update realms/tackle -s internationalizationEnabled=true -s supportedLocales+=en \
    +  -s supportedLocales+=es -s defaultLocale=en --server http://localhost:8080/auth \
    +  --realm master --user $KEYCLOAK_USER --password $KEYCLOAK_PASSWORD'
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.1.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.1.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.1.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.1.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+ + +
+ + diff --git a/feed.xml b/feed.xml new file mode 100644 index 00000000..ab0ab44d --- /dev/null +++ b/feed.xml @@ -0,0 +1 @@ +Jekyll2025-01-25T18:02:59-06:00/feed.xmlTackle DocumentationTackle documentation \ No newline at end of file diff --git a/index.html b/index.html new file mode 100644 index 00000000..af778c72 --- /dev/null +++ b/index.html @@ -0,0 +1,80 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Tackle Documentation

+
+
+
+
+
+

Warning Tackle 2.0 has been released and all Tackle documentation has been moved to the new official Konveyor documentation website (https://konveyor.github.io/tackle2/) and GitHub Repo (https://konveyor.github.io/tackle2/).

+
+
+
+
+
+
+

What is Tackle?

+
+
+

Tackle is a tool in the Konveyor community for refactoring your applications for Kubernetes.

+
+
+
+
+

Documentation

+
+
+ +
+
+
+ + +
+ + diff --git a/jekyll-theme-cayman.gemspec b/jekyll-theme-cayman.gemspec new file mode 100644 index 00000000..4a1c2d28 --- /dev/null +++ b/jekyll-theme-cayman.gemspec @@ -0,0 +1,22 @@ +# frozen_string_literal: true + +Gem::Specification.new do |s| + s.name = 'jekyll-theme-cayman' + s.version = '0.1.1' + s.license = 'CC0-1.0' + s.authors = ['Jason Long', 'GitHub, Inc.'] + s.email = ['opensource+jekyll-theme-cayman@github.com'] + s.homepage = 'https://github.com/pages-themes/cayman' + s.summary = 'Cayman is a Jekyll theme for GitHub Pages' + + s.files = `git ls-files -z`.split("\x0").select do |f| + f.match(%r{^((_includes|_layouts|_sass|assets)/|(LICENSE|README)((\.(txt|md|markdown)|$)))}i) + end + + s.platform = Gem::Platform::RUBY + s.add_runtime_dependency 'jekyll', '> 3.5', '< 5.0' + s.add_runtime_dependency 'jekyll-seo-tag', '~> 2.0' + s.add_development_dependency 'html-proofer', '~> 3.0' + s.add_development_dependency 'rubocop', '~> 0.50' + s.add_development_dependency 'w3c_validators', '~> 1.3' +end diff --git a/modules/about-pathfinder/index.html b/modules/about-pathfinder/index.html new file mode 100644 index 00000000..7faf9097 --- /dev/null +++ b/modules/about-pathfinder/index.html @@ -0,0 +1,55 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About Tackle

+
+

Tackle is a cloud-native application that assesses your applications to determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring. Tackle also helps you to plan the migration of your applications to an enterprise Kubernetes platform.

+
+
+

Tackle uses an interactive questionnaire for the assessment. The assessment process enables key stakeholders to gather information about applications, to discuss risks flagged by Tackle, and to reach a consensus in formulating recommendations for each application.

+
+ + +
+ + diff --git a/modules/about-reports/index.html b/modules/about-reports/index.html new file mode 100644 index 00000000..51ee6cae --- /dev/null +++ b/modules/about-reports/index.html @@ -0,0 +1,94 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

About reports

+
+

You can view a report of the assessments and reviews on the Reports page of the Tackle web console.

+
+
+

The Reports page contains the following sections:

+
+
+
+
Current landscape
+
+

This section displays all applications according to their risk levels.

+
+
Adoption candidate distribution
+
+

This section lists the assessed applications with the following columns:

+
+
    +
  • +

    Criticality is based on the Business criticality value of the review.

    +
  • +
  • +

    Priority is based on the Work priority value of the review.

    +
  • +
  • +

    Effort is based on the Effort estimate value of the review.

    +
  • +
  • +

    Decision is based on the Proposed action value of the review.

    +
    +

    By default, all applications are selected. You can clear some of the application check boxes to filter the report.

    +
    +
  • +
+
+
+
Suggested adoption plan
+
+

This section displays a suggested adoption plan based on effort, priority, and dependencies.

+
+
Identified risks
+
+

This section lists the severe risks identified in the assessments for all applications.

+
+
+
+ + +
+ + diff --git a/modules/accessing-console/index.html b/modules/accessing-console/index.html new file mode 100644 index 00000000..0df91adf --- /dev/null +++ b/modules/accessing-console/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Logging in to the Tackle web console

+
+

You can log in to the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    You must have the Tackle application installed.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Kubernetes dashboard, click ServicesIngresses.

    +
  2. +
  3. +

    Click the Endpoint of the tackle-sample ingress to launch the Tackle web console in a new browser window.

    +
  4. +
  5. +

    Enter tackle in the Username or email field, password in the Password field, and click Log in.

    +
  6. +
+
+
+ + + + + +
+
Important
+
+
+

You must change the default password of the tackle user.

+
+
+
+ + +
+ + diff --git a/modules/accessing-keycloak-admin-console/index.html b/modules/accessing-keycloak-admin-console/index.html new file mode 100644 index 00000000..ada58fb9 --- /dev/null +++ b/modules/accessing-keycloak-admin-console/index.html @@ -0,0 +1,86 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Accessing the Keycloak admin console

+
+

When you install Tackle, a Keycloak admin user is created. You must obtain the admin user name and password to log in to the Keycloak admin console. The credentials are stored in the tackle-keycloak secret.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Run the following command to obtain the admin credentials:

    +
    +
    +
    $ kubectl get secret tackle-keycloak -o go-template='{{range $k,$v := .data}}{{printf "%s: " $k}}{{if not $v}}{{$v}}{{else}}{{$v | base64decode}}{{end}}{{"\n"}}{{end}}'
    +
    +
    +
    +
    Example output
    +
    +
    ADMIN_PASSWORD: <password>
    +ADMIN_USERNAME: admin
    +
    +
    +
  2. +
  3. +

    Launch a browser and navigate to https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  4. +
  5. +

    Log in to the Keycloak admin console with the admin user name and password.

    +
  6. +
+
+ + +
+ + diff --git a/modules/adding-users/index.html b/modules/adding-users/index.html new file mode 100644 index 00000000..da00e2cc --- /dev/null +++ b/modules/adding-users/index.html @@ -0,0 +1,80 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Adding users

+
+

You can add users by using the Keycloak admin console.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Create a new user in the Tackle realm. See Creating a new user in the Keycloak documentation.

    +
  4. +
  5. +

    Create a password for the new user. See Creating a password for the user.

    +
  6. +
  7. +

    Optional: Set attributes and permissions for the new user. See User profile.

    +
  8. +
+
+ + +
+ + diff --git a/modules/changing-default-password/index.html b/modules/changing-default-password/index.html new file mode 100644 index 00000000..afb01fcc --- /dev/null +++ b/modules/changing-default-password/index.html @@ -0,0 +1,83 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Changing the default password

+
+

You must change the default password of the tackle user.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges

    +
  • +
  • +

    You must have the Keycloak admin user name and password.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Log in to the Keycloak admin console at https://<www.example.com>/auth, specifying the Tackle cluster URL.

    +
  2. +
  3. +

    Locate the tackle user in the Tackle realm. See Searching for users in the Keycloak documentation.

    +
  4. +
  5. +

    Update the tackle user’s password. See User Credentials.

    +
  6. +
  7. +

    Log out of the Keycloak admin console.

    +
  8. +
  9. +

    Log in to the Tackle web console as the tackle user to verify the new password.

    +
  10. +
+
+ + +
+ + diff --git a/modules/common-attributes/index.html b/modules/common-attributes/index.html new file mode 100644 index 00000000..2e93303c --- /dev/null +++ b/modules/common-attributes/index.html @@ -0,0 +1,49 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+ + + +
+ + diff --git a/modules/console-services/index.html b/modules/console-services/index.html new file mode 100644 index 00000000..72fecc93 --- /dev/null +++ b/modules/console-services/index.html @@ -0,0 +1,197 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Tackle web console services

+
+
+
+

Tackle web console provides the following services:

+
+
+
    +
  • +

    Application inventory

    +
  • +
  • +

    Assessments

    +
  • +
  • +

    Reviews

    +
  • +
  • +

    Reports

    +
  • +
  • +

    Controls

    +
  • +
+
+
+
+
+

Application inventory

+
+
+

The Application inventory page enables you to perform the following tasks:

+
+
+
    +
  • +

    Manage your application portfolio.

    +
  • +
  • +

    Define and manage application dependencies.

    +
  • +
  • +

    Link applications to the business services that they support.

    +
  • +
  • +

    Describe and categorize applications by using tags.

    +
  • +
+
+
+
+
+

Assessments

+
+
+

You can assess your applications on the Application inventory page.

+
+
+

The assessment helps you determine an appropriate migration strategy for each application, for example, rehosting, replatforming, or refactoring.

+
+
+

The assessment is an interactive questionnaire that gathers information and identifies possible risks and their severity.

+
+
+
+
+

Reviews

+
+
+

You can review a completed assessment on the Application inventory page.

+
+
+

The following information is collected from each reviewer:

+
+
+
    +
  • +

    Proposed action: Proposed action for the application, for example, replatforming or rehosting.

    +
  • +
  • +

    Effort estimate: How much effort is involved in migrating the application, based on the proposed action and the identified risks.

    +
  • +
  • +

    Business criticality: How critical the application is to your business on a scale of 1 to 10.

    +
  • +
  • +

    Work priority: Your work priority estimate for the proposed action on a scale of 1 to 10.

    +
  • +
+
+
+

The Reports page displays the results of the reviews.

+
+
+
+
+

Reports

+
+
+

The Reports page displays the results of the application assessments and reviews and can help you to plan your migration.

+
+
+

The reports provide information about the following:

+
+
+
    +
  • +

    Suitability of applications for containerization.

    +
  • +
  • +

    Possible risks and severity.

    +
  • +
  • +

    Adoption plan based on estimated effort, work priority, and application dependencies.

    +
  • +
+
+
+
+
+

Controls

+
+
+

The Controls page enables you to manage the following entities:

+
+
+
    +
  • +

    Stakeholder: A stakeholder is an individual with an interest in an application or a subject matter expert.

    +
  • +
  • +

    Stakeholder group: A stakeholder group is a group of related stakeholders. A stakeholder can belong to one or more stakeholder groups. Stakeholder groups are used to assign multiple stakeholders to review an assessment.

    +
  • +
  • +

    Job function: A job function is an attribute of a stakeholder. You use a predefined job function or create a new job function.

    +
  • +
  • +

    Business service: A business service is an attribute of an application, for example, credit card service, transportation, or IT support. You can use a predefined business service or create a new business service.

    +
  • +
  • +

    Tag: A tag is an attribute of an application. Tags are an extensible and flexible way to add metadata to applications. Tags are grouped under a parent tag type. You can use a predefined tag or create a new tag.

    +
  • +
  • +

    Tag type: A tag type defines the rank and background color of a group of related tags.

    +
  • +
+
+
+
+ + +
+ + diff --git a/modules/copying-assessments-and-reviews/index.html b/modules/copying-assessments-and-reviews/index.html new file mode 100644 index 00000000..a6869367 --- /dev/null +++ b/modules/copying-assessments-and-reviews/index.html @@ -0,0 +1,92 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Copying and applying assessments and reviews

+
+

You copy an assessment or assessment and review from a single application and apply them to multiple applications on the Application inventory page of the Tackle web console.

+
+
+

You can apply assessments and reviews to groups of related applications, for example, applications written in Java or belonging to the same business service.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status or Completed assessment and review statuses, depending on whether you are copying an assessment or an assessment and review.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status or Completed assessment and review statuses.

    +
  4. +
  5. +

    Select Copy assessment or Copy assessment and review.

    +
  6. +
  7. +

    Optional: In the dialog box, click Name to select a filter, for example, Tag, and select a tag, for example, Java, to display a filtered list of applications.

    +
  8. +
  9. +

    Select the applications to which you want to apply the copied assessment or assessment and review.

    +
  10. +
  11. +

    If a selected application has an existing assessment or review, select the Yes, continue check box to confirm that existing assessments and reviews will be overwritten.

    +
  12. +
  13. +

    Click Copy.

    +
    +

    The selected applications display a Completed assessment status or Completed assessment and review statuses.

    +
    +
  14. +
+
+ + +
+ + diff --git a/modules/creating-application/index.html b/modules/creating-application/index.html new file mode 100644 index 00000000..906e59eb --- /dev/null +++ b/modules/creating-application/index.html @@ -0,0 +1,91 @@ + + + + + + +Installing and using Tackle | Tackle Documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating an application

+
+

You can create an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory and then click Create new.

    +
  2. +
  3. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the application.

      +
    • +
    • +

      Description: Optional. Description of the application.

      +
    • +
    • +

      Business service: Optional. You can select a business service that describes the application.

      +
    • +
    • +

      Tags: Optional. You can select one or more tags.

      +
    • +
    • +

      Comments: Optional. Comments about the application.

      +
    • +
    +
    +
  4. +
  5. +

    Click Create.

    +
    +

    The new application is displayed on the Application inventory page.

    +
    +
  6. +
  7. +

    Expand the application to view its tags and comments.

    +
  8. +
+
+ + +
+ + diff --git a/modules/creating-business-service/index.html b/modules/creating-business-service/index.html new file mode 100644 index 00000000..0acf6625 --- /dev/null +++ b/modules/creating-business-service/index.html @@ -0,0 +1,85 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a business service

+
+

A business service is an attribute of an application. You can create a business service on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Business services tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the business service.

      +
    • +
    • +

      Description: Optional: Description of the business service.

      +
    • +
    • +

      Owner: Optional: Select a stakeholder.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new business service is displayed on the Business services tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/modules/creating-job-function/index.html b/modules/creating-job-function/index.html new file mode 100644 index 00000000..4447d59a --- /dev/null +++ b/modules/creating-job-function/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a job function

+
+

A job function is an attribute of a stakeholder. You can use a predefined job function or create a new job function on the Controls page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Job functions tab and then click Create new.

    +
  4. +
  5. +

    Enter the Name of the job function and click Create.

    +
    +

    The new job function is displayed on the Job functions tab.

    +
    +
  6. +
+
+ + +
+ + diff --git a/modules/creating-stakeholder-group/index.html b/modules/creating-stakeholder-group/index.html new file mode 100644 index 00000000..fbf00e78 --- /dev/null +++ b/modules/creating-stakeholder-group/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder group

+
+

You can create stakeholder groups on the Controls page of the Tackle web console. Stakeholder groups enable you to assign multiple stakeholders to review an assessment.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholder groups tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the stakeholder group.

      +
    • +
    • +

      Description: Optional. Description of the stakeholder group.

      +
    • +
    • +

      Member(s): Optional. You can select one or more stakeholders to add to the group.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder group is displayed on the Stakeholder groups tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder group to view the group members.

    +
  10. +
+
+ + +
+ + diff --git a/modules/creating-stakeholder/index.html b/modules/creating-stakeholder/index.html new file mode 100644 index 00000000..31f0ec01 --- /dev/null +++ b/modules/creating-stakeholder/index.html @@ -0,0 +1,99 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a stakeholder

+
+

You can create a stakeholder on the Controls page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The stakeholder must have a valid email address.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Stakeholders tab and then click Create new.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Email: Email address of the stakeholder.

      +
    • +
    • +

      Display name: Name of the stakeholder.

      +
    • +
    • +

      Job function: Optional. You can select a predefined job function or type a job function to create it.

      +
    • +
    • +

      Groups: Optional. You can select one or more stakeholder groups from a list of stakeholder groups that you have created.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new stakeholder is displayed on the Stakeholders tab.

    +
    +
  8. +
  9. +

    Expand the stakeholder to view the stakeholder groups to which the stakeholder belongs.

    +
  10. +
+
+ + +
+ + diff --git a/modules/creating-tag-type/index.html b/modules/creating-tag-type/index.html new file mode 100644 index 00000000..beeaafac --- /dev/null +++ b/modules/creating-tag-type/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag type

+
+

You can create a tag type on the Controls page of the Tackle web console.

+
+
+

A tag type is the parent of a group of related tags. The tag type defines the rank and background color of the tags on the Application inventory page.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag type.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag type.

      +
    • +
    • +

      Rank: The rank determines the order in which the tags are displayed.

      +
    • +
    • +

      Color: The color is displayed as the background color for all tags associated with this tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag type is displayed on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/modules/creating-tag/index.html b/modules/creating-tag/index.html new file mode 100644 index 00000000..e291586a --- /dev/null +++ b/modules/creating-tag/index.html @@ -0,0 +1,88 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Creating a tag

+
+

You can create a tag on the Controls page of the Tackle web console.

+
+
+

Tags are an extensible and flexible way to add metadata to applications. Tags are added to applications on the Application inventory page.

+
+
+

Tags belong to a parent tag type that determines the display order and color of the tags. You can use a predefined tag type or create a new tag type.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Controls.

    +
  2. +
  3. +

    Click the Tags tab and then click Create tag.

    +
  4. +
  5. +

    Complete the following fields:

    +
    +
      +
    • +

      Name: Name of the tag.

      +
    • +
    • +

      Tag type: Select a tag type.

      +
    • +
    +
    +
  6. +
  7. +

    Click Create.

    +
    +

    The new tag is displayed under its tag type on the Tags tab.

    +
    +
  8. +
+
+ + +
+ + diff --git a/modules/deleting-assessment/index.html b/modules/deleting-assessment/index.html new file mode 100644 index 00000000..b21c183b --- /dev/null +++ b/modules/deleting-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Deleting an assessment

+
+

You delete an application assessment on the Application inventory page of the Tackle web console. Deleting an assessment deletes its review.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application with a Completed assessment status and select Discard assessment.

    +
  4. +
  5. +

    Click Continue to confirm the deletion.

    +
    +

    The Assessment and Review status of the application are Not started.

    +
    +
  6. +
+
+ + +
+ + diff --git a/modules/editing-assessment/index.html b/modules/editing-assessment/index.html new file mode 100644 index 00000000..db14980d --- /dev/null +++ b/modules/editing-assessment/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Editing an assessment

+
+

You can make an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Click Continue to confirm that you want to edit the assessment.

    +
  6. +
  7. +

    After you have updated your responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
  8. +
+
+ + +
+ + diff --git a/modules/images/kebab.png b/modules/images/kebab.png new file mode 100644 index 00000000..81893bd4 Binary files /dev/null and b/modules/images/kebab.png differ diff --git a/modules/images/konveyor-logo-tackle.svg b/modules/images/konveyor-logo-tackle.svg new file mode 100644 index 00000000..4f21a7b4 --- /dev/null +++ b/modules/images/konveyor-logo-tackle.svg @@ -0,0 +1,189 @@ + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/importing-applications/index.html b/modules/importing-applications/index.html new file mode 100644 index 00000000..5273046a --- /dev/null +++ b/modules/importing-applications/index.html @@ -0,0 +1,324 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Importing applications

+
+

You can import one or more applications into the Application inventory page of the Tackle web console by using a CSV file.

+
+
+ + + + + +
+
Note
+
+
+

You cannot create tags or business services by importing a CSV file. Specified tags or business services must exist in the web console before you import the applications.

+
+
+
+
+

The CSV file contains the following fields:

+
+
+

Record Type 1:

+
+
+
    +
  • +

    Describes an application or application dependencies.

    +
  • +
  • +

    Required for all records.

    +
  • +
+
+
+

The following values are allowed for Record Type 1:

+
+
+
    +
  • +

    1: Application: This option has the following fields:

    +
    +
      +
    • +

      Application Name: Required.

      +
    • +
    • +

      Description: Optional.

      +
    • +
    • +

      Comments: Optional.

      +
    • +
    • +

      Business Service: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag Type <1..20>: Optional. Must exist in the web console.

      +
    • +
    • +

      Tag <1..20>: Optional. Must exist in the web console.

      +
      +

      You can import up to 20 Tag Type <x> and Tag <x> fields.

      +
      +
    • +
    +
    +
  • +
  • +

    2: Application dependencies: This option requires the following fields:

    +
    +
      +
    • +

      Application Name

      +
    • +
    • +

      Dependency: Must be the same as the Application Name of the dependency.

      +
    • +
    • +

      Dependency Direction: Allowed values are northbound and southbound.

      +
      +

      All other fields are empty.

      +
      +
    • +
    +
    +
  • +
+
+ + +++++++++++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1. CSV example
Record Type 1Application NameDependencyDependency DirectionDescriptionCommentsBusiness ServiceTag Type 1Tag 1Tag Type 2Tag 2Tag Type 3Tag 3

1

Imported-Purchasing

Vendor management

Required for purchase order processing and accounts payable

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

2

Imported-Purchasing

Tiller

northbound

1

Imported-PO

Requisitions, purchase orders, goods received

Requisition to receipt

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-Payroll

Payroll

To be retired at the end of the financial year

Finance and HR

Language

Java

Database

Oracle

Language

Java

2

Imported-Payroll

Imported-GL

northbound

2

Imported-Payroll

Imported-HR

southbound

1

Imported-GL

General Ledger

Finance and HR

Operating System

Z/OS

Database

DB2

Language

COBOL

1

Imported-HR

Human Resources

Go live scheduled for Q3

Finance and HR

Operating System

RHEL 8

Database

PostgreSQL

Language

Python

+
+
Prerequisites
+
    +
  • +

    Valid CSV file.

    +
  • +
  • +

    Specified business services, tag types, and tags created in the web console.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Import.

    +
  4. +
  5. +

    Browse to the CSV file and click Open.

    +
  6. +
  7. +

    Click Import.

    +
    +

    The imported applications are displayed on the Application inventory page .

    +
    +
  8. +
+
+ + +
+ + diff --git a/modules/installing-operator/index.html b/modules/installing-operator/index.html new file mode 100644 index 00000000..8fa07db0 --- /dev/null +++ b/modules/installing-operator/index.html @@ -0,0 +1,84 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle Operator

+
+

You download and install the Tackle Operator on an Enterprise Kubernetes Platform cluster.

+
+
+
Prerequisites
+
    +
  • +

    You must have cluster-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Install the Tackle Operator:

    +
    +
    +
    $ kubectl create -f https://operatorhub.io/install/tackle-operator.yaml
    +
    +
    +
    +

    The Tackle Operator is installed in the {namespace} namespace by default.

    +
    +
  2. +
  3. +

    Verify the Tackle Operator installation by viewing its resources:

    +
    +
    +
    $ kubectl get all -n my-tackle-operator
    +
    +
    +
  4. +
+
+ + +
+ + diff --git a/modules/installing-tackle-application/index.html b/modules/installing-tackle-application/index.html new file mode 100644 index 00000000..68119fc8 --- /dev/null +++ b/modules/installing-tackle-application/index.html @@ -0,0 +1,93 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Installing the Tackle application

+
+

You install Tackle in a namespace by creating an instance of the Tackle application.

+
+
+
Prerequisites
+
    +
  • +

    The Tackle Operator must be installed on the cluster.

    +
  • +
  • +

    You must have project-admin privileges.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    Create an instance of the Tackle application, specifying its namespace:

    +
    +
    +
    $ kubectl apply -n <namespace> -f https://raw.githubusercontent.com/konveyor/tackle-operator/main/src/main/resources/k8s/tackle/tackle.yaml
    +
    +
    +
    + + + + + +
    +
    Note
    +
    +
    +

    You can create multiple instances of the Tackle application in the same namespace by specifying a unique name for each instance in the tackle.yaml file.

    +
    +
    +
    +
  2. +
  3. +

    In the Kubernetes dashboard, click WorkloadsDeployments to verify the installation.

    +
  4. +
+
+ + +
+ + diff --git a/modules/making-open-source-more-inclusive/index.html b/modules/making-open-source-more-inclusive/index.html new file mode 100644 index 00000000..2764662c --- /dev/null +++ b/modules/making-open-source-more-inclusive/index.html @@ -0,0 +1,52 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Making open source more inclusive

+
+

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

+
+ + +
+ + diff --git a/modules/managing-application-dependencies/index.html b/modules/managing-application-dependencies/index.html new file mode 100644 index 00000000..4ef945d1 --- /dev/null +++ b/modules/managing-application-dependencies/index.html @@ -0,0 +1,72 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application dependencies

+
+

You can add, delete, and view application dependencies in the Manage dependencies window on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab beside an application and select Manage dependencies.

    +
  4. +
  5. +

    To add dependencies, select applications in the northbound or southbound dependencies fields.

    +
  6. +
  7. +

    To remove dependencies, delete selected applications in the northbound or southbound dependencies fields.

    +
  8. +
  9. +

    Click Close to save and close.

    +
  10. +
+
+ + +
+ + diff --git a/modules/managing-imports/index.html b/modules/managing-imports/index.html new file mode 100644 index 00000000..f04c36fe --- /dev/null +++ b/modules/managing-imports/index.html @@ -0,0 +1,82 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Managing application imports

+
+

You can manage application imports on the Application import page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Options menu kebab in the toolbar and select Manage imports.

    +
    +

    The Application import page displays a list of application imports.

    +
    +
  4. +
  5. +

    Click the Options menu kebab beside an application import and select one of the following options:

    +
    +
      +
    • +

      Delete deletes the application import.

      +
    • +
    • +

      View error report displays a table of application import errors.

      +
    • +
    • +

      Export errors enables you to save the application import errors as a CSV file.

      +
    • +
    +
    +
  6. +
+
+ + +
+ + diff --git a/modules/reviewing-assessment/index.html b/modules/reviewing-assessment/index.html new file mode 100644 index 00000000..2798be2b --- /dev/null +++ b/modules/reviewing-assessment/index.html @@ -0,0 +1,95 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Reviewing an assessment

+
+

You review an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    An application must have a Completed assessment status and a Not started review status.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application with a Completed assessment status and a Not started review status and click the Review button in the toolbar.

    +
  4. +
  5. +

    Review the assessment in the Assessment summary section on the Review page.

    +
    +

    The Assessment summary table contains a Risk column that indicates the severity of the risk associated with each response.

    +
    +
  6. +
  7. +

    Select a Proposed action and an Effort estimate.

    +
  8. +
  9. +

    Set values for Business criticality and Work priority.

    +
  10. +
  11. +

    Optional: Enter comments in the Comments field.

    +
  12. +
  13. +

    Click Submit review.

    +
    +

    The Review status of each application is Completed.

    +
    +
  14. +
  15. +

    Expand the application to view the review results.

    +
  16. +
+
+ + +
+ + diff --git a/modules/starting-assessment/index.html b/modules/starting-assessment/index.html new file mode 100644 index 00000000..01bd6a17 --- /dev/null +++ b/modules/starting-assessment/index.html @@ -0,0 +1,89 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Starting an assessment

+
+

You start an application assessment on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Select an application that does not have a Completed assessment status and click the Assess button in the toolbar.

    +
  4. +
  5. +

    Select individual stakeholders or stakeholder groups and then click Next.

    +
  6. +
  7. +

    Select responses to questions on each page of the Application assessment wizard and then click Next.

    +
    + + + + + +
    +
    Note
    +
    +
    +

    All questions are mandatory.

    +
    +
    +
    +
  8. +
  9. +

    When you have completed all the responses, click Save to save the assessment or Save and review to start the assessment review process.

    +
    +

    The Assessment status of each assessed application is Completed.

    +
    +
  10. +
+
+ + +
+ + diff --git a/modules/updating-business-service-of-application/index.html b/modules/updating-business-service-of-application/index.html new file mode 100644 index 00000000..36f10429 --- /dev/null +++ b/modules/updating-business-service-of-application/index.html @@ -0,0 +1,77 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the business service assigned to an application

+
+

You can update the business service assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Prerequisites
+
    +
  • +

    The business service must exist on the Controls page.

    +
  • +
+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Select a business service and click Save.

    +
    +

    The updated business service is displayed in the Business service column of the application.

    +
    +
  6. +
+
+ + +
+ + diff --git a/modules/updating-tags-of-application/index.html b/modules/updating-tags-of-application/index.html new file mode 100644 index 00000000..f44fce7e --- /dev/null +++ b/modules/updating-tags-of-application/index.html @@ -0,0 +1,69 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Updating the tags assigned to an application

+
+

You can add or remove tags assigned to an application on the Application inventory page of the Tackle web console.

+
+
+
Procedure
+
    +
  1. +

    In the Tackle web console, click Application inventory.

    +
  2. +
  3. +

    Click the Edit icon beside an application.

    +
  4. +
  5. +

    Add or delete tags and click Save.

    +
  6. +
  7. +

    Expand the application to view the updated tags.

    +
  8. +
+
+ + +
+ + diff --git a/modules/upgrading/index.html b/modules/upgrading/index.html new file mode 100644 index 00000000..d1323562 --- /dev/null +++ b/modules/upgrading/index.html @@ -0,0 +1,208 @@ + + + + + + +Tackle Documentation | Tackle documentation + + + + + + + + + + + + + + + + + + + + + + +
+

Upgrading the Tackle application

+
+
+
+

You manually upgrade instances of the Tackle application.

+
+
+
+
+

Upgrading from version 1.1.0 to 1.2.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.1.0 to 1.2.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-keycloak keycloak-theme=quay.io/konveyor/tackle-keycloak-init:1.2.0
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.2.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.2.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.2.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.2.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+
+

Upgrading from version 1.0.0 to 1.1.0

+
+
+

You manually upgrade an instance of the Tackle application from 1.0.0 to 1.1.0.

+
+
+
Prerequisites
+
    +
  • +

    You must have project administrator privileges.

    +
  • +
+
+
+
Procedure
+

For each step, specify the namespace and the Tackle instance name.

+
+
+
    +
  1. +

    Update the keycloak deployment of the Tackle instance:

    +
    +
    +
    $ kubectl -n <namespace> exec deployments/<tackle_instance>-keycloak \
    +  -c <tackle_instance>-keycloak -- bash -c '/opt/jboss/keycloak/bin/kcadm.sh \
    +  update realms/tackle -s internationalizationEnabled=true -s supportedLocales+=en \
    +  -s supportedLocales+=es -s defaultLocale=en --server http://localhost:8080/auth \
    +  --realm master --user $KEYCLOAK_USER --password $KEYCLOAK_PASSWORD'
    +
    +
    +
  2. +
  3. +

    Update the application-inventory-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-application-inventory-rest \
    +  <tackle_instance>-application-inventory-rest=quay.io/konveyor/tackle-application-inventory:1.1.0-native
    +
    +
    +
  4. +
  5. +

    Update the controls-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-controls-rest \
    +  <tackle_instance>-controls-rest=quay.io/konveyor/tackle-controls:1.1.0-native
    +
    +
    +
  6. +
  7. +

    Update the pathfinder-rest deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-pathfinder-rest \
    +  <tackle_instance>-pathfinder-rest=quay.io/konveyor/tackle-pathfinder:1.1.0-native
    +
    +
    +
  8. +
  9. +

    Update the ui deployment:

    +
    +
    +
    $ kubectl set image -n <namespace> deployment/<tackle_instance>-ui \
    +  <tackle_instance>-ui=quay.io/konveyor/tackle-ui:1.1.0
    +
    +
    +
  10. +
  11. +

    Log in to the web console and click the Help icon beside the user name to verify the upgrade.

    +
    +

    The About Tackle window opens and displays the version number.

    +
    +
  12. +
+
+
+
+ + +
+ + diff --git a/redirects.json b/redirects.json new file mode 100644 index 00000000..9e26dfee --- /dev/null +++ b/redirects.json @@ -0,0 +1 @@ +{} \ No newline at end of file diff --git a/robots.txt b/robots.txt new file mode 100644 index 00000000..e087884e --- /dev/null +++ b/robots.txt @@ -0,0 +1 @@ +Sitemap: /sitemap.xml diff --git a/sitemap.xml b/sitemap.xml new file mode 100644 index 00000000..f66da30e --- /dev/null +++ b/sitemap.xml @@ -0,0 +1,277 @@ + + + +/CONTRIBUTING/ + + +/modules/about-pathfinder/ + + +/documentation/modules/about-pathfinder/ + + +/documentation/doc-installing-and-using-tackle/modules/about-pathfinder/ + + +/documentation/modules/about-reports/ + + +/documentation/doc-installing-and-using-tackle/modules/about-reports/ + + +/modules/about-reports/ + + +/documentation/doc-installing-and-using-tackle/modules/accessing-console/ + + +/modules/accessing-console/ + + +/documentation/modules/accessing-console/ + + +/documentation/modules/accessing-keycloak-admin-console/ + + +/documentation/doc-installing-and-using-tackle/modules/accessing-keycloak-admin-console/ + + +/modules/accessing-keycloak-admin-console/ + + +/documentation/modules/adding-users/ + + +/documentation/doc-installing-and-using-tackle/modules/adding-users/ + + +/modules/adding-users/ + + +/documentation/doc-installing-and-using-tackle/modules/changing-default-password/ + + +/modules/changing-default-password/ + + +/documentation/modules/changing-default-password/ + + +/documentation/modules/common-attributes/ + + +/modules/common-attributes/ + + +/documentation/doc-installing-and-using-tackle/modules/common-attributes/ + + +/modules/console-services/ + + +/documentation/doc-installing-and-using-tackle/modules/console-services/ + + +/documentation/modules/console-services/ + + +/documentation/modules/copying-assessments-and-reviews/ + + +/documentation/doc-installing-and-using-tackle/modules/copying-assessments-and-reviews/ + + +/modules/copying-assessments-and-reviews/ + + +/modules/creating-application/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-application/ + + +/documentation/modules/creating-application/ + + +/documentation/modules/creating-business-service/ + + +/modules/creating-business-service/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-business-service/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-job-function/ + + +/modules/creating-job-function/ + + +/documentation/modules/creating-job-function/ + + +/modules/creating-stakeholder-group/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder-group/ + + +/documentation/modules/creating-stakeholder-group/ + + +/documentation/modules/creating-stakeholder/ + + +/modules/creating-stakeholder/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-stakeholder/ + + +/documentation/modules/creating-tag-type/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-tag-type/ + + +/modules/creating-tag-type/ + + +/documentation/doc-installing-and-using-tackle/modules/creating-tag/ + + +/documentation/modules/creating-tag/ + + +/modules/creating-tag/ + + +/documentation/modules/deleting-assessment/ + + +/modules/deleting-assessment/ + + +/documentation/doc-installing-and-using-tackle/modules/deleting-assessment/ + + +/modules/editing-assessment/ + + +/documentation/doc-installing-and-using-tackle/modules/editing-assessment/ + + +/documentation/modules/editing-assessment/ + + +/documentation/doc-installing-and-using-tackle/modules/importing-applications/ + + +/documentation/modules/importing-applications/ + + +/modules/importing-applications/ + + +/ + + +/documentation/modules/installing-operator/ + + +/modules/installing-operator/ + + +/documentation/doc-installing-and-using-tackle/modules/installing-operator/ + + +/documentation/doc-installing-and-using-tackle/modules/installing-tackle-application/ + + +/documentation/modules/installing-tackle-application/ + + +/modules/installing-tackle-application/ + + +/documentation/modules/making-open-source-more-inclusive/ + + +/documentation/doc-installing-and-using-tackle/modules/making-open-source-more-inclusive/ + + +/modules/making-open-source-more-inclusive/ + + +/documentation/modules/managing-application-dependencies/ + + +/documentation/doc-installing-and-using-tackle/modules/managing-application-dependencies/ + + +/modules/managing-application-dependencies/ + + +/modules/managing-imports/ + + +/documentation/modules/managing-imports/ + + +/documentation/doc-installing-and-using-tackle/modules/managing-imports/ + + +/documentation/doc-installing-and-using-tackle/master/ + + +/documentation/modules/reviewing-assessment/ + + +/modules/reviewing-assessment/ + + +/documentation/doc-installing-and-using-tackle/modules/reviewing-assessment/ + + +/documentation/modules/starting-assessment/ + + +/documentation/doc-installing-and-using-tackle/modules/starting-assessment/ + + +/modules/starting-assessment/ + + +/documentation/modules/updating-business-service-of-application/ + + +/documentation/doc-installing-and-using-tackle/modules/updating-business-service-of-application/ + + +/modules/updating-business-service-of-application/ + + +/documentation/modules/updating-tags-of-application/ + + +/documentation/doc-installing-and-using-tackle/modules/updating-tags-of-application/ + + +/modules/updating-tags-of-application/ + + +/documentation/modules/upgrading/ + + +/documentation/doc-installing-and-using-tackle/modules/upgrading/ + + +/modules/upgrading/ + + +/documentation/docinfo.html +2025-01-25T18:02:28-06:00 + +