Instantiate and manage services through Operator, part 2

[serenamarie125]

User Story

As a user, I want to create a new instance of my database or another service managed by operators So that I can use it (link it) with my application

Acceptance Criteria

• odo service create -o json create a new instance of an operator in my project, and output information about the created operator in JSON format (the output should have the same info as odo service describe <newly created service> -o json) (Instantiate operator backed service and output JSON data #2784)
• odo service describe <service name> -o json should print detailed information about service that was created (for example if is it running or not, how many instances it has, what parameters were used to create this service) in JSON format (Instantiate operator backed service and output JSON data #2784)
• odo service describe <service name> should print detailed information about service that was created (for example if is it running or not, how many instances it has, what parameters were used to create this service) (Instantiate operator backed service and output JSON data #2784)
• odo catalog describe service <name> & odo catalog describe service <name> -o json should provide detailed information about the service from OperatorHub. (describe operator backed services #2615)
• odo service create and odo service delete should should add/delete service info from devfile. Subsequent odo push should create/delete service from the cluster. odo service list should print service information with its state. (odo service create should add operator CR to the devfile #4160)
• User should not be required to provide or write any CR definitions or YAML. It should be possible to provide additional arguments for operator via the command line (as arguments to odo service create command) Provide parameters to create service backed by operators #2785

good to have:

• odo service create should allow user to interactively create operator backed services (Interactive mode for creating operator backed service #2799)

Links

• Feature Request: Instantiating operators using CRDs #2462
• Feature Request: List & Provision Services from the in-cluster installed operators (Dev Catalog) #2161

/area service-operators
/area service
/kind feature

JIRA Epic Tracking

ODO-48

[serenamarie125]

@kadel @dharmit please update with story points, thanks!

[dharmit]

odo service describe <service name> should print detailed information about service that was created (for example if is it running or not, how many instances it has, what parameters were used to create this service)

This command is applicable only for a service that's already created using odo service create (maybe even pushed to the cluster using odo push.) So we already have the spec of the service. We only need to print the spec in a pretty way.

[dharmit]

@serenamarie125 pointed it to 4 and added one more item to acceptance criteria - #4160.

[dharmit]

Moved #2785 from "good to have" to "Acceptance Criteria' since it is immediate next step after odo catalog describe service.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[dharmit]

Marking this closed as it's been done since a few sprints back.

/close

[openshift-ci]

@dharmit: Closing this issue.

In response to this:

Marking this closed as it's been done since a few sprints back.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.