Skip to content

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jun 5, 2015

#2853

If any DeploymentConfigs lack triggers, it produces:

In project default

service docker-registry (172.30.139.142:5000)
  docker-registry deploys docker.io/openshift/origin-docker-registry:v0.5.4 (manual)
    #1 deployed 2 hours ago - 1 pod

service kubernetes (172.30.0.2:443)

service kubernetes-ro (172.30.0.1:80)

To see more information about a Service or DeploymentConfig, use 'osc describe service <name>' or 'osc describe dc <name>'.
You can use 'osc get all' to see lists of each of the types described above.

@smarterclayton I debating wiring this into the graph structure, but it felt weird to have a DeploymentConfig with an edge back to itself.

@smarterclayton
Copy link
Contributor

I think I was looking for something different - a simple indicator next to the DC that's says "manual triggers"

@deads2k
Copy link
Contributor Author

deads2k commented Jun 5, 2015

I think I was looking for something different - a simple indicator next to the DC that's says "manual triggers"

ok

@smarterclayton
Copy link
Contributor

Let's just do (manual) (no triggers) only.

----- Original Message -----

In project first

service database (172.30.71.209:5434 -> 3306)
  database deploys docker.io/openshift/mysql-55-centos7:latest on
  ConfigChange
    #1 deployment pending about an hour ago

service frontend (172.30.65.112:5432 -> 8080)
  frontend deploys origin-ruby-sample:latest <-
    builds git://github.com/openshift/ruby-hello-world.git with
    first/ruby-20-centos7:latest on (ImageChange|ConfigChange)
    build 1 pending for about an hour
    #1 deployment waiting on image or update

To see more information about a Service or DeploymentConfig, use 'osc
describe service <name>' or 'osc describe dc <name>'.
You can use 'osc get all' to see lists of each of the types described above.

and

In project default

service docker-registry (172.30.139.142:5000)
  docker-registry deploys docker.io/openshift/origin-docker-registry:v0.5.4
  on Manual
    #1 deployed 2 hours ago - 1 pod

service kubernetes (172.30.0.2:443)

service kubernetes-ro (172.30.0.1:80)

To see more information about a Service or DeploymentConfig, use 'osc
describe service <name>' or 'osc describe dc <name>'.
You can use 'osc get all' to see lists of each of the types described above.

? Manual only?


Reply to this email directly or view it on GitHub:
#2875 (comment)

@deads2k
Copy link
Contributor Author

deads2k commented Jun 5, 2015

In project default

service docker-registry (172.30.139.142:5000)
  docker-registry deploys docker.io/openshift/origin-docker-registry:v0.5.4 (manual)
    #1 deployed 2 hours ago - 1 pod

service kubernetes (172.30.0.2:443)

service kubernetes-ro (172.30.0.1:80)

To see more information about a Service or DeploymentConfig, use 'osc describe service <name>' or 'osc describe dc <name>'.
You can use 'osc get all' to see lists of each of the types described above.

@smarterclayton
Copy link
Contributor

LGTM [merge]

@openshift-bot
Copy link
Contributor

Evaluated for origin up to 5020b74

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/2284/) (Image: devenv-fedora_1726)

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/2843/)

openshift-bot pushed a commit that referenced this pull request Jun 6, 2015
@openshift-bot openshift-bot merged commit 13a19c3 into openshift:master Jun 6, 2015
@deads2k deads2k deleted the osc-status branch June 8, 2015 11:44
@deads2k
Copy link
Contributor Author

deads2k commented Jun 8, 2015

Fixes #2853

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