[opnfv-tech-discuss] [OVN4NFV] Weekly Meeting (10th April 2018) - Cancelled.

[Trinath Somanchi]

Hi -

Today's weekly meeting is cancelled.

If you find some topic to be discussed, please mail me.

Lets meet next week (17th April 2018).

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

Re: [opnfv-tech-discuss] Guideline for participants //RE: Discussion about Fraser Plugfest/Plugtest from Testperf

[Yuyang (Gabriel)]

Thanks Trevor and Al,

I have registered! :)

Best,
Gabriel

From: MORTON, ALFRED C (AL) [mailto:a...@research.att.com]
Sent: Tuesday, April 10, 2018 5:31 AM
To: Cooper, Trevor ; Yuyang (Gabriel) 
; pierre.lynch 
Cc: test-wg ; Brattain, Ross B 
; georg.kunz ; tim.irnich 
; ahothan ; mark.beierl 
; cedric.olivier ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Also, The ETSI folks said that registration deadline is now
April 15th. (can’t remember if the new date was mentioned this morning)

Al

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Monday, April 9, 2018 4:59 PM
To: Yuyang (Gabriel) 
>; pierre.lynch 
>
Cc: test-wg >; 
Brattain, Ross B >; 
MORTON, ALFRED C (AL) >; 
georg.kunz >; 
tim.irnich >; ahothan 
>; mark.beierl 
>; cedric.olivier 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hi Gabriel …this is the registration link 
https://portal.etsi.org/webapp/plugtests/Register.asp?EventID=250

/Trevor



From: Yuyang (Gabriel) [mailto:gabriel.yuy...@huawei.com]
Sent: Wednesday, April 04, 2018 10:51 AM
To: pierre.lynch >
Cc: test-wg >; 
Brattain, Ross B >; 
Cooper, Trevor >; 
acmorton >; georg.kunz 
>; tim.irnich 
>; ahothan 
>; mark.beierl 
>; cedric.olivier 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hi Pierre,

Thanks a lot for all these information! I have subscribed your new email to the 
test-wg email list: 
https://lists.opnfv.org/mailman/listinfo/test-wg.
 I will send you the password in another mail.

I echo that it is a great idea to involve dovetail in ETSI Plugtest and we 
should start our pre-testing now.
From what I know, the release set and optional set (draft) of test cases of 
Dovetail has already included some tests from Funtest, Yarstick and Bottlenecks.
As to other test cases from our testing projects, we should also need the 
feedbacks before the weekend.
We could dicuss it at tomorrow's Testperf meeting.

Moreover, I could not find the registration link for ETSI plugtest. It is said 
on the website that the registration ends at March 31st.
Could you also help with that? Thanks a lot!


Best,
Gabriel
发件人： pierre.lynch
收件人： Yuyang 
(Gabriel)>
抄送： 
test-wg>;ross.b.brattain>;trevor.cooper>;acmorton>;georg.kunz>;tim.irnich>;ahothan>;mark.beierl>;cedric.olivier>
主题： Re: Guideline 

Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on LaaS ARM

[Alexandru Avadanii]

Hi,

+Joe


Lincoln is right, you could spawn a VM, but it would be emulated without hw 
acceleration, so not really useful.

Reserving a single aarch64 node might be limiting though, Armband Fuel requires 
at least 6 nodes (1 jump server + 5 cluster nodes) right now.

Not sure what the mininum requirement for Compass4NFV + k8 are, but if you want 
to stick to Openstack, you should try reserving more nodes (afaik, there are 
enough available in UNH lab).


BR,

Alex


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
 on behalf of Lincoln Lavoie 

Sent: Friday, April 6, 2018 4:48:18 PM
To: Beierl, Mark
Cc: opnfv-tech-discuss@lists.opnfv.org; Parker Berberian
Subject: Re: [opnfv-tech-discuss] [armband] [fuel] Deployment file for Fuel on 
LaaS ARM

Hi Mark,

I think you can do a virtual deployment, which is 1 level of VMs.  But, I don't 
think you can host a VM on top of the open stack deployment (because that's 
nested).

Cheers,
Lincoln

On Fri, Apr 6, 2018 at 9:45 AM, Beierl, Mark 
> wrote:
Hello, Parker, and thanks for the quick response.

So to be clear, I cannot deploy OPNFV on this system at this time?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com

On Apr 6, 2018, at 09:43, Parker Berberian 
> wrote:

Mark,

You have to be mindful that ARM does not support nested virtualization (and 
therefore virtual deployments with openstack are impossible). If Fuel does not 
support Kubernetes, then you may be out of luck until we can provide pharos 
POD's through LaaS.

Thanks,
Parker

On Fri, Apr 6, 2018 at 9:39 AM, Beierl, Mark 
> wrote:
Hello, folks!

I have reserved an Arm server (arm41) in the LaaS and it's ready.  I am 
wondering if anyone has a configuration file for deploying Fuel on a single Arm 
server that I can borrow for this?

Or is there a better way to deploy Fuel on Arm, like re-using an existing 
Jenkins job?

Regards,
Mark

Mark Beierl
SW System Sr Principal Developer
Dell EMC | Cloud & Communication Service Provider Solution
mobile +1 613 314 8106
mark.bei...@dell.com






--
***
Lincoln Lavoie
Senior Engineer, Broadband Technologies

[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]
www.iol.unh.edu
21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
lylav...@iol.unh.edu
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/facebook.png]
  [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/twitter.png] 

   [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/linkedin.png] 


Ars sine scientia nihil est! -- Art without science is nothing.
Scientia sine ars est vacua! -- Science without art is empty.

Broadband Forum Gfast Certified Product 

Re: [opnfv-tech-discuss] Guideline for participants //RE: Discussion about Fraser Plugfest/Plugtest from Testperf

[MORTON, ALFRED C (AL)]

Also, The ETSI folks said that registration deadline is now
April 15th. (can’t remember if the new date was mentioned this morning)

Al

From: Cooper, Trevor [mailto:trevor.coo...@intel.com]
Sent: Monday, April 9, 2018 4:59 PM
To: Yuyang (Gabriel) ; pierre.lynch 

Cc: test-wg ; Brattain, Ross B 
; MORTON, ALFRED C (AL) ; 
georg.kunz ; tim.irnich ; 
ahothan ; mark.beierl ; cedric.olivier 
; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hi Gabriel …this is the registration link 
https://portal.etsi.org/webapp/plugtests/Register.asp?EventID=250

/Trevor



From: Yuyang (Gabriel) [mailto:gabriel.yuy...@huawei.com]
Sent: Wednesday, April 04, 2018 10:51 AM
To: pierre.lynch >
Cc: test-wg >; 
Brattain, Ross B >; 
Cooper, Trevor >; 
acmorton >; georg.kunz 
>; tim.irnich 
>; ahothan 
>; mark.beierl 
>; cedric.olivier 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hi Pierre,

Thanks a lot for all these information! I have subscribed your new email to the 
test-wg email list: 
https://lists.opnfv.org/mailman/listinfo/test-wg.
 I will send you the password in another mail.

I echo that it is a great idea to involve dovetail in ETSI Plugtest and we 
should start our pre-testing now.
From what I know, the release set and optional set (draft) of test cases of 
Dovetail has already included some tests from Funtest, Yarstick and Bottlenecks.
As to other test cases from our testing projects, we should also need the 
feedbacks before the weekend.
We could dicuss it at tomorrow's Testperf meeting.

Moreover, I could not find the registration link for ETSI plugtest. It is said 
on the website that the registration ends at March 31st.
Could you also help with that? Thanks a lot!


Best,
Gabriel
发件人： pierre.lynch
收件人： Yuyang 
(Gabriel)>
抄送： 
test-wg>;ross.b.brattain>;trevor.cooper>;acmorton>;georg.kunz>;tim.irnich>;ahothan>;mark.beierl>;cedric.olivier>
主题： Re: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf
时间： 2018-04-04 22:38:48

Hello all,

First: looks like I am not subscribed to the test-wg list, so my last email 
bounced back to me. I didn’t find it on the OPNFV mailing lists site….can 
someone please subscribe me to that? New email: 
pierre.ly...@keysight.com

I spoke with Silvia Almagia, the Plugtest organizer at ETSI.


  *   I told her about the plan to brainstorm in the community which scenarios 
(features) could be brought to the Plugtest. It will be like I described: each 
scenario would be listed as a separate platform for scheduling purposes.
  *   There is no formal process to insert test cases directly into the test 
plan. It’s done by suggesting and discussing it on the Plugtest email list, and 
then discussing it during the weekly meeting. There are people who will help to 
format it correctly, etc.

 *   In order to do this, you need to be registered to the Plugtest.
 *   The test case should involve 

Re: [opnfv-tech-discuss] Guideline for participants //RE: Discussion about Fraser Plugfest/Plugtest from Testperf

[Cooper, Trevor]

Hi Gabriel …this is the registration link 
https://portal.etsi.org/webapp/plugtests/Register.asp?EventID=250

/Trevor



From: Yuyang (Gabriel) [mailto:gabriel.yuy...@huawei.com]
Sent: Wednesday, April 04, 2018 10:51 AM
To: pierre.lynch 
Cc: test-wg ; Brattain, Ross B 
; Cooper, Trevor ; acmorton 
; georg.kunz ; tim.irnich 
; ahothan ; mark.beierl 
; cedric.olivier ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf

Hi Pierre,

Thanks a lot for all these information! I have subscribed your new email to the 
test-wg email list: https://lists.opnfv.org/mailman/listinfo/test-wg. I will 
send you the password in another mail.

I echo that it is a great idea to involve dovetail in ETSI Plugtest and we 
should start our pre-testing now.
From what I know, the release set and optional set (draft) of test cases of 
Dovetail has already included some tests from Funtest, Yarstick and Bottlenecks.
As to other test cases from our testing projects, we should also need the 
feedbacks before the weekend.
We could dicuss it at tomorrow's Testperf meeting.

Moreover, I could not find the registration link for ETSI plugtest. It is said 
on the website that the registration ends at March 31st.
Could you also help with that? Thanks a lot!


Best,
Gabriel

发件人： pierre.lynch
收件人： Yuyang 
(Gabriel)>
抄送： 
test-wg>;ross.b.brattain>;trevor.cooper>;acmorton>;georg.kunz>;tim.irnich>;ahothan>;mark.beierl>;cedric.olivier>
主题： Re: Guideline for participants //RE: Discussion about Fraser 
Plugfest/Plugtest from Testperf
时间： 2018-04-04 22:38:48

Hello all,

First: looks like I am not subscribed to the test-wg list, so my last email 
bounced back to me. I didn’t find it on the OPNFV mailing lists site….can 
someone please subscribe me to that? New email: 
pierre.ly...@keysight.com

I spoke with Silvia Almagia, the Plugtest organizer at ETSI.


  *   I told her about the plan to brainstorm in the community which scenarios 
(features) could be brought to the Plugtest. It will be like I described: each 
scenario would be listed as a separate platform for scheduling purposes.
  *   There is no formal process to insert test cases directly into the test 
plan. It’s done by suggesting and discussing it on the Plugtest email list, and 
then discussing it during the weekly meeting. There are people who will help to 
format it correctly, etc.

 *   In order to do this, you need to be registered to the Plugtest.
 *   The test case should involve interoperability. That’s the goal of the 
Plugtest, so it should involve the three functional blocks: Platform 
(NFVI+VIM), MANO and VNF(s)
 *   If it doesn’t meet the criteria above, it can still be done in a 
separate track

  *   Dovetail

 *   We can include a separate (optional) track to have Dovetail testing at 
the Plugtest. I can introduce it to the team at a weekly meeting, and then we 
can start planning it. This would likely involve finding out who of the 
platform vendors would like to attempt it

The most important point: time is getting critical. If a VPN connection to HIVE 
is necessary, it takes a bit of time. Plus there is pre-testing to be done 
between now and the Plugtest event itself. We really need to get moving with 
this.


Best Regards,

Pierre

***Please note the new email and phone number***
Pierre Lynch
Lead Technologist
Ixia Solutions Group
Keysight Technologies
M: +19193788248
pierre.ly...@keysight.com


From: Pierre Lynch >
Date: Wednesday, April 4, 2018 at 8:16 AM
To: "Yuyang (Gabriel)" 
>
Cc: "test...@lists.opnfv.org" 
>, "Brattain, Ross B" 
>, Trevor Cooper 
>, "MORTON, ALFRED C 
(AL)" >, Georg Kunz 
>, Tim Irnich 

Re: [opnfv-tech-discuss] [RelEng] Docker container build triggered by tag + committers permission on DockerHub folder

[Trevor Bramwell]

Hi Alec,

If your project has a '{project}-docker-build-push-{stream}' job defined[1] any
tags added to the project repo will trigger a docker build (regardless of tag
format). So you don't need to add the 'gerrit-trigger-tag-created'[2] to your
project (unless you want to do something different for tagged/merge jobs?)

I believe currently builds on the master branch are tagged (in dockerhub)
'latest', while builds on the stable branch are tagged 'stable'.

> Is that sufficient to trigger a container build based on the tag that is just
> pushed and create a container with docker tag set to the same value and push
> it to docker hub?

These docker builds will be tagged with the tag name used in git. For
example, if you created a 1.0.0 tag on the nvfbench repo, then a docker build 
'opnfv/nfvbench:1.0.0' should be pushed to docker-hub.

> Does that apply to all branches?
I actually don't know, and that's an interesting question. From my
understanding of git-internals, tags exist independent of branches as the hash
of a git-tree, though that does mean they are intrinsicly linked to a branch.

The clone happens against GERRIT_REFSPEC, which resolves to refs/heads/... for
a branch and refs/tags/... for tags. You'll have to find out and let us know
if a trigger-by-tag build creates jobs for both '-master' and '-fraser'.

> Does that apply to any tag (regardless of format/syntax)?
Yep. The trigger doesn't look for any specific format beyond there being a tag
created.

For dockerhub, please create a helpdesk ticket (helpd...@opnfv.org) and let me
know your dockerhub username and I'd be happy to get you access.

Regards,
Trevor Bramwell

[1] https://git.opnfv.org/releng/tree/jjb/releng/opnfv-docker.yml#n277
[2] https://git.opnfv.org/releng/tree/jjb/global/releng-macros.yml#n176

On Sat, Apr 07, 2018 at 04:42:25PM +, Alec Hothan (ahothan) wrote:
> Hi Trevor
> 
> Finally found a bit of time to try the new trigger to build a container based 
> on a tag (introduced in https://gerrit.opnfv.org/gerrit/#/c/48049)
> Given that I could not find any documentation on how to do that, could you 
> check if I missed anything?
> The tentative diff in releng file to achieve that:
> https://gerrit.opnfv.org/gerrit/55149
> 
> Is that sufficient to trigger a container build based on the tag that is just 
> pushed and create a container with docker tag set to the same value and push 
> it to docker hub?
> Does  that apply to all branches?
> Does that apply to any tag (regardless of format/syntax)?
> 
> Finally, as we discussed last week at ONS, please provide permission to 
> manage my project dockerhub folder.
> 
> Thanks
> 
>   Alec
> 
> 
> 


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] [Fuel] [Danube] openstack step in fuel install fails with pacemaker

[Damon2]

Julien,

Did you set this up, and can share the steps?  How would you ensure you only 
pull down 16.04.03?

D

 

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Julien
Sent: Monday, April 09, 2018 11:41 AM
To: Damon
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] [Danube] openstack step in fuel 
install fails with pacemaker

 

Hi,

 

I meet the same issue a month ago. It is because that Ubuntu release 16.04.04 
LTS in March 2018, while it is only 16.04.02 LTS when Danube released. There 
are some of the packages updated from the Ubuntu OS. They are not compatible 
with Fuel installers' packages.

 

There are other packages issues when you even resolved this one. The only 
possible way is to set up a local apt repo with the version 16.04.03 at most.

 

BR,

Julien

 

 

 

Damon 于2018年4月9日周一 上午11:41写道：

 

OPNFV – Danube 3.0 Fuel install error.

I am getting this error during the openstack install process.  I have installed 
OS using fuel many times before on previous Openstack releases, and never ran 
into this.

It says pacemaker can’t install without corosync, but corosync does appear to 
be installed.  Would anyone know why I’m seeing this error?

 

Tried this with a single controller and a dual one, same result.  Node is 
simple KVM, standard OVS VLAN config, with cinder as storage.

 

This is the command the install script seems to be failing at:

 

root@node-10:~# /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold -o 
APT::Get::AllowUnauthenticated=1 install pacemaker

Reading package lists...

Building dependency tree...

Reading state information...

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

 

The following packages have unmet dependencies:

pacemaker : Depends: corosync (>= 2.3.0) but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

root@node-10:~#

 

Coroysnc appears to be installed passed the required version.

 

||/ Name  Version Architecture  
  Description

+++-=-===-===-

ii  corosync  2.3.5-3ubuntu2.1amd64 
  cluster engine daemon and utilities

