search

jpetazzo / pipework

Software-Defined Networking tools for LXC (LinuX Containers)
Apache License 2.0
4.22k stars 726 forks source link

Release version #208

Closed antoinetran closed 7 months ago

antoinetran commented 7 years ago

Hi,

It could be great if there are release versions, or even alpha/beta. Pulling from master is not really production wise for us.

Thank you!

jpetazzo commented 7 years ago

Hi!

I hear you. Unfortunately, I don't have much time to commit to maintain pipework, let alone cut release versions.

Pipework was initially a workaround (back when Docker didn't have network plugins, or even host networking!) but it has been mostly superseded by Docker features.

The repo is still here, and I'm still accepting PRs and trying to answer questions, but I really can't do much more.

However, I'd be happy to hear more about your use-case, to help you to find a way to address it with more stable solutions!

Sincerely,

antoinetran commented 7 years ago

Hi,

Thank you for your answer. Well, I understand about the time needed about maintaining this project, but does it take a lot of time to just tag it in git? Just once, and without making release archive, just a tag. This feels more production-ready.

Related to network plugins, do you know if there is one that seems to replace pipework? We use pipework to give an external ip to the docker container, so that this is accessible externally.

Thank you for your time.

Yours sincerely,

Antoine

Le 03/12/2016 01:47, Jérôme Petazzoni a écrit :

Hi!

I hear you. Unfortunately, I don't have much time to commit to maintain pipework, let alone cut release versions.

Pipework was initially a workaround (back when Docker didn't have network plugins, or even host networking!) but it has been mostly superseded by Docker features.

The repo is still here, and I'm still accepting PRs and trying to answer questions, but I really can't do much more.

However, I'd be happy to hear more about your use-case, to help you to find a way to address it with more stable solutions!

Sincerely,

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/jpetazzo/pipework/issues/208#issuecomment-264600662, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANcNvmPfHEsSaCKUuw6fJPu9fKMeMAFfks5rELwOgaJpZM4K_NYf.

-- My THALES email is antoine-b.tran@thalesgroup.com. +33 (0)5 62 88 84 40

jpetazzo commented 7 years ago

Hi Antoine!

Hey that's a very good suggestion. I think I'll add a version tag even if it's very symbolic. That will let people easily pin to a specific version.

To assign public IP addresses to containers, I'd suggest to check this great blog post by the excellent Jess Frazelle, it looks like it might explain to do what you want?

antoinetran commented 7 years ago

Hi, Is-it possible to have a tag? We are referring to master branch in our production code, and we don't want the pipework code to change without testing it first. Even a 0.0.1-alpha or 0.0.1-rc1 is ok!

jpetazzo commented 6 years ago

Hello back,

Would it be possible for you to just reference a given commit hash?

(Initially I wanted to add a tag, but I'm afraid that if I do that, it'll give the wrong impression to some people; i.e. that I'd be maintaining this code, which is not the case!)

antoinetran commented 6 years ago

I can. But there is nothing wrong in tagging as an alpha, and writing that this product is deprecated in the wiki.

jpetazzo commented 7 months ago

Added a deprecation warning in the README!