19:00:40 <davidlenwell> #startmeeting refstack
19:00:40 <openstack> Meeting started Mon Jan 19 19:00:40 2015 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:43 <openstack> The meeting name has been set to 'refstack'
19:01:08 <vladiskuz_> o/
19:01:10 <pvaneck> o/
19:01:22 <catherineD2> o/
19:01:35 <davidlenwell> Hello everyone!
19:02:12 <pvaneck> hello!
19:02:38 <davidlenwell> So lets kick off..
19:03:01 <davidlenwell> mostly I want to drill through the action items we left off with from last weeks f2f.
19:03:12 <davidlenwell> #f2f Action items
19:03:20 <davidlenwell> #topic f2f action items
19:03:33 <davidlenwell> #link https://etherpad.openstack.org/p/refstack-january-2015-midcycle
19:03:39 <davidlenwell> I'll go first
19:04:08 <davidlenwell> I'm in contact with folks on the q/a team at piston.
19:04:10 <zehicle> o/
19:04:23 <davidlenwell> We need to work out a date to drop in their office and help them get a working config.
19:05:03 <davidlenwell> I had initially thought this friday would work.. but I had forgotten that I have to be in seattle at the end of this week. So I am going to email them back today and see about postponing it till next week.
19:05:24 <davidlenwell> Still waiting to hear back about who to bother at hp.. will stay on top of that.
19:05:56 <catherineD2> ic ... Pleae try to set that up on Friday (any)...
19:06:31 <davidlenwell> I believe chris is with the rest of the foundation team at their retriet .. so anything on my list that involved working with hogepodge will be delayed until he returns or checks in.. I hope he's snorkling and not checking his email.
19:07:12 <davidlenwell> refstack.org
19:07:14 <catherineD2> zehicle: Did the by-law pass?
19:07:25 <davidlenwell> we will get to that soon catherineD2
19:07:28 <davidlenwell> lets stay on topic
19:07:33 <davidlenwell> we're going to drill through this list
19:07:33 <catherineD2> davidlenwell sorry
19:08:03 <sslypushenko__> o/
19:08:30 <davidlenwell> So joshua doesn't have control over refstack.org .. he had registered it with the piston account .. I am waiting to hear back from them about getting it parked on a free dns service so that we can make adjustments ourselves.
19:09:10 <davidlenwell> I believe chris macgown is out today.. so I'll follow up with him on that and get it in our control as soon as possible.
19:09:48 <zehicle> catherineD2, yes
19:09:57 <davidlenwell> catherineD2: lets go through your list now.
19:10:03 <catherineD2> OK
19:11:01 <catherineD2> work with chris on tempest config guide --> on going should have first draft up in google doc this week
19:11:29 <davidlenwell> awesome!
19:11:36 <sslypushenko__> +1
19:11:41 <catherineD2> alpha test refstack client against new public api -- on going trying to pass more test and document the findings
19:12:38 <catherineD2> ook into putting cleanup scripts into tempest and get them involved --> open story and assign to Paul https://storyboard.openstack.org/#!/story/2000117 (https://storyboard.openstack.org/#%21/story/2000117)
19:13:04 <davidlenwell> cool
19:13:38 <davidlenwell> okay .. thats a good segway into paul...
19:13:44 <sslypushenko__> Is it should be part of refstack-client?
19:13:51 <davidlenwell> no sslypushenko__
19:13:57 <davidlenwell> it shouldn't be part of refstack at all
19:14:01 <catherineD2> maintain a list / google drive doc of tempest short commings --> on going should have google doc this week,   Add a comments on https://bugs.launchpad.net/tempest/+bug/1250866.  That refstack is working on the issue ...
19:14:08 <davidlenwell> tempest cleanup scripts belong in tempest
19:14:10 <sslypushenko__> Agreed
19:14:33 <davidlenwell> So part of this task was to get the tempest team involved in our work
19:14:42 <davidlenwell> and try to land the clean up scripts in tempest
19:14:53 <sslypushenko__> Biggest part
19:14:54 <catherineD2> davidlenwell: sslypushenko__: we start by prototyping and then work on commit to tempest later ..
19:14:57 <davidlenwell> that work has now been assigned to paul.. am I right pvaneck?
19:15:22 <pvaneck> davidlenwell: yep. it is a work in progress
19:15:32 <davidlenwell> thanks
19:15:44 <catherineD2> that is all for me on the f2f action items ...
19:16:01 <davidlenwell> lets move on to pvaneck
19:16:22 <davidlenwell> I am in the middle of reviewing your patch pvaneck but as of this morning it needs a rebase
19:16:27 <davidlenwell> not sure if you already pressed that button.
19:16:53 <pvaneck> yes, I will rebase it now since sergey's patch was just merged
19:17:05 <davidlenwell> awesome
19:17:15 <davidlenwell> once thats done I'll lay my feedback on it.
19:17:32 <davidlenwell> pvaneck:  I also want you to add to the api spec with what you did
19:17:43 <davidlenwell> so that its up to date
19:18:24 <pvaneck> okay, i will outline the new requests and urls
19:19:05 <davidlenwell> thanks
19:19:45 <davidlenwell> doesn't look like rocky is here.. so we can catch up with her on her stuff later on
19:20:15 <davidlenwell> #topic team changes decided on durring f2f
19:21:01 <davidlenwell> Catherine and I had a long and productive discussion about our need for better project managment.  Based on that we decided to nominate rockyg as our official team project manager.
19:21:26 <davidlenwell> Someone who is not a core reviewer who can help us maintain storyboard states and keep us on track.
19:21:51 <davidlenwell> her and I have agreed to get in sync this week and to transition into her being sort of a scrum master for the project.
19:22:32 <vladiskuz_> what about video from f2f meeting?
19:22:37 <zehicle> +1
19:22:38 <davidlenwell> additionally we had many long discussion for bringing on more core reviewers to the project.
19:22:53 <davidlenwell> vladiskuz_: we didn't end up recording a lot of it I am sorry about that.
19:22:57 <davidlenwell> well any of it..
19:22:58 <zehicle> vladiskuz, sorry, no video.  We tried but it was not productive
19:23:35 <davidlenwell> a week from today .. in next weeks meetings we will vote on core reviewers.
19:24:53 <davidlenwell> at this time I think 3 cores is the right number for the size of the team.. the requirments are that a candidate must have made meaningful contributions to our code base, has a clear understanding of the general architecture and has demonstrated strong reviewing skills.
19:25:16 <davidlenwell> with that in mind I'd like to nominate sslypushenko__ as a core reviewer.
19:25:21 <zehicle> +1
19:25:24 <vladiskuz_> +1
19:25:28 <catherineD2> ++1
19:25:30 <davidlenwell> again .. we'll vote on this next week
19:25:31 <pvaneck> +1 lol
19:25:42 <zehicle> FWIW, you mingled two items.  # of cores and a nomination
19:25:49 <davidlenwell> if anyone else would like to throw a hat in the ring
19:26:02 <davidlenwell> now is the time
19:26:12 <zehicle> I'd like to suggest the hogepodge also be a core reviewer
19:26:22 <davidlenwell> he hasn't made a single commit to our code base
19:26:49 <zehicle> ...thinking...
19:26:57 <davidlenwell> once he has I'd be more open to that idea
19:27:02 <zehicle> +1
19:27:14 <davidlenwell> we had that discussion face to face too
19:27:22 <davidlenwell> I don't think he has a problem with it.
19:27:30 <davidlenwell> not to speak for him or anything.
19:27:38 <zehicle> yes, and I'm concerned that we need someone from the foundation as a core as we try to get into the gate
19:27:53 <zehicle> but I'm OK w/ a wait and see
19:28:09 <davidlenwell> I'm not okay with letting someone be core who hasn't made any contributions
19:28:25 <davidlenwell> that is basically unheard of
19:28:52 <zehicle> davidlenwell, I'm good w/ the position
19:29:20 <davidlenwell> so next week we'll vote.. if anyone else wants to dive in just let us know.
19:29:27 <zehicle> can we just vote now?
19:29:46 <Rockyg> o/
19:29:56 <davidlenwell> I'd like more members to be present
19:30:13 <davidlenwell> I don't have a huge objection to it.
19:30:46 <zehicle> seems like we have quorum - next week will be less b/c of the product meeting
19:31:21 <davidlenwell> I don't think we have any objections to making sslypushenko__ core .. but I wanted to see if anyone else wanted to take a shot at it..
19:31:29 <zehicle> #agreed you must be a committer before you are considered for core status
19:32:25 <sslypushenko__> Thank you for your confidence)
19:32:38 <davidlenwell> you earned it sslypushenko__
19:33:04 <Rockyg> +1
19:33:21 <catherineD2> sslypushenko__: ++1 you earned it
19:33:37 <vladiskuz_> +1
19:33:53 <davidlenwell> sslypushenko__: you will have to have a short meeting with catherineD2 and I to discuss the rules.. but I think its safe to say you're in .. and I'll make the change today that ads you as a reviewer.
19:34:57 <sslypushenko__> Sounds great)
19:35:01 <catherineD2> sslypushenko__: Congratulation ...
19:35:32 <davidlenwell> okay .. thats a good segway to the next topic
19:35:37 <davidlenwell> #topic api api api
19:35:51 <sslypushenko__> catherineD2 Thank you!
19:36:06 <davidlenwell> sslypushenko__:  you have have noticed that we merged the api with db patch this morning.
19:36:19 <sslypushenko__> Sure, I did
19:36:38 <davidlenwell> I'd like to now have a discussion about what is next
19:36:54 <vladiskuz_> I making changes w/ oslo.db library
19:37:05 <davidlenwell> vladiskuz_:  I saw that wip.. good start
19:38:07 <sslypushenko__> I think we should land Vlad's and Paul's patch
19:38:28 <davidlenwell> is vlads no longer a wip?
19:38:28 <catherineD2> we also need https://storyboard.openstack.org/#!/story/2000118 so that vendor can stand up their own refstack server if they want to
19:38:40 <sslypushenko__> I'm planing to work on validation feature
19:39:08 <davidlenwell> sslypushenko__:  there is a package on pypi called Webster ..  check it out
19:39:13 <vladiskuz_> davidlenwell: It's need more tests
19:39:36 <davidlenwell> okay.. let me know when you think its ready for merge and I'll give it a deaper look.
19:40:08 <sslypushenko__> davidlenwell Thx, I watched on https://pypi.python.org/pypi/jsonschema
19:40:09 <vladiskuz_> ok, np
19:40:34 <davidlenwell> sslypushenko__: can you follow up on that storyboard?
19:40:38 <sslypushenko__> In any way, I will start from spec
19:40:47 <sslypushenko__> Sure.
19:40:48 <davidlenwell> make sure the readme us up to date.
19:41:06 <davidlenwell> thanks
19:41:35 <catherineD2> sslypushenko__: if we have something like setup_env for refstack (just like the one we have in refstack-client) that would be great ....
19:41:44 <davidlenwell> another thing we need to do is create a script that can detect a change in the repo and upgrade and redeploy the api server.
19:42:00 <davidlenwell> So that as we merge things .. it will cause the server to update itself.
19:42:19 <zehicle> davidlenwell, that would be great
19:42:32 <davidlenwell> I want to eliminate the manual steps around fixing things
19:42:42 <catherineD2> should we create those stories so we can track ..
19:42:56 <davidlenwell> I will create a story for this and assign an initial spike for writing a spec
19:42:59 <catherineD2> and know who is working on it ..
19:43:31 <davidlenwell> if nobody else has expierance with this kind of thing I can work on this one..
19:43:48 <davidlenwell> just the spec mind you
19:44:04 <davidlenwell> I will assign work items to others.
19:44:10 <Rockyg> This might be a good one for Chris.
19:44:25 <Rockyg> If DavidLenwell does the spec, chris can implement
19:44:37 <davidlenwell> perhaps.. we'll see if he's comfortable with that
19:44:38 <Rockyg> With help from othrs
19:45:03 <davidlenwell> we cannot speak for him while he's in the caribbean
19:45:10 <Rockyg> +1
19:45:18 <davidlenwell> and until the spec is defined it doesn't make sense to assign the work items
19:45:29 <davidlenwell> now that you are here Rockyg..
19:45:33 <davidlenwell> did you read the back scroll?
19:45:39 <Rockyg> Yup.
19:45:52 <Rockyg> Update on my stuff?
19:46:23 <davidlenwell> yes
19:46:34 <Rockyg> I need an estimate of how much time each of the devs on this project have to work on it per week.  It will help me estimate what we can get done in a sprint.
19:46:36 <davidlenwell> we need to schedule some time to talk about work flow
19:47:04 <davidlenwell> want to get lunch with me tomorrow?
19:47:06 <Rockyg> I believe DavidLenwell and I are only part time.
19:47:14 <Rockyg> But I don't know how much.
19:47:30 <Rockyg> I know Hogepoge is part time, but again, don't know how much
19:47:41 <davidlenwell> that will all work it self out
19:47:43 <Rockyg> Where are you going to be?
19:47:57 <davidlenwell> I can go down south...
19:48:06 <Rockyg> Cool.
19:48:14 <davidlenwell> lets coordinate offline
19:48:18 <Rockyg> Or we can meet part way, like in Fremont.
19:48:43 <davidlenwell> I need to be in san bruno in the late afternoon.. so the other side of the bay would be better
19:48:44 <Rockyg> K
19:49:06 <Rockyg> Redwood City?  That might be good.
19:49:12 <davidlenwell> okay
19:49:32 <davidlenwell> we have 10 minutes left.. lets have open discussion
19:49:38 <davidlenwell> #topic open discussion
19:49:43 <Rockyg> anyway,  we need to figure out how much can get done in two weeks' time so that we can have a target for the Summit.
19:50:13 <zehicle> it may be a good idea to be able to recruit beta sitesat the Product meeting next week
19:50:25 <Rockyg> +1
19:50:48 <davidlenwell> zehicle:  I think we have our beta list basically worked out .. if we onboard too many the first week we are going to cause our selves problems
19:51:02 <davidlenwell> I think its important to make sure we are taking bite sized steps to our goal
19:51:08 <Rockyg> I also would like to get a reference small HA stack install designed, including tempest.cfg for easy install/test/small site use.
19:51:19 <zehicle> +1 davidlenwell
19:51:34 <davidlenwell> right now we have three beta testers and what we would call alphas in ibm
19:51:44 <Rockyg> Then,, with tempst.cfg and refstack, they can validate their cloud install.
19:51:47 <davidlenwell> ibm making 4
19:51:51 <zehicle> let's see if we can build a pipeline and give them a time frame to start planning
19:51:59 <Rockyg> I figure it would be available maybe summit timeframe?
19:52:18 <catherineD2> here is the list from f2f for beta testing     Bluebox   DavidL      Piston      Chris McGowan      Dreamhost      HP             Monty      Mirantis      suse      Redhat      Canonic
19:52:19 <zehicle> vendors need to be ready to test a month ahead of summit
19:52:33 <Rockyg> Yeah.  I need to work with hogepose/foundation on questionaire/response team
19:52:40 <zehicle> kk, I just reached out the Dreamhost too
19:52:51 <davidlenwell> I think we'll have at least psiton and bluebox within the next few weeks.
19:52:57 <Rockyg> I think hogepose got mataclud last week.
19:53:20 <catherineD2> so right now David is responsible for contacting: HP, Piston, Bluebox
19:53:32 <davidlenwell> zehicle:  I think you are right for wanting to define the pipeline
19:53:36 <catherineD2> zehicle: for Dreamhost ..
19:54:02 <davidlenwell> my plan was to work f2f with pistons q/a team in the next week and use the expierance to help define a process for dealing with the rest.
19:54:19 <zehicle> ll
19:54:21 <zehicle> kk
19:54:28 <zehicle> I'm in SJC area most of next week
19:54:28 <Rockyg> Yeah.  I think we'll need some heavy handhoding on the setup.  so, only bring on one at a time.
19:54:38 <davidlenwell> well at first
19:54:43 <davidlenwell> we are going to learn a lot as we go
19:54:49 <davidlenwell> and document our expierances
19:54:55 <Rockyg> ++
19:54:57 <zehicle> anyone have a config that works against the default packstack?  pretty easy for me to run it in that
19:55:03 <davidlenwell> this will help us get better and it will help us to have some things to talk about
19:55:04 <zehicle> and even screencast a demo
19:55:35 <Rockyg> hogepose installed a cloud last week, but don't know which.  he's working to get the config working best
19:55:36 <davidlenwell> does anyone have spare cycles to work on zehicle's suggestion?
19:55:38 <zehicle> I just don't have the time to fight through getting the config right.  setting up OpenStack & running it is not a big deal
19:55:39 <davidlenwell> It hink its a good idea
19:56:04 <davidlenwell> if zehicle can get a cloud up and pass creds on to paul .. maybe we can get the tests running?
19:56:07 <zehicle> I'm willing to do a 1x1 via hangout to get it working
19:56:08 <davidlenwell> what do you guys think?
19:56:11 <catherineD2> davidlenwell: I will submiit a sample to refstack-client today
19:56:18 <davidlenwell> okay
19:56:21 <catherineD2> sample tempest.conf
19:56:26 <zehicle> easy for me to start w/ a basic packstack install
19:56:27 <davidlenwell> we are about out of time folks
19:56:39 <zehicle> moving to refstack
19:56:52 <davidlenwell> I want to make sure we are wrapped up on time because another team needs the room.. we can move the discussion to #refstack.
19:56:54 <catherineD2> zehicle: what is the impack to refstack with the election results?
19:57:08 <davidlenwell> Thank you all.. lets talk about that in channel
19:57:14 <Rockyg> see you there.
19:57:18 <catherineD2> ok
19:57:21 <davidlenwell> #endmeeting