*** esker has joined #refstack | 00:53 | |
*** markvoelker has quit IRC | 01:01 | |
*** esker has quit IRC | 02:04 | |
*** esker has joined #refstack | 02:06 | |
*** esker has quit IRC | 02:06 | |
*** esker has joined #refstack | 02:06 | |
*** esker has quit IRC | 02:29 | |
*** markvoelker has joined #refstack | 02:47 | |
*** markvoelker has quit IRC | 02:51 | |
*** coolsvap|away is now known as coolsvap | 03:15 | |
*** esker has joined #refstack | 03:29 | |
*** esker has quit IRC | 03:35 | |
*** markvoelker has joined #refstack | 03:48 | |
*** markvoelker has quit IRC | 03:52 | |
*** esker has joined #refstack | 03:58 | |
*** esker has quit IRC | 04:23 | |
*** esker has joined #refstack | 04:46 | |
*** markvoelker has joined #refstack | 04:49 | |
*** markvoelker has quit IRC | 04:53 | |
*** esker has quit IRC | 04:57 | |
*** esker has joined #refstack | 05:23 | |
*** esker has quit IRC | 05:28 | |
*** markvoelker has joined #refstack | 05:49 | |
*** markvoelker has quit IRC | 05:54 | |
*** cody-somerville has joined #refstack | 06:49 | |
*** cody-somerville has quit IRC | 06:49 | |
*** cody-somerville has joined #refstack | 06:49 | |
*** markvoelker has joined #refstack | 06:50 | |
*** markvoelker has quit IRC | 06:55 | |
*** esker has joined #refstack | 07:27 | |
*** esker has quit IRC | 07:32 | |
*** markvoelker has joined #refstack | 08:51 | |
*** markvoelker has quit IRC | 08:55 | |
*** markvoelker has joined #refstack | 10:52 | |
*** markvoelker has quit IRC | 10:57 | |
*** esker has joined #refstack | 11:31 | |
*** esker has quit IRC | 11:36 | |
*** markvoelker has joined #refstack | 12:52 | |
*** openstackgerrit has quit IRC | 12:53 | |
*** markvoelker has quit IRC | 12:57 | |
*** openstackgerrit has joined #refstack | 13:05 | |
*** esker has joined #refstack | 13:35 | |
*** esker has quit IRC | 13:40 | |
*** markvoelker has joined #refstack | 13:53 | |
*** esker has joined #refstack | 13:54 | |
*** markvoelker has quit IRC | 13:58 | |
*** esker has quit IRC | 13:59 | |
*** coolsvap is now known as coolsvap|away | 14:37 | |
*** markvoelker has joined #refstack | 14:54 | |
*** markvoelker has quit IRC | 14:59 | |
*** esker has joined #refstack | 15:41 | |
*** esker has quit IRC | 15:46 | |
*** esker has joined #refstack | 16:42 | |
*** esker has quit IRC | 16:47 | |
*** markvoelker has joined #refstack | 16:55 | |
*** markvoelker has quit IRC | 16:59 | |
*** esker has joined #refstack | 17:43 | |
*** esker has quit IRC | 17:49 | |
*** alevine has joined #refstack | 18:41 | |
*** catherineD has quit IRC | 18:50 | |
*** catherine_d|1 has joined #refstack | 18:51 | |
*** sslypushenko has joined #refstack | 19:06 | |
*** esker has joined #refstack | 19:22 | |
*** edmondsw has joined #refstack | 19:22 | |
*** edmondsw has quit IRC | 19:22 | |
*** esker has quit IRC | 19:27 | |
catherine_d|1 | hello | 20:00 |
---|---|---|
alevine | We 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 |
alevine | Hi :) | 20:00 |
sslypushenko | alevine: Actually, I have one more question for you | 20:00 |
alevine | sure | 20:00 |
sslypushenko | How do you plan using RefStack? | 20:01 |
sslypushenko | What kind of value it brings to your side | 20:01 |
alevine | It's in my doc. Our requirements are in there. And my Enhancement document (previous one) listed them explicitly | 20:01 |
alevine | Of course I was thinking about our needs all the time as well :) | 20:01 |
alevine | In short - we want to be able to validate various OpenStack reference architectures. | 20:02 |
alevine | Not just the DefCore one but any other else. Meaning, that it should be defined first (new Guidelines) and then validated. | 20:02 |
sslypushenko | What do you mean under validation? | 20:03 |
alevine | I mean certification like DefCore does with OpenStack giving the OpenStack logo, but in other Guidelines cases it'll be other badges. | 20:03 |
alevine | Testing. | 20:03 |
sslypushenko | In Mirantis we also have kind project for cloud validation, but that team found RefStack is suitable for validation purpose | 20:04 |
alevine | Testing against some predefined set of Tempest tests with external plugins. | 20:04 |
alevine | RefStack can be suitable if implements all I listed in the reqs :) | 20:04 |
sslypushenko | yeap | 20:04 |
catherine_d|1 | +1 | 20:04 |
catherine_d|1 | that is why I am so eagre to engage alevine: 's team on RefStack | 20:05 |
catherine_d|1 | but I want to do it systematically with DefCore on our side | 20:05 |
sslypushenko | It 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|1 | alevine: 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.8fxpb1onf6vr | 20:07 |
alevine | That'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 |
sslypushenko | I meant sync with Defcore and alevine's prototype adoption | 20:07 |
catherine_d|1 | sslypushenko: i am so thankful that you keep working iwth us | 20:08 |
sslypushenko | catherine_d|1: np) Hanging out with you, guys means a lot to me) | 20:08 |
alevine | Sergey 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|1 | sslypushenko: 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 |
alevine | I can share the previous version. Hold on. | 20:09 |
sslypushenko | alevine: Yeap I don't have issues with access to doc | 20:09 |
alevine | https://docs.google.com/document/d/1GeLL7XHT2VnuO40lmR-tHLuaomNExWZCza4iFb8VODI/edit | 20:10 |
alevine | But I'm not sure Sergey wants to read ALL of that. :) | 20:10 |
catherine_d|1 | sslypushenko: 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|1 | sslypushenko: or maybe only check whether alevine: and I have had any discussion on the areas that you DISAGREE | 20:11 |
sslypushenko | alevine: Hmmm.... something went wrong, Now I have only view acces | 20:11 |
alevine | Because that's Refstack Requirements History. Another doc. First draft. | 20:12 |
alevine | I don't think you want to comment something right there. Better go into the new clean doc. | 20:12 |
sslypushenko | I don't see any comments | 20:13 |
sslypushenko | That is why we like gerrit) | 20:13 |
alevine | You don't? Weird. Hold on. | 20:13 |
sslypushenko | At minimum, it is predictable) | 20:14 |
alevine | How about now? | 20:15 |
alevine | Google docs are quite predictable I assure you. | 20:15 |
alevine | I shared the second doc with you. | 20:15 |
sslypushenko | got it | 20:15 |
alevine | How 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|1 | sslypushenko: that is great | 20:16 |
sslypushenko | alevine: Lets keep things as it is) | 20:17 |
sslypushenko | We definitely will move to gerrit, but later | 20:17 |
alevine | No, 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|1 | alevine: the biggest problem I have by using google doc is ownership of the doc . | 20:18 |
alevine | catherine: What do you mean? | 20:18 |
sslypushenko | alevine: We can put in rst books as complicated content as we want | 20:19 |
catherine_d|1 | using google doc the individual is the owner ... you can delete the doc that you share .. I can delete the data modle that I hsare | 20:19 |
sslypushenko | even pictures and schemas | 20:19 |
catherine_d|1 | but in gerrit ...everything is owned by OpenStack | 20:19 |
alevine | sslypushenko: How easy is it? Can I do this with such a doc in two days as I did with mine? | 20:19 |
sslypushenko | but it takes time | 20:19 |
alevine | sslypushenko: Do you have any example? | 20:19 |
alevine | sslypushenko: Seriously, maybe that's why some tasks take too long. We shouldn't be handicapped by our instruments, you know. | 20:20 |
alevine | Instruments should help us not stop us. | 20:20 |
sslypushenko | alevine: yeap) all content on developer.openstack.org is generated from rst | 20:20 |
sslypushenko | but google docs are good for the time being | 20:21 |
sslypushenko | Actually we have one more option here - openstack wiki | 20:21 |
alevine | Guys, 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 |
sslypushenko | but lets stick to googe gocs | 20:21 |
alevine | :) good suggestion | 20:22 |
catherine_d|1 | alevine: agree that is why I have no objective using google doc now ,.. | 20:22 |
sslypushenko | white it is working for all of us) | 20:22 |
sslypushenko | *while | 20:22 |
catherine_d|1 | but once agree we will convert to wiki or spec | 20:22 |
alevine | Absolutely. | 20:22 |
catherine_d|1 | yup | 20:22 |
alevine | That's written in my doc exactly | 20:22 |
catherine_d|1 | yup ... that is exactly while I put up a datamodel presentation for discussion ,,, I will follow up with a spect for formal approval | 20:23 |
catherine_d|1 | alevine: I think you reuqiement is so long that it make more sesne in wiki ... but we can talk about that later | 20:24 |
sslypushenko | alevine: One more technical question, about your proto | 20:24 |
catherine_d|1 | anyting else? I know it is late for your time zone | 20:24 |
alevine | sure | 20:25 |
sslypushenko | Is docker script working for your fork? | 20:25 |
sslypushenko | I did not have a chance to try | 20:25 |
alevine | What do you mean by docker script? | 20:25 |
sslypushenko | I meant run-in-docker | 20:26 |
alevine | It's a brought up website. We did have another one brought up as well so it's two now. | 20:26 |
sslypushenko | I meant run-in-docker script | 20:26 |
alevine | We didn't do anything about docker. It's in Amazon instance. So we copy it if we want. | 20:26 |
sslypushenko | no no) It just for testing on local setup | 20:27 |
alevine | No docker. We didn't need to. | 20:27 |
sslypushenko | It would be helpful if it is working) | 20:27 |
alevine | Andrey Pavlov, my teammate, developed it locally and then just brought it up in AWS. | 20:27 |
sslypushenko | then anyone can just pull repo, run run-in-docker script and get working prototype locally | 20:28 |
alevine | Well, 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 |
sslypushenko | it is how things work now | 20:28 |
sslypushenko | alevine: sure, no pressure) | 20:29 |
sslypushenko | You can mail me, if you have some questions | 20:29 |
alevine | About docker? When we are ready we'll ask. Or see if someone more familiar can do the thing. | 20:30 |
sslypushenko | Just mail me, lets see what we can do | 20:31 |
sslypushenko | I actually hope, that almost everything should works fine | 20:31 |
alevine | Perfect :) | 20:32 |
catherine_d|1 | great .. 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 |
sslypushenko | catherine_d|1: you too) | 20:33 |
alevine | you too | 20:33 |
alevine | bye | 20:33 |
sslypushenko | bye | 20:33 |
*** alevine has left #refstack | 20:33 | |
catherine_d|1 | see you next year :-) | 20:33 |
*** catherine_d|1 has quit IRC | 20:33 | |
*** catherineD has joined #refstack | 20:35 | |
*** esker has joined #refstack | 21:24 | |
*** esker has quit IRC | 21:29 | |
*** esker has joined #refstack | 23:27 | |
*** esker has quit IRC | 23:31 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!