15:11:05 #startmeeting oVirt Infra 15:11:05 Meeting started Mon Dec 9 15:11:05 2013 UTC. The chair is knesenko. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:11:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:11:26 * bkp here 15:11:34 fabiand: so I should wait for Jenkins build for patch set 5? Last Jenkins' comment is about patch set 3, but I cannot find iso in build link 15:12:24 #topic Hosting 15:12:28 ok guys 15:12:36 #chair dcaro obasan eedri 15:12:36 Current chairs: dcaro eedri knesenko obasan 15:12:49 update on rackspcae 15:12:53 singler, yeah you should wait for patchset 5 - when you follow that jenkins link, the iso link is somewhat hidden. select centos or fedora at the bottom of the linked page and then the samll plus at the top of the follow up page, near artifacts 15:12:53 host is back 15:13:09 we need to try reinstall it once again .... 15:13:35 there are still issues with VPN, so if it will fail will need to open them a tciket once again 15:13:45 #action knesenko install rackspace03 15:15:01 #info there are still issues with VPN console 15:15:18 anything else on hosting ? eedri ? 15:15:36 knesenko, we need to add new vm for images 15:15:46 knesenko, that will be able to hold 100-200GB, 15:15:50 eedri: saw it ... on which setup ? 15:16:02 eedri: i don't think we have an infra for that right now 15:16:07 knesenko, well..if we manage to bring up RAX this week, we can put it there 15:16:14 knesenko, it has almost 1 TB free space 15:16:40 knesenko: we do a very ugly 'hack' to restore the network if the connectivity is lost 15:16:43 knesenko, if not, itamar will create a new vm on amazon and we'll just need to request DNS for it 15:16:51 eedri: I don't remember how much space we have for glusterfs 15:17:02 knesenko, iirc it's 1TB or more 15:17:11 eedri: rakckspace is not a stable setup 15:17:20 knesenko, we need it for backup as well 15:17:21 eedri: so we need to think before we install it 15:17:30 knesenko, ok, we can start with amazon vm then 15:17:35 eedri: ok 15:17:43 eedri: who will install it ? 15:17:56 eedri: itamar already created a VM with 500GB (for now) and gave oved access to take a look at setting it up 15:18:15 itamar: DNS name ? 15:18:17 itamar, thanks. can oved provide us with the ip so we can open a ticket for dns 15:18:18 no dns yet... 15:18:24 ping oved please... 15:18:43 #info itamar has created a VM on amazon to store images 15:18:45 knesenko, please add action item on oved to provide info and one for adding dns entry for images.ovirt.org? 15:19:27 #action once we have a DNS name update the WIKI 15:20:00 #action talk to oved and ask him for an info about images.ovirt.org 15:20:12 #action open a ticket for a DNS request 15:20:18 ok what next ? 15:20:34 there is open action item on upgrading all centos 6.4 to 6.5 15:20:45 ewoud, said he'll take it, but i don't know if its done yet 15:20:56 also jenkins slaves labels/names are not updated as well 15:21:21 knesenko, can you verify? and update if needed? 15:21:34 knesenko, currently blocking vdsm from pushing some patches to master 15:22:04 #action update all centos slaves from 6.4 to 6.5 15:22:25 #action eedri open a ticket and assign it to someone to upgrade centos slaves 15:22:47 #action knesenko update jenkins slaves labels 15:23:10 * orc_orc appears later 15:23:35 #chair orc_orc 15:23:35 Current chairs: dcaro eedri knesenko obasan orc_orc 15:23:45 ok ... anything else on hosting ? 15:24:09 I enabled ssl for gerrit.ovirt.org the other day 15:24:26 I'm not sure why it wasnt enabled 15:25:03 dcaro: this certificated is expired 15:25:14 knesenko: that might be it :) 15:25:25 dcaro: need to request a new one 15:25:59 dcaro: and it should be issued to gerrit.ovirt.org ... can you request it ? 15:26:35 knesenko: I think I even have a ticket on it 15:26:56 #action dcaro request a new certificate for gerrit.ovirt.org 15:27:15 Hi, is there a procedure to import an existing VG into ovirt-engine 3.3, i'm moving my hypervisors from ovirt-engine 3.1 15:27:44 the VG is created in ovirt-enginge 3.1 and is located an a san lun 15:27:50 martingo, we're currently in an infra ovirt meeting, can you hold you question another 30 min please? 15:28:01 shure 15:28:37 #topic Foreman and Puppet 15:28:56 dcaro: why do we have sudo rule for jenkins ALL = (root) 15:29:07 whynot to set it as ALL=(ALL) ? 15:29:26 it wont block us when we want to run commands as postgres user for example 15:29:49 obasan: you sent a patch for this right ? 15:30:10 knesenko, yes. but I still that it still doesn't work. this job is problematic 15:30:12 knesenko: no specific reason, I suppose that before when it was limited to a set of commands had sense, but now it does not 15:30:39 so I am +1 to change it to ALL=(ALL) 15:30:42 objections ? 15:31:24 o_O 15:31:38 Rydekull: want to join us ? 15:31:41 Well, quite a few ones without knowing the context why it is needed :-) 15:31:47 knesenko: Well, I just arrived 15:32:35 Rydekull: np 15:32:41 #chair Rydekull 15:32:41 Current chairs: Rydekull dcaro eedri knesenko obasan orc_orc 15:33:14 Hi fabiand 15:33:28 #action obasan send a patch to enable sudo for jenkins as ALL=(ALL) 15:34:03 So, I dont know the context for that rule. But any security implementation should work in the principle of least privilege 15:34:17 and ALL=(ALL) is quite the opposite of that :-) 15:34:38 now its ALL = (root) 15:35:00 and when trying to run as jenkins - sudo -u postgres cmd 15:35:02 it fails 15:35:17 Well, that's better then ALL=(ALL) even though it kinda works along the lines of security through obscurity 15:36:15 If you want jenkins to be able to run a command as user @ host, i'd define just that, host=(user) 15:36:18 why its better ? 15:36:44 Rydekull: you mean a specific rule ? 15:36:50 Cause it limits it to the root user (but since the root user has access, it gives access to everything) 15:37:18 Like Im telling you, I dont know the context. Im just arguing that ALL=(ALL) is bad practice security wise :-) 15:37:21 Rydekull: right .... so ALL = (root) 15:37:42 Rydekull: the context is executting jobs on the slave jenkins machines 15:37:55 lid, hey 15:38:16 Is it a good time to chat about stateless node? 15:38:23 I believe you can add more users to run as in sudoers, so you could just add root,postgres,etc on as needed basis 15:38:48 dcaro: as postgres? build hostgroup in sudo, add a rule for jenkins to that specific hostgroup and the user 15:38:51 postgres in this case 15:38:59 Seems dangerous to give jenkins root access 15:39:22 Rydekull: well, for other jobs we had to enable the root access, in that case is giving it also postres access 15:39:54 I'd revise those other jobs as another action point. 15:39:59 lid, sure - tho we could wait for the meeting to end .. 15:40:02 Rydekull: so I assume we need to add a group of a specific commands 15:40:20 But in this case I'd change "ALL" to a hostgroup and extend users from "root" to "root,postgres" 15:40:39 knesenko: well, it seems like a smart move to do :-) 15:43:01 #info start thinking to create sudo command groups for all users 15:43:13 dcaro: something else here ? 15:43:21 Revise sudo rules in general it seems like :-) 15:44:05 nothing else comes to mind 15:44:15 fabiand: sure, I 'll wait for the meeting to end 15:44:20 #topic Jenkins 15:44:25 ok what do we have here ? 15:44:29 obasan: ^^ 15:45:27 knesenko, we are trying to fix the dao tests 15:46:01 knesenko, it worked on the wrong user. we changed it and it still doesn't work. and we updated the puppet manifest to grant the jenkins user with the correct sudo permissions 15:46:08 #info knesenko review upgrade_params job 15:46:12 obasan: ok thanks 15:46:17 instead of that ? 15:48:14 #Other Business 15:48:48 obasan: wakey wakey 15:48:51 obasan: oh, sorry 15:49:12 knesenko: I think you missed #info in previous command :-) 15:49:21 Rydekull, partially awake :) 15:49:36 obasan: heh, it was a command going wrong, meant to message a friend ;-) 15:49:39 knesenko, I see "install to rackspace3" as one of your actions... did you sort out the issues? 15:50:19 dneary: hello ... yes we are 15:50:43 dneary: but we still have issues that are not related to us...keyboard doesn't works via VPN 15:51:06 dneary: so when we lost a connectivity to the host, its impossible for us to open a console and debug 15:51:15 dneary: that's a blocker for us right now 15:52:09 So still the idrac issue? 15:52:30 dneary: correct 15:52:42 How is the keyboard issue presenting itself? 15:52:52 tried using different versions of java/browers/.net etc? 15:53:25 Rydekull: the problem seems related to the machine installed os and console redirection from the iDRAC, tried different oses, javas, browsers... 15:54:12 Hrm 15:54:40 What os is the machine running? 15:54:45 and what kind of model is the machine? 15:55:14 Rydekull: is idrac related to OS ? 15:55:22 idrac issues 15:56:11 Shouldn't be affected by what OS you're running on the server. 15:57:13 is it iDRAC7? (Im assuming so) 15:57:26 Rydekull: fedora 19, let me check the details 15:59:29 ie 10 with activex ought to be working with iDRAC atleast 15:59:45 well, or java, but java could be a matter of having the correct version of java 16:00:03 Rydekull: the hardware is Dell R720, running iDRAC7 version 1.42.42 16:00:14 ok we are out of time ... thanks guys 16:00:18 #endmeeting