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 this topic after
the point with Bitergia?
Do not hesitate to modify directly the agenda at your convenience
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)
/Morgan
On 12/07/2017 17:43, Alec Hothan (ahothan) wrote:
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" <morgan.richo...@orange.com>
wrote:
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) wrote:
> 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 test projects for now at
least.
>
> To the agenda:
> - Problem statement for those who have not followed the email thread
> - General goals
> - Get feedback from current projects wrt current container versioning
scheme, Q&A
> - Who would like to participate and how to proceed
> We might need about 15’ to go over these points (no question we will
need more detailed discussion which can be better done through email or IRC after
that meeting).
>
> What would be great is for those concerned project owners to think about
how the requirements of their respective project wrt to their container versioning:
> - How often do you think you need to build your containers
> - Any hurdles experienced while building/managing container images
> - How do your container images relate to OPNFV releases (e.g. do you
have a 1 container version per release of do you prefer to have 1 version that
tackles all supported releases)
> - How do you “bundle” your containers to OPNFV releases (or how do your
users know what version of container to use for a given release)
>
> We can also use email to get a head start or for those who cannot attend
the meeting.
> I hope we can get a draft proposal by early August.
>
> Thanks
>
> Alec
>
>
> On 7/11/17, 8:29 AM, "Fatih Degirmenci" <fde...@gmail.com> wrote:
>
> +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
>
> On 11 Jul 2017, at 17:16, Alec Hothan (ahothan) <ahot...@cisco.com>
wrote:
>
> Can we work on a proposal and get every project that deals with
containers involved?
>
> _______________________________________________
> test-wg mailing list
> test...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/test-wg
--
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA
Network architect for innovative services
Future of the Network community member
Open source Orange community manager
tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
--
Morgan Richomme
Orange/ IMT/ OLN/ CNC/ NCA/ SINA
Network architect for innovative services
Future of the Network community member
Open source Orange community manager
tel. +33 (0) 296 072 106
mob. +33 (0) 637 753 326
morgan.richo...@orange.com
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
