Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-151

R&D E2E app dev scenario

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • r&d e2e flow
    • To Do
    • QE Needed, Docs Needed, TE Needed, Customer Facing
    • 0% To Do, 0% In Progress, 100% Done

      Problem

      As a Developer, I want to have a simple way to get started, have the tools generate all the code, deployment configs/manifests, as well as git repos...so that I can start with an opinionated end-to-end workflow that illustrations how I can easily take my application changes through the promotion cycle centered around git.

      Customers are given many tools, configuration options, deployment options and told to work with consulting to pull together the right end-to-end set of these to meet the right solution. Customers are wanting a more turnkey or opinionated solution that takes care of the full lifecycle of their applications: from initial change/creation all the way through their environment until it lands on instanced in production. Without some common patterns and tools, customers and consultants have to create their own solutions and it is costly to maintain.

      Acceptance Criteria

      • Developer creates a new application - generates skeleton. Which provides the right number of git repos with both skeleton code and deployment templates
      • Developer iterates on code and deployments, leveraging tools like odo, oc and helm to validate in the inner loop
      • Developer commits changes, which triggers the CI builds to define image.
      • Developer initiations promotion via a PR to git repo with promotion changes
      • Pipeline recognizes changes and deploys
      • GitOps engineer sees successful promotion, they initiate another promotion by another - PR to git repo with promotion changes to next environment repo (or folder).
      • Application and components have been deployed into the final environment

      These demonstrations/validations can be manually done to validate the approach and outline the tooling need. This will include updating and created needed supporting documents to describe the primary flow(s), tooling gaps and plans to address.

      Solution considerations

      The solution involved building out an end-to-end set of integrated set of tools around a set of opinions. In order to fully do that, it could require multiple releases to solve that. This epic brief looks evolve this solution by providing this pieces:

      • End-to-end flow of a new skeleton application, with at least 1 source code component and 1 operator-backed.
      • Document and further refinement of end-to-end solution for #1, identifying additional areas for elaboration and delivery for next release.

      Resources

            Unassigned Unassigned
            sspeiche@redhat.com Steve Speicher (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: