Date   

FD.io outage

Vanessa Valderrama
 

Multiple LF projects are experiencing issues reaching Jenkins and Nexus,
. We are aware of the issue and are in contact with our vendor who is
working on the issue. Unfortunately we do not have an ETA at this time.
We apologize for the inconvenience.

Thank you,
Vanessa


Re: FD.io - Gerrit Authentication Errors

Vanessa Valderrama
 

The issue has been resolved. Please let us know if you have any other problems.

Thank you,
Vanessa

On 02/19/2019 09:09 AM, Vanessa Valderrama wrote:
We are aware of users experiencing authentication issues when trying to
log into gerrit.fd.io. We have identified the cause and are working to
resolve it as quickly as possible. I have requested an ETA but have not
been provided one at this time.

Thank you,
Vanessa



FD.io - Gerrit Authentication Errors

Vanessa Valderrama
 

We are aware of users experiencing authentication issues when trying to
log into gerrit.fd.io. We have identified the cause and are working to
resolve it as quickly as possible. I have requested an ETA but have not
been provided one at this time.

Thank you,
Vanessa


Re: FD.io Maintenance: 2019-02-26 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Vanessa Valderrama
 

Maintenance has been rescheduled for 2019-02-26 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Thank you,
Vanessa

On 02/14/2019 09:16 AM, Vanessa Valderrama wrote:
What:

FD.io system maintenance

  • Jenkins resizing, security patch upgrade, and OS updates
  • Nexus upgrade and OS updates
  • Gerrit upgrade and OS updates
  • JIRA upgrade and OS updates
  • Sonar upgrade and OS updates
  • OpenGrok OS updates

When:

2019-02-19 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Impact:

The maintenance will require a reboot of each FD.io system.  The following systems will be impacted:

  • Jenkins production
  • Jenkins sandbox
  • Nexus
  • Gerrit
  • JIRA
  • Sonar
  • OpenGrok

Why:

The Jenkins resizing is to resolve gateway timeout errors causing build failures. The rest of the system maintenance is standard LF maintenance


Published: FD.io CSIT-1901 Open-Source Benchmarking Report

Maciek Konstantynowicz (mkonstan)
 

Hi All,

FD.io CSIT-1901 report has been published on FD.io docs site:

html: https://docs.fd.io/csit/rls1901/report/
pdf: https://docs.fd.io/csit/rls1901/report/_static/archive/csit_rls1810.pdf

Many thanks to All in CSIT, VPP and FD.io community who contributed, worked
very hard to make CSIT-1901 happen!

FD.io VPP points of note in the report:

1. VPP release notes
a. Changes in CSIT-1901: http://bit.ly/2tnfF1p
b. Known issues: http://bit.ly/2I9rWAO

2. VPP performance graphs
a. Throughput 64B frames: http://bit.ly/2EbYxC5
b. Speedup Multi-Core: http://bit.ly/2Bw45FR
c. Latency: http://bit.ly/2SxeDPm

3. VPP performance comparisons
a. VPP-19.01 vs. VPP-18.10: http://bit.ly/2EbrTAs
b. 3-Node Skylake vs. 3-Node Haswell testbeds: http://bit.ly/2tng7g7

4. VPP performance test details
a. Detailed results 64B IMIX 1518B 9kB: http://bit.ly/2V2pEVV
b. Configuration: http://bit.ly/2EbyACE
c. Run-time telemetry: http://bit.ly/2tkqG3L

DPDK Testpmd and L3fwd performance sections follow similar structure.

1. DPDK release notes:
a. Changes in CSIT-1901: http://bit.ly/2SDRvyL
b. Known issues: http://bit.ly/2DCCT8A

2. DPDK performance graphs for Testpmd and L3fwd demonstrator apps
a. Throughput 64B frames: http://bit.ly/2BBzrLj
b. Latency: http://bit.ly/2IfiUCu

Functional tests, including VPP_Device (functional device tests),
VPP_VIRL, HoneyComb and DMM are all included in the report.

Welcome all comments, best by email to csit-dev@lists.fd.io.

Cheers,
-Maciek
On behalf of FD.io CSIT Open-Source Benchmarking Project.


FD.io Maintenance: 2019-02-19 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Vanessa Valderrama
 

What:

FD.io system maintenance

  • Jenkins resizing, security patch upgrade, and OS updates
  • Nexus upgrade and OS updates
  • Gerrit upgrade and OS updates
  • JIRA upgrade and OS updates
  • Sonar upgrade and OS updates
  • OpenGrok OS updates

When:

2019-02-19 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Impact:

The maintenance will require a reboot of each FD.io system.  The following systems will be impacted:

  • Jenkins production
  • Jenkins sandbox
  • Nexus
  • Gerrit
  • JIRA
  • Sonar
  • OpenGrok

Why:

The Jenkins resizing is to resolve gateway timeout errors causing build failures. The rest of the system maintenance is standard LF maintenance


FD.io Maintenance: 2019-02-19 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Vanessa Valderrama
 

Please let us know if this maintenance causing any conflict for your project

What:

FD.io system maintenance

  • Jenkins resizing, security patch upgrade, and OS updates
  • Nexus upgrade and OS updates
  • Gerrit upgrade and OS updates
  • JIRA upgrade and OS updates
  • Sonar upgrade and OS updates
  • OpenGrok OS updates

When:

2019-02-19 @ 2000 UTC (12:00pm PST) - 0000 UTC (4:00pm PST)

Impact:

The maintenance will require a reboot of each FD.io system.  The following systems will be impacted:

  • Jenkins production
  • Jenkins sandbox
  • Nexus
  • Gerrit
  • JIRA
  • Sonar
  • OpenGrok

Why:

The Jenkins resizing is to resolve gateway timeout errors causing build failures. The rest of the system maintenance is standard LF maintenance


Re: [tsc] FD.io Emergency Jenkins Maintenance

Dave Barach
 

Today is the fd.io vpp project 19.01 final release date. This is a really bad time for infrastructure issues. Please plan on turning up at tomorrow's TSC meeting with a detailed explanation of what went wrong.

D.

-----Original Message-----
From: tsc@lists.fd.io <tsc@lists.fd.io> On Behalf Of Vanessa Valderrama
Sent: Wednesday, January 30, 2019 2:34 PM
To: discuss@lists.fd.io; infra-steering@lists.fd.io; tsc@lists.fd.io; csit-dev@lists.fd.io; vpp-dev@lists.fd.io; hc2vpp@lists.fd.io; Anton Baranov <abaranov@linuxfoundation.org>; Ed Kern <ejkern@mac.com>
Subject: [tsc] FD.io Emergency Jenkins Maintenance

We have placed Jenkins into shutdown mode. It will require a restart to resolve slowness. We'll do the restart at the top of the hour.  Please let us know as soon as possible if there are any builds that cannot be terminated if not complete. We apologize for the inconvenience and hope to have this issue resolved as soon as possible.

Thank you,
Vanessa


Re: FD.io Emergency Jenkins Maintenance

Vanessa Valderrama
 

Jenkins restart is complete.  Please open an RT ticket if you experience
any additional issues.

Thank you,

Vanessa

On 01/30/2019 01:34 PM, Vanessa Valderrama wrote:
We have placed Jenkins into shutdown mode. It will require a restart to
resolve slowness. We'll do the restart at the top of the hour.  Please
let us know as soon as possible if there are any builds that cannot be
terminated if not complete. We apologize for the inconvenience and hope
to have this issue resolved as soon as possible.

Thank you,
Vanessa



FD.io Emergency Jenkins Maintenance

Vanessa Valderrama
 

We have placed Jenkins into shutdown mode. It will require a restart to
resolve slowness. We'll do the restart at the top of the hour.  Please
let us know as soon as possible if there are any builds that cannot be
terminated if not complete. We apologize for the inconvenience and hope
to have this issue resolved as soon as possible.

Thank you,
Vanessa


Re: FD.io Maintenance: 2018-01-29 @ 2100 UTC (1:00pm PST)

Vanessa Valderrama
 

We weren't able to successfully resize Jenkins. We've brought the system back up.  Builds are running.  We'll reschedule maintenance once we've figured out the issue.

Thank you for your patience,

Vanessa


On 01/29/2019 04:19 PM, Vanessa Valderrama wrote:

We're experiencing issues resizing Jenkins. We apologize for the delay and will send an update as soon as possible.

Thank you,
Vanessa

On 01/29/2019 02:03 PM, Vanessa Valderrama wrote:

Putting Jenkins in shutdown mode for maintenance.


On 01/24/2019 11:35 AM, Vanessa Valderrama wrote:

What:

Upgrade Jenkins and Nexus systems

When:

2018-01-29 @ 2100 UTC (1:00pm PST)

Impact:

The maintenance will require a reboot of Jenkins and Nexus. The expected down time is 1 hour

Why:

This upgrade is to resolve Gateway timeout errors causing build failures




Re: FD.io Maintenance: 2018-01-29 @ 2100 UTC (1:00pm PST)

Vanessa Valderrama
 

We're experiencing issues resizing Jenkins. We apologize for the delay and will send an update as soon as possible.

Thank you,
Vanessa

On 01/29/2019 02:03 PM, Vanessa Valderrama wrote:

Putting Jenkins in shutdown mode for maintenance.


On 01/24/2019 11:35 AM, Vanessa Valderrama wrote:

What:

Upgrade Jenkins and Nexus systems

When:

2018-01-29 @ 2100 UTC (1:00pm PST)

Impact:

The maintenance will require a reboot of Jenkins and Nexus. The expected down time is 1 hour

Why:

This upgrade is to resolve Gateway timeout errors causing build failures



Re: FD.io Maintenance: 2018-01-29 @ 2100 UTC (1:00pm PST)

Vanessa Valderrama
 

Putting Jenkins in shutdown mode for maintenance.


On 01/24/2019 11:35 AM, Vanessa Valderrama wrote:

What:

Upgrade Jenkins and Nexus systems

When:

2018-01-29 @ 2100 UTC (1:00pm PST)

Impact:

The maintenance will require a reboot of Jenkins and Nexus. The expected down time is 1 hour

Why:

This upgrade is to resolve Gateway timeout errors causing build failures


Re: FD.io Maintenance: 2018-01-29 @ 2100 UTC (1:00pm PST)

Vanessa Valderrama
 

Reminder we'll be performing Jenkins and Nexus maintenance tomorrow.


On 01/24/2019 11:35 AM, Vanessa Valderrama wrote:

What:

Upgrade Jenkins and Nexus systems

When:

2018-01-29 @ 2100 UTC (1:00pm PST)

Impact:

The maintenance will require a reboot of Jenkins and Nexus. The expected down time is 1 hour

Why:

This upgrade is to resolve Gateway timeout errors causing build failures


FD.io Maintenance: 2018-01-29 @ 2100 UTC (1:00pm PST)

Vanessa Valderrama
 

What:

Upgrade Jenkins and Nexus systems

When:

2018-01-29 @ 2100 UTC (1:00pm PST)

Impact:

The maintenance will require a reboot of Jenkins and Nexus. The expected down time is 1 hour

Why:

This upgrade is to resolve Gateway timeout errors causing build failures


FD.io - Scheduled maintenance packagecloud.io - Jan 18, 2019

Vanessa Valderrama
 

Notification of packagecloud maintenance on January 18th.

Thank you,

Vanessa



-------- Forwarded Message --------
Subject: [releng] [collab-it] [packagecloud] Scheduled maintenance Jan 18, 2019
Date: Fri, 04 Jan 2019 17:18:48 +0000
From: packagecloud <app@...>
Reply-To: support@...
To: collab-it+fdio@...


Hi,

packagecloud.io has scheduled a maintenance window on January 18, 2019, from 12 pm to 3 pm Pacific Standard Time.

We wanted to send you an email to let you know that during this time the service will be unavailable as we perform a large infrastructure upgrade.

Please check our blog post here: https://blog.packagecloud.io/eng/2019/01/04/scheduled-maintenance/ for more information on this upgrade.

We'll be posting updates to Twitter and our status page (links at the bottom of this email) before, during, and at the conclusion of the maintenance window.

Thanks,

The packagecloud crew
---
Email us any time! support@...
Follow us on twitter! https://twitter.com/packagecloudio
Join our slack! https://bit.ly/packagecloud-users
Subscribe to our status page! http://www.packagecloudstatus.io/
Privacy Policy: https://packagecloud.io/legal/privacy


Re: VPP graph configuration

Raj
 

Thanks!

I will read the docs and get back if I have any questions.


Raj



Raj

On Mon, Dec 17, 2018 at 12:32 PM Jim Thompson <jim@netgate.com> wrote:



On Dec 16, 2018, at 11:50 PM, Raj <rajlistuser@gmail.com> wrote:

Hello all,

I am a newbie to VPP and trying to understand how it works. I am going
through all the documentation and videos of Paris training program. So
please be gentle :)

I understand that VPP is internally organized as a graph of nodes,
with each node performing a specific function and the passing [a bunch
of?] packets to the next node.

What I could not figure out is the exact graph layout. ie which nodes
is connected to which other nodes and on what condition an input
packet is transmitted over to one of the different output links by a
node.

How is the node graph set up initially?


https://wiki.fd.io/view/VPP/Software_Architecture#Node_Graph_Initialization

Can it be changed dynamically, ie remove some nodes or add some nodes at another location? (not sure
if that makes any sense, though)


https://wiki.fd.io/view/VPP/Modifying_The_Packet_Processing_Directed_Graph (tl;dr: you can add, but not remove nodes)

Can I export the graph to graphviz for viewing?


“show vlib graph” at the CLI.

https://lists.fd.io/g/vpp-dev/message/7159 for graphviz. I don’t know if it still works.

Jim


Re: VPP graph configuration

Jim Thompson
 



On Dec 16, 2018, at 11:50 PM, Raj <rajlistuser@...> wrote:

Hello all,

I am a newbie to VPP and trying to understand how it works. I am going
through all the documentation and videos of Paris training program. So
please be gentle :)

I understand that VPP is internally organized as a graph of nodes,
with each node performing a specific function and the passing [a bunch
of?] packets to the next node.

What I could not figure out is the exact graph layout. ie which nodes
is connected to which other nodes and on what condition an input
packet is transmitted over to one of the different output links by a
node.

How is the node graph set up initially?

https://wiki.fd.io/view/VPP/Software_Architecture#Node_Graph_Initialization

Can it be changed dynamically, ie remove some nodes or add some nodes at another location? (not sure
if that makes any sense, though)

https://wiki.fd.io/view/VPP/Modifying_The_Packet_Processing_Directed_Graph (tl;dr: you can add, but not remove nodes)

Can I export the graph to graphviz for viewing?

“show vlib graph” at the CLI.

https://lists.fd.io/g/vpp-dev/message/7159 for graphviz. I don’t know if it still works.

Jim



VPP graph configuration

Raj
 

Hello all,

I am a newbie to VPP and trying to understand how it works. I am going
through all the documentation and videos of Paris training program. So
please be gentle :)

I understand that VPP is internally organized as a graph of nodes,
with each node performing a specific function and the passing [a bunch
of?] packets to the next node.

What I could not figure out is the exact graph layout. ie which nodes
is connected to which other nodes and on what condition an input
packet is transmitted over to one of the different output links by a
node.

How is the node graph set up initially? Can it be changed dynamically,
ie remove some nodes or add some nodes at another location? (not sure
if that makes any sense, though)

Can I export the graph to graphviz for viewing?

My apologies if this is not the appropriate list for this question.

Thanks and Regards,

Raj


LF IT Release Engineering team Holiday Schedule

Vanessa Valderrama
 

The Linux Foundation will be reducing daily operations from December 17, 2018 to January 2, 2019.  During this time the LF IT Release Engineering team will have limited support available and projects should plan accordingly.

We recommend that major releases or other work, if they have not already been planned and the responsible Release Engineer(s) made aware, be postponed until after Jan. 2.

Please note that CI change code review will not occur with LF Release Engineering staff during this window, unless it is related to an environment stopping issue.

If you have any issues please send request to helpdesk@...

161 - 180 of 756