[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

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Cedric OLLIVIER]

Hello,

I would advice the offical OpenStack documentation about this topic:
https://docs.openstack.org/infra/manual/developers.html

Cédric

2017-10-19 4:23 GMT+02:00 Yujun Zhang (ZTE) :
> This could do the trick but I don't quite recommend it. There would be some
> commits on master you do NOT want to include in stable branches.
>
> I suggest to pick commits carefully after inspection and do the cherrypick
> one by one on gerrit. It will keep a record of which patch sets have been
> cherry-picked in review history (not just git log).
>
> If you have too many patch sets to be cherrypicked. Something may have gone
> wrong. By the time we created stable branch, it should be considered as a
> stable branch and not expecting too many changes, except for bug fix and
> document amending.
>
> My 2 cents.
>
> On Thu, Oct 19, 2017 at 6:04 AM Trevor Bramwell
>  wrote:
>>
>> Hey Alec,
>>
>> Here's a quick way to cherry-pick these all over to the stable/euphrates
>> branch. Though you'll still need to submit them all through Gerrit:
>>
>>   git checkout euphrates
>>   git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git
>> cherry-pick -x '{}'
>>
>> 'git review' will ask you to confirm you want to upload multiple
>> patchsets. A 'yes' should put all of them up for review.
>>
>> Regards,
>> Trevor Bramwell
>>
>> On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
>> > I have many commits in master which I’d like to merge to
>> > stable/euphrates.
>> > Would like to check if anybody knows how to merge master into a release
>> > branch using gerrit?
>> > Looks like I may need the permission to upload merges with Gerrit.
>> >
>> > Here is what I did:
>> >
>> > $ git fetch origin  stable/euphrates:euphrates
>> > $ git checkout euphrates
>> >
>> > $ git merge master –no-ff
>> >
>> > # at this point, so far so good, I got all my commits into my euphrates
>> > branch
>> >
>> > # git review fails due to permission:
>> >
>> > $ git review
>> > Warning: Permanently added
>> > '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' (RSA) to the list of known
>> > hosts.
>> > remote: Processing changes: refs: 1, done
>> > To ssh://gerrit.opnfv.org:29418/nfvbench.git
>> > ! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not
>> > allowed to upload merges)
>> > error: failed to push some refs to
>> > 'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'
>> >
>> >
>> > Is there a different way to achieve this?
>> > I do not want to cherry pick my commits as I have too many of them.
>> >
>> > Thanks
>> >
>> >   Alec
>> >
>>
>> > ___
>> > 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
>
> --
> Yujun Zhang
>
> ___
> 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-tsc][Compass]Nomination of Committer promotion for Yifei Xue

[Weidong.Shao]

+1

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Chigang 
(Justin)
Sent: Tuesday, October 17, 2017 12:47 AM
To: TSC OPNFV 
Cc: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [opnfv-tsc][Compass]Nomination of Committer 
promotion for Yifei Xue

I would like to nominate Yifei Xue as committer to Compass4nfv Project.

The motivation for nominating Yifei to committer on Compass4nfv project is due 
to his commitment of providing value to the project through consistent high 
quality and valuable contributions.
His active participation through patch submissions and code reviews for 
Compass4nfv project SDN features integration (such as OpenDaylight, ONOS, etc) 
has been invaluable.

Please provide a +1/-1 vote before the end of next week, Oct 29.

Regards
Justin


华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
手　　机：13472817001
电子邮件：chig...@huawei.com

 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

___
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] [Compass]Nomination of Committer promotion for Xinhui Hu

[Weidong.Shao]

+1

From: opnfv-tsc-boun...@lists.opnfv.org 
[mailto:opnfv-tsc-boun...@lists.opnfv.org] On Behalf Of Chigang (Justin)
Sent: Tuesday, October 17, 2017 12:58 AM
To: TSC OPNFV 
Cc: TECH-DISCUSS OPNFV ; 104511458 

Subject: [opnfv-tsc] [Compass]Nomination of Committer promotion for Xinhui Hu

I would like to nominate Xinhui Hu as committer to Compass4nfv Project.

The motivation for nominating Xinhui Hu to committer on Compass4nfv project is 
due to his commitment of providing value to the project through consistent high 
quality and valuable contributions.
He is a senior architect for Cloud Computing in Fiberhome, more than 7 years’ 
development experience in Cloud, familiar with Vmware, OpenStack, Kubernetes 
high availability cluster building.
His active participation through patch submissions and code reviews for 
contributing K8s integration in Euphrates has been invaluable.

Please provide a +1/-1 vote before the end of next week, Oct 29.

Regards
Justin


华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
手　　机：13472817001
电子邮件：chig...@huawei.com

 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!

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

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Yujun Zhang (ZTE)]

This could do the trick but I don't quite recommend it. There would be some
commits on master you do NOT want to include in stable branches.

I suggest to pick commits carefully after inspection and do the cherrypick *one
by one *on gerrit. It will keep a record of which patch sets have been
cherry-picked in review history (not just git log).

If you have too many patch sets to be cherrypicked. Something may have gone
wrong. By the time we created stable branch, it should be considered as a
*stable* branch and not expecting too many changes, except for bug fix and
document amending.

My 2 cents.

On Thu, Oct 19, 2017 at 6:04 AM Trevor Bramwell <
tbramw...@linuxfoundation.org> wrote:

