help text for juju set-constraints needs improving

Bug #1563932 reported by Peter Matulis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Reed O'Brien

Bug Description

e.g.:

Usage: juju set-constraints [options] <service> <constraint>=<value> ...

Summary:
Sets machine constraints for a service.

Options:

-m, --model (= "")
    Model to operate in

Details:
Sets constraints for a service, which are used for all new machines provisioned for that service. They can be viewed with `juju get-constraints`.
By default, the model is the current model.
Service constraints are combined with model constraints, set with `juju set-model-constraints`, for commands (such as 'juju deploy') that provision machines for services. Where model and service constraints overlap, the service constraints take precedence.
Constraints for a specific model can be viewed with `juju get-model-constraints`.
This command requires that the service to have at least one unit. To apply constraints to the first unit set them at the model level or pass them as an argument when deploying.

Examples:

    juju set-constraints mysql mem=8G cpu-cores=4
    juju set-constraints -m mymodel apache2 mem=8G arch=amd64

See also: get-constraints
          get-model-constraints
          set-model-constraints

Tags: helpdocs
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.0-beta4
Revision history for this message
Tim Penhey (thumper) wrote :

I'm not sure the second example shown is valid.

It certainly doesn't match the usage. I think it should have the double quotes removed.

Revision history for this message
Peter Matulis (petermatulis) wrote :

Corrected and added a few other things.

description: updated
Changed in juju-core:
milestone: 2.0-beta4 → 2.0-rc1
Revision history for this message
Reed O'Brien (reedobrien) wrote :

The details line breaks don't look like paras they look kind of random. Please confirm they are correct.

Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Reed O'Brien (reedobrien)
Revision history for this message
Reed O'Brien (reedobrien) wrote :
Revision history for this message
Peter Matulis (petermatulis) wrote :

Re comment #3, right, the RB shows this:

This command requires that the service to have at least one unit. To apply
constraints to
the first unit

That is wrong. Just compare to what is in this bug's description.

Revision history for this message
Reed O'Brien (reedobrien) wrote :

That is exactly how it appears in this bug description, which is why I requested confirmation above.
I assume it should not break between "to" and "the", is that correct?

Revision history for this message
Matthew Helmke (matthelmke) wrote :

Correct, it should not break between "to" and "the."

description: updated
Revision history for this message
Matthew Helmke (matthelmke) wrote :

I have fixed the description.

Revision history for this message
Reed O'Brien (reedobrien) wrote :

Great, thanks!

 I see that the PR didn't merge yesterday evening. So I can easily push this change to that PR. Easy:)

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta5 → none
milestone: none → 2.0-beta5
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.