Usability issues with deployments

[smarterclayton]

• Verify osc rollback disables triggers and it's possible to restore them (probably something osc deploy should do) (rollback should disable triggers and users should be able to re-enable them #3008)
• I should be able to "fail back" a deployment - scale back up the N-1 deployment and mark the latest failed, even after it's complete. Example - I rollout a change, I realize it's bad, i don't want to disable automatic updates, but I do want to not deploy until another automatic change happens. I want to scale N-1 back up, scale N down to zero, and mark N failed. (Fail back a deployment #2854)
• Rolling update deployment strategies should support canary on readiness test at minimum (Support canary for rolling deployments #2637)
• I should be able to see that automatic deployments are disabled in osc status and osc deploy (osc status and osc deploy should highlight deploymentconfigs with automatic triggers disabled #2853)

[smarterclayton]

I should be able to enable/disable triggers on osc deploy.

[deads2k]

I'll take a stab at: I should be able to see that automatic deployments are disabled in osc status and osc deploy

[abhgupta]

@deads2k Thanks! Please spin off a new issue and link it here.

[abhgupta]

I have picked up deployment "fail-back"

[smarterclayton]

Reenabling triggers is the last item remaining here.