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

Tracking card for new deploy keys in v3 #644

Closed
8 of 9 tasks
cdrage opened this issue Jun 15, 2017 · 18 comments · Fixed by #664
Closed
8 of 9 tasks

Tracking card for new deploy keys in v3 #644

cdrage opened this issue Jun 15, 2017 · 18 comments · Fixed by #664

Comments

@cdrage
Copy link
Member

cdrage commented Jun 15, 2017

We have to cover the new keys in deploy for v3 of Docker Compose, at the moment, we only have mem_limit complete.

New keys:

  • mode
  • replicas
  • placement
  • update_config
  • resources
  • restart_policy
  • labels
  • cpus (under 'resources')
  • memory (under 'resources')
@surajnarwade
Copy link
Contributor

I will take replicas key

@cdrage cdrage self-assigned this Jun 16, 2017
@cdrage
Copy link
Member Author

cdrage commented Jun 16, 2017

@surajnarwade I already started work on it, sorry :( I'm setting up a separate function so that we can parse these keys easier.

@surajnarwade
Copy link
Contributor

@cdrage okay no worries

@ashetty1
Copy link
Contributor

@cdrage also, Ports in long syntax?

@cdrage
Copy link
Member Author

cdrage commented Jun 16, 2017

@ashetty1 Open up another issue for that. But it's v3.2 and it's not even integrated into moby/moby yet.

@cdrage
Copy link
Member Author

cdrage commented Jun 20, 2017

Hey @surajnarwade wanna take this up and see how we can implement the deploy side of things? I was starting work on this but got side-tracked by the 1.0.0 release

@surajnarwade
Copy link
Contributor

@cdrage, sure, can you point me towards where you start

@cdrage
Copy link
Member Author

cdrage commented Jun 21, 2017

@surajnarwade https://github.com/docker/cli/blob/master/cli/compose/types/types.go#L159 would be a good start. Luckily we're able to easily access the deploy keys via v3.go 😄

surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
@surajnarwade
Copy link
Contributor

I will take restart-policy as well

surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 22, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 23, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 27, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 27, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 27, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jun 27, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 4, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 4, 2017
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 6, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 6, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 6, 2017
Resolves `restart_policy` from issue kubernetes#644
surajnarwade added a commit to surajnarwade/kompose that referenced this issue Jul 6, 2017
Resolves `restart_policy` from issue kubernetes#644
@surajssd
Copy link
Member

surajssd commented Jul 6, 2017

this was closed by #664 this by mistake, if this is a tracking card @surajnarwade please don't add the fixes thing in your PR because this will get closed on the next PR that says that again

@surajssd surajssd reopened this Jul 6, 2017
@surajnarwade
Copy link
Contributor

@cdrage @surajssd , I think mode is swarm specific command, it will be better if we can add it to unsupported keys

@cdrage cdrage added this to the 1.1.0 release milestone Jul 19, 2017
ashetty1 pushed a commit to ashetty1/kompose that referenced this issue Aug 10, 2017
ashetty1 pushed a commit to ashetty1/kompose that referenced this issue Aug 10, 2017
@cdrage
Copy link
Member Author

cdrage commented Aug 16, 2017

Three more to-go.

@surajnarwade

I have added mode here: #771 you said it couldn't be done, but I did it! 👍

@cdrage cdrage modified the milestones: 1.1.0 release, 1.2.0 release Aug 30, 2017
@surajnarwade
Copy link
Contributor

@cdrage , that's good.
I have investigated on placement key, I found only two mappings,

  • engine.labels.operatingsystem is equivalent to beta.kubernetes.io/os
  • node.hostname is equivalent to kubernetes.io/hostname

Does this makes sense ?
I havn't found any other mappings.

@cdrage
Copy link
Member Author

cdrage commented Sep 11, 2017

@surajnarwade that makes sense. everything else we can warn / info out.

@surajnarwade surajnarwade self-assigned this Sep 26, 2017
@cdrage
Copy link
Member Author

cdrage commented Oct 6, 2017

Placement has been completed. 1 more to-go.

@cdrage cdrage modified the milestones: 1.3.0 release, 1.4.0 release Oct 10, 2017
@cdrage cdrage modified the milestones: 1.4.0 release, 1.5.0 release Oct 31, 2017
@surajnarwade
Copy link
Contributor

@cdrage since update_config has no direct mapping in kubernetes, Let's close this issue

@cdrage
Copy link
Member Author

cdrage commented Nov 13, 2017

@surajnarwade Before that, we will have to update the conversion matrix documentation.

@surajnarwade
Copy link
Contributor

@cdrage since conversion matrix is also updated now, Let's close the issue :)

@cdrage cdrage closed this as completed Dec 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants