Skip to content

Refactors the TasksService requires per platform#2523

Merged
dmcgowan merged 1 commit intocontainerd:masterfrom
jterry75:windows_v2_tasks_service
Aug 6, 2018
Merged

Refactors the TasksService requires per platform#2523
dmcgowan merged 1 commit intocontainerd:masterfrom
jterry75:windows_v2_tasks_service

Conversation

@jterry75
Copy link
Copy Markdown
Contributor

@jterry75 jterry75 commented Aug 2, 2018

Removes the start dependency on V1 runtimes in the TasksService for:
// +build windows_v2. For unix and windows (v1) this code remains to load all
v1 runtimes as expected.

Signed-off-by: Justin Terry (VM) [email protected]

Removes the start dependency on V1 runtimes in the TasksService for:
// +build windows_v2. For unix and windows (v1) this code remains to load all
v1 runtimes as expected.

Signed-off-by: Justin Terry (VM) <[email protected]>
@jterry75
Copy link
Copy Markdown
Contributor Author

jterry75 commented Aug 2, 2018

@crosbymichael - This is what we talked about. Removes the dependency on the Windows V2 work to have a V1 runtime present on start. Eventually once windows (v1) is removed the windows_v2 tag will just be windows is my plan.

@codecov-io
Copy link
Copy Markdown

Codecov Report

Merging #2523 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2523   +/-   ##
=======================================
  Coverage   45.07%   45.07%           
=======================================
  Files          93       93           
  Lines        9780     9780           
=======================================
  Hits         4408     4408           
  Misses       4654     4654           
  Partials      718      718
Flag Coverage Δ
#linux 49.1% <ø> (ø) ⬆️
#windows 41.58% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b8f4c7a...9936370. Read the comment docs.

@@ -0,0 +1,56 @@
// +build !windows_v2
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

is windows_v2 being used here for shorthand that it imples !windows; assuming that a Makefile section at some point marries the BUILDTAG addition of windows_v2 to only be turned on when GOOS=windows?

I only ask because in your windows source file you were explicit to join windows and windows_v2. Not a big deal, but curious as maybe they should both use the same strategy, even though I think build-time constraints will most likely make it immaterial.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@estesp - Actually, in this case local_unix.go is confusing. This really is local_all.go where all is everything that exists today !windows_v2. I named it this way though because when Windows v1 is removed this would be only for Unix. You can see in Makefile.windows#L30 the following:

ifeq (${BUILD_WINDOWS_V2},1)
	BUILDTAGS += windows_v2
endif

So windows_v2 is really GOOS=windows and an additional tag -tags windows_v2. It is used to flip/flop between the Windows runtime v1 service and the new runtime v2 TasksService while the implementation is completed. Then the Windows v1 runtime will be removed.

@crosbymichael
Copy link
Copy Markdown
Member

LGTM

1 similar comment
@dmcgowan
Copy link
Copy Markdown
Member

dmcgowan commented Aug 6, 2018

LGTM

@dmcgowan dmcgowan merged commit dd97a11 into containerd:master Aug 6, 2018
@jterry75 jterry75 deleted the windows_v2_tasks_service branch August 6, 2018 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants