FV started from its launch. I
appreciate you all in the community who spend your precious time and efforts
in/around OPNFV, especially who worked together with me in some project I join.
You can find me either Facebook or LinkdIn. I'll be in the same NFV industry,
so might see you again.
Best
David, all,
I’d like to nominate myself.
Name: Ryota Mibu
Organization: NEC
Statement:
I’ve been contributing OPNFV as a developer and led Doctor project (fault
management and maintenance) until it’s graduation from incubation status.
Even focusing on such limited technical area, there are
;mailto:fuq...@chinamobile.com>; Stephen Wong
mailto:stephen.wo...@huawei.com>>; brian.j.skerry
mailto:brian.j.ske...@intel.com>>; Rossella Sblendido
mailto:rsblend...@suse.com>>; julienjut
mailto:julien...@gmail.com>>; Fatih Degirmenci
mailto:fatih.degirme...@ericsson.co
David, ALL,
As Doctor PTL cap has been transferred to Tomi, I won’t join release meeting
except when I need to proxy Tomi. So, I cannot push my request and am also able
to join the US timezone call in such cases.
In general, release meeting is important to deliver our integrated software
with
Hi Amar and all OPNFV folks,
I'm planning to submit a Hands-on CFP to ONS Europe. Do you think you can join
such session? If I can get good number of speaker, we can extend this session
to workshop (1/2 day) with multiple speakers. And, we also need multiple
engineers to support actual hands-o
Fatih,
I appreciate your enthusiastic leadership and huge contribution in OPNFV CI.
Your reviews are always valuable and thoughtful. We all know your
unsatisfaction comes from your willingness to make things better.
ALL,
In case you are not aware of the PTL vote, here's the link. Vote now!
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEG
Hi Doctor team,
I've decided to step down from Doctor PTL and nominate Tomi Juvonen for new PTL.
This is for new team formation in order to focus on maintenance topic rather
than fault management topic. As Doctor team, we've finished R&D phase for fault
management. We are now maintaining testi
issue? It should be identified whether it’s
common issue or not.
Best,
Ryota
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Monday, March 05, 2018 8:58 PM
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss
Hi Doctors,
Let’s use the Zoom from March 12th.
Seeing the time in PT [1], our room is https://zoom.us/j/2362828999 .
Find more info at https://etherpad.opnfv.org/p/doctor_meetings .
[1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180312T11
BR,
Ryota
From: opnfv-tech-discuss
Hi Doctors,
My apologies for the short notice and no proposal for another meeting chair.
I got the flu and cannot chair todays meeting.
What I want you to know is that we are working CI fix. Last week we change
doctor job definition in releng, especially node label names. Now, we are
waiting
Hi Carlos,
Thank you for all your works in the project and taking polite way in leaving.
Your resignation process is running at https://gerrit.opnfv.org/gerrit/50989 .
Best regards,
Ryota
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On
Subject: ##freemail## Re: [opnfv-tech-discuss] opnfv gerrit page update
Hi Royta,
It's useful. If possible, I suggest to just put a logo to avoid the main page
is too congested.
I completely agree that Gerrit "as the main portal site for day-to-day
development".
Ryota
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEG
ech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota
> Mibu
> Sent: Wednesday, January 17, 2018 8:59 PM
> To: Juvonen, Tomi (Nokia - FI/Espoo) ; Kunzmann,
> Gerald ;
> opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [op
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEG
discuss->
> boun...@lists.opnfv.org<mailto:boun...@lists.opnfv.org>] On Behalf Of Ryota
> Mibu
> Sent: Monday, January 15, 2018 5:57 PM
> To:
> opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
> Subject: [opnfv-tech-discuss] opnfv gerr
special case it happens. Also the usage of
> irc more might be nice if people would keep it open to 24/7 questions and
> answer when around. Otherwise have to stick
> with the mailing list (spam). Gerrit surely works.
>
> Br,
> Tomi
>
> > -Original Message-
>
r -7 would be perfect.
>
> Br,
> Tomi
>
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org
> > [mailto:opnfv-tech-discuss- boun...@lists.opnfv.org] On Behalf Of
> > Kunzmann, Gerald
> > Sent: Tuesday, January 16, 2018 10:58 PM
&
Hi Doctor team,
As I raised this topic in the last weekly meeting, I'd like to shift our weekly
meeting time slot bit earlier. That will be good for participants from Asia.
I've checked other OPNFV meeting and found that we have multiple options for
our new timeslot from -1 hour to -3 hours. D
Hi OPNFV developers,
I'd like to gather comments on the following ideas for our gerrit page update
(https://gerrit.opnfv.org/gerrit/).
1. Logo in gerrit page
Add OPNFV logo in our gerrit page, so that we can easily identify OPNFV
gerrit page among other gerrit pages of other upstream pr
+1
Also we need to consider long term transition. Each repo or sub-team would be
getting bigger then could be independent project/repo eventually. So, it would
be nice to find sub-team lead or key person who is responsible in each repo
along with this list modification. Just two cents though.
Hi David,
Here’s the link to Doctor test case.
http://testresults.opnfv.org/test/api/v1/projects/doctor/cases
We won’t have a new test case in this release cycle.
BR,
Ryota
From: opnfv-project-leads-boun...@lists.opnfv.org
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of Da
BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGI
Hi Ciprian,
Thank you for checking out Doctor project and reaching out us.
In Danube, we officially support OpenStack Congress, but haven’t supported
Vitrage yet. See, our release notes [1]. I’m not a fuel expert, but doctor
driver in Congress may not be enabled in default, as it is not in the
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEG
friendly to people in US.
I've also updated Wiki page.
https://wiki.opnfv.org/display/meetings/Doctor
BR,
Ryota
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota
> Mibu
>
Bryan,
Here's the short version of the slide deck presented by the idea from KDDI Labs:
https://www.slideshare.net/kimw001/kddi-openstack-summit-2016red-hat-nfv-mini-summit
We also have updates presented in OpenStack Summit Boston. You can get slides
and video from the official site:
Hi Doctors,
TSC meeting will be shifted from July 11th, so let's find out our new meeting
time and apply the change from that week (July 10th to 14th).
All team members, please put your preferred meeting time slots here:
http://doodle.com/poll/8s949vxi7xkxk6rq
The time slots are set in U
Wenjuan,
Please go ahead!
Thanks,
Ryota
From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Sent: Monday, June 26, 2017 7:46 PM
To: Mibu Ryota(壬生 亮太)
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: 答复: [opnfv-tech-discuss] [doctor] zte-virtual3(apex) zte-virtual4(fuel)
Hi,
As I
Hi Jose and Functest team,
I'm wondering how we can run experimental jobs with functest in OPNFV CI
pipeline. Could you help me figure out a solution?
There are two problems sharing the same root issue;
1) Current Doctor verify jobs are failing due to "not supported" [1], after
[2] got mer
Hi doctor committers who has access to the Doctor PODs,
As I said yesterday, I pasted quick notes regarding Doctor CI PODs in OOL.
https://etherpad.opnfv.org/p/doctor_ci_pod
Please check and update this page if you touch configuration, so that other can
follow. I reported wrong setup proced
Yujun,
I won’t say no, but concern a broad scope of work as a feature project. For
testing project, that would be find. Let’s see how we can do.
BR,
Ryota
From: Yujun Zhang (ZTE) [mailto:zhangyujun+...@gmail.com]
Sent: Wednesday, April 26, 2017 12:25 PM
To: Mibu Ryota(壬生 亮太)
Cc: TECH-DISCUSS
Hi Fu Qiao,
Yes, I can join and also ask other Doctor members to join during our Doctor
meeting the day before (April 11).
My initial concern is that "Fault in VM" is not in the scope of Doctor, so I'm
not clear whether we can contribute our insights. But, yes, we can join the
discussion at t
David,
I tagged “danube.1.0” on stable/Danube branch of doctor.
BR,
Ryota
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Friday, March 31, 2017 10:56 AM
To: Yujun Zhang (ZTE) ; David McBride
; Sofia Wallin
David McBride
mailto:dmcbr...@linuxfoundation.org>> wrote:
FYI - Doctor release notes link is empty
http://docs.opnfv.org/en/stable-danube/release/release-notes.html
David
On Thu, Mar 30, 2017 at 8:49 AM, Ryota Mibu
mailto:r-m...@cq.jp.nec.com>> wrote:
Hi team,
We have jus
Hi team,
We have just merged our release notes of Doctor.
I suppose there are nothing left for D1 release in Doctor.
We have long backlog list though.
Let me know if I miss something (e.g. bug) ASAP.
By tomorrow, we need to express that we finished D1 activity as Doctor project
by tagging in ou
Hi,
Apologies for the missing notification of the meeting time change today.
We started doctor weekly meeting one hour earlier due to the start of US summer
time.
Let me list items that I want to share within the team.
- The deadline for OPNFV Summit CFP is March 27th, bring your idea in the
once fixed
> and verified in Apex.
>
> Carlos
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of
> morgan.richo...@orange.com
> Sent: 08 March 2017 15:48
> To
me
>
> Last CI run I found was on fuel started at 6:19 jenkins and should not
> include the change but next run should include
> it, wait and see...
>
> /Morgan
>
> Le 06/03/2017 à 01:16, Ryota Mibu a écrit :
> > Jose, Functest team,
> >
> >
> &g
.opnfv.org] On Behalf Of Ryota
> Mibu
> Sent: Wednesday, March 01, 2017 12:34 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging
>
> Hi,
>
>
> As we discussed in doctor meeting today, I created JIRA
Hi,
As we discussed in doctor meeting today, I created JIRA tickets for tracking
status of our debug in each installer. We need to get green lights in doctor
scenario test in functest report. As we may need to track different bugs for
each installer, I created three tickets for each.
Fuel -
ework. Not necessarily
including or not including any of the current component projects; more a
discussion of the "ideal" solution to work towards
Aaron
On Mon, Feb 6, 2017 at 4:00 AM, Ryota Mibu
mailto:r-m...@cq.jp.nec.com>> wrote:
Hi,
Of course, I’m interested in such to
Hi,
Of course, I’m interested in such topic. The problem is I cannot join Barometer
meeting as it would be 2 AM in my time zone… I hope someone can take notes.
Doctor project is still candidate to have such discussion. And I’m open to add
them to our meeting agenda. How about having “Polling v
Hi Gerald and Aric,
Actually, this is miss-configuration of merge jobs. So, other merge jobs could
have the same issue. We need to use 'git-scm' for merge jobs instead of
'git-scm-gerrit' which is for verify jobs.
Best,
Ryota
> -Original Message-
> From: Kunzmann, Gerald via RT [mail
Hi Gerald and Aric,
Actually, this is miss-configuration of merge jobs. So, other merge jobs could
have the same issue. We need to use 'git-scm' for merge jobs instead of
'git-scm-gerrit' which is for verify jobs.
Best,
Ryota
> -Original Message-
> From: Kunzmann, Gerald via RT [mail
Hi joid team,
I know that you guys are working on MAAS 2.0 support [1] and Ubuntu 16.04 [2],
but not sure which version of ubuntu can be used for jumphost now. Could you
advise how we can build pod with latest joid? Should I use trusty + maas 2.0
manual installation?
Note, I'm using '00-maasd
Hi,
As I mentioned, I created an etherpad page to have discussion for our CFPs.
https://etherpad.opnfv.org/p/doctor_openstack_summit_boston_2017
VES demo is also put in this page, although we can post the CFP to ONS.
I encourage you all to post your idea and be a presenter. ;-)
Cheers,
R
enode.net>]
+1.281.736.5150narindergupta2007[skype]
Ubuntu- Linux for human beings | www.ubuntu.com<http://www.ubuntu.com> |
www.canonical.com<http://www.canonical.com>
On Mon, Jan 9, 2017 at 11:21 PM, Ryota Mibu
mailto:r-m...@cq.jp.nec.com>> wrote:
Hi Artur and JOID team,
I've found config bug in ceilometer for aodh even-alarm, while I'm testing
doctor scenario in my joid deployment.
Could you help me fix the bug in upstream? I already posted a patch:
https://review.openstack.org/418202
I also filed the bug.
https://jira.opnfv.
Yujun and Fatih,
Let’s use “silent-start” option for gerrit trigger plugin [1].
I checked gerrit plugin for Jenkins [2,3], but I cannot find how we can make
jenkins not to reset verified status by another solution, although
‘silent-start’ won’t put the link to triggered jenkins job.
I posted
Hi,
Thank you for your effort in developing yamllint job.
I’ve just reviewed your latest patch set. Please check my minor comments in
gerrit.
Once we confirmed that the job works fine, we can use it in other projects.
BR,
Ryota
From: Haojingbo [mailto:haojin...@huawei.com]
Sent: Thursday, D
Tommy,
You've been great from the beginning of this project. I’ve enjoyed working with
you.
As project lead, I’ll inform your resignation from doctor project to TSC at the
end of this year.
Wish you good luck on your new journey.
Best regards and thanks,
Ryota
From: opnfv-tech-discuss-boun
Yujun,
Feel free to COPY the fix version and priority to your sub-tasks, as these
tasks don’t expand scope of the original task which we agreed. We can try to
complete these tasks. If not, just defer when the release cut approaches.
BR,
Ryota
From: Yujun Zhang [mailto:zhangyu...@gmail.com]
S
PM Ryota Mibu
mailto:r-m...@cq.jp.nec.com>> wrote:
Hi,
Let me explain current status in today’s meeting.
BR,
Ryota
From: Carlos Goncalves
[mailto:carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>]
Sent: Monday, December 05, 2016 11:52 AM
To: Yujun Zhang mailto:z
iscuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: 05 December 2016 02:00
To: Ryota Mibu;
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [doctor] doctor CI now available
Nice job!
One comment inline.
On Sun, Dec 4,
We can take care of this in person tomorrow at the Hackfest :-)
>
> Carlos
>
> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota
> Mibu
> Sent: 04 December 2016 08:54
> To: opnfv
Hi,
Doctor CI jobs are now available and I confirmed those returns green lights
with current codes on the master branch.
Reviewers, please check the CI results before merging a patch set. If the CI
jobs were run before Dec 2nd, just trigger CI jobs again by leaving comment
"recheck".
doct
Hi Maryam,
Sounds nice!
Let me list some.
For Doctor, we might need explicit error with threathhold checks (e.g. 10%
packet loss) that can be reported via doctor south bound API [1].
[1]
http://artifacts.opnfv.org/doctor/docs/requirements/index.html#detailed-southbound-interface-specificatio
Yujun,
Well, we don't have much new features in Danube. We need documentation and
testing improvements in Danube. Those are not easy to be mapped in an overview
picture.
We wrote down the release plan while we didn't have JIRA and guidelines at the
early stage of OPNFV. The original plan and
Hi Steve,
? Can you confirm the OPNFV Doctor project did not make any changes to
the aodh v2 API (/V2/alarms) and use it as it is currently defined?
Correct, we use Aodh API as-is.
? I see the aodh alarm notification does not contain a timestamp when the
alarm notification is tra
Yujun,
I agree, I’m open to change language if we have an alternative works fine in
the team.
As far as I know, there is no rule and guideline for code language in OPNFV.
If we consider that we should work closer with OpenStack, we should use python
and tempest.
The separation of testing code
ot DB issue since just sending notifications took same time as changing DB at
the same.
Br,
Tomi
From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>]
Sent: Tuesday, October 04, 2016 3:48 PM
To: Juvonen, Tomi (Nokia - FI/Espoo)
mailto:tomi.juvo...@nokia.c
Hi David and Doctor team,
I’ve just created doctor entry for D release planning according to our release
planning discussion which already completed before the MS1 deadline.
https://wiki.opnfv.org/display/SWREL/Doctor+Release+Plan+for+OPNFV+Danube
BR,
Ryota
From: opnfv-project-leads-boun...@
Hi,
Sorry for the short notice, but we won't have doctor meeting today as some
committer are attending OpenStack Summit Barcelona this week.
BR,
Ryota
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailm
Hi Doctor team,
In order to complete D release planning by MS1(Oct. 25), let's start task
review from next week meeting.
Here's a rough schedule:
Oct 10: all tasks should be registered in JIRA, proposed priority
(Trivial/Minor/Critical/Blocker) and due date (see
https://etherpad.opnfv.org/p/
- FI/Espoo)
Sent: Tuesday, October 04, 2016 12:30 PM
To: Ryota Mibu mailto:r-m...@cq.jp.nec.com>>; Yujun Zhang
mailto:zhangyujun+...@gmail.com>>;
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Suspected SPAM - Re: [opnfv-tech-discuss] [Doct
Hi,
That’s interesting evaluation!
Yes, this should be an important issue.
I doubt that token validation in keystone might take major part of processing
time. If so, we should consider to use keystone trust which can skip the
validation or to use token caches. Tomi, can you try the same evalu
Hi,
I received a security review report for Doctor from Luke Hinds today.
It makes sense and we can change the Flask option easily, although we have to
figure out the way to enhance the sample inspector and monitor in doctor tree.
-
Yujun,
Agree to write guideline for inspector. I guess we may find enhamcements of
existing inspectors (congress and vitrage).
BR,
Ryota
From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: Tuesday, September 13, 2016 9:51 AM
To: Juvonen, Tomi (Nokia - FI/Espoo) ; Souville,
Bertrand ; c
Hi,
To track our activity, we have to use JIRA. Spec review in gerrit could be
additional step for our design discussion. In OpenStack, developers are using
Launchpad (similar to JIRA) as well as gerrit for spec discussion.
Thinking of size and characteristic of Doctors, I prefer to avoid an a
tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun
> Zhang
> Sent: Freitag, 19. August 2016 14:39
> To: Ryota Mibu ; opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [doctor] status and remaining work for
> bran
Hi,
I have good news for you, let's keep doing our best.
[Report]
- Wenjuan rebased open patches, so that we can merge them promptly once we got
a green light in our CI.
- Viktor tested the doctor scenario in a Nokia pod and helped us with
debugging. Now, we got 'OK' (success) in the pod.
Hi,
> If I understand it correctly, the major issue is that by default fuel
> installs ceilometer with no notifiers configured,
> i.e. `- notifier://` while doctor requires a topic setting i.e. `-
> notifier://?topic=alarm.all`
Doctor team is not only one who need this config, but there could
,
Ryota
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Tuesday, August 02, 2016 8:44 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion
for: Bertrand
iscuss-boun...@lists.opnfv.org<mailto:discuss-boun...@lists.opnfv.org>] On
> Behalf Of Ryota Mibu
> Sent: Friday, July 29, 2016 2:51 PM
> To:
> opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
> Subject: [opnfv-tech-discuss] [doctor] Nominati
Hi Doctor committers,
I'd like to nominate Bertrand Souville to Doctor committer.
He is so active in checking Doctor CI tests and patch reviews which are huge
helps for us, as we are tackling CI fixes. His +2 will accelerate our
development and debugging of Doctor tests.
https://gerrit.op
d.
Thank you for letting us know there is an issue in Jenkins configuration for
doc build.
Thanks
Bin
From:
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Thu
/Configurartion+guide, the
folder name is configguide.
Really confused which one is correct
Best Regards
Chaoyi Huang (joehuang)
From: Ryota Mibu [r-m...@cq.jp.nec.com]
Sent: 29 July 2016 11:52
To: joehuang;
opnfv-tech-discuss@lists.opnfv.org<mailto:op
nfigguide" which is for Releasse B to
"configurationguide" in Release C?
Best Regards
Chaoyi Huang (joehuang)
____
From: Ryota Mibu [r-m...@cq.jp.nec.com]
Sent: 22 July 2016 20:10
To: joehuang;
opnfv-tech-discuss@lists.opnfv.org<mailto:opnf
Hi,
Kvm4nfv is not included in the target projects for this artifact cleanup.
https://git.opnfv.org/cgit/releng/tree/utils/retention_script.sh#n20
I don't know how they built and upload rpms to the artifact server in B release
cycle.
Cheers,
Ryota
> -Original Message-
> From: op
Hi,
We updated structure and templates in opnfvdocs.
You can find latest templates in opnfvdocs;
opnfvdocs/docs/configurationguide/configuration.options.render.rst
opnfvdocs/docs/configurationguide/scenario.description.rst
Also, please check https://wiki.opnfv.org/display/DOC/Documenta
iscuss] [RELENG] Vote to make Trevor a submitter on
> releng.
>
> +1
>
> -Original Message-
> From: Aric Gardner [mailto:agard...@linuxfoundation.org]
> Sent: Thursday, July 21, 2016 20:05 PM
> To: OPNFV Tech
> Cc: Fatih Degirmenci; Jose Lausuch; Meimei; R
83 matches
Mail list logo