> Hey Alec,
>
> Here's a quick way to cherry-pick these all over to the stable/euphrates
> branch. Though you'll still need to submit them all through Gerrit:
>
>   git checkout euphrates
>   git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git
> cherry-pick -x '{}'
>
> 'git review' will ask you to confirm you want to upload multiple
> patchsets. A 'yes' should put all of them up for review.
>
> Regards,
> Trevor Bramwell
>
> On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
> > I have many commits in master which I’d like to merge to
> stable/euphrates.
> > Would like to check if anybody knows how to merge master into a release
> branch using gerrit?
> > Looks like I may need the permission to upload merges with Gerrit.
> >
> > Here is what I did:
> >
> > $ git fetch origin  stable/euphrates:euphrates
> > $ git checkout euphrates
> >
> > $ git merge master –no-ff
> >
> > # at this point, so far so good, I got all my commits into my euphrates
> branch
> >
> > # git review fails due to permission:
> >
> > $ git review
> > Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418'
> (RSA) to the list of known hosts.
> > remote: Processing changes: refs: 1, done
> > To ssh://gerrit.opnfv.org:29418/nfvbench.git
> > ! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not
> allowed to upload merges)
> > error: failed to push some refs to 'ssh://
> ahot...@gerrit.opnfv.org:29418/nfvbench.git'
> >
> >
> > Is there a different way to achieve this?
> > I do not want to cherry pick my commits as I have too many of them.
> >
> > Thanks
> >
> >   Alec
> >
>
> > ___
> > 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
>
-- 
Yujun Zhang
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Alexandru Avadanii]

Hi,
Not really. A squashed commit will be just that – a single commit, optionally 
keeping the commit titles and/or descriptions of all the patches, but no 
further code separation.
It’s basically one big patch, with all commit metdata concatenated.
If you are after a link between the commits on master and their counterparts on 
stable, this is clearly not what you want ☺

BR,
Alex


From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com]
Sent: Thursday, October 19, 2017 3:35 AM
To: Alexandru Avadanii; Trevor Bramwell
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Alex,

Ross has proposed a method using rebase, is that what you are also proposing?
It is still not quite same as a merge (see my reply to Ross).

Thanks

  Alec



From: Alexandru Avadanii 
mailto:alexandru.avada...@enea.com>>
Date: Wednesday, October 18, 2017 at 4:20 PM
To: "Alec Hothan (ahothan)" mailto:ahot...@cisco.com>>, 
Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hi, Alec,
If all you want is one commit on the stable branch, you should look at 
squashing all commits from master into a single commit on the stable branch.

Alex

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Thursday, October 19, 2017 1:31 AM
To: Trevor Bramwell
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hi Trevor,

Thanks for the tip!
If I am not mistaken that will result in as many commits in euphrates as there 
are commits to cherry-pick from master?
Although you achieve the same final state in stable/euphrates you do end up 
with potentially significantly more commits than a simple merge. I think it is 
best to keep release branches clean and devoid of unnecessary detailed commits.
I was just looking at the functest repo and they do have tons of small commits 
in their release branch, which is the result of multiple cherry picking.
In my case I have well over 40 commits to merge into stable/euphrates so that 
requires as many gerrit reviews and result in as many commits on the release 
branch (I only need one – not 40+)… ;-(

Is there any objection to allow merges to be submitted in git review? They 
should be reviewed equally and can be accepted/rejected by committers.
I think this requires adding the “Push Merge Commit” access right for the 
“refs/for/refs/*” reference in Gerrit.

See gerrit doc at: 
https://codereview.qt-project.org/Documentation/access-control.html#category_push_merge

If we want to allow all projects to submit merges to gerrit (such as syncing 
master to their stable branch), we’d need to enable it for All-Projects:
https://gerrit.opnfv.org/gerrit/#/admin/projects/All-Projects,access

I think that will result in “cleaner” stable branches.


David and all: note that this ability to submit merges in Gerrit (sync content 
of one branch to another) might be needed for XCI if we move towards the use of 
a long-lived “stable” branch (a branch that contains only stable commits off 
master that are validated for XCI usage) that sits between master (which 
contains all dev commits subject to each project CI but not necessarily vetted 
for XCI use) and the release branches (which contain only release material and 
would then be branched off the stable branch). The benefit of this extra stable 
branch is you can effectively run CD/XCI anytime and well before release 
branches are even created.
I’ll try to send out a diagram of how that branching model works out with CI 
and XCI.

Thanks

   Alec






From: Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>>
Date: Wednesday, October 18, 2017 at 3:04 PM
To: "Alec Hothan (ahothan)" mailto:ahot...@cisco.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tec

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Alec Hothan (ahothan)]

Alex,

Ross has proposed a method using rebase, is that what you are also proposing?
It is still not quite same as a merge (see my reply to Ross).

Thanks

  Alec



From: Alexandru Avadanii 
Date: Wednesday, October 18, 2017 at 4:20 PM
To: "Alec Hothan (ahothan)" , Trevor Bramwell 

Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: RE: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hi, Alec,
If all you want is one commit on the stable branch, you should look at 
squashing all commits from master into a single commit on the stable branch.

Alex

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Thursday, October 19, 2017 1:31 AM
To: Trevor Bramwell
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hi Trevor,

Thanks for the tip!
If I am not mistaken that will result in as many commits in euphrates as there 
are commits to cherry-pick from master?
Although you achieve the same final state in stable/euphrates you do end up 
with potentially significantly more commits than a simple merge. I think it is 
best to keep release branches clean and devoid of unnecessary detailed commits.
I was just looking at the functest repo and they do have tons of small commits 
in their release branch, which is the result of multiple cherry picking.
In my case I have well over 40 commits to merge into stable/euphrates so that 
requires as many gerrit reviews and result in as many commits on the release 
branch (I only need one – not 40+)… ;-(

Is there any objection to allow merges to be submitted in git review? They 
should be reviewed equally and can be accepted/rejected by committers.
I think this requires adding the “Push Merge Commit” access right for the 
“refs/for/refs/*” reference in Gerrit.

See gerrit doc at: 
https://codereview.qt-project.org/Documentation/access-control.html#category_push_merge

If we want to allow all projects to submit merges to gerrit (such as syncing 
master to their stable branch), we’d need to enable it for All-Projects:
https://gerrit.opnfv.org/gerrit/#/admin/projects/All-Projects,access

I think that will result in “cleaner” stable branches.


David and all: note that this ability to submit merges in Gerrit (sync content 
of one branch to another) might be needed for XCI if we move towards the use of 
a long-lived “stable” branch (a branch that contains only stable commits off 
master that are validated for XCI usage) that sits between master (which 
contains all dev commits subject to each project CI but not necessarily vetted 
for XCI use) and the release branches (which contain only release material and 
would then be branched off the stable branch). The benefit of this extra stable 
branch is you can effectively run CD/XCI anytime and well before release 
branches are even created.
I’ll try to send out a diagram of how that branching model works out with CI 
and XCI.

Thanks

   Alec






From: Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>>
Date: Wednesday, October 18, 2017 at 3:04 PM
To: "Alec Hothan (ahothan)" mailto:ahot...@cisco.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hey Alec,

Here's a quick way to cherry-pick these all over to the stable/euphrates
branch. Though you'll still need to submit them all through Gerrit:

  git checkout euphrates
  git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git 
cherry-pick -x '{}'

'git review' will ask you to confirm you want to upload multiple
patchsets. A 'yes' should put all of them up for review.

Regards,
Trevor Bramwell

On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.
Here is what I did:
$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates
$ git merge master –no-ff
# at this point, so far so good, I got all my commits into my euphrates branch
# git review fails due to permission:
$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Alec Hothan (ahothan)]

Hi Ross,

I tried the rebase path and it seems to work.
The rebase duplicates all commits of master to the euphrates branch which can 
make that branch very busy.
It is possible to squash all commits into 1 (which is what I’d like to keep the 
release branch clean).
In any case, the main difference with a merge is that we’re missing the 
ancestor link from master to the new commit on euphrates (the one that 
indicates where the merge comes from). I’d have to add a commit description 
such as “merge from master at hash …).
Do you agree?
A regular merge would have done this in a more formal and clean way – but 
requires push merge commit permission in gerrit.
If all else is not possible I’ll sync using your method + squashing all commits.

Thanks

  Alec



From: "Brattain, Ross B" 
Date: Wednesday, October 18, 2017 at 3:06 PM
To: "Alec Hothan (ahothan)" , 
"opnfv-tech-discuss@lists.opnfv.org" 
Subject: RE: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

git remote update
# create new branch based on master
git checkout -B euphrates-sync-$(date -I) origin/master
# rebase on euphrates
git rebase origin/stable/euphrates
# or to pick patches
git rebase -i origin/stable/euphrates
# resolve conflicts
# submit all patches to gerrit
git review stable/euphrates

+2 all in Gerrit and Submit including parents.


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Wednesday, October 18, 2017 1:15 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] How to merge master to euphrates with 
gerrit

I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.

Here is what I did:

$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates

$ git merge master –no-ff

# at this point, so far so good, I got all my commits into my euphrates branch

# git review fails due to permission:

$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not allowed 
to upload merges)
error: failed to push some refs to 
'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'


Is there a different way to achieve this?
I do not want to cherry pick my commits as I have too many of them.

Thanks

  Alec

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

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Alexandru Avadanii]

Hi, Alec,
If all you want is one commit on the stable branch, you should look at 
squashing all commits from master into a single commit on the stable branch.

Alex

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Thursday, October 19, 2017 1:31 AM
To: Trevor Bramwell
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hi Trevor,

Thanks for the tip!
If I am not mistaken that will result in as many commits in euphrates as there 
are commits to cherry-pick from master?
Although you achieve the same final state in stable/euphrates you do end up 
with potentially significantly more commits than a simple merge. I think it is 
best to keep release branches clean and devoid of unnecessary detailed commits.
I was just looking at the functest repo and they do have tons of small commits 
in their release branch, which is the result of multiple cherry picking.
In my case I have well over 40 commits to merge into stable/euphrates so that 
requires as many gerrit reviews and result in as many commits on the release 
branch (I only need one – not 40+)… ;-(

Is there any objection to allow merges to be submitted in git review? They 
should be reviewed equally and can be accepted/rejected by committers.
I think this requires adding the “Push Merge Commit” access right for the 
“refs/for/refs/*” reference in Gerrit.

See gerrit doc at: 
https://codereview.qt-project.org/Documentation/access-control.html#category_push_merge

If we want to allow all projects to submit merges to gerrit (such as syncing 
master to their stable branch), we’d need to enable it for All-Projects:
https://gerrit.opnfv.org/gerrit/#/admin/projects/All-Projects,access

I think that will result in “cleaner” stable branches.


David and all: note that this ability to submit merges in Gerrit (sync content 
of one branch to another) might be needed for XCI if we move towards the use of 
a long-lived “stable” branch (a branch that contains only stable commits off 
master that are validated for XCI usage) that sits between master (which 
contains all dev commits subject to each project CI but not necessarily vetted 
for XCI use) and the release branches (which contain only release material and 
would then be branched off the stable branch). The benefit of this extra stable 
branch is you can effectively run CD/XCI anytime and well before release 
branches are even created.
I’ll try to send out a diagram of how that branching model works out with CI 
and XCI.

Thanks

   Alec






From: Trevor Bramwell 
mailto:tbramw...@linuxfoundation.org>>
Date: Wednesday, October 18, 2017 at 3:04 PM
To: "Alec Hothan (ahothan)" mailto:ahot...@cisco.com>>
Cc: 
"opnfv-tech-discuss@lists.opnfv.org" 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hey Alec,

Here's a quick way to cherry-pick these all over to the stable/euphrates
branch. Though you'll still need to submit them all through Gerrit:

  git checkout euphrates
  git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git 
cherry-pick -x '{}'

'git review' will ask you to confirm you want to upload multiple
patchsets. A 'yes' should put all of them up for review.

Regards,
Trevor Bramwell

On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.
Here is what I did:
$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates
$ git merge master –no-ff
# at this point, so far so good, I got all my commits into my euphrates branch
# git review fails due to permission:
$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not allowed 
to upload merges)
error: failed to push some refs to 
'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'
Is there a different way to achieve this?
I do not want to cherry pick my commits as I have too many of them.
Thanks
   Alec

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Alec Hothan (ahothan)]

Hi Trevor,

Thanks for the tip!
If I am not mistaken that will result in as many commits in euphrates as there 
are commits to cherry-pick from master?
Although you achieve the same final state in stable/euphrates you do end up 
with potentially significantly more commits than a simple merge. I think it is 
best to keep release branches clean and devoid of unnecessary detailed commits.
I was just looking at the functest repo and they do have tons of small commits 
in their release branch, which is the result of multiple cherry picking.
In my case I have well over 40 commits to merge into stable/euphrates so that 
requires as many gerrit reviews and result in as many commits on the release 
branch (I only need one – not 40+)… ;-(

Is there any objection to allow merges to be submitted in git review? They 
should be reviewed equally and can be accepted/rejected by committers.
I think this requires adding the “Push Merge Commit” access right for the 
“refs/for/refs/*” reference in Gerrit.

See gerrit doc at: 
https://codereview.qt-project.org/Documentation/access-control.html#category_push_merge

If we want to allow all projects to submit merges to gerrit (such as syncing 
master to their stable branch), we’d need to enable it for All-Projects:
https://gerrit.opnfv.org/gerrit/#/admin/projects/All-Projects,access

I think that will result in “cleaner” stable branches.


David and all: note that this ability to submit merges in Gerrit (sync content 
of one branch to another) might be needed for XCI if we move towards the use of 
a long-lived “stable” branch (a branch that contains only stable commits off 
master that are validated for XCI usage) that sits between master (which 
contains all dev commits subject to each project CI but not necessarily vetted 
for XCI use) and the release branches (which contain only release material and 
would then be branched off the stable branch). The benefit of this extra stable 
branch is you can effectively run CD/XCI anytime and well before release 
branches are even created.
I’ll try to send out a diagram of how that branching model works out with CI 
and XCI.

Thanks

   Alec






From: Trevor Bramwell 
Date: Wednesday, October 18, 2017 at 3:04 PM
To: "Alec Hothan (ahothan)" 
Cc: "opnfv-tech-discuss@lists.opnfv.org" 
Subject: Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates 
with gerrit

Hey Alec,

Here's a quick way to cherry-pick these all over to the stable/euphrates
branch. Though you'll still need to submit them all through Gerrit:

  git checkout euphrates
  git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git 
cherry-pick -x '{}'

'git review' will ask you to confirm you want to upload multiple
patchsets. A 'yes' should put all of them up for review.

Regards,
Trevor Bramwell

On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.
Here is what I did:
$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates
$ git merge master –no-ff
# at this point, so far so good, I got all my commits into my euphrates branch
# git review fails due to permission:
$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not allowed 
to upload merges)
error: failed to push some refs to 
'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'
Is there a different way to achieve this?
I do not want to cherry pick my commits as I have too many of them.
Thanks
   Alec

___
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] [releng] How to merge master to euphrates with gerrit

[Brattain, Ross B]

git remote update
# create new branch based on master
git checkout -B euphrates-sync-$(date -I) origin/master
# rebase on euphrates
git rebase origin/stable/euphrates
# or to pick patches
git rebase -i origin/stable/euphrates
# resolve conflicts
# submit all patches to gerrit
git review stable/euphrates

+2 all in Gerrit and Submit including parents.


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Alec Hothan 
(ahothan)
Sent: Wednesday, October 18, 2017 1:15 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [releng] How to merge master to euphrates with 
gerrit

I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.

Here is what I did:

$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates

$ git merge master –no-ff

# at this point, so far so good, I got all my commits into my euphrates branch

# git review fails due to permission:

$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not allowed 
to upload merges)
error: failed to push some refs to 
'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'


Is there a different way to achieve this?
I do not want to cherry pick my commits as I have too many of them.

Thanks

  Alec

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

Re: [opnfv-tech-discuss] [releng] How to merge master to euphrates with gerrit

[Trevor Bramwell]

Hey Alec,

Here's a quick way to cherry-pick these all over to the stable/euphrates
branch. Though you'll still need to submit them all through Gerrit:

  git checkout euphrates
  git cherry -v stable/euphrates master | cut -d' ' -f2 | xargs -I{} git 
cherry-pick -x '{}'

'git review' will ask you to confirm you want to upload multiple
patchsets. A 'yes' should put all of them up for review.

Regards,
Trevor Bramwell

On Wed, Oct 18, 2017 at 08:14:59PM +, Alec Hothan (ahothan) wrote:
> I have many commits in master which I’d like to merge to stable/euphrates.
> Would like to check if anybody knows how to merge master into a release 
> branch using gerrit?
> Looks like I may need the permission to upload merges with Gerrit.
> 
> Here is what I did:
> 
> $ git fetch origin  stable/euphrates:euphrates
> $ git checkout euphrates
> 
> $ git merge master –no-ff
> 
> # at this point, so far so good, I got all my commits into my euphrates branch
> 
> # git review fails due to permission:
> 
> $ git review
> Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
> (RSA) to the list of known hosts.
> remote: Processing changes: refs: 1, done
> To ssh://gerrit.opnfv.org:29418/nfvbench.git
> ! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not 
> allowed to upload merges)
> error: failed to push some refs to 
> 'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'
> 
> 
> Is there a different way to achieve this?
> I do not want to cherry pick my commits as I have too many of them.
> 
> Thanks
> 
>   Alec
> 

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



signature.asc
Description: PGP 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] [releng] How to merge master to euphrates with gerrit

[David McBride]

+Aric, Trevor

Aric or Trevor - could you please advise Alec?

On Wed, Oct 18, 2017 at 1:14 PM, Alec Hothan (ahothan) 
wrote:

> I have many commits in master which I’d like to merge to stable/euphrates.
>
> Would like to check if anybody knows how to merge master into a release
> branch using gerrit?
>
> Looks like I may need the permission to upload merges with Gerrit.
>
>
>
> Here is what I did:
>
>
>
> $ git fetch origin  stable/euphrates:euphrates
>
> $ git checkout euphrates
>
>
>
> $ git merge master –no-ff
>
>
>
> # at this point, so far so good, I got all my commits into my euphrates
> branch
>
>
>
> # git review fails due to permission:
>
>
>
> $ git review
>
> Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418'
> (RSA) to the list of known hosts.
>
> remote: Processing changes: refs: 1, done
>
> To ssh://gerrit.opnfv.org:29418/nfvbench.git
>
> ! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not
> allowed to upload merges)
>
> error: failed to push some refs to 'ssh://ahothan@gerrit.opnfv.
> org:29418/nfvbench.git'
>
>
>
>
>
> Is there a different way to achieve this?
>
> I do not want to cherry pick my commits as I have too many of them.
>
>
>
> Thanks
>
>
>
>   Alec
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>


-- 
*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] [releng] How to merge master to euphrates with gerrit

[Alec Hothan (ahothan)]

I have many commits in master which I’d like to merge to stable/euphrates.
Would like to check if anybody knows how to merge master into a release branch 
using gerrit?
Looks like I may need the permission to upload merges with Gerrit.

Here is what I did:

$ git fetch origin  stable/euphrates:euphrates
$ git checkout euphrates

$ git merge master –no-ff

# at this point, so far so good, I got all my commits into my euphrates branch

# git review fails due to permission:

$ git review
Warning: Permanently added '[gerrit.opnfv.org]:29418,[198.145.29.81]:29418' 
(RSA) to the list of known hosts.
remote: Processing changes: refs: 1, done
To ssh://gerrit.opnfv.org:29418/nfvbench.git
! [remote rejected] HEAD -> refs/publish/master/euphrates (you are not allowed 
to upload merges)
error: failed to push some refs to 
'ssh://ahot...@gerrit.opnfv.org:29418/nfvbench.git'


Is there a different way to achieve this?
I do not want to cherry pick my commits as I have too many of them.

Thanks

  Alec

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

[opnfv-tech-discuss] [fuel] [armband] Full network parameterization using PDF/IDF

[Alexandru Avadanii]

Hi,
I am happy to announce we finally submitted the final changes for PDF/IDF 
support in Fuel.
We have been using PDF for a few weeks to describe most of the hardware 
parameters (IPMI credentials for cluster nodes, network VLANs etc.),
but we were lacking support for dynamic configuration of interface allocation 
(e.g. mgmt VLAN was always assigned to the Xth NIC, tagged; public was always 
assigned to Yth NIC etc.).

For those of you who have securedlab access, the IDF change, adding some new 
Fuel-specific params for lf-pod2/arm-pod5 is at [1].
For those who don't, we also provide a sample IDF in Fuel@OPNFV, which is 
basically a copy of lf-pod2's IDF.

The Fuel code consuming the new data is at [2]. We can now model any 
arrangement of tagged/untagged, vlan or physical interface configuration.

This means that soon after the release, we can start re-enabling all Fuel PODs 
that did not align with the lf-pod2/arm-pod5 hardcoded setups (ericsson-pod1, 
zte-pod1 etc.).

To summarize, here are the PDF/IDF requirements for Fuel:
- PDF (as per Pharos specification), including net_config section (which is not 
part of the spec yet, but it doesn't collide with it either - see sample [3], 
which is basically lf-pod2's PDF);
- IDF - we don't depend on the shared section (yet), and the Fuel-specific 
section is quite lightweight and self-explanatory - see sample [4];

BR,
Alex

[1] https://gerrit.opnfv.org/gerrit/#/c/45587
[2] https://gerrit.opnfv.org/gerrit/#/c/45427
[3] https://github.com/opnfv/fuel/blob/master/mcp/config/labs/local/pod1.yaml
[4] 
https://gerrit.opnfv.org/gerrit/#/c/45427/4/mcp/config/labs/local/idf-pod1.yaml
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Srikanth Vavilapalli]

That’s good to know… Thanks Peri for the fix.

From: Jose Lausuch [mailto:jalaus...@suse.com]
Sent: Wednesday, October 18, 2017 10:40 AM
To: Srikanth Vavilapalli 
Cc: David McBride ; Tim Irnich 
; Tim Rozet ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Srikanth,

That issue has been already fixed https://gerrit.opnfv.org/gerrit/#/c/45503/

Yes, I think the plugfest is a good forum. Unfortunately I won’t be able to 
attend but many folks will be there. We can always start the discussion on any 
of the infra or weekly tech-discuss meetings.

Regards,
Jose




On 18 Oct 2017, at 19:20, Srikanth Vavilapalli 
mailto:srikanth.vavilapa...@ericsson.com>> 
wrote:

Hi Jose

Yes, the cleaner solution is to move the log collection or any deployer 
specific actions to outside of test frameworks such that they can be run 
against any OPNFV compliant platforms. We need to brainstorm in some forum on 
the best way to achieve this. David, plz help us.

For the immediate need, we can add a fix in sdnvpn project such that  
sdnvpn.lib.utils.get_nodes() returns an empty list of nodes rather than 
throwing exception if the INSTALLER_TYPE is set to anything else other than 
“apex” and “fuel”. So this is kind of disabling the sdnvpn LOG collection in 
other installer types.

Plz let me know any comments or inputs…

Thanks
Srikanth



From: Jose Lausuch [mailto:jalaus...@suse.com]
Sent: Tuesday, October 17, 2017 8:18 AM
To: David McBride 
mailto:dmcbr...@linuxfoundation.org>>; Srikanth 
Vavilapalli 
mailto:srikanth.vavilapa...@ericsson.com>>
Cc: Tim Irnich mailto:tim.irn...@ericsson.com>>; Tim 
Rozet mailto:tro...@redhat.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

IMO, the log collection topic is a CI/Releng function rather than the test 
framework’s responsibility,  we should not discuss it only during the Functest 
weekly since we would lose audience.
@David, will you bring this discussion to the infra or technical weekly meeting?

Thanks,
Jose




On 17 Oct 2017, at 00:32, Srikanth Vavilapalli 
mailto:srikanth.vavilapa...@ericsson.com>> 
wrote:

Hi

Can we have a quick discussion in any weekly meeting (sdnvpn, functest?) on 
this topic to pick the best approach to move forward? Also Xu Dan has raised 
few other concerns on the location of log files and option for disabling the 
gathering logs…etc.

Thanks
Srikanth



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Friday, October 13, 2017 4:28 AM
To: Tim Irnich mailto:tim.irn...@ericsson.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi Tim,

My only concern is that by implementing this function inside the test case, we 
might run into exceptions raised if there is a problem with SSH keys or 
whatever other problem accessing the nodes.

Collecting logs when the test fails makes sense, but it doesn’t harm if we 
collect it when it passes as well. Anyway, if we do it only when having 
failures, I imagine that logic could also be implemented post-job by checking 
the "criteria": “FAIL" value on the DB and executing some j-job to collect the 
logs. This logs could be uploaded to artifact repo for further analysis as we 
do for the Functest logs.

Regards,
Jose




On 13 Oct 2017, at 09:27, Tim Irnich 
mailto:tim.irn...@ericsson.com>> wrote:

Jose,

I see the point of avoiding log collection in the code for test execution to 
avoid false negatives in case something with the log collection itself goes 
wrong (although I’m wondering a bit if that cannot also be handled by carefully 
implementing the test pass/fail criteria).

There are however cases where we’ll want to collect logs only if a test fails, 
in order to enable a first tier of offline troubleshooting. You’ll remember the 
gather_logs function Niko implemented for the bgpvpn tests – that is one 
example. Can that effectively be handled if we separate things as you suggest?

Regards, Tim


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Friday, October 13, 2017 09:16
To: xudan (N) mailto:xuda...@huawei.com>>; Morgan, Jack 
mailto:jack.mor...@intel.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

When it comes to log collection, I st

Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Jose Lausuch]

Srikanth,

That issue has been already fixed https://gerrit.opnfv.org/gerrit/#/c/45503/ 


Yes, I think the plugfest is a good forum. Unfortunately I won’t be able to 
attend but many folks will be there. We can always start the discussion on any 
of the infra or weekly tech-discuss meetings.

Regards,
Jose





> On 18 Oct 2017, at 19:20, Srikanth Vavilapalli 
>  wrote:
> 
> Hi Jose
>  
> Yes, the cleaner solution is to move the log collection or any deployer 
> specific actions to outside of test frameworks such that they can be run 
> against any OPNFV compliant platforms. We need to brainstorm in some forum on 
> the best way to achieve this. David, plz help us.
>  
> For the immediate need, we can add a fix in sdnvpn project such that  
> sdnvpn.lib.utils.get_nodes() returns an empty list of nodes rather than 
> throwing exception if the INSTALLER_TYPE is set to anything else other than 
> “apex” and “fuel”. So this is kind of disabling the sdnvpn LOG collection in 
> other installer types.
>  
> Plz let me know any comments or inputs…
>  
> Thanks
> Srikanth
>  
>  
>  
> From: Jose Lausuch [mailto:jalaus...@suse.com] 
> Sent: Tuesday, October 17, 2017 8:18 AM
> To: David McBride ; Srikanth Vavilapalli 
> 
> Cc: Tim Irnich ; Tim Rozet ; 
> opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
> installer dependent information in the test tools
>  
> IMO, the log collection topic is a CI/Releng function rather than the test 
> framework’s responsibility,  we should not discuss it only during the 
> Functest weekly since we would lose audience.
> @David, will you bring this discussion to the infra or technical weekly 
> meeting?
>  
> Thanks,
> Jose
>  
>  
>  
> 
>  
> On 17 Oct 2017, at 00:32, Srikanth Vavilapalli 
>  > wrote:
>  
> Hi
>  
> Can we have a quick discussion in any weekly meeting (sdnvpn, functest?) on 
> this topic to pick the best approach to move forward? Also Xu Dan has raised 
> few other concerns on the location of log files and option for disabling the 
> gathering logs…etc.
>  
> Thanks
> Srikanth
>  
>  
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>  
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
> ] On Behalf Of Jose Lausuch
> Sent: Friday, October 13, 2017 4:28 AM
> To: Tim Irnich mailto:tim.irn...@ericsson.com>>
> Cc: opnfv-tech-discuss@lists.opnfv.org 
> 
> Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
> installer dependent information in the test tools
>  
> Hi Tim,
>  
> My only concern is that by implementing this function inside the test case, 
> we might run into exceptions raised if there is a problem with SSH keys or 
> whatever other problem accessing the nodes. 
>  
> Collecting logs when the test fails makes sense, but it doesn’t harm if we 
> collect it when it passes as well. Anyway, if we do it only when having 
> failures, I imagine that logic could also be implemented post-job by checking 
> the "criteria": “FAIL" value on the DB and executing some j-job to collect 
> the logs. This logs could be uploaded to artifact repo for further analysis 
> as we do for the Functest logs.
>  
> Regards,
> Jose
>  
>  
>  
> 
>  
> On 13 Oct 2017, at 09:27, Tim Irnich  > wrote:
>  
> Jose, 
>  
> I see the point of avoiding log collection in the code for test execution to 
> avoid false negatives in case something with the log collection itself goes 
> wrong (although I’m wondering a bit if that cannot also be handled by 
> carefully implementing the test pass/fail criteria). 
>  
> There are however cases where we’ll want to collect logs only if a test 
> fails, in order to enable a first tier of offline troubleshooting. You’ll 
> remember the gather_logs function Niko implemented for the bgpvpn tests – 
> that is one example. Can that effectively be handled if we separate things as 
> you suggest?
>  
> Regards, Tim
>  
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>  
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
> ] On Behalf Of Jose Lausuch
> Sent: Friday, October 13, 2017 09:16
> To: xudan (N) mailto:xuda...@huawei.com>>; Morgan, Jack 
> mailto:jack.mor...@intel.com>>
> Cc: opnfv-tech-discuss@lists.opnfv.org 
> 
> Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
> installer dependent information in the test tools
>  
> Hi,
>  
> When it comes to log collection, I strongly believe it should be done 
> post-job in our CI pipeline, not as part of the test case. Users can always 
> collect logs manually regardless o

[opnfv-tech-discuss] [opnfvdocs] [release] Don't forget to cherry pick your documentation

[Sofia Wallin]

Hi everyone,
Please don’t forget to cherry pick your documentation to stable/euphrates.


Thanks,
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] [functest] [sdnvpn] Proposal for removing installer dependent information in the test tools

[Srikanth Vavilapalli]

Hi Jose

Yes, the cleaner solution is to move the log collection or any deployer 
specific actions to outside of test frameworks such that they can be run 
against any OPNFV compliant platforms. We need to brainstorm in some forum on 
the best way to achieve this. David, plz help us.

For the immediate need, we can add a fix in sdnvpn project such that  
sdnvpn.lib.utils.get_nodes() returns an empty list of nodes rather than 
throwing exception if the INSTALLER_TYPE is set to anything else other than 
“apex” and “fuel”. So this is kind of disabling the sdnvpn LOG collection in 
other installer types.

Plz let me know any comments or inputs…

Thanks
Srikanth



From: Jose Lausuch [mailto:jalaus...@suse.com]
Sent: Tuesday, October 17, 2017 8:18 AM
To: David McBride ; Srikanth Vavilapalli 

Cc: Tim Irnich ; Tim Rozet ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

IMO, the log collection topic is a CI/Releng function rather than the test 
framework’s responsibility,  we should not discuss it only during the Functest 
weekly since we would lose audience.
@David, will you bring this discussion to the infra or technical weekly meeting?

Thanks,
Jose




On 17 Oct 2017, at 00:32, Srikanth Vavilapalli 
mailto:srikanth.vavilapa...@ericsson.com>> 
wrote:

Hi

Can we have a quick discussion in any weekly meeting (sdnvpn, functest?) on 
this topic to pick the best approach to move forward? Also Xu Dan has raised 
few other concerns on the location of log files and option for disabling the 
gathering logs…etc.

Thanks
Srikanth



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Friday, October 13, 2017 4:28 AM
To: Tim Irnich mailto:tim.irn...@ericsson.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi Tim,

My only concern is that by implementing this function inside the test case, we 
might run into exceptions raised if there is a problem with SSH keys or 
whatever other problem accessing the nodes.

Collecting logs when the test fails makes sense, but it doesn’t harm if we 
collect it when it passes as well. Anyway, if we do it only when having 
failures, I imagine that logic could also be implemented post-job by checking 
the "criteria": “FAIL" value on the DB and executing some j-job to collect the 
logs. This logs could be uploaded to artifact repo for further analysis as we 
do for the Functest logs.

Regards,
Jose




On 13 Oct 2017, at 09:27, Tim Irnich 
mailto:tim.irn...@ericsson.com>> wrote:

Jose,

I see the point of avoiding log collection in the code for test execution to 
avoid false negatives in case something with the log collection itself goes 
wrong (although I’m wondering a bit if that cannot also be handled by carefully 
implementing the test pass/fail criteria).

There are however cases where we’ll want to collect logs only if a test fails, 
in order to enable a first tier of offline troubleshooting. You’ll remember the 
gather_logs function Niko implemented for the bgpvpn tests – that is one 
example. Can that effectively be handled if we separate things as you suggest?

Regards, Tim


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jose Lausuch
Sent: Friday, October 13, 2017 09:16
To: xudan (N) mailto:xuda...@huawei.com>>; Morgan, Jack 
mailto:jack.mor...@intel.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [functest] [sdnvpn] Proposal for removing 
installer dependent information in the test tools

Hi,

When it comes to log collection, I strongly believe it should be done post-job 
in our CI pipeline, not as part of the test case. Users can always collect logs 
manually regardless of the installer tools they use…

And regarding making it automated in OPNFV after Functest/Yardstick execution, 
would it make sense to re-use the PDF (Pod Descriptor File)? Otherwise, we are 
duplicating config files like pod.yaml or new files with information about the 
servers…
@Jack: is there a possibility to include login information in the PDF (user, 
password, path to private key, …) of the nodes already deployed?

Regards,
Jose




On 12 Oct 2017, at 03:50, xudan (N) 
mailto:xuda...@huawei.com>> wrote:

Hi Srikanth,

I have one question. Are the paths of all these log files constant for 
different environment (Apex, Fuel and commercial deployments)?
If all paths for different deployments are the same, then using config file to 
login and getting files can work.
If not, there will be some errors even tho

[opnfv-tech-discuss] MoMs from the SFC weekly meeting

[Manuel Buil]

Hi,

Here are the MoMs:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2017/opnfv-sfc.
2017-10-18-14.02.html

Thanks,
Manuel___
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

[Sofia Wallin]

The current theme (color scheme, font size and font type) one is what’s being 
used on https://www.opnfv.org/

Best option or not... I’ll wait and see what the feedback is. The font type 
will probably stay but to change the font size is this not a big deal.

Thanks,
Sofia

From: Gerald Kunzmann 
Date: Wednesday, 18 October 2017 at 14:16
To: Sofia Wallin , OPNFV 

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

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/

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
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
 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] On Behalf Of Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
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

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/

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
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
 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] On Behalf Of Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
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
 ?

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 ta

Re: [opnfv-tech-discuss] Support of new types in TOSCA

[xdy shang]

Hi, Julien and Serena.
I'am sorry missed Serena's email in my office mail, and i cann't find the
real reason. Please add my gmail in the receivers in the future, thanks.

As julien said, adding tosca in verigraph is great ideal. From the Tosca
specification point of view, if the basic types(node type, relationship
type, requirement type, etc.) don't meet the requirements, you can
optionally add custom types as long as the specification constraints can be
satisfied, the point is how to use the topology(defined with new types)
parsed by tosca-parser.

We can discusse it again through email or usring meeting or irc. and it
will be better for our discussion if you could send your demand ahead of
schedule.


On Wed, Oct 18, 2017 at 7:14 PM, Julien  wrote:

> cc to Shang's another email-box.
>
>
> Julien 于2017年10月16日周一 上午9:12写道：
>
>> Hi Serena,
>>
>> It's a great news for TOSCA supported in Verigraph. It will make TOSCA
>> template more useful and enhance Parser ecosystem. Currently Parser is
>> integrating with ONAP project.
>>
>> If it is reasonable, we can add it in Parser project. Let's discuss this
>> issue in email or with a meeting.
>> Xiaodong, can you hold a team meeting using zoom?
>>
>> BR/Julien
>>
>>
>> Serena Spinoso 于2017年10月7日周六 下午10:38写道：
>>
>>> Hi Shang, All,
>>>
>>> we would like to add the support of TOSCA in Verigraph, but we noticed
>>> that our catalogue of network functions does not exactly match with the
>>> types of nodes offered by TOSCA. That is the reason why we would kindly
>>> ask you how we can add new node types in TOSCA and, in turn, in Parser.
>>>
>>> Thanks a lots.
>>>
>>> Serena
>>>
>>> --
>>> Research Fellow
>>> Politecnico di Torino
>>> DAUIN - Dipartimento di Automatica e Informatica
>>> Email: serena.spin...@polito.it
>>>
>>> ___
>>> 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] [opnfvdocs] Question on font size and page width

[Sofia Wallin]

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/

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 
Date: Wednesday, 18 October 2017 at 10:51
To: Sofia Wallin , OPNFV 

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) ; 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
 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] On Behalf Of Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
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
 ?

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

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

Re: [opnfv-tech-discuss] Support of new types in TOSCA

[Julien]

cc to Shang's another email-box.


Julien 于2017年10月16日周一 上午9:12写道：

> Hi Serena,
>
> It's a great news for TOSCA supported in Verigraph. It will make TOSCA
> template more useful and enhance Parser ecosystem. Currently Parser is
> integrating with ONAP project.
>
> If it is reasonable, we can add it in Parser project. Let's discuss this
> issue in email or with a meeting.
> Xiaodong, can you hold a team meeting using zoom?
>
> BR/Julien
>
>
> Serena Spinoso 于2017年10月7日周六 下午10:38写道：
>
>> Hi Shang, All,
>>
>> we would like to add the support of TOSCA in Verigraph, but we noticed
>> that our catalogue of network functions does not exactly match with the
>> types of nodes offered by TOSCA. That is the reason why we would kindly
>> ask you how we can add new node types in TOSCA and, in turn, in Parser.
>>
>> Thanks a lots.
>>
>> Serena
>>
>> --
>> Research Fellow
>> Politecnico di Torino
>> DAUIN - Dipartimento di Automatica e Informatica
>> Email: serena.spin...@polito.it
>>
>> ___
>> 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] [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
 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] On Behalf Of Kunzmann, 
Gerald
Sent: Monday, October 02, 2017 8:37 AM
To: 
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
 ?

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

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] 答复: [Auto] Re: All pods are pending when setting up kubernetes

[huangxiangyu]

The prepull_docker.sh works and I can see 7 green lines with Kubectl 
cluster-info. But kubernetes pods just keep pending. Parker would you please 
help to reinstall a Ubuntu 16.04 in this pod ? Maybe there is no such issue in 
ubuntu environment.

发件人: Michael O'Brien [mailto:frank.obr...@amdocs.com]
发送时间: 2017年10月18日 4:31
收件人: Tina Tsou ; huangxiangyu ; 
lylav...@iol.unh.edu; pberber...@iol.unh.edu
抄送: opnfv-tech-discuss@lists.opnfv.org; onap-disc...@lists.onap.org
主题: RE: [Auto] Re: All pods are pending when setting up kubernetes

Tina, Harry,
   It looks like your kubernetes pods under rancher are not up – they are all 
0/1 or 0/3 – in the instructions after setting up your kube client run
Kubectl cluster-info
– you should see all 7 green lines – errors usually means there are issues 
either with your file system or dns – are you running collocated (server/client 
on same machine – I think so right?)
  Also I need to update the meeting minutes with the demo video – I’ll post the 
time where I checked this during the demo.

For any image issues - could you verify that you ran the prepull_docker sh 
script from the page
https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation

https://jira.onap.org/secure/attachment/10501/prepull_docker.sh

[https://jira.onap.org/images/icons/issuetypes/story.svg]OOM-328 - Preload 
docker images script before createAll.sh will allow 7 min startup IN 
PROGRESS

curl https://jira.onap.org/secure/attachment/10501/prepull_docker.sh > 
prepull_docker.sh
chmod 777 prepull_docker.sh
nohup ./prepull_docker.sh > prepull.log &


Then do the following to verify that at least all the docker images were pulled.
Docker images

After that try bringing up an independent component like onap-robot – this does 
not need anything else and can be used to verify your install

./createAll.bash –n onap –a onap-robot

/michael



From: Tina Tsou [mailto:tina.t...@arm.com]
Sent: Tuesday, October 17, 2017 13:21
To: huangxiangyu mailto:huangxiang...@huawei.com>>; 
lylav...@iol.unh.edu; 
pberber...@iol.unh.edu
Cc: Michael O'Brien mailto:frank.obr...@amdocs.com>>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [Auto] Re: All pods are pending when setting up kubernetes

Include UNH Lab...


Thank you,
Tina

On Oct 16, 2017, at 11:33 PM, huangxiangyu 
mailto:huangxiang...@huawei.com>> wrote:
HI Michael

Currently I manage to bring up onap pods in our local lab and most of them are 
in running state. But there seem to be a rancher bug that block me in UNH lab.  
Everything seems fine and throws no error when I created rancher-agent. Somehow 
pods in kube-system just keep getting stuck in pending state. I check the 
docker images and even images for these pods are not pulled.
[root@pod1 ~]# kubectl get pods --all-namespaces -a
NAMESPACE NAME   READY STATUS
RESTARTS   AGE
kube-system   heapster-4285517626-8r16j  0/1   Pending   0  
20h
kube-system   kube-dns-638003847-hkn34   0/3   Pending   0  
20h
kube-system   kubernetes-dashboard-716739405-n7x9l   0/1   Pending   0  
20h
kube-system   monitoring-grafana-2360823841-bfd5b0/1   Pending   0  
1d
kube-system   monitoring-influxdb-2323019309-mgnb5   0/1   Pending   0  
1d
kube-system   tiller-deploy-737598192-dq0pm  0/1   Pending   0  
1d

This new pod should be powerful enough but still installed centos. I used to 
have no problem when setting up undercloud in previous pod which is also a 
centos pod. Have you ever met this problem ? or maybe we should ask UNH lab to 
reinstall a Ubuntu OS.

Thanks
Harry Huang

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.
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss