Wednesday, 2016-11-16

*** Dusty has joined #craton00:28
*** klindgren__ has joined #craton00:54
*** klindgren_ has quit IRC00:56
*** Dusty has quit IRC01:39
*** syed__ has quit IRC02:35
*** Dusty has joined #craton02:44
*** valw has joined #craton02:54
*** valw has quit IRC02:56
*** valw has joined #craton03:01
*** Dusty has quit IRC03:20
*** valw has quit IRC03:38
*** valw has joined #craton03:42
*** Mudpuppy has joined #craton04:44
*** valw has quit IRC05:02
*** harlowja has quit IRC05:55
*** Mudpuppy has quit IRC07:45
*** Mudpuppy has joined #craton08:15
*** Mudpuppy has quit IRC08:20
*** Mudpuppy has joined #craton12:17
*** Mudpuppy has quit IRC12:22
*** Mudpuppy has joined #craton12:42
*** Mudpuppy has quit IRC12:46
*** Dusty has joined #craton14:09
*** valw has joined #craton14:39
*** valw has quit IRC15:10
*** valw has joined #craton15:11
*** valw has quit IRC15:15
*** Mudpuppy has joined #craton15:15
*** valw has joined #craton15:15
*** valw has quit IRC15:17
*** valw has joined #craton15:30
*** syed__ has joined #craton15:31
*** valw has quit IRC15:35
*** valw has joined #craton15:59
*** valw has quit IRC16:05
*** valw has joined #craton16:12
*** tojuvone has quit IRC16:27
jimbakersigmavirus, thanks for responding to tomi. i will follow up as well. completely missed that post in the openstack-dev firehose - need to prioritize [craton] in my inbox!16:49
jimbakersigmavirus, the best part of reading https://wiki.opnfv.org/display/doctor/Doctor+Home is just seeing a lot of acronyms that i'm sure are perfectly common in NFV discussions, but are not used outside17:04
jimbakermy favorite must be VIM17:04
jimbakerwhich we in the openstack community perhaps more commonly call "cloud" :)17:04
*** valw has quit IRC17:32
*** valw has joined #craton17:41
*** valw has quit IRC17:46
*** david-lyle has quit IRC17:48
*** david-lyle has joined #craton17:48
jimbakerDusty, sulo, sigmavirus, just to follow up more on the multicloud aspects. with respect to craton, the obvious mapping to AWS would be craton device -> AWS resources, with the ARN (amazon resource name) stored in a variable as a foreign identifier (possibly multiple such elements, but easy enough as a JSON column)17:50
*** valw has joined #craton17:54
Dustyfor Multicloud, we should address it not just for AWS, but also Azure and VMware, etc.  How do we devise a system that identifies the cloud provider 1st then the DC or availability zone, then the resources?17:57
*** valw has quit IRC18:08
jimbakerDusty, these are good questions, and hopefully we can figure out possible mappings. do either clouds have a fundamentally different model than what aws presents?18:09
jimbakerfor aws, i'm going against this doc, http://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html18:10
*** harlowja has joined #craton18:14
*** valw has joined #craton18:16
sulolets get some reviews going here:18:18
sulohttps://review.openstack.org/#/c/395191/18:18
sulohttps://review.openstack.org/#/c/395191/18:18
sulohttps://review.openstack.org/#/c/395191/18:18
sulohttps://review.openstack.org/#/c/360605/18:19
sulohttps://review.openstack.org/#/c/360605/18:19
sulo...18:19
sulothere is two more that dep on these18:19
*** valw has quit IRC18:20
jimbakerharlowja, btw, back to our discussion in barcelona: i was completely wrong on the event listener in taskflow. it works just fine18:20
sulohttps://review.openstack.org/#/c/395074/18:20
jimbakerspecifically with respect to new state18:20
harlowjajimbaker woot18:20
jimbakersulo, thanks for that reminder about pending reviews18:21
sulogit-harry: that schema just looks wrong .. roles should be list of string18:30
sulogit-harry: iam pretty sure there are few more of those18:31
suloI guess we havent tested user etc enough to catch that18:32
jimbakersulo, looks like the ordering of that change got screwed up, or something like that with the PEP 8 failure; can you make the minor change? http://logs.openstack.org/91/395191/4/gate/gate-craton-pep8-ubuntu-xenial/41aa4e8/console.html18:32
jimbakerminor needed change18:32
sulosure18:34
sulowerid18:34
suloits catching stuff i havent touched18:34
sulothis is somethign new18:34
suloanyway .. let me fix18:34
DustyJim, I am not sure.  We do have a very large VMWare practice here, so we can tie off with someone on that team to figure it out.  The PM for Azure should be able to tell us as well.  If we understand all 4 use cases we can build in a way to ingest them and "play well with others".18:38
git-harrysulo: okay, I've updated that. The patch combined with your change, on which it depends, should mean that the schema are now all valid and will hopefully stay that way.18:40
sulogit-harry: thanks !!18:40
jimbakerDusty, right, that sounds like a good plan to me. it would be straightforward to adjust our schema with respect to region/cell if it makes sense18:40
jimbakerthe more interesting question is how we map resources in such environments to what we are doing?18:41
jimbakerare there considerations of multitenancy that do not map?18:41
jimbakerwe have a simple model - nothing is shared across project (tenant)18:42
*** valw has joined #craton18:43
jimbakerdo we have to adjust this concept with respect to say federated clouds?18:43
jimbakerand in all fairness, imperfect fits are not necessarily bad, so long as there is a value in using craton with these other clouds18:45
DustyI know some of our customers are delivering it as a multi-tenant solution and we are in discussions with some other customers that are looking at very large multi-tenant offerings18:46
DustyI think it depends who is utilizing craton to determine if we need that level18:47
*** valw has quit IRC18:47
Dustyfrom a RPC perspective, we probably do not care if the customer is delivering multi-tenant18:48
Dustybut I can see it beneficial for someone who does care18:48
jimbakerDusty, right. so a customer has created a federated/hybrid cloud solution, and has resources in their cloud X that work with their cloud Y18:49
sulojimbaker: can you re check those prs18:50
suloi am not sure why we suddently started getting whole bunch of different pep errors18:51
sulobut hey18:51
jimbakerfrom craton's perspective, these are completely separate. now if they have parallel layouts, or use some corresponding labeling, the customer (or support) could look at them in a similar fashion18:51
jimbakersulo, yeah, no worries18:51
jimbakeri see that as the problem with applying split patches like this; and minimal ordering  support of patches18:52
suloits not that18:52
sulothis is erroring on things not related to the chag18:52
sulo*change18:52
sulolike tools/craton-inventory.py18:52
jimbakersulo, ahh, right, that's crazy18:53
Dustysure.  I do not know if you are familiar with Rghtscale, but they extract the cloud provider for the customer allowing them to deploy their code on different clouds and not worry about how it gets there.  I see Craton working similarly in that it shouldn't care where the resource is, just have a record of what it is suppose to be and then keep it in that state18:53
jimbakerDusty, i haven't looked at the rightscale solution in any depth, but i think i understand its approach18:55
suloDusty: jimbaker: as cool as that sound re: aws/multicloud .. its probably out of scope of the project right now18:55
suloits nice to keep synergy in that region though18:55
jimbakerin some sense, the proposed used for craton here is coming from the opposite end - resources exist, we want to track18:55
jimbakerso we can better manage18:56
jimbakervs driving deployments as seen in right scale18:56
*** valw has joined #craton18:57
jimbakersulo, agreed, we should keep our multitenancy model simple for now. i have been trying to avoid going down, the solution to any problem is a DAG :)18:57
*** Dusty has quit IRC19:15
*** Dusty has joined #craton19:24
*** Dusty1 has joined #craton19:35
*** Dusty has quit IRC19:35
*** valw has quit IRC19:40
*** valw has joined #craton19:44
sulook rebased: https://review.openstack.org/#/c/360605/19:59
*** Dusty1 has quit IRC20:00
*** valw has quit IRC20:00
*** Dusty has joined #craton20:07
*** rainya has joined #craton20:16
syed__sigmavirus: do you have sometime ? Need to ask a general question20:17
sigmavirusI am in a meeting20:17
syed__so i have installed cratonclient, but when i run tox, despite of it failing which i am fixing, why does it gives me this20:18
syed__https://www.irccloud.com/pastebin/VLshUuDS/20:18
*** rainya has quit IRC20:20
*** rainya has joined #craton20:22
harlowja@jimbaker @sulo is there any <where is craton at, roadmap kind of thing> somewhere?20:43
harlowjai don't want internal folks getting to down the path of well craton isn't ready yet, or ... so we'll just do this or that until then20:44
harlowja(and/or other excuse for doing short-term thing instead of helping craton work out and use its workflow mechanisms...)20:44
harlowjaa roadmap might help for that20:49
*** Dusty has quit IRC20:55
*** Dusty has joined #craton21:00
*** hughsaunders has quit IRC21:03
jimbakerharlowja, right, we need to publish this. i will send something out to openstack-dev [craton], does that work for you?21:05
harlowjathat'd be nice :)21:05
jimbakerharlowja, awesome. i'm going to factor in both the barcelona discussion, along with some recent considerations around supporting multicloud (which increasingly makes sense); and our conversations with OSA21:07
harlowjacool beans21:07
*** hughsaunders has joined #craton21:07
*** jovon has joined #craton21:28
*** Dusty has quit IRC22:03
*** Dusty has joined #craton22:04
*** Mudpuppy_ has joined #craton22:18
*** Mudpuppy has quit IRC22:21
*** rainya has quit IRC22:22
*** Mudpuppy_ has quit IRC22:23
*** rainya has joined #craton22:27
*** rainya has quit IRC22:42
*** rainya has joined #craton22:53
*** Dusty has quit IRC23:11
*** Dusty has joined #craton23:15
*** Dusty has quit IRC23:16
*** rainya has quit IRC23:44
*** david-lyle_ has joined #craton23:50
*** david-lyle has quit IRC23:51
*** rainya has joined #craton23:55
*** syed__ has quit IRC23:55

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