FD.io - Decommission OpenGrok Instance
Vanessa Valderrama
What: LF will decomission the FD.io OpenGrok instance When: 2020-07-22 at 1700 UTC Impact: opengrok.fd.io will no longer be accessible Why: After reviewing our inventory it doesn't appear
OpenGrok is being used by the community. We'll be shutting the
service down as a cost saving effort. Vanessa
|
|||||||||||
|
|||||||||||
FD.io - Decommission SonarQube Instance
Vanessa Valderrama
What: LF will decomission the FD.io SonarQue instance When: 2020-07-22 at 1700 UTC Impact: sonar.fd.io and code quality reports and history will no longer be accessible Why: LF has migrated to SonarCloud. All FD.io project
yaml files have been configured for SonarCloud jobs. Vanessa
|
|||||||||||
|
|||||||||||
OpenGrok Question
Vanessa Valderrama
LF is doing reviewing our INFRA inventory. We'd like to know if the
community actively uses OpenGrok? Thank you, Vanessa
|
|||||||||||
|
|||||||||||
Re: sw_if_index in vent_buffer giving wrong IP address with ip_interface_address_get_address
Dave Barach
If the packet was received on HundredGigabitEthernet12/0/0, you should get 192.168.198.2. If it was received on memif0/0 you should get 192.168.1.3. "trace add dpdk-input" [or send pkts, then "show trace". If that produces nothing, s/dpdk-input/memif-input/
or whatever the memif input node is called.
Use "show int addr" / "show int" to determine the sw_if_index to name mapping, and to display the interface ip addresses.
From: discuss@... <discuss@...> on behalf of ravi.jupvpp@... <ravi.jupvpp@...>
Sent: Thursday, June 18, 2020 3:54 PM To: discuss@... <discuss@...> Subject: [discuss] sw_if_index in vent_buffer giving wrong IP address with ip_interface_address_get_address [Edited Message Follows] Hi Team,
I am writing a plugin and my plugin is attached to device_input, so that I can receive all the traffic.
In my plugin, I am checking the headers and deciding to forward to my application or to the Native VPP. This is working fine, However ICMP case I have one requirement to check is it destined to Interface I attached my plugin or some other IP, So to check that
I am using following APIs,
I am receiving packets and doing following things to get the IP address,
sw_if_index0 = vnet_buffer(b0)->sw_if_index[
ip4_main_t *im = &ip4_main;
ip_lookup_main_t *lm = &im->lookup_main; ip_interface_address_t *if_add = pool_elt_at_index (lm->if_address_pool, if_index); ip4_address_t *if_ip = ip_interface_address_get_
I am getting IP Address but the IP Address I am getting is something different,
For Example:
In VPPCTL If I create the interfaces in the following order:
set interface ip add HundredGigabitEthernet12/0/0 192.168.198.2/24
set interface state HundredGigabitEthernet12/0/0 up set interface ip addr HundredGigabitEthernet12/0/0 2001:5b0:ffff:7cf0::98fc/64 create interface memif id 0 socket-id 0 master set interface state memif0/0 up set interface ip add memif0/0 192.168.1.3/24 set interface ip addr memif0/0 2001:5b0:ffff:7cf1::98fc/64
I am getting IP Address as 192.168.1.3.
If I am creating interfaces in the following order:
create interface memif id 0 socket-id 0 master
set interface state memif0/0 up set interface ip add memif0/0 192.168.1.3/24 set interface ip addr memif0/0 2001:5b0:ffff:7cf1::98fc/64
set interface ip add HundredGigabitEthernet12/0/0 192.168.198.2/24
set interface state HundredGigabitEthernet12/0/0 upset interface ip addr HundredGigabitEthernet12/0/0 2001:5b0:ffff:7cf0::98fc/64 I am getting IP Address as 192.168.198.2.
But in both cases the sw_if_index is same and my plugin attached to the HundredGigabitEthernet12/0/0 only. I am expecting IP address of this but its getting the order I created. So My questions are
1> How to get IP address of a interface from sw_if_index0?
2> Can you please let me know if you find any issue in my code to get the IP Address?
3> Is there any better method to get IP address from the buffer using any other parameter? I needed IP address of interface the packet received.
Regards,
Ravi.
|
|||||||||||
|
|||||||||||
sw_if_index in vent_buffer giving wrong IP address with ip_interface_address_get_address
Hi Team,
I am writing a plugin and my plugin is attached to device_input, so that I can receive all the traffic.
In my plugin, I am checking the headers and deciding to forward to my application or to the Native VPP. This is working fine, However ICMP case I have one requirement to check is it destined to Interface I attached my plugin or some other IP, So to check that I am using following APIs,
I am receiving packets and doing following things to get the IP address,
sw_if_index0 = vnet_buffer(b0)->sw_if_index[
ip4_main_t *im = &ip4_main;
ip_lookup_main_t *lm = &im->lookup_main; ip_interface_address_t *if_add = pool_elt_at_index (lm->if_address_pool, if_index); ip4_address_t *if_ip = ip_interface_address_get_ I am getting IP Address but the IP Address I am getting is something different,
For Example:
In VPPCTL If I create the interfaces in the following order:
set interface ip add HundredGigabitEthernet12/0/0 192.168.198.2/24
set interface state HundredGigabitEthernet12/0/0 up set interface ip addr HundredGigabitEthernet12/0/0 2001:5b0:ffff:7cf0::98fc/64 create interface memif id 0 socket-id 0 master set interface state memif0/0 up set interface ip add memif0/0 192.168.1.3/24 set interface ip addr memif0/0 2001:5b0:ffff:7cf1::98fc/64 I am getting IP Address as 192.168.1.3.
If I am creating interfaces in the following order:
create interface memif id 0 socket-id 0 master
set interface state memif0/0 up set interface ip add memif0/0 192.168.1.3/24 set interface ip addr memif0/0 2001:5b0:ffff:7cf1::98fc/64 set interface ip add HundredGigabitEthernet12/0/0 192.168.198.2/24
set interface state HundredGigabitEthernet12/0/0 upset interface ip addr HundredGigabitEthernet12/0/0 2001:5b0:ffff:7cf0::98fc/64 I am getting IP Address as 192.168.198.2.
But in both cases the sw_if_index is same and my plugin attached to the HundredGigabitEthernet12/0/0 only. I am expecting IP address of this but its getting the order I created. So My questions are
1> How to get IP address of a interface from sw_if_index0?
2> Can you please let me know if you find any issue in my code to get the IP Address?
3> Is there any better method to get IP address from the buffer using any other parameter? I needed IP address of interface the packet received.
Regards,
Ravi.
|
|||||||||||
|
|||||||||||
Virtual LFN Developer & Testing Forum (June 22 - 25)
Trishan de Lanerolle
Greetings LFN Technical Community, We wanted to make sure that you had the new format and dates for the upcoming LFN Developer & Testing Forum on your radar. The event was originally planned for the first week of June but has now been scheduled for June 22 - 25. Like the LFN Technical Meetings in April, this will be a virtual event. As the principal technical event for the LF Networking projects, this bi-annual gathering provides the opportunity for each participating community to advance their project roadmaps and explore cross-community collaboration and integration points. The CNTT/OPNFV, ONAP, OpenDaylight, and Tungsten Fabric communities have confirmed their participation. Registration is required and we encourage you to register early. Please learn more and register at the links below and let us know directly if you have any questions or feedback. Thank you! Event Webpage & Registration: https://events.linuxfoundation.org/lfn-dev-test-forum/ Wiki Planning Page: https://wiki.lfnetworking.org/x/6wUQAg
|
|||||||||||
|
|||||||||||
Re: Production Jenkins Incident
Vanessa Valderrama
The upgrade is complete and Jenkins has been restarted. We will continue
toggle quoted messageShow quoted text
to monitor for additional issues. If you experience any issues, please open a ticket at support.linuxfoundation.org. Thank you, Vanessa
On 5/13/20 11:14 AM, Vanessa Valderrama wrote:
Jenkins is currently in shutdown mode. We need to do an emergency JDK
|
|||||||||||
|
|||||||||||
Re: Production Jenkins Incident
Vanessa Valderrama
Jenkins is currently in shutdown mode. We need to do an emergency JDK
toggle quoted messageShow quoted text
upgrade to OpenJDK 8u252 (1.8.0_252-b09). We believe the upgrade on April 28th introduced a new defect that is resolved in the latest version JDK-8219597: (bf) Heap buffer state changes could provoke unexpected exceptions Release Notes - https://adoptopenjdk.net/release_notes.html#jdk8u252 Thank you, Vanessa
On 5/13/20 10:38 AM, Vanessa Valderrama wrote:
We are experiencing intermittent issues with jenkins.fd.io. We are
|
|||||||||||
|
|||||||||||
Production Jenkins Incident
Vanessa Valderrama
We are experiencing intermittent issues with jenkins.fd.io. We are
working on resolving the issues as quickly as possible. Thank you, Vanessa
|
|||||||||||
|
|||||||||||
Re: FD.io Maintenance: Tuesday April 28, 2020 1800 UTC to 2200 UTC
Vanessa Valderrama
Maintenance is complete. If you experience any issues, please submit a ticket at support.linuxfoundation.org Thank you,Anton & Vanessa
On 4/28/20 1:06 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Re: FD.io Maintenance: Tuesday April 28, 2020 1800 UTC to 2200 UTC
Vanessa Valderrama
Starting maintenance
On 4/28/20 12:02 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Re: FD.io Maintenance: Tuesday April 28, 2020 1800 UTC to 2200 UTC
Vanessa Valderrama
Jenkins has been placed into shutdown mode in preparation for maintenance. Please contact me via Slack or IRC if jobs cannot be terminated at 1800 UTC. Thank you,Vanessa
On 4/16/20 4:12 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Re: FD.io Maintenance: Tuesday April 28, 2020 1800 UTC to 2200 UTC
Vanessa Valderrama
Maintenance reminder
On 4/16/20 4:12 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
FD.io Maintenance: Tuesday April 28, 2020 1800 UTC to 2200 UTC
Vanessa Valderrama
When: Tuesday
April 28, 2020 1800 UTC to 2200 UTC
What: Linux
foundation upgrades, OS updates, and security patches
Gerrit will be
unavailable for all or part of the window as we do the
following:
The standard upgrades
and maintenance will require a reboot of each FD.io system.
Jenkins will be placed in shutdown mode at 1700 UTC. Running
jobs will be aborted at 1800 UTC, please let us know if that
will cause a problem for your project.
The following systems
will be unavailable during the maintenance window:
|
|||||||||||
|
|||||||||||
Re: [csit-dev] FDIO Maintenance - 2020-02-20 1900 UTC to 2400 UTC
Nana Adjei <nadjei@...>
Hello, Sorry for the mix up . I believe that was for slot 9. I will proceed to site for the replacement. Best Regards,
On Thu, Feb 20, 2020 at 1:04 PM Vanessa Valderrama <vvalderrama@...> wrote:
|
|||||||||||
|
|||||||||||
Re: FDIO Maintenance - 2020-02-20 1900 UTC to 2400 UTC
Vanessa Valderrama
Maintenance is complete. Jenkins has been taken out of shutdown mode. Jobs are starting up. If you experience any issues, please open a ticket at support.linuxfoundation.org Thank you,Anton & Vanessa
On 2/20/20 1:00 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Re: FDIO Maintenance - 2020-02-20 1900 UTC to 2400 UTC
Vanessa Valderrama
Starting maintenance now.
On 2/20/20 12:04 PM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Re: FDIO Maintenance - 2020-02-20 1900 UTC to 2400 UTC
Vanessa Valderrama
Jenkins is being placed into shutdown mode now. Maintaince will start at 1900 UTC. Please let us know if there are any running jobs that cannot be terminated. Thank you,Vanessa
On 2/20/20 9:47 AM, Vanessa Valderrama
wrote:
|
|||||||||||
|
|||||||||||
Test
Vanessa Valderrama
Testing list
|
|||||||||||
|
|||||||||||
Re: FDIO Maintenance - 2020-02-20 1900 UTC to 2400 UTC
Vanessa Valderrama
Reminder: Jenkins will be placed in shutdown mode at 1800 UTC
On 2/19/20 9:44 AM, Vanessa Valderrama
wrote:
|
|||||||||||
|