Hi,
OPNFV is an integration project leveraging continuous integration best
practices.
Most of the well-known OPNFV milestones can be achieved by linters,
unit tests and fonctional gates (see Functest).
I would encourage a release management focusing on Jenkins rather than
on JIRA.
If we do create
Hi Alexandru,
Well noted. I will update the Functest jjbs.
Byw I'm able to build the containers without arm64 build servers.
Thank you for all your contributions,
Cedric
Le jeu. 24 sept. 2020 à 18:41, Alexandru Avadanii <
alexandru.avada...@enea.com> a écrit :
> Hi,
>
> Since we are taking most
What's the OpenStack version?
I would rather advise you to select the rolling ones (hunter, iruya, jerma,
kali or latest).
Le mer. 9 sept. 2020 à 20:35, Cedric OLLIVIER a
écrit :
> Hi,
>
> The timeout are huge and we shouldn't modify them.
>
> Could you please send me
Hi,
The timeout are huge and we shouldn't modify them.
Could you please send me all Functest logs (/home/opnfv/functest/results)?
It will ease finding the root cause.
Cédric
Le mer. 9 sept. 2020 à 19:21, Ankit Goel a
écrit :
> Hi All,
>
> We have deployed OPNFV via FUEL installer on Azure ubu
Cyborg testing is part of Functest Kali and master.
Cédric
Le lun. 31 août 2020 à 18:31, Al Morton a écrit :
> Hi OPNFV,
>
> This week's Release meeting will focus on some very specific requirement
> areas, and I ask that everyone with expertise please attend! (PTLs,
> Committers, Contributors)
Hi,
You do connect to the root url (/test), login, and then you can declare
your new testcase as PTL.
Swagger can't be used for a while.
Cédric
Le lun. 31 août 2020 à 18:59, Chen Liang a
écrit :
> Hello all,
>
>
>
> I would like to integrate with test api, by following a
> https://wik
Hi,
Could you please check the routes defined in your jumphost (check the
external network)?
You may try to simply reach any floating ip via your jumphost (docker
simply adds an addional nat).
Cédric
Le lun. 24 août 2020 à 18:55, Vivekanandan Muthukrishnan <
vmuthukrish...@aarnanetworks.com> a é
Hi Daniel,
We will miss you a lot ! It has been a true pleasure to discuss with
you especially during the LFN technical events.You're amongst the best
OPNFV supporters and you always emphasize our leitmotiv: Code first!
+1 for "May the source be with you!""Try it, you will love it" as used
in a few
unfortunately)OPNFV
> documentation.
>
> We basically need to allow PTL to bypass JJB based workflows which is
> IMHO very inconvenient and discouraging. How are other LF projects
> doing?
>
> Thanks
>
>Alec
>
>
>
> From:
> on behalf of Cedric O
Please see:
https://jira.opnfv.org/browse/RELENG-427
https://jira.opnfv.org/browse/RELENG-428
Again who, from OPNFV active members and out of LF, can merge in
lfit/releng-global-jjb?
Cédric
On Sat, 2019-12-14 at 22:29 +0100, Cedric OLLIVIER via Lists.Opnfv.Org
wrote:
> Ok the root cause of
;t do it out of LF)? and then reverting this change breaking
> > master?
> >
> > Cédric
> >
> > On Fri, 2019-12-13 at 19:57 -0500, Aric Gardner wrote:
> > > It was actually this change, that failed jjb-merge
> > >
> > > https://gerrit.
Cédric
On Fri, 2019-12-13 at 19:57 -0500, Aric Gardner wrote:
> It was actually this change, that failed jjb-merge
>
> https://gerrit.opnfv.org/gerrit/c/releng/+/67813
>
> that is breaking future commits.
>
> I will look at it tomorrow.
>
>
> On Fri, Dec
Hi,
I think a few people have faced with Releng issues for the last days
when creating their stable branches. The problem is linked to releng-
jjb-verify which seems defined out of OPNFV via submodule [1] (hoping
I'm wrong as all OPNFV projects would depend on it) or to the build
host.
jenkins
Hi,
Clearwater repo is down for maintainance which raises side effects in
our Ims-based testcases:
http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/2019-October/001800.html
http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/2019
Hi,
Functest doesn't need this job as we build our docs directly on readthedocs
(rtd).
Else we (DOC PTL?) could update the job to a newer interpreter available on
the build servers.
Cédric
Le mer. 9 oct. 2019 à 04:25, Dan Xu a écrit :
> Hi all,
>
>
>
> When I submit a patch to gerrit, it auto
Hello,
What's the roles defined for Swift?Could you please send me all
artifacts located in /home/opnfv/functest/results? It will help here.
Thank you,Cédric
Le vendredi 27 septembre 2019 à 06:07 +, via Lists.Opnfv.Org a
écrit :
> Hi all,
>
>
>
>
>
>
>
> While running functest all the
Hi,
Forcing cinder = true could please the SUT here which may be wrong
regarding verification or certification.
At first glance , I think block-storage should have been created in
Apex (I'm very suprised we didn't catch it in OPNFV gates) and XCI.
I'm diving into the details but devstack (and the c
Hi,
If I'm not wrong, XCI still deploys OpenStack Rocky, right?
https://git.opnfv.org/releng-xci/tree/xci/config/pinned-versions#n40
Devstack creates 'block-storage' which seems fine regarding the
comments
https://github.com/openstack/devstack/blob/stable/rocky/lib/cinder#L350https://github.com/ope
Hi,
We could rather add the right endpoint according to the OpenStack
release under test.Could you please precise the release here?
>From an overall point of view, that hook is incorrect because Rally
must discover the service and then must write the right tempest
config.Also we may also care about
Hi Malavika,
Have you precised the upper-constraints when installing the
package?Then the right versions will be automatically installed.
Cédric
Le mardi 30 juillet 2019 à 07:00 +, via Lists.Opnfv.Org a écrit :
> Hi all,
>
>
>
>
>
> Recently I tried to debug functest code in visual stud
Hi,
Could we please clean the Jenkins job cache and generate the Jenkins
jobs. Some multijobs have been false for a while and it will be great
to maintain the current system even if it concerns a few active
projects right now.
It would have been great to investigate why it has occured a few times
Hello,
You must be able to reach all $OS_INTERFACE endpoints and Keystone internal
endpoint from our containers, and then public endpoints from VMs (VNF).
Else this error is returned.
If I'm not wrong, you can directly run your containers from Director.
EXTERNAL_NETWORK is the public network defi
I accept the nomination.
Thank you,Cédric
On Sat, 2019-07-06 at 20:11 +, HU, BIN wrote:
> Dear OPNFV Community,
>
> I would like to nominate Cedric Ollivier from Orange for a seat on
> the TSC.
>
> Being a current member of TSC, Cedric has made many contributions to
>
Hi Deepak,
Most notably, IaaS verification requires the admin role to check or
call the admin operations (tempest, rally, vmtp, etc...).But Functest
also asks for this role to ensure that the testcases can be executed
whatever the resources already allocated when: - verifying production
environmen
Hi,
Yes we can easily update that part even if the benefits are not so
clear out of '*'.We can allow regex in our logics (or simply exclude
the tests for all values if scenarios is unset in blacklist.yaml).I
will add you as reviewer.
Cédric
On Fri, 2019-06-21 at 08:25 +, xudan wrote:
> Hi all
Hi,
My main concern about Releng is simply its overall architecture (I consider
Jenkins jobs builder as quite powerful even if we do spend time before
mastering it).
It forbids all projects to manage jobs in project branches (see Zuul,
travis-ci,etc...). Then a simple renaming leads to lots of sta
r
> Dell EMC |
> Cloud & Communication Service Provider Solution
>
> mark.bei...@dell.com
>
>
> From: on behalf of Cedric
> OLLIVIER
>
> Date: Saturday, March 30, 2019 at 13:12
>
> To: "HU, BIN" , "Cooper, Trevor" <
> trevor.
Hello,
Functest team proudly announces the publication of Functest Iruya containers.
They allow verifying Kubernetes v1.14.0 and the next OpenStack Stein which
should be released between Apr 08 - Apr 12 [1].
(Functest is already synchronized with OpenStack stable/stein requirements and
upper-con
Hello,
Who is the target audience here? internal or external?At firth glance,
I would have considered internal discussions to prevent from next
damaging public messages like the next 2 email sent to ONAP TSC and
OPNFV TSC.
https://lists.onap.org/g/onap-tsc/message/4804https://lists.opnfv.org/g/opnf
e 4, in
import sfc.lib.openstack_utils as os_sfc_utils File
"/usr/lib/python2.7/site-packages/sfc/lib/openstack_utils.py", line 13,
in from snaps.config.vm_inst import
FloatingIpConfigImportError: No module named config.vm_inst>>>
Le jeudi 14 mars 2019 à 17:39 +0100,
; >
> > As you suggested, I started using the container "opnfv/functest-
> > features:latest"; however, I don't see sfc project there. Is there
> > anything wrong?
> >
> > Regards,
> > Manuel
> >
> > On Wed, 2019-03-06 at 19:00 +0
SFC is now enabled in Functest master which could be the best
containers regarding your SUT (XCI).https://gerrit.opnfv.org/gerrit/#/c
/66811/
It had been disabled in Functest master when the SFC hunter branch
didn't exist (requirement synchronization).
Cédric
Le mercredi 06 mars 2019 à 11:39 +0100
Hello Aric,
Yes. Our gates are rolling this morning
https://build.opnfv.org/ci/view/functest/job/functest-latest-gate/72/
Thank you for your quick fix!
Have a nice weekend,
Cédric
Le vendredi 15 février 2019 à 16:08 -0500, Aric Gardner a écrit :
> Side effects after the last gerrit migration (1
Hello,
It seems that we can't access to git refs anymore via cgit.
e.g.
https://git.opnfv.org/functest/tree/upper-constraints.txt?h=refs/changes/35/67035/3
Or even by commit id:
https://git.opnfv.org/functest/commit/upper-constraints.txt?id=fa8c50f4fd19576a2fde5b04077810d4ca91b330
Is it my mis
Hi Alec,
You're right.
It should be noted that we are excluding the oldest opensource projects
(Linux, GNU/Linux distributions, etc...) from that discussion.We are
just listing few LFN projects and OpenStack (and wrongly in case of ODL
which has been cited multiple times).
But it's simply related t
Hello Manuel.
I fully second you about asking Linux team about their processes.The
Linux Kernel leverages on maintainers which is far from what we are
proposing.And you become arch/release maintainers thanks to your skills
(Meritocraty). https://www.kernel.org/doc/html/latest/process/2.Process
.htm
Hello,
New development process enforcement for which developers?
The proposal could maybe make sense in a very active community with lots of
developers without any automated verification jobs.
Both assumptions are false:
* as bitergia statistics (https://opnfv.biterg.io) have been showing
Hello,
New Xtesting and Functest Ansible playbooks were recently published to ease
deploying your own testing toolchains (even on your laptop).
They conform with the OPNFV model except for the dependency to Google Storage
(Minio is selected here).
For the time being, the next components are auto
Hello,
I would like to comment a little bit the removal of "Operate a set of
servers/labs and services (git, gerrit, jenkins,..)".It may partially
work at OPNFV project level but I'm not convinced it's doable
everywhere in OPNFV.I would have thought it's up to OPNFV projects to
ease the reuse by g
Hello,
On behalf of OPNFV Functest team, I'm proud to announce that Functest
containers run on Raspberry PI. Then we can verify any OpenStack
deployment at the price of 50 euros (hardware and software included).
Be free to apply the procedures described in our wiki:
https://wiki.opnfv.org/display
Hello,
I don't know if the current issues are related to a missing strategy
but I think we are moving away from the project scope.
Why not emphazing here XCI which only supports virtual machine
deployment and the compliance program which mainly includes sparsed
functional tests. But our endusers
Hello,
The purpose of this mail is to notify the OPNFV TSC that Functest
project intends to participate in the OPNFV Hunter and Iruya
releases.We intend to follow both the traditional track and the
continuous delivery track.
It should be noted that: - Functest Hunter was released - Functest
Iruy
+1
We could improve the process here.
If I'm not wrong, it's not the first release delayed few days before the
first schedule.
Cédric
Le ven. 2 nov. 2018 à 09:25, Yang (Gabriel) Yu
a écrit :
> +1
>
> -Original Message-
> From: opnfv-...@lists.opnfv.org [mailto:opnfv-...@lists.opnfv.org
Hello,
Functest Gambia targets OpenStack Queens (or older thanks to backward
compatibility).
It mustn't be executed in any installer master jobs (even more in case
of Apex which is already deploying OpenStack master or Rocky).
It shouldn't work by design as it has been already widely explained.
ht
Hello,
Yes, we can easily take that rule into account.If I'm not wrong, the
issue is just about adding 1 upper-case char here.
It should work already if you rename all testcases in testcases.yaml.
The only issue is more or less about the Functest version
selected.Dovetail is far away from Functest
Hello,
Functest team proudly announces the first publications of Functest Gambia [1]
and Hunter [2].
As OpenStack Rocky was released [3], Functest branches have to be created
earlier (regarding the traditional track).
That's the best way to manage all 3 OpenStack releases which have been asked b
Hello Georg,
Functest simply reads the input env vars which would suit very well your next
v3->v2 proxy.
Cédric
De : Georg Kunz [mailto:georg.k...@ericsson.com]
Envoyé : mardi 11 septembre 2018 00:46
À : Cedric OLLIVIER
Cc : Yuyang (Gabriel); OLLIVIER Cédric IMT/OLN; Rex Lee; xudan
I think there is one packaged in sdesbure/identity_wrapper. I don't know if
the code can be shared.
https://hub.docker.com/r/sdesbure/identity_wrapper/tags/
It should not be so difficult for Dovetail to implement it if you need to
support v2 due to your backport rules.
https://github.com/openstack
Georg,
You could meet your backward compatibility requirements by adding a
Keystone v2/v3 proxy.It will be the best (and not so difficult)
approach if Dovetail selects Fraser containers.
Or Dovetail may pick the right OPNFV releases according to SUT.
Cédric
On jeu., 2018-09-06 at 12:56 +, Georg
Hello,
Nothing has been proved by reducing the number of threads
here.OpenStack sets it to 4 because they know the number of cores
available in their VMsIn the context of OPNFV we could have increased
this value.
Refstack runs in parallel the previous release as well.It would be
better to go into a
Thank you, Morgan,I accept the nomination.
Cédric
On ven., 2018-08-31 at 09:02 +, Morgan Richomme wrote:
>
>
> Hi
>
>
>
>
>
>
>
> I would like to nominate Cedric Ollivier for the TSC.
>
>
>
> He has been involved in OPNFV for a
Hello Alec.
No it's clear and I agree with you.
I would simply add that there is no real requirements management in OPNFV
which has been a key issue in the current release model.
https://wiki.opnfv.org/display/functest/Requirements+management
Only Functest and few Features are synchronized with
Hello Gabriel,
Functest was split into a test framework and (OpenStack and Kubernetes)
test cases before Fraser.
Xtesting (aka the framework) is already continuously delivered and reused
by other opensource projects.
https://pypi.org/project/xtesting/
https://xtesting.readthedocs.io/en/latest/
Ye
Hello Trevor,
I think the key issues have been already deeply explained many times for
more than 6 months.
The testing frameworks cannot be verified independently for many reasons:
- no hardware resources
- no referent platform (at least one OPNFV Queens installer is closed to
be fully verifie
enstack.org/pipermail/openstack-infra/
> 2018-June/005983.html
>
>
>
> *From:* opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@
> lists.opnfv.org] *On Behalf Of *Cedric OLLIVIER
> *Sent:* Monday, July 30, 2018 8:22 PM
> *To:* xudan (N)
> *Cc:* opnfv-tech-discuss@
Hello Xudan,
60s is just in case of Cirros. That duration is very big regarding the one
required: vping testcases ends before that minute.
In case of Cloudify, the image is much more bigger which increases the
duration when caching images.
Why not setting 180 but all installers are passing all Ci
Hello,
Could you please clarify why there are two different rules applied about
Dovetail testcase names?
Most of the testcases coming from OPNFV Test Frameworks are renamed
Dovetail without the real OPNFV project supporting them (even if they are
ran asis).
If I'm not wrong, the only exception is
Hello Louie,
Our vnfs run only for os-nosdn-nofeature-* scenarios (amd64) in OPNFV gates.
It makes sense to activate vnfs in that scenarios too.
Thank you for the feedback.
We are rewriting all our vnfs to allow hugepages.
(And it’s also required to support vmdk images, provider networks, etc…).
Hello Trevor,
I don't see the point about development.
As already explained during Release meetings and Weekly Technical
meetings (+mail Tue, 19 Jun 2018), Functest team wants to introduce
Functional Gating which is mandatory for our development.
We do stop linking the test frameworks gating and
Hello Louie,
You were absolutely right to verify your deployment via Functest
Fraser. I suggest you to switch to master because this version can be
already considered as better regarding deployment configurations which
are unverified or partially verified by OPNFV gates such for instance:
- few
Hello,
Would you mind trying the two vping testcases in master (they have moved to
opnfv/functest-healthcheck)?
We have switched to the floating ip address instead of the vm attribute.
Please let us know if it works, we would backport the required changes.
Thank you in advance,
Cédric
De : op
Hello David,
We have worked hard to clean the interfaces between Functest, SFC and
SDNVPN.
It remains from our side to add few remaining docstrings to complete the
API docs.
Cédric
2018-02-28 17:12 GMT+01:00 David McBride :
> Manuel,
>
> Did this resolve your issue? Thanks.
>
> David
>
> On We
+1
Le 11 janv. 2018 8:47 AM, "Michael Polenchuk" a
écrit :
> +1
>
> On Thu, Jan 11, 2018 at 5:15 AM, Alexandru Avadanii <
> alexandru.avada...@enea.com> wrote:
>
>> Hi,
>>
>> I would like to nominate Guillermo Herrero (Enea) as a committer in
>> Fuel@OPNFV.
>>
>> I have been in contact with Guil
Yes you can safely revert it from functest side (we have written our own
multijobs). But that may raise side effects if several projects don't write
it in their Dockerfiles.
Cédric
Le 22 déc. 2017 7:27 PM, "Beierl, Mark" a écrit :
> Hello,
>
> All the StorPerf docker builds on ARM have been fai
I consider this proposal as very good regarding the multiple different
skills involved in the current releng tree.
Functest could leverage on it too as it will incubate requirements and
xtesting which could differ on interests and skills.
Switching to a dedicated project will cost at least to rena
Again squashing is not a good technical solution as it will forbid the
next cherry-picks.
You will spend much more time to fix the next conflicts than
cherry-picking by hand now.
If you have many commits to fix docs or trivial fixes in code in the
week before release, it seems that your project is
tainer it would have been really helpful to keep that formal link in
> the repo.
>
>
>
> This could be enabled very easily – only one place to change in the
> All-Projects config of gerrit. But it looks like it will take time to get
> this approved.
>
>
>
> Fo
Hello,
I would advice the offical OpenStack documentation about this topic:
https://docs.openstack.org/infra/manual/developers.html
Cédric
2017-10-19 4:23 GMT+02:00 Yujun Zhang (ZTE) :
> This could do the trick but I don't quite recommend it. There would be some
> commits on master you do NOT wa
>> >
>> >
>>
>> [Cédric]
>> Could you please have a look to the stable branch instead? You're reading
>> the
>> master Dockerfiles.
>> Here you are also mixing Project (FDS) and OPNFV gatings. We will publish
>> a
>> kind of Fu
to use).
>
>
>
> And to answer to Cedric’s question on how do other projects like openstack
> do, it is pretty simple, they all version their project code (i.e they put
> git tags to mark versions using semver syntax) and their version is
> independent of the release version ;-)
e
> they don't have native arm64 builders.
>
> BR,
> Alex
>
>
>> -Original Message-
>> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-
>> boun...@lists.opnfv.org] On Behalf Of Cedric OLLIVIER
>> Sent: Saturday, October 14,
to come up with
> clear requirements. We can then fix whatever you need together with you.
>
> /Fatih
>
> On 14 Oct 2017, at 12:32, Cedric OLLIVIER wrote:
>
> Hello,
>
> We simply require concurrent jobs properties which can be simplified
> here as parallel builds,
Hello,
We simply require concurrent jobs properties which can be simplified
here as parallel builds, concurrency control and dependency.
They are mainly required as:
- functest-core must be built before other Functest containers
- other containers should be built in parallel as soon as
functes
the arch) and allows multiple
maintainers.
But it could break rules about cross repositories. That's why we
agreed to multiply tags as storperf did.
Cédric
2017-10-13 22:59 GMT+02:00 Cedric OLLIVIER :
> Hello,
>
> Of course I will vote for 1.
> I consider 2 and 3 as false from a
Hello,
Of course I will vote for 1.
I consider 2 and 3 as false from a Docker point of view.
Yes we already have published manifests which are suitable solutions
to avoid duplicating Dockerfiles and jenkins jobs.
Let me know if you want much technical details.
I must precise that the choice done
10032185; ;
> *抄送人：* ;冯晓伟00125593; <
> opnfv-tech-discuss@lists.opnfv.org>;
> *日 期 ：*2017年09月19日 17:40
> *主 题 ：**Re: 答复: Re: 答复: Re: [opnfv-tech-discuss] About parser integration
> with functest usingthe lates container*
>
>
> It's related to the latest ansible update
t's related to the latest ansible updates. I added a constraint.
> https://gerrit.opnfv.org/gerrit/#/c/42399/
>
> Thank you
> Cédric
>
> 2017-09-19 10:23 GMT+02:00 Cedric OLLIVIER :
>
>> Hello,
>>
>> Let's try with a newer rally version (pike) as I
It's related to the latest ansible updates. I added a constraint.
https://gerrit.opnfv.org/gerrit/#/c/42399/
Thank you
Cédric
2017-09-19 10:23 GMT+02:00 Cedric OLLIVIER :
> Hello,
>
> Let's try with a newer rally version (pike) as I kept the one which we
> have tested v
Hello,
Let's try with a newer rally version (pike) as I kept the one which we have
tested via the main containers.
It's globally a big overhead.
Cédric
2017-09-19 9:17 GMT+02:00 :
> Hi,ollivier.
>
> After updating your patch about Rally error, i built the functest-parsr
> image and tested it lo
Hello Mark,
It should be noticed that Docker automated builds forbid ARG defined
before FROM and variables in FROM too.
But it's fine if they are built via releng (thanks to last Docker versions)
Great job!
Cédric
2017-09-15 17:38 GMT+02:00 Beierl, Mark :
> Hello,
>
> It is with immense pleasure
Badly we must install tempest even here as it's automically configured when
preparing env.
I will work during F dev cycle to split functest core/ci and testcases
hosted in Functest.
The issue is simply due to OpenStack upper-constraints. I must override
them to add -e (then it will be installed in
Hello,
No you shouldn't inherit from opnfv/functest-core. Otherwise you're
mixing requirements from stable/ocata and stable/pike.
It could also increase the size of the container.
I am working on it this afternoon.
Cédric
2017-09-14 12:55 GMT+02:00 :
> HI, ollivier.
>
> Using the latest contai
Cedric,
>
>
>
> Inline…
>
>
>
>
>
> From: Cedric OLLIVIER
> Date: Monday, September 11, 2017 at 10:31 PM
> To: "Alec Hothan (ahothan)"
> Cc: "Beierl, Mark" , Alexandru Avadanii
> , opnfv-project-leads
> , "opnfv-tech-discuss@lists.opnfv.or
PNFV
> release using semver compatible tags (like virtually every other open source
> project out there)
>
>
>
>
>
> Regards,
>
>
>
> Alec
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: Cedric OLLIVIER
> Date: Monday, September 11, 201
>
>
>
>
>
>
>
>
> From: on behalf of "Beierl,
> Mark"
> Date: Monday, September 11, 2017 at 6:31 AM
> To: Alexandru Avadanii
> Cc: opnfv-project-leads , Cedric
> OLLIVIER , "opnfv-tech-discuss@lists.opnfv.org"
>
> Subject: Re: [
Hello,
Could you please confirm that no stable/euphrates branch will be
created for releng again?
Else we are obliged to select a specific git commit id to build our
Functest stable containers which is not the best way.
I precise Functest depends on the opnfv python package which is hosted
by rele
ncipal Engineer
> *Dell **EMC* | Office of the CTO
> mobile +1 613 314 8106 <1-613-314-8106>
> mark.bei...@dell.com
>
> On Jul 9, 2017, at 21:00, Cedric OLLIVIER
> wrote:
>
> No we cannot (parent directory) and we should mostly avoid copying files
> (e
ul 9, 2017, at 19:03, Julien wrote:
>
> Hi Cédric,
>
> Patch in https://gerrit.opnfv.org/gerrit/#/c/36963/ is exact what I
> mean. Let's collect the opinions from the releng team.
>
> Julien
>
>
>
> Cedric OLLIVIER 于2017年7月10日周一 上午4:15写道：
>
>> H
Hello,
Please see https://gerrit.opnfv.org/gerrit/#/c/36963/ which introduces
several containers for Functest too.
I think the tree conforms with the previous requirements.
Automating builds on Docker Hub is a good solution too.
Cédric
2017-07-09 12:10 GMT+02:00 Julien :
> Hi Jose,
>
> Accordi
89 matches
Mail list logo
