Le mercredi 25 novembre 2015 à 11:05 +0530, Kaushal M a écrit : > On Wed, Nov 25, 2015 at 12:22 AM, Michael Scherer <[email protected]> wrote: > > Le lundi 23 novembre 2015 à 11:56 +0100, Michael Scherer a écrit : > >> Le jeudi 29 octobre 2015 à 11:24 +0000, Niels de Vos a écrit : > >> > Humble Chirammal <hchiramm@...> writes: > >> > > > >> > > > >> > > Hi, > >> > > FYI, > >> > > It seems that, https://github.com/gluster/glusterfs code > >> > > repo has not synced from gerrit for some time and the last commit ( > >> > > 51632e1eec3ff88d19867dc8d266068dd7db432a) > >> > > recorded on Sep 10 . > >> > > Does any one know, why the gerrit plugin is broken? -- > >> > > >> > I've now manually synced the glusterfs repo on GitHub with the current > >> > state > >> > from Gerrit. If the automatic sync takes time to get configured/setup > >> > again, we > >> > might need to do this on regular basis? Anyway, ping me if it needs to > >> > be done > >> > again (not for each commit though!). > >> > >> One solution is to just add a ssh key on the repo, it can be found in > >> the settings. > >> > >> That's how I plan to do for the salt repo, but github is being annoying > >> a requires 1 different ssh key per repo, and I do need to take that in > >> account. > >> (the joy of having a SaaS service...) > > > > So I was looking at that, and just want to be sure I do publish the good > > repository. > > > > So we are looking at pushing the git repo from dev.gluster.org ( ie, > > gerrit ), in /review/review.gluster.org/git > > > > And there is all of them: > > > > All-Projects.git > > automation.git > > glusterfs-afrv1.git > > glusterfs.git > > glusterfs-hadoop.old.git > > glusterfs-nsr.git > > glusterfs-quota.git > > glusterfs-snapshot.git > > glusterfs-specs.git > > gluster-nagios-addons.git > > gluster-nagios-common.git > > gluster-nagios.git > > gluster-operations-guide.git > > gluster-swift.git > > gmc.git > > libgfapi-python.git > > nagios-gluster-addons.git > > nagios-server-addons.git > > qa.git > > regression.git > > swiftkrbauth.git > > > > Should all be synced ? > > Most of these are inactive. We'll need to check with the owners to > find out if they need to be replicated. > The most important and active repos here would be glusterfs.git and > glusterfs-specs.git. These need to be replicated.
Ok. And I assume I can sync the anonymous clone, and use git push -f ? I propose to have a separate small VM for that, so the ssh keys to push on github are separate from any complex application like github. We can later move it back on a regular server ( or just use some magic kubernetes/atomic system ). (Ideally, i would even add support for the github api to deploy the key, but it might be overkill for now) -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