root@node-10:~#

 

 

Puppet log, which is basically the output of the failed command.


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) E: Unable to correct 
problems, you have held broken packages.


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) pacemaker : Depends: corosync 
(>= 2.3.0) but it is not going to be installed


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) The following packages have 
unmet dependencies:


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure)


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) The following information may 
help to resolve the situation:


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) or been moved out of Incoming.


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) distribution that some 
required packages have not yet been created


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) requested an impossible 
situation or if you are using the unstable


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) Some packages could not be 
installed. This may mean that you have


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) Reading state information...


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) Building dependency tree...


2018-04-06 14:42:07

ERR

(/Stage[main]/Corosync/Package[pacemaker]/ensure) change from purged to present 
failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold 
-o APT::Get::AllowUnauthenticated=1 install pacemaker' returned 100: Reading 
package lists...

 

 

___
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 Doctor weekly meeting

[Juvonen, Tomi (Nokia - FI/Espoo)]

Hi,

As it was discussed in the today's meeting, we could still move to use 9am UTC 
starting from next week (16th April). This would also take the late vote into 
consideration given to meeting time voting.

If no objections before weekend, I will change accordingly.

Thanks,
Tomi

P.S. Note the zoom will then again change

-Original Appointment-
From: Juvonen, Tomi (Nokia - FI/Espoo) [mailto:tomi.juvo...@nokia.com]
Sent: Monday, April 09, 2018 9:47 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] OPNFV Doctor weekly meeting
When: Occurs every maanantai effective 9.4.2018 until 31.12.2018 from 13:00 to 
14:00 FLE Standard Time.
Where: zoom


This sender failed our fraud detection checks and may not be who they appear to 
be. Learn about spoofing

Feedback

Doctor is a fault management and maintenance project to develop and realize the 
consequent implementation for the OPNFV reference platform.
More details:
https://etherpad.opnfv.org/p/doctor_meetings
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/5014627785
Or iPhone one-tap :
US: +16699006833,,5014627785# or +16465588656,,5014627785#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 
880 1246 (Toll Free)
Meeting ID: 501 462 7785
International numbers available: 
https://zoom.us/zoomconference?m=cpvYf3PSXuESVw8UnsBwch31JgoOq2JC
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] [Danube] openstack step in fuel install fails with pacemaker

[Julien]

Hi,

I meet the same issue a month ago. It is because that Ubuntu release
16.04.04 LTS in March 2018, while it is only 16.04.02 LTS when Danube
released. There are some of the packages updated from the Ubuntu OS. They
are not compatible with Fuel installers' packages.

There are other packages issues when you even resolved this one. The only
possible way is to set up a local apt repo with the version 16.04.03 at
most.

BR,
Julien



Damon 于2018年4月9日周一 上午11:41写道：

>
>
> OPNFV – Danube 3.0 Fuel install error.
>
> I am getting this error during the openstack install process.  I have
> installed OS using fuel many times before on previous Openstack releases,
> and never ran into this.
>
> It says pacemaker can’t install without corosync, but corosync does appear
> to be installed.  Would anyone know why I’m seeing this error?
>
>
>
> Tried this with a single controller and a dual one, same result.  Node is
> simple KVM, standard OVS VLAN config, with cinder as storage.
>
>
>
> This is the command the install script seems to be failing at:
>
>
>
> root@node-10:~# /usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold
> -o APT::Get::AllowUnauthenticated=1 install pacemaker
>
> Reading package lists...
>
> Building dependency tree...
>
> Reading state information...
>
> Some packages could not be installed. This may mean that you have
>
> requested an impossible situation or if you are using the unstable
>
> distribution that some required packages have not yet been created
>
> or been moved out of Incoming.
>
> The following information may help to resolve the situation:
>
>
>
> The following packages have unmet dependencies:
>
> pacemaker : Depends: corosync (>= 2.3.0) but it is not going to be
> installed
>
> E: Unable to correct problems, you have held broken packages.
>
> root@node-10:~#
>
>
>
> Coroysnc appears to be installed passed the required version.
>
>
>
> ||/ Name  Version
> ArchitectureDescription
>
>
> +++-=-===-===-
>
> ii  corosync  2.3.5-3ubuntu2.1
> amd64   cluster engine daemon and utilities
>
> root@node-10:~#
>
>
>
>
>
> Puppet log, which is basically the output of the failed command.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) E: Unable to correct
> problems, you have held broken packages.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) pacemaker : Depends:
> corosync (>= 2.3.0) but it is not going to be installed
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following packages
> have unmet dependencies:
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure)
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) The following
> information may help to resolve the situation:
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) or been moved out of
> Incoming.
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) distribution that some
> required packages have not yet been created
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) requested an impossible
> situation or if you are using the unstable
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Some packages could not
> be installed. This may mean that you have
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Reading state
> information...
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) Building dependency
> tree...
>
> 2018-04-06 14:42:07
>
> ERR
>
> (/Stage[main]/Corosync/Package[pacemaker]/ensure) change from purged to
> present failed: Execution of '/usr/bin/apt-get -q -y -o
> DPkg::Options::=--force-confold -o APT::Get::AllowUnauthenticated=1 install
> pacemaker' returned 100: Reading package lists...
>
>
>
>
> ___
> 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] [pharos][infra-wg] PDF Sepc 1.0

