[opnfv-tech-discuss] Upcoming OPNFV Infrastructure Restarts - 2017-10-08 @ 9:00 - 11:00 PDT (16:00 - 18:00 UTC)

[Trevor Bramwell]

What: Package upgrades and restarts of Gerrit, JIRA, Confluence, and
Etherpad

When: Sun, Oct 8 from 9:00AM-11:00AM PDT (16:00-18:00 UTC)

Why: Outstanding package and kernel updates.

Impact: We will be applying package updates across several systems and
restarting services.

This should cause a brief ( < 30 minutes) outage to the following
services as they are restarted:

 * Gerrit (gerrit.opnfv.org)
 * JIRA (jira.opnfv.org)
 * Confluence (wiki.opnfv.org)
 * Etherpad (etherpad.opnfv.org)

Notices will be sent to the mailing list prior to and after updates.

If you have any questions or concerns, please reach out through
helpd...@opnfv.org.

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

Re: [opnfv-tech-discuss] Problems deploying xci

[Markos Chandras]

Hello,

On 05/10/17 19:06, Manuel Buil wrote:
> Hello,
> 
> I tried today to get familiar with the releng-xci master branch but I
> was very unlucky because I tried two times and both failed.
> 
> First time I tried with flavor= aio and this is the result:
> 
> https://hastebin.com/suseyojepu.md
> 
> Then I tried with flavor = noha and it failed before:

I guess the VM is in 'shut off' state. Try starting the opnfv VM
manually and see what libvirt says.

> 
> https://hastebin.com/oyejesafos.sm
> 
> After this second try, I ran bifrost-provision.sh alone to see if I was
> getting more information but I could not see anything extra
> 
> https://hastebin.com/amaqelafij.coffeescript

Running bifrost-provision.sh doesn't work because it expects to run in
an XCI deployment and certain variables are expected to be set (as the
error suggests)

-- 
markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
___
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] [opnfv-project-leads] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Dave Neary]

+1

Dave.

On 10/05/2017 05:04 AM, Ulrich Kleber wrote:
> +1
> 
>  
> 
> *From:*opnfv-project-leads-boun...@lists.opnfv.org
> [mailto:opnfv-project-leads-boun...@lists.opnfv.org] *On Behalf Of
> *David McBride
> *Sent:* Wednesday, 04 October, 2017 20:44
> *To:* TECH-DISCUSS OPNFV
> *Cc:* opnfv-project-leads; TSC OPNFV; Raymond Paik; Tapio Tallgren
> *Subject:* [opnfv-project-leads] [release][euphrates] proposal to
> eliminate one of the two point releases for Euphrates
> 
>  
> 
> Team,
> 
>  
> 
> Please respond to this mail with (+1, 0, -1) and your thoughts,
> suggestions, or alternatives.  
> 
>  
> 
> During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial
> Euphrates release (5.0) to October 20.  In addition, I also proposed
> eliminating one of the two point releases (5.1, 5.2) planned for
> Euphrates.  The reasoning was as follows:
> 
>  1. Moving the 5.0 release to Oct 20 places that release just 3 weeks
> before the planned release of 5.1 (Nov 10).
>  2. Slipping 5.1 and 5.2 could have negative consequences for the OPNFV
> "F" release, as happened with Euphrates when we decided to slip
> Danube 3.0.
> 
> Therefore, the proposal is to eliminate the planned release on Nov 10,
> so that there would just be one point release on Dec 15.  
> 
>  
> 
> The proposal is described in more detail in the slide deck that I
> presented during the TSC meeting
>  (see
> link labeled "euphrates contingency.pptx" under the heading "Euphrates
> update").
> 
>  
> 
> David
> 
>  
> 
> -- 
> 
> *David McBride*
> 
> Release Manager, OPNFV
> 
> Mobile: +1.805.276.8018 
> 
> Email/Google Talk: dmcbr...@linuxfoundation.org
> 
> 
> Skype: davidjmcbride1
> 
> IRC: dmcbride
> 
> 
> 
> ___
> opnfv-tsc mailing list
> opnfv-...@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tsc
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Problems deploying xci

[Manuel Buil]

Hello,

I tried today to get familiar with the releng-xci master branch but I
was very unlucky because I tried two times and both failed.

First time I tried with flavor= aio and this is the result:

https://hastebin.com/suseyojepu.md

Then I tried with flavor = noha and it failed before:

https://hastebin.com/oyejesafos.sm

After this second try, I ran bifrost-provision.sh alone to see if I was
getting more information but I could not see anything extra

https://hastebin.com/amaqelafij.coffeescript

Any idea?

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] [announce] F-release name poll (part II)

[Raymond Paik]

A quick reminder that the poll closes tomorrow at 5pm Pacific Time if you
haven't voted yet...

On Sun, Oct 1, 2017 at 1:36 PM, Raymond Paik 
wrote:

> All,
>
> Here's the new poll for the F-release name:
> https://www.surveymonkey.com/r/Y2CFCKP
>
> The poll will close at 5pm Pacific Time on October 6th (Friday). Happy
> voting (again) :-) .
>
> Thanks,
>
> Ray
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Euphrates release DOC preparation

[Alec Hothan (ahothan)]

I would like to bring your attention on one discussion happening in the 
functest DOC gerrit review and that concerns every project that participates to 
euphrates.
The question is should each project doc mention exactly which version of 
artifact to use (in case of functest it will be the exact dockerhub tag to pull)

Firstly, the project documentation as currently packaged is clearly related to 
an OPNFV release because it is part of an umbrella doc which is clearly labeled 
for a given release, so it is not necessary to mention to which OPNFV release 
each project doc is associated. Text like “this is the project documentation 
for the euphrates 5.0 release” should not be needed and should be removed.

Secondly I don’t think every project doc should describe exactly which artifact 
tag to pull (eg. “pull opnfv/functest-core:opnfv-5.0.0”) for the following 
reasons:

  *   There would be a lot of redundant explanation in every project doc (to 
keep in sync)
  *   This would require project doc writers to be aware of the way artifacts 
are released and tagged (and possibly modified)
  *   If there was a maintenance release the doc would have to be edited and 
kept in sync which is a lot of overhead
  *   And last but not least, I believe it is in the interest of projects to 
keep a versioning of their code+doc that is independent of the OPNFV release 
(and this of course means you do not mention OPNFV release versions in your own 
doc)  - one of the many reasons is that a project can ship to an external user 
a project specific version of its code (with a version tag 1.4.2 for example) 
and clearly you do not want the corresponding project documentation to say 
“euphrates 5.0”



I think it would make more sense to have a global OPNFV release document that 
describes the release packaging: what are all the artifacts that make up a 
release, how they are versioned, where to find them: doc, ISO, dockerhub. 
Perhaps there is already such document?
I was looking for such document when I started to look at OPNFV and had trouble 
finding the answer of what is it that OPNFV releases exactly. The doc is easy 
to find, but a list of git repos, docker hub repos, artifact repos is hardly 
sufficient.
From what I can see (and I might be a bit simplistic), there are ISOs that 
correspond to OPNFV installers/deployers that install openstack + features and 
there are docker containers that mostly contain OPNFV tools for testing an 
installation of the same release. So it would kind of make sense to use the 
same version of testing tools to test a given version of openstack+features.


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] [StorPerf] Cancelling weekly meeting

[Beierl, Mark]

Hello,

I won't be able to chair the meeting today, so I am cancelling it, sorry.

Regards,
Mark

Mark Beierl
SW System Sr Principal Engineer
Dell EMC | Office of the CTO
mobile +1 613 314 8106
mark.bei...@dell.com

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

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][euphrates] proposal to eliminate one of the two point releases for Euphrates

[Stuart Mackie]

+1

Stuart
-914 886 2534

From:  on behalf of David McBride 

Date: Wednesday, October 4, 2017 at 2:44 PM
To: TECH-DISCUSS OPNFV 
Cc: opnfv-project-leads , TSC OPNFV 
, Raymond Paik , Tapio 
Tallgren 
Subject: [opnfv-project-leads] [release][euphrates] proposal to eliminate one 
of the two point releases for Euphrates

Team,

Please respond to this mail with (+1, 0, -1) and your thoughts, suggestions, or 
alternatives.

During the TSC call on Tues, Oct 3, the TSC agreed to slip the initial 
Euphrates release (5.0) to October 20.  In addition, I also proposed 
eliminating one of the two point releases (5.1, 5.2) planned for Euphrates.  
The reasoning was as follows:
1.  Moving the 5.0 release to Oct 20 places that release just 3 weeks 
before the planned release of 5.1 (Nov 10).
2.  Slipping 5.1 and 5.2 could have negative consequences for the OPNFV "F" 
release, as happened with Euphrates when we decided to slip Danube 3.0.
Therefore, the proposal is to eliminate the planned release on Nov 10, so that 
there would just be one point release on Dec 15.

The proposal is described in more detail in the slide deck that I presented 
during the TSC 
meeting
 (see link labeled "euphrates contingency.pptx" under the heading "Euphrates 
update").

David

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