16:00:10 <j^2> #startmeeting openstack-chef
16:00:13 <openstack> Meeting started Mon Jun  1 16:00:10 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:17 <openstack> The meeting name has been set to 'openstack_chef'
16:00:24 <j^2> hey everyone!
16:00:30 <j^2> this is the _correct_ time :D
16:00:41 <markvan> howdy
16:00:45 <j^2> we have a couple things on the agenda
16:01:04 <j^2> especially haveing a week in essance off last week
16:01:13 <sc`> hi
16:01:29 <j^2> please take a couple mins add any last min agenda items and we’ll start at 05 past the hour
16:01:38 <j^2> https://etherpad.openstack.org/p/openstack-chef-meeting-20150601
16:04:31 <j^2> nice, ok first topic:
16:04:54 <j^2> #topic sam and the update of c7?
16:05:30 <j^2> sc`: ^^
16:05:35 <sc`> i was able to converge aio-nova with some workarounds, namely removing ironic from the roles and changing the mariadb service name from 'mysql' to 'mariadb'
16:05:47 <sc`> workarounds are outlined in http://paste.openstack.org/show/253072/
16:06:42 <sc`> there have been efforts to move the packages' source of truth to mirror.centos.org from repos.fedorapeople, which can come in a later change once the packages pass gpg verification
16:07:24 <j^2> hmm, ok, is there anything we can help/do to move this forward?
16:07:25 <sc`> the biggest takeaway is that Ironic packages are still WIP
16:07:33 <j^2> man, Ironic AGAIN
16:07:45 * j^2 stares daggers at markvan
16:07:55 <j^2> i blame you
16:07:57 * markvan ouch...
16:08:39 <markvan> seems like ironic is low priprity for rdo, where as ubuntu and other had that done long ago...humm.
16:08:56 <j^2> lovely
16:09:04 <markvan> sc`: for the mariadb, is that a cookbok bug?
16:09:23 <sc`> markvan: yes it is. the package on c7 comes with 'mariadb.service'
16:09:36 <j^2> i think it’s a problem with the versions of the mysql cookbook we’re running
16:09:40 <j^2> we need up probably update
16:09:41 <j^2> it
16:09:49 <sc`> it's specifically the mariadb cookbook
16:09:56 <markvan> ah
16:10:33 <sc`> will need to do some upstream work on that one
16:10:58 <j^2> can you put a small todo list about the fix for it?
16:11:04 <j^2> if we can track it we could probably make it happ
16:11:05 <j^2> en
16:11:09 <j^2> i cant seem to type today
16:11:12 <sc`> sure
16:11:32 <j^2> thanks, just drop it in the agenda so i can move it to the next to track the steps
16:11:43 <j^2> #topic markvan and the trials of ubuntu
16:12:05 <j^2> the most important question off of all of this: Does this mean we need to start looking at 15.04? if there is no plan to back port to trusty?
16:12:08 <markvan> Looks like that bug is in the trusty repo now, running a verify test now
16:12:24 <markvan> hopefully this is the end of that saga.
16:12:28 <alanmeadows> I had just gotten my head completely around 14.04 :/
16:13:04 <j^2> markvan: nice
16:13:10 <j^2> so progress is progress right?
16:13:17 <markvan> yup
16:13:47 <j^2> so we’ll wait on the validation, then we’ll circle back on this?
16:14:08 <markvan> yup, I'll post up when verified
16:14:13 <j^2> #topic sc` and fauxhai
16:15:25 <sc`> fauxhai is still at 2.3.0 on rubygems.org. still need to get a new gem released for the rhel7 update
16:15:31 <j^2> grr
16:16:03 <j^2> I can try to pull some strings to get fauxhai updated, let me see what resources i can leverage
16:16:35 <markvan> Yeah, this hack is ugly: https://github.com/stackforge/cookbook-openstack-common/blob/master/bootstrap.sh#L13   j^2 can we maybe push form ChefDK side?   Is mean ChefDK lacks suppport for rhel 7 without this hack
16:16:56 <j^2> will do
16:17:07 <j^2> added it to the Action items on the agenda
16:17:23 <j^2> #topic jklare Eastern Hemi update
16:18:18 <j^2> jklare: around?
16:18:54 <markvan> have not heard from kingkong today...(as I try to get his new kick to stick...
16:19:01 <j^2> hahah i like it
16:19:41 <markvan> We have the CI patch proposed for  a new gate here: https://review.openstack.org/#/c/186379/   Please review if you have not already,t hx
16:20:07 <j^2> markvan: bad, we have an agenda, you shouldnt drop things in like that
16:20:17 <j^2> still great work though
16:20:37 <markvan> just trying to fill jklare gap about where CI is
16:20:59 <j^2> heh
16:21:02 <j^2> ok, next topic
16:21:18 <j^2> #topic core reviewer
16:21:37 <alanmeadows> j^2, when you get a chance, give a final yay or nay to MAINTAINERS.md, and I'll make it so across the field with the README updates
16:21:47 <j^2> yay
16:21:48 <j^2> wait
16:21:50 <j^2> no
16:21:53 <alanmeadows> heh
16:22:04 <j^2> yeah i’ll take the action item for it
16:22:27 <alanmeadows> This is the guinea pig: https://review.openstack.org/185113
16:22:35 <j^2> perfect,’ i was just about to ask that
16:22:59 <j^2> i’ll give this topic a few more mins
16:23:16 <j^2> we have our maintainers and we’ll leverage the review for new cores
16:23:33 <j^2> this actaully brings up something that showed up in openstack-infra the other day
16:23:41 <j^2> i’d like to mention this while we have everyone here
16:25:01 <j^2> so as Cores we are the leaders of our project, make sure you acknowalge this, the PTL is only an administrator and there to step in when the community is at a standstill. So as we start growing our project now please keep this in mind as we start recruiting more people
16:25:27 <j^2> and as alanmeadows says, the PTL is only a hub of information
16:25:55 <markvan> agree
16:26:15 <j^2> as we are now santioned i can imagine our community is going to have some growth, if not sudden steady and we’re gonna be bigger than we are used to
16:26:25 * j^2 gets off his soap box
16:26:58 <j^2> any thoughts objections questions?
16:27:25 <sc`> seems sensible to me
16:27:27 <markvan> something for cores to discuss, schedules for our project?  (bp deadlines and such...)
16:27:46 <markvan> or are they first proposed by ptl
16:28:09 <j^2> i think there isn’t an offical way to decide, it’s a perproject thing
16:28:25 <j^2> especially if your interdependant on the other projects
16:28:33 <markvan> ok, I'll add something to agenda for next meeting to discuss
16:28:40 <j^2> souds good
16:29:44 <j^2> ok, so this topic dove tails into our another topic
16:29:55 <j^2> #topic stackforge -> openstack
16:30:03 <j^2> so I’ve put in:
16:30:11 <j^2> #link https://review.openstack.org/#/c/186532/
16:30:36 <j^2> this should be the final step we need to get moved
16:30:46 <j^2> but it requires downtime with infra
16:31:13 <j^2> i have us on the agenda for the next meeting which is tomorrow
16:31:46 <j^2> we should be set to get put on the next down time, but if we can make the meeting and make sure there are no hang ups it would help:
16:31:47 <markvan> yup, also will have a small ripple effect on our tools/doc
16:31:59 <j^2> https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames
16:32:35 <j^2> any thoughts objections questions?
16:33:21 <markvan> I can't think of any timing issues with doing that now vs later, but that would be my only concern
16:33:49 <markvan> And does that mean that we could not be also part of the supermarket?
16:33:59 <alanmeadows> good question
16:34:35 <j^2> i don’t think so
16:34:41 <j^2> we still don’t own the repo
16:35:03 <j^2> though, I’ve been tasked with creating a “simple compute cookbook” that we can publish to supermarket leveraging our cookbooks
16:35:10 <j^2> and it’ll be in chef-partners
16:35:22 <j^2> assuming i ever get time to code again, i’ll be making that asap
16:35:32 <markvan> ok
16:35:37 <j^2> think of a “simpler version of the testing-stack"
16:36:08 <j^2> no cinder or ironic or anything, just the bare minimum
16:36:43 <j^2> next topic?
16:37:14 <j^2> #topic client cookbook
16:37:32 <j^2> so i need to spend some time working on the client cookbook
16:38:03 <j^2> i’d like to send out a doodle to find some time for everyone to do a hacksession
16:38:08 <j^2> would anyone be interested?
16:38:23 <markvan> Im in
16:38:27 <j^2> awesome
16:38:44 <j^2> i’ll send out the doodle to the ML
16:38:56 <alanmeadows> although even so, the move is still worth it but I was also curious about that
16:40:08 <j^2> #topic kilo bugs and BPs
16:40:12 <j^2> markvan: thoughts ^^
16:40:29 <j^2> or do you want to set up a deicated time for it?
16:40:56 <markvan> was just wondering if we are at the point to think about a date for the stable/kilo branch
16:41:25 <markvan> we can certainly do a bug/bp walk thru to make sure we have agreement on what's left.
16:41:58 <j^2> i thought we took the lions share down at summit?
16:42:24 <markvan> yup, just trying to followup and wind this down to zero
16:42:30 <j^2> ah sounds good
16:43:39 <j^2> ok, i’ll let the last 20ish mins open discussion?
16:43:44 <j^2> #topic open discussion
16:44:01 <j^2> the floor is anyones
16:45:03 <markvan> yeah, looks like the ubuntu bug is in trusty cloud archive: libvirt-bin                         1.2.12-0ubuntu13~cloud0   yeah!
16:45:13 <j^2> !!!
16:45:14 <openstack> j^2: Error: "!!" is not a valid command.
16:45:15 <j^2> link?
16:45:23 <alanmeadows> a quick one: I think with the move/rename in progress, it makes sense to introduce a designate cookbook post-rename?
16:45:30 <markvan> j^2: http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/trusty-updates/kilo/main/binary-amd64/Packages
16:45:50 <j^2> alanmeadows: seems reasonable
16:46:00 <alanmeadows> to be sure, a "dnsaas" cookbook
16:46:34 <j^2> yeah the std is cookbook-openstack-<something>
16:46:44 <j^2> i guess dnsaas could work
16:47:05 <sc`> the centos cloud sig has packages up at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-kilo/ but i've found that not all packages are signed by the standard centos package key
16:47:31 <sc`> there also exists packages for juno on c6
16:50:08 <j^2> lovely
16:51:34 <sc`> the packages for c6 may be incomplete. once it stabilizes and gpg checks out, might be worth switching the common cookbook over to using those repos instead of repos.fp.o
16:53:38 <markvan> and just a possible TODO, I don't see us listed on this wiki page, but not sure how this is generated, might be from openstack projects, not stackforge: https://wiki.openstack.org/wiki/New_home
16:57:23 <j^2> cool, i think we’re done for today, thanks everyone
16:57:28 <j^2> #endmeeting