[Julien]

Hi OPNFV lab owners,

According to TSC meeting on Mar. 30th, the first 3 stages has been approved
by the TSC(https://wiki.opnfv.org/display/meetings/tsc#TSC-March20,2018)
"*TSC approved the PDF spec 1.0 as mandatory baseline for CI in Pharos pods
and the three staged introduction time plan"*

If the CI POD does not meet the requirement, you should give an exception
request to the TSC.

As for stage 1, there is only one week left.
Please submit your PDFs patches and Infra and Pharos team will help to
review your patches.

BR,
Julien

Julien 于2018年3月19日周一 下午8:40写道：

> Hi OPNFV lab owners,
>
> I got the email list from [1]. If you are not the correct person, please
> correct me.
>
> With the help of the community, we have implemented most the PDF features
> for the physical POD.
> According to the discussion in INFRA WG and TC, we propose the PDF Spec
> 1.0 to the TSC to be approved at this week's TSC meeting.
> Currently, 17 PDF files have been submitted from 8 Labs.
>
> You can get detail PDF specifications on the link[2].
> The schedule of the PDF in the proposal is listed here.
>
>- Stage1: April 15th
>Final date for lab owners to create PDFs for CI resources
>- Stage2: June 15th
>2.1 Final date for installers to use PDF/IDF for production
>2.2 Final date for CI PODs to adopt PDF/IDF
>- Stage3: August 15th
>3.1 Final date for all community labs to adopt PDF/IDF
>3.2 Final date for LaaS to adopt PDF/IDF
>
>
> I would like to double check with you about your plan to meet the
> schedule.
> Can you provide all the PDF files of your PODs according to the schedule?
> If yes, what's your plan?
>
> [1], https://wiki.opnfv.org/display/pharos/Community+Labs
> [2],
> https://docs.google.com/viewer?url=https%3A%2F%2Fwiki.opnfv.org%2Fdownload%2Fattachments%2F2925933%2FPDF%2520-report.pdf%3Fversion%3D1%26modificationDate%3D1520873681000%26api%3Dv2=true=false=1
>
>
> If you have any question about PDF Spec 1.0, please contact me or INFRA WG.
>
> BR,
> Julien
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [docs] Cross Community Documentation effort

[Thanh Ha]

Hi Everyone,

Just a gentle reminder to fill out the doodle. I'm thinking I will leave
this open about another week before picking a date for the first meeting.

Thanks,
Thanh


On Thu, Apr 5, 2018 at 7:26 PM, Thanh Ha 
wrote:

> On Thu, Apr 5, 2018 at 6:03 PM, Thanh Ha 
> wrote:
>
>> Hi Everyone,
>>
>> I believe I've included everyone who has indicated they were interested
>> in cross community docs efforts. If you are not interested feel free to
>> mute this thread.
>>
>> I've tried to include community mailing lists where existing to reach
>> hopefully the right audience for this email. If anyone knows of folks who
>> should be included please feel free to add them to this thread.
>>
>> At ONS we few of us from the ODL, OPNFV, and ONAP communities got
>> together to discuss some cross community documentation efforts we've been
>> pushing. We discussed lfdocs [0][1] and lfdocs-conf [2][3] projects who's
>> purpose is to enable projects to easily share common configuration as well
>> as create common documentation that projects can link to using
>> intersphinx linking rather than rewriting their own.
>>
>> One of the things that came out of the meeting was that it would be good
>> to create a cross-project-docs community so that we can ask questions and
>> share ideas since all of us are using very similar tooling to build our
>> docs.
>>
>> For a start I've created an IRC channel #lf-docs @ irc.freenode.net
>> which I hope folks will join and discuss docs related things in. It could
>> be a valuable resource rather than all of us hanging in our own small docs
>> communities I'm sure we are all understaffed as it is.
>>
>> We should setup a mailing list somewhere, I'll work with LF to figure out
>> where the best place for such a list is such that it is not specific to any
>> project.
>>
>> Also there was discussion about setting up some kind of regular meeting
>> maybe once a month where we can all get together and sync up to share any
>> ideas we have. I think there are 2 things we need to figure out together:
>>
>> 1. How often is the right amount as to not overload everyone with
>> meetings but give us time to get together?
>> 2. What is the best time for the meeting?
>>
>> For 2 I've created a doodle poll please ignore the dates as we are only
>> interested in finding out during any given week which times are generally
>> good for folks. Please respond with the times that are okay with you and
>> we'll try to pick a time that is good for the most people.
>>
>> https://doodle.com/poll/dykpgubs3fvd2agw
>>
>> Regards,
>> Thanh
>>
>> [0] http://docs.releng.linuxfoundation.org/en/latest/
>> [1] https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/docs
>> [2] http://docs.releng.linuxfoundation.org/projects/lfdocs-
>> conf/en/latest/index.html
>> [3] https://gerrit.linuxfoundation.org/infra/#/admin/
>> projects/releng/docs-conf
>>
>
>
> Adding some more folks to the list.
>
> Regards,
> Thanh
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Updated invitation: [qtip] Project Weekly Meeting @ Weekly from 15:30 to 16:30 on Monday from Mon 2017-07-03 to Sun 2018-04-08 (CST) (opnfv-tech-discuss@lists.opnfv.org)

[zhangyujun]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Shanghai
X-LIC-LOCATION:Asia/Shanghai
BEGIN:STANDARD
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:CST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Shanghai:20170703T153000
DTEND;TZID=Asia/Shanghai:20170703T163000
EXDATE;TZID=Asia/Shanghai:20170501T153000
EXDATE;TZID=Asia/Shanghai:20170612T153000
RRULE:FREQ=WEEKLY;UNTIL=20180408T155959Z;BYDAY=MO
DTSTAMP:20180409T081126Z
ORGANIZER;CN=opnfv-qtip:mailto:pidut08o57erkd7gv17vns6...@group.calendar.go
 ogle.com
UID:l5aqhe2gjdc7u3jirsn9aqi...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=serena.feng@gmail.com;X-NUM-GUESTS=0:mailto:serena.feng.711@gma
 il.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=zhihui.wu2...@gmail.com;X-NUM-GUESTS=0:mailto:zhihui.wu2...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Taseer Ahmed;X-NUM-GUESTS=0:mailto:tasee...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Akhil Batra;X-NUM-GUESTS=0:mailto:akhil.batra...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhifeng jiang;X-NUM-GUESTS=0:mailto:zhifeng.jian...@gmail.com
CREATED:20170331T081738Z
DESCRIPTION:Regular agenda\n\n- action follow up\n- weekly status update\n-
  current release progress\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this sectio
 n of the description.\n\nView your event at https://www.google.com/calendar
 /event?action=VIEW=bDVhcWhlMmdqZGM3dTNqaXJzbjlhcWlqbWsgb3BuZnYtdGVjaC1k
 aXNjdXNzQGxpc3RzLm9wbmZ2Lm9yZw=NTIjcGlkdXQwOG81N2Vya2Q3Z3YxN3ZuczY4MzhA
 Z3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWRiNTRkMDdlMzM1ZTFiOTFiMTBkZjJmNjYwMGMxNzZ
 lYTAwOGMxMDA=Asia%2FShanghai=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180409T081126Z
LOCATION:irc://#opnfv-qtip@freenode
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:[qtip] Project Weekly Meeting
TRANSP:OPAQUE
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
END:VEVENT
END:VCALENDAR


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

[opnfv-tech-discuss] Updated invitation: [qtip] Project Weekly Meeting @ Every 2 weeks from 15:30 to 16:30 on Monday (CST) (opnfv-tech-discuss@lists.opnfv.org)

[zhangyujun]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Shanghai
X-LIC-LOCATION:Asia/Shanghai
BEGIN:STANDARD
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:CST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Shanghai:20180416T153000
DTEND;TZID=Asia/Shanghai:20180416T163000
EXDATE;TZID=Asia/Shanghai:20170501T153000
EXDATE;TZID=Asia/Shanghai:20170612T153000
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=MO
DTSTAMP:20180409T081126Z
ORGANIZER;CN=opnfv-qtip:mailto:pidut08o57erkd7gv17vns6...@group.calendar.go
 ogle.com
UID:g84cm41q5le3hdls1eee43q...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=serena.feng@gmail.com;X-NUM-GUESTS=0:mailto:serena.feng.711@gma
 il.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhihui.wu2...@gmail.com;X-NUM-GUESTS=0:mailto:zhihui.wu2006@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Taseer Ahmed;X-NUM-GUESTS=0:mailto:tasee...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Akhil Batra;X-NUM-GUESTS=0:mailto:akhil.batra...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech
 -disc...@lists.opnfv.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhifeng jiang;X-NUM-GUESTS=0:mailto:zhifeng.jian...@gmail.com
CREATED:20170331T081738Z
DESCRIPTION:Regular agenda\n\n- action follow up\n- weekly status update\n-
  current release progress\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this sectio
 n of the description.\n\nView your event at https://www.google.com/calendar
 /event?action=VIEW=Zzg0Y200MXE1bGUzaGRsczFlZWU0M3FhMTggb3BuZnYtdGVjaC1k
 aXNjdXNzQGxpc3RzLm9wbmZ2Lm9yZw=NTIjcGlkdXQwOG81N2Vya2Q3Z3YxN3ZuczY4MzhA
 Z3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbWU3YTg1NTJmMTI0ZmM4M2UzOGNlZWUxN2I2NTcxYzI
 yMGY0MWIyZmU=Asia%2FShanghai=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180409T081126Z
LOCATION:irc://#opnfv-qtip@freenode
SEQUENCE:3
STATUS:CONFIRMED
SUMMARY:[qtip] Project Weekly Meeting
TRANSP:OPAQUE
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
END:VEVENT
END:VCALENDAR


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

[opnfv-tech-discuss] OPNFV Doctor weekly meeting

[Juvonen, Tomi (Nokia - FI/Espoo)]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:FLE Standard Time
BEGIN:STANDARD
DTSTART:16010101T04
TZOFFSETFROM:+0300
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T03
TZOFFSETFROM:+0200
TZOFFSETTO:+0300
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Juvonen, Tomi (Nokia - FI/Espoo)":MAILTO:tomi.juvo...@nokia.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:Doctor is a fault management and maintenance pro
 ject to develop and realize the consequent implementation for the OPNFV re
 ference platform.\nMore details:\nhttps://etherpad.opnfv.org/p/doctor_meet
 ings\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/50146
 27785\nOr iPhone one-tap :\nUS: +16699006833\,\,5014627785# or +1646558865
 6\,\,5014627785#\nOr Telephone:\nDial(for higher quality\, dial a number b
 ased on your current location):\nUS: +1 669 900 6833 or +1 646 558 8656 or
  +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)\nMeeting ID: 5
 01 462 7785\nInternational numbers available: https://zoom.us/zoomconferen
 ce?m=cpvYf3PSXuESVw8UnsBwch31JgoOq2JC\n\n\n
RRULE:FREQ=WEEKLY;UNTIL=20181231T11Z;INTERVAL=1;BYDAY=MO;WKST=MO
UID:04008200E00074C5B7101A82E00890BEE3A7E4CFD301000
 01D2D1BD7816FC84E8F8E2D91ED20C728
SUMMARY;LANGUAGE=en-US:OPNFV Doctor weekly meeting
DTSTART;TZID=FLE Standard Time:20180409T13
DTEND;TZID=FLE Standard Time:20180409T14
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180409T064722Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:zoom
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1500071906
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-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-LOCATIONS:[{"DisplayName":"zoom"\,"LocationAnnotation":""\,"Loc
 ationUri":""\,"LocationStreet":""\,"LocationCity":""\,"LocationState":""\,
 "LocationCountry":""\,"LocationPostalCode":""\,"LocationFullAddress":""}]
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