+1

30 day artefact availability (except official release artefacts, of course) is 
enough for us.

Thanks,
Jan

-----Original Message-----
From: csit-...@lists.fd.io <csit-...@lists.fd.io> On Behalf Of Peter Mikus via 
Lists.Fd.Io
Sent: Tuesday, August 28, 2018 8:57 AM
To: fdio-helpd...@rt.linuxfoundation.org
Cc: csit-...@lists.fd.io
Subject: Re: [csit-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP 
artifacts

Hello,

Yes I think this will work long term. (still will let others to comment but, 
for now looks good to me)

Thank you.

Peter Mikus
Engineer – Software
Cisco Systems Limited

-----Original Message-----
From: Vanessa Valderrama via RT <fdio-helpd...@rt.linuxfoundation.org>
Sent: Monday, August 27, 2018 6:27 PM
To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com>
Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-dev@lists.fd.io
Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP artifacts

Ed developed a script that will allow us to keep/remove artifacts based on the 
number of days. So we will remove artifacts older than 30 days.  Please let me 
know if this meets your requirements.

Thank you,
Vanessa


On Fri Aug 10 09:14:10 2018, jgel...@cisco.com wrote:
> 
> Hello,
> 
> Could you, please, let us know if the solution proposed by Peter below 
> is possible to implement or we need to start thinking about another
> (non-optimal) solution, e.g.
> 
> - compile vpp artefacts for every csit-vpp-functional job (time and 
> resource wasting)
> 
> - copy vpp artefacts needed for csit-vpp-functional jobs to one of 
> VIRL servers and use nfs/rsync/apache2 (just temporary solution as 
> VIRL servers are planned to be re-used when CSIT VIRL tests migration 
> to VPP_path and VPP_device tests is finished)
> 
> - copy vpp artefacts needed for csit-vpp-functional jobs to another 
> location on Nexus that is used to store csit reports (here we would 
> need solution for deleting obsolete artefacts)
> 
> Thanks,
> Jan
> 
> Jan Gelety
> Engineer - Software
> Cisco Systems, Inc.
> 
> -----Original Message-----
> From: csit-...@lists.fd.io <csit-...@lists.fd.io> On Behalf Of Peter 
> Mikus via Lists.Fd.Io
> Sent: Wednesday, August 8, 2018 5:29 PM
> To: fdio-helpd...@rt.linuxfoundation.org
> Cc: csit-...@lists.fd.io
> Subject: Re: [csit-dev] [FD.io Helpdesk #56625] Nexus
> fd.io.master.centos7 VPP artifacts
> 
> Hello,
> 
> We are creating branches on weekly basis and CSIT being verified in 
> weekly job. So the question is if there is option to set "date" or 
> "number" when limiting repo.
> 
> Counting the cadence of up to 10 merges per day (artifacts posted on
> Nexus) then means that safe value is around 100-120 artifacts.
> This I am talking about master branch of VPP. Stable branches we 
> should be ok with just 10-15 artifacts.
> 
> Peter Mikus
> Engineer – Software
> Cisco Systems Limited
> 
> -----Original Message-----
> From: Vanessa Valderrama via RT [mailto:fdio- 
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, August 08, 2018 5:22 PM
> To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) 
> <pmi...@cisco.com>
> Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp- 
> d...@lists.fd.io
> Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP 
> artifacts
> 
> Peter,
> 
> How many artifacts do you need us to retain for your testing?
> 
> Thank you,
> Vanessa
> 
> 
> On Mon Aug 06 04:53:29 2018, pmi...@cisco.com wrote:
> > Hello Vanessa,
> >
> > For CSIT it is not about release or not. We would need to increase 
> > cadence on our weekly jobs to daily. Currently CSIT jobs are all 
> > failing as VPP has more than 10-15 artifacts in week.
> > Our defined stable versions of VPP (updated once a week) are not in 
> > repo anymore or are obsoleting faster than we are updating. This is 
> > impacting everything.
> >
> > Right now we are *blocked* and we need to work new solution do adopt.
> >
> > One of the option is that we will have to start building VPP from 
> > scratch for every job as we cannot use artifacts anymore. This will 
> > cause huge overhead on infrastructure and execution times will 
> > extend as nexus acted as optimization for us.
> > Right now Nexus is not an option for us anymore. This also means 
> > that Nexus artifacts will not be tested by CSIT.
> >
> > Peter Mikus
> > Engineer – Software
> > Cisco Systems Limited
> >
> > -----Original Message-----
> >   From: Vanessa Valderrama via RT [mailto:fdio- 
> > helpd...@rt.linuxfoundation.org]
> > Sent: Tuesday, July 31, 2018 8:16 PM
> >  To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) 
> > <pmi...@cisco.com>
> >  Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp- 
> > d...@lists.fd.io
> >  Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP 
> > artifacts
> >
> > Peter,
> >
> > We need to make a decision on the number of artifacts to keep. I'd 
> > like to propose the following
> >
> > previous release repos - 10 packages per subproject master - 10 to
> > 15 packages per subproject
> >
> > Thank you,
> > Vanessa
> >
> > On Tue Jun 05 00:51:02 2018, pmi...@cisco.com wrote:
> > > Hello Vanessa,
> > >
> > > Thank you for an explanation. Indeed this will impact certain 
> > > things that are planned like "automatic bisecting" (downloading 
> > > and testing range of artifacts). Let me analyze current situation 
> > > with CSIT team and get back to you.
> > >
> > > Peter Mikus
> > > Engineer – Software
> > > Cisco Systems Limited
> > >
> > >
> > > -----Original Message-----
> > >    From: Vanessa Valderrama via RT [mailto:fdio- 
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Monday, June 04, 2018 9:47 PM
> > >   To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) 
> > > <pmi...@cisco.com>
> > >   Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp- 
> > > d...@lists.fd.io
> > >   Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP 
> > > artifacts
> > >
> > > Peter,
> > >
> > > The fd.io.master.centos7 repo had to be cleaned up significantly 
> > > to eliminate Jenkins build timeout errors.  This was discussed in 
> > > the TSC. Going forward we'll only be keeping an average of 10 of 
> > > the current release candidate artifacts in the repository.  Please 
> > > let me know if this retention policy causes an issue for you.
> > >
> > > We do need to clean up the other repositories as well.  Please let 
> > > me know if you'd like to discuss retention policies.  I'll hold 
> > > off on cleaning up other repositories for now.
> > >
> > > Thank you,
> > > Vanessa
> > >
> > > On Wed May 30 10:20:21 2018, pmi...@cisco.com wrote:
> > > > Hello,
> > > >
> > > > I have recently spotted that CentOS repo got reduced and old 
> > > > binaries are missing [1].
> > > >
> > > > Is this expected?
> > > > Will the similar be done for Ubuntu repos?
> > > >
> > > > Was this announced somewhere?
> > > >
> > > > Thank you.
> > > >
> > > > [1]
> > > > https://nexus.fd.io/content/repositories/fd.io.master.centos7/io
> > > > /f
> > > > d/
> > > > vp
> > > > p/vpp/
> > > >
> > > > Peter Mikus
> > > > Engineer - Software
> > > > Cisco Systems Limited
> > > > [http://www.cisco.com/web/europe/images/email/signature/logo05.j
> > > > pg
> > > > ]
> > > > Think before you print.
> > > >     This email may contain confidential and privileged material 
> > > > for the
> > > >    sole use of the intended recipient. Any review, use, 
> > > > distribution or
> > > >   disclosure by others is strictly prohibited. If you are not the
> > > >    intended recipient (or authorized to receive for the 
> > > > recipient),  please contact the sender by reply email and delete 
> > > > all copies of this message.
> > > > For corporate legal information go to:
> > > > http://www.cisco.com/web/about/doing_business/legal/cri/index.ht
> > > > ml
> > >
> > >
> > >
> >
> >
> >
> 
> 
> 




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

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

Reply via email to