Skip to content
This repository has been archived by the owner on Dec 5, 2017. It is now read-only.

Check whether podtask.T.Spec and T.Data is actually needed #646

Open
s-urbaniak opened this issue Nov 24, 2015 · 0 comments
Open

Check whether podtask.T.Spec and T.Data is actually needed #646

s-urbaniak opened this issue Nov 24, 2015 · 0 comments
Assignees
@s-urbaniak
Labels
area/scheduler class/refactoring

Comments

@s-urbaniak
Copy link

Currently the podtask.go#T struct holds a reference to the podtask Spec and Data to be used for launching the actual pod.

This is confusing because in the procurement we also have a reference to the podtask Spec in the ProcureState.

The aim is to check whether the T.Spec and T.Data reference can be removed at all.
@s-urbaniak s-urbaniak self-assigned this Nov 24, 2015
@s-urbaniak s-urbaniak changed the title Check whether podtask.T.Spec is actually needed Check whether podtask.T.Spec and T.Data is actually needed Nov 24, 2015
@s-urbaniak s-urbaniak mentioned this issue Nov 24, 2015
Merged
33 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@s-urbaniak s-urbaniak

Labels
area/scheduler class/refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@s-urbaniak @jdef