Re: [Gluster-infra] Gerrit issues
Hi Niels, That worked for me. Thanks a lot, that was a quick response. On Mon, Jul 18, 2016 at 6:27 PM, Niels de Voswrote: > On Mon, Jul 18, 2016 at 04:34:18PM +0530, Muthu Vigneshwaran wrote: > > Hi, > > > > I am a new contributor to Glusterfs. I have been sending some patches. > > Sadly, it neither maps my name in the bugzilla(It says as "Anonymous > > coward")[1] nor suggest my name to be added as a reviewer in Gerrit. I > have > > cloned the gluster repository from Gerrit with the same user name I have > on > > Github[2] > > I think you have to set your "Full Name" and email address in Gerrit as > well. After loggin in, go to teh settings: > http://review.gluster.org/#/settings/contact > > This might require you to logout/login after changing. Commenting on a > patch should show your name correctly after that. > > HTH, > Niels > > > > > > Here is the output of 'git config --list' > > > > user.email=mvign...@redhat.com > > user.name=Muthu-vigneshwaran > > core.repositoryformatversion=0 > > core.filemode=true > > core.bare=false > > core.logallrefupdates=true > > remote.origin.url=ssh://muthu-vigneshwa...@git.gluster.org/glusterfs.git > > remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* > > branch.master.remote=origin > > branch.master.merge=refs/heads/master > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=789278 (Look on the > recent > > comment) > > > > [2] https://github.com/Muthu-vigneshwaran > > > > > > -- > > Thanks, > > Muthu Vigneshwaran. > ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] Gerrit issues
Hi, I am a new contributor to Glusterfs. I have been sending some patches. Sadly, it neither maps my name in the bugzilla(It says as "Anonymous coward")[1] nor suggest my name to be added as a reviewer in Gerrit. I have cloned the gluster repository from Gerrit with the same user name I have on Github[2] Here is the output of 'git config --list' user.email=mvign...@redhat.com user.name=Muthu-vigneshwaran core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=ssh://muthu-vigneshwa...@git.gluster.org/glusterfs.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master [1] https://bugzilla.redhat.com/show_bug.cgi?id=789278 (Look on the recent comment) [2] https://github.com/Muthu-vigneshwaran -- Thanks, Muthu Vigneshwaran. ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Netbsd folders filling up
Nigel Babuwrote: > Thank you. I'll give that a shot. I also want to setup ntp Add ntpd=YES in /etc/rc.conf and run /etc/rc.d/ntpd start Note that the ntpdcurrently installed needs a secrity update. > and change passwords for all the machines in one go. Do it on one machine using vipw, copy /etc/master.passwd and run pwd_mkdb -p /etc/master.passwd eveyrwhere to regenerate /etc/passwd -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1357545] Gerrit login (review.gluster.org)
https://bugzilla.redhat.com/show_bug.cgi?id=1357545 Venky Shankarchanged: What|Removed |Added Assignee|b...@gluster.org|nig...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=7qYpifPr5z=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1357545] New: Gerrit login (review.gluster.org)
https://bugzilla.redhat.com/show_bug.cgi?id=1357545 Bug ID: 1357545 Summary: Gerrit login (review.gluster.org) Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: vshan...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Description of problem: Unable to login to review.gluster.org with github username: vshankar (gerrit user: venky). Please do the required "mapping". -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=eoNn4DnwFn=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Gerrit issues
On Mon, Jul 18, 2016 at 04:34:18PM +0530, Muthu Vigneshwaran wrote: > Hi, > > I am a new contributor to Glusterfs. I have been sending some patches. > Sadly, it neither maps my name in the bugzilla(It says as "Anonymous > coward")[1] nor suggest my name to be added as a reviewer in Gerrit. I have > cloned the gluster repository from Gerrit with the same user name I have on > Github[2] I think you have to set your "Full Name" and email address in Gerrit as well. After loggin in, go to teh settings: http://review.gluster.org/#/settings/contact This might require you to logout/login after changing. Commenting on a patch should show your name correctly after that. HTH, Niels > > Here is the output of 'git config --list' > > user.email=mvign...@redhat.com > user.name=Muthu-vigneshwaran > core.repositoryformatversion=0 > core.filemode=true > core.bare=false > core.logallrefupdates=true > remote.origin.url=ssh://muthu-vigneshwa...@git.gluster.org/glusterfs.git > remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* > branch.master.remote=origin > branch.master.merge=refs/heads/master > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=789278 (Look on the recent > comment) > > [2] https://github.com/Muthu-vigneshwaran > > > -- > Thanks, > Muthu Vigneshwaran. signature.asc Description: PGP signature ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Netbsd folders filling up
Thank you. I'll give that a shot. I also want to setup ntp and change passwords for all the machines in one go. On Mon, Jul 18, 2016 at 5:22 PM, Emmanuel Dreyfuswrote: > Nigel Babu wrote: > > > Oh, can I apply this to all the machines in one go? > > disklabel as is works with an interactive editor, but you can ealso > disklabel xbd0 > protofile then tweak the file and use disklabel -R > xbd0 protofile to load is in a batch. > > Or you can just modify nbslave70, image it and deploy to other machines, > it would not hurt. > > -- > Emmanuel Dreyfus > http://hcpnet.free.fr/pubz > m...@netbsd.org > -- nigelb ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1357466] New: NetBSD machines have IPv6 ip line for localhost before IPV4 line
https://bugzilla.redhat.com/show_bug.cgi?id=1357466 Bug ID: 1357466 Summary: NetBSD machines have IPv6 ip line for localhost before IPV4 line Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: rta...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Description of problem: /etc/hosts has the following content on NetBSD machines. ::1 localhost localhost. 127.0.0.1 localhost localhost. This is a problem when localhost is used for operations in tests. Let us have the current infra to give out only IPv4 IPs for now. We need a dedicated setup for IPv6 testing. How reproducible: Always Steps to Reproduce: 1. check /etc/hosts Additional info: -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=7khXrvrSUU=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Updating /opt/qa and installing dependencies
Le lundi 18 juillet 2016 à 09:51 +0530, Nigel Babu a écrit : > On Fri, Jul 15, 2016 at 04:45:24PM +0200, Michael Scherer wrote: > > Le vendredi 15 juillet 2016 à 11:43 +0530, Nigel Babu a écrit : > > > Hello, > > > > > > I'm toying with the idea that each job will have commands to install > > > dependencies and update the /opt/qa folder. This will make the whole > > > process of > > > adding a new node in the testing pool trivial requiring not a lot of > > > effort > > > from the infrastructure team. > > > > I do think this will make things more complex. > > > > Now, we have 1 ansible playbook to make a working jenkins builder [1], > > and later, we would have a half playbook, half jenkins jobs. > > > > We would still need to have stuff in ansible, because we need to > > configure the VM before leting jenkins run (installing java, setting the > > user and ssh keys, for a start, removing extra network card and ipv6 for > > more complicated stuff). > > > > What advantages would it bring to convert the existing work to jenkins > > jobs that we do not already have ? > > > > > However, if we break the /opt/qa repo, we'll spread the breakage > > > everywhere. > > > The fallback for errors would be to push a revert. Thoughts on this idea? > > > > [1] > > https://github.com/gluster/gluster.org_ansible_configuration/tree/master/roles/jenkins_builder > > -- > > Michael Scherer > > Sysadmin, Community Infrastructure and Platform, OSAS > > > > > > Here's what I'm thinking. I'm going to redefine our pool so we have a centos > pool. All linux jobs run on this pool. Ansible will be used to bootstrap these > machines. But in case we add a new job which needs a new package installed for > that particular test, the changes need to be made in both places, but you are > not blocked by the ansible run to deploy the new test. It can be pushed to > Jenkins immediately after merging. So that would be to remove friction for something that do not happen that much in practice, if I am not wrong. Because I still do not see how this is worth the extra complexity on ansible playbooks side, nor why we can't ask to people to push a ansible patch at the same time as a job. > Primarily, I want to remove any friction in deploying new tests. > > This means two things: > 1. The /opt/qa folder needs to be updated at the start of every run. > 2. Install any dependencies before the test. Most likely not needed. The 1 is ok. We will see right away when stuff broke (like on freebsd) But I am not ok for 2 to be done by the job itself. People should put a PR on the ansible repo, and it will be deployed once merged as well. This will make sure that we have one specific place to look for all package installation, and will avoid hidden missing deps (like "job A require rpm B, job C requires rpm B too, but since job A is everywhere, no one ever add rpm B to job C, and so the day we remove job A, job C is suddenly incomplete"). This will also be slightly faster to not check the package db on every run, even if I recognize this is not gonna have a huge impact on perf. And if we ever start to need to add more repo than EPEL (since EPEL do not seems to provides the right go packages for some tests that were proposed), I rather have a good overview of that to avoid conflict in the long term. > I'm open to other solutions that will reduce this friction without needing > manual intervention. Making a PR to ansible is not more a manual intervention than making a PR for a job. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra