Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-14 Thread Jose Lausuch
Hi Alec, Sounds good. We can talk about that during the meeting. Thanks for proposing it. Jose -Original Message- From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com] Sent: Friday, July 14, 2017 16:53 PM To: Jose Lausuch Cc: Morgan Richomme ; Mark Beierl ; opnfv-tech-discuss@lists.opn

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-14 Thread Alec Hothan (ahothan)
Hi Jose, I have moved this topic and added a sub-agenda to the July 27 test-wg weekly meeting agenda (https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting) It is good that this issue has not caused any big problem yet for container owners (likely because none of the artifac

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-13 Thread Jose Lausuch
Hi Alec, The versioning is not an urgent matter and it is working well today. I agree it is a topic to be discussed but maybe it is better to wait until everyone is back from PTO as it will be difficult to align without the participation of the people who are really involved. - Jose - > O

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-13 Thread Alec Hothan (ahothan)
Jose, You should start the discussion at the next infra wg meeting (I’ll be on PTO whole of next week). I think if the issue can be raised and acknowledged it will already be a good step. I will just note that: - this has to be a joint work by both infra and project teams - perhaps we could use

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread Jose Lausuch
Hi, Is there time to discuss this during the next infra wg meeting on Monday? Although the test projects are the main ones using docker containers, we are talking about versioning here, which I believe is topic the Infra team should address. I also would like to add to the agenda: - decisio

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread Alec Hothan (ahothan)
July/August is tricky with PTOs. Perhaps we should start the discussion by email on this mailer and discuss about it in 2 weeks at the test-wg meeting? Do you guys usually use a text document reviewed with gerrit to discuss/collaborate on a spec? Or any other method? Please let me know and I ca

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread morgan.richomme
I will be in PTO too :) Unfortunately the weekly meeting was today at 8 UTC (APAC slot) we will use the slot of tomorrow to organize an ad-hoc meeting with Bitergia on result vizualization not sure we will have 15 minutes for another topic It is maybe possible to organize an ad-hoc meeting on

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread Alec Hothan (ahothan)
Morgan, Unfortunately, I won’t be able to attend next week (on PTO). Can this be squeezed into tomorrow’s meeting (July 13)? We could shorten it and follow up with a separate meeting or on email/IRC. Thanks Alec On 7/12/17, 8:32 AM, "morgan.richo...@orange.com" wrote: topic added fo

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread morgan.richomme
topic added for the next meeting (20th of July) https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting Mark and Jose are already involved in several activities dealing with docker. Cedric has a good view on this topic. /Morgan On 12/07/2017 17:27, Alec Hothan (ahothan) wrot

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-12 Thread Alec Hothan (ahothan)
I’d like to add this topic to the next weekly meeting of the test-wg and would like to know if anybody else from test-wg would be interested to help redact a proposal for enhancing the docker container versioning and build workflow in OPNFV. As I understand this will only concern a subset of te

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-11 Thread Fatih Degirmenci
+1 to "Can we work on a proposal and get every project that deals with containers involved?" It is mainly test projects who use containers so I again let testing community to take the lead and point you to where/how the conversation started. We can then try to generalize it later on. /Fatih O

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-11 Thread Alec Hothan (ahothan)
Hi Fatih, From: Fatih Degirmenci Date: Monday, July 10, 2017 at 2:04 PM To: "Alec Hothan (ahothan)" , "Beierl, Mark" Cc: "opnfv-tech-discuss@lists.opnfv.org" , "test...@lists.opnfv.org" Subject: Re: [test-wg] docker container versioning Hi Alec, Your understanding about the docker image ta

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-10 Thread Brattain, Ross B
yardstick danube.3.0 was a mistaken premature tag before the release was postponed, we can't delete git tags, so new git tag will be danube.3.1 with docker tag danube.3.1 docker danube.3.0 image was custom build for Dovetail. We have projects consuming other project's dockers, so there are d

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-10 Thread Fatih Degirmenci
Hi Alec, Your understanding about the docker image tags seem correct to me (latest vs stable) but I let someone from test projects answer to that. When it comes to artifact versioning in general; you are asking really good questions. Let me go back in time and summarize what plans we had (ie wh

[opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-10 Thread Alec Hothan (ahothan)
[ cc test-wg - was [opnfv-tech-discuss] Multiple docker containers from one project) ] Hi Fatih It is generally not easy to deal with container tags that do not include any information that links easily to a git repo commit (e.g. a “version” number increased by 1 for each build does not tell