Re: [opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

2017-08-30 Thread Fatih Degirmenci 
Hi,

About using docker hub for builds; I thought the docker builds would remain on 
OPNFV Jenkins due to the limitation you highlighted below and the other 
limitations/potential issues we summarized in earlier discussions. [1]
I might have missed to followup discussions that have happened during the 
summer period so I'd be happy to catch up and read the reasons behind this.

If you still think of moving to docker hub for builds, we need to think and 
have a long term strategy rather than just moving builds to there and getting 
paid service as it will limit our ability to improve how we are doing things 
for test projects or projects that are building docker images.

[1] https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-July/017177.html
 
/Fatih

On 2017-08-30, 11:43, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
morgan.richo...@orange.com"  wrote:

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf

As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng

But, of course, it would make more sense to rely on official OPNFV 
docker...

José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.

Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?

BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.

Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.

Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).

The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?

Any comment welcome

/Morgan


_

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


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV] 2 questions on OPNFV docker repo

2017-08-30 Thread morgan.richomme 

Hi,

2 pending questions regarding the way we are managing our docker files

1) Cedric sent a mail 2 weeks ago ([OPNFV Helpdesk #42909] New Functest 
Docker repositories) in order to create new docker repositories: 
opnfv/functest-features, opnfv/functest-components and opnfv/functest-vnf


As it has not been done yet we are currently using Cedric's private 
docker repo (where he customized the different hook) 
ollivier/functest-components,  ollivier/functest-features and 
ollivier/functest-vnf and we referenced them in releng


But, of course, it would make more sense to rely on official OPNFV 
docker...


José asked Trevor B. to create the first repo (opnfv/functest-core, 
opnfv/functest-healthcheck and opnfv/functest-smoke) before he left in PTO.


Cedric asked for the new repo on this mail thread. Should we create a 
new ticket?


BTW it seems that there is an issue on the hooks used for OPNFV docker 
repos. Builds must be done in a precise order (core must be built prior 
to any other built), which seems not the case on OPNFV docker hub. 
Cedric detailed the issue and the fix (screenshots) in the same mail thread.


Any help will be welcome to reference official sources.

2) At the moment the Docker automated builds are used per gerrit merge 
for all OPNFV projects. As we are using a basic account and the number 
of docker produced within OPNFV is increasing there is a high risk of 
congestion.


Could it be possible to migrate to an account allowing parallel builds 
(https://hub.docker.com/billing-plans/).


The cost is reasonable, we could start with a Medium or Large one.

As docker management is transverse, widely used by testing projects, Who 
should take the lead to ask for such change to the TSC? Releng? Infra 
Group? Testig group?


Any comment welcome

/Morgan

_

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