Skip to content

Make experimental a runtime flag#27223

Merged
thaJeztah merged 1 commit intomoby:masterfrom
mlaventure:merge-experimental
Oct 24, 2016
Merged

Make experimental a runtime flag#27223
thaJeztah merged 1 commit intomoby:masterfrom
mlaventure:merge-experimental

Conversation

@mlaventure
Copy link
Contributor

@mlaventure mlaventure commented Oct 7, 2016

Signed-off-by: Kenfe-Mickael Laventure [email protected]

Left to do:

  • Update the install script to automatically set "experimental": true if fetched from https://experimental.docker.com/
  • See what solution is adopted by API/CLI version mismatch #25498 and piggy back on it to check the daemon experimental flag
  • Update documentation

Closes #26713

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: IMO the comment should be moved to L267

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, thanks.

@mlaventure mlaventure force-pushed the merge-experimental branch 5 times, most recently from bba1b28 to da64999 Compare October 14, 2016 21:02
@icecrime
Copy link
Contributor

icecrime commented Oct 17, 2016

See what solution is adopted by #25498 and piggy back on it to check the daemon experimental flag

I think it's perfectly fine to rely on /info in the meantime (we're just talking about optimizations here). Nevermind, Swarm-mode makes this potentially slow.

Otherwise design LGTM 👍

@icecrime
Copy link
Contributor

icecrime commented Oct 19, 2016

See what solution is adopted by #25498 and piggy back on it to check the daemon experimental flag

This is a requirement, but it won't change much about this PR, so I'm moving it to code review so we can try and get it in for 1.13.0.

@justincormack
Copy link
Contributor

This seems to be working as expected, code looks fine.

LGTM

@LK4D4
Copy link
Contributor

LK4D4 commented Oct 20, 2016

LGTM
@mlaventure but need rebase

@mlaventure mlaventure force-pushed the merge-experimental branch 2 times, most recently from ec36188 to f522adf Compare October 20, 2016 17:29
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this block just be removed completely, as in build-deb?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thaJeztah
Copy link
Member

We should have a CI check or label to prevent future PR's from adding an experimental build-flag

/cc @ehazlett @mlaventure

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were we just never running tests on windows with experimental enabled previously?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, all the test have DaemonIsLinux as a prerequisite

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't the experimental features tested regardless of whether this is set on our integration daemon, or does this mean we'll still need to run the full test suite twice (once without and once with this set)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without it the experimental endpoint are not "exposed" to the clients.

However, if there''s code elsewhere that is supposed to be experimental and isn't guard by the proper check, testing both with and without the flag should help catch it.

@vdemeester
Copy link
Member

@thaJeztah @mlaventure should we move this to docs-review or should we do that in a follow up PR?

Copy link
Contributor

@vieux vieux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ehazlett
Copy link
Contributor

@docker/core-machine-maintainers machine will need some updates to support the new experimental flag.

LGTM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing "header", I guess?

Every API response now includes a `Docker-Experimental` header specifying if 
experimental features are enabled (value can be `true` or `false`).

@thaJeztah
Copy link
Member

Had one small nit on docs, but feel free to go ahead if you prefer

Signed-off-by: Kenfe-Mickael Laventure <[email protected]>
@mlaventure
Copy link
Contributor Author

@thaJeztah made the doc change.

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah
Copy link
Member

all green!

@tianon
Copy link
Member

tianon commented Dec 14, 2016

@thaJeztah
Copy link
Member

@tianon see #28160 ❤️

@praving55
Copy link

Can you point me to the reference please? I could not see it in docs

@thaJeztah
Copy link
Member

docs for 1.13 are not yet published, but the flag itself is documented in the dockerd reference. You can either set a --experimental flag on the daemon (but depends on what init system (upstart, sysv-init, systemd) you're using, or use a daemon.json configuration file, as described here; https://github.com/docker/docker/blob/v1.13.0/docs/reference/commandline/dockerd.md#daemon-configuration-file

@praving55
Copy link

Is there a reason docs are lagging? I never saw that happening before.

@thaJeztah
Copy link
Member

Not all parts of the release are released yet, so the release will be officially announced after all projects have finished their release, and the docs will probably go out together with that.

@praving55
Copy link

ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Changing the definition of experimental