Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quantum on learn.openshift.com #882

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Quantum on learn.openshift.com #882

wants to merge 6 commits into from

Conversation

husky-parul
Copy link

Scenarios for using openshift-quantum-operators

@husky-parul
Copy link
Author

@btannous Please review this.

Copy link
Contributor

@bttnns bttnns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the scenario! I would like a few changes and/or comments before merging this in.

General Quantum Fixes

  • Needs a description and intro description
  • Since I talked to you openshift 4.5 is now released. If this should be able to run in OCP4.5 please update index.json to target this release.
  • I'd say this is intermediate level, quantum is complex but this is a getting started scenario
  • The ending step would be awesome to add links of where to get more information on OpenShift and Quantum here to direct students to additional information. Maybe include the link to the documentation that is currently in step 3 as well.
  • Can we deploy this using the "Openshift Ibm Quantum Operator" or one of the other two (not sure why there are three) within the OpenShift OperatorHub instead of cloning a repo and pulling in the source?
    • Maybe this would help with the "kernel error"?

The scenario does not work due to a jupyter kernel error

Step 1

  • setting up IBMQ Account token, I highly suggest not using vi, I usually prefer vim personally but too many people get confused with the various modes and how to get into insert mode/save/and exit. There is a built in editor for katacoda that is in the browser, I'd prefer this if there are a good amount of editing. Can also use nano or sed or something else.

Step 2

  • I'd tack this into the end of step 1. There is a template to use in markdown to automate the link instead of having to go through the openshift console.

Step 3

  • We prefer not to link to other documentation. Can this or something similar be included into this markdown instead?

Step 4

  • This looks like an awesome description! It should be put into the intro step!

Step 5

  • Not sure what is different here from step 1. Is this different?

Step 6

  • See notes of step 5.
  • See notes of step 2 on the template link.

@ryanj
Copy link
Member

ryanj commented Mar 25, 2021

Let me know when this is ready for another look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants