Thank you, all!
From: Jonas Bjurel [mailto:jonas.bju...@ericsson.com]
Sent: Monday, September 26, 2016 8:14 PM
To: Gregory Elkinbard; Stefan Berg K
Cc: Daniel Smith; opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii
Subject: RE: [opnfv-tech-discuss] [fuel] Nominating of Alexandru Avadanii
Hi, Maryam,
The next Fuel (upcoming in D release) will be Fuel 10, which is intended for
Ubuntu 16.04 (Xenial LTS).
BR,
Alex
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
> Sent:
Hi,
I started a very small etherpad for gathering ideas about packaging CI in
OPNFV, see [1].
I am aware our purpose is upstreaming our changes, but this is not always
possible or effective, hence the need for some form of our own package
distribution systems.
Hopefully, this could be a nice
Hi!
I would like to nominate Cristina Pauna (ENEA) as a committer to Armband@OPNFV,
I have checked with her and she's willing to take on the role.
Cristina has a vast networking background, and has been very active as a
contributor to Armband and Functest.
OPNFV Armband committers, please
solution.
BR,
Alex
From: Luke Hinds [mailto:lhi...@redhat.com]
Sent: Tuesday, September 27, 2016 1:20 PM
To: Leif Madsen
Cc: Alexandru Avadanii; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV Packaging CI
On Tue, Sep 27, 2016 at 1:55 AM, Leif Madsen
<lmad...@redhat.
Hi,
If gerrit web login fails, make sure you also try using the lowercase username,
even though you used to login with a capitalized username before.
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> discuss-boun...@lists.opnfv.org] On Behalf
[easily], in which case fetching some precompiled packages from an OPNFV public
repo would be nice.
BR,
Alex
From: Luke Hinds [mailto:lhi...@redhat.com]
Sent: Sunday, September 25, 2016 11:51 AM
To: Alexandru Avadanii
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV
(Bob) Monkman
Networking Software Strategy & Ecosystem Programs
ARM
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman
From: Beierl, Mark [mailto:mark.bei...@dell.com]
Sent: Thursday, July 27, 2017 6:07 PM
To: Bob Monkman <bob.monk...@arm.com<mailto:bob.monk...@arm.
]
Sent: Thursday, August 03, 2017 11:43 PM
To: Alexandru Avadanii; Taseer Ahmed
Cc: Bob Monkman; opnfv-tech-discuss@lists.opnfv.org; Alexandru Nemes
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing
Hello,
I think the docker version is too old for the build and docker
Hi,
Fuel and Armband projects are pleased to announce the public release of Danube
3.0.
1. Fuel artifacts
Git tag at [1], ISO build logs [3], ISO [5], documentation [7, 8, 9].
2. Armband artifacts
Git tag at [2], ISO build logs [4], ISO [6], documentation [10, 11, 12].
BR,
Alex
[1]
Hi,
I am looking at integrating Fuel@OPNFV/MCP with our OPNFV baremetal PODs (both
x86_64 and aarch64).
Right now I am playing with MaaS and its network configuration.
The old Fuel@OPNFV was relying on the jump server's "pxebr" bridge interface,
which is supposed to reach all baremetal nodes,
...@dell.com]
Sent: Friday, August 04, 2017 5:43 PM
To: Alexandru Avadanii
Cc: Taseer Ahmed; Bob Monkman; opnfv-tech-discuss@lists.opnfv.org; Alexandru
Nemes; Cristina Pauna; Charalampos Kominos
Subject: Re: [opnfv-tech-discuss] [armband] Resource for development or testing
Hello,
I also see
Hi,
Fuel and Armband projects are pleased to announce the public release of Danube
2.0.
1. Fuel artifacts
Git tag at [1], ISO build logs [3], ISO [5], documentation [7, 8, 9].
2. Armband artifacts
Git tag at [2], ISO build logs [4], ISO [6], documentation [10, 11, 12].
BR,
Alex
[1]
Hi,
I would like to nominate Michael Polenchuk (Mirantis) as a committer in
Fuel@OPNFV.
I have been in contact with Michael and he is willing to take on the role.
Michael is one of the main contributors in Fuel@OPNFV, as well as numerous
upstream projects,
and he has been one of the most active
Hi,
Fuel and Armband teams are working on the final bits for switching to PDF.
We proposed a minor improvement to the parsing mechanism [1]; a PDF file for
our arm-pod5 is already in place [2]; lf-pod2 PDF will land shortly (we have an
internal draft we are currently revising), and of course an
...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alexandru
Avadanii
Sent: Friday, September 15, 2017 9:03 PM
To: Julien; hu.zhiji...@zte.com.cn; chig...@huawei.com; bob.monk...@arm.com;
mpolenc...@mirantis.com; tro...@redhat.com; narinder.gu...@canonical.com;
jack.mor
relocated. Old tools will still be available in securedlab until it’s safe to
remove.
If this affects your project, please review.
BR,
Alex
[1] https://gerrit.opnfv.org/gerrit/#/q/topic:copy-pdf-from-securedlab
[2] https://gerrit.opnfv.org/gerrit/#/q/topic:use-pharos-pdf
From: Alexandru Avadanii
Sent
Hi, Trevor,
I think the new repo should have a stable/euphrates branch, but I might be
wrong.
BR,
Alex
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-
> boun...@lists.opnfv.org] On Behalf Of Trevor Bramwell
> Sent: Friday, September
[mailto:dmcbr...@linuxfoundation.org]
Sent: Thursday, September 21, 2017 3:15 AM
To: Tim Rozet; Narinder Gupta; Chigang (Justin); huzhj_zte; jason; Michail
Polenchuk; Alexandru Avadanii; Cristina Pauna; Jose Lausuch; Brattain, Ross B;
Fatih Degirmenci; Beierl, Mark
Cc: TECH-DISCUSS OPNFV; Raymond Paik; Tapio
Hi, Mark,
Thank you for the kind words :) and congratulations to all the people involved
for proposing a clean multiarch design!
We will try to slowly propose this design choice (single repo, multiarch tags)
to other test projects as well.
Looking forward to adding storperf to our daily jobs.
for not double-checking this with Jack and the Pharos
team before reaching the whole list.
And a big thanks to Jack for catching this in time!
BR,
Alex
From: yangya...@zte.com.cn [mailto:yangya...@zte.com.cn]
Sent: Tuesday, September 19, 2017 5:08 AM
To: Alexandru Avadanii
Cc: julien...@gmail.com
; hu.zhiji...@zte.com.cn;
opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii; chig...@huawei.com;
bob.monk...@arm.com; mpolenc...@mirantis.com; tro...@redhat.com;
narinder.gu...@canonical.com; jack.mor...@intel.com;
agard...@linuxfoundation.org; fatih.degirme...@ericsson.com;
huzhiji
– a simple comment w/ an e-mail at the
beggining should be enough;
BR,
Alex
From: Alexandru Avadanii
Sent: Tuesday, September 19, 2017 12:29 AM
To: 'Julien'; 'hu.zhiji...@zte.com.cn'; 'chig...@huawei.com';
'bob.monk...@arm.com'; 'mpolenc...@mirantis.com'; 'tro...@redhat.com';
'narinder.gu
Hi, David,
Fuel now pushes Yardstick results too [1]. The results are not filtered by arch
yet.
BR,
Alex
[1] http://testresults.opnfv.org/reporting/euphrates/yardstick/status-fuel.html
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On
Hi,
Fuel has been using PDF and IDF for weeks now.
We still rely on net_config, which is out of spec, to map between PDF networks
and the network role within the installer.
Apart from net_config, we still need to sort out the mapping between interfaces
indexes in PDF and the interface names
Hi,
During the E release cycle, Fuel and Armband projects merged their
documentation(s).
Currently, the contents of Fuel's 'docs/' dir describe usage for both
architecture.
To keep the old behavior unchanged, we duplicated that docs dir in Armband for
now.
Going forward, I think building the
Hi,
> -Original Message-
> From: Cedric OLLIVIER [mailto:ollivier.ced...@gmail.com]
> Sent: Sunday, October 15, 2017 8:27 PM
> To: Alec Hothan (ahothan)
> Cc: Alexandru Avadanii; Fatih Degirmenci; cedric.olliv...@orange.com; opnfv-
> tech-discuss; Delia Pope
t; Can we collect a list the requirements we need from Releng in this wiki
> >> [1]?
> >> It will facilitate the support and I will help to speed it up.
> >> Otherwise, nothing will happen as people don’t know what we need.
> >>
> >> [1]
> >> h
Hi, Ray,
It’s hard to say whether this will continue beyond E release.
Meanwhile, we will keep the docs dir in Armband, like we did in previous
releases.
BR,
Alex
From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Monday, October 16, 2017 6:26 AM
To: Alexandru Avadanii
Cc: Sofia
interface index defined in PDF and the OS interface name.
I will announce it here once we have a PoC for the network interface name
mapping.
BR,
Alex
From: Julien [mailto:julien...@gmail.com]
Sent: Monday, October 16, 2017 3:26 AM
To: Alexandru Avadanii; Jack Morgan; opnfv-tech-discuss
Cc
Hi,
Cédric pointed out that Docker uses DEB/kernel format for describing the
architecture of a Docker container.
To align with this, the Functest Docker tags were updated from
"x86_64-latest"/"aarch64-latest" to "amd64-latest"/"arm64-latest".
Although the arch-naming convention is not enforced
Hi, Jack,
No problem, thank you very much for fixing it so fast!
BR,
Alex
From: chenjiankun [mailto:chenjiank...@huawei.com]
Sent: Friday, October 13, 2017 4:40 AM
To: Alexandru Avadanii
Cc: opnfv-project-leads; TSC OPNFV; TECH-DISCUSS OPNFV; Michail Polenchuk;
David McBride
Subject: RE: [opnfv
Hi,
That is correct, everything is now AArch64 in our PODs.
BR,
Alex
From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 11:48 AM
To: Alexandru Avadanii; opnfv-us...@lists.opnfv.org;
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai
to this scenario, but again, we never
looked into it.
BR,
Alex
From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com]
Sent: Friday, September 08, 2017 4:21 PM
To: Alexandru Avadanii; opnfv-us...@lists.opnfv.org;
opnfv-tech-discuss@lists.opnfv.org
Cc: svc-armband; Bob Monkman; Shai Tsur
Hi,
How about tagging releng, without branching it?
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: Monday, September 11, 2017 7:51 AM
> To: David McBride
> Cc:
Hi, Srikanth,
I'm glad to hear about new AArch64 hardware joining OPNFV.
First, note that Pharos specs require 5 nodes, which depending on the scenario
can be used as 3 controllers + 2 computes, or 1 controller + computes.
This makes it hard to mix x86 and ARM targets in a Pharos POD. Therefore,
Hi,
Fuel and Armband projects renamed the ODL-L3 scenario to simply ODL, and
dropped the ODL-L2 scenarios, as described in [1].
I noticed that the Functest results dashboard pages [2, 3] still use the old
naming scheme, although the new scenario is also listed.
Would it be possible to cleanup
(kubi) [mailto:jean.gaoli...@huawei.com]
> Sent: Wednesday, September 13, 2017 9:59 AM
> To: Ross Brattain
> Cc: opnfv-tech-discuss@lists.opnfv.org; vven...@codeaurora.org; Alexandru
> Avadanii; 'RICHOMME Morgan IMT/OLN'
> Subject: Re: [opnfv-tech-discuss] Fuel/Armband ODL scenario rename in
&g
Hi,
A. Current Fuel PDF integration status
Fuel and Armband teams have been working on moving to the new PDF as a single
input configuration file.
We have proposed a new installer adapter template for Fuel in Pharos [1], as
well as new PDFs in securedlab for the PODs Fuel uses:
- lf-pod2 [2];
Hi, Julien,
I agree on all the items below.
Thank you for the feedback!
BR,
ALex
From: Julien [mailto:julien...@gmail.com]
Sent: Tuesday, September 26, 2017 5:52 PM
To: david.blaisonn...@orange.com; Alexandru Avadanii;
opnfv-tech-discuss@lists.opnfv.org
Cc: Guillermo Herrero
Subject: Re
+1 for the tag prefix.
How about adding the architecture to that prefix?
e.g. opnfv/functest:x86_64-release-5.0.0
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan
(ahothan)
Sent: Wednesday, September 27, 2017 11:01
Hi,
See inline.
BR,
Alex
From: david.blaisonn...@orange.com [mailto:david.blaisonn...@orange.com]
Sent: Tuesday, September 26, 2017 11:54 AM
To: Alexandru Avadanii; opnfv-tech-discuss@lists.opnfv.org
Cc: jack.mor...@intel.com; Guillermo Herrero
Subject: Re: PDF feedback and questions from our
From: david.blaisonn...@orange.com [mailto:david.blaisonn...@orange.com]
Sent: Monday, September 25, 2017 12:11 PM
To: Alexandru Avadanii; opnfv-tech-discuss@lists.opnfv.org
Cc: jack.mor...@intel.com; Guillermo Herrero
Subject: Re: PDF feedback and questions from our experience with Fuel
Hi Alexandru,
th
: chenjiankun [mailto:chenjiank...@huawei.com]
Sent: Thursday, August 24, 2017 12:24 PM
To: vven...@codeaurora.org
Cc: opnfv-tech-discuss@lists.opnfv.org; Alexandru Avadanii
Subject: RE: [opnfv-tech-discuss] [yardstick] yardstick env prepare - chroot
error
Hi
Is there yardstick-image in /home/opnfv
Hi,
Great work, Mark and Fatih, I really like the way you built the verify jobs!
I would like to propose this design for other multiarch projects as well (e.g.
functest, yardstick, dovetail, doctor etc.). We will try to submit some patches
soon.
Congrats to the Storperf team for one of the
Hi,
Since only one of the two nodes is failing this check, this does not look like
an infra issue (internet access to the nodes), but rather a configuration issue.
Is the node with MAC ending in "e8:00" the compute by any chance? Does the
compute have the public network assigned and properly
on master and their counterparts on
stable, this is clearly not what you want ☺
BR,
Alex
From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Thursday, October 19, 2017 3:35 AM
To: Alexandru Avadanii; Trevor Bramwell
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss
Hi,
I am happy to announce we finally submitted the final changes for PDF/IDF
support in Fuel.
We have been using PDF for a few weeks to describe most of the hardware
parameters (IPMI credentials for cluster nodes, network VLANs etc.),
but we were lacking support for dynamic configuration of
Hi, Alec,
If all you want is one commit on the stable branch, you should look at
squashing all commits from master into a single commit on the stable branch.
Alex
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan
Hi,
Michael fixed an important issue for Fuel OVS-DPDK scenario, so we tagged
'opnfv-5.0.1' in Fuel git repo.
Please use this updated tag instead of previous 5.0.0 [1].
[1'] https://git.opnfv.org/fuel/tag/?h=opnfv-5.0.1
BR,
Alex
> -Original Message-
> From: Alexandru Avadanii
/stable-euphrates/submodules/armband/docs/release/userguide/userguide.html
> -Original Message-
> From: Alexandru Avadanii
> Sent: Friday, October 20, 2017 7:38 PM
> To: 'Aric Gardner'
> Cc: 'opnfv-tech-discuss@lists.opnfv.org'; 'svc-armband'; Bob Monkman;
> 'Michail Polenchuk'
Hi,
1. Fuel
a. Functest healthcheck pass [1]
b. Done, see [2]
c. Done, see [2]
d. Done, see [2]
2. Armband
a. Functest healtcheck pass [3]
b. Done, see [4]
c. Done, see [5]
d. Done, see [5]
BR,
Alex
[1]
Hi, Sofia,
Your gerrit URL looks wrong – the should be your Linux Foundation
ID (which is also the gerrit account username).
-gerritssh://@review.opnfv.org:29418/opnfv/container4nfv.git
(fetch)
+gerritssh://yourl...@review.opnfv.org:29418/opnfv/container4nfv.git (fetch)
Also, you
Hi,
Old Fuel (the one used in Danube 3.0) was the only OPNFV release to switch from
`fuel-mirror` to `python-packetary`.
You can take a look at [1] to get an idea on how to use packetary to create
offline mirrors.
You can also install an older version of `fuel-mirror` if you’re familiar with
...@gmail.com]
Sent: Wednesday, April 25, 2018 9:42 PM
To: Nikolas Hermanns; Jonas Bjurel; Stefan Berg K; Daniel Smith; Szilard
Cserey; Michal Skalski; Guo, Ruijing; Fedor Zhadaev; Alexandru Avadanii;
Michail Polenchuk; Guillermo Herrero
Cc: Cristina Pauna
Subject: Cleaning up Fuel @ OPNFV committer rolls
This is to inform the TSC that the Fuel@OPNFV project intends to participate in
the Gambia release.
We intend to follow the traditional release track for select scenarios.
BR,
Alex
This message, including attachments, is CONFIDENTIAL. It may also be privileged
or otherwise protected by law. If
> -Original Message-
> From: Alexandru Avadanii
> Sent: Friday, December 15, 2017 9:44 PM
> To: 'Aric Gardner'
> Cc: 'opnfv-tech-discuss@lists.opnfv.org'; 'svc-armband'; 'Bob Monkman';
> 'Michail Polenchuk'
> Subject: [opnfv-5.1.0] Fuel and Armband Fuel Release Artifact
Fuel PTL.
Any active project committer is allowed to run.
However I would like to nominate Alexandru Avadanii for his extra ordinary
contributions to the project over the last several years.
Voting period is open for one week. Project committers are allowed to vote.
Committers please respond
/release-notes.html
[8]
http://docs.opnfv.org/en/stable-fraser/submodules/armband/docs/release/installation/installation.instruction.html
[9]
http://docs.opnfv.org/en/stable-fraser/submodules/armband/docs/release/userguide/userguide.html
> -Original Message-
> From: Alexandru Avadanii
/installation/installation.instruction.html
> -Original Message-
> From: Alexandru Avadanii
> Sent: Friday, July 14, 2017 9:49 PM
> To: 'Aric Gardner'
> Cc: opnfv-tech-discuss@lists.opnfv.org
> Subject: FW: Fuel and Armband Fuel Danube 3.0 ISOs
>
> Hi,
>
Hi,
One minor observation about encrypted yaml – I succesfully used `eyaml` on
Ubuntu Trusty a while back, so I expect that to work without any issues.
I think the problem was about missing instructions for this (what packages to
install to get `eyaml` on Ubuntu).
BR,
Alex
From:
Hi,
Today we re-enabled ericsson-pod1 as a Fuel CI POD in OPNFV, only by populating
the PDF/IDF correctly.
A big thank you to Dianfeng for helping us fill in the missing data, as well as
Fatih and Aric for their support along the way!
This is the validation we were looking for when we added PDF
Hi,
Actually you can run x86_64 containers on AArch64 just fine (and the other way
around), provided you use the appropiate translation tools, like
qemu-user-static.
See [1], I can't find a guide that explains how to do this step-by-step for
containers, but I'm quite sure it's possible (I think
Hi,
I would like to nominate Guillermo Herrero (Enea) as a committer in Fuel@OPNFV.
I have been in contact with Guillermo and he is willing to take on the role.
Guillermo is one of the main contributors in Armband and Fuel@OPNFV,
and he has been one of the most active and valuable contributors
Hi, Jack,
Thank you for your great contributions and the patience in answering all our
questions!
I wish you the best of luck in your future endeavours!
+2 for Julien as the new PTL.
BR,
Alex
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
Hi, Dan,
Thank you for your contributions and the occasional nightly debugging sessions!
No doubt we will meet again :)
All the best,
Alex
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-
> boun...@lists.opnfv.org] On Behalf Of Dan Radez
Hi,
Intended audience:
- Pharos contributors;
- installer teams;
- lab owners;
There are some APs summarized at the end, if you want to skip to that.
I propose a few changes trying to achieve the following goals:
- prepare for introducing a strict schema validation for PDFs;
- clean up PDF spec
: Saturday, January 27, 2018 11:51 AM
To: Alexandru Avadanii
Cc: Rautakumpu, Mika (Nokia - FI/Espoo); opnfv-tech-discuss@lists.opnfv.org;
Jack Morgan
Subject: Re: [opnfv-tech-discuss] [pharos] [infra] POD Descriptor File
documentation for OPNF Docs hackfest?
Hi Alex,
You have listed all the most
+1
From: opnfv-tech-discuss@lists.opnfv.org
[mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Wednesday, July 11, 2018 10:00 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [gerrit] Allow forge author across projects on
Gerrit
Forge author is
Hi,
I would like to nominate 3 people for TSC. Somehow I feel the statements are
superfluous ☺
I know I’m not doing a great job at praising them here, but that’s not the
point; most of you should have worked with them at some point or another.
1. Name: Tim Rozet
Organization: Red Hat
[mailto:tro...@redhat.com]
Sent: Friday, September 07, 2018 4:36 PM
To: Alexandru Avadanii
Subject: Re: OPNFV TSC Nomination
Hi Alex,
That would be great. Thanks for thinking of me.
>On Fri, Sep 7, 2018, 9:12 AM Alexandru Avadanii
>mailto:alexandru.avada...@enea.com>> wrote:
>Hi, Tim,
>
Hi,
+Joe
Lincoln is right, you could spawn a VM, but it would be emulated without hw
acceleration, so not really useful.
Reserving a single aarch64 node might be limiting though, Armband Fuel requires
at least 6 nodes (1 jump server + 5 cluster nodes) right now.
Not sure what the mininum
Sent: Monday, June 25, 2018 7:16 PM
To: Tim Rozet; Cristina Pauna; Alexandru Avadanii; Bob Monkman; Chigang
(Justin); Xueyifei (Yifei Xue); huangxiangyu
Cc: TECH-DISCUSS OPNFV; opnfv-project-leads; tim.irn...@ericsson.com
Subject: Re: [release][gambia] MS3.1 - June 29
Reminder... this Friday.
On Wed,
Hi,
The purpose of this mail is to notify the OPNFV TSC that the Fuel project
intends to participate in the OPNFV Hunter release.
We intend to follow the traditional track.
BR,
Alex
This message, including attachments, is CONFIDENTIAL. It may also be privileged
or otherwise protected by law.
Hi,
Fuel and Armband 7.0.0 release information:
1. Fuel artifacts:
- git tag [1];
- documentation [3, 4, 5];
2. Armband Fuel artifacts:
- git tag [2];
- documentation [6, 7, 8];
NOTE: Although we release Armband like we did in the previous releases, all
AArch64 specifics are now upstream in
Hi,
I would like to nominate Cristina Pauna (Enea) as a committer in Fuel@OPNFV.
I have been in contact with Cristina and she is willing to take on the role.
Cristina is one of the main contributors in multiple OPNFV projects
and she has been one of the most active and valuable contributors
dules/fuel/docs/release/userguide/userguide.html>
From: Alexandru Avadanii
Sent: Saturday, November 10, 2018 4:44 PM
To: David McBride
Cc: opnfv-tech-discuss@lists.opnfv.org; svc-armband; Bob Monkman
Subject: [opnfv-7.0.0] Fuel and Armband Fuel Release Artifacts
Hi,
Fuel and Armband 7.0.0 relea
Hi,
Fuel release information:
1. Fuel artifacts:
- git tag [1];
- documentation [2, 3, 4];
NOTE: Although we do not release Armband like we did in the previous releases,
all AArch64 specifics are now upstream in OPNFV Fuel as well, so starting with
7.0.0, the Fuel artifacts can be used for
Hi,
Fuel intends to participate in the Iruya release.
BR,
Alex
From: opnfv-tech-discuss@lists.opnfv.org
on behalf of David McBride
Sent: Saturday, September 14, 2019 3:58 AM
To: OLLIVIER Cédric IMT/OLN ; Juvonen, Tomi (Nokia
- FI/Espoo)
Hi, Tomi,
Fuel already supports a dynamic number of compute nodes based on the total
number of nodes in PDF/IDF and assumes the following node definition ordering
in both files:
* the first 3 nodes in PDF/IDF are controller/gateway or opendaylight
roles, depending on the current scenario
Hi,
Fuel release information:
1. Fuel artifacts:
- git tag [1] (available once [5] is merged);
- documentation [2, 3, 4];
NOTE: Although we do not release Armband like we did in the previous releases,
all AArch64 specifics are now upstream in OPNFV Fuel as well, so starting with
7.0.0, the
Hi,
Fuel release information:
1. Fuel artifacts:
- git tag [1];
- documentation [2, 3, 4];
NOTE: Documentation on RTD is not yet available due to RTD webhooks refusing to
trigger new builds for Fuel - I'll follow up with LF on this in a ticket [5].
BR,
Alex
[1]
Hi,
Since we are taking most of the Enea Pharos Lab offline soon, arm-build3 and
arm-build4 will be retired.
I see there are some functest build jobs still occasionally running on
arm-build4 - these should either be disabled or moved to different hosts,
either aarch64 baremetal/VMs or using
83 matches
Mail list logo
