c6o / provisioners Goto Github PK

Summary:

Blank installer page:

Error running:

To Reproduce:

Steps to reproduce the behaviour:

1. Run the Ghost provisioner on staging.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Assign the following apps to the associated marketplace categories:

Grafana - Monitoring
Node-RED - IoT
Visual Studio Code - Developer Tools
Prometheus - Monitoring
Grafana - Monitoring | Dashboards
Precog - ETL
Logging (ELK) - Logging (note: can we also change the app name for consistency?)
Verdaccio - Developer Tools
Certificate Manager - DevOps tools (note: is there a more specific app name we can use?)

Business Requirements:

Our current mattermost provisioner only supports a slimmed down, preview only instance which is not production ready.
In order for teams to be able to use a production ready instance of Mattermost we will need to be able to support a full blown k8s clustered version of the product.

User Story:

As a DevOps engineer
I want to be able to provision a full blown matermost instance, ready for production
So that my team can use the instance over the long term.

Acceptance Criteria:

The provisioner is installed, with all cluster/production ready characteristics. Both the CLI and UI should work to provision with appropriate settings.

Technical Requirements:

Create a provision for mattermost which allows for a cluster based installation.

UX/UI Design:

N/A

Background:

Needs to be public facing for customers.

Summary:

Tried a fresh installation of Mattermost enterprise edition, but it does not finish installing (2+ hours so far).

NOTE: I did not supply a "mattermost license secret", though it says it's optional.

To Reproduce:

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Observed Results:

A clear and concise description of what happened that was not expected.

Expected Behavior:

A clear and concise description of what you expected to happen.

Screenshots:

If applicable, add screenshots to help explain your problem.

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Summary:

Error when building the provisioners repository.

To Reproduce:

Steps to reproduce the behavior:

1. Clone c6o/provisioners
2. Change directories (Run cd provisioners)
3. Run yarn install
4. Run yarn build
5. See error during build

Observed Results:

Isto build fails with error: "Cannot resolve dependency '@c6o/ui-theme'"

Expected Results:

The build should complete successfully.

Screenshots:

Summary:

Installation of FoldingAtHome requests 2 replicas with pod anti affinity (aka, cannot be on the same node). This means Kubernetes will complain if the cluster only has one node.

Priority: Very low. This does not actually impact Marina, or the installation of FoldingAtHome. The only way to notice something is wrong is by looking at the Kubernetes dashboard, or otherwise inspecting the cluster manually.

To Reproduce:

Steps to reproduce the behavior:

1. Create a cluster with one node.
2. Install FoldingAtHome
3. Check Kubernetes Dashboard.
4. Observe that one pod is in an error state.

Observed Results:

A clear and concise description of what happened that was not expected.

Expected Behavior:

A clear and concise description of what you expected to happen.

Screenshots:

If applicable, add screenshots to help explain your problem.

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Background:

To help developer learn how to write a provisioner so that it's easier to do. (also to help robb learn...).

Update the documentation to make it clearer and easier to get started and learn c60.

https://github.com/JanLoebel/face_recognition

https://www.tensorflow.org/tfx/serving/serving_kubernetes

https://missinglink.ai/guides/tensorflow/tensorflow-face-recognition-three-quick-tutorials/

https://github.com/natanielruiz/dockerface

1. Support UnInstall Volume UI
   a. If the app has volumes
   b. list all volumes
   c. allow user to choose which volumes to delete
   d. by default NO volumes will be chosen

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Create a MQTT provisioner.

New Change, Reorganization, System or Architecture.

Please describe the change to be made. What are the technical requirements?

Expected Benefit

Please describe how the change benefit the code base or development speed. This is the "why" of the needed change.

Systems to be changed

What is the current behavior?

Sample Code

If applicable, provide a sample code snippet that demonstrates the gist of feature you're proposing.

Context

Please provide any relevant information about the context where this feature is active.

Architetural Drawings

Please add links to relevant documentation, plans and architectural drawings.

Akaunting
etc..

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• Rename references from pilot to istiod
• Modify comments in code
• Fix spelling mistakes

Summary:

While installing Jitsy, the user is presented with a blank white screen with no text. User can still proceed with installation successfully, but it may be a little confusing to users.

To Reproduce:

Steps to reproduce the behavior:

1. Install Jitsy
2. Select edition and enter namespace.
3. Click Next
4. Observe blank white screen.

Observed Results:

Blank white configuration screen during Jitsy installation

Expected Behavior:

Should skip this page if there are no configurations to enter (or at least provide some message to say there is nothing needed)

Screenshots:

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Tasks:

1. Ensure startup probes are working, record which have them
2. Ensure apps startup correctly
3. Record apps which need a database, and which database
4. Any other relevant updates to provisioners

Create a provisioner for Folding@Home

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Tasks:

1. Consider the askAnswered arg passed in the CLI UI and remove most of them.
2. Ensure edition is not indicated in any yaml files.
3. Ensure we are considering args from the CLI itself, and that they have relatively friendly names vs our variable names.

Linked issue #1029

https://github.com/c6o/node-monorepo/issues/1029

Currently, the Mattermost provisioner ignores the uninstall inquiry to keep media and data. We need to see if we can preserve data even if the app is uninstalled. If the user re-installs, can we re-attach the data?

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Summary:

On staging: Installed Jitsi, however, I cannot join a meeting, it continually says I have been disconnected.

To Reproduce:

Steps to reproduce the behavior:

1. Install Jitsi to a new cluster
2. Open the Jitsi App
3. Attempt to start a meeting
4. Observe disconnection messages.

Observed Results:

Metting cannot start cause unable to connect

Expected Behavior:

Meeting should work out of the box

Screenshots:

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Summary:

It probably doesn't make sense to publish AppEngine as an app of its own in the marketplace. Can we remove it from the marketplace?

If we want to keep it in the marketplace for CLI purposes, then would it be possible to have it displayed in the marketplace similarly to NavStation and other system apps?

Other system apps need to be removed from the marketplace or be marked with "SYSTEM" and not installable:

• Lifeboat (persistence)
• Nav Station
• Harbourmaster (security)
• Store
• App Engine
• c6o System
• Marina

Screenshots:

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Summary:

Trying to install SuiteCRM from the marketplace using the Web UI fails to install.

To Reproduce:

1. Go to any cluster
2. Open the store
3. Search for SuiteCRM
4. Click Install.
5. See how SuiteCRM fails to install.

Observed Results:

Silent error, but changes to status "Failed"

Expected Behavior:

Should install successfully.

Screenshots:

If applicable, add screenshots to help explain your problem.

Failure Logs

Please include any relevant log snippets or files here.

Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I'm reporting the issue to the correct repository (for multi-repository projects)
• I have provided sufficient information for the team

Business Requirements:

Add support for a c6o folder + manifest.yaml file for all current provisioners so that each provisioner can be self-describing in nature. For example, fields such as:

AppId, Name, Provisioner, logo, screenshots, short/long description, editions, edition specs, ediction spec ports needed, etc..

User Story:

As a developer
I want to be able to describe my provisioner using a manifest file
So that when it is placed in the Hub it will automatically upsert all the correct values which I require.

Technical Requirements

1. When we add the provisioner to the hub, it will UPSERT the manifest into our backing datastore
2. During packaging, the c6o folder must be included in the package (yarn package)

Background:

Provide context for why this chore is needed. Remember that chores are for work that is not user-facing.

Requirements:

Describe what tasks are needed to complete the chore.

• [ ]
• [ ]
• [ ]

Business Requirements:

So that developers can control updates of their application, we need to have the App Engine honour templating of a tag in the provisioner section of the edition manifest.

      provisioner:
        name: echoserver
        tag: 2.1
        tag-prefix: appengine
        package: '@provisioner/appengine'
        image: 'robblovell/echo-server:{{tag}}'
        automated: true
        port:

User Story:

As a developer
I want to use a tag to specify what version represents this edition
So that I can update customer's installs.

Acceptance Criteria:

1. Given a provisioner manifest
   When a tag is available with a templated image
   Then the provisioner inserts the tag into the image name using the tag given.