Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document container launch algorithm on cluster #6524

Merged
merged 1 commit into from Nov 28, 2019

Conversation

@dnegreira
Copy link
Collaborator

dnegreira commented Nov 28, 2019

Clarify what happens when one does not define a target when
launching a container in a LXD cluster.

Signed-off-by: David Negreira david.negreira@canonical.com

Clarify what happens when one does not define a target when
launching a container in a LXD cluster.

Signed-off-by: David Negreira <david.negreira@canonical.com>
@lxc-jenkins

This comment has been minimized.

Copy link

lxc-jenkins commented Nov 28, 2019

This pull request didn't trigger Jenkins as its author isn't in the whitelist.

An organization member must perform one of the following:

  • To have this branch tested by Jenkins, use the "ok to test" command.
  • To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

@freeekanayaka

This comment has been minimized.

Copy link
Member

freeekanayaka commented Nov 28, 2019

Thanks!

@freeekanayaka freeekanayaka merged commit 2948b1c into lxc:master Nov 28, 2019
4 checks passed
4 checks passed
Branch target Branch target is correct
Details
DCO All commits signed-off
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@dnegreira dnegreira deleted the dnegreira:doc-lxd-cluster branch Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.