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

[Kunzmann, Gerald]

+1

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Carlos 
Goncalves
Sent: Freitag, 29. Juli 2016 13:57
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion 
for: Bertrand Souville

+1!

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 29 July 2016 13:51
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Nomination of Committer promotion for: 
Bertrand Souville

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.opnfv.org/gerrit/#/q/r:souville%2540docomolab-euro.com

Please reply "+1" if you support his promotion.


Thanks,
Ryota

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

Re: [opnfv-tech-discuss] [Orchestra] new project proposal

[Kunzmann, Gerald]

Hi Guiseppe,

Thanks for your proposal.
I assume you meant “present it during the next tech discuss call” on Thursday, 
right?   ☺

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Carella, 
Giuseppe
Sent: Montag, 1. August 2016 23:09
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Michael Pauls 
Subject: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi all,

please find on the wiki [1] a new project proposal, named Orchestra, having as 
main objective the integration between Open Baton and OPNFV. We’ll be available 
to present it during the next TSC call.

Get in touch if you are interested in getting involved.

[1] https://wiki.opnfv.org/display/PROJ/Orchestra

Cheers,
Giuseppe

Join us at the IEEE 5G Week in November in Berlin (http://www.berlin5gweek.org/)

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

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

[Kunzmann, Gerald]

Hi all,

+1 to go for the least risky approach for Colorado.

For D release and after the Fuel bug is fixed, we can optimize and change to a 
different approach.

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: Dienstag, 16. August 2016 07:33
To: Yujun Zhang ; TECH-DISCUSS OPNFV 

Subject: 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 be other 
users who need this config in order to use/provide event-alarm. Actually, fuel 
seems to install aodh-listener, which is for event-alarm evaluation and listens 
bus with topic=alarm.all, in default. Fuel, however, doesn't configure 
event_pipeline.yaml of ceilometer correctly, so aodh-listener would be hanging 
a silent message bus. This is certainly a bug in fuel.

Apex had the same issue, but they already fixed it.

In ceilometer project, we had a discussion that we shouldn't send notification 
to aodh by setting this config *in default*, as it is different service, 
although is in the same telemetry umbrella. And, we left this config to an 
integrator and a packager.

> Since there is no perfect way to resolve it, I would propose we choose 
> a less risky way at the release window. What about we modify the 
> configuration on the fly in doctor testing script and restore to origin when 
> the test is done. This could be considered as part of the preparation of 
> testing environment.

+1

It should be easier to land.


Best,
Ryota

> -Original Message-
> From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
> Sent: Tuesday, August 16, 2016 11:51 AM
> To: TECH-DISCUSS OPNFV
> Cc: Mibu Ryota(壬生 亮太); carlos.goncal...@neclab.eu; 
> dong.wenj...@zte.com.cn
> Subject: ##freemail## [doctor][fuel] how to modify ceilometer 
> configuration for doctor testing
> 
> There has been quite a lot of discussion on how to deploy doctor test with 
> fuel installer [1] [2].
> 
> 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`
> 
> 
> On both sides, we agree that the configuration required for one 
> scenario should not affect other scenarios. And we almost agree that 
> it can hardly be done if the scenarios requires different configuration. We 
> need either modify the configuration with a scenario based plugin 
> (fuel-doctor-plugin) [3] or the affected service (ceilometer).
> 
> Since there is no perfect way to resolve it, I would propose we choose 
> a less risky way at the release window. What about we modify the 
> configuration on the fly in doctor testing script and restore to origin when 
> the test is done. This could be considered as part of the preparation of 
> testing environment.
> 
> We may leave the dispute on how to handle it gracefully and safely to next 
> release. What do you guys think?
> 
> [1] https://gerrit.opnfv.org/gerrit/#/c/18285/
> [2] https://jira.opnfv.org/browse/FUEL-159
> [3] https://github.com/openzero-zte/fuel-plugin-doctor
> 

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

[opnfv-tech-discuss] [Promise] Agenda for today's meeting

[Kunzmann, Gerald]

Dear all,

Today's Promise meeting will take place at 5pm UTC.

The tentative agenda is (https://wiki.opnfv.org/display/meetings/Promise) :


1.   Colorado release status (15 min)

-  Status of Promise Colorado work

-  Promise documentation (PROMISE-78)

-  Promise installation (FUEL-52)

-  Stable branch cut



2.   Blazar (20 min)

-  Presentation by HPE on planned steps for Blazar


3.   (tentative) Orchestra project (5 min)

-  Introduction to Orchestra project with focus on relation with 
Promise project


Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht München, HRB 132976

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

Re: [opnfv-tech-discuss] [Promise] Agenda for today's meeting at 4pm UTC

[Kunzmann, Gerald]

Sorry, I meant 4pm UTC, 18:00 CET:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=8&day=18&hour=16&min=0&sec=0&p1=37&p2=64

Sorry for any confusion caused.

Gerald

From: Kunzmann, Gerald
Sent: Donnerstag, 18. August 2016 12:35
To: 'TECH-DISCUSS OPNFV' ; 'Arturo Martin 
De Nicolas' ; 
'rchund...@clearpathnet.com' ; 
'serge.mann...@sprint.com' ; 'Carella, Giuseppe' 

Cc: Ashiq Khan ; 'Ryota Mibu' ; 
Carlos Goncalves (carlos.goncal...@neclab.eu) 
Subject: [Promise] Agenda for today's meeting

Dear all,

Today's Promise meeting will take place at 5pm UTC.

The tentative agenda is (https://wiki.opnfv.org/display/meetings/Promise) :


1.   Colorado release status (15 min)

-  Status of Promise Colorado work

-  Promise documentation (PROMISE-78)

-  Promise installation (FUEL-52)

-  Stable branch cut



2.   Blazar (20 min)

-  Presentation by HPE on planned steps for Blazar


3.   (tentative) Orchestra project (5 min)

-  Introduction to Orchestra project with focus on relation with 
Promise project


Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht München, HRB 132976

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA process status report

[Kunzmann, Gerald]

Hi David,

What about tasks that a project is not planning to fix in Colorado, nor D 
release, but wants to keep the task as a reminder for a future release, i.e. 
the fix version is not clear yet? In Doctor and Promise we had left the 
“fixVersion” field empty for such cases. Which would be the recommended 
“fixVersion” version for such cases?

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Donnerstag, 18. August 2016 20:51
To: Beierl, Mark 
Cc: opnfv-project-le...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA 
process status report

Yes, all tasks, including sub-tasks.  Thanks.

David

On Thu, Aug 18, 2016 at 11:30 AM, Beierl, Mark 
mailto:mark.bei...@emc.com>> wrote:
Hey, David.

Are you asking that all subtasks also be assigned to a version when you are 
doing your check for Unassigned Issues found?  I only track fix version to the 
story level as subtasks are assigned to the story and it has a fix version.

Regards,
Mark

Mark Beierl | Advisory Solutions Architect
Communication & Media Cloud – CTO Office
EMC Federation
+1 (613) 314-8106
@MarkBeierl

On Aug 18, 2016, at 1:57 PM, David McBride 
mailto:dmcbr...@linuxfoundation.org>> wrote:

Team,

As you know, I've been asking PTLs to update their JIRA projects to improve 
accuracy and to enable use of JIRA as a project management tool.  Note that 
these updates will also improve the accuracy and relevance of JIRA reports 
produced by Bitergia.

Essentially, I'm asking the team to follow four basic principles:

  1.  All JIRA issues must be assigned to a common version string, using the 
"fix version" field.
  2.  Commit messages must include a reference to the issue ID.
  3.  JIRA issue status should be updated whenever the status changes.
  4.  All JIRA issues assigned to a particular release must either be closed, 
or pushed out to a future release (i.e. update "fix version") by the release 
date.
In order to track progress for 1 and 3, I've put together a script that pulls 
data from JIRA.  The first report is attached.  Please locate your project in 
the report and make plans to resolve any issues that are identified.

Notes on the report:

  *   "no versions" - indicates that the admin page contains no version strings 
for selection in the "fix version" field.

 *   To fix this, add the common version strings to the "Versions" section 
on the project admin page.

  *   "Version list NOT correct" - the project contains version strings, but is 
missing one or more of the common version strings.

 *   All projects must use the common set of version strings.

  *   "Unassigned issues found: [list]" - the project has issues where the "fix 
version" field is empty.

 *   Remember, all issues must be assignee to a version, using the "fix 
version" field.
 *   About 85% of the projects have unassigned issues.
 *   There are two solutions to this: (a) educate your project team to set 
the field when they create the ticket; (b) when you conduct a bug scrub, or 
triage, search your JIRA project for issues that are unassigned and update them.
Kudos!  Note that the Domino, Models, and IPv6 projects all have the correct 
version list and no unassigned issues.  An inspiration to us all :)

Final note:  this script is new, so it wouldn't surprise me if there are 
errors.  If you see something that doesn't make sense, please let me know.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
<08182016_opnfv_jira.txt>___
opnfv-project-leads mailing list
opnfv-project-le...@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads




--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Can we wait for the next run in the official CI? If we are lucky, we already 
get the green light. Then, we could immediately merge the other patches.
If there is no green light in the next CI run and we don’t see any issue with 
the current code, then let’s be confident to merge the open patches.

Gerald

From: opnfv-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 branch 
cut

I think we should be confident to merge the open patches since they are tested 
locally and also passed Viktor's test.

Furthermore, the patches in queue are split properly, it would not be too 
difficult to revert in case there is any problem.
--
Yujun

On Fri, Aug 19, 2016 at 7:28 PM Ryota Mibu 
mailto:r-m...@cq.jp.nec.com>> wrote:
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. :)


[Remaining Tasks]

 1. Merge open patches for congress integration and fuel support

 2. Update documents accordingly if we merged these patches

 3. Request helpdesk to cut branch


[Question]

CI jobs are not so stable these days. Waiting a green light in official CI 
might take days. Then we don't have enough time to work for open patches right 
now. SO, I propose to take the OK reported in Viktor's test in Nokia pod as our 
green light, and start to merge open patches. What do you think?


Thanks,
Ryota

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

[opnfv-tech-discuss] [opnfvdocs][doctor] Issue with "Adjust the structure of doctor/userguide dir" - any idea?

[Kunzmann, Gerald]

Dear Opnfvdocs-Team,

We have an issue with this patch: https://gerrit.opnfv.org/gerrit/#/c/18805/
Please refer to the history to see which things we had already tried to solve 
the issue with the figure numbering and the figure not showing.

Does anyone have an idea what is the reason? Maybe an issue with how opnfvdocs 
building scripts handle includes and figures?

Best regards,
Gerald

-Original Message-
From: Gerrit Code Review [mailto:ger...@opnfv.org] 
Sent: Donnerstag, 25. August 2016 08:01
To: Yuanzhen Li 
Cc: Ryota Mibu ; Souville, Bertrand 
; Carlos Goncalves ; 
jenkins-ci ; Kunzmann, Gerald 

Subject: Change in doctor[master]: Adjust the structure of doctor/userguide dir

>From Yujun Zhang :

Yujun Zhang has posted comments on this change.

Change subject: Adjust the structure of doctor/userguide dir 
..


Patch Set 14:

Sorry, it's still not working. The only way I could suggest now is to check how 
opnfvdocs building script handles include and figure.

--
To view, visit https://gerrit.opnfv.org/gerrit/18805
To unsubscribe, visit https://gerrit.opnfv.org/gerrit/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie526d921dabbfa3b7a9c95f1705390c2eef53998
Gerrit-PatchSet: 14
Gerrit-Project: doctor
Gerrit-Branch: master
Gerrit-Owner: Yuanzhen Li 
Gerrit-Reviewer: Bertrand Souville 
Gerrit-Reviewer: Carlos Goncalves 
Gerrit-Reviewer: Gerald Kunzmann 
Gerrit-Reviewer: Ryota Mibu 
Gerrit-Reviewer: Yuanzhen Li 
Gerrit-Reviewer: Yujun Zhang 
Gerrit-Reviewer: jenkins-ci 
Gerrit-HasComments: No
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OPNFV D-release naming

[Kunzmann, Gerald]

Danube +1:
“the river passes through or touches the borders of 10 countries. Its drainage 
basin extends into nine more.” https://en.wikipedia.org/wiki/Danube

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Juraj Linkes 
-X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)
Sent: Montag, 29. August 2016 09:20
To: Raymond Paik ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV D-release naming

Danube +1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Monday, 29 August, 2016 7:03
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] OPNFV D-release naming

All,

As discussed on the last TSC call, I'd like to get the process started for the 
D-release naming.

A quick reminder that we have a river theme for OPNFV releases and our first 3 
release names are Arno (Europe), Brahmaputra (Asia), and Colorado (Americas).  
I'd like to continue the tradition of going to different 
continents/geographies, so we could venture into Africa or return to Europe...

Can you send me your top 2-3 nominations (at most) in the following format by 
5pm Pacific Time on September 2nd?  After I collect all the nominations, I'll 
send out a SurveyMonkey poll so the community can pick the winner

Format: River name (locations)
For example,
·  Danube (Austria, Germany, Hungary, etc.)
·  Draa (Algeria, Morocco)
·  etc.

Thanks,

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA process status report

[Kunzmann, Gerald]

Hi Chris, all,

What about introducing another label "non-release" and allowing (as David had 
mentioned in his other email) the use of alternative label for specific 
"non-release related" topics.
I understand David's concern that we should be able to identify issues that are 
not assigned with a fixVersion as someone had forgotten to do so vs. issues 
that are on purpose not assigned to the current release.
@Marc: could we update the Jira such that the fixVersion is a "mandatory" field 
when creating a new issue?

Best regards,
Gerald



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Dienstag, 30. August 2016 10:31
To: Christopher Price 
Cc: opnfv-project-le...@lists.opnfv.org; TECH-DISCUSS OPNFV 

Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA 
process status report

My previous experience was to track only stories and bugs against a release. 
Sub-tasks are always associated with a specific story and tracked that way.   
As for tasks, those usually indicate out of band (ie: non release) work that is 
to be done.

Just my $0.02...

Regards,
Mark

On Aug 30, 2016, at 10:06, Christopher Price 
mailto:chrispric...@gmail.com>> wrote:
Hi David,

I'm getting a little lost in the thread now.

Is there a perceived issue around having tasks that are not planned as part of 
a specific release?
It may even be that there are tasks that are being tracked in Jira that are not 
intended to be tracked to a release process.  (Lab tickets, wiki updates 
etc...) I'm not sure we should be terribly concerned with % of tasks intended 
to be completed as part of a release process or not.  We may also have projects 
that choose not to participate in a release at this stage that wish to use Jira 
which would further impact that % figure.
Assigning something to "future release" indicates it does not have a desired 
timeline which may not be the case, I don't know that is the right way to 
address this.

Maybe we should focus our release metrics on tasks that are intended to be 
completed as part of a release activity.  Leave other "non-release related" 
Jira tasks out of those metrics.

/ Chris

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Date: Monday 29 August 2016 at 20:46
To: "morgan.richo...@orange.com" 
mailto:morgan.richo...@orange.com>>
Cc: opnfv-project-leads 
mailto:opnfv-project-le...@lists.opnfv.org>>,
 TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [release][jira] JIRA process status report

Hi Morgan,

Sorry - I should have been more clear.  When I say "assigned", I mean "assigned 
to a release" (i.e. the "fix version" field is NOT empty).

David

On Mon, Aug 29, 2016 at 4:04 AM, 
mailto:morgan.richo...@orange.com>> wrote:
Hi,

I am a bit surprised by the results.

I reviewed the FUNCTEST JIRA.
As far as I can read I found only 14 JIRAs non assigned, all the others are 
assigned.
For me, "assigned" means there is one person in the Assignee field, am I wrong?

the non assigned JIRA corresponded to:
- D release
- Epic: generic topic for which we do not necessarily assign someone, e.g. 
FUNCTEST-88 is the EPIC linked to documentation. JIRA tasks/bugs are created 
under this EPIC, all these JIRAs are assigned the umbrella EPIC was not.
As Epic does not appear in board/backlogs, I forgot to close some.

/Morgan


Le 26/08/2016 à 22:59, David McBride a écrit :
Team,

Some updates for this week's report:

  1.  My script will how automatically add any missing versions to your 
project, so you no longer need to worry about that task.  To be clear, the 
script simply makes the version strings available for selection in your 
project.  It does not assign any issues to those versions.
  2.  The script also now determines the ratio of unresolved issues to total 
issues assigned to the current release (i.e. Colorado 1.0)
Observations:
? The percentage of projects with no unassigned issues improved 
slightly from 15% to 25% since my first report.
oHowever, this still means that 3/4 of OPNFV projects still have unassigned 
issues.  We cannot do meaningful analysis of progress without knowing which 
version issues are assigned.
oNote that all projects now have the "Future Release" version string.  So, 
if you do not plan to resolve an issue for the current release, and you aren't 
sure that you will do it in the next release, then assign it to "Future 
Release".
? We are less than one month out from the Colorado 1.0 release, yet 
there are a startling large number of issues assigned to the release that are 
unresolved.
oPlease make sure that you are updating the status of your JIRA issues 
whenever there is a relevant change.  Don't let fixed issues remain reported as 
unresolved in JIRA.  This creates a lot of ambiguity when

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[Kunzmann, Gerald]

Hi David, all,

My 2 cent on your question:

The question is: does it make sense for requirements projects to participate in 
releases until they're ready to deliver code?

Requirement projects are an essential part of OPNFV and some may even do all 
development in upstream, i.e. there might even be no code within OPNFV except 
test cases. Thus, I support having the requirement documents as part of the 
release documentation.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Mittwoch, 31. August 2016 09:42
To: Daniel Smith ; David McBride 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi Daniel, hi all,

Thank you Daniel for stating the advantages for the requirements projects and 
for OPNFV. From my point of view it is important for projects which are 
currently in the “requirements phase” to be represented in an OPNFV release:


-  We are in the process of reaching out to the OpenStack community 
based on our document. Making the requirements document an official part of an 
OPNFV release helps us in doing that by having an “official backing” of OPNFV 
(we are an OPNFV project after all)

-  It shows to the outside world that projects are active in all phases 
(requirements phase), supporting the overall perception of OPNFV

-  It gives the project members the feeling of contributing to OPNFV


I had some discussions with Chris and Sofia on this during the OPNFV summit. 
Back then the proposal was to include our requirements document in the 
“document library” under a section such as “requirements projects”. This could 
be a simple link – just as we have it right now on our project wiki.

As David pointed out, there is some overhead involved for the project, but I 
believe the benefits outweigh the overhead.

Looking forward to discussing with you in today’s docs meeting.

Best regards
Georg

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Daniel Smith
Sent: Tuesday, August 30, 2016 11:44 PM
To: David McBride
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hey All.

I spoke with Sofia as well about this and presented our NetReady situation. We 
have a document that covers what we wanted to cover for Phase 1 (targeting C 
release) of the NetReady Requirements Project.   We now want to stop internally 
editing it and release it for comment – and the thinking is that, since we have 
built the document in gerrit and based on DOCS formatting guidelines, was the 
vehicle to provide the following in terms of the work that the team did:


-Allow for the completion and publishing of the Project Goals Phase 1 
targets (in line with agreed principles when the project  was approved/started) 
– Phase2,3,4 as outlined are targeted for subsequent releases as documented

-Allow for the distribution of the finished product to external (non 
commiter/contributer groups) -  is it realistic to think that someone from 
Openstack (whom the requirements are destined for) will look at the RST line 
format in our gerrit repository to find our documentation? (rather than in the 
released docs page/artifact)?   Or perhaps a different way of looking at it 
would be to ask, how do we move the finished requirements document for C 
release to a platform to be viewed and commented (i.e JIRA for D release for 
review or in gerrit) going forward

-Allows us to tag and timestamp the work (and thus the evolution) of 
the work the team is doing.  Provides start and stop points to coordinate work 
for the team (goal/endpoints).

-Allows all projects to feel that they are contributing to a finished 
release product

o   Further to that maybe this plays into the idea of “release participation” 
discussion.


At any rate, I thought that Sofia’s response of there would be a 
../release/Colorado/docs/RequirementProcject page in the final release that 
would point to the links that requirements projects delivered and that made 
sense to me.


In the end do as you see fit of course, I would wonder about how requirements 
projects are to gain inclusiveness in releases and how that affects the ability 
to trace back to “why did we make this code” when that comes time – since that 
backstory would have to be ported at that point.

Thank you all for the responses.
Daniel


From: David McBride 
[mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, August 30, 2016 2:25 PM
To: Daniel Smith mailto:daniel.sm...@ericsson.com>>
Cc: Sofia Wallin mailto:sofia.wal...@ericsson.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentati

Re: [opnfv-tech-discuss] opnfv.org is not resolving

[Kunzmann, Gerald]

Hi Bryan,

Have checked www, wiki and jira. Seems to be fine on my side.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Mittwoch, 31. August 2016 19:46
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] opnfv.org is not resolving

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

Thanks,
Bryan Sullivan | AT&T

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

[opnfv-tech-discuss] [Promise] Extra-ordinary meeting on Sept 8th 6am PST / 3pm CEST / 10pm JST

[Kunzmann, Gerald]

Dear Promise team,

As discussed during today's call, I'd like to propose an extra-ordinary call 
next week on Sept 8th at 22:00 JST / 15:00 CEST / 6am PST, where all of us 
could join.

Muroi-san (NTT) plans to present a PoC implementation based on the idea we had 
discussed in the Berlin Summit.
It would be great if all Promise team could make it for this call.

I will send out the meeting invite shortly.

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht München, HRB 132976

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

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Hi Madhu, all,

Find attached a commented version of the user story. I believe we need to do 
further changes to make it read more like a user story instead of specific 
detailed requirements. I am not sure defining requirements would be accepted by 
the PWG.

Looking forward to your feedback.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kashyap, Madhu
Sent: Donnerstag, 1. September 2016 20:19
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Gangur, Hrushikesh ; Thulasi, Arun 

Subject: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi,

As discussed during the call, attached is the capacity management user story 
with my edits. Please review and  provide comments. Also think about the 
granularity of the scope the reservation request.

Thanks
-Madhu


Capacity_Management_User_Story-MK-GK.docx
Description: Capacity_Management_User_Story-MK-GK.docx
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Dear all,

Sorry for the delay, I had been on a 2 week vacation.
Attached a new version addressing, amongst others, Arturo's comments.

@Madhu: Can you try to finalize the document and input it to the next meeting 
of the PWG?

Best regards,
Gerald

From: Gangur, Hrushikesh [mailto:hrushikesh.gan...@hpe.com]
Sent: Dienstag, 13. September 2016 20:37
To: Kashyap, Madhu ; Arturo Martin De Nicolas 
; Kunzmann, Gerald 
; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 

Subject: RE: [Promise]Capacity Management User Story

Madhu - looks good and see my comments with emphasis on VNFD being a primary 
source of RUR elements.

From: Kashyap, Madhu
Sent: Tuesday, September 13, 2016 11:01 AM
To: Arturo Martin De Nicolas ; Kunzmann, 
Gerald ; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 
; Gangur, Hrushikesh 
Subject: RE: [Promise]Capacity Management User Story

Hi,

I have  edited the document to reflect the scope of the RUR. Please review and 
comment. Also added a few comments.
Arturo, I have not addressed your comments. Perhaps Gerald can shed some light 
on your comments.

Best Regards
-Madhu

From: Arturo Martin De Nicolas [mailto:arturo.martin-de-nico...@ericsson.com]
Sent: Thursday, September 08, 2016 1:14 AM
To: Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; Kashyap, 
Madhu mailto:madhu.kash...@hpe.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Hi Madhu, Gerald, all.

Please, see some comments from my side.

Best regards,
Arturo



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 Kunzmann, 
Gerald
Sent: Friday, September 02, 2016 12:06 PM
To: Kashyap, Madhu; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand; Thulasi, Arun; Gangur, Hrushikesh
Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi Madhu, all,

Find attached a commented version of the user story. I believe we need to do 
further changes to make it read more like a user story instead of specific 
detailed requirements. I am not sure defining requirements would be accepted by 
the PWG.

Looking forward to your feedback.

Best regards,
Gerald

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 Kashyap, Madhu
Sent: Donnerstag, 1. September 2016 20:19
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>; Thulasi, Arun 
mailto:arun.thul...@hpe.com>>
Subject: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi,

As discussed during the call, attached is the capacity management user story 
with my edits. Please review and  provide comments. Also think about the 
granularity of the scope the reservation request.

Thanks
-Madhu


Capacity_Management_User_Story-MK-GK-AMN-HJG-GK.DOCX
Description: Capacity_Management_User_Story-MK-GK-AMN-HJG-GK.DOCX
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Dear all,

I have had the chance to discuss this document with Arturo in today's Promise 
call and I have updated the document based on his comments - see attachment.

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Dienstag, 20. September 2016 17:51
To: 'Gangur, Hrushikesh' ; Kashyap, Madhu 
; Arturo Martin De Nicolas 
; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 
; Ashiq Khan 
Subject: RE: [Promise]Capacity Management User Story

Dear all,

Sorry for the delay, I had been on a 2 week vacation.
Attached a new version addressing, amongst others, Arturo's comments.

@Madhu: Can you try to finalize the document and input it to the next meeting 
of the PWG?

Best regards,
Gerald

From: Gangur, Hrushikesh [mailto:hrushikesh.gan...@hpe.com]
Sent: Dienstag, 13. September 2016 20:37
To: Kashyap, Madhu mailto:madhu.kash...@hpe.com>>; 
Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Madhu - looks good and see my comments with emphasis on VNFD being a primary 
source of RUR elements.

From: Kashyap, Madhu
Sent: Tuesday, September 13, 2016 11:01 AM
To: Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Hi,

I have  edited the document to reflect the scope of the RUR. Please review and 
comment. Also added a few comments.
Arturo, I have not addressed your comments. Perhaps Gerald can shed some light 
on your comments.

Best Regards
-Madhu

From: Arturo Martin De Nicolas [mailto:arturo.martin-de-nico...@ericsson.com]
Sent: Thursday, September 08, 2016 1:14 AM
To: Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; Kashyap, 
Madhu mailto:madhu.kash...@hpe.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Hi Madhu, Gerald, all.

Please, see some comments from my side.

Best regards,
Arturo



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 Kunzmann, 
Gerald
Sent: Friday, September 02, 2016 12:06 PM
To: Kashyap, Madhu; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand; Thulasi, Arun; Gangur, Hrushikesh
Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi Madhu, all,

Find attached a commented version of the user story. I believe we need to do 
further changes to make it read more like a user story instead of specific 
detailed requirements. I am not sure defining requirements would be accepted by 
the PWG.

Looking forward to your feedback.

Best regards,
Gerald

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 Kashyap, Madhu
Sent: Donnerstag, 1. September 2016 20:19
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>; Thulasi, Arun 
mailto:arun.thul...@hpe.com>>
Subject: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi,

As discussed during the call, attached is the capacity management user story 
with my edits. Please review and  provide comments. Also think about the 
granularity of the scope the reservation request.

Thanks
-Madhu


Capacity_Management_User_Story-MK-GK-AMN-HJG-GK2.docx
Description: Capacity_Management_User_Story-MK-GK-AMN-HJG-GK2.docx
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Hi Madhu, all,

Thanks for the updated version based on the PWG discussions.

My comments:

-  I would not use the term "best-effort" for the reservation requests 
as we also would like to get a guarantee on the requested aggregated resources.

o   What about the terms "discrete" and "aggregate"?

o   Alternatively, introduce two levels of granularity "discrete" / "aggregate" 
 and in addition introduce two levels of "confidence", i.e. "guaranteed" vs 
"planned (best-effort)", where you can indicate a) that you want to do a 
reservation to have a guaranteed access to the resources  or b) you inform the 
CSP about the planned usage of resources such that the CSP can improve his 
capacity mgmt..

?  Should we distinguish between a resource reservation request (RRR) and a 
planned resource usage notification (RUN)?

o

-  I am not sure about the term "prescribed"; would you use it when 
talking about the VNFD   or did you mean  s/prescribed/described/?

Best regards,
Gerald

From: Kashyap, Madhu [mailto:madhu.kash...@hpe.com]
Sent: Mittwoch, 28. September 2016 20:37
To: Kunzmann, Gerald ; Gangur, Hrushikesh 
; Arturo Martin De Nicolas 
; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 
; Ashiq Khan 
Subject: RE: [Promise]Capacity Management User Story

Hi Gerald and all,

Based on the call from a couple weeks ago, I have made some changes to reflect 
what we discussed.

The main point is that there are two kinds of reservation requests:

1.   Guaranteed - this is based on discrete, specific requests as described 
in the VNFD

2.   Best-effort - these are requests based on aggregate resources such as 
"give me 60 vCPUs, 240 Gig RAM, 600 GIG disk etc."
Please review the attached doc in detail and provide feedback.

Let's try to close on this soon so we can provide the reviews back to PWG.

Best regards
-Madhu

From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com]
Sent: Thursday, September 22, 2016 2:47 AM
To: Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>; Kashyap, Madhu 
mailto:madhu.kash...@hpe.com>>; Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Ashiq Khan 
mailto:k...@nttdocomo.com>>
Subject: RE: [Promise]Capacity Management User Story

Dear all,

I have had the chance to discuss this document with Arturo in today's Promise 
call and I have updated the document based on his comments - see attachment.

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Dienstag, 20. September 2016 17:51
To: 'Gangur, Hrushikesh' 
mailto:hrushikesh.gan...@hpe.com>>; Kashyap, Madhu 
mailto:madhu.kash...@hpe.com>>; Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Ashiq Khan 
mailto:k...@nttdocomo.com>>
Subject: RE: [Promise]Capacity Management User Story

Dear all,

Sorry for the delay, I had been on a 2 week vacation.
Attached a new version addressing, amongst others, Arturo's comments.

@Madhu: Can you try to finalize the document and input it to the next meeting 
of the PWG?

Best regards,
Gerald

From: Gangur, Hrushikesh [mailto:hrushikesh.gan...@hpe.com]
Sent: Dienstag, 13. September 2016 20:37
To: Kashyap, Madhu mailto:madhu.kash...@hpe.com>>; 
Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Madhu - looks good and see my comments with emphasis on VNFD being a primary 
source of RUR elements.

From: Kashyap, Madhu
Sent: Tuesday, September 13, 2016 11:01 AM
To: Arturo Martin De Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>
Subject: RE: [Promise]Capacity Management User Story

Hi,

I have  edited the document to reflect the scope of the RUR. Please review and 
comment. Also added a few comments.
Arturo, I have not addressed your c

Re: [opnfv-tech-discuss] [doctor] figure number missing in document

[Kunzmann, Gerald]

Hi Yujun,

Thanks for reporting. I can confirm the issue also in my browser.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: Donnerstag, 29. September 2016 08:50
To: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [doctor] figure number missing in document

I though we have already resolved this issue in [1]. But it seems some figure 
numbers are missing in the document[2]. There should be Figure.X before the 
caption under the figure.

[Screen Shot 2016-09-29 at 2.46.19 PM.png]
Is it only an issue in my browser or common to all?

[1] https://gerrit.opnfv.org/gerrit/#/c/18805/
[2] http://artifacts.opnfv.org/doctor/docs/index.html#figure1

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

Re: [opnfv-tech-discuss] [doctor] [opnfvdocs] figure number missing in document

[Kunzmann, Gerald]

There is an option (from Sphinx 1.3) that we may need to set to TRUE to enable 
figure numbering:

numfig
If true, figures, tables and code-blocks are automatically numbered if they 
have a caption. At same time, the numref role is enabled. For now, it works 
only with the HTML builder and LaTeX builder. Default is False.
Note
LaTeX builder always assign numbers whether this option is enabled or not.
New in version 1.3.



From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: Donnerstag, 29. September 2016 13:37
To: Yujun Zhang ; TECH-DISCUSS OPNFV 

Subject: Re: [opnfv-tech-discuss] [doctor] figure number missing in document

Hi Yujun,

Thanks for reporting. I can confirm the issue also in my browser.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: Donnerstag, 29. September 2016 08:50
To: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [doctor] figure number missing in document

I though we have already resolved this issue in [1]. But it seems some figure 
numbers are missing in the document[2]. There should be Figure.X before the 
caption under the figure.

[Screen Shot 2016-09-29 at 2.46.19 PM.png]
Is it only an issue in my browser or common to all?

[1] https://gerrit.opnfv.org/gerrit/#/c/18805/
[2] http://artifacts.opnfv.org/doctor/docs/index.html#figure1

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

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Hi Madhu,

I agree with the increase of complexity. Looking at the other use cases, they 
are much more simply/short.
In order not to confuse others and to get the important use cases agreed soon, 
I propose to limit the changes and consider to add some details -if needed- at 
a later stage.

Detailed comments:

-  Existing text introduces cloud service providers (CSP). The new 
proposed text adds the same abbreviation for Communication Service Providers. 
This should be avoided.

-  Proposal to shorten/simplify the new paragraph on VNFs and VNFDs?

-  What you call generic reservation is already an agreed use case, so 
we should keep this level of granularity and also IMHO we should not 
touch/change other use cases as we haven't talked to the contributor of those 
use cases and may not know their intention behind.

-  The proposed part on "minimal  set of parameters" could be 
misleading as we would like to have the option to specify those parameters, but 
we don't want to enforce those parameters to all use cases, i.e. the parameter 
shall be available but its usage is optional.
What about changing this part to use cases that require those parameters?

* Start time: is already there in the existing use cases: future start 
time in 1+2; immediate start time in 3 (to be more explicit on this we could 
add a "from now", but IMHO no strong need).

* Expiry time: I had a proposal in my first draft of this (see email 
August 25th):

* As a CSP, I want to be able to cancel a RUR if the user has not started using 
the requested capacity in a given time window after the planned start time of 
the RUR. Note, this is similar to a "no-show" rule for hotel and restaurant 
bookings.

We could also hold back this item for the time being and add it in a later 
revision once the main part on the reservation of instances is approved.


* Compute (vCPU, RAM), network and storage volume are already covered 
by other use cases.
"Future items" can be added in a later revision.

See also the attached revision of the document.

Best regards,
Gerald


From: Kashyap, Madhu [mailto:madhu.kash...@hpe.com]
Sent: Donnerstag, 6. Oktober 2016 00:48
To: Kunzmann, Gerald ; Gangur, Hrushikesh 
; Arturo Martin De Nicolas 
; opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 
; Ashiq Khan 
Subject: RE: [Promise]Capacity Management User Story

Perhaps this is getting a little complicated with different reservation 
requests (discrete or aggregate) and confidence levels (guaranteed or best 
effort).

Here's another proposal - we have reservations either against specific VNFs or 
we have generic reservations.

In the case of reservations for specific VNFs we know the exact requirements 
from a virtual machine perspective which is based on VNFD. The granularity of 
the reservation is a virtual machine.

The other kind of reservation is a generic reservation, similar to "I want 60 
vCPUs, 240 gig ram and 600 Gig disk". Here the granularity is more fine-grained.

In both cases the reservations, specific or generic,  would be guaranteed if 
the resources are available. In the generic reservation we don't know how the 
resources would be used. It is possible that the resources are spread across 
many hosts. Let's take an extreme case based on a request for 60 vCPUs. These 
could be spread across 60 hosts. So even though these were requested and 
reserved it is possible that when you go to deploy a VM it could fail.  This is 
because we don't know  how these resources are going to be used even though it 
has been reserved.

Again in both requests (specific or generic) we guarantee the resources but for 
the generic request it is up to the operator on how they use the resources.

Welcome any thoughts and comments.

-Madhu

From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com]
Sent: Thursday, September 29, 2016 3:24 AM
To: Kashyap, Madhu mailto:madhu.kash...@hpe.com>>; 
Gangur, Hrushikesh 
mailto:hrushikesh.gan...@hpe.com>>; Arturo Martin De 
Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>;
 opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Cc: Souville, Bertrand 
mailto:souvi...@docomolab-euro.com>>; Thulasi, 
Arun mailto:arun.thul...@hpe.com>>; Ashiq Khan 
mailto:k...@nttdocomo.com>>
Subject: RE: [Promise]Capacity Management User Story

Hi Madhu, all,

Thanks for the updated version based on the PWG discussions.

My comments:

-  I would not use the term "best-effort" for the reservation requests 
as we also would like to get a guarantee on the requested aggregated resources.

o   What about the terms "discrete" and "aggregate"?

o   Alternatively, introduce two levels of granularity "discrete" / "aggregate" 
 and in addition introduce two levels of 

Re: [opnfv-tech-discuss] [announce] Upgrade of Gerrit report - Access to repo tree

[Kunzmann, Gerald]

Hi Aric,

In the previous version of Gerrit, I could reach the project repo/tree from the 
"branches" tab: https://gerrit.opnfv.org/gerrit/#/admin/projects/doctor,branches

It seems this option is not available anymore. Is it a bug? Does anyone know 
another way to access the code through gerrit?

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Montag, 3. Oktober 2016 01:20
To: infra-steer...@lists.opnfv.org; OPNFV Tech 
; Fatih Degirmenci 

Subject: [opnfv-tech-discuss] [announce] Upgrade of Gerrit report. (ssh host 
key changed)

Hello,

The upgrade of gerrit to 2.13.1 is complete.
And jenkins has been restarted to give it more memory.

There is an unfortunate caveat. I did not consider the rsa keys on the old 
gerrit server would not be compatible with java on the new server

the old gerrit server has only one key.

ssh_host_key

the new gerrit server has

ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_rsa_key
ssh_host_rsa_key.pub

I tried to copy over the old ssh_host_key and use it as the rsa key on the new 
server, but it is in MINA SSHD custom format. Both the public and private 
halves are stored in the "ssh_host_key" file using a Java serialization format. 
I searched online, and did not find any utilities to convert this.

Gerrit failed to start like so:
[2016-10-02 22:32:38,226] [main] WARN
org.apache.sshd.common.util.SecurityUtils$BouncyCastleFileKeyPairProvider
: Failed (IOException) to load key
resource=/opt/gerrit/etc/ssh_host_rsa_key: Failed to read 
/opt/gerrit/etc/ssh_host_rsa_key - unknown result object: null

18:56 < AlexAvadanii> aricg-: given the time, we could fix this, but it's 
probably not
  that easy as converting one file to another using a cli 
tool ...
  or if there is such a tool, I can't find it

I agree with Alex, but we can't stop using gerrit while we try to fix this 
unforeseen problem.

So going forward, everything works excepting the host key change. Any machine 
or developer that clones over ssh will see this warning.

git clone ssh://jenkins...@gerrit.opnfv.org:29418/releng
Initialized empty Git repository in /tmp/releng/.git/ 
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is 
46:3a:c5:80:58:7e:24:9e:88:d3:83:29:6c:9a:80:17.
Please contact your system administrator.
Add correct host key in /home/agardner/.ssh/known_hosts to get rid of this 
message.
Offending key in /home/agardner/.ssh/known_hosts:1 RSA host key for 
[gerrit.opnfv.org]:29418 has changed and you have requested strict checking.
Host key verification failed.

you will need to remove the specified line in /home/"Your 
user"/.ssh/known_hosts:"The line number to delete"
and then re-accept the new key.

Apologies in advance and best regards,
-Aric
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Hi Mike,

Your thoughts are highly valuable and appreciated.

Isn’t the current OpenStack already the platform / environment that we are 
talking about? I agree that the platform providers’ interest is to create a 
common framework that fits as many users as possible. Isn’t it then now the 
stage to write down our specific Telco use cases and based on that identify the 
gaps and let the “innovative program coders” expand the(ir) platform to meet 
our use cases?

Also, the PWG has already defined this kind of template/approach and somehow if 
we want to bring our use cases/requirements through the PWG we should follow 
it. It would be a different story and we would need to include the PWG folks if 
we want to fundamentally question/change their approach proposing a different 
value path.

Or did I mis-read your message?

Best regards,
Gerald


From: Bugenhagen, Michael K [mailto:michael.k.bugenha...@centurylink.com]
Sent: Freitag, 7. Oktober 2016 15:32
To: Kunzmann, Gerald ; Kashyap, Madhu 
; Gangur, Hrushikesh ; Arturo 
Martin De Nicolas ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 

Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Gerald,

I’m going to suggest a slightly different “value” path -
First establish what the framework for delivering capacity is -  THEN see if 
one can use it to satisfy the use cases, and identify the gaps.

In compute, and Cloud when one makes a platform / Environment, you don’t do a 
use case on every application that can be made, you document the platform, and 
how it functions and then you let the innovative program coders expand how to 
use it.
i.e. – you expose a framework, they utilize it.

The role of the platform provider is to evolve and maintain a common 
framework that works for all the users… vs. trying to build every single user 
story
In a closed system dev. View one does create all the system use, cases – in 
Open platforms / OS efforts we’re really more focused enabling the environment 
/ platform vs. depicting all the users stories.

   So – I would recommend identifying the “frameworks” for “resource 
management” and “use management” in both the Telecom bearer path, and the Cloud 
service platforms “first” and then use those frameworks to describe what can be 
done, and what gaps exist.

Example

a)  What are the “components” (resource levels) or entities we are applying 
use control (CAC) to

b)  Identify what “utilization frameworks” do those components use

c)   Identify the “load sharing / dedicated” resource schema those 
components use   (what are the algorithms used across the resource entity for 
weighted, dedicated, or shared use).


Providers “do this” when designing our platform design.

Aka -   QoS marking built for QoE goals.. in our forwarding plane q’s.
We need to do the same exercise here.   What are the QoS 
mechanisms in Cloud, and how are they applied to reach what you are describing.

I think the framework itself is going to be a tricky thing because different 
NFVI hosts have different resource and use algorithms…

Anyway – just sharing my thoughts.
Thanks,
Mike








From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Kunzmann, Gerald" 
mailto:kunzm...@docomolab-euro.com>>
Date: Friday, October 7, 2016 at 5:38 AM
To: "Kashyap, Madhu" mailto:madhu.kash...@hpe.com>>, 
"Gangur, Hrushikesh" 
mailto:hrushikesh.gan...@hpe.com>>, Arturo Martin De 
Nicolas 
mailto:arturo.martin-de-nico...@ericsson.com>>,
 
"opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Cc: "Souville, Bertrand" 
mailto:souvi...@docomolab-euro.com>>, "Thulasi, 
Arun" mailto:arun.thul...@hpe.com>>
Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi Madhu,

I agree with the increase of complexity. Looking at the other use cases, they 
are much more simply/short.
In order not to confuse others and to get the important use cases agreed soon, 
I propose to limit the changes and consider to add some details –if needed- at 
a later stage.

Detailed comments:

-  Existing text introduces cloud service providers (CSP). The new 
proposed text adds the same abbreviation for Communication Service Providers. 
This should be avoided.

-  Proposal to shorten/simplify the new paragraph on VNFs and VNFDs?

-  What you call generic reservation is already an agreed use case, so 
we should keep this level of granularity and also IMHO we should not 
touch/change other use cases as we haven’t talked to the contributor of those 
use cases and may not know their intention behind.

-  The proposed part on “minimal  set of parameters” could be 
misleading as we would like to have the option to specify those param

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

[Kunzmann, Gerald]

Hi Tomi,

Nice! I am relieved that this simple trick worked. Thanks for the testing.

Have a nice weekend.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Juvonen, Tomi 
(Nokia - FI/Espoo)
Sent: Freitag, 7. Oktober 2016 11:05
To: 'Ryota Mibu' ; 'Yujun Zhang' 
; 'opnfv-tech-discuss@lists.opnfv.org' 

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

Good news!

Changing Inspector to make parallel execution (threads) for reset server state 
did the trick and now we are back in business ☺
Doctor test case now goes through with any decent number of VMs on failing host:
With 20VMs where 10 VMs on failing host: 340ms
(This used to be: With 20VMs where 10 VMs on failing host: 1540ms to 1780ms)
Works also with bigger amount of VMs:
With 100VMs where 50 VMs on failing host: 550ms

Have a nice weekend.

Br,
Tomi

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Juvonen, Tomi 
(Nokia - FI/Espoo)
Sent: Wednesday, October 05, 2016 10:27 AM
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] [Doctor] Reset Server State 
and alarms in general

Hi,

Furthermore it seems that making the payload to notification in Nova is the 
pain point, so I do not think there is much to optimize in that as of the 
general usage of that. This takes ~115ms in Nokia POD for each VM.

That would leave options:

· Can notifications/reset server state be parallel (quick and dirty fix 
if even possible)

· Can there be new notification.

oCan there be new tenant specific notification instead of notification for 
each VM. Meaning if tenant has 10 VMs on a failing host, there would only be 
one tenant specific notification including all his VMs. Payload should not be 
as heavy as currently as this would be for the tenant specific alarm of his VMs 
on failing host. Also as not so many notifications, should not have the 
cumulative problem of wasting time in forming several notifications. Also one 
could subscribe to this tenant specifically and not like now that one need to 
subscribe alarms VM id specifically. Currently this would still remain as 
downside of current implementation if need to alarm only single VM failure, 
making the tenant alarm subscribing not very convenient.

§  This can be achieved by having this new notification done by force-down API 
and the unwanted reset server state could be removed.

§  This can be achieved by having this new notification done by Inspector and 
the unwanted reset server state could be removed. (faster, can be parallel to 
force-down call).

oNeeded state information is already done by force-down API as of 
implementation of “get valid server state BP in Nova” and therefore no reset 
server state is needed. Inspector should do the needed notification. This would 
have the fastest execution time where information do not need to flow through 
nova to notifier and has it easy to have parallel execution to notification and 
force-down API. This is the right thing in long run (while technically speaking 
of “Telco grade” there would be even more to enhance to have things as quickly 
as possible, like one should subscribe alarms directly from Inspector; but we 
cannot achieve everything that easily and that will be far in future.)

Br,
Tomi


From: Juvonen, Tomi (Nokia - FI/Espoo)
Sent: Tuesday, October 04, 2016 3:08 PM
To: Ryota Mibu mailto:r-m...@cq.jp.nec.com>>; Yujun Zhang 
mailto:zhangyujun+...@gmail.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Doctor] Reset Server State and alarms in 
general

Hi,

Still modified the test so that I do not do the reset server state, but instead 
just make the notification about “reset server state error” for each instance 
when force-down API called:
for instance in instances:
notifications.send_update_with_states(context, instance,
instance.vm_state, vm_states.ERROR,instance.task_state,
None, service="compute", host=host,verify_states=False)

This had the same result as trough instance.save() that also changes the DB. So 
didn’t make things any better.

Br,
Tomi

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Juvonen, Tomi 
(Nokia - 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
Subject: Suspected SPAM - Re: [opnfv-tech-discuss]

Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

[Kunzmann, Gerald]

Hi Mike,

Okay. thanks for confirming.
Do you plan to collect some initial input on identifying the underlying 
management framework?

Have a nice weekend.

Best regards,
Gerald

From: Bugenhagen, Michael K [mailto:michael.k.bugenha...@centurylink.com]
Sent: Freitag, 7. Oktober 2016 16:09
To: Kunzmann, Gerald ; Kashyap, Madhu 
; Gangur, Hrushikesh ; Arturo 
Martin De Nicolas ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 

Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

No you got it right – I didn’t do that good of job of putting it together so 
you did great.
   One thing I completely missed is that a “implementation use case” consider 
the system an “actor” so we have to identify the frameworks in the actor as 
part of the use case.

i.e. – we have to identify the underlying management framework as I put in the 
prior message.

It probably would have been nice if I started off with that  ☺ - my 
apologies for the choppy response.

Best regards,
Mike



From: "Kunzmann, Gerald" 
Date: Friday, October 7, 2016 at 8:53 AM
To: "Bugenhagen, Michael K" , "Kashyap, 
Madhu" , "Gangur, Hrushikesh" 
, Arturo Martin De Nicolas 
, "opnfv-tech-discuss@lists.opnfv.org" 

Cc: "Souville, Bertrand" , "Thulasi, Arun" 

Subject: RE: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Hi Mike,

Your thoughts are highly valuable and appreciated.

Isn’t the current OpenStack already the platform / environment that we are 
talking about? I agree that the platform providers’ interest is to create a 
common framework that fits as many users as possible. Isn’t it then now the 
stage to write down our specific Telco use cases and based on that identify the 
gaps and let the “innovative program coders” expand the(ir) platform to meet 
our use cases?

Also, the PWG has already defined this kind of template/approach and somehow if 
we want to bring our use cases/requirements through the PWG we should follow 
it. It would be a different story and we would need to include the PWG folks if 
we want to fundamentally question/change their approach proposing a different 
value path.

Or did I mis-read your message?

Best regards,
Gerald


From: Bugenhagen, Michael K [mailto:michael.k.bugenha...@centurylink.com]
Sent: Freitag, 7. Oktober 2016 15:32
To: Kunzmann, Gerald ; Kashyap, Madhu 
; Gangur, Hrushikesh ; Arturo 
Martin De Nicolas ; 
opnfv-tech-discuss@lists.opnfv.org
Cc: Souville, Bertrand ; Thulasi, Arun 

Subject: Re: [opnfv-tech-discuss] [Promise]Capacity Management User Story

Gerald,

I’m going to suggest a slightly different “value” path -
First establish what the framework for delivering capacity is -  THEN see if 
one can use it to satisfy the use cases, and identify the gaps.

In compute, and Cloud when one makes a platform / Environment, you don’t do a 
use case on every application that can be made, you document the platform, and 
how it functions and then you let the innovative program coders expand how to 
use it.
i.e. – you expose a framework, they utilize it.

The role of the platform provider is to evolve and maintain a common 
framework that works for all the users… vs. trying to build every single user 
story
In a closed system dev. View one does create all the system use, cases – in 
Open platforms / OS efforts we’re really more focused enabling the environment 
/ platform vs. depicting all the users stories.

   So – I would recommend identifying the “frameworks” for “resource 
management” and “use management” in both the Telecom bearer path, and the Cloud 
service platforms “first” and then use those frameworks to describe what can be 
done, and what gaps exist.

Example

a)  What are the “components” (resource levels) or entities we are applying 
use control (CAC) to

b)  Identify what “utilization frameworks” do those components use

c)   Identify the “load sharing / dedicated” resource schema those 
components use   (what are the algorithms used across the resource entity for 
weighted, dedicated, or shared use).


Providers “do this” when designing our platform design.

Aka -   QoS marking built for QoE goals.. in our forwarding plane q’s.
We need to do the same exercise here.   What are the QoS 
mechanisms in Cloud, and how are they applied to reach what you are describing.

I think the framework itself is going to be a tricky thing because different 
NFVI hosts have different resource and use algorithms…

Anyway – just sharing my thoughts.
Thanks,
Mike








From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "Kunzmann, Gerald" 
mailto:kunzm...@docomolab-euro.com>>
Date: Friday, October 7, 2016 at 5:38 AM
To: "Kashyap, Madhu" mailto:madhu.kash...@hpe.com>>, 
"Gangur, Hrushikesh" 
mailto:hrushikesh.gan...@hpe.com>>, Arturo

Re: [opnfv-tech-discuss] [Infra-steering] OPNFV Maintainance: 2016-10-16 @ 08:00 PDT (14:00 UTC)

[Kunzmann, Gerald]

Dear Trevor, Aric,

Thanks for the early notice.

I had reported to Aric some issue with access to the repo tree in Gerrit (see 
attached email). Did you have a chance to investigate on this? Is it a bug or 
has this feature been removed? It would be great if that functionality could be 
brought back in the upcoming Gerrit maintenance.

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jonas Bjurel
Sent: Donnerstag, 13. Oktober 2016 00:44
To: Trevor Bramwell ; 
it-infrastructure-ale...@linuxfoundation.org; 
opnfv-tech-discuss@lists.opnfv.org; infra-steer...@lists.opnfv.org; 
infra...@lists.opnfv.org; Heather Kirksey ; 
Raymond Paik ; Aric Gardner 

Subject: Re: [opnfv-tech-discuss] [Infra-steering] OPNFV Maintainance: 
2016-10-16 @ 08:00 PDT (14:00 UTC)

Trevor - Thanks for the early heads-up, some SLA/sanity requests from me below:

I require that there will be a pre-staging environment that we can test prior 
to shifting this change into production environment. This is to avoid OPNFV 
production discontinuity as experienced before.
If you could provide a pre-staging dummy area - which the community could 
evaluate before the production upgrade is exercised we could likely out-rule 
issues with upgrades we have seen in the past.
Me - Jonas Bjurel, and others in my team: Stefan Berg, Fatih Degirmency - would 
be happy to smoke-test the pre-staging environment!
Other obvious things around change-management: Complete back-up, 24/7 
preparedness on roll-back, communication on the changes and any measures needed 
by the consumers of the service, and of course logging of everything 
performed/issues during the evaluation of the change, and from the change it 
self.

Me and others are happy to help such that these changes flow seamlessly work - 
going forward.

Hope this helps!
BR/Jonas  

-Original Message-
From: infra-steering-boun...@lists.opnfv.org 
[mailto:infra-steering-boun...@lists.opnfv.org] On Behalf Of Trevor Bramwell
Sent: Wednesday, October 12, 2016 11:05 PM
To: it-infrastructure-ale...@linuxfoundation.org; 
opnfv-tech-discuss@lists.opnfv.org; infra-steer...@lists.opnfv.org; 
infra...@lists.opnfv.org
Subject: [Infra-steering] OPNFV Maintainance: 2016-10-16 @ 08:00 PDT (14:00 UTC)

Hello,

The Linux Foundation will be performing maintenance on the following
services: Gerrit

When: 

  2016-10-16 @ 08:00 - 09:00 PDT (14:00 - 15:00 UTC)

Why:

  The OPNFV Gerrit server configuration needs to be updated to fix the
  following issues:

   - Automatic Stale Patchset (> 6 months) Abandonment
   - Login names with uppercase characters required to be typed in all
 lowercase

  These changes requires a restart of Gerrit.

Who:

  Trevor Bramwell 
  Aric Gardner 

Impact:

  Gerrit (https://gerrit.opnfv.org) will experience a brief outage as it
  is restarted.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--- Begin Message ---
Hi Aric,

In the previous version of Gerrit, I could reach the project repo/tree from the 
"branches" tab: https://gerrit.opnfv.org/gerrit/#/admin/projects/doctor,branches

It seems this option is not available anymore. Is it a bug? Does anyone know 
another way to access the code through gerrit?

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Montag, 3. Oktober 2016 01:20
To: infra-steer...@lists.opnfv.org; OPNFV Tech 
; Fatih Degirmenci 

Subject: [opnfv-tech-discuss] [announce] Upgrade of Gerrit report. (ssh host 
key changed)

Hello,

The upgrade of gerrit to 2.13.1 is complete.
And jenkins has been restarted to give it more memory.

There is an unfortunate caveat. I did not consider the rsa keys on the old 
gerrit server would not be compatible with java on the new server

the old gerrit server has only one key.

ssh_host_key

the new gerrit server has

ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_rsa_key
ssh_host_rsa_key.pub

I tried to copy over the old ssh_host_key and use it as the rsa key on the new 
server, but it is in MINA SSHD custom format. Both the public and private 
halves are stored in the "ssh_host_key" file using a Java serialization format. 
I searched online, and did not find any utilities to convert this.

Gerrit failed to start like so:
[2016-10-02 22:32:38,226] [main] WARN
org.apache.sshd.common.util.SecurityUtils$BouncyCastleFileKeyPairProvider
: Failed (IOException) to load key
resource=/opt/gerrit/etc/ssh_host_rsa_key: Failed to read 
/opt/gerrit/etc/ssh_host_rsa_key - unknown result object: null

18:56 < AlexAvadanii> aricg-: given the time, we could fix this, but it's 
probably not
  that easy as converting one file to another using a cli 
tool ...
   

Re: [opnfv-tech-discuss] Meetings discussion (GoToMeeting, meetings info on wiki, etc)

[Kunzmann, Gerald]

Dear all,

My 2 cent on the topic:


-  +1 on the single recurring meetings to solve the disconnect issue

-  IMHO, both the calendar view as well as the list of meetings have 
their justifications and pros. As some meetings only occur on a bi-weekly 
basis, the calendar view for one week may not show you all project meetings. In 
order to reduce the maintenance efforts (which I agree exist), what about 
having the meeting info in a rst file which is then automatically added to 
meeting list and the project meeting subpage? I am not sure we could even 
include the calendar, or, alternatively, generate the meeting details from the 
calendar – that would be awesome.

-  On the other conferencing tools: in the past, we had for some time 
been using our WebEx account for Promise meetings. The reason we changed back 
to OPNFV GTM was that if I was not available for the call, it was difficult for 
others to start the meeting. Moreover, some other conferencing tools do not 
work well with some company firewalls, e.g. I am always having issues 
connecting to a Lync session.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Dienstag, 22. November 2016 22:57
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Meetings discussion (GoToMeeting, meetings info 
on wiki, etc)

Continuing the conversation from the TSC call...


  *   One proposal was to have a single recurring meeting per each GTM account 
(tech-proje...@opnfv.org & 
tech-projec...@opnfv.org) so that individual 
project meeting won't get disconnected when someone else dials for another 
meeting with a different access code.  If there's a consensus for this (it did 
sound like it on the call), I can create a new/global recurring meeting for 
each account and delete other individual project meetings.
  *   On the wiki front, there are two places where meeting information needs 
to be updated on the main meetings page 
(https://wiki.opnfv.org/display/meetings).  The calendar on the right-hand side 
of the page plus the list of meetings on the left.  I personally find the 
calendar view useful to get a sense of what meetings are taking place each day. 
 As for the list of meeting on the left, does it make sense to maintain this 
list when we also have daughter pages such as 
https://wiki.opnfv.org/display/meetings/Release?  In addition, some project 
wiki pages have meeting information on their project pages.  I think this is 
more a decision on how/where the community wants to maintain meeting 
information.  If the community agrees that each project, work groups, etc. will 
maintain daughter pages (e.g. https://wiki.opnfv.org/display/meetings/ABC) I 
think this will simplify things as people will only need to maintain meeting 
information in 2 places (calendar + daughter page) vs. 4 today as Trevor Copper 
suggested on the call.
  *   Another reminder on conferencing tools.  Some people are already doing 
this, but if you have access to other conferencing tools (e.g. through work) 
and you don't need all the features of GTM (e.g. screen sharing), there's no 
need to use OPNFV GTM accounts for all project meetings.  Getting more GTM 
accounts not only costs money for OPNFV, but it also becomes more difficult to 
manage.
Please reply to the thread with your comments/questions.

Thanks,

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

[opnfv-tech-discuss] [Promise] Minimum feature set

[Kunzmann, Gerald]

Dear all,

I have generated an Etherpad page: 
https://etherpad.opnfv.org/p/promise_minimum_features showing the table we had 
discussed in the last meeting.
Feel free to comment on that page.

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

Re: [opnfv-tech-discuss] Single recurring meetings for the two GTM accounts

[Kunzmann, Gerald]

Hi Ray,

Now I am confused. You write we should use:
OPNFV Tech Projects meetings (for meetings starting during odd-number hours 
Pacific Time)
OPNFV Tech Projects2 meetings (for meetings starting during even-number hours 
Pacific Time)

Does that mean we should not have any more parallel calls? That was not my 
understanding from the previous discussion (sorry, I had missed the final 
discussion in the TSC). E.g. Testperf and Dovetail have parallel meetings on 
Friday 1pm UTC. I thought, that one would use the Tech Projects meeting, the 
other one the Tech Projects2 meeting.

Did I get something wrong?

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Freitag, 2. Dezember 2016 19:04
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Single recurring meetings for the two GTM accounts

All,

As discussed in the TSC call, I created single recurring meetings for each of 
the GTM accounts we have for calls.  You can find the info below (and I also 
added this to the main meetings wiki page at 
https://wiki.opnfv.org/display/meetings/Meetings).

For people who were not on the TSC call, there was a consensus to move to a 
single recurring meeting so that your project call does not get dropped when 
someone else dials in for the next meeting.  If your meeting runs late, you'll 
simply be asked to leave by others who join for the next call...

Please start migrating to these dial-ins over the next few weeks.  I would also 
like to ask PTLs and other meeting organizers to start removing other recurring 
meetings for your projects from the GTM accounts by December 16th.  After the 
16th, I'll remove other recurring meetings from the accounts (except for the 
two below).

Thanks,

Ray
--
OPNFV Tech Projects meetings (for meetings starting during odd-number hours 
Pacific Time)

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/144838637

You can also dial in using your phone.
United States +1 (786) 358-5410

Access Code: 144-838-637

More phone numbers
Australia +61 2 8355 1040
Austria +43 7 2088 0034
Belgium +32 (0) 28 93 7018
Canada +1 (647) 497-9353
Denmark +45 69 91 88 64
Finland +358 (0) 923 17 0568
France +33 (0) 170 950 592
Germany +49 (0) 692 5736 7210
Ireland +353 (0) 15 360 728
Italy +39 0 247 92 13 01
Netherlands +31 (0) 208 080 379
New Zealand +64 9 909 7888
Norway +47 75 80 32 07
Spain +34 955 32 0845
Sweden +46 (0) 853 527 836
Switzerland +41 (0) 225 3314 51
United Kingdom +44 (0) 330 221 0086


OPNFV Tech Projects2 Meetings (for meetings starting during even-number hours 
Pacific Time)

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/819733085

You can also dial in using your phone.
United States +1 (312) 757-3126

Access Code: 819-733-085

More phone numbers
Australia +61 2 8355 1040
Austria +43 7 2088 0034
Belgium +32 (0) 28 93 7018
Canada +1 (647) 497-9350
Denmark +45 69 91 88 64
Finland +358 (0) 923 17 0568
France +33 (0) 170 950 592
Germany +49 (0) 692 5736 7211
Ireland +353 (0) 15 360 728
Italy +39 0 247 92 13 01
Netherlands +31 (0) 208 080 219
New Zealand +64 9 280 6302
Norway +47 75 80 32 07
Spain +34 911 82 9906
Sweden +46 (0) 853 527 836
Switzerland +41 (0) 435 0167 13
United Kingdom +44 (0) 330 221 0086

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

Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

[Kunzmann, Gerald]

Hi everyone,

Independent on which timezone we use, this will result in conflicts in some 
regions. I agree with Bob that for US/EU this would mean a shift in meeting 
time for months and might lead to meeting clashes with other non-OPNFV 
meetings. However, at the moment this problem is with Asia as they don’t have 
daylight saving times. So, this will mean pain for a large group of people in 
the one and the other case.

The benefit I see for using UTC times is that it would be easier to calculate 
the meeting times for the individual time zones. You don’t have to worry about 
PST/PDT etc… Furthermore, I guess everyone knows that his timezone is UTC+X so 
he can easily figure out the meeting time in his zone, whereas I have to be 
more careful to remember what is the delta between PST/PDT and CET/CEST.

If we plan to go to UTC times and adapt meeting times to daylight saving, then, 
which daylight saving schedule to take into account? Note that US and Europe 
start/end daylight saving at different weeks, which has in the past often 
caused some confusion for some OPNFV meetings.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bob Monkman
Sent: Sonntag, 4. Dezember 2016 23:44
To: Raymond Paik ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

Ray,
I am flexible if folks in the majority wish to switch to UTC. Like others have 
mentioned, all of my company meetings are pretty much set to US time. When my 
Armband call is set to PST, there is confusion and shift 1-3 weeks at DST 
times- the UTC would shift times for months and cause us to request other 
meetings to shift for the same period. I would prefer therefore to _not_ change.

Bob

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Friday, December 2, 2016 10:33 AM
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

All,

Another follow-up from the TSC...

Over the past couple of years, we've had discussions on whether meetings like 
TSC or Release call times should be based on Pacific Time (as has been the 
tradition since OPNFV started) or if the community should move to UTC.

UTC obviously has the benefit of not changing with Daylight Savings/Summer time 
switches twice a year in North America/Europe.  When we last had the 
discussion, a large number of people preferred staying with Pacific Time as 
most of their work meetings (esp. outside of OPNFV) are based on their local 
timezones and not UTC.

If we're to move to UTC here's how the meeting times will change for the TSC 
call in Pacific and Central European Timezones.

Standard Time (now)

  *   PT: 07:00
  *   CET: 16:00
  *   UTC: 15:00
  *   China: 23:00
Daylight Savings/Summer Time (March-November in 2017)

  *   PT: 08:00
  *   CET: 17:00
  *   UTC: 15:00
  *   China: 23:00
Can you reply to the email with your comments/preference on UTC. vs Pacific 
Time?

Thanks,

Ray
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [promise] Project Lead Transition

[Kunzmann, Gerald]

Hi Peter,

As you couldn’t have joined last Promise meeting, I’d also like to use this way 
to express my thanks to your contributions to Promise. You had been leading the 
project from the very beginning and had created the first releases for OPNFV 
Promises and its test cases.
We are all happy that you, with your excellent knowledge of the project 
requirements and pain points (and there had been numerous), will stay active in 
the project and continue to provide your guidance to us.

Thanks also for your nomination as your successor. I am happy to accept the 
nomination.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Peter Lee
Sent: Dienstag, 6. Dezember 2016 19:36
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [promise] Project Lead Transition

Hi everyone,

I would like to inform the wider community that I will be stepping down as PTL 
for the Promise project and initiating a new election period for the next 
project team lead.

It's been an amazing two years serving as PTL for the Promise project. As one 
of the founding projects of OPNFV initiated by Docomo, the Promise project has 
participated in every OPNFV release to date and has benefited much from active 
participation from many Committers and Contributors along the way. Thank you!

We will have a one week nomination period for anyone interested in serving as 
the new PTL for the Promise project. Please share your nominations by 12/13 and 
the current Promise team Committers will cast their vote starting on 12/14.

As outgoing PTL, I would like to nominate Gerald Kunzmann from Docomo as the 
next PTL for the Promise project. He has been an active Contributor and 
Committer since the project's inception and we wouldn't be where we are today 
without his leadership.

I will continue to remain as a Committer to the Promise project and support the 
ongoing project initiatives under the guidance of the next elected PTL.

On a related note, I am now serving as project lead for the newly incubated 
Composer project in OpenCORD. If anyone's interested in modeling their services 
and integrating into the CORD platform, just let me know.

Best,

Peter Lee
Promise PTL
Corenova Technologies
--
Peter Lee
Corenova Technologies
+1 310 400 6450
pe...@corenova.com
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Gotomeeting reservation

[Kunzmann, Gerald]

Hi Luke,


1)  Go to https://wiki.opnfv.org/display/meetings/Meetings and check in the 
table whether there is already another project is using this slot

a.   If there are already 2 parallel sessions -> sorry you’d have to find a 
new slot

b.  If there is 1 session -> check which GTM account is being used -> 
create a new entry for the other account and update your project page 
accordingly

c.   If there is no session -> pick one of the two GTM accounts, create a 
new entry in the table and update your project page accordingly.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Luke Hinds
Sent: Dienstag, 13. Dezember 2016 11:09
To: opnfv-tech-discuss@lists.opnfv.org; Ash ; 
degirmenci, fatih ; opnfv-security 

Subject: [opnfv-tech-discuss] Gotomeeting reservation

Hi,
I'll be honest, I am completely out of sync with what we are doing for 
gotomeeting slots now.
In the security group, we went to IRC only a while ago to free up a session 
slot, but we now need a gotomeeting session to walk over some stuff that will 
need audio / video for one time.
The security group meeting is at 14:00 UTC Wednesday, and we want it for 
tomorrow , how would I go about getting tabs on this time?

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

Re: [opnfv-tech-discuss] committer list maintainance

[Kunzmann, Gerald]

Hi,

I agree, some metric to help the PTL to find out inactive committers and maybe 
some rules that, based on a certain inactivity, the PTL may on his own remove 
such committers.

However, I would be very careful with any fully automatic removal of committers:

-  The team/PTL should have the right to decide about removal of 
committers (e.g. there could be a good reason for a certain period of 
inactivity of one committer)

-  Such decisions/actions should be transparent and as such IMHO the 
TSC should be involved -at least be notified- about such actions/decisions

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tapio Tallgren
Sent: Freitag, 16. Dezember 2016 09:11
To: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] committer list maintainance

Hi,

I think we have to update the Project Governance to be able to remove inactive 
committers. I can take a look at that. The initial idea really was that 
committers had an important role in the project governance, so the PTL could 
not just remove committers. In theory, you could have a very contentious 
project with members fighting with each others and all decisions happening by 
voting among committers. Then the PTL could start removing committers 
involuntarily to make sure that the votes go his/her way.

This is not likely and it is not happening, so I think we can try to change the 
rules. We have to take this to the TSC vote.

-Tapio




On 12/16/2016 04:39 AM, Yujun Zhang wrote:
+1 for the idea of automatic monitoring
--
Yujun

On Fri, Dec 16, 2016 at 4:15 AM Heather Kirksey 
mailto:hkirk...@linuxfoundation.org>> wrote:
I like Morgan's suggestion -- the expectation of committers is that they're 
active and actively working the project; if they're not participating and not 
responding to emails, it's reasonable to remove them from the committer file. 
As folks say, this isn't a "punishment for bad faith" but a recognition that 
people move on from companies, roles, or projects. Having an automated way to 
handle this sounds reasonable…..

From my perspective, our TSC isn't focusing on what it needs to focus on if 
they're voting on the removal of every nonactive committer on every project. 
That's also not entirely a scalable solution as we continue to grow as a 
community. Empowering PTLs to manage their committers with the help of 
automated tools seems like the right thing to do.

This also relates to our community metrics discussion; if some projects 
experience much higher than average turnover in committers, it might be a 
reason to see what's going on and if the project needs help in some way. 
Focusing on how to enable and help projects be successful and removing 
obstacles if they're having issues is a good use of time; micro-managing 
committer lists is not.

My $.02.

Heather





On Thu, Dec 15, 2016 11:46 AM, Raymond Paik 
rp...@linuxfoundation.org wrote:
Please see an example from May of this year: 
https://wiki.opnfv.org/display/meetings/TSC#TSC-May17,2016 when the VSPERF PTL 
had several inactive committers who were non-responsive/not reachable.

If this is still too taxing for the PTLs, we can have a discussion in the TSC 
call

On Wed, Dec 14, 2016 at 1:33 AM, 
mailto:morgan.richo...@orange.com>> wrote:
in line with Yujun
no need to attend TSC to remove non active committers
usually we can do it through a patch of INFO file

the only case I can see a need to attend TSC is in case of conflict but I never 
saw that so far

during OpenStack Barcelona, we mentioned that it would be also nice to 
implement something to automatically remove 6 months non active contributors.
the idea is not to blame but to clean the repo and reflect the reality of the 
project activity
I agree that there are no commitments, people can move from one project to 
another
however it is better to have a good idea of the project activity and then 
keeping long list of non active contributors is misleading

So I would suggest to implement a job that will automatically remove a 
contributor Y of a project X if no activitiy has been reported since more than 
6 months
If the project has no commitor anymore or only the PTL or empty repo since x 
months => raise an alarm to TSC to clean also the project

/Morgan



Le 14/12/2016 à 08:31, joehuang a écrit :
+1000 for this "I never think it is a shame to leave a project,  since it is 
normal that people move on to a new target and didn't have time to say goodbye"

Best Regards
Chaoyi Huang (joehuang)

From: Yujun Zhang [zhangyujun+...@gmail.com]
Sent: 14 December 2016 15:10
To: joehuang; Raymond Paik
Cc: opnfv-tech-discuss
Subject: Re: [opnfv-tech-discuss] committer list maintainance
I think there is no mandatory rule for PTL to attend TSC meeting in order to 
complete the removal process. At l

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

[Kunzmann, Gerald]

Hi Yujun, Mark, all,

Thanks for the pointer to the list view.

Does anyone know if I could include the “OPNFV Team Meetings” calendar in my 
project and *filter for Promise meetings*. That way, I could avoid maintaining 
a Promise calendar and the “OPNFV Team Meetings” calendar.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: Freitag, 16. Dezember 2016 10:41
To: Raymond Paik ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

On Fri, Dec 16, 2016 at 3:36 AM Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:
All,

Next step is to see if there's a way to streamline the meetings calendar on the 
upper right corner.  If anyone has good ideas/suggestions, please let me know.

We use the list view in TestPerf meeting calendar[1]. Not sure if this works 
for massive meetings.

[1]: https://wiki.opnfv.org/display/meetings/TestPerf
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Dear Tommy,

I'd like to express my thanks for your contributions and guidance in the Doctor 
project.
You had been with the Doctor project from the very beginning, where we started 
from a few initial requirements. Now, look how far the journey has already 
taken us.

I am not sure where your journey will take you from now, however, independent 
of that, I wish you all the best for this future road.

I hope you'll enjoy the Christmas season and I hope you have a good start into 
the year 2017 and the next stage of your life.

Cheers,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tommy Lindgren
Sent: Dienstag, 20. Dezember 2016 13:24
To: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: [opnfv-tech-discuss] [Doctor] Resigning from committer role

Hi Doctor project,

I will leave Ericsson by the end of this year and thus I am also resigning from 
my committer role in the OPNFV Doctor project.

It has been a pleasure to work with all the devoted and competent people in 
this group and I wish you all luck in bringing the Doctor project to a 
successful completion.

Best regards
/Tommy











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

Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

[Kunzmann, Gerald]

Hi Mark, all,

Thanks for checking about the possibility and the evaluation you provided.

I am in favor of this approach. Can we discuss this proposal in the TSC?

Best regards,
Gerald

From: Georg Kunz [mailto:georg.k...@ericsson.com]
Sent: Montag, 19. Dezember 2016 10:03
To: Beierl, Mark ; Kunzmann, Gerald 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

Hi Mark,

I think the extended legend is not an issue and I like the possibility of 
including the meeting calendar on the project page. However, we must make sure 
that we somehow “encode” in a useful manner which GTM meeting account is used 
by a particular team – either by means of color as today or as part of the 
description.

Best regards
Georg

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 Beierl, Mark
Sent: Friday, December 16, 2016 5:52 PM
To: Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

Hello, Gerald.

Unfortunately, there is not an easy way to filter out events from a calendar, 
but what can be done is to include the Promise calendar into the Team Meetings 
calendar.  As long as you use the same type for your event (i.e. OPNFV 
GoToMeeting) and colour, it will show up.

I am not sure if that is the right approach, however, as that means each 
project would have its own calendar for meetings, instead of having a single 
calendar.

Advantages:

  *   Users can subscribe to a project's calendar and see only those events 
instead of everything.
  *   Might get rid of the annoying "Some events were not shown in the 
calendars below..." banner
  *   Teams have cleaner view
Disadvantages:

  *   "Legend" for team calendars will be huge as it must show every project 
title.
  *   Each team calendar must have same event types and colours.

I have put a "Test" calendar into the Demonstration Space [1] that shows what 
it looks like to display multiple calendars in a single view.  Note the legend 
on the left where it shows "TestPerf", "StorPerf", OPNFV Team Meetings.

What do others think of the choices?

[1] https://wiki.opnfv.org/display/ds/calendars

Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com<mailto:mark.bei...@dell.com>

On Dec 16, 2016, at 05:27, Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>> wrote:

Hi Yujun, Mark, all,

Thanks for the pointer to the list view.

Does anyone know if I could include the “OPNFV Team Meetings” calendar in my 
project and *filter for Promise meetings*. That way, I could avoid maintaining 
a Promise calendar and the “OPNFV Team Meetings” calendar.

Best regards,
Gerald

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 Yujun Zhang
Sent: Freitag, 16. Dezember 2016 10:41
To: Raymond Paik mailto:rp...@linuxfoundation.org>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Starting to clean-up meetings page on the wiki

On Fri, Dec 16, 2016 at 3:36 AM Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:
All,

Next step is to see if there's a way to streamline the meetings calendar on the 
upper right corner.  If anyone has good ideas/suggestions, please let me know.

We use the list view in TestPerf meeting calendar[1]. Not sure if this works 
for massive meetings.

[1]: https://wiki.opnfv.org/display/meetings/TestPerf

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

[opnfv-tech-discuss] [Promise] Team meeting on Jan 12th

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Dear Promise team\,\n\nin the last call he had a
 gree to have an extra-ordinary Promise meeting on Jan 12th\, 2017 at 13:00
  UTC.\n\n\nPromise team meeting (bi-weekly)\nChanged: IRC: #opnfv-promise\
 n\nhttps://global.gotomeeting.com/join/144838637<https://www.google.com/ur
 l?q=https%3A%2F%2Fglobal.gotomeeting.com%2Fjoin%2F144838637&sa=D&usd=2&usg
 =AFQjCNHS-P6MQKdkIDREa4sjkr6t5XqO-g>\nAccess Code: 144-838-637\nYou can al
 so dial in using your phone:\nUnited States (Toll-free) 1 877 309 2070\nGe
 rmany +49 (0) 692 5736 7206\nMore information and additional dial in numbe
 rs: https://wiki.opnfv.org/display/meetings/Promise+Team+Meetings\n\n\nBest regards\,\nGerald\n\n
SUMMARY;LANGUAGE=en-US:[Promise] Team meeting on Jan 12th
DTSTART;TZID=W. Europe Standard Time:20170112T14
DTEND;TZID=W. Europe Standard Time:20170112T15
UID:04008200E00074C5B7101A82E008609868DD2D60D201000
 01000621C4A166CD0CA41A02BC20C93C2D593
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161227T094451Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/144838637
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1352386528
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Follow-up on the meetings wiki page discussion

[Kunzmann, Gerald]

Dear Yujun, Mark, all,

Thanks for taking the lead on this.
I have implemented the team calendar for Promise: 
https://wiki.opnfv.org/display/meetings/Promise+Team+Meetings

I have used the name "OPNFV GoToMeeting" and added "Promise" to the description 
of the calendar. That way, it can easily be identified in the list of calendars.

How can I add this calendar to the team calendar on 
https://wiki.opnfv.org/display/meetings/Meetings ?

Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Beierl, Mark
Sent: Mittwoch, 11. Januar 2017 15:28
To: Yujun Zhang 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Follow-up on the meetings wiki page discussion

Looks great, Yujun.

The one extra step would be to ask that we name the events according to what 
type of account is being used:

OPNFV GoToMeeting
2nd OPNFV GoToMeeting
Etc.

And to change the colour to match the meeting page. That way it will be 
visually obvious in the aggregated calendar what account is being used, like it 
is today.
Regards,
Mark

Mark Beierl
Advisory Solutions Architect
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com


On Jan 11, 2017, at 02:40, Yujun Zhang 
mailto:zhangyujun+...@gmail.com>> wrote:
Done for QTIP.  See https://wiki.opnfv.org/display/meetings/QTIP

Please check if this is the expected result.


×
Yujun

On Wed, Jan 11, 2017 at 2:02 PM Raymond Paik 
mailto:rp...@linuxfoundation.org>> wrote:
All,

Following up on our conversation from the TSC call...

As discussed, we streamlined the project/working group meetings information on 
the wiki (https://wiki.opnfv.org/display/meetings) so that you don't have to 
update the same meeting information both on the main meetings page and the 
daughter pages for individual meetings.

As Mark also noted during the call, we have the opportunity to carry this 
further if project teams utilize the "team calendars" macro in meetings pages.  
The information from the team calendars can be aggregated into the main 
calendar on the meetings wiki page which now has to be manually updated.  
You'll find an example on the Storperf meetings page 
(https://wiki.opnfv.org/display/meetings/Storperf+Team+Weekly+Meeting) plus 
Mark's proposal before the holidays at 
https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-December/014182.html. 
 [Mark, feel free to add/correct anything :-)]

Please let us know if you have any thoughts/suggestions...

Thanks,

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

[opnfv-tech-discuss] [opnfv-docs] References in documentation to master or release files?

[Kunzmann, Gerald]

Dear OPNFVDOCS Team,

We are discussing about the pros/cons of referencing in documentation to master 
or release files.


A) The correct (?) way: always refer to master files/URLs in master branch 
and refer to release files/URLs in release branches.
For example, someone trying to git clone origin/stable/danube as documented in 
master branch will fail. Instead, pointing to a specific release should only 
happen in the corresponding release branch.

Also, rendered files in artifacts.opnfv.org from master branch (e.g. 
http://artifacts.opnfv.org/doctor/docs/manuals/mark-host-down_manual.html) 
should be placed under a 'master' directory just like it happens to rendered 
files from release branches.

Consequences:  When updating the documentation prior to branch split, we would 
have to use references to master and at branch split update all references to 
release branch. And patches that are being cherry picked to the release would 
require changing the links contained in it. Also, the references would have to 
be updated for each release.


B)  The pragmatic way: reduce the need/effort to update such links from 
release to release and use references to master for those parts of the 
documentation that will not change for the release, e.g. references to some 
manuals where we don't have any plans to update those parts of the code.

See also the discussion and example in 
https://gerrit.opnfv.org/gerrit/#/c/24365/

We are not sure what would be the preferred/recommended way.
Some recommendations by the opnfvdocs team would help the different projects to 
use a common approach.

I would like to get some more feedback from other OPNFV'ers on how to best 
address this.

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

[Kunzmann, Gerald]

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)  that the patch is only changing the editorial fixes, and/or

b)  result in a "merge conflict" as parts of the repo had been changed with 
the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  ,
but the document links provided by jenkins-ci still show the old version of the 
table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
update the table,
I am very concerned that this behavior may also cause similar issues in other 
patch submissions that go unnoticed

Can someone please have a look at this?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

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

[Kunzmann, Gerald]

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
update the table, I am very concerned that this behavior may also cause similar 
issues in other patch submissions that go unnoticed….

Can someone please have a look at this?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH Landsberger Strasse 312, 80687 
Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura, Amtsgericht München, HRB 132976


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

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

[Kunzmann, Gerald]

Dear all,

So this issue is easily reproducible. It had again happened today with another 
patch being merged

https://gerrit.opnfv.org/gerrit/24365

We are now back to the old table again :(

We have to find a solution to this problem!!!

Best regards,
Gerald

-Original Message-
From: Kunzmann, Gerald 
Sent: Mittwoch, 25. Januar 2017 13:56
To: 'opnfv-helpd...@rt.linuxfoundation.org' 

Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
update the table, I am very concerned that this behavior may also cause similar 
issues in other patch submissions that go unnoticed….

Can someone please have a look at this?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH Landsberger Strasse 312, 80687 
Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura, Amtsgericht München, HRB 132976


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

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

[Kunzmann, Gerald]

Dear all,

Sorry for another email on this issue:

Today the situation is even more strange:

There is the old alarm table in generated artifacts file: 
http://artifacts.opnfv.org/doctor/docs/requirements/index.html
But the git tree still contains the new table: 
https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst

What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
Ryota had merged the patch,
jenkins-ci has just sent the document links, but there was no specific build 
started. Is this normal/okay?

Best regards,
Gerald

-Original Message-
From: Kunzmann, Gerald 
Sent: Donnerstag, 26. Januar 2017 13:40
To: 'opnfv-helpd...@rt.linuxfoundation.org' 
; 'Fatih Degirmenci' 

Cc: 'opnfv-tech-discuss@lists.opnfv.org' ; 
'r-m...@cq.jp.nec.com' 
Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

So this issue is easily reproducible. It had again happened today with another 
patch being merged

https://gerrit.opnfv.org/gerrit/24365

We are now back to the old table again :(

We have to find a solution to this problem!!!

Best regards,
Gerald

-----Original Message-
From: Kunzmann, Gerald 
Sent: Mittwoch, 25. Januar 2017 13:56
To: 'opnfv-helpd...@rt.linuxfoundation.org' 

Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
up

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

[Kunzmann, Gerald]

Hi Aric,

Thanks for your investigations! I'll do the fix as you have proposed.

If I understand your reply correctly, this issue is limited to opnfvdocs?

Best regards,
Gerald

-Original Message-
From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Donnerstag, 26. Januar 2017 20:54
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org 
#35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

Hi,

Looks like the merge job is doing the wrong thing.

its checking out the patchset, rather than what is in master.
since the patchset is from Dec 28, and does not touch
./docs/requirements/05-implementation.rst (which has been updated
since then)
git does not see a conflict with merging this code.

If you look at the console output for the merge job
https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
its doing this. > git fetch --tags --progress
ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
timeout=15
and it should be just doing a straight clone of whats in master (after
24365 is merged)

For now you can just submit a small change to doctor/docs/whatever and
then merge it, this will get the latest version of all rst files into
artifacts.

I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this
confusing behavior in the future.

Regards,
Aric



On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT
 wrote:
> Dear all,
>
> Sorry for another email on this issue:
>
> Today the situation is even more strange:
>
> There is the old alarm table in generated artifacts file: 
> http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> But the git tree still contains the new table: 
> https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst
>
> What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
> Ryota had merged the patch,
> jenkins-ci has just sent the document links, but there was no specific build 
> started. Is this normal/okay?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Donnerstag, 26. Januar 2017 13:40
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> ; 'Fatih Degirmenci' 
> 
> Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
> ; 'r-m...@cq.jp.nec.com' 
> 
> Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Dear all,
>
> So this issue is easily reproducible. It had again happened today with 
> another patch being merged
>
> https://gerrit.opnfv.org/gerrit/24365
>
> We are now back to the old table again :(
>
> We have to find a solution to this problem!!!
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Mittwoch, 25. Januar 2017 13:56
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> HI Fatih,
>
> Thanks for your quick check. The remerged had helped to bring back the 
> table...
>
> Let's see docs team's reply on it.
>
> I agree gerrit was fine not raising conflict as the changed line in the 
> "editorial" patch was not conflicting with the other patch.
> Still, shouldn't gerrit have just changed that one line instead of also other 
> parts of the file and/or shouldn't gerrit have raised some warning it was 
> changing more than just the one line?
>
> When looking at the diff in gerrit for the "editorial" patch, it does not 
> compare against the latest master, otherwise it would have shown more changes 
> than just this one line. This might have caused the issue?!?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: fatih.degirme...@ericsson.com via RT 
> [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Mittwoch, 25. Januar 2017 13:38
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Hi,
>
> I had a quick look at this and diffed the commits and I see no conflict so 
> Gerrit was fine not raising conflict. (the changed line in 
> 05-implementation.rst in most recent patch is not a conflicting change)
>
> I then tried regenerating the documents by putting remerge as comment to 
> check the doc generation script/job o

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

[Kunzmann, Gerald]

Hi Sofia,

Could you please highlight the "structural changes" that we should implement?

Also, on the ML there had been the question on references in OPNFV documents? 
Was there any decision/solution on it?

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin
Sent: Dienstag, 7. Februar 2017 14:26
To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) 
; opnfv-project-le...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube 
release

To all projects that plans to contribute with documentation to the Danube 
release.

Hi,
As a reminder that documentation is part of the release even this time, 
following email contains some useful information and links.

Since we are moving to read the docs 
(NOTE: this page is still work in progress) for the Danube release some 
structural changes has been made. Please have a look at the wiki page linked 
below to make sure that you store your documentation according to directives.

Wiki
Information on general documentation handling can be found 
here

Milestones relevant for documentation is MS6 and MS10.
MS6 17/2 - Preliminary documentation completed
Documentation outlines or placeholders committed to repo for all project and 
release documentation
MS10 24/3 - Documentation completed
All project and release documentation reviewed and approved.

Since we still haven't manage to establish or communicate a review process for 
release related documentation it is important to always add one or two members 
from the docs project as reviewer on documentation related additions or changes.

Everyone is welcome to join the docs 
meeting held every second 
week.

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

Re: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube release

[Kunzmann, Gerald]

Hi Sofia,

Thanks. I will update for Doctor and Promise.

Best regards,
Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Dienstag, 7. Februar 2017 15:50
To: Kunzmann, Gerald ; TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org) ; 
opnfv-project-le...@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube 
release

Hi Gerald,
The documentation is divided into 3 different entry points/areas so the 
structure will look as following,

/docs/release
 /configguide
 /installation
 /release-notes
/scenarios
  └── scenario.name
/userguide

/docs/developer
/design
/overview
/requirements

/docs/testing

So one more layer is added under /docs/ which will steer to where the 
documents will be generated and presented.

Also, on the ML there had been the question on references in OPNFV documents? 
Was there any decision/solution on it?
Please see answer from Chris on this. We have a docs meeting tomorrow where we 
could have a discussion about this.

BR,
Sofia

From: Kunzmann, Gerald [mailto:kunzm...@docomolab-euro.com]
Sent: den 7 februari 2017 14:35
To: Sofia Wallin ; TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org) ; 
opnfv-project-le...@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube 
release

Hi Sofia,

Could you please highlight the "structural changes" that we should implement?

Also, on the ML there had been the question on references in OPNFV documents? 
Was there any decision/solution on it?

Best regards,
Gerald

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 Sofia Wallin
Sent: Dienstag, 7. Februar 2017 14:26
To: TECH-DISCUSS OPNFV 
(opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>) 
mailto:opnfv-tech-discuss@lists.opnfv.org>>;
 opnfv-project-le...@lists.opnfv.org<mailto:opnfv-project-le...@lists.opnfv.org>
Subject: [opnfv-tech-discuss] [opnfvdocs] Documentation update for Danube 
release

To all projects that plans to contribute with documentation to the Danube 
release.

Hi,
As a reminder that documentation is part of the release even this time, 
following email contains some useful information and links.

Since we are moving to read the docs<http://opnfv.readthedocs.io/en/latest/> 
(NOTE: this page is still work in progress) for the Danube release some 
structural changes has been made. Please have a look at the wiki page linked 
below to make sure that you store your documentation according to directives.

Wiki
Information on general documentation handling can be found 
here<https://wiki.opnfv.org/display/DOC>

Milestones relevant for documentation is MS6 and MS10.
MS6 17/2 - Preliminary documentation completed
Documentation outlines or placeholders committed to repo for all project and 
release documentation
MS10 24/3 - Documentation completed
All project and release documentation reviewed and approved.

Since we still haven't manage to establish or communicate a review process for 
release related documentation it is important to always add one or two members 
from the docs project as reviewer on documentation related additions or changes.

Everyone is welcome to join the docs 
meeting<https://wiki.opnfv.org/display/meetings/OPNFVDOCS> held every second 
week.

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

Re: [opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - Migration to readthedocs

[Kunzmann, Gerald]

Hi Sofia, all,

The current content of the userguide.introduction.rst doesn't at all look like 
the example in 
http://docs.opnfv.org/en/latest/how-to-use-docs/include-documentation.html#include-documentation

vim opnfvdocs/docs/release/userguide.introduction.rst
This opens the text editor. Identify where you want to add the userguide. If 
the userguide is to be added to the toctree, simply include the path to it, 
example:
.. toctree::
:maxdepth: 1

submodules/functest/docs/userguide/index
submodules/bottlenecks/docs/userguide/index
submodules/yardstick/docs/userguide/index


Will opnfvdocs team do the first version of this file according to the 
instructions? Or should individual projects start adding submodules for their 
project?

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin
Sent: Mittwoch, 22. Februar 2017 11:26
To: TECH-DISCUSS OPNFV (opnfv-tech-discuss@lists.opnfv.org) 
; opnfv-project-le...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [opnfvdocs] [opnfv-project-leads] Update - 
Migration to readthedocs

Hello,

As many of you already know, as part of the Danube release we are migrating all 
our documentation to readthedocs, an online documentation service. There are a 
few changes with respect to documentation that everyone should be aware of:

Distinct release, development and testing documentation
As part of the D release, the docs projects is working towards organizing the 
documentation under three distinct banners: release, development and testing, 
as also seen on docs.opnfv.org [1]
We have put together a documentation guide [2] which will help project teams 
understand the changes expected in each project repo.
NOTE: Discussions regarding structure of the page and naming was brought up 
yesterday and are ongoing.

Simplified documentation toolchain
The move to readthedocs has greatly simplified our documentation toolchain. The 
docs project has incorporated each project as a submodule in its repo. Whenever 
content is merged in /docs/, the documentation toolchain shall 
automatically trigger building of the new documentation on readthedocs (allow 
around 15 minutes for the documentation to show after merging). The new doc 
jobs are docs-verify-rtd-{stream} & docs-merge-rtd-{stream}.

Detailed instructions on how to include documentation, validate markup and test 
build (locally) have been mentioned in the 'Include Documentation' [3]

We shall gradually be phasing out the 
artifacts.opnfv.org as part of the migration to 
readthedocs. Project teams are requested to adapt to the new tool chain.
Please let us know if you have questions.
Regards,
OPNFVDOCS Team

[1] http://docs.opnfv.org/en/latest/

[2] http://docs.opnfv.org/en/latest/how-to-use-docs/documentation-guide.html

[3] http://docs.opnfv.org/en/latest/how-to-use-docs/include-documentation.html

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

[opnfv-tech-discuss] [Promise] CfP for OPNFV Summit

[Kunzmann, Gerald]

Dear Promiser's,

As discussed in today's meeting, find an Etherpad for our discussion for 
Promise session(s) at the OPNFV Summit in Bejing in June:

https://etherpad.opnfv.org/p/promise_opnfv_summit_2017

I have already proposed a first session on "Promise + Blazar", as well as a 
Breakout Session in the Design Summit.

Please check. If you have other proposals / ideas, feel free to propose a 
second/third talk.

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

[opnfv-tech-discuss] FW: [openstack-dev] [keystone][defcore][refstack] Removal of the v2.0 API

[Kunzmann, Gerald]

Dear OPNFV’ers,

Please note below announcement from OpenStack on the possibility of removal of 
Keystone V2.0 API.

I guess this may affect some of our projects that still rely on Keystone V2.0.

Best regards,
Gerald

From: Lance Bragstad [mailto:lbrags...@gmail.com]
Sent: Wednesday, March 01, 2017 2:10 PM
To: OpenStack Development Mailing List (not for usage questions) 
mailto:openstack-...@lists.openstack.org>>; 
openstack-operat...@lists.openstack.org
Subject: [openstack-dev] [keystone][defcore][refstack] Removal of the v2.0 API

During the PTG, Morgan mentioned that there was the possibility of keystone 
removing the v2.0 API [0]. This thread is a follow up from that discussion to 
make sure we loop in the right people and do everything by the books.

The result of the session [1] listed the following work items:
- Figure out how we can test the removal and make the job voting (does the 
v3-only job count for this)?
- Reach out to defcore and refstack communities about removing v2.0 (which is 
partially what this thread is doing)

Outside of this thread, what else do we have to do from a defcore perspective 
to make this happen?

Thanks for the time!

[0] https://review.openstack.org/#/c/437667/
[1] https://etherpad.openstack.org/p/pike-ptg-keystone-deprecations
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
User-committee mailing list
user-commit...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [multisite] weekly meeting of Mar.23

[Kunzmann, Gerald]

Dear multisite-Team,

FYI, the arch guide [1] in OpenStack is being rewritten, and the multi-site 
docs that were there are no longer there (see archived manuals in [2])
So there are currently no official docs on multi-site/region in OpenStack. In 
the Telco/NFV meeting it was suggested they could use some help writing those.

[1] https://docs.openstack.org/arch-design/
[2] 
https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/arch-design-to-archive/source

It seems the plan is to rewrite the arch guide piece by piece and they just 
haven't gotten to the multisite part yet, and could probably use some help. 
There is also potentially a NFV section to it.

Is there someone from multi-site team interested to work on this? Maybe you 
could discuss this in your meeting tomorrow.

I am not sure who would be the right person to contact, maybe Heidi from 
OpenStack heidi...@openstack.org?

Best regards,
Gerald


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of joehuang
Sent: Mittwoch, 22. März 2017 06:04
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [multisite]weekly meeting of Mar.23


Hello, team,



HA PTL FuQiao was invited to talk about multi-site requirements in this weekly 
meeting



Mar.23 2017 Agenda:

* CMCC multi-site requirements

* Functest issue.

* E-Release discussion

* OPNFV Beijing summit preparation

* Open discussion


IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM).

Other topics are also welcome in the weekly meeting, please reply in this mail.


Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [release][euphrates] Intent-to-Participate - Promise

[Kunzmann, Gerald]

Dear David, all,

Promise project intends to participate in the upcoming release. Our work will 
mainly focus on upstream development in OpenStack Blazar project. We will also 
do maintenance work on the existing code –where needed- to ensure test cases 
are passing.

Best regards,
Gerald

From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Montag, 27. März 2017 03:57
To: TECH-DISCUSS OPNFV ; 
opnfv-project-leads ; TSC OPNFV 

Cc: Raymond Paik ; Tapio Tallgren 

Subject: [opnfv-project-leads] [release][euphrates] Intent-to-Participate 
window for Euphrates

Team,

I'm excited to announce that the intent-to-participate window will open on 
Monday, March 27, and will remain open until 5 p.m. on April 24 (MS1).

The process is documented 
here, 
but essentially just requires sending an email to the TSC mailing list.  Note 
that your project must have been approved by the TSC before you may join a 
release.

Once you have stated your intent to participate, you must complete your release 
planning by MS1 on April 24.  This includes completing the release plan 
summary.

Please let me know if you have any questions.

David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The Promise team holds a meeting on (biweekly). 
 We use GoToMeeting for audio and IRC for meeting minutes. For further deta
 ils please see: https://wiki.opnfv.org/display/meetings/Promise+Team+Meeti
 ngs\n\nIRC channel: #opnfv-promise\nGoToMeeting: https://global.go
 tomeeting.com/join/144838637\n\n
RRULE:FREQ=WEEKLY;UNTIL=20171026T11Z;INTERVAL=2;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=UTC:20170330T11
DTEND;TZID=UTC:20170330T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170327T090853Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/144838637
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV Summit CFP

[Kunzmann, Gerald]

Dear Brandon, OPNFV Events-Team,

If I want to reserve a room at the OPNFV summit for a project team meeting / 
breakout session, do I also need to request this through the CfP page as 
"breakout session"?

Best regards,
Gerald

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of yunhong jiang
Sent: Dienstag, 21. März 2017 21:12
To: Brandon Wick 
Cc: opnfv-tech-dis. 
Subject: Re: [opnfv-tech-discuss] REMINDER: One Week Left to Submit to OPNFV 
Summit CFP

On Tue, 21 Mar 2017 12:55:25 -0700
Brandon Wick  wrote:

> Hello Jiang,
> 
> Thanks for your question. Please send any future questions to
> eve...@opnfv.org.
> 
> The Design Summit takes place June 12-13 and is where the OPNFV
> technical community will convene to continue working on the E-Release
> and have plenary sessions and project breakouts. It is very focused
> on the OPNFV platform. The Summit Conference takes place Jun 14-15
> and is for the wider NFV ecosystem, featuring keynotes, breakout
> sessions, a technology showcase, networking opportunities, etc. This
> is where the the breakouts will be structured into the six tracks.
> Panels consist of 4 or more speakers in a single session. When in
> doubt, we recommend you submit for the Summit conference as a
> breakout session. From there, our track chairs will be able to make
> further recommendations as needed.

Hi, Brandon,
Thanks for the reply and it's clear now.

--jyh

> 
> Best,
> 
> 
> Brandon Wick
> OPNFV Head of Marketing, The Linux Foundation
> Mobile: +1.917.282.0960  Skype: wick.brandon
> Email / Google Talk: bw...@linuxfoundation.org
> 
> *The OPNFV Summit CFP Closes 3/27!
> *
> 
> On Tue, Mar 21, 2017 at 12:31 PM, yunhong jiang <
> yunhong.ji...@linux.intel.com> wrote:
> 
> > Hi, Brandon,
> > When I try to submit the CFP, I noticed there are two types of
> > the session. One is for Design Summit session and one is for OPNFV
> > Summit session. Are there any key differences of these two? I
> > attended the Openstack summit before and they are quite
> > different there.
> >
> > Also on the Design Summit session, there are two formats called
> > break out session and panel discussion. What's the difference of
> > them? How should I decide which format should my session be?
> >
> > Hope your guide on this, thanks!
> >
> > -jyh
> >
> > On Mon, 20 Mar 2017 07:24:43 -0700
> > Brandon Wick  wrote:
> >
> > > OPNFV Technical Community:
> > >
> > > This is a reminder that the CFP for the OPNFV Summit
> > > , June
> > > 12-15, Beijing, China, closes *Monday, March 27*. We encourage
> > > you to prepare and submit a proposal by the deadline. The six
> > > primary tracks are the following:
> > >
> > >- NFV Applications and Orchestration
> > >- Testing, Infrastructure, and DevOps
> > >- NFV Strategy and End User Stories
> > >- NFV Platform Requirements
> > >- Community and Upstream
> > >- Futures and Research
> > >
> > > *Access the CFP Here
> > >  > details>*
> > >
> > > We look forward to your submissions. If you have any questions,
> > > please email eve...@opnfv.org.
> > >
> > > Best,
> > >
> > > Brandon Wick
> > > OPNFV Head of Marketing, The Linux Foundation
> > > Mobile: +1.917.282.0960  Skype: wick.brandon
> > > Email / Google Talk: bw...@linuxfoundation.org
> >
> >

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] revised schedule for release

[Kunzmann, Gerald]

Dear David, Aric, all,

We had been trying to tag the release as described in the Wiki page, however, 
with no success and the following error message:

opnfv@souville-VirtualBox:~$ git clone 
ssh://kunzm...@gerrit.opnfv.org:29418/promise
Cloning into 'promise'...
remote: Counting objects: 85, done
remote: Finding sources: 100% (13/13)
remote: Total 453 (delta 0), reused 451 (delta 0)
Receiving objects: 100% (453/453), 1.64 MiB | 530.00 KiB/s, done.
Resolving deltas: 100% (112/112), done.
Checking connectivity... done.
opnfv@souville-VirtualBox:~$ cd promise/
opnfv@souville-VirtualBox:~/promise$ git fetch origin
opnfv@souville-VirtualBox:~/promise$ git checkout stable/danube
Branch stable/danube set up to track remote branch stable/danube from origin.
Switched to a new branch 'stable/danube'
opnfv@souville-VirtualBox:~/promise$ git checkout 
92bd641d511dd52ab73122842f616ec2b6fc1c24
Note: checking out '92bd641d511dd52ab73122842f616ec2b6fc1c24'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 92bd641... Update doc structure to better fit release notes:  - 
There is no need for heading "Manual testing"  - Update to user guide abstract
opnfv@souville-VirtualBox:~/promise$ git tag -am "danube.1.RC1" danube.1.RC1
opnfv@souville-VirtualBox:~/promise$ git push origin danube.1.RC1
Counting objects: 1, done.
Writing objects: 100% (1/1), 174 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
remote: Processing changes: refs: 1, done
To 
ssh://kunzm...@gerrit.opnfv.org:29418/promise
 ! [remote rejected] danube.1.RC1 -> danube.1.RC1 (prohibited by Gerrit)
error: failed to push some refs to 
'ssh://kunzm...@gerrit.opnfv.org:29418/promise'


Any idea what went wrong?
Aric, could you kindly tag Promise for us?

Best regards,
Gerald

From: opnfv-project-leads-boun...@lists.opnfv.org 
[mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of David McBride
Sent: Dienstag, 28. März 2017 21:44
To: TECH-DISCUSS OPNFV ; 
opnfv-project-leads 
Cc: Aric Gardner ; Raymond Paik 
; Rudy Grigar ; Tapio 
Tallgren 
Subject: [opnfv-project-leads] [release][danube] revised schedule for release

Team,

The TSC voted this morning to change the release date to Friday, March 31.  I 
will be updating the schedule on the wiki, but here is a summary of what will 
happen this week.

Note:  on the release call this morning, I said that MS9 would be on Wednesday. 
 However, it was pointed out that finishing up the documentation includes 
resolving and closing JIRA tickets, so I decided that it would make more sense 
to schedule it on the same day as the documentation completion.

  *   Wednesday, March 29

 *   MS8 - end of formal testing and data collection

  *   Thursday, March 30

 *   MS9 - JIRA cleanup
 *   MS10 - complete documentation

  *   Friday, March 31, 3 p.m. PDT

 *   PTLs tag 
projects
 *   Note that we are using an "RC" tag, initially, for this release.  You 
can apply this tag while you are completing your final reviews, etc., then once 
you are certain that you are done, then you can apply the "1.0" tag.
David

--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
DESCRIPTION;LANGUAGE=en-US:Update: new dial-in for Promise calls due to cha
 nges in the first OPNFV GTM account.\n\nThe Promise team holds a meeting o
 n (biweekly). We use GoToMeeting for audio and IRC for meeting minutes. Fo
 r further details please see: https://wiki.opnfv.org/display/meetings/Prom
 ise+Team+Meetings\n\nIRC channel: #opnfv-promise\nGoToMeeting: htt
 ps://global.gotomeeting.com/join/391235029 <https://global.gotomeeting.com
 /join/391235029>\n\n
RRULE:FREQ=WEEKLY;UNTIL=20171026T11Z;INTERVAL=2;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=UTC:20170427T11
DTEND;TZID=UTC:20170427T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170419T071152Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] Preparations for summit and cancelation of this week's call

[Kunzmann, Gerald]

Dear Promisers,

Few information and requests:


-  Please review the instance reservation BP draft: 
https://blueprints.launchpad.net/blazar/+spec/new-instance-reservation (if not 
yet done)
Your feedback is appreciated to conclude on this spec drafting.



-  Relevant sessions at the upcoming OpenStack Boston event:

o   May 8th

§  12:05-12:45 - Project Update Blazar

§  13:00-16:00 - Blazar team meeting on Blazar internal features



o   May 9th

§  13:00-14:00 - PROMISE working session in "Republic Ballroom" (tbc)

Would you be available for a dedicated Promise session or would you prefer to 
merge with the Blazar team meeting on Monday?
@Pierre: would merging be an option for you?



o   May 10th

§  9:00-9:40 - Collaboration between Telecom/NFV related groups

§  9:50-10:30 -  Advanced instance scheduling - reservations and preemption

§  11:00-11:40 - Collaboration of OpenStack Blazar and OPNFV Promise for 
meeting NFV resource management requirements

§  17:20-18:00 - Nova Scheduler: Optimizing, Configuring and Deploying NFV 
VNF's on OpenStack



o   May 11th

§  9:00-10/11:00 - Meeting between Blazar and Placement API teams

§  11:00 - OpenStack Operators Telecom/NFV WG



Any session I have missed?



-  I would like to cancel this week's call as I am out of office.

If you have any topics to discuss, please use the mailing list.

Best regards and looking forward to seeing many of you in Boston.
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting - see you in Boston

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
DESCRIPTION;LANGUAGE=en-US:Dear all\,\n\nI would like to cancel the next OP
 NFV Promise online meeting and I am looking forward to meet many of you in
  Boston.\n\nRelevant sessions at the upcoming OpenStack Boston event:\no  
  May 8th\n•   12:05-12:45 – Project Update Blazar\n•   1
 3:00-16:00 – Blazar team meeting on Blazar internal features\n h
 ttps://etherpad.openstack.org/p/blazar-boston-summit\n\no   May 10th\n
 •   9:00-9:40 – Collaboration between Telecom/NFV related groups\n
 •   9:50-10:30 –  Advanced instance scheduling - reservations and 
 preemption\n•   11:00-11:40 – Collaboration of OpenStack Blazar an
 d OPNFV Promise for meeting NFV resource management requirements\n• 
   17:20-18:00 – Nova Scheduler: Optimizing\, Configuring and Deploying N
 FV VNF's on OpenStack\n\no   May 11th\n•   9:00-10/11:00 – Mee
 ting between Blazar and Placement API teams\n•   11:00 – OpenStack
  Operators Telecom/NFV WG\n•   11:00-11:40 - Scheduler Wars: A new h
 ope\n•   15:10-15:50 - Scheduler Wars: Revenge of the split\n\nPleas
 e also note the draft specs for the new instance reservation:\nhtt
 ps://blueprints.launchpad.net/blazar/+spec/new-instance-reservation\nhttps

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Thulasi, A
 run":MAILTO:arun.thul...@hpe.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bachu, Tej
 aswi R":MAILTO:tejaswi.r.ba...@hpe.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Khan, Tari
 q":MAILTO:tariq.k...@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
DESCRIPTION;LANGUAGE=en-US:Dear Promisers\n\nDue to public holiday in most 
 Europe and as most of us had met in the Summit\, I’d like to cancel next
  Promise meeting.\nTalk to you in 2 weeks where we will\, amongst other to
 pics\, discuss about the upcoming OPNFV Summit.\n\nBest regards\,\nGerald\
 n\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20170525T11
DTEND;TZID=UTC:20170525T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20170525T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170519T153406Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:4
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:4
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MIC

[opnfv-tech-discuss] OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
DESCRIPTION;LANGUAGE=en-US:Dear Promise Team\,\n\nI would like to schedule 
 a Promise call this week (due to out of office situation of few team membe
 rs next week).\nI hope you will be able to join.\n\nBest regards\,\nGerald
 \n\n\n
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=UTC:20170601T11
DTEND;TZID=UTC:20170601T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20170608T11
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170529T073446Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:5
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] Nomination of committer promotion for Masahito

[Kunzmann, Gerald]

Dear Promise Team,

as announced in today's Promise meeting I would like to promote Masahito MUROI 
to become a Promise committer.
Masahito has a deep knowledge of the project, its use cases, and the upstream 
Blazar project where he is PTL.

I would like to ask all Promise committers to reply to this email with their 
vote.

Best regards,
Gerald


===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura,
Amtsgericht München, HRB 132976

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
DESCRIPTION;LANGUAGE=en-US:This week’s OPNFV Promise meeting is canceled 
 due to summer break and no urgent topics on the agenda.\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20170803T11
DTEND;TZID=UTC:20170803T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20170803T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170801T082056Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:7
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:7
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
DESCRIPTION;LANGUAGE=en-US:The meeting on  August 17th is canceled due to 
 several team members still on vacation / out of office.\nIf you have any t
 opics to discuss\, pls use the mailing list instead.\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20170817T11
DTEND;TZID=UTC:20170817T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20170817T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170810T144300Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:8
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:8
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [doctor] Doctor project graduation review

[Kunzmann, Gerald]

Dear Carlos,

I have added some initial comments / thoughts to the slideset. I will help 
editing the document later today as well as end of this week.

Best regards,
Gerald

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Carlos 
Gonçalves
Sent: Montag, 21. August 2017 17:02
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] Doctor project graduation review

Doctors,

Please find on [1] a slide deck draft proposing Doctor for project graduation. 
It is publicly editable, so don't be shy -- have a look and contribute :-)

The goal is to have the final deck ready and agreed by next Monday after the 
weekly Doctor call. Ryota will then submit it to TSC for approval.


[1] 
https://docs.google.com/presentation/d/1Ppz4kwjkIxCEyXTUxn3cvEWQpxXXAZx6LeYQYDBT4DU

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

[opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Dear Opnfvdocs-Team,

I have created this table but I am quite unhappy about the narrow, and thus 
long, description column:
http://artifacts.opnfv.org/promise/review/40835/development_manuals/index.html

Is there a way to specify font size for specific tables or change page width 
for specific pages?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
DESCRIPTION;LANGUAGE=en-US:Meeting on Sept 14th is canceled due to OpenStac
 k PTG and ETSI NFV meetings.\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20170914T11
DTEND;TZID=UTC:20170914T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20170914T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20170901T120252Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:9
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Dear Opnfvdocs-Team,

I have not received any feedback on this email, so I'd like to bring it up 
again.
How can I get a different rendering of the HTML page, e.g. similar to the one 
for Euphrates release docs: 
http://artifacts.opnfv.org/opnfvdocs/review/42243/index.html ?

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Freitag, 1. September 2017 13:43
To: 'opnfv-tech-discuss@lists.opnfv.org' 
Subject: [opnfvdocs] Question on font size and page width

Dear Opnfvdocs-Team,

I have created this table but I am quite unhappy about the narrow, and thus 
long, description column:
http://artifacts.opnfv.org/promise/review/40835/development_manuals/index.html

Is there a way to specify font size for specific tables or change page width 
for specific pages?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Hi Sofia,

thanks for the feedback and explanation. I will then merge the patch and check 
its result on docs.opnfv.org.

Best regards,
Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Dienstag, 3. Oktober 2017 17:47
To: SULLIVAN, BRYAN L (BRYAN L) ; Kunzmann, 
Gerald ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Bryan and Gerald,
The artifact urls doesn’t give you complete fair view of the rendering in 
comparison to the actual result on docs.opnfv.org.

We currently have the old toolchain running which give you a somewhat 
reasonable idea on the final result. This is unfortunately not possible to do 
with readthedocs since the builds are triggered when something is merged.
And that is why we have chosen to keep the artifact urls for now.

If you look at the Promise 
documentation<http://docs.opnfv.org/en/stable-danube/submodules/promise/docs/development/requirements/index.html>
 for example on the docs.opnfv.org you can see that you have a different result.

Best regards,
Sofia

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "SULLIVAN, BRYAN L (BRYAN L)" 
mailto:bryan.sulli...@research.att.com>>
Date: Monday, 2 October 2017 at 18:03
To: Gerald Kunzmann 
mailto:kunzm...@docomolab-euro.com>>, OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

I agree, that for use on the web that the presentation should:
1)  use the full width of the screen
2)  offer the ability to specify column-width as in CSS (percent, or pixels)
3)  if possible offer the ability to minimize the navigation links on the 
left - that might be something we could also hack via CSS

Thanks,
Bryan Sullivan | AT&T

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 Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Dear Opnfvdocs-Team,

I have not received any feedback on this email, so I’d like to bring it up 
again.
How can I get a different rendering of the HTML page, e.g. similar to the one 
for Euphrates release docs: 
http://artifacts.opnfv.org/opnfvdocs/review/42243/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__artifacts.opnfv.org_opnfvdocs_review_42243_index.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=T8qRkPkBjktOhUf08PN0qN9XOB4vp1ZeLePAZ9gk25I&e=>
 ?

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Freitag, 1. September 2017 13:43
To: 'opnfv-tech-discuss@lists.opnfv.org' 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfvdocs] Question on font size and page width

Dear Opnfvdocs-Team,

I have created this table but I am quite unhappy about the narrow, and thus 
long, description column:
http://artifacts.opnfv.org/promise/review/40835/development_manuals/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__artifacts.opnfv.org_promise_review_40835_development-5Fmanuals_index.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=TWvhDX5081sNU52DukcNjUOSQ44D2xwL_LEg7mk3qUM&e=>

Is there a way to specify font size for specific tables or change page width 
for specific pages?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: 
http://www.docomoeurolabs.de<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.docomoeurolabs.de_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=F10hPh_CrOu2AVVsN-VGOAyAwF0A35tfVFPcJlTBeXg&e=>

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Aron Wahl:
 MAILTO:a.w...@f5.com
DESCRIPTION;LANGUAGE=en-US:Dear all\,\n\nLet me propose to cancel this week
 ’s meeting as I will be traveling tomorrow.\nIf you have any topics\, pl
 ease start a thread on the mailing list.\n\nBest regards\,\nGerald\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20171012T11
DTEND;TZID=UTC:20171012T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20171012T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171011T152706Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:10
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Hi Sofia,

the docs.opnfv.org seems to contain the official release documentation. What 
about other development documentation under /docs/development/ ?
Do I have to do some manual action to have such documents included in the 
readthedocs?
E.g. where/how can I get this manual 
https://git.opnfv.org/promise/tree/docs/development/manuals on 
http://docs.opnfv.org ?

Best regards,
Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Dienstag, 3. Oktober 2017 17:47
To: SULLIVAN, BRYAN L (BRYAN L) ; Kunzmann, 
Gerald ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Bryan and Gerald,
The artifact urls doesn’t give you complete fair view of the rendering in 
comparison to the actual result on docs.opnfv.org.

We currently have the old toolchain running which give you a somewhat 
reasonable idea on the final result. This is unfortunately not possible to do 
with readthedocs since the builds are triggered when something is merged.
And that is why we have chosen to keep the artifact urls for now.

If you look at the Promise 
documentation<http://docs.opnfv.org/en/stable-danube/submodules/promise/docs/development/requirements/index.html>
 for example on the docs.opnfv.org you can see that you have a different result.

Best regards,
Sofia

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "SULLIVAN, BRYAN L (BRYAN L)" 
mailto:bryan.sulli...@research.att.com>>
Date: Monday, 2 October 2017 at 18:03
To: Gerald Kunzmann 
mailto:kunzm...@docomolab-euro.com>>, OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

I agree, that for use on the web that the presentation should:
1)  use the full width of the screen
2)  offer the ability to specify column-width as in CSS (percent, or pixels)
3)  if possible offer the ability to minimize the navigation links on the 
left - that might be something we could also hack via CSS

Thanks,
Bryan Sullivan | AT&T

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 Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Dear Opnfvdocs-Team,

I have not received any feedback on this email, so I’d like to bring it up 
again.
How can I get a different rendering of the HTML page, e.g. similar to the one 
for Euphrates release docs: 
http://artifacts.opnfv.org/opnfvdocs/review/42243/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__artifacts.opnfv.org_opnfvdocs_review_42243_index.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=T8qRkPkBjktOhUf08PN0qN9XOB4vp1ZeLePAZ9gk25I&e=>
 ?

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Freitag, 1. September 2017 13:43
To: 'opnfv-tech-discuss@lists.opnfv.org' 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfvdocs] Question on font size and page width

Dear Opnfvdocs-Team,

I have created this table but I am quite unhappy about the narrow, and thus 
long, description column:
http://artifacts.opnfv.org/promise/review/40835/development_manuals/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__artifacts.opnfv.org_promise_review_40835_development-5Fmanuals_index.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=TWvhDX5081sNU52DukcNjUOSQ44D2xwL_LEg7mk3qUM&e=>

Is there a way to specify font size for specific tables or change page width 
for specific pages?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: 
http://www.docomoeurolabs.de<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.docomoeurolabs.de_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=F10hPh_CrOu2AVVsN-VGOAyAwF0A35tfVFPcJlTBeXg&e=>

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page width

[Kunzmann, Gerald]

Hi Sofia,

thanks for the clarification.

I just realized that there are changes e.g. on the font size and font type for 
Euphrates compared to Danube.

http://docs.opnfv.org/en/stable-euphrates/submodules/promise/docs/development/requirements/index.html
http://docs.opnfv.org/en/stable-danube/submodules/promise/docs/development/requirements/index.html

To be honest I preferred the smaller font size used in Danube documentation, 
whereas I prefer the new color scheme.
What was the reason for change?

Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Mittwoch, 18. Oktober 2017 13:18
To: Kunzmann, Gerald ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Gerald,
The purpose and structure of the ‘Developer’ section on docs.opnfv.org is still 
a work in progress.
However, recommended structure for your documentation under docs/development/ 
is found here, 
http://docs.opnfv.org/<http://docs.opnfv.org/en/latest/how-to-use-docs/documentation-guide.html#document-structure-and-contribution>

When you have your structure is in place links needs to be added manually to 
opnfvdocs/docs/featureproject.rst.
This can either be done by the projects or someone from the docs team.

BR,
Sofia

From: Gerald Kunzmann 
mailto:kunzm...@docomolab-euro.com>>
Date: Wednesday, 18 October 2017 at 10:51
To: Sofia Wallin mailto:sofia.wal...@ericsson.com>>, 
OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Sofia,

the docs.opnfv.org seems to contain the official release documentation. What 
about other development documentation under /docs/development/ ?
Do I have to do some manual action to have such documents included in the 
readthedocs?
E.g. where/how can I get this manual 
https://git.opnfv.org/promise/tree/docs/development/manuals on 
http://docs.opnfv.org ?

Best regards,
Gerald

From: Sofia Wallin [mailto:sofia.wal...@ericsson.com]
Sent: Dienstag, 3. Oktober 2017 17:47
To: SULLIVAN, BRYAN L (BRYAN L) 
mailto:bryan.sulli...@research.att.com>>; 
Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Hi Bryan and Gerald,
The artifact urls doesn’t give you complete fair view of the rendering in 
comparison to the actual result on docs.opnfv.org.

We currently have the old toolchain running which give you a somewhat 
reasonable idea on the final result. This is unfortunately not possible to do 
with readthedocs since the builds are triggered when something is merged.
And that is why we have chosen to keep the artifact urls for now.

If you look at the Promise 
documentation<http://docs.opnfv.org/en/stable-danube/submodules/promise/docs/development/requirements/index.html>
 for example on the docs.opnfv.org you can see that you have a different result.

Best regards,
Sofia

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "SULLIVAN, BRYAN L (BRYAN L)" 
mailto:bryan.sulli...@research.att.com>>
Date: Monday, 2 October 2017 at 18:03
To: Gerald Kunzmann 
mailto:kunzm...@docomolab-euro.com>>, OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

I agree, that for use on the web that the presentation should:
1)  use the full width of the screen
2)  offer the ability to specify column-width as in CSS (percent, or pixels)
3)  if possible offer the ability to minimize the navigation links on the 
left - that might be something we could also hack via CSS

Thanks,
Bryan Sullivan | AT&T

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 Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [opnfvdocs] Question on font size and page 
width

Dear Opnfvdocs-Team,

I have not received any feedback on this email, so I’d like to bring it up 
again.
How can I get a different rendering of the HTML page, e.g. similar to the one 
for Euphrates release docs: 
http://artifacts.opnfv.org/opnfvdocs/review/42243/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__artifacts.opnfv.org_opnfvdocs_review_42243_index.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=VyrWwNQYqeC5aohO6lzmchhAxiDc4Kmxeh58IzjcQx8&s=T8qRkPkBjktOhUf08PN0qN9XOB4vp1ZeLePAZ9gk25I&e=>
 ?

Best regards,
Gerald

From: Kunzmann, Gerald
Sent: Freitag, 1. September 2017 13:43
To: 'opnfv-tech-discuss@lists.opnfv.org' 
mailto

[opnfv-tech-discuss] [opnfvdocs] Online Sphinx Editor

[Kunzmann, Gerald]

HI Sofia,

this is the online Sphinx editor I was referring to in Stockholm:
https://livesphinx.herokuapp.com

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de

Managing Directors (Geschaeftsfuehrer):
Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata, 
Takaaki Sato, Junichi Igarashi
Amtsgericht Müchen, HRB 132976

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

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Csatari, G
 ergely (Nokia - HU/Budapest)":MAILTO:gergely.csat...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Maria Toer
 oe:MAILTO:maria.toe...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Vei
 tch:MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bernier, D
 aniel":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Charles Ha
 le:MAILTO:charlie.h...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Prashant S
 unkari:MAILTO:p.sunk...@f5.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Juraj Link
 es -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco):MAILTO:jlin...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ahmed Elbo
 rnou (amaged):MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Marco Varl
 ese:MAILTO:marco.varl...@suse.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Piyush Sar
 wal:MAILTO:psar...@us.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bharat Bhu
 shan:MAILTO:bharat.bhus...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Hesham ElB
 akoury:MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rabi, Abde
 l":MAILTO:abdel.r...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON, AL
 FRED C (AL)":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lawrence L
 amers:MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nagananda 
 Chumbalkar:MAILTO:nchumbal...@lenovo.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pierre Lyn
 ch:MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Soumya Sha
 nkar Sardar:MAILTO:soumya.shankar.sar...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Aron Wahl:
 MAILTO:a.w...@f5.com
DESCRIPTION;LANGUAGE=en-US:Canceled due to most committers not available th
 is week.\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20171026T11
DTEND;TZID=UTC:20171026T12
UID:04008200E00074C5B7101A82E00810B4E5E6E9A6D201000
 010007CA1B4BED81343459CFC20419236D853
RECURRENCE-ID;TZID=UTC:20171026T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171026T063934Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:11
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:11
X-MICROSOFT-CDO-OWNERAPPTID:-1684326431
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] Proposed new meeting time during winter

[Kunzmann, Gerald]

Dear Promiser’s,

 

I propose to have the Promise meetings during winter time at 11:00am UTC,
12:00 CET, 20:00 JST starting the bi-weekly meetings from this week Nov
16th.

Is there any objection from any of the regular participants? If not, I will
update the OPNFV meetings calendar accordingly and send a meeting invite via
the ML.

 

Best regards,

Gerald

 

=== 
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH
Landsberger Strasse 312, 80687 Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300

Web:   http://www.docomoeurolabs.de 
 

Managing Directors (Geschaeftsfuehrer):

Atsushi Takeshita, Takatoshi Okagawa, Dr. Thomas Walter, Hisahiro Hamahata,
Takaaki Sato, Junichi Igarashi 

Amtsgericht Müchen, HRB 132976

 



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The Promise team holds a meeting on (biweekly). 
 We use GoToMeeting for audio and IRC for meeting minutes. For further deta
 ils please see: https://wiki.opnfv.org/display/meetings/Promise+Team+Meeti
 ngs\n\nIRC channel: #opnfv-promise\nGoToMeeting: https://global.go
 tomeeting.com/join/391235029 <https://global.gotomeeting.com/join/39123502
 9>\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180322T10Z;INTERVAL=2;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=W. Europe Standard Time:20171116T11
DTEND;TZID=W. Europe Standard Time:20171116T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171114T104216Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Canceled due to Christmas and Year End season\n\
 n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=W. Europe Standard Time:20171228T11
DTEND;TZID=W. Europe Standard Time:20171228T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
RECURRENCE-ID;TZID=W. Europe Standard Time:20171228T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171114T104314Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The Promise team holds a meeting on (biweekly). 
 We use GoToMeeting for audio and IRC for meeting minutes. For further deta
 ils please see: https://wiki.opnfv.org/display/meetings/Promise+Team+Meeti
 ngs\n\nIRC channel: #opnfv-promise\nGoToMeeting: https://global.go
 tomeeting.com/join/391235029 <https://global.gotomeeting.com/join/39123502
 9>\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180322T11Z;INTERVAL=2;BYDAY=TH;WKST=MO
SUMMARY;LANGUAGE=en-US:OPNFV Promise meeting
DTSTART;TZID=UTC:20171116T11
DTEND;TZID=UTC:20171116T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171116T100544Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:11
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:11
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Rajesh Kum
 ar Tewari:MAILTO:rajesh.tew...@hsc.com
DESCRIPTION;LANGUAGE=en-US:Christmas and New Year vacations\n\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20171228T11
DTEND;TZID=UTC:20171228T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
RECURRENCE-ID;TZID=UTC:20171228T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171116T100649Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:12
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:12
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jerome Tol
 let (jtollet):MAILTO:jtol...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Rajesh Kum
 ar Tewari:MAILTO:rajesh.tew...@hsc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ferriter, 
 Cian":MAILTO:cian.ferri...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
DESCRIPTION;LANGUAGE=en-US:Dear all\,\n\nWe have only few Promise updates:\
 n\n* Plugfest: Fatih talked to Promise/Blazar about next steps for XCI\n  
- Student (Taseer) will work on this\; Bertrand will support\n\
 n* Blazar:\n - Code review meeting on Tuesday with good progre
 ss:\n   http://eavesdrop.openstack.org/irclogs/%23
 openstack-blazar/%23openstack-blazar.2017-12-12.log.html\n - Q
 ueens Rel. 2: one patch under review\n   https://r
 eview.openstack.org/#/c/526616/\n\n\nTherefore\, I propose to cancel today
 ’s call. Sorry for the short notice.\nThe next meeting will be on Januar
 y 11th.\n\nThanks to the whole team for your work and support during 2017.
 \nHave a nice Christmas and New Year’s season and wishing you a good sta
 rt into 2018.\n\nGerald\n
SUMMARY;LANGUAGE=en-US:Canceled: OPNFV Promise meeting
DTSTART;TZID=UTC:20171214T11
DTEND;TZID=UTC:20171214T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
RECURRENCE-ID;TZID=UTC:20171214T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20171214T103057Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:13
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:13
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Abgesagt: OPNFV Promise meeting

[Kunzmann, Gerald]

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
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Rajesh Kum
 ar Tewari:MAILTO:rajesh.tew...@hsc.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ferriter, 
 Cian":MAILTO:cian.ferri...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gabor Hal
 ász:MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Frattura, 
 David":MAILTO:david.fratt...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jerome Tol
 let (jtollet):MAILTO:jtol...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Raúl Álv
 arez Pinilla:MAILTO:raul.alvarez.pini...@outlook.com
DESCRIPTION;LANGUAGE=de-DE:Canceld as per agreement in last meeting due to 
 conflicting meetings\n\n
SUMMARY;LANGUAGE=de-DE:Abgesagt: OPNFV Promise meeting
DTSTART;TZID=UTC:20180125T11
DTEND;TZID=UTC:20180125T12
UID:04008200E00074C5B7101A82E0083084C8633D5DD301000
 01000F78C70F85DAA2443984DCE41A3127AA2
RECURRENCE-ID;TZID=UTC:20180125T11
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20180112T144248Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:15
LOCATION;LANGUAGE=de-DE:https://global.gotomeeting.com/join/391235029
X-MICROSOFT-CDO-APPT-SEQUENCE:15
X-MICROSOFT-CDO-OWNERAPPTID:-1076971551
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Dear Ryota,

-3 hours would be 12am in Europe during winter time.
-2 hours is 1pm in Europe.

Both options somehow overlap with my usual lunch time, however, both options
would be fine for me (small preference for -3) and would even allow me to
join the meetings more regular.

Best regards,
Gerald

-Ursprüngliche Nachricht-
Von: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] Im Auftrag von Ryota
Mibu
Gesendet: Dienstag, 16. Januar 2018 19:14
An: opnfv-tech-discuss@lists.opnfv.org
Betreff: [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. During the last meeting, -3 hour
option seems to be good, but I found that is lunch time in CET. So, now I
propose -2 hour option.

 
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180122T12&ah=1

Please let me know your availability and thoughts by this Thursday. If there
is no problem, we'll shift time slot from the next meeting on Jan 22th.


BR,
Ryota


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


smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Dear Carlos,

I would like to complement on this and thank you for all the support and
engagement in the Doctor project and beyond.

I wish you all the best for your private and professional future.

Unfortunately, I will not be able to attend the PTG this time; let's share a
beer at the next occasion.

Best regards,
Gerald

-Ursprüngliche Nachricht-
Von: opnfv-tsc-boun...@lists.opnfv.org
[mailto:opnfv-tsc-boun...@lists.opnfv.org] Im Auftrag von khan ashiq
Gesendet: Montag, 22. Januar 2018 09:37
An: Carlos Gon?alves 
Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Betreff: Re: [opnfv-tsc] [doctor] Stepping down

Dear Carlos,

You had been an integral part of the Doctor team. 
Without your enormous contribution, Doctor wouldn't have been where it is
today.

Wishing you all the best in your future endevour.

Thank you and best regards,
Ashiq

Ashiq KHAN
NTT DOCOMO, INC.
Mobile: +81 90 8032 6542

- Original Message -
From: Carlos Gon?alves 
To: opnfv-tech-discuss@lists.opnfv.org, opnfv-...@lists.opnfv.org
Sent: Monday, January 22, 2018 5:22 PM
Subject: [opnfv-tsc] [doctor] Stepping down

> Hi Doctor team, OPNFV TSC,
> 
> Due to a change in my professional affiliation I stopped contributing 
> to the project. I don't think my current position will realistically 
> give me enough time to pursue other interests in OPNFV. Therefore, I 
> would like to step down and resign from the role of committer.
> 
> I would like to express my sincere gratitude for having had the 
> opportunity to meet and work alongside many talented people in the 
> Doctor project and in OPNFV in general.
> 
> In case you're attending the OpenStack Rocky PTG in Dublin next month, 
> drop me a note and let's grab a beer (or two).
> 
> LinkedIn: https://www.linkedin.com/in/carloseduardogoncalves/
> 
> All the best to you all!
> 
> Cheers,
> Carlos
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 


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


smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Abgesagt: OPNFV Promise meeting

[Kunzmann, Gerald]

smime.p7m
Description: S/MIME encrypted message
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Hi Ryota,

 

thanks for your great support and commitment to the project. You did a
really great job.

 

I remember well many milestones of the project, including the OpenStack
Boston keynote:



 

It is good news that you will be able to remain a core member of the
project.

 

Best regards,

Gerald 

 

-Ursprüngliche Nachricht-
Von: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] Im Auftrag von Ryota
Mibu
Gesendet: Mittwoch, 14. März 2018 18:23
An: opnfv-tech-discuss@lists.opnfv.org
Betreff: [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&D phase for
fault management. We are now maintaining testing code internally, although
there are new test cases and improvements we are working on. The scope of
Doctor project includes maintenance use case, as the target feature can be
commonly used to provide state of virtualized resource to VIM consumers from
monitoring of the underlying infrastructure.

 

Tomi is one of original members joining from the project creation. As you
know, he brings valuable architecture views to this project and has been
working on maintenance specification quite a long time. He has already
reached out multiple upstream projects for design discussion, and also led
the series of maintenance PoC development.

 

Doctors, please vote on this change.

 

 
https://gerrit.opnfv.org/gerrit/53807

 

Thank you all for your great support, I've really enjoyed my time as the
PTL. I'll remain the project though. :)

 

 

Best regards,

Ryota

 

 

___

opnfv-tech-discuss mailing list

 
opnfv-tech-discuss@lists.opnfv.org

 
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[Kunzmann, Gerald]

Hi Tomi,

Congratulations. We are looking forward to "phase 2" of the Doctor project
with you as PTL.

Best regards,
Gerald

-Ursprüngliche Nachricht-
Von: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] Im Auftrag von Juvonen,
Tomi (Nokia - FI/Espoo)
Gesendet: Donnerstag, 15. März 2018 07:21
An: Ryota Mibu ; opnfv-tech-discuss@lists.opnfv.org
Betreff: Re: [opnfv-tech-discuss] [doctor] replacement of Doctor PTL for new
team formation

Hi Ryota and Doctors,

Thank you for the nomination. You have done a great job leading the Doctor
project and we have achieved a lot thanks to that. It will be an honor to
continue the work towards fulfilling also the maintenance use case and other
challenges.

Besides the maintenance, future challenges in the project could include
compliancy testing for infrastructure and application/VNFM side towards
Doctor. Also we have till now focused on virtual machines, but should move
to support containers too.

Best regards,
Tomi

> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss- boun...@lists.opnfv.org] On Behalf Of 
> Ryota Mibu
> Sent: Wednesday, March 14, 2018 7:23 PM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [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&D 
> phase for fault management. We are now maintaining testing code 
> internally, although there are new test cases and improvements we are 
> working on. The scope of Doctor project includes maintenance use case, 
> as the target feature can be commonly used to provide state of 
> virtualized resource to VIM consumers from monitoring of the underlying
infrastructure.
> 
> Tomi is one of original members joining from the project creation. As 
> you know, he brings valuable architecture views to this project and 
> has been working on maintenance specification quite a long time. He 
> has already reached out multiple upstream projects for design 
> discussion, and also led the series of maintenance PoC development.
> 
> Doctors, please vote on this change.
> 
> https://gerrit.opnfv.org/gerrit/53807
> 
> Thank you all for your great support, I've really enjoyed my time as 
> the PTL. I'll remain the project though. :)
> 
> 
> Best regards,
> Ryota
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] OPNFV Promise meeting canceled

[Kunzmann, Gerald]

Due to multiple core team members out of office, I suggest to cancel the
next meeting on March 22nd.

 

Best regards,

Gerald

 



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] Resource Reservation - Breakout Session - ONS

[Kunzmann, Gerald]

Dear all interested in Resource Reservation,

 

There will be a Promise/Blazar breakout session in ONS next week. Everyone
interested in the resource reservation feature and the two projects is
welcome to join. 

 

Meeting dates:

Tuesday March 27th

10:15 -> 11:15 PDT

Meeting room: K-Town room

 

Topics include (not limited to):

*   Update on OpenStack Blazar project (what is available in the latest
release; which features will be available next)
*   XCI Integration for Promise/Blazar

 

See also the Etherpad page:

 
https://etherpad.opnfv.org/p/ons_devforum_promise_blazar

 

Best regards,

Gerald

 



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Promise] Next Promise meeting

[Kunzmann, Gerald]

Dear all,

 

we had the F2F meeting last week at ONS so I propose to have the next
Promise meeting next week THU April 12th.

On the agenda for next week, we would discuss topics/participation for
Gambia release.

 

As summer time had started, I propose to start the meeting at 9:00 UTC /
11:00 CET / 18:00 JST. Would that work for everyone? If not, please let us
know by latest MON April 9th and propose a new time.

 

Best regards,

Gerald



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=de-DE:The Promise <https://wiki.opnfv.org/display/prom
 ise/Promise> team holds a meeting on (biweekly). We use ZOOM for audio and
  IRC for meeting minutes.\n\n  *   IRC channel: #opnfv-promise<http://webc
 hat.freenode.net/?channels=%23opnfv-promise>\n  *   Zoom: https://zoom.us/
 j/5014627785(1st Zoom account)\n\n  *   Bi-Weekly on Thursdays\n  *   New 
 meeting times during summer (starting from April 12th) at 9am UTC (11:00 E
 urope\, 18:00 Japan)\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180927T09Z;INTERVAL=1;BYDAY=TH;WKST=MO
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
SUMMARY;LANGUAGE=de-DE:Promise meeting
DTSTART;TZID=W. Europe Standard Time:20180412T11
DTEND;TZID=W. Europe Standard Time:20180412T12
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180410T095615Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=de-DE:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=de-DE:The Promise <https://wiki.opnfv.org/display/prom
 ise/Promise> team holds a meeting on (biweekly). We use ZOOM for audio and
  IRC for meeting minutes.\n\n  *   IRC channel: #opnfv-promise<http://webc
 hat.freenode.net/?channels=%23opnfv-promise>\n  *   Zoom: https://zoom.us/
 j/5014627785(1st Zoom account)\n\n  *   Bi-Weekly on Thursdays\n  *   New 
 meeting times during summer (starting from April 12th) at 9am UTC (11:00 E
 urope\, 18:00 Japan)\n\n
RRULE:FREQ=WEEKLY;UNTIL=20180927T09Z;INTERVAL=2;BYDAY=TH;WKST=MO
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
SUMMARY;LANGUAGE=de-DE:Promise meeting
DTSTART;TZID=W. Europe Standard Time:20180412T11
DTEND;TZID=W. Europe Standard Time:20180412T12
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180416T102817Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:26
LOCATION;LANGUAGE=de-DE:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:26
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [opnfv-tsc] [release][gambia][Promise] Intent to Participate in the OPNFV Gambia Release

[Kunzmann, Gerald]

Dear David, all,



Promise project intends to participate in the Gambia release following the 
continuous delivery track.

The release plan for Promise will be available by MS1. Our main activity will 
be to integrate OpenStack Blazar into the release.



Best regards,

Gerald



On Thu, Apr 12, 2018 at 3:36 PM, David McBride mailto:dmcbr...@linuxfoundation.org> > wrote:

Team,



Tomorrow (April 13) marks the opening of the intent-to-participate window for 
the Gambia release (i.e. MS0).  Please find the procedure 
 here. 
The window closes as of MS1 on May 11.



NEW FOR GAMBIA. PLEASE READ CAREFULLY.

As you probably know by now, we are supporting two release tracks for Gambia: 
1) traditional (i.e., the process we've been using) and 2) continuous delivery 
(as implemented by XCI and Apex).  So, in addition to the usual procedure 
found in the link above.  Please let me know which release track you intend to 
participate in by including one of the following statements in your intent to 
participate notification:

1.  We intend to follow the traditional track.
2.  We intend to follow the continuous delivery track
3.  We intend to follow both the traditional track and the continuous 
delivery 
track

Also, please remember that if you are planning a new project for the Gambia 
release, you have two weeks to submit your proposal to the TSC and still have 
time to be approved and to join the release before the intent-to-participate 
window closes.



Let me know if you have questions.  Thanks.



David




-- 

David McBride

Release Manager, OPNFV

Mobile:   +1.805.276.8018

Email/Google Talk:   
dmcbr...@linuxfoundation.org

Skype: davidjmcbride1

IRC: dmcbride







-- 

David McBride

Release Manager, OPNFV

Mobile:   +1.805.276.8018

Email/Google Talk:   
dmcbr...@linuxfoundation.org

Skype: davidjmcbride1

IRC: dmcbride



smime.p7s
Description: S/MIME cryptographic signature
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Abgesagt: Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SULLIVAN, 
 BRYAN L (BRYAN L)":MAILTO:bryan.sulli...@research.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ketchum, B
 rian":MAILTO:brian.ketc...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Arif Khan:
 MAILTO:a...@voereir.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Souville, 
 Bertrand":MAILTO:souvi...@docomolab-euro.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tomasini, 
 Lorenzo":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=pierre.lyn
 c...@keysight.com:MAILTO:pierre.ly...@keysight.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nicolas Bo
 uthors:MAILTO:nicolas.bouth...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jamil.chaw
 k...@orange.com:MAILTO:jamil.cha...@orange.com
DESCRIPTION;LANGUAGE=de-DE:Dear all\,\nSome team members are not available 
 this week so I propose to cancel the meeting this week.\n\nBest regards\,\
 nGerald\n\n
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
RECURRENCE-ID;TZID=W. Europe Standard Time:20180524T11
SUMMARY;LANGUAGE=de-DE:Abgesagt: Promise meeting
DTSTART;TZID=W. Europe Standard Time:20180524T11
DTEND;TZID=W. Europe Standard Time:20180524T12
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20180522T095611Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:27
LOCATION;LANGUAGE=de-DE:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:27
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Abgesagt: Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Canio Cill
 is:MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SULLIVAN, 
 BRYAN L (BRYAN L)":MAILTO:bryan.sulli...@research.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ketchum, B
 rian":MAILTO:brian.ketc...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Arif Khan:
 MAILTO:a...@voereir.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Souville, 
 Bertrand":MAILTO:souvi...@docomolab-euro.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tomasini, 
 Lorenzo":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=pierre.lyn
 c...@keysight.com:MAILTO:pierre.ly...@keysight.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nicolas Bo
 uthors:MAILTO:nicolas.bouth...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jamil.chaw
 k...@orange.com:MAILTO:jamil.cha...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Siddharth 
 Gogar:MAILTO:siddharth.go...@flex.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Laporte, L
 aurent [CTO]":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Elsie Wahl
 ig:MAILTO:ewah...@qti.qualcomm.com
DESCRIPTION;LANGUAGE=de-DE:The Promise <https://wiki.opnfv.org/display/prom
 ise/Promise> team holds a meeting on (biweekly). We use ZOOM for audio and
  IRC for meeting minutes.\n\n  *   IRC channel: #opnfv-promise<http://webc
 hat.freenode.net/?channels=%23opnfv-promise>\n  *   Zoom: https://zoom.us/
 j/5014627785(1st Zoom account)\n\n  *   Bi-Weekly on Thursdays\n  *   New 
 meeting times during summer (starting from April 12th) at 9am UTC (11:00 E
 urope\, 18:00 Japan)\n\n
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
RECURRENCE-ID;TZID=W. Europe Standard Time:20180621T11
SUMMARY;LANGUAGE=de-DE:Abgesagt: Promise meeting
DTSTART;TZID=W. Europe Standard Time:20180621T11
DTEND;TZID=W. Europe Standard Time:20180621T12
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20180614T200121Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:28
LOCATION;LANGUAGE=de-DE:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:28
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Canceled: Promise meeting

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tallgren, 
 Tapio (Nokia - FI/Espoo)":MAILTO:tapio.tallg...@nokia.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SULLIVAN, 
 BRYAN L (BRYAN L)":MAILTO:bryan.sulli...@research.att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ketchum, B
 rian":MAILTO:brian.ketc...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Arif Khan:
 MAILTO:a...@voereir.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Souville, 
 Bertrand":MAILTO:souvi...@docomolab-euro.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tomasini, 
 Lorenzo":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Alam, Taim
 oor":MAILTO:taimoor.a...@tum.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kedalagudd
 e, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vul, Alex":
 MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=pierre.lyn
 c...@keysight.com:MAILTO:pierre.ly...@keysight.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Nicolas Bo
 uthors:MAILTO:nicolas.bouth...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Bob Monkma
 n:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jamil.chaw
 k...@orange.com:MAILTO:jamil.cha...@orange.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Siddharth 
 Gogar:MAILTO:siddharth.go...@flex.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Laporte, L
 aurent [CTO]":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Elsie Wahl
 ig:MAILTO:ewah...@qti.qualcomm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Sean Campb
 ell:MAILTO:scamp...@qti.qualcomm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Cathy Zhan
 g:MAILTO:cathy.h.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Michal Ros
 tecki:MAILTO:mroste...@suse.com
DESCRIPTION;LANGUAGE=en-US:As discussed with the other team members\, today
 ’s meeting is canceled. Sorry for the short notice.\n\n
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
RECURRENCE-ID;TZID=W. Europe Standard Time:20180719T11
SUMMARY;LANGUAGE=en-US:Canceled: Promise meeting
DTSTART;TZID=W. Europe Standard Time:20180719T11
DTEND;TZID=W. Europe Standard Time:20180719T12
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20180719T082653Z
TRANSP:TRANSPARENT
STATUS:CANCELLED
SEQUENCE:29
LOCATION;LANGUAGE=en-US:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:29
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR

[opnfv-tech-discuss] Promise meeting - re-scheduled by 1 week

[Kunzmann, Gerald]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Kunzmann, Gerald":MAILTO:kunzm...@docomolab-euro.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=TECH-DISCU
 SS OPNFV:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The Promise <https://wiki.opnfv.org/display/prom
 ise/Promise> team holds a meeting on (biweekly). We use ZOOM for audio and
  IRC for meeting minutes.\n\n  *   IRC channel: #opnfv-promise<http://webc
 hat.freenode.net/?channels=%23opnfv-promise>\n  *   Zoom: https://zoom.us/
 j/5014627785(1st Zoom account)\n\n  *   Bi-Weekly on Thursdays\n  *   New 
 meeting times during summer (starting from April 12th) at 9am UTC (11:00 E
 urope\, 18:00 Japan)\n\n
UID:04008200E00074C5B7101A82E00830BAC9C9C2D0D301000
 010004DAD2132E0A2EF4EBFB82AD89DC1CE74
RECURRENCE-ID;TZID=W. Europe Standard Time:20180802T11
SUMMARY;LANGUAGE=en-US:Promise meeting - re-scheduled by 1 week
DTSTART;TZID=W. Europe Standard Time:20180809T11
DTEND;TZID=W. Europe Standard Time:20180809T12
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180801T081644Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:31
LOCATION;LANGUAGE=en-US:https://zoom.us/j/5014627785
X-MICROSOFT-CDO-APPT-SEQUENCE:31
X-MICROSOFT-CDO-OWNERAPPTID:495601634
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

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

[Kunzmann, Gerald via RT]

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
update the table, I am very concerned that this behavior may also cause similar 
issues in other patch submissions that go unnoticed….

Can someone please have a look at this?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH Landsberger Strasse 312, 80687 
Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura, Amtsgericht München, HRB 132976



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

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

[Kunzmann, Gerald via RT]

Dear all,

So this issue is easily reproducible. It had again happened today with another 
patch being merged

https://gerrit.opnfv.org/gerrit/24365

We are now back to the old table again :(

We have to find a solution to this problem!!!

Best regards,
Gerald

-Original Message-
From: Kunzmann, Gerald 
Sent: Mittwoch, 25. Januar 2017 13:56
To: 'opnfv-helpd...@rt.linuxfoundation.org' 

Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
update the table, I am very concerned that this behavior may also cause similar 
issues in other patch submissions that go unnoticed….

Can someone please have a look at this?

Best regards,
Gerald

===
Dr. Gerald Kunzmann, Manager
DOCOMO Communications Laboratories Europe GmbH Landsberger Strasse 312, 80687 
Munich
Tel: +49-89-56824-239 / Fax: +49-89-56824-300
Web: http://www.docomoeurolabs.de<http://www.docomoeurolabs.de/>

Geschäftsführer: Atsushi Takeshita, Dr. Thomas Walter, Hisahiro Hamahata, 
Hiroyuki Oto, Kei Tonokura, Amtsgericht München, HRB 132976



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

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

[Kunzmann, Gerald via RT]

Dear all,

Sorry for another email on this issue:

Today the situation is even more strange:

There is the old alarm table in generated artifacts file: 
http://artifacts.opnfv.org/doctor/docs/requirements/index.html
But the git tree still contains the new table: 
https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst

What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
Ryota had merged the patch,
jenkins-ci has just sent the document links, but there was no specific build 
started. Is this normal/okay?

Best regards,
Gerald

-Original Message-
From: Kunzmann, Gerald 
Sent: Donnerstag, 26. Januar 2017 13:40
To: 'opnfv-helpd...@rt.linuxfoundation.org' 
; 'Fatih Degirmenci' 

Cc: 'opnfv-tech-discuss@lists.opnfv.org' ; 
'r-m...@cq.jp.nec.com' 
Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

So this issue is easily reproducible. It had again happened today with another 
patch being merged

https://gerrit.opnfv.org/gerrit/24365

We are now back to the old table again :(

We have to find a solution to this problem!!!

Best regards,
Gerald

-----Original Message-
From: Kunzmann, Gerald 
Sent: Mittwoch, 25. Januar 2017 13:56
To: 'opnfv-helpd...@rt.linuxfoundation.org' 

Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

HI Fatih,

Thanks for your quick check. The remerged had helped to bring back the table...

Let's see docs team's reply on it.

I agree gerrit was fine not raising conflict as the changed line in the 
"editorial" patch was not conflicting with the other patch.
Still, shouldn't gerrit have just changed that one line instead of also other 
parts of the file and/or shouldn't gerrit have raised some warning it was 
changing more than just the one line?

When looking at the diff in gerrit for the "editorial" patch, it does not 
compare against the latest master, otherwise it would have shown more changes 
than just this one line. This might have caused the issue?!?

Best regards,
Gerald

-Original Message-
From: fatih.degirme...@ericsson.com via RT 
[mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Mittwoch, 25. Januar 2017 13:38
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
[opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Hi,

I had a quick look at this and diffed the commits and I see no conflict so 
Gerrit was fine not raising conflict. (the changed line in 
05-implementation.rst in most recent patch is not a conflicting change)

I then tried regenerating the documents by putting remerge as comment to check 
the doc generation script/job output for possible errors which I didn't see 
any. But the generated document is correct now. If you don't see the updates, 
please try using a different browser or refresh the page after couple of 
minutes due to caching.

With that said, this doesn't really help us as we need to be able to trust our 
toolchain and we shouldn't need to remerge stuff just to make sure.
I'll raise this to docs team and see what they say.

/Fatih

From:  on behalf of "Kunzmann, 
Gerald" 
Date: Wednesday, 25 January 2017 at 11:28
To: "opnfv-tech-discuss@lists.opnfv.org" , 
"opnfv-helpd...@rt.linuxfoundation.org" 
Subject: [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins

Dear all,

Not sure how is the best team to address this to. We have noticed the following 
issue:

In Doctor project there had been two patches merged on the alarm comparison 
table in Section 5.5.3:

-  https://gerrit.opnfv.org/gerrit/26715

-  https://gerrit.opnfv.org/gerrit/27237

Few days later, we merged another patch addressing some editorial changes in 
the document but NOT touching this alarm comparison table:

-  https://gerrit.opnfv.org/gerrit/26731

Unfortunately, this patch has overwritten the two patches merged earlier and 
the alarm comparison table is back to the old version.
I would have expected

a)   that the patch is only changing the editorial fixes, and/or

b)   result in a “merge conflict” as parts of the repo had been changed 
with the other patch.

I had tried to revert the last patch 26731 in patch 
https://gerrit.opnfv.org/gerrit/#/c/27531/  , but the document links provided 
by jenkins-ci still show the old version of the table.
I would have expected that with the revert of the last patch, we would be back 
to the version we had after having submitted patch 27237.

Now, whilst I could manually fix this issue by providing another patch to 
up

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

[Kunzmann, Gerald via RT]

Hi Aric,

Thanks for your investigations! I'll do the fix as you have proposed.

If I understand your reply correctly, this issue is limited to opnfvdocs?

Best regards,
Gerald

-Original Message-
From: Aric Gardner via RT [mailto:opnfv-helpd...@rt.linuxfoundation.org] 
Sent: Donnerstag, 26. Januar 2017 20:54
To: Kunzmann, Gerald 
Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
Subject: Re: [opnfv-tech-discuss] [OPNFV Helpdesk #35878] [linuxfoundation.org 
#35878] [releng][opnfvdocs] Problem with Git/Gerrit/Jenkins

Hi,

Looks like the merge job is doing the wrong thing.

its checking out the patchset, rather than what is in master.
since the patchset is from Dec 28, and does not touch
./docs/requirements/05-implementation.rst (which has been updated
since then)
git does not see a conflict with merging this code.

If you look at the console output for the merge job
https://build.opnfv.org/ci/job/opnfv-docs-merge-master/1232/console
its doing this. > git fetch --tags --progress
ssh://gerrit.opnfv.org:29418/$GERRIT_PROJECT refs/changes/65/24365/4 #
timeout=15
and it should be just doing a straight clone of whats in master (after
24365 is merged)

For now you can just submit a small change to doctor/docs/whatever and
then merge it, this will get the latest version of all rst files into
artifacts.

I will submit at change to jjb/opnfvdocs/opnfvdocs.yml to fix this
confusing behavior in the future.

Regards,
Aric



On Thu, Jan 26, 2017 at 7:50 AM, Kunzmann, Gerald via RT
 wrote:
> Dear all,
>
> Sorry for another email on this issue:
>
> Today the situation is even more strange:
>
> There is the old alarm table in generated artifacts file: 
> http://artifacts.opnfv.org/doctor/docs/requirements/index.html
> But the git tree still contains the new table: 
> https://git.opnfv.org/doctor/tree/docs/requirements/05-implementation.rst
>
> What I realized is that in https://gerrit.opnfv.org/gerrit/#/c/24365/ after 
> Ryota had merged the patch,
> jenkins-ci has just sent the document links, but there was no specific build 
> started. Is this normal/okay?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Donnerstag, 26. Januar 2017 13:40
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> ; 'Fatih Degirmenci' 
> 
> Cc: 'opnfv-tech-discuss@lists.opnfv.org' 
> ; 'r-m...@cq.jp.nec.com' 
> 
> Subject: RE: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Dear all,
>
> So this issue is easily reproducible. It had again happened today with 
> another patch being merged
>
> https://gerrit.opnfv.org/gerrit/24365
>
> We are now back to the old table again :(
>
> We have to find a solution to this problem!!!
>
> Best regards,
> Gerald
>
> -Original Message-
> From: Kunzmann, Gerald
> Sent: Mittwoch, 25. Januar 2017 13:56
> To: 'opnfv-helpd...@rt.linuxfoundation.org' 
> 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> HI Fatih,
>
> Thanks for your quick check. The remerged had helped to bring back the 
> table...
>
> Let's see docs team's reply on it.
>
> I agree gerrit was fine not raising conflict as the changed line in the 
> "editorial" patch was not conflicting with the other patch.
> Still, shouldn't gerrit have just changed that one line instead of also other 
> parts of the file and/or shouldn't gerrit have raised some warning it was 
> changing more than just the one line?
>
> When looking at the diff in gerrit for the "editorial" patch, it does not 
> compare against the latest master, otherwise it would have shown more changes 
> than just this one line. This might have caused the issue?!?
>
> Best regards,
> Gerald
>
> -Original Message-
> From: fatih.degirme...@ericsson.com via RT 
> [mailto:opnfv-helpd...@rt.linuxfoundation.org]
> Sent: Mittwoch, 25. Januar 2017 13:38
> To: Kunzmann, Gerald 
> Cc: opnfv-tech-discuss@lists.opnfv.org; r-m...@cq.jp.nec.com
> Subject: [OPNFV Helpdesk #35878] [linuxfoundation.org #35878] Re: 
> [opnfv-tech-discuss] [releng][helpdesk] Problem with Git/Gerrit/Jenkins
>
> Hi,
>
> I had a quick look at this and diffed the commits and I see no conflict so 
> Gerrit was fine not raising conflict. (the changed line in 
> 05-implementation.rst in most recent patch is not a conflicting change)
>
> I then tried regenerating the documents by putting remerge as comment to 
> check the doc generation script/job o