15:31:53 <j^2> #startmeeting Openstack-Chef
15:31:54 <openstack> Meeting started Thu Feb  5 15:31:53 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:31:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:31:57 <openstack> The meeting name has been set to 'openstack_chef'
15:32:04 <j^2> hey everyone
15:32:30 <j^2> so i only have one thing that a community member wanted to bring up so i’ll open it up to the floor
15:32:36 <j^2> #topic General Discussion
15:34:08 <j^2> anyone?
15:34:11 <j^2> http://www.youtube.com/watch?v=f4zyjLyBp64
15:34:42 <krtyyy> What's the status of ceph changes?
15:34:49 <cmluciano> I have a fairly noob question about getting started
15:34:49 <j^2> great question
15:35:02 <j^2> libsysguy: can you talk about ceph?
15:35:10 <j^2> cmluciano: yeah we’ll jump on that in a sec
15:35:27 <j^2> the ceph issue dovetails into what i wanted to talk about too
15:35:50 <j^2> the ceph change has broken some downstream testing: http://logs.openstack.org/01/152001/2/check/gate-cookbook-openstack-image-chef-unit/e91d2c5/console.html
15:36:52 <j^2> one way around it: https://review.openstack.org/#/c/152001/3/spec/api_spec.rb
15:37:18 <j^2> cmluciano: what’s your question?
15:39:01 <cmluciano> We woudl like to get started with openstack and are wondering what the easiest path is. we mostly want to bring new nodes so I imagine most of our interest is in the compute layer. So mainly is there a huge difference between RDO and Openstack’s releases. And also how does openstack-chef fit into the mix
15:39:23 <j^2> cmluciano: ah cool
15:39:40 <j^2> ok yeah so that’s where our testing-stack comes into play and the Ref Archs i’m trynig to write
15:39:41 <libsysguy> hey j^2
15:39:45 <libsysguy> sorry, had people in the office
15:39:51 <j^2> suuuurrreee
15:39:52 <libsysguy> Ceph work is all pushed
15:40:37 <libsysguy> so it just needs +2's
15:41:27 <j^2> cmluciano: basicly, openstack-chef is leveraging the RDO yum repos to build it out via chef. We leverage different Ubuntu repos, i’m blanking on the repo atm. We try to stay as close as we can to the packages releases, and we’ve had some work on creating git pulls on trunk to, but those projects haven’t really gone anywhere
15:41:58 <j^2> cmluciano: do you want neutron? or are you going nova?
15:42:04 <j^2> libsysguy: ah ok
15:42:55 <j^2> krtyyy: is it breaking things still for you?
15:43:03 <j^2> the ceph changes that is
15:43:17 <cmluciano> j^2: Unsure ATM. We’ve just started diggin in, so I have not grokked all of the names and pieces
15:43:31 <krtyyy> Yup, but only for 2 of them. I can hold off on putting 'skip' in if the changes are just around the corner.
15:44:02 <cmluciano> I guess first step is to get an instance up and running, play around with provisioning machiens with knife openstack, and then really start to build out
15:44:35 <j^2> krtyyy: it sounds like its not going to be, if it’s pushed skips are have to gonna be used
15:44:51 <j^2> cmluciano: ok, yeah the testing-stack is where you want to start
15:44:59 <cmluciano> This one https://github.com/jjasghar/chef-openstack-testing-stack
15:45:10 <j^2> the chef-repo is only really up-to date through havana
15:45:12 <krtyyy> fair 'nuff. I'll go ahead and get to skipping.
15:45:20 <j^2> cmluciano: yep
15:45:46 <j^2> it’ll be in stackforge as soon as i get some patches in from some community memembers to help provision baremetal
15:45:48 <cmluciano> Cool, and I should be able to stand this up in a VM somewhere and have people access it from the get-go right?
15:46:01 <j^2> cmluciano: yep
15:46:36 <cmluciano> Cool. And you mentioned that most things pull from the RDO repos? Are they different than the source openstack?
15:46:43 <j^2> and if you find issues please report them asap
15:46:59 <j^2> they create the rpms for everyone yeah
15:47:01 <cmluciano> I didnt know if there was “openstack” and then everyone has their own flavor
15:47:10 <cmluciano> Ohhhhh ok that makes sense
15:47:12 <j^2> own flavor
15:47:28 <j^2> hell technically speaking just a swift cluster is considered an openstack cloud
15:47:40 <j^2> there is no requirement to have nova/compute even be a part of it
15:47:57 <j^2> its one of the things that confuses people just getting into the life
15:48:07 <j^2> yes, i use life there for a reason :P
15:48:25 <cmluciano> Cool
15:50:35 <j^2> libsysguy: got anything you want to talk about?
15:50:46 <j^2> markvan: anything you’d like to bring up to the group?
15:51:55 <markvan> nothing new...just need everyone help with reviews
15:52:27 <j^2> ah your trusty updates need to be pushed
15:52:36 <j^2> you have a couple -1’s there
15:52:56 <j^2> and krtyyy i’ll try to look at yours today too
15:53:14 <markvan> yup, those are waiting for the ceph ones, there are a couple in that boat, but I see libsysguy has made good progress today
15:54:36 <markvan> btw, my swift patch https://review.openstack.org/#/c/151002/ has gotton rather large, but there's still more work to do.  So, I will create a followup patch to address remaining issues I found.  (not sure if anybody cares much about swift right now...)
15:55:39 <krtyyy> I'm slighted confused. Just to confirm... I *should* go ahead and add the 'skip's to my two -1 reviews? Or are the ceph changes going to make that unnecessary?
15:56:47 <markvan> krtyyy: no I don't like skips, lets instead focus on getting the ceph ones in and then just rebase ours and moveforward.
15:57:07 <krtyyy> Wilco
15:57:26 <markvan> krtyyy: btw nice job on working that discussion forthe endpoints!
15:57:40 <j^2> markvan: wait, so now i’m confused
15:57:51 <j^2> i thought all the ceph changes where punted. libsysguy
15:57:56 <krtyyy> (blush) Shucks. Tip o' the hat the Sachi for finding the issue.
15:58:12 * libsysguy reads back
15:58:29 <j^2> and i’m ok with skips; they kept the test around for a later date
15:58:35 <markvan> j^2: these two look ready to go: https://review.openstack.org/#/q/owner:%22Elliott+Davis%22+status:open,n,z
15:58:56 <libsysguy> yup those are my last two for Juno
15:59:02 <j^2> kk
15:59:04 <j^2> looknig now
15:59:43 <markvan> libsysguy: u get the ceph crown, nice and shiny
15:59:56 <libsysguy> YAYY!!
16:00:13 <libsysguy> I thought the way I dealt with ceph was very elegant :p
16:00:27 <j^2> heh
16:01:10 <markvan> libsysguy: anytime you want to do the same for swift, let me know....
16:02:07 * libsysguy ducks for cover
16:02:17 <libsysguy> Ceph makes sense to me…swift does not :p
16:05:08 <j^2> cool anything else pressing?
16:07:00 <j^2> on Monday we should take a moment to sync up Marks list with what needs to get done?
16:07:05 <j^2> any objcetions?
16:07:25 <markvan> Yup, I will update the ML with latest status over the weekend....  good progress here!
16:10:14 <j^2> :D
16:10:39 <j^2> i’d like to just mention that i love how our communinity is growing
16:11:14 <j^2> if you have people that would benifit to being more involed please don’t hesitate to speak up or ping me directly jj@chef.io
16:11:55 <j^2> with the stable/juno cut then moving to kilo, we can get this little corner humming along to be the go to way to run openstack :)
16:13:28 <markvan> FYI anyone in the Minn area: http://openstack.meetup.com/cities/us/mn/minneapolis/
16:14:01 <markvan> bunch from ibm rochester are heading to twin cites for this meetup....
16:14:02 <krtyyy> I'm looking forward to helping out. We're seeing some things that we'd like to tweak that might be useful to other folks as well.  ;-)
16:14:20 <sc`> I'm running icehouse, but already looking at juno and farther
16:14:56 <krtyyy> I need to sign off and start peddling to work. Thanks for the guidance!
16:14:59 <markvan> krtyyy: yup, we're getting better with our blueprint/spec process, but it still needs some work...
16:15:09 <sc`> gots to be cognizant of what all is happening in the community if I intend to be a consumer of stackforge resources
16:15:41 <j^2> awesome! thanks everyone
16:15:43 <j^2> #endmeeting