Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying out Ubuntu cloud infrastructure in a lab environment, I had couple attempts and fails mostly because my references are outdated. "My main ref. now is"

My lab consists of three powerful servers, 3 low PCs, and 4 notebooks.

Constrains: Due to diversity in resources. I tried to selectively direct juju to deploy services by commissioning the low nodes first then bootstrap/deploy the needed service. But I saw in another ticket here that I can do that by specifying constrains. Is there a reference/ticket/how to article for that?

Consolidation: As jitsu is obsolete, and juju deploy to still consumes whole nodes for low services, I think add-node is the best alternative, yet again I lack the proper documentation to try this.

So I guess I'm asking for some demo case studies or best practices guides from the experts.

share|improve this question
up vote 1 down vote accepted

You can use any of the following constraints to pick the hardware required for particular machines or services. If you're using maas, you can set up tags on your nodes and then specify them with the tags constraint in juju; otherwise the cpu-cores, mem, and root-disk constraints may be enough for the situation you've described.

Note that the relevant part of jitsu's functionality has been consumed by juju: if you used, say, juju add-machine --constraints tags=bigserver to create a new machine, and that machine got given id 3, you could then use --to 3 with juju deploy or juju add-unit to place service units on that particular instance.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.