Monday, 2015-12-28

*** esker has joined #refstack00:53
*** markvoelker has quit IRC01:01
*** esker has quit IRC02:04
*** esker has joined #refstack02:06
*** esker has quit IRC02:06
*** esker has joined #refstack02:06
*** esker has quit IRC02:29
*** markvoelker has joined #refstack02:47
*** markvoelker has quit IRC02:51
*** coolsvap|away is now known as coolsvap03:15
*** esker has joined #refstack03:29
*** esker has quit IRC03:35
*** markvoelker has joined #refstack03:48
*** markvoelker has quit IRC03:52
*** esker has joined #refstack03:58
*** esker has quit IRC04:23
*** esker has joined #refstack04:46
*** markvoelker has joined #refstack04:49
*** markvoelker has quit IRC04:53
*** esker has quit IRC04:57
*** esker has joined #refstack05:23
*** esker has quit IRC05:28
*** markvoelker has joined #refstack05:49
*** markvoelker has quit IRC05:54
*** cody-somerville has joined #refstack06:49
*** cody-somerville has quit IRC06:49
*** cody-somerville has joined #refstack06:49
*** markvoelker has joined #refstack06:50
*** markvoelker has quit IRC06:55
*** esker has joined #refstack07:27
*** esker has quit IRC07:32
*** markvoelker has joined #refstack08:51
*** markvoelker has quit IRC08:55
*** markvoelker has joined #refstack10:52
*** markvoelker has quit IRC10:57
*** esker has joined #refstack11:31
*** esker has quit IRC11:36
*** markvoelker has joined #refstack12:52
*** openstackgerrit has quit IRC12:53
*** markvoelker has quit IRC12:57
*** openstackgerrit has joined #refstack13:05
*** esker has joined #refstack13:35
*** esker has quit IRC13:40
*** markvoelker has joined #refstack13:53
*** esker has joined #refstack13:54
*** markvoelker has quit IRC13:58
*** esker has quit IRC13:59
*** coolsvap is now known as coolsvap|away14:37
*** markvoelker has joined #refstack14:54
*** markvoelker has quit IRC14:59
*** esker has joined #refstack15:41
*** esker has quit IRC15:46
*** esker has joined #refstack16:42
*** esker has quit IRC16:47
*** markvoelker has joined #refstack16:55
*** markvoelker has quit IRC16:59
*** esker has joined #refstack17:43
*** esker has quit IRC17:49
*** alevine has joined #refstack18:41
*** catherineD has quit IRC18:50
*** catherine_d|1 has joined #refstack18:51
*** sslypushenko has joined #refstack19:06
*** esker has joined #refstack19:22
*** edmondsw has joined #refstack19:22
*** edmondsw has quit IRC19:22
*** esker has quit IRC19:27
catherine_d|1hello20:00
alevineWe do have the prototype right now. It's just a replica of the RefStack. So we can bring it closer to current reqs and then take a look at it together.20:00
alevineHi :)20:00
sslypushenkoalevine: Actually, I have one more question for you20:00
alevinesure20:00
sslypushenkoHow do you plan using RefStack?20:01
sslypushenkoWhat kind of value it brings to your side20:01
alevineIt's in my doc. Our requirements are in there. And my Enhancement document (previous one) listed them explicitly20:01
alevineOf course I was thinking about our needs all the time  as well :)20:01
alevineIn short - we want to be able to validate various OpenStack reference architectures.20:02
alevineNot just the DefCore one but any other else. Meaning, that it should be defined first (new Guidelines) and then validated.20:02
sslypushenkoWhat do you mean under validation?20:03
alevineI mean certification like DefCore does with OpenStack giving the OpenStack logo, but in other Guidelines cases it'll be other badges.20:03
alevineTesting.20:03
sslypushenkoIn Mirantis we also have kind project for cloud validation, but that team found RefStack is suitable for validation purpose20:04
alevineTesting against some predefined set of Tempest tests with external plugins.20:04
alevineRefStack can be suitable if implements all I listed in the reqs :)20:04
sslypushenkoyeap20:04
catherine_d|1+120:04
catherine_d|1that is why I am so eagre to engage alevine: 's team on RefStack20:05
catherine_d|1but I want to do it systematically with DefCore on our side20:05
sslypushenkoIt will be cool to do it at the same time. I wish to have more time to spend it on RefStack)20:07
catherine_d|1alevine: could you share this doc so that sslypushenko: can see all our comments/discussion https://docs.google.com/document/d/1s_dAIuluztlCC6AZ-WO4_FR2CLje1QyS6kbMxlFHaMk/edit#heading=h.8fxpb1onf6vr20:07
alevineThat's why we need to agree with DefCore the requirements and after that we're done with them - we can just think about implementation.20:07
sslypushenkoI meant sync with Defcore and alevine's prototype adoption20:07
catherine_d|1sslypushenko: i am so thankful that you keep working iwth us20:08
sslypushenkocatherine_d|1: np) Hanging out with you, guys means a lot to me)20:08
alevineSergey can see everything. We've resolved it, that's why it disappeared. But if he clicks on Comments he'll see.20:09
catherine_d|1sslypushenko: once  alevine: share that link with you .... please log in and then click on "comments" on the upper right hand side ... you will see our discusssion ...20:09
alevineI can share the previous version. Hold on.20:09
sslypushenkoalevine: Yeap I don't have issues with access to doc20:09
alevinehttps://docs.google.com/document/d/1GeLL7XHT2VnuO40lmR-tHLuaomNExWZCza4iFb8VODI/edit20:10
alevineBut I'm not sure Sergey wants to read ALL of that. :)20:10
catherine_d|1sslypushenko: so we did put a lot of time to dscuss so I think the requirement is a great doc as a blue print for us to implement we just need to prioritize ...20:10
catherine_d|1sslypushenko: or maybe only check whether alevine: and I have had any discussion on the areas that you DISAGREE20:11
sslypushenkoalevine: Hmmm.... something went wrong, Now I have only view acces20:11
alevineBecause that's Refstack Requirements History. Another doc. First draft.20:12
alevineI don't think you want to comment something right there. Better go into the new clean doc.20:12
sslypushenkoI don't see any comments20:13
sslypushenkoThat is why we like gerrit)20:13
alevineYou don't? Weird. Hold on.20:13
sslypushenkoAt minimum, it is predictable)20:14
alevineHow about now?20:15
alevineGoogle docs are quite predictable I assure you.20:15
alevineI shared the second doc with you.20:15
sslypushenkogot it20:15
alevineHow do you propose to comfortably work with text docs in gerrit I wonder? How about tables of contents, heading fonts, pictures and other stuff?20:16
catherine_d|1sslypushenko: that is great20:16
sslypushenkoalevine: Lets keep things as it is)20:17
sslypushenkoWe definitely will move to gerrit, but later20:17
alevineNo, seriously. It's rather important. Maybe I don't understand something. How do you comfortably present all of the information in this docs in gerrit?20:18
catherine_d|1alevine: the biggest problem I have by using google doc is ownership of the doc .20:18
alevinecatherine: What do you mean?20:18
sslypushenkoalevine: We can put in rst books as complicated content as we want20:19
catherine_d|1using google doc the individual is the owner ... you can delete the doc that you share .. I can delete the data modle that I hsare20:19
sslypushenkoeven pictures and schemas20:19
catherine_d|1but in gerrit ...everything is owned by OpenStack20:19
alevinesslypushenko: How easy is it? Can I do this with such a doc in two days as I did with mine?20:19
sslypushenkobut it takes time20:19
alevinesslypushenko: Do you have any example?20:19
alevinesslypushenko: Seriously, maybe that's why some tasks take too long. We shouldn't be handicapped by our instruments, you know.20:20
alevineInstruments should help us not stop us.20:20
sslypushenkoalevine: yeap) all content on developer.openstack.org is generated from rst20:20
sslypushenkobut google docs are good for the time being20:21
sslypushenkoActually we have one more option here - openstack wiki20:21
alevineGuys, as soon as we agree upon everything OpenStack can have it all. But the work should be done somewhere where it can be done efficiently, that's my opinion.20:21
sslypushenkobut lets stick to googe gocs20:21
alevine:) good suggestion20:22
catherine_d|1alevine: agree that is why I have no objective using google doc now ,..20:22
sslypushenkowhite it is working for all of us)20:22
sslypushenko*while20:22
catherine_d|1but once agree we will convert to wiki or spec20:22
alevineAbsolutely.20:22
catherine_d|1yup20:22
alevineThat's written in my doc exactly20:22
catherine_d|1yup ... that is exactly while I put up a datamodel presentation  for discussion ,,, I will follow up with a spect for formal approval20:23
catherine_d|1alevine: I think you reuqiement is so long that it make more sesne in wiki ... but we can talk about that later20:24
sslypushenkoalevine: One more technical question, about your proto20:24
catherine_d|1anyting else?  I know it is late for your time zone20:24
alevinesure20:25
sslypushenkoIs docker script working for your fork?20:25
sslypushenkoI did not have a chance to try20:25
alevineWhat do you mean by docker script?20:25
sslypushenkoI meant run-in-docker20:26
alevineIt's a brought up website. We did have another one brought up as well so it's two now.20:26
sslypushenkoI meant run-in-docker script20:26
alevineWe didn't do anything about docker. It's in Amazon instance. So we copy it if we want.20:26
sslypushenkono no) It just for testing on local setup20:27
alevineNo docker. We didn't need to.20:27
sslypushenkoIt would be helpful if it is working)20:27
alevineAndrey Pavlov, my teammate, developed it locally and then just brought it up in AWS.20:27
sslypushenkothen anyone can just pull repo, run run-in-docker script and get working prototype locally20:28
alevineWell, we can think about it but we don't have it now and both of us are out for vacation till January 10.20:28
sslypushenkoit is how things work now20:28
sslypushenkoalevine: sure, no pressure)20:29
sslypushenkoYou can mail me, if you have some questions20:29
alevineAbout docker? When we are ready we'll ask. Or see if someone more familiar can do the thing.20:30
sslypushenkoJust mail me, lets see what we can do20:31
sslypushenkoI actually hope, that almost everything should works fine20:31
alevinePerfect :)20:32
catherine_d|1great .. I am taking off ... If we do not talk again ... Have a very Happy Holidays and New Year!!!  Thank you very much for contributing to RefStack!!!20:32
sslypushenkocatherine_d|1: you too)20:33
alevineyou too20:33
alevinebye20:33
sslypushenkobye20:33
*** alevine has left #refstack20:33
catherine_d|1see you next year :-)20:33
*** catherine_d|1 has quit IRC20:33
*** catherineD has joined #refstack20:35
*** esker has joined #refstack21:24
*** esker has quit IRC21:29
*** esker has joined #refstack23:27
*** esker has quit IRC23:31

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!