19:00:18 <davidlenwell> #startmeeting refstack
19:00:19 <openstack> Meeting started Mon Feb  9 19:00:18 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:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:22 <openstack> The meeting name has been set to 'refstack'
19:00:44 <catherineD2> o/
19:01:00 <hogepodge> o/
19:01:04 <markvoelker> o/
19:01:04 <vladiskuz> o/
19:01:17 <zehicle_> o/
19:01:30 <davidlenwell> Good day everyone!
19:01:50 <sslypushenko__> o/
19:02:05 <pvaneck> o/
19:02:31 <davidlenwell> okay .. lets get started..
19:03:01 <clee> o/
19:03:29 <davidlenwell> agenda: uuid, oslo api changes, beta onboarding, ui face to face, talk submission
19:04:09 <davidlenwell> #topic uuid
19:05:17 <davidlenwell> as most of you should know .. this spec.. https://review.openstack.org/#/c/144329/  has landed..
19:05:52 <davidlenwell> I'd like us to start work on this right away..
19:06:00 <hogepodge> I've started on the hacking rule. https://review.openstack.org/#/c/154127/
19:06:25 <davidlenwell> awesome!
19:07:00 <sslypushenko__> cool
19:07:24 <catherineD2> davidlenwell: we also need to consider the case where tests include parameters
19:07:29 <sslypushenko__> I can update my script with landed spec
19:07:36 <catherineD2> pvaneck: can give example ...
19:07:40 <hogepodge> It may not be able to land until uuids are already in place, but it's not terribly difficult code. Already have some good feedback from Matt. We're going to need to document that the decorators have to appear in a specific order, otherwise it becomes a testing nightmare
19:08:01 <davidlenwell> understood
19:08:16 <davidlenwell> sslypushenko__:  please do
19:08:49 <sslypushenko__> davidlenwell What is more importand thing autoupdate script or uuid ?
19:08:54 <catherineD2> sslypushenko__: does your script cover the test name with parameter cases?
19:08:58 <davidlenwell> uuid
19:09:22 <davidlenwell> I can work on the autoupdate script while you work on uuid
19:09:37 <sslypushenko__> catherineD2 Can you give an example, pls?
19:09:54 <sslypushenko__> davidlenwell greate!
19:10:54 <catherineD2> sslypushenko__: pvaneck: is getting the examples ...
19:11:09 <davidlenwell> okay.. lets move on to the next topic and circle back..
19:11:19 <davidlenwell> #topic  oslo api changes
19:11:27 <catherineD2> davidlenwell: can we wait one sec for the example
19:11:45 <sslypushenko__> sure
19:11:53 <davidlenwell> we'll wait
19:11:53 <catherineD2> it is important ... if UUID do not take care of these cases ... then we weill ahve duplicate UUID
19:13:06 <sslypushenko__> catherineD2 we can't manage this issue on the first interation
19:13:30 <catherineD2> sslypushenko__: then we will have duplicate uuid
19:13:53 <davidlenwell> I'd like to see the examples of this
19:13:54 <sslypushenko__> I know, I wrote about it in spec)
19:13:54 <pvaneck> yea, going to have to give me a  bit. y virtualenv is having issues
19:14:11 <pvaneck> i dont have a full test listing on hand
19:14:20 <davidlenwell> lets come back to it at the end
19:14:25 <davidlenwell> we have a lot more to cover
19:14:36 <davidlenwell> oslo api changes
19:14:36 <catherineD2> davidlenwell: agree let discuss later
19:15:25 <davidlenwell> catherineD2 raised some concerns in the review that we just merged.. I'dl like youguys to discuss it
19:16:23 <catherineD2> sslypushenko_vladiskuz: I do not see where to update the env DB authetication info ...
19:16:55 <vladiskuz> sql_connection is depricated now, but we can use 'connection' option in database section
19:17:24 <vladiskuz> it's the same thing
19:17:36 <sslypushenko__> I think it is just a renaming...
19:17:47 <catherineD2> vladiskuz: then we should update the readme ...
19:17:50 <pvaneck> tempest scenario test examples btw: http://pastebin.com/drxr0rBz
19:18:12 <sslypushenko__> catherineD2 Thx that you notice deprication message)
19:18:41 <catherineD2> sslypushenko__: I will test the installation and update the readme
19:19:14 <vladiskuz> catherineD2: It's already updated
19:19:21 <sslypushenko__> Thx for your testing work!
19:19:40 <vladiskuz> catherineD2: 'Note value of connection in database section should be corrected.' in refstack.md
19:20:18 <catherineD2> ok
19:20:29 <sslypushenko__> I guess we can solve this issue in review process. Lets return to uuids
19:20:41 <davidlenwell> okay
19:20:44 <catherineD2> ok
19:20:53 <davidlenwell> #topic uuid's
19:21:35 <sslypushenko__> I invetigate how this tests generates
19:21:52 <sslypushenko__> We can add uuid in generation spec
19:22:26 <sslypushenko__> as a required value
19:23:59 <sslypushenko__> But any way we should  add uuids to all other tests, firstly. Then we can resolve issue with these tests
19:24:29 <davidlenwell> I agree sslypushenko__
19:24:41 <sslypushenko__> It is good that there are no a lot of them)
19:25:18 <davidlenwell> okay . lets move on
19:25:23 <davidlenwell> #topic  beta onboarding
19:26:31 <davidlenwell> I'm still waiting to hear back from piston about their attempts to use the client.. I have an email into steve.
19:27:30 <davidlenwell> this week I am working on standing up a bluebox cluster to run the client against..
19:29:08 <davidlenwell> hogepodge: Can we reach out to a few more from your list?
19:29:34 <hogepodge> I don't see why not.
19:29:54 <hogepodge> Early results are showing that anyone using neutron is going to fail many tests, including defore core tests.
19:31:51 * clee can vouch for that
19:32:37 <davidlenwell> and this is from a short comming in those tests?
19:33:06 <hogepodge> CatherineD2 has documented this failure.
19:33:09 <clee> I haven't had a chance to investigate deeply, but simple things like "assign a floating IP" fail completely
19:33:23 <clee> even though that feature works properly in our clusters via neutron.
19:33:23 <hogepodge> There was an abandoned patch to address it, which she's been looking at bringing back.
19:33:33 <davidlenwell> ahh yes ..
19:33:35 <hogepodge> There's also a spec to address it and tempest accounts in general.
19:33:43 <catherineD2> clee:how about trying to assing floating IP manual?
19:33:49 <catherineD2> does that work?
19:33:52 <clee> catherineD2: like I said, that works fine
19:33:57 <clee> as long as you use the neutron client, and not the nova CLI
19:34:09 <hogepodge> It's my understanding that when this lands it will fix a number of problems. http://specs.openstack.org/openstack/qa-specs/specs/test-accounts-continued.html
19:34:10 <clee> (also works in Horizon)
19:34:18 <davidlenwell> makes sense
19:35:15 <davidlenwell> the test must be using the nova cli and isn't smart enough to pick up that it should use the neutron client
19:35:20 <hogepodge> #link http://specs.openstack.org/openstack/qa-specs/specs/test-accounts-continued.html
19:35:39 <catherineD2> hogepodge: I have asked Simeon in IBM to pick up that patch
19:36:01 <hogepodge> catherineD2 Fantastic. Thank you.
19:36:16 <catherineD2> It is a big job ...
19:36:17 <hogepodge> Can you loop him in with me on it too?
19:36:36 <hogepodge> yes :-/
19:37:27 <davidlenwell> okay .. I think this is going to require a lot more discussion and followthrough ..
19:37:35 <davidlenwell> lets make it a topic for our face to face
19:37:42 <davidlenwell> which is our next topic
19:39:13 <davidlenwell> #topic f2f
19:39:26 <davidlenwell> I've made an etherpad.. that remains empty
19:39:29 <davidlenwell> #link https://etherpad.openstack.org/p/refstack_f2f_feb_2015
19:39:44 <davidlenwell> we need to nail down a date and then decide on a location
19:41:51 <catherineD2> davidlenwell: what are the perspective dates and location? still in Silicon Valley?
19:42:20 <davidlenwell> catherineD2: yes ..
19:42:27 <davidlenwell> I can travel south again
19:43:45 <davidlenwell> how about next wednesday?
19:43:59 <davidlenwell> the 18th?
19:45:07 <catherineD2> 18th works for me ...
19:45:33 <davidlenwell> okay .. lets work on a location
19:46:41 <catherineD2> who else will attend?
19:47:04 <hogepodge> I'm on travel so will not make it.
19:47:24 <davidlenwell> okay
19:47:45 <davidlenwell> we'll make sure we plan some phone calls to include the larger group
19:48:00 <sslypushenko__> What time?
19:48:22 <davidlenwell> this should be sort of a high level discussion anyways.. since we'll be planning the next few months of development..
19:48:49 <davidlenwell> sslypushenko__:  we'll probably do an all day kind of thing.. starting at 11 am.. earlier than that is much harder to get through traffic.
19:49:21 <catherineD2> davidlenwell: Is that 18th or 15th?  the etherpad shows 18th ..
19:49:38 <davidlenwell> 18th.. the 15th is a sunday
19:49:53 <davidlenwell> sorry .. that was my typio
19:50:51 <sslypushenko__> 11am work for me. I can attend for 2-3 hours
19:51:04 <davidlenwell> awesome!
19:51:09 <catherineD2> sslypushenko__: that is great
19:51:09 <davidlenwell> I'll bring my webcam
19:52:49 <vladiskuz> probably I will attend too
19:52:58 <davidlenwell> okay .. finally topic talk submission
19:53:04 <davidlenwell> #topic talk submission
19:54:03 <davidlenwell> hogepodge:  and catherineD2 there was discussion about you two doing a talk together.. did you make that submission?
19:54:11 <hogepodge> Yes
19:54:22 <davidlenwell> what is the title?
19:54:37 <Rockyg> Sorry.  Calendar reminder fail.
19:55:31 <hogepodge> Testing Your Cloud: How to Configure your Cloud and Tempest
19:56:05 <catherineD2> Should we mention Defcore/Refstack in the titile?
19:56:37 <hogepodge> I'm also on a Defcore panel discussion. The DefCore Show: "is it core or not"  feud episode
19:56:54 <catherineD2> Like "How to Configure your Cloud and Tempest for Refstack test"
19:57:12 <davidlenwell> sounds like a fun panel
19:58:05 <davidlenwell> okay .. we're out of time here.. as always please feel free to continue the conversation in #refstack.. and ping me for attention of reviews.
19:58:24 <hogepodge> right now the submission focuses on configuring tempest, and refernences introp generally without regard to defcore or refstack
19:58:57 <davidlenwell> I think thats better.. its a broader topic ..
19:59:33 <davidlenwell> for use with the refstack client can be metioned..
20:00:04 <davidlenwell> lets end.. next meeting starts now
20:00:07 <davidlenwell> #endmeeting