[opnfv-tech-discuss] [Doctor][Releng][Promise][Docs] stepping down

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 regards, Ryota

Re: [opnfv-tech-discuss] [opnfv-tsc] [announce][election] Opening nominations for OPNFV Technical Steering Committee (TSC)

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

Re: [opnfv-tech-discuss] The OPNFV Cloud Native working group proposal is being discussed in the TSC

;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

Re: [opnfv-tech-discuss] OPNFV Release Meeting (ASIA) - IRC Only

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

[opnfv-tech-discuss] OPNFV Hands-on @ ONS Europe

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

Re: [opnfv-tech-discuss] [releng] Stepping down as Releng PTL

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!

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

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

[opnfv-tech-discuss] [doctor] replacement of Doctor PTL for new team formation

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 phase for fault management. We are now maintaining

Re: [opnfv-tech-discuss] Migration to Zoom for OPNFV project calls

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 <opnfv-tech-disc

[opnfv-tech-discuss] [doctor] Migration to Zoom for OPNFV project calls

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] cancel doctor meeting today

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

Re: [opnfv-tech-discuss] [doctor] Stepping down

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

Re: [opnfv-tech-discuss] opnfv gerrit page update

te for day-to-day development". Ryota Mibu <r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>>于2018年1月18日周四 上午12:35写道： Julien, I mean the #2 propose is to add links on top of all pages in gerrit. And by those links, you can go JIRA, Wiki and other pages useful for developer

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

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

Re: [opnfv-tech-discuss] [doctor] new weekly meeting time

s-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) <tomi.juvo...@nokia.com>; Kunzmann, > Gerald <kunzm...@docomolab-euro.com>; >

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

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

Re: [opnfv-tech-discuss] opnfv gerrit page update

boun...@lists.opnfv.org> > [mailto:opnfv-tech-discuss-<mailto:opnfv-tech-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:opn

Re: [opnfv-tech-discuss] [doctor] new weekly meeting time

eded sometimes, but it would be more or less > 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 &g

Re: [opnfv-tech-discuss] [doctor] new weekly meeting time

so bad idea. > > That said, -4 or -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

[opnfv-tech-discuss] [doctor] new weekly meeting time

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.

[opnfv-tech-discuss] opnfv gerrit page update

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

Re: [opnfv-tech-discuss] [releng] Committer list per Releng repository

+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.

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][fraser] MS2 - Test case documentation in the test case database - Nov 17

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

[opnfv-tech-discuss] Canceled: OPNFV Doctor weekly meeting

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

Re: [opnfv-tech-discuss] [Doctor] Integration with VNFM

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

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

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

Re: [opnfv-tech-discuss] [doctor] new meeting time

, and is 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 > Sent

[opnfv-tech-discuss] [doctor] new meeting time

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

Re: [opnfv-tech-discuss] [doctor] zte-virtual3(apex) zte-virtual4(fuel)

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)

[opnfv-tech-discuss] [doctor] Doctor CI PODs in OOL

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

Re: [opnfv-tech-discuss] ##freemail## [doctor] verification job in Python and the package

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(壬生 亮太)

Re: [opnfv-tech-discuss] [opnfv-tech-discussion][availability][doctor]Discussion of HA API with the doctor team

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

Re: [opnfv-tech-discuss] [doctor] about to finalize D1 release

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) <zhangyujun+...@gmail.com>;

Re: [opnfv-tech-discuss] [doctor] about to finalize D1 release

it.opnfv.org/gerrit/#/c/32637/ On Fri, Mar 31, 2017 at 1:08 AM David McBride <dmcbr...@linuxfoundation.org<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

[opnfv-tech-discuss] [doctor] about to finalize D1 release

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

[opnfv-tech-discuss] [doctor] meeting skipped

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

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

to be a regression > in Apex. It should be removed 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...@or

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

your > changes are taken into account since this time > > 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 : >

Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging

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 tickets for tra

Re: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

monitoring / notification framework. 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 <r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>

Re: [opnfv-tech-discuss] [doctor] Further discussion of NFVI / APP monitoring

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

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

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

Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

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

[opnfv-tech-discuss] [joid] ubuntu version for jumphost?

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

[opnfv-tech-discuss] [doctor] CFP planning for OpenStack Summit and ONS

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,

Re: [opnfv-tech-discuss] [joid] ceilometer config bug

ode.net<http://irc.freenode.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 &l

[opnfv-tech-discuss] [joid] ceilometer config bug

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.

Re: [opnfv-tech-discuss] [infra][doctor] experimental trigger not working

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

Re: [opnfv-tech-discuss] Add yamllint in releng

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,

Re: [opnfv-tech-discuss] [Doctor] Resigning from committer role

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:

Re: [opnfv-tech-discuss] [doctor] subtasks created for performance profiler

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]

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

ch-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-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

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

t code (!=0), though. > > https://gerrit.opnfv.org/gerrit/#/c/24399/ > > 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-dis

[opnfv-tech-discuss] [doctor] doctor CI now available

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".

Re: [opnfv-tech-discuss] [doctor][ves][barometer] Metrics and Events Requirements High Level List

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]

Re: [opnfv-tech-discuss] [doctor] aodh vs monasca for alarm notifier

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

Re: [opnfv-tech-discuss] [doctor] question on code refactoring task (DOCTOR-71)

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

Re: [opnfv-tech-discuss] ##freemail## Re: [Doctor] Reset Server State and alarms in general

<tomi.juvo...@nokia.com<mailto:tomi.juvo...@nokia.com>> wrote: Hi, Not 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:

[opnfv-tech-discuss] [Doctor] no meeting today

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

Re: [opnfv-tech-discuss] [Doctor] Reset Server State and alarms in general

cuss-boun...@lists.opnfv.org] On Behalf Of Juvonen, Tomi (Nokia - FI/Espoo) Sent: Tuesday, October 04, 2016 12:30 PM To: Ryota Mibu <r-m...@cq.jp.nec.com<mailto:r-m...@cq.jp.nec.com>>; Yujun Zhang <zhangyujun+...@gmail.com<mailto:zhangyujun+...@gmail.com>>; opnfv-te

[opnfv-tech-discuss] [doctor] security review

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.

Re: [opnfv-tech-discuss] [doctor] How to propose topics for D-release

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

[opnfv-tech-discuss] [doctor] status and remaining work for branch cut

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

Re: [opnfv-tech-discuss] ##freemail## [doctor][fuel] how to modify ceilometer configuration for doctor testing

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

Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: Bertrand Souville

to:opnfv-tech-> > discuss-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-d

Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user guide/installation guide and configuration guide

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: Thursday, July 28, 2016 8

Re: [opnfv-tech-discuss] [OPNFVDOCS][multisite] template for user guide/installation guide and configuration guide

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:opnfv-tech-discuss@