> 1. Keep the status quo.
> That means using VAT for some operations (e.g. adding multiple routes [5]),
> and creating "exec scripts" [6] for operations without VAT one-liner.
> Pros: No work needed, good speed, old VPP versions are supported.
> Cons: Relying on VAT functionality (outside API
Following up on Peter's comments in the changeset,
Have you seen [0]? It separates out the transports, so that you can
implement/subclass your own without poking in values from your executor.
Poking in the values is an ingenious way to go about solving the problem,
but it is going to make the
Vexxhost has restored the service.
Please recheck or rebase your gerrit changes as necessary.
Thank you for your patience.
-daw-
On 2/3/2021 2:02 PM, Dave Wallace via lists.fd.io wrote:
Update from Vexxhost:
- %< -
We were doing some prep work for the DC migration that seems to have
Update from Vexxhost:
- %< -
We were doing some prep work for the DC migration that seems to have
affected it, we're investigating this right now.
Regards,
Mohammed Naser
- %< -
Thanks,
-daw-
On 2/3/2021 12:52 PM, Dave Wallace via lists.fd.io wrote:
Folks,
We are currently
Folks,
We are currently experiencing a communications outage between the
Vexxhost yul1 & yul2 data centers which host the FD.io CI & CSIT
hardware. Peter Mikus has opened a ticket with Vexxhost and we will be
monitoring the situation.
This outage is causing some CI job failures.
I will
Most of the current rules have been there for a couple of years, so
based on the number of Jenkins/restarts over that period of time I would
think that they are persistent.
I haven't tested these rules on the sandbox, so I'm not sure if they
work there. I chose instead to create [2] for
> The rules are managed via [1].
Does that mean the rules are guaranteed to survive
any sudden Jenkins upgrade (needed for security reasons)?
I will feel safer if we had a copy of the database in ci-management.
That way, if I contribute a new rule,
you can manually apply it when merging the
Hi Neale,
Looking at the show ip arp we see that the arp entries still remain the
same even after the link is down.
show ip arp
Time IP4 Flags Ethernet Interface
1.995410.0.0.14 Dde:ad:de:ad:00:04 GigabitEthernet0/3/0
1.9633
Vratko,
The rules are managed via [1]. Vanessa gave me permission to
create/edit these rules which appear to be applied universally to all
jenkins.fd.io projects. Let me know if there are any rules you would
like me to add.
I agree that JCASC would be the ideal means of managing the
Ben,
In theory, there are statistics captured, but I have not investigated
how to utilize them.
Generally speaking, I'd prefer not to overload Jenkins
managing/displaying stats as a few of the plugins that we recently
removed were graph intensive and complete memory/cpu hogs. I'd prefer
> Hello people interested in PAPI (VPP's Python API client library).
Hello again.
This is an update e-mail, adding some information,
while still asking basically the same questions.
Since my first e-mail, there was some private communication,
mostly related to reasons the vanilla performance is
Hi Rupesh,
Dropping those ARP responses is a clue that you’re not doing something right
I would expect the ARP entry, adj and adj-source on the fib entry to be removed
(in that order) when the link goes down. ‘sh ip eighbours’ please.
Hi Neale,
Thanks for your reply.
I am adding a default route via 10.0.0.15 dev Ge0/4/0, a subnet route
10.0.0.0/24 via 10.0.0.15 dev Ge0/4/0 and a host route to the 10.0.0.15/32
on dev Ge0/4/0. No explicit arp entry is added. Without the specific
10.0.0.15/32 on dev Ge0/4/0 link the arp ipv4
Nice.
> new rules to the VPP Failure Cause Management database [0]
How do we manage the rules?
I think the database is different from usual plugin configuration,
so "Jenkins configuration as code" plugin will not help directly [5].
But I think we can manage the exported database manually in
Hi Rupesh,
10.0.0.15 remains unresolved after link down because there remains an
adjacency/ARP-entry for it on Ge0/4/0 – did you add a static one? It is
unresolved because it fails the adjacency source refinement criteria. Packets
to 10.0.0.15 are forwarded using the default route. This is
Very nice!
Do you also get statistics per failure cause?
Best
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of Dave Wallace
> Sent: mercredi 3 février 2021 02:28
> To: vpp-dev
> Subject: [vpp-dev] Jenkins/Gerrit Failure Cause Notifications
>
> Folks,
>
> Per a
16 matches
Mail list logo
