Support adding CAAS units #8180

Merged
merged 4 commits into from Dec 6, 2017

Conversation

Projects
None yet
3 participants
Member

axw commented Dec 6, 2017

Description of change

Fixes to state and the Application facade to support "juju add-unit" in CAAS models.

  • Adding a CAAS application no longer ignores the NumUnits parameter.
  • The state/stateenvirons policy returns "not implemented" for CAAS models. TODO(caas) added where we should add policies later.
  • The add-unit facade method doesn't attempt to assign CAAS units to machines

QA steps

  1. juju bootstrap localhost
  2. juju add-caas kubernetes k8s
  3. juju add-model k8s k8s
  4. juju deploy path/to/gitlab
  5. watch kubectl get all
    (the operator should come up, and set a container spec; the unit provisioner should then create a pod)
  6. juju add-unit gitlab
    (another pod should be created)

Documentation changes

None.

Bug reference

None.

axw added some commits Dec 6, 2017

facades/.../application: simplify tests
Simplify tests by not recording the ModelTag
method calls. It's not that interesting.
facades/.../application: don't assign CAAS units
When adding units to a CAAS application, don't
attempt to assign them to machines. When removing
CAAS units or applications, don't attempt to
destroy/detach storage.
Member

axw commented Dec 6, 2017

$$merge$$

Contributor

jujubot commented Dec 6, 2017

Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju

@jujubot jujubot merged commit 39243aa into juju:develop Dec 6, 2017

1 check failed

continuous-integration/jenkins/pr-merge This commit cannot be built
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment