Re: RPM Repository Metadata

[Nathan McGarvey]

You might also consider tying the createrepo command into something
that is trigger-based instead of time-based. (E.g. a systemd.path unit
or something with inotify, or if you have an automated publisher like
Jenkins or something, just put it as a post-publish command.)

That --baseurl is also causing everyone to go directly to the source
instead, since their main repomd.xml will redirect them to the
non-mirror instead of downstream mirror, which may have different
filelist and primary and other files. You might save some bandwidth and
other headaches if you left that flag out so it is just a relative link
to wherever you run that as so:

cd 
createrepo  .

Note the dot for the current directory.


...unless you want everyone to go directly to the upstream source.
I'm not sure what design you're going for.


   Thanks both for considering this so quickly.

Thanks,
-Nathan


On 2/16/21 1:59 AM, Wido den Hollander wrote:
> 
> 
> On 16/02/2021 07:00, Rohit Yadav wrote:
>> Wido - in that case should we disable metadata re-generating cronjobs
>> for both rpm/deb repos? We only need to regenerate repo metadata on a
>> new release. There's no need to do this via cron for official releases.
>>
> 
> I have disabled the CRON jobs for now for both RPM and DEB. Need to run
> them manually if we upload new packages.
> 
> Wido
> 
>>
>> Regards.
>>
>> 
>> From: Wido den Hollander 
>> Sent: Monday, February 15, 2021 21:30
>> To: dev@cloudstack.apache.org ; Rohit Yadav
>> 
>> Subject: Re: RPM Repository Metadata
>>
>>
>>
>> On 15/02/2021 09:51, Rohit Yadav wrote:
>>> Hi Nathan,
>>>
>>> Thanks for reporting, I've been managing the rpm builds/repos on the
>>> server and I wasn't aware of this issue.
>>> I checked and found there's a hourly cron job that updates rpm repo
>>> metadata using:
>>>
>>>   createrepo --update --workers 1 --baseurl >> options/paths>
>>>
>>>
>>> Based on your suggestion, I've changed the script to include:
>>> "createrepo --update --retain-old-md ".
>>>
>>> @Wido Hollander @Gabriel Beims
>>> Bräscher - any reason why we have the
>>> cron job to update repo metadata?
>>
>> No, I think it's just an oversight. It was setup and I don't think it
>> was very well thought of.
>>
>> The CRON is a very simple Shell script which probably can use some
>> attention.
>>
>> Wido
>>
>>>
>>> Regards.
>>>
>>> 
>>> From: Nathan McGarvey 
>>> Sent: Sunday, February 14, 2021 08:32
>>> To: dev@cloudstack.apache.org 
>>> Subject: RPM Repository Metadata
>>>
>>> To whom this reaches (@widodh, perhaps?):
>>>
>>>   First of all, thank you for building binary distributions (rpm,
>>> deb)
>>> of CloudStack.
>>>
>>>   I am attempting to create a downstream rsync mirror of the
>>> http://download.cloudstack.org/ centos/rhel repos. (Namely, centos and
>>> systemvm) and noticed two oddities:
>>>
>>>   1. The frequency with which the metadata is being rebuilt is
>>> astronomical. E.g.
>>> http://download.cloudstack.org/centos/8/4.15/repodata/ looks like it is
>>> being fully rebuilt every hour, though the RPMs contained within haven't
>>> been updated in over a month. Was this supposed to have a
>>> --retain-old-md or --retain-old-md-by-age flag? The default for things
>>> like RHEL 8 is 48 hours for metadata expiry, so re-generating the entire
>>> repo every hour can (and does) cause caching issues.
>>>
>>>   2. The metadata contained in
>>> http://download.cloudstack.org/centos/8/4.15/repodata/repomd.xml makes
>>> it virtually impossible to mirror since it points the  tag at
>>> http://cloudstack.apt-get.eu/
>>>   a. Most RPM repos (E.g. The CentOS official ones, just
>>> point the
>>>  tag to the repodata/> of the data type without external
>>> links via relative URI. (See
>>> http://mirror.centos.org/centos-8/8.3.2011/BaseOS/x86_64/os/repodata/repomd.xml
>>>
>>> , for example.)
>>>   b. Putting the xml:base in there effectively makes it not a
>>> mirror since anyone pointed at their local mirror will actually redirect
>>> to whatever xml:base is set to.
>>>
>>>   FWIW: It looks like cloudstack.apt-get.eu and
>>> download.cloudstack.org are *probably* the same host, which likely means
>>> the xml:base being set at all may not actually be doing anything useful.
>>>
>>>
>>>   Please pardon my ignorance if these technical configurations are
>>> intentional and have already been discussed as I am new poster to this
>>> thread.
>>>
>>>
>>> Thanks,
>>> -Nathan McGarvey
>>>
>>> rohit.ya...@shapeblue.com
>>> www.shapeblue.com
>>> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>>
>> rohit.ya...@shapeblue.com
>> www.shapeblue.com
>> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
>> @shapeblue
>>     
>>

AD zone networking

[Support Admin]

*Hi,*

I needed Advanced networking guide for create Advanced Zone. Than means 
network flow.


CT server and public to guest instance. My network diagram like this. My 
all server get ip from eth1 is local ip *10.66.0.0/16*


My server have two interface *eth0* and *eth1*.
*My query :* What is network diagram for Advanced zone with *Tag vLAN*. 
I have one managed switch.


Please give me any suggestion or tell me my network is ok.
--

*Thanks & Regards.*

Support Admin

Facebook  | Twitter 
 | Website 


116/1 West Malibagh, D. I. T Road

Dhaka-1217, Bangladesh

*Mob :* +088 01716915504

*Email :* support.ad...@technologyrss.com

*Web :* www.technologyrss.com 

Re: Goggle Summer of Code 2021

[Rohit Yadav]

Thanks for starting the thread Giles.

I would like to propose an idea that would help community onboard users with 
existing XenServer/VMware/* environments with VMs to CloudStack/KVM. This may 
sound like a big task but I see virt-v2v being used by some projects such as 
oVirt where it looks like virt-v2v does the heavy lifting and the 
integration/duct-tape is all that is required:
https://github.com/apache/cloudstack/issues/4696

I've added the proposal on the comdev wiki:
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list


Regards.


From: Giles Sirett 
Sent: Tuesday, February 16, 2021 14:59
To: dev@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: Goggle Summer of Code 2021

Hi all

It would be great if the CloudStack project were able to get a few Google 
Summer of Code  [1] students this year to work on projects within our 
community. We've had a number of previous GSoC students (examples at [2] ), who 
have worked on innovative features/ projects within cloudstack and have then 
gone on to become significant contributors to Cloudstack .


In order to be able to attract students to work on Cloudstack, we need 2 things:

  1.  A number of candidate projects for students to work on. Students browse 
all GSoC the candidate projects and choose one that interests them- effectively 
every organisation is competing for the students interest.  These projects 
therefore need to be reasonably interesting looking projects to attract 
potential students. The students spend approximately 9 weeks coding, so the 
projects need to be appropriately scaled
  2.  Somebody prepared to mentor the student throughout the duration of the 
project (usually the person who suggests the project)

The student application period starts 29 March [3]
The ASF  has registered itself as a mentor  organisation with Google , allowing 
individual Apache projects to list candidate projects  for students to work on. 
A wiki page [4]  has been created at the ASF level to allow ASF projects to  
list their ideas for students


I'm happy to coordinate this from a Cloudstack perspective.
If others are happy with this approach, then I ask for two things at this stage:


  1.  Could people suggest appropriate projects. This could be a piece of 
integration that you've always considered and not got around to or could be an 
improvement that you've always wanted to do. If people can reply to this thread 
with ANY ideas, it would be a good start (irrespective of whether you wish to 
be a mentor or not)
  2.  At the same time, could people say whether they'd be prepared to be a 
student mentor or not




[1] https://summerofcode.withgoogle.com/


[2]
https://blog.netapp.com/blogs/mentoring-with-google-summer-of-code-and-lessons-in-cloudstack/
https://dzone.com/articles/cloudstack-google-summer-code
https://opensource.googleblog.com/2014/07/gsoc-students-create-google-compute.html


[3]https://summerofcode.withgoogle.com/how-it-works/#timeline

[4] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list



Kind regards
Giles


giles.sir...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue




rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Goggle Summer of Code 2021

[Giles Sirett]

Hi all

It would be great if the CloudStack project were able to get a few Google 
Summer of Code  [1] students this year to work on projects within our 
community. We've had a number of previous GSoC students (examples at [2] ), who 
have worked on innovative features/ projects within cloudstack and have then 
gone on to become significant contributors to Cloudstack .


In order to be able to attract students to work on Cloudstack, we need 2 things:

  1.  A number of candidate projects for students to work on. Students browse 
all GSoC the candidate projects and choose one that interests them- effectively 
every organisation is competing for the students interest.  These projects 
therefore need to be reasonably interesting looking projects to attract 
potential students. The students spend approximately 9 weeks coding, so the 
projects need to be appropriately scaled
  2.  Somebody prepared to mentor the student throughout the duration of the 
project (usually the person who suggests the project)

The student application period starts 29 March [3]
The ASF  has registered itself as a mentor  organisation with Google , allowing 
individual Apache projects to list candidate projects  for students to work on. 
A wiki page [4]  has been created at the ASF level to allow ASF projects to  
list their ideas for students


I'm happy to coordinate this from a Cloudstack perspective.
If others are happy with this approach, then I ask for two things at this stage:


  1.  Could people suggest appropriate projects. This could be a piece of 
integration that you've always considered and not got around to or could be an 
improvement that you've always wanted to do. If people can reply to this thread 
with ANY ideas, it would be a good start (irrespective of whether you wish to 
be a mentor or not)
  2.  At the same time, could people say whether they'd be prepared to be a 
student mentor or not




[1] https://summerofcode.withgoogle.com/


[2]
https://blog.netapp.com/blogs/mentoring-with-google-summer-of-code-and-lessons-in-cloudstack/
https://dzone.com/articles/cloudstack-google-summer-code
https://opensource.googleblog.com/2014/07/gsoc-students-create-google-compute.html


[3]https://summerofcode.withgoogle.com/how-it-works/#timeline

[4] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list



Kind regards
Giles


giles.sir...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue