Re: can we kill the closed: question is answered feature on ask fedora?
On 03/24/2015 10:51 PM, David Gay wrote: - Original Message - From: Matthew Miller mat...@fedoraproject.org To: infrastructure@lists.fedoraproject.org Sent: Tuesday, March 24, 2015 6:13:07 PM Subject: can we kill the closed: question is answered feature on ask fedora? I might have complained about this before, but now I'm serious. :) It's incredibly counterintuitive and weird to have questions closed because they're answered, I guess unless they're an individual issue that only affects one person. Anything that might be helpful later and which has a helpful answer should be the _opposite_ of closed! -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure I forgot about this! Closing the question removes it from visibility/searchability, right? If so, killing this feature makes sense to me. -- David ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure Closing the question adds a blockquote that says This question was closed by 'person' because 'the question has been answered and the answer was accepted'. Users can continue to comment, suggest answers, edit, post comments as answers, contribute inaccurate answers, whatever, as long as they aren't deterred by the closed banner. Basically, I agree about it being a silly reason to close a question, except that it might do things that it isn't actually doing. So, +1 from me, let's turn it off. Amusingly, the only way to access the list of close reasons is to have moderation turned on, and start choosing reasons to reject a post :) I'll remove this soon, unless someone gets to it or strenuously objects soon. --Pete ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: users belonging to tenant in FedoraCloud
On 03/25/2015 02:40 AM, Kevin Fenzi wrote: The login here doesn't actually work for me in the new cloud; is it expected to, or were new passwords allocated? These were new randomly generated passwords. I can send you that one, but... see below. This is kind of tricky. I have to first set a password for new user. So I can then upload his SSH key. Then Kevin or somebody else have to tell you that password so you can log in and change it. In OpenStack Kilo will be Forgoten password feature, where you will be able to reset it yourself. However that is far feature for us. I'd like to use instances in the cloud for status reporting of tasks from the current atomic01.qa machine, and move off the deprecated fed-cloud02. Thats great, but the new cloud is not yet done. It's not open for business. ;) We are going to reinstall it at least one more time before we put it in service. So, I can send you info, but you should realize any instances you make can and will be completely vaporized when we reinstall, and possibly could break when we try and fix something else. I'm not sure if anyone else was using the old cockpit tenant anymore; I briefly repurposed it for rpm-ostree work. So perhaps the right thing here is to request a new atomic tenant. Sure, we could rename... makes sense, but we can do that when we reinstall more likely. OK. I will rename it to atomic in playbook. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: users belonging to tenant in FedoraCloud
On 03/24/2015 11:29 PM, Colin Walters wrote:
- { name: cockpit, email: 'walt...@redhat.com', tenant: scratch,
password: {{cockpit_password}} }
Colin,
to which FAS account this maps? I need to know which SSH key I should upload
for this account. Or you can even provide
me different SSH key, which is not in FAS (but then please send it with GPG
signed email).
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: can we kill the closed: question is answered feature on ask fedora?
On 25 March 2015 at 00:00, Pete Travis li...@petetravis.com wrote: On 03/24/2015 10:51 PM, David Gay wrote: - Original Message - From: Matthew Miller mat...@fedoraproject.org To: infrastructure@lists.fedoraproject.org Sent: Tuesday, March 24, 2015 6:13:07 PM Subject: can we kill the closed: question is answered feature on ask fedora? I might have complained about this before, but now I'm serious. :) It's incredibly counterintuitive and weird to have questions closed because they're answered, I guess unless they're an individual issue that only affects one person. Anything that might be helpful later and which has a helpful answer should be the _opposite_ of closed! -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure I forgot about this! Closing the question removes it from visibility/searchability, right? If so, killing this feature makes sense to me. -- David ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure Closing the question adds a blockquote that says This question was closed by 'person' because 'the question has been answered and the answer was accepted'. Users can continue to comment, suggest answers, edit, post comments as answers, contribute inaccurate answers, whatever, as long as they aren't deterred by the closed banner. Basically, I agree about it being a silly reason to close a question, except that it might do things that it isn't actually doing. So, +1 from me, let's turn it off. Amusingly, the only way to access the list of close reasons is to have moderation turned on, and start choosing reasons to reject a post :) I'll remove this soon, unless someone gets to it or strenuously objects soon. --Pete I don't object. Is there a way to say This problem was solved for me. by the original poster? ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: can we kill the closed: question is answered feature on ask fedora?
On Wed, Mar 25, 2015 at 09:27:46AM -0600, Stephen John Smoogen wrote: I don't object. Is there a way to say This problem was solved for me. by the original poster? Absolutely -- they can put a checkmark by an answer, which a) marks that answer as such, b) gives extra karma to the person who provided that answer, and c) marks the whole question as answered (which is different from just has answers) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Filters in our ansible.git
I created ./filter_plugins/openstack.py in our ansible.git to easy writing host_vars in our new cloud. So instead of ids you can write names of networks, images... So far I tested it on separate machine and it works, when I have this directory in ./ and I run ansible playbook in that directory. And according the ansible documentation the directory structure is correct and those filters should be loaded automaticaly without need to load them directly. However: $ sudo rbac-playbook groups/copr-backend.yml EXECV: /usr/bin/sudo -i /bin/bash -i -c /usr/bin/python2 /usr/bin/ansible-playbook /srv/web/infra/ansible/playbooks/groups/copr-backend.yml PLAY [check/create instance] ** TASK: [spin UP VM using nova_compute] * fatal: [copr-be-dev.cloud.fedoraproject.org - 127.0.0.1] = template error while templating string: no filter named 'image_name_to_id' FATAL: all hosts have already failed -- aborting This playbook use new tasks/persistent_cloud_new.yml so it may not work completely, but the goal is to get past this error. I have no clue how I can debug it on lockbox. Can somebody from @sysadmin-main investigate it please? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: can we kill the closed: question is answered feature on ask fedora?
On Mar 25, 2015 9:28 AM, Stephen John Smoogen smo...@gmail.com wrote: On 25 March 2015 at 00:00, Pete Travis li...@petetravis.com wrote: On 03/24/2015 10:51 PM, David Gay wrote: - Original Message - From: Matthew Miller mat...@fedoraproject.org To: infrastructure@lists.fedoraproject.org Sent: Tuesday, March 24, 2015 6:13:07 PM Subject: can we kill the closed: question is answered feature on ask fedora? I might have complained about this before, but now I'm serious. :) It's incredibly counterintuitive and weird to have questions closed because they're answered, I guess unless they're an individual issue that only affects one person. Anything that might be helpful later and which has a helpful answer should be the _opposite_ of closed! -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure I forgot about this! Closing the question removes it from visibility/searchability, right? If so, killing this feature makes sense to me. -- David ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure Closing the question adds a blockquote that says This question was closed by 'person' because 'the question has been answered and the answer was accepted'. Users can continue to comment, suggest answers, edit, post comments as answers, contribute inaccurate answers, whatever, as long as they aren't deterred by the closed banner. Basically, I agree about it being a silly reason to close a question, except that it might do things that it isn't actually doing. So, +1 from me, let's turn it off. Amusingly, the only way to access the list of close reasons is to have moderation turned on, and start choosing reasons to reject a post :) I'll remove this soon, unless someone gets to it or strenuously objects soon. --Pete I don't object. Is there a way to say This problem was solved for me. by the original poster? There is a mechanism to mark an answer as 'correct' ; the status also shows in list/search views. The original poster needs 10 karma to mark a correct answer to their question; which is a handful of upvotes or comments, very minimal participation. Anyone with a moderately higher level of karma can mark answers to other's questions as correct. There's an adequate level of signal that a 'good' answer has been provided. --Pete ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Filters in our ansible.git
Hi, This is because ansible only looks in the cwd or in /usr/lib/ansible according to the documentation. I have submitted a PR to rbac-playbook to fix the cwd: https://bitbucket.org/tflink/ansible_utils/pull-request/3/set-the-correct-working-directory/diff With kind regards, Patrick Uiterwijk Fedora Infra - Original Message - I created ./filter_plugins/openstack.py in our ansible.git to easy writing host_vars in our new cloud. So instead of ids you can write names of networks, images... So far I tested it on separate machine and it works, when I have this directory in ./ and I run ansible playbook in that directory. And according the ansible documentation the directory structure is correct and those filters should be loaded automaticaly without need to load them directly. However: $ sudo rbac-playbook groups/copr-backend.yml EXECV: /usr/bin/sudo -i /bin/bash -i -c /usr/bin/python2 /usr/bin/ansible-playbook /srv/web/infra/ansible/playbooks/groups/copr-backend.yml PLAY [check/create instance] ** TASK: [spin UP VM using nova_compute] * fatal: [copr-be-dev.cloud.fedoraproject.org - 127.0.0.1] = template error while templating string: no filter named 'image_name_to_id' FATAL: all hosts have already failed -- aborting This playbook use new tasks/persistent_cloud_new.yml so it may not work completely, but the goal is to get past this error. I have no clue how I can debug it on lockbox. Can somebody from @sysadmin-main investigate it please? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: can we kill the closed: question is answered feature on ask fedora?
- Original Message - From: Matthew Miller mat...@fedoraproject.org To: Fedora Infrastructure infrastructure@lists.fedoraproject.org Sent: Wednesday, March 25, 2015 9:04:37 AM Subject: Re: can we kill the closed: question is answered feature on ask fedora? On Wed, Mar 25, 2015 at 09:27:46AM -0600, Stephen John Smoogen wrote: I don't object. Is there a way to say This problem was solved for me. by the original poster? Absolutely -- they can put a checkmark by an answer, which a) marks that answer as such, b) gives extra karma to the person who provided that answer, and c) marks the whole question as answered (which is different from just has answers) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure I never understood why the close answered questions practice was adopted. I assume there was a good reason, but I've never heard of a Q/A site doing that (ex. Stack Exchange). -- David ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: can we kill the closed: question is answered feature on ask fedora?
On Wed, Mar 25, 2015 at 02:46:38PM -0400, David Gay wrote: I never understood why the close answered questions practice was adopted. I assume there was a good reason, but I've never heard of a Q/A site doing that (ex. Stack Exchange). I think it comes from webforums, and is a workaround for that software not really being meant to handle QA. Keeps threads from being bumped by the inevitable off-topic discussion or from other people with similar questions who glom on to an old thread. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: users belonging to tenant in FedoraCloud
On Tue, Mar 24, 2015, at 09:40 PM, Kevin Fenzi wrote: Thats great, but the new cloud is not yet done. It's not open for business. ;) We are going to reinstall it at least one more time before we put it in service. So, I can send you info, but you should realize any instances you make can and will be completely vaporized when we reinstall, and possibly could break when we try and fix something else. That's fine by me. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: users belonging to tenant in FedoraCloud
On Wed, Mar 25, 2015, at 05:14 AM, Miroslav Suchý wrote:
On 03/24/2015 11:29 PM, Colin Walters wrote:
- { name: cockpit, email: 'walt...@redhat.com', tenant: scratch,
password: {{cockpit_password}} }
Colin,
to which FAS account this maps?
walters
I have walt...@redhat.com set as the email on that FAS account, and I assume
FAS would only allow that email to be associated with at most one account?
___
infrastructure mailing list
infrastructure@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Plan for tomorrow's Fedora Infrastructure meeting (2015-03-26)
The infrastructure team will be having it's weekly meeting tomorrow, 2015-03-26 at 18:00 UTC in #fedora-meeting on the freenode network. This week we are continuing to try something new. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of this morning is included in this email. kevin -- = Introduction = This shared document is for the next fedora infrastructure meeting. We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2015-03-26) #meetingname infrastructure #topic aloha #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk #topic New folks introductions / Apprentice feedback = Status / information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info the thing - your name) #topic announcements and information #info Got all our iscsi storage moved from old to new filer with no downtime! - kevin #info Got new rbac-playbook installed and working - patrick and tim #info New FMN release deployed to production. New features and bugfixes. - ralph #info Hooked some email lists up to fmn (scm-commits, meetingminutes) - ralph #info Turned off old emails from dist-git and pkgdb - ralph #info = Things we should discuss = (Use #topic your discussion topic - your username) #topic = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the info in this section) #topic Learn about ... = Meeting end stuff = #topic Open Floor #endmeeting pgp2qOxXU6Q5e.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: MM2 XMLRPC
On 24 March 2015 at 01:31, Adrian Reber adr...@lisas.de wrote: The xml-rpc interface does not work right now. I get Error checking in. Connection closed before checkin complete. Please try again later. There is no error in the error_log on mm-frontend01 and the access_log just says: 10.5.126.88 - - [17/Mar/2015:21:51:13 +] POST /mirrormanager2/xmlrpc HTTP/1.0 200 326 - xmlrpclib.py/1.0.1 (by www.pythonware.com) I don't know where to look for more error/debug messages. Something we could do for quick testing is setting the application in debug mode (this is only for testing and we should make sure to remove it afterward). in the wsgi: /var/www/mirrormanager2.wsgi set: application.debug = True then restart apache. This might give us more clue as to what's going on. I tried it with debug enabled but there is nothing in logs on mm-frontend01. Can something be seen in the proxy logs? Oh crap I didn't see this til now. Did anyone help you on this? If not can we work on this tomorrow (Thursday?) Adrian ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure -- Stephen J Smoogen. ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
