Re: [vpp-dev] [dmm-dev] FD.io - Gerrit 2.16 Changes

2019-07-30 Thread Florin Coras 
Apologies, seems today is not my day with links. 

Florin

[1] https://github.com/openstack-infra/git-review/tree/master/git_review 


> On Jul 30, 2019, at 1:51 PM, Florin Coras via Lists.Fd.Io 
>  wrote:
> 
> Pushed send too soon 
> 
> Florin
> 
> [1] /usr/lib/python3/dist-packages/git_review/cmd.py
> 
>> On Jul 30, 2019, at 1:49 PM, Florin Coras via Lists.Fd.Io 
>> > > wrote:
>> 
>> It seems that this [1] supports the new workflows. Just overwriting 
>> /usr/lib/python3/dist-packages/git_review/cmd.py seems to do the trick. 
>> 
>> I’m sure there must be a cleaner way … 
>> 
>> Florin
>> 
>>> On Jul 30, 2019, at 1:20 PM, Vanessa Valderrama 
>>> mailto:vvalderr...@linuxfoundation.org>> 
>>> wrote:
>>> 
>>> Changes that will happen with Gerrit:
>>> 
>>> 1) The 'New UI' for Gerrit will become the default UI
>>> 
>>> 2) The Draft work flow is removed and replaced with 'Work in Progress'
>>> aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
>>> support either of these workflows directly. Utilizing them means either
>>> pushing your changes the manual way for either system or pushing them up
>>> with git-review and then marking the change via the UI into either of
>>> the workflows.
>>> 
>>> 
>>> To push a private change you may do so as follows:
>>> git push origin HEAD:refs/for/master%private
>>> 
>>> To pull it out of private you may do so as follows:
>>> git push origin HEAD:refs/for/master%remove-private
>>> 
>>> To push a WIP you may do so as follows:
>>> git push origin HEAD:refs/for/master%wip
>>> 
>>> To mark it ready for review you may do so as follows:
>>> git push origin HEAD:refs/for/master%ready
>>> 
>>> Once a change is in either private or WIP state it does not switch the
>>> change to a ready state until the current state has been removed.
>>> 
>>> In both cases, the state can be set via the UI by selecting the tripple
>>> dot menu option on the change and selecting the appropriate option.
>>> 
>>> To remove WIP state press the 'START REVIEW' button. To remove the
>>> private state you must do so via the menu.
>>> 
>>> NOTE: We are not moving to Gerrit 3 at this time. That is on the road
>>> map but we need to come to the latest 2.x as we have to do various
>>> migrations that are only available at the 2.16 level before we can move
>>> to Gerrit 3.
>>> 
>>> Thank you,
>>> Vanessa
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> 
>>> View/Reply Online (#61): https://lists.fd.io/g/dmm-dev/message/61 
>>> 
>>> Mute This Topic: https://lists.fd.io/mt/32658314/675152 
>>> 
>>> Group Owner: dmm-dev+ow...@lists.fd.io 
>>> Unsubscribe: https://lists.fd.io/g/dmm-dev/unsub 
>>>   [fcoras.li...@gmail.com 
>>> ]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>> 
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#13624): https://lists.fd.io/g/vpp-dev/message/13624 
>> 
>> Mute This Topic: https://lists.fd.io/mt/32658598/675152 
>> 
>> Group Owner: vpp-dev+ow...@lists.fd.io 
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub 
>>   [fcoras.li...@gmail.com 
>> ]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13625): https://lists.fd.io/g/vpp-dev/message/13625
> Mute This Topic: https://lists.fd.io/mt/32658616/675152
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13626): https://lists.fd.io/g/vpp-dev/message/13626
Mute This Topic: https://lists.fd.io/mt/32658627/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [dmm-dev] FD.io - Gerrit 2.16 Changes

2019-07-30 Thread Florin Coras 
Pushed send too soon 

Florin

[1] /usr/lib/python3/dist-packages/git_review/cmd.py

> On Jul 30, 2019, at 1:49 PM, Florin Coras via Lists.Fd.Io 
>  wrote:
> 
> It seems that this [1] supports the new workflows. Just overwriting 
> /usr/lib/python3/dist-packages/git_review/cmd.py seems to do the trick. 
> 
> I’m sure there must be a cleaner way … 
> 
> Florin
> 
>> On Jul 30, 2019, at 1:20 PM, Vanessa Valderrama 
>> mailto:vvalderr...@linuxfoundation.org>> 
>> wrote:
>> 
>> Changes that will happen with Gerrit:
>> 
>> 1) The 'New UI' for Gerrit will become the default UI
>> 
>> 2) The Draft work flow is removed and replaced with 'Work in Progress'
>> aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
>> support either of these workflows directly. Utilizing them means either
>> pushing your changes the manual way for either system or pushing them up
>> with git-review and then marking the change via the UI into either of
>> the workflows.
>> 
>> 
>> To push a private change you may do so as follows:
>> git push origin HEAD:refs/for/master%private
>> 
>> To pull it out of private you may do so as follows:
>> git push origin HEAD:refs/for/master%remove-private
>> 
>> To push a WIP you may do so as follows:
>> git push origin HEAD:refs/for/master%wip
>> 
>> To mark it ready for review you may do so as follows:
>> git push origin HEAD:refs/for/master%ready
>> 
>> Once a change is in either private or WIP state it does not switch the
>> change to a ready state until the current state has been removed.
>> 
>> In both cases, the state can be set via the UI by selecting the tripple
>> dot menu option on the change and selecting the appropriate option.
>> 
>> To remove WIP state press the 'START REVIEW' button. To remove the
>> private state you must do so via the menu.
>> 
>> NOTE: We are not moving to Gerrit 3 at this time. That is on the road
>> map but we need to come to the latest 2.x as we have to do various
>> migrations that are only available at the 2.16 level before we can move
>> to Gerrit 3.
>> 
>> Thank you,
>> Vanessa
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> 
>> View/Reply Online (#61): https://lists.fd.io/g/dmm-dev/message/61 
>> 
>> Mute This Topic: https://lists.fd.io/mt/32658314/675152 
>> 
>> Group Owner: dmm-dev+ow...@lists.fd.io 
>> Unsubscribe: https://lists.fd.io/g/dmm-dev/unsub 
>>   [fcoras.li...@gmail.com 
>> ]
>> -=-=-=-=-=-=-=-=-=-=-=-
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13624): https://lists.fd.io/g/vpp-dev/message/13624
> Mute This Topic: https://lists.fd.io/mt/32658598/675152
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13625): https://lists.fd.io/g/vpp-dev/message/13625
Mute This Topic: https://lists.fd.io/mt/32658616/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [dmm-dev] FD.io - Gerrit 2.16 Changes

2019-07-30 Thread Florin Coras 
It seems that this [1] supports the new workflows. Just overwriting 
/usr/lib/python3/dist-packages/git_review/cmd.py seems to do the trick. 

I’m sure there must be a cleaner way … 

Florin

> On Jul 30, 2019, at 1:20 PM, Vanessa Valderrama 
>  wrote:
> 
> Changes that will happen with Gerrit:
> 
> 1) The 'New UI' for Gerrit will become the default UI
> 
> 2) The Draft work flow is removed and replaced with 'Work in Progress'
> aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
> support either of these workflows directly. Utilizing them means either
> pushing your changes the manual way for either system or pushing them up
> with git-review and then marking the change via the UI into either of
> the workflows.
> 
> 
> To push a private change you may do so as follows:
> git push origin HEAD:refs/for/master%private
> 
> To pull it out of private you may do so as follows:
> git push origin HEAD:refs/for/master%remove-private
> 
> To push a WIP you may do so as follows:
> git push origin HEAD:refs/for/master%wip
> 
> To mark it ready for review you may do so as follows:
> git push origin HEAD:refs/for/master%ready
> 
> Once a change is in either private or WIP state it does not switch the
> change to a ready state until the current state has been removed.
> 
> In both cases, the state can be set via the UI by selecting the tripple
> dot menu option on the change and selecting the appropriate option.
> 
> To remove WIP state press the 'START REVIEW' button. To remove the
> private state you must do so via the menu.
> 
> NOTE: We are not moving to Gerrit 3 at this time. That is on the road
> map but we need to come to the latest 2.x as we have to do various
> migrations that are only available at the 2.16 level before we can move
> to Gerrit 3.
> 
> Thank you,
> Vanessa
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#61): https://lists.fd.io/g/dmm-dev/message/61
> Mute This Topic: https://lists.fd.io/mt/32658314/675152
> Group Owner: dmm-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/dmm-dev/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13624): https://lists.fd.io/g/vpp-dev/message/13624
Mute This Topic: https://lists.fd.io/mt/32658598/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io - Gerrit 2.16 Changes

2019-07-30 Thread Vanessa Valderrama 
Changes that will happen with Gerrit:

1) The 'New UI' for Gerrit will become the default UI

2) The Draft work flow is removed and replaced with 'Work in Progress'
aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
support either of these workflows directly. Utilizing them means either
pushing your changes the manual way for either system or pushing them up
with git-review and then marking the change via the UI into either of
the workflows.

*To push a private change you may do so as follows:*
git push origin HEAD:refs/for/master%private

*To pull it out of private you may do so as follows:*
git push origin HEAD:refs/for/master%remove-private

*To push a WIP you may do so as follows:*
git push origin HEAD:refs/for/master%wip

*To mark it ready for review you may do so as follows:*
git push origin HEAD:refs/for/master%ready

Once a change is in either private or WIP state it does not switch the
change to a ready state until the current state has been removed.

In both cases, the state can be set via the UI by selecting the tripple
dot menu option on the change and selecting the appropriate option.
*
**To remove WIP state press the 'START REVIEW' button. To remove the**
**private state you must do so via the menu.*

NOTE: We are not moving to Gerrit 3 at this time. That is on the road
map but we need to come to the latest 2.x as we have to do various
migrations that are only available at the 2.16 level before we can move
to Gerrit 3.

Thank you,
Vanessa
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13623): https://lists.fd.io/g/vpp-dev/message/13623
Mute This Topic: https://lists.fd.io/mt/32658320/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

2019-07-30 Thread Vanessa Valderrama 
Apparently there was a change to the Draft work flow in Gerrit 2.16. I
apologize for not providing this information sooner. i missed a team
discussion that addressed this change.

The Draft work flow is removed and replaced with 'Work in Progress'
aka 'WIP' and 'Private' workflows. Unfortunately git-review does not
support either of these workflows directly. Utilizing them means either
pushing your changes the manual way for either system or pushing them up
with git-review and then marking the change via the UI into either of
the workflows.

To push a private change you may do so as follows:

git push origin HEAD:refs/for/master%private

To pull it out of private you may do so as follows:

git push origin HEAD:refs/for/master%remove-private

To push a WIP you may do so as follows:

git push origin HEAD:refs/for/master%wip

To mark it ready for review you may do so as follows:

git push origin HEAD:refs/for/master%ready

Once a change is in either private or WIP state it does not switch the
change to a ready state until the current state has been removed.

In both cases, the state can be set via the UI by selecting the tripple
dot menu option on the change and selecting the appropriate option.

To remove WIP state press the 'START REVIEW' button. To remove the
private state you must do so via the menu.

Thank you,
Vanessa

On 07/30/2019 02:37 PM, Florin Coras wrote:
> I definitely like the new UI. But now I’m getting:
>
> "! [remote rejected]     HEAD -> refs/drafts/master *(draft workflow
> is disabled)*”
>
> Did something change?
>
> Thanks, 
> Florin
>
>> On Jul 30, 2019, at 11:57 AM, Vanessa Valderrama
>> > > wrote:
>>
>> Maintenance is complete. All systems are now available. We'll be
>> doing some additional testing and monitoring throughout the day. If
>> you experience any issues please open a ticket at
>> support.linuxfoundation.org .
>>
>> Thank you,
>> Vanessa
>>
>> On 07/30/2019 12:01 PM, Vanessa Valderrama wrote:
>>>
>>> Starting maintenance
>>>
>>>
>>> On 07/30/2019 11:02 AM, Vanessa Valderrama wrote:

 Jenkins has been placed in shutdown mode for maintenance



 On 07/29/2019 10:29 AM, Vanessa Valderrama wrote:
>
> Maintenance reminder
>
>
> On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:
>>
>> *What:*
>>
>> FD.io  system maintenance
>>
>>   * Jenkins
>>   o OS updates
>>   o Upgrade from 2.164.3 to 2.176.2
>>   + https://jenkins.io/changelog-stable/
>>   o Update plug-ins
>>   o Memory upgrade
>>
>>   * Nexus
>>   o OS updates
>>
>>   * Gerrit
>>   o OS updates
>>   o Upgrade from 2.14.6 to 2.16
>>   + https://www.gerritcodereview.com/2.16.html
>>
>>   * JIRA
>>   o OS updates
>>
>>   * Sonar
>>   o OS updates
>>
>>   * OpenGrok OS updates
>>
>> *When:*
>>
>> 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
>>
>> *Impact:*
>>
>> The maintenance will require a reboot of each FD.io
>>  system. Jenkins will be placed in shutdown mode at
>> 1600 UTC.  Please let us know if there are any jobs that cannot
>> be aborted.  The following systems will be impacted:
>>
>>   * Jenkins production
>>   * Jenkins sandbox
>>   * Nexus
>>   * Gerrit
>>   * JIRA
>>   * Sonar
>>   * OpenGrok
>>
>>
>

>>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#1062): https://lists.fd.io/g/tsc/message/1062
>> Mute This Topic: https://lists.fd.io/mt/32603363/675152
>> Group Owner: tsc+ow...@lists.fd.io 
>> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [fcoras.li...@gmail.com
>> ]
>> -=-=-=-=-=-=-=-=-=-=-=-
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13622): https://lists.fd.io/g/vpp-dev/message/13622
Mute This Topic: https://lists.fd.io/mt/32657900/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

2019-07-30 Thread Florin Coras 
I definitely like the new UI. But now I’m getting:

"! [remote rejected] HEAD -> refs/drafts/master (draft workflow is 
disabled)”

Did something change?

Thanks, 
Florin

> On Jul 30, 2019, at 11:57 AM, Vanessa Valderrama 
>  wrote:
> 
> Maintenance is complete. All systems are now available. We'll be doing some 
> additional testing and monitoring throughout the day. If you experience any 
> issues please open a ticket at support.linuxfoundation.org.
> 
> Thank you,
> Vanessa
> 
> On 07/30/2019 12:01 PM, Vanessa Valderrama wrote:
>> Starting maintenance
>> 
>> 
>> On 07/30/2019 11:02 AM, Vanessa Valderrama wrote:
>>> Jenkins has been placed in shutdown mode for maintenance
>>> 
>>> 
>>> 
>>> 
>>> On 07/29/2019 10:29 AM, Vanessa Valderrama wrote:
 Maintenance reminder
 
 
 On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:
> 
> What:
> 
> FD.io system maintenance
> 
> Jenkins
> OS updates
> Upgrade from 2.164.3 to 2.176.2
> https://jenkins.io/changelog-stable/ 
> 
> Update plug-ins
> Memory upgrade
> Nexus
> OS updates
> Gerrit
> OS updates
> Upgrade from 2.14.6 to 2.16
> https://www.gerritcodereview.com/2.16.html 
> 
> JIRA
> OS updates
> Sonar
> OS updates
> OpenGrok OS updates
> When:
> 
> 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
> 
> Impact:
> 
> The maintenance will require a reboot of each FD.io system. Jenkins will 
> be placed in shutdown mode at 1600 UTC.  Please let us know if there are 
> any jobs that cannot be aborted.  The following systems will be impacted:
> 
> Jenkins production
> Jenkins sandbox
> Nexus
> Gerrit
> JIRA
> Sonar
> OpenGrok
> 
 
>>> 
>> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#1062): https://lists.fd.io/g/tsc/message/1062
> Mute This Topic: https://lists.fd.io/mt/32603363/675152
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13621): https://lists.fd.io/g/vpp-dev/message/13621
Mute This Topic: https://lists.fd.io/mt/32657900/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

2019-07-30 Thread Vanessa Valderrama 
Maintenance is complete. All systems are now available. We'll be doing
some additional testing and monitoring throughout the day. If you
experience any issues please open a ticket at support.linuxfoundation.org.

Thank you,
Vanessa

On 07/30/2019 12:01 PM, Vanessa Valderrama wrote:
>
> Starting maintenance
>
>
> On 07/30/2019 11:02 AM, Vanessa Valderrama wrote:
>>
>> Jenkins has been placed in shutdown mode for maintenance
>>
>>
>>
>> On 07/29/2019 10:29 AM, Vanessa Valderrama wrote:
>>>
>>> Maintenance reminder
>>>
>>>
>>> On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:

 *What:*

 FD.io system maintenance

   * Jenkins
   o OS updates
   o Upgrade from 2.164.3 to 2.176.2
   + https://jenkins.io/changelog-stable/
   o Update plug-ins
   o Memory upgrade

   * Nexus
   o OS updates

   * Gerrit
   o OS updates
   o Upgrade from 2.14.6 to 2.16
   + https://www.gerritcodereview.com/2.16.html

   * JIRA
   o OS updates

   * Sonar
   o OS updates

   * OpenGrok OS updates

 *When:*

 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

 *Impact:*

 The maintenance will require a reboot of each FD.io system. Jenkins
 will be placed in shutdown mode at 1600 UTC.  Please let us know if
 there are any jobs that cannot be aborted.  The following systems
 will be impacted:

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


>>>
>>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13620): https://lists.fd.io/g/vpp-dev/message/13620
Mute This Topic: https://lists.fd.io/mt/32603362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

2019-07-30 Thread Vanessa Valderrama 
Starting maintenance


On 07/30/2019 11:02 AM, Vanessa Valderrama wrote:
>
> Jenkins has been placed in shutdown mode for maintenance
>
>
>
> On 07/29/2019 10:29 AM, Vanessa Valderrama wrote:
>>
>> Maintenance reminder
>>
>>
>> On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:
>>>
>>> *What:*
>>>
>>> FD.io system maintenance
>>>
>>>   * Jenkins
>>>   o OS updates
>>>   o Upgrade from 2.164.3 to 2.176.2
>>>   + https://jenkins.io/changelog-stable/
>>>   o Update plug-ins
>>>   o Memory upgrade
>>>
>>>   * Nexus
>>>   o OS updates
>>>
>>>   * Gerrit
>>>   o OS updates
>>>   o Upgrade from 2.14.6 to 2.16
>>>   + https://www.gerritcodereview.com/2.16.html
>>>
>>>   * JIRA
>>>   o OS updates
>>>
>>>   * Sonar
>>>   o OS updates
>>>
>>>   * OpenGrok OS updates
>>>
>>> *When:*
>>>
>>> 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
>>>
>>> *Impact:*
>>>
>>> The maintenance will require a reboot of each FD.io system. Jenkins
>>> will be placed in shutdown mode at 1600 UTC.  Please let us know if
>>> there are any jobs that cannot be aborted.  The following systems
>>> will be impacted:
>>>
>>>   * Jenkins production
>>>   * Jenkins sandbox
>>>   * Nexus
>>>   * Gerrit
>>>   * JIRA
>>>   * Sonar
>>>   * OpenGrok
>>>
>>>
>>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13619): https://lists.fd.io/g/vpp-dev/message/13619
Mute This Topic: https://lists.fd.io/mt/32603362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] jenkins jobs failing timing out trying to reach gerrit

2019-07-30 Thread Ed Kern via Lists.Fd.Io 

Just a heads up that this outage looks like network issues between vexxhost and 
gerrit servers
and lasted <30 minutes.

Looks like many of the failed jobs passed in the retry.

We are now full steam ahead into the maint window.

Ed



On Jul 30, 2019, at 9:12 AM, Ed Kern via Lists.Fd.Io 
mailto:ejk=cisco@lists.fd.io>> wrote:


https://jira.linuxfoundation.org/servicedesk/customer/portal/4/SUPPORT-321


vanessa is actively looking into this presently.

Ed


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13616): https://lists.fd.io/g/vpp-dev/message/13616
Mute This Topic: https://lists.fd.io/mt/32655012/675649
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  
[e...@cisco.com]
-=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13618): https://lists.fd.io/g/vpp-dev/message/13618
Mute This Topic: https://lists.fd.io/mt/32655012/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io Maintenance: 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

2019-07-30 Thread Vanessa Valderrama 
Jenkins has been placed in shutdown mode for maintenance



On 07/29/2019 10:29 AM, Vanessa Valderrama wrote:
>
> Maintenance reminder
>
>
> On 07/25/2019 04:09 PM, Vanessa Valderrama wrote:
>>
>> *What:*
>>
>> FD.io system maintenance
>>
>>   * Jenkins
>>   o OS updates
>>   o Upgrade from 2.164.3 to 2.176.2
>>   + https://jenkins.io/changelog-stable/
>>   o Update plug-ins
>>   o Memory upgrade
>>
>>   * Nexus
>>   o OS updates
>>
>>   * Gerrit
>>   o OS updates
>>   o Upgrade from 2.14.6 to 2.16
>>   + https://www.gerritcodereview.com/2.16.html
>>
>>   * JIRA
>>   o OS updates
>>
>>   * Sonar
>>   o OS updates
>>
>>   * OpenGrok OS updates
>>
>> *When:*
>>
>> 2019-07-30 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)
>>
>> *Impact:*
>>
>> The maintenance will require a reboot of each FD.io system. Jenkins
>> will be placed in shutdown mode at 1600 UTC.  Please let us know if
>> there are any jobs that cannot be aborted.  The following systems
>> will be impacted:
>>
>>   * Jenkins production
>>   * Jenkins sandbox
>>   * Nexus
>>   * Gerrit
>>   * JIRA
>>   * Sonar
>>   * OpenGrok
>>
>>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13617): https://lists.fd.io/g/vpp-dev/message/13617
Mute This Topic: https://lists.fd.io/mt/32603362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] jenkins jobs failing timing out trying to reach gerrit

2019-07-30 Thread Ed Kern via Lists.Fd.Io 

https://jira.linuxfoundation.org/servicedesk/customer/portal/4/SUPPORT-321


vanessa is actively looking into this presently.

Ed


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13616): https://lists.fd.io/g/vpp-dev/message/13616
Mute This Topic: https://lists.fd.io/mt/32655012/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] SIGSEGV when adding route and abf with the same gateway

2019-07-30 Thread fdr . kozlov 
Hi Neale,
The patch fixed my problem.
Thanks.

Fedor
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13615): https://lists.fd.io/g/vpp-dev/message/13615
Mute This Topic: https://lists.fd.io/mt/32639594/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Not able to access https://git.fd.io/ - Invalid certificate

2019-07-30 Thread Ray Kinsella 
I have raised an LF ticket to fix this.

On 30/07/2019 06:46, Akshay Joshi wrote:
> Hi,
> 
> I am not able to able to access https://git.fd.io/ . Looks like
> certificate is expired on 30 July 2019. I have attached the screenshot.
> 
> Thanks,
> Akshay
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#13608): https://lists.fd.io/g/vpp-dev/message/13608
> Mute This Topic: https://lists.fd.io/mt/32651182/675355
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [m...@ashroe.eu]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13614): https://lists.fd.io/g/vpp-dev/message/13614
Mute This Topic: https://lists.fd.io/mt/32651691/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Not able to access https://git.fd.io/ - Invalid certificate

2019-07-30 Thread Akshay Joshi 
Thanks for reply. I can ignore the warnings on browser but it is impacting 
while downloading GoVPP (go get git.fd.io/govpp.git).
Sorry this is a wrong mailing list, I have posted the same query on GoVPP 
mailing list.

Thanks,
Akshay
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13613): https://lists.fd.io/g/vpp-dev/message/13613
Mute This Topic: https://lists.fd.io/mt/32651691/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] SIGSEGV when adding route and abf with the same gateway

2019-07-30 Thread Neale Ranns via Lists.Fd.Io 

Hi,

Here’s the fix:
  https://gerrit.fd.io/r/c/20914/

/neale

De :  au nom de "Neale Ranns via Lists.Fd.Io" 

Répondre à : "Neale Ranns (nranns)" 
Date : lundi 29 juillet 2019 à 19:25
À : "fdr.koz...@yandex.com" , "vpp-dev@lists.fd.io" 

Cc : "vpp-dev@lists.fd.io" 
Objet : Re: [vpp-dev] SIGSEGV when adding route and abf with the same gateway


Hi,

You can reorder the route and ABF programming as a work around.
I’ll have a fix shortly.

/neale

De :  au nom de "fdr.koz...@yandex.com" 

Date : lundi 29 juillet 2019 à 08:24
À : "vpp-dev@lists.fd.io" 
Objet : [vpp-dev] SIGSEGV when adding route and abf with the same gateway

Hi vpp-dev
When I add an abf policy and then add a route to the same gateway, a SIGSEGV 
will appear.
These are the steps to generate the problem:
First setup interfaces:
vppctl set int state GigabitEthernet3/0/0 up
vppctl set int state GigabitEthernet4/0/0 up
vppctl set int ip address GigabitEthernet3/0/0 200.200.200.2/24
vppctl set int ip address GigabitEthernet4/0/0 100.100.100.1/24
Now create an acl using vpp_api_test
acl_add_replace permit dst 1.1.1.1
And then add abf policy and route which cause crash
vppctl abf policy add id 9001 acl 0 via 100.100.100.2 GigabitEthernet4/0/0
vppctl abf attach ip4 policy 9001 priority 1 GigabitEthernet3/0/0
vppctl ip route add 8.8.8.0/24 via 100.100.100.2 GigabitEthernet4/0/0

I see this SIGSEGV on both master and stable/1904 branches:

received signal SIGSEGV, PC 0x7f51a1b60160, faulting address 0x7f61608d8814
#0  0x7f51a0fde0db 0x7f51a0fde0db
#1  0x7f51a0904890 0x7f51a0904890
#2  0x7f51a1b60160 fib_urpf_list_lock + 0x10
#3  0x7f51a1b5408f fib_entry_src_mk_lb + 0x1bf
#4  0x7f51a1b54391 fib_entry_src_action_install + 0x131
#5  0x7f51a1b51691 fib_entry_create + 0x71
#6  0x7f51a1b486b8 fib_table_entry_update + 0x1c8
#7  0x7f51a1b6398e fib_api_route_add_del + 0x7e
#8  0x7f51a1879e3f vl_api_ip_route_add_del_t_handler + 0x21f
#9  0x7f51a1f26d8c vl_msg_api_handler_with_vm_node + 0x8c
#10 0x7f51a1f0b815 vl_mem_api_handle_msg_main + 0x45
#11 0x7f51a1f1b38d 0x7f51a1f1b38d
#12 0x7f51a0f92ea6 0x7f51a0f92ea6
#13 0x7f51a04818bc 0x7f51a04818bc

What should I do to solve this problem?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13612): https://lists.fd.io/g/vpp-dev/message/13612
Mute This Topic: https://lists.fd.io/mt/32639594/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] abf problem with arp

2019-07-30 Thread Neale Ranns via Lists.Fd.Io 

Hi Brayan,

Please try with:
https://gerrit.fd.io/r/c/20913/

/neale

De :  au nom de brayan ortega 
Date : dimanche 28 juillet 2019 à 12:44
À : "Neale Ranns (nranns)" 
Cc : "vpp-dev@lists.fd.io" 
Objet : Re: [vpp-dev] abf problem with arp

Dear Neale,
I have tried to config vpp based on your proposed configuration and after apply 
this command "abf policy add id 9001 acl 0  via ip4-lookup-in-table 42", a 
Segfault is happened.
I'm using vpp v19.08-rc0~698-g1f50bf8fc (master branch). also, I checked it on 
vpp 19.04 and the result was same.

log:
2019 Jul 28 10:30:08  received signal SIGSEGV, PC 0x7fc588126c6c, faulting 
address 0x
2019 Jul 28 10:30:08 #0  0x7fc5875b604b 0x7fc5875b604b
2019 Jul 28 10:30:08 #1  0x7fc586edc890 0x7fc586edc890
2019 Jul 28 10:30:08 #2  0x7fc588126c6c unformat_fib_route_path + 0x3ec
2019 Jul 28 10:30:08 #3  0x7fc586a9e5bb va_unformat + 0x6bb
2019 Jul 28 10:30:08 #4  0x7fc586a9ec67 unformat + 0x87
2019 Jul 28 10:30:08 #5  0x7fc545aa1114 0x7fc545aa1114
2019 Jul 28 10:30:08 #6  0x7fc58754d859 0x7fc58754d859
2019 Jul 28 10:30:08 #7  0x7fc58754db95 0x7fc58754db95
2019 Jul 28 10:30:08 #8  0x7fc58754df44 vlib_cli_input + 0xa4
2019 Jul 28 10:30:08 #9  0x7fc5875afbea 0x7fc5875afbea
2019 Jul 28 10:30:08 #10 0x7fc5875b3998 0x7fc5875b3998
2019 Jul 28 10:30:08 #11 0x7fc58756ae36 0x7fc58756ae36
2019 Jul 28 10:30:08 #12 0x7fc586a597fc 0x7fc586a597fc

Best regards, Brayan

On Thu, Jul 25, 2019 at 12:38 PM Neale Ranns (nranns) 
mailto:nra...@cisco.com>> wrote:

Hi Brayan,

First let’s discuss a bit your config and your objectives:

  acl ID 0 permit { any }
  set int ip addr GigabitEthernetb/0/0 30.30.30.1/24
  set int ip addr GigabitEthernet3/0/0 20.20.20.1/24

  abf policy add id 9001 acl 0  via 0.0.0.0 GigabitEthernetb/0/0
  abf attach ip4 policy 9001 priority 1 GigabitEthernet3/0/0

I’m sure you know that you can achieve the same by replacing the ABF route with 
a default route, so no doubt this is a test for you and you intend to make the 
ACL more expressive. So let’s consider some more scenarios. First we’ll correct 
policy rule to include the nexthop, since any packets not going to 
30.30.30.0/24 need to be sent to a next-hop on the LAN 
(we’ll discount proxy ARP as a solution because it does scale to add an ARP 
entry for every host on the internet).

  Acl ID 0 permit (tcp port 80 }
  abf policy add id 9001 acl 0  via 30.30.30.2 GigabitEthernetb/0/0

so if a packet now arrives for 30.30.30.3 to TCP port 80, where wold you like 
it to go? Do you want it to follow a routing decision and go to 30.30.30.3, or 
follow the abf decision to 30.30.30.2?

now let’s add another connected subnet.

  set int ip addr GigabitEthernet9/0/0 40.40.40.1/24

packets destined to this subnet will also match the ABF rule. Again consider a 
packet to 40.40.40.2 do you want these packets to follow a routing decision and 
be forwarded to 40.40.40.2 on GigabitEthernet9/0/0 or to 30.30.30.2 on 
GigabitEthernetb/0/0?

In general, when does a routing decision override the ABF result?
In VPP’s ABF implementation the answer is never. The ABF feature runs first and 
it is the only decision that is made. If you want to change this behaviour you 
can ‘insert’ a routing decision by using it as the result of ABF. For example:

  # create a table in which the post ABF routing decision will be made
  ip table add 42
  # add routes for prefixes that we want to override the ABF decision
  # these routes will then perform a lookup in default table
  ip route add table 42 30.30.30.0/24 via 
ip4-lookup-in-table 0
  ip route add table 42 40.40.40.0/24 via 
ip4-lookup-in-table 0
  # all the rest of the packets do the same as the ABF policy
  ip route add table 42 0.0.0.0/24 via 30.30.30.2 
GigabitEthernetb/0/0

  # the ABF policy result in a lookup in our override table
  abf policy add id 9001 acl 0  via ip4-lookup-in-table 42


hope this helps,
neale



De : brayan ortega 
mailto:brayan.ortega6...@gmail.com>>
Date : mercredi 24 juillet 2019 à 16:13
À : "Neale Ranns (nranns)" mailto:nra...@cisco.com>>
Cc : "vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Objet : Re: [vpp-dev] abf problem with arp

Dear Neale,
Thanks for your prompt response.
Answer comments inline.

On Wed, Jul 24, 2019 at 5:16 PM Neale Ranns (nranns) 
mailto:nra...@cisco.com>> wrote:

Dear Brayan,

You should always add a next-hop to a path when IP routing.
Answers comments inline.

/neale

De : mailto:vpp-dev@lists.fd.io>> au nom de brayan ortega 
mailto:brayan.ortega6...@gmail.com>>
Date : mercredi 24 juillet 2019 à 11:25
À : "vpp-dev@lists.fd.io" 
mailto:vpp-dev@lists.fd.io>>
Objet : [vpp-dev] abf problem with arp

Dear VPP Folks,
I'm using vpp v19.08-rc0~698-g1f50bf8fc (master

Re: [vpp-dev] Not able to access https://git.fd.io/ - Invalid certificate

2019-07-30 Thread Zhiyong Yang 
Akshay,

I can access https://git.fd.io/ .

Thanks
Zhiyong
From: vpp-dev@lists.fd.io  On Behalf Of Akshay Joshi
Sent: Tuesday, July 30, 2019 1:46 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Not able to access https://git.fd.io/ - Invalid certificate

Hi,

I am not able to able to access https://git.fd.io/ . Looks like certificate is 
expired on 30 July 2019. I have attached the screenshot.

Thanks,
Akshay
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13609): https://lists.fd.io/g/vpp-dev/message/13609
Mute This Topic: https://lists.fd.io/mt/32651691/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-