[opnfv-tech-discuss] Canceled: Pinpoint weekly meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Israel Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0300 TZOFFSETTO:+0200 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT

[opnfv-tech-discuss] [fuel] Fuel@OPNFV colorado.1.0 release artifacts and meta-data

Fuel@OPNFV is now ready for the OPNFV Colorado 1.0 release; artifacts and release info can be found below: Release: Colorado 1.0 Project: Fuel@OPNFV Git-tag: colorado.1.0 GIT Repository: https://git.opnfv.org/cgit/fuel/tree/?h=colorado.1.0 Commit-Id:/SHA-1:

Re: [opnfv-tech-discuss] Results of Security Threat Analysis for Colorado.

Well done, Thanks Luke :) On 2016-09-21 16:49, Luke Hinds wrote: > Hello All, > > An update on the results of the Security Threat Analysis for Colorado. > > All projects were given a cursory scan using our security lint tool > 'anteater', and I then took an in-depth manual review and released >

Re: [opnfv-tech-discuss] Labelling your Colorado repo for the release.

That should be fine Jonas. Aric will run through and make sure everything is in order tomorrow morning US time, you should be done before that. / Chris From: Jonas Bjurel Date: Wednesday 21 September 2016 at 20:39 To: Christopher Price

Re: [opnfv-tech-discuss] Labelling your Colorado repo for the release.

My plan was to tag it 4.30 PM CET tomorrow such that we could have a final committer review in the fuel project meeting, Chris would that be to late? BR/Jonas From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Christopher Price

Re: [opnfv-tech-discuss] [opnfv-project-leads] Labelling your Colorado repo for the release.

I just got that final doc patch merged. The SFC project is now labeled for Colorado 1.0: $ git tag -am "colorado.1.0" colorado.1.0 $ git push origin colorado.1.0 Counting objects: 1, done. Writing objects: 100% (1/1), 169 bytes | 0 bytes/s, done. Total 1 (delta 0), reused 0

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule

I really think this is unnecessary governance from the release projects, if a project secure resources them self and push relevant patches to releng to enable branch verification I have very hard time to see that anyone else should bother. I also don’t see the point with the resources, I do

Re: [opnfv-tech-discuss] [opnfv-project-leads] Labelling your Colorado repo for the release.

Chris, I understood that we had until Thursday to do the labeling. I have one minor release notes and scenario doc patch pending that should be merged shortly. Once its merged, I'll do the label. Regards, Brady On 21/09/16 19:25, David McBride wrote: Note that Aric just added some

Re: [opnfv-tech-discuss] [opnfv-project-leads] Labelling your Colorado repo for the release.

Note that Aric just added some troubleshooting instructions at the bottom of the page that Chris just linked. Please follow those instructions if you are having difficulty. David On Wed, Sep 21, 2016 at 10:23 AM, Christopher Price < christopher.pr...@ericsson.com> wrote: > Hi Project leads, >

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule

Jonas, There may not be sufficient resources available prior to the opening of the window. So, this is a signal to the infra/CI team to be prepared to support CI on both master and stable branch. However, perhaps we could consider expanding the window from 1 week to, say 2 weeks. David On

[opnfv-tech-discuss] Labelling your Colorado repo for the release.

Hi Project leads, If you have not already done it, now is the right time to make sure you have the Colorado 1.0 label correctly applied to your repo. Please follow the instructions here: https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Colorado+Release / Chris

Re: [opnfv-tech-discuss] OPNFV Jenkins Restart

Hi, Jenkins has been restarted and some jobs were aborted during the process. We will keep an eye on it to make sure it stays alive until the release is done and increase the memory afterwards. /Fatih From: on behalf of Fatih Degirmenci

[opnfv-tech-discuss] Technical Community Discussion Canceled Tomorrow (9/22)

Hello community, There is no new project proposal in the backlog. And there is not urgent issue to discuss either. So I propose to cancel our technical discussion tomorrow (9/22) so that everyone can focus on the last sprint of Colorado release, which is targeted for tomorrow 9/22. We

Re: [opnfv-tech-discuss] [opnfv-tsc] Results of Security Threat Analysis for Colorado.

Thanks for all your hard work, Luke! On Wed, Sep 21, 2016 at 7:49 AM, Luke Hinds wrote: > Hello All, > > An update on the results of the Security Threat Analysis for Colorado. > > All projects were given a cursory scan using our security lint tool > 'anteater', and I then

[opnfv-tech-discuss] Results of Security Threat Analysis for Colorado.

Hello All, An update on the results of the Security Threat Analysis for Colorado. All projects were given a cursory scan using our security lint tool 'anteater', and I then took an in-depth manual review and released individual project reports to the PTL's, with each containing recommended code

Re: [opnfv-tech-discuss] [SFC] Agenda for today's meeting, Sep 21

Here are the minutes of meeting from today's meeting: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2016/opnfv-sfc.2016-09-21-14.02.html Regards, Brady On 21/09/16 12:39, Brady Allen Johnson wrote: Hello, Lets cover the following in today's weekly meeting: * Scope for

[opnfv-tech-discuss] Qtip Contribution

Hi I had want to contribute to the Qtip Project.[0] My Linux Foundation account is 'linux_geek'. Besides code patches, would I also be able to get reviews for changes in documentations as well ? [0]. https://gerrit.opnfv.org/gerrit/#/q/Qtip Thank you,

[opnfv-tech-discuss] [tech-discuss][fuel] master is open for D-release

The master branch is now open for D-release work. Fixes relevant to both master and stable/colorado should still be cherry-picked, while fixes to stable/colorado not relevant to master are pushed directly to stable/colorado. BR/Jonas ___

[opnfv-tech-discuss] [Security Advisory] Private key `vtep-privkey.pem` resides in ansible files directory for open-contrail role in Compass4NFV.

Private key `vtep-privkey.pem` resides in ansible files directory for open-contrail role in Compass4NFV. --- Date: Sep 21, 2016 CVE #: Pending ### Affects ### Brahmaputra release. ### Description ### A private key ‘vtep-privkey.pem’ was discovered in the ansible role for open-contrail in

[opnfv-tech-discuss] [SFC] Agenda for today's meeting, Sep 21

Hello, Lets cover the following in today's weekly meeting: * Scope for Colorado 2.0 o what's the status of the Tacker plug-in for FUEL? Should we spend time registering the service in the proxy or better wait for the plug-in? * Help debugging Netvirt issue o OPNFV SFC

[opnfv-tech-discuss] [bottlenecks] bottlenecks weekly meeting 09-22 (1:00-2:00 UTC, Thursday, 9:00-10:00 Beijing Time, Thursday, PDT 18:00-19:00 Wednesday )

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:W. Australia Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800

[opnfv-tech-discuss] [ovsnfv] [vsperf] Analysis of Microburst on VSwitch

Hi Chunghan, Thanks for your presentation on Monday (https://wiki.opnfv.org/download/attachments/5046510/0919_ovsnfv.pdf?version=1=1474280389000=v2 ). It was very interesting to see where packets are lost when OVS is overloaded. There is a vSwitch testing project in OPNFV - vsperf

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Hello team, Last year, use case 4 was discussed, some network related requirements were identified: https://etherpad.opnfv.org/p/multisite_centralized_servic * global view for tenant level IP address / mac address space

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

After reading the whole message, I could not agree more on the conclusion, IIUC, we should probably raise a deducted alarm in inspector instead of requesting the controller to reset server state. On Wed, Sep 21, 2016 at 2:51 PM Juvonen, Tomi (Nokia - FI/Espoo) < tomi.juvo...@nokia.com> wrote: >

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

Hi, I had a lively discussion yesterday with OpenStack Nova cores about the reset server state. At first how to have that by one API call for all VMs on a host (hypervisor) as discussed in DOCTOR-78. But then it came to a question why we actually want the reset server state in the first place.

[opnfv-tech-discuss] [SFC] Nominating Manuel Buil as committer

Hello, I would like to nominate Manuel Buil as committer for the OPNFV SFC project. Since OPNFV isnt really about commits, I wont bother listing his commits, although he has done alot of them for SFC in Fuel, Yardstick, ODL SFC, and Functest. Manuel has been very active this release, and