17:03:09 #startmeeting 17:03:09 Meeting started Fri Sep 26 17:03:09 2014 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:03:16 #meetingname Cloud SIG 17:03:16 The meeting name has been set to 'cloud_sig' 17:03:29 #topic Roll Call 17:03:38 .hellomynameis imcleod 17:03:39 who's around for some cloudy goodness? 17:03:40 imcleod: imcleod 'Ian McLeod' 17:03:49 .hellomynameis jzb 17:03:50 jzb: jzb 'Joe Brockmeier' 17:04:09 .hellomynameis hguemar 17:04:11 number80: hguemar 'Haïkel Guémar' 17:04:19 .hellomynameis roshi 17:04:20 roshi: roshi 'Mike Ruckman' 17:05:10 alright then, let's get to stuff 17:05:18 #topic Previous Meeting followup 17:05:47 I see mattdm emailed the list about composition 17:05:53 where was that left? 17:06:22 .hellomynameis lalatendu 17:06:23 lalatenduM: lalatendu 'Lalatendu Mohanty' 17:06:31 with no follow-up at all from me 17:06:38 that's where 17:06:55 I had intended to post a proposed new slate 17:07:06 but.. stuff this week 17:07:22 roshi: ah, I thought you meant composing images or something :-) 17:07:32 dude - go get lunch :p 17:07:36 basically was going to draw from everyone active here, on the mailing list, or tickets 17:07:45 roshi: not yet, mattdm was busy with shellshock and the board :) 17:07:55 at least, he did his board homework ! 17:08:00 oh yeah, jzb - #communication fail ;) 17:08:10 really anyone can make that list 17:08:11 oh, carry on then :) 17:08:15 * number80 grade mattdm homework with A- 17:08:25 so I'd anyone wants to go ahead 17:08:25 .beefy mattdm 17:08:25 Have a Beefy Miracle, mattdm 17:08:28 * number80 minus because he didn't bring cake 17:08:38 number80: +1 17:08:40 alright then 17:08:48 otherwise I will 17:08:55 #action mattdm to follow up on list or tickets for WG Composition 17:08:56 Yeah, I think mattdm gets a pass on any missing homework this week due to Shellshocked 17:09:16 * jzb notes - security vulnerabilities are no longer allowed without catchy names. 17:09:16 yup 17:09:19 that's a fair point 17:09:29 and logo's, oddly enough 17:09:57 anything else on this? 17:10:30 if you help fix the bash bug, make sure you're on the list for this badge ;) https://fedorahosted.org/fedora-badges/ticket/308 17:10:47 define help fix? 17:11:00 * roshi tested and gave karma if that counts 17:11:25 oh, I wish I could clame that 17:11:28 er claim 17:11:28 roshi: it does. 17:11:32 * lalatenduM also tested and gave karma for f19 n f20 :) 17:11:53 All I did was tweet Ryan and Matt's stuff about it :-) 17:12:08 roshi: what's next? 17:12:33 looking for stuff that isn't in tickets already 17:12:49 you got feedback for the magazine article 17:12:56 did you get enough feedback jzb ? 17:13:22 roshi: I did. I also was out of time this week + bash bug 17:13:26 Stuff to review: * jzb start change page for F22 on cloud-init 17:13:26 * jzb move discussion on cloud-init to mailing list. 17:13:27 * mattdm connect with base wg, lsm5, docker, rel-eng about docker base image upload to registry 17:13:29 * jzb file RFE for zodbot on actions during meeting 17:13:31 yeah 17:13:40 I had some time updating and testing my systems 17:13:40 roshi: so I'll post it Monday, barring any further horrible vulnerabilities. 17:13:51 found all the systems I forgot I had running too (I think) 17:13:57 for sure 17:14:00 I have not gotten to cloud-init, either. 17:14:02 #shme 17:14:07 er, #shame 17:14:18 zodbot RFE? 17:15:02 * number80 thinks he should resume working on min-metadata-service 17:15:10 anybody else have a machine in the house they can't find, but still responds to ping? 17:15:15 roshi: I had that? 17:15:22 * jzb goes to look at minutes 17:15:23 oh, right 17:15:27 I'll do that now 17:15:30 i pasted them in here :) 17:15:47 mattdm, if you're still around: did you talk to base about the docker image upload? 17:16:07 roshi: The legend - http://www.theregister.co.uk/2001/04/12/missing_novell_server_discovered_after/ - netware server sealed behind drywall. 17:16:21 haha 17:16:43 it'd be nice if my FAS login persisted across Trac instances. 17:16:58 instead of logging into cloud, fedora-infrastructure, rel-eng separately 17:17:08 yeah 17:18:33 ok, onto the tickets 17:18:39 #topic Smoketests 17:18:44 #link https://fedorahosted.org/cloud/ticket/38 17:18:46 * jsmith shows up late for the meeting -- sorry 17:18:58 #addchair jsmith 17:19:16 #chair jzb jsmith number80 imcleod mattdm 17:19:16 Current chairs: imcleod jsmith jzb mattdm number80 roshi 17:19:34 didn't really get a chance to mess with this this week 17:19:54 I did however get access to some openstack, so once I figure out how to use the access I can start on some testing 17:20:09 agrimm: you have anything for this? 17:20:15 I noticed no unusual issues this week on openstack 17:20:37 * number80 dogfooding alpha at $DAYJOB on openstack 17:20:42 nice 17:21:01 I'll probably spend more time on atomic later 17:21:38 number80: rock 17:22:20 :) 17:22:31 I think we can move to the next ticket 17:22:38 ok 17:22:47 we already discussed #75 17:22:57 #topic Magazine article 17:23:25 * jsmith didn't do his homework and provide feedback 17:23:29 #info jzb to publish on Monday (2014-09-29) 17:23:38 roshi: will update ticket, thx 17:23:46 roshi: and I'll set it to closed Monday 17:23:47 sweet 17:24:01 #topic Atomic Testdays 17:24:12 #link https://fedorahosted.org/cloud/ticket/74 17:24:50 we decided on next week, I still need to get the Wiki page finished + promote 17:24:53 any help is welcome 17:25:09 it appears the NetworkManager testday is the 2nd 17:25:15 I am trying to get the image respun w/new bash 17:25:47 * number80 will take a look 17:25:56 https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day 17:26:04 it seems we need to do some testday updating 17:26:10 RDO isn't on the calendar 17:26:17 ah, OK 17:26:28 Sorry I am late (I am in a conference). 17:26:36 but it seems we'll have a couple testdays all going on at the same time 17:26:44 anybody want to take the action of updating the calendar? 17:26:45 that's not ideal 17:26:49 I will 17:26:51 roshi: well, different groups 17:26:58 #action roshi to update fedocal 17:27:05 I think we agreed that 1 & 2 October overlap w/RDO was good? 17:27:16 yeah, but in a perfect world we'd help them with their test days and vice versa 17:27:30 do we want to skip a week forward? 17:27:36 where is the docs for the RDO testday? 17:27:40 I'm happy to have a few more days to prepare. 17:27:43 roshi: just a sec 17:27:49 I'm fine with moving it 17:28:50 #info http://community.redhat.com/blog/2014/09/rdo-juno-test-day/ 17:29:04 #info https://openstack.redhat.com/RDO_test_day_Juno_milestone_3_test_cases 17:29:12 let's do a quick show of hands? 17:29:24 who's in favor of moving to the next week for Atomic test days? 17:29:41 o/ 17:30:01 \o 17:30:09 * number80 will be participating anyway to RDO test days 17:30:23 who's coordinating with the RDO folks? 17:30:30 o/ 17:30:34 jzb, I m in favor of moving it , not sure if that counts :) 17:30:53 lalatenduM: this isn't a binding vote, just a check on opinion. 17:30:59 roshi: I guess that'd be me. 17:31:24 well, we don't have quorum anyway and we're open by default ;) 17:31:32 also dustymabe but dustymabe doesn't seem to be around today 17:31:46 something something other obligations... :-) 17:32:48 proposed #agreed - Move atomic test day to 2014-10-08 and 2014-10-09 17:32:48 * oddshocks steps out 17:33:12 acks? 17:33:17 +1 17:33:33 +1 17:33:45 +1 17:33:48 * roshi is used to blocker review meetings and it's rituals 17:33:56 #agreed - Move atomic test day to 2014-10-08 and 2014-10-09 17:34:21 alright, I'll update the calendar and work with jzb on wiki and whatnot 17:34:37 should also probably write a magazine post for the atomic testday 17:34:41 woohoo 17:34:47 roshi, yup 17:34:49 #action roshi to write brief writeup about atomic testday 17:35:05 I think that's it for this ticket 17:35:07 roshi: if you want Fedora Magazine, I'll cover Project Atomic + atomic mailing lists 17:35:16 works for me :) 17:35:27 * roshi just has to get into the habit or writing more 17:35:35 and this is a good kick in the rear to do it 17:35:42 s/or/of 17:36:00 #action jzb to email lists and update Project Atomic 17:36:21 #topic .Next Website 17:36:25 #link https://fedorahosted.org/cloud/ticket/36 17:36:45 anything with this jzb ? 17:37:07 roshi: we're good on it for now, only leaving it open for beta + final updates. 17:37:12 staging instance is here: https://stg.fedoraproject.org/en/ 17:37:16 kk 17:37:32 #info site is good to go atm, will update with later releases 17:37:58 #topic Collaboration on cloud image updates 17:38:01 #link https://fedorahosted.org/cloud/ticket/51 17:38:15 I think this has been pretty much resolved 17:38:24 it went to the list iirc with no issues 17:39:12 great 17:40:29 can we close this? 17:40:35 is there anything else outstanding for it? 17:40:50 aiui, when we need a rebuild we just notify releng - right? 17:41:08 yup 17:41:14 roshi: uh, about that 17:41:20 uh oh 17:41:27 so I got several very pointed comments that "notify" 17:41:32 == opening a ticket 17:41:40 and not == emailing infrastructure@ 17:41:41 that's what I figured 17:41:41 apparently 17:41:43 so ... 17:41:57 let's have a process that details that w/what they want in said ticket? 17:42:10 do you want to update the ticket with that info, or the wiki? 17:42:29 I figure it's going to become a cloud sig process we should have documented somewhere 17:42:55 roshi: I haven't filed the ticket yet, not sure exactly which info is needed - whether "hey, we need this" is sufficient or if there's more info wanted. 17:42:57 which is exactly what you said :) 17:43:01 roshi: I got the replies a few hours ago 17:43:06 still have been buried in meetings 17:43:08 :-) 17:43:12 I know the feeling 17:43:30 someone to coordinate with releng to see what they'd need and document it on the wiki? 17:44:00 am I volunteering for this? 17:44:04 I guess I am. 17:44:14 action me if you have too much work :) 17:44:21 #action jzb coordinate with releng to see what they'd need and document it on the wiki? 17:44:28 number80: I would, but I need to do this today anyway 17:44:41 no problem 17:44:53 I have a delayed reaction since it's dinner time here :) 17:44:54 I was gonna say you or me jzb 17:44:58 .moarwork jzb 17:44:58 jzb here, have some more work 17:46:02 well, if you can't, I'm at 30 minutes away from a releng guy :) 17:46:39 sounds good 17:46:46 anything else for this ticket? 17:47:00 nope, I'll update it. 17:47:11 jzb: ping me or number80 if you want/need some help 17:47:31 #topic Test Plan 17:47:34 #link https://fedorahosted.org/cloud/ticket/61 17:48:07 I created a wiki space to discuss this almost 4 months ago to the day 17:48:38 I don't have anything new for this 17:48:47 but also don't know if anything else is needed 17:49:37 roshi: I dimly recall we were going to solicit input from testing 17:49:44 (QA) 17:49:50 I don't recall if that happened. 17:51:42 for what input though? 17:51:49 that's the bit I don't recall 17:52:01 I can always add it to the QA meeting on monday 17:52:06 1500 UTC iirc 17:52:13 whether it matches expectations of QA? 17:52:28 like whether it's a complete enough test plan, or if we're missing things? 17:52:59 I can probably get adamw to take a look at it, but it's pretty much the same as the other WGs 17:53:14 hmm? 17:53:41 questions on whether my test plan and test overview meet the expectations of QA 17:53:47 Overview here: https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/Test_Overview 17:55:23 * roshi thinks they do, but he's bias 17:55:30 * number80 shivers every time he hears "SCL" 17:56:22 * adamw reads 17:58:46 i don't have time the read the PRD right now, but basically, the test coverage should ensure that the cloud product as defined in it meets the overall quality expectations for fedora alpha/beta/final products 17:58:52 which...aren't as well documented as i'd like, but hey. 17:59:00 I can shore that up 17:59:17 "All of the "featured" images will need to be tested to ensure they meet the "mandatory requirements" defined in the PRD. " basically covers it 17:59:29 presuming this is a high-level 'statement of intent' not an actual test paln 17:59:46 when I wrote it, I asked for comments in several meetings but never got feedback so thought it must be good enough 17:59:49 which iirc it was (i know i invented the idea) 18:00:01 it's meant to be high level as you intended adamw 18:00:24 roshi: I have not given much input b/c it's so not my field of expertise 18:00:27 #action roshi to shore up overview specifics 18:00:33 I need to hop on a phone meeting now 18:00:43 I'll keep an eye on channel but may be distracted 18:00:43 #action everyone else to read his new version when he mails the list with it 18:00:46 roshi: basically seems fine to me then 18:00:48 np 18:00:52 we're at our time then 18:01:00 and I also have to depart 18:01:02 roshi: if you feel good w/it and people have had plenty of time 18:01:05 thanks adamw :) 18:01:08 roshi: then I'd go ahead and close it 18:01:13 adamw: thanks for the advice. 18:01:58 last item was project atomic - but I think we've already covered that with the test day 18:02:02 and jzb is out 18:02:04 sorry, all... had a lunch meeting today that ran late. 18:02:34 np agrimm 18:02:45 anybody have anything else, or can I endmeeting? 18:03:47 * roshi sets fuze 18:04:11 thanks for coming folks! 18:04:16 #endmeeting