Monday, 2016-10-31

« Sunday, 2016-10-30 Index Tuesday, 2016-11-01 »
*** jerrygb has quit IRC00:17
*** muralia has joined #openstack-containers00:50
*** muralia has quit IRC00:54
*** tonanhngo has joined #openstack-containers01:03
*** tonanhngo has quit IRC01:08
*** zz_dimtruck is now known as dimtruck01:12
*** sergmelikyan has joined #openstack-containers01:30
*** sergmelikyan has quit IRC01:34
*** hieulq has joined #openstack-containers01:52
*** anushkrishnamurt has joined #openstack-containers02:00
*** kevin has joined #openstack-containers02:34
*** kevin is now known as Guest5619002:34
*** anushkrishnamurt has quit IRC02:40
*** muralia has joined #openstack-containers02:51
*** muralia has quit IRC02:56
*** jerrygb has joined #openstack-containers03:33
*** jerrygb has quit IRC03:37
*** Jeffrey4l has joined #openstack-containers03:44
*** jwcroppe has quit IRC03:53
*** sergmelikyan has joined #openstack-containers04:31
*** sergmelikyan has quit IRC04:35
*** jerrygb has joined #openstack-containers04:37
*** muralia has joined #openstack-containers04:53
*** hehx_ has quit IRC04:53
*** muralia has quit IRC04:57
openstackgerritMichael Liu proposed openstack/magnum: magnum support cni network driver  https://review.openstack.org/39171805:00
*** tonanhngo has joined #openstack-containers05:04
*** jerrygb has quit IRC05:04
*** tonanhngo has quit IRC05:09
*** chhavi has joined #openstack-containers05:25
*** tonanhngo has joined #openstack-containers05:31
*** Wenzhi has joined #openstack-containers05:38
*** vimal has joined #openstack-containers05:43
*** muralia has joined #openstack-containers05:54
*** muralia has quit IRC05:59
*** mjura has joined #openstack-containers06:26
*** mjura_ has joined #openstack-containers06:26
*** mjura has quit IRC06:26
chhaviI am trying to create a cluster using openstack-magnum, its failing for "os-collect-config:cfn unavailable"06:46
chhavichecking further it looks cfn is default for os-collect-config, does that means the image should have the heat-cfn-tools06:47
*** muralia has joined #openstack-containers06:55
*** belmoreira has joined #openstack-containers06:59
openstackgerritRyosuke Mizuno proposed openstack/magnum-ui: Add javascript tests for clusterCreateInfoController  https://review.openstack.org/39172706:59
chhavi*heat-cfntools07:00
*** muralia has quit IRC07:00
*** jerrygb has joined #openstack-containers07:02
*** jerrygb has quit IRC07:08
openstackgerritMichael Liu proposed openstack/magnum: magnum support cni network driver  https://review.openstack.org/39171807:12
*** Oku_OS-away is now known as Oku_OS07:12
*** tonanhngo has quit IRC07:18
*** yuanying has joined #openstack-containers07:27
*** yuanying has quit IRC07:27
*** chhavi has quit IRC07:33
*** Jeffrey4l has quit IRC07:34
*** tonanhngo has joined #openstack-containers07:41
*** dimtruck is now known as zz_dimtruck07:43
*** zz_dimtruck is now known as dimtruck07:43
*** chhavi has joined #openstack-containers07:44
*** tonanhngo has quit IRC07:46
*** dimtruck is now known as zz_dimtruck07:53
*** muralia has joined #openstack-containers07:56
*** muralia has quit IRC08:00
*** absubram has joined #openstack-containers08:02
*** Oku_OS is now known as Oku_OS-away08:12
*** Oku_OS-away is now known as Oku_OS08:13
*** fragatina has joined #openstack-containers08:21
*** Oku_OS is now known as Oku_OS-away08:21
*** fragatina has quit IRC08:21
*** fragatina has joined #openstack-containers08:22
*** Wenzhi has quit IRC08:23
*** fragatina has quit IRC08:36
*** Oku_OS-away is now known as Oku_OS08:48
*** kbyrne has quit IRC08:56
*** muralia has joined #openstack-containers08:57
*** muralia has quit IRC09:01
*** chhavi has quit IRC09:29
*** yuanying has joined #openstack-containers09:39
*** tonanhngo has joined #openstack-containers09:42
*** yuanying has quit IRC09:44
*** tonanhngo has quit IRC09:47
*** vimal has quit IRC09:47
*** muralia has joined #openstack-containers09:57
*** vimal has joined #openstack-containers09:57
*** chhavi has joined #openstack-containers09:58
*** muralia has quit IRC10:02
strigazimjura_ jgrassler ping10:06
mjura_strigazi: I'm here10:07
mjura_good morning10:07
mjura_strigazi: how can I help you?10:07
strigaziGood Morning,10:08
strigaziWould suse be interested in providing a third party CI to run functional tests for the k8s_suse driver?10:09
strigaziDo you know whom the magnum team should contact for this?10:09
strigaziWe plan to ask Canonical too, for ubuntu flavors10:10
strigazis/flavors/drivers10:10
mjura_strigazi: I think that we should be interested in10:12
mjura_I think we should escalate through few people10:13
*** apuimedo has joined #openstack-containers10:26
openstackgerritSpyros Trigazis proposed openstack/magnum: Add user-domain in role creation  https://review.openstack.org/39177910:32
mjura_strigazi: ok, I've sent official email to our PM and CI guys10:40
mjura_strigazi: from my site this idea has +110:40
mjura_strigazi: but let's what will be discussion10:40
mjura_strigazi: I've added you to CC10:41
strigazimjura_, cool, Thanks!10:42
*** fragatina has joined #openstack-containers10:44
*** jerrygb has joined #openstack-containers10:57
*** anushkrishnamurt has joined #openstack-containers11:14
*** chhavi has quit IRC11:20
*** fragatina has quit IRC11:24
*** chhavi has joined #openstack-containers11:34
*** anushkrishnamurt has quit IRC11:36
*** tonanhngo has joined #openstack-containers11:43
*** tonanhngo has quit IRC11:48
*** absubram has quit IRC11:53
*** absubram_ has joined #openstack-containers11:53
*** askb has quit IRC11:53
*** muralia has joined #openstack-containers11:59
*** jerrygb has quit IRC12:01
*** muralia has quit IRC12:03
*** tonanhngo has joined #openstack-containers12:17
*** tonanhngo_ has joined #openstack-containers12:21
*** tonanhngo has quit IRC12:22
*** tonanhngo_ has quit IRC12:25
*** fragatina has joined #openstack-containers12:29
*** yuanying has joined #openstack-containers12:40
*** Drago has joined #openstack-containers12:43
*** yuanying has quit IRC12:45
*** sergmelikyan has joined #openstack-containers12:46
*** Drago has quit IRC12:47
*** sergmelikyan has quit IRC12:50
*** Drago has joined #openstack-containers12:52
*** Drago has quit IRC12:52
*** dave-mccowan has joined #openstack-containers12:53
*** Drago has joined #openstack-containers12:55
*** Drago1 has joined #openstack-containers12:57
*** Drago has quit IRC13:00
*** muralia has joined #openstack-containers13:00
*** jerrygb has joined #openstack-containers13:03
*** muralia has quit IRC13:04
*** jerrygb has quit IRC13:07
*** tonanhngo has joined #openstack-containers13:08
*** jerrygb has joined #openstack-containers13:11
*** jerrygb has quit IRC13:11
*** Drago1 has quit IRC13:11
*** Drago has joined #openstack-containers13:12
*** tonanhngo has quit IRC13:12
*** Drago has quit IRC13:14
*** absubram_ has quit IRC13:14
*** jmckind has joined #openstack-containers13:19
*** jwcroppe has joined #openstack-containers13:32
openstackgerritSpyros Trigazis proposed openstack/magnum: WIP: Make cinder volume optional  https://review.openstack.org/39183013:35
*** Drago has joined #openstack-containers13:37
*** Drago1 has joined #openstack-containers13:41
*** Drago has quit IRC13:42
*** Drago1 has quit IRC13:45
*** sergmelikyan has joined #openstack-containers13:56
*** absubram has joined #openstack-containers13:56
*** Drago1 has joined #openstack-containers14:00
*** muralia has joined #openstack-containers14:00
*** muralia has quit IRC14:05
*** jerrygb has joined #openstack-containers14:08
*** zz_dimtruck is now known as dimtruck14:09
*** sergmelikyan has quit IRC14:13
*** sergmelikyan has joined #openstack-containers14:13
*** chris_hultin|AWA is now known as chris_hultin14:14
*** mtanino has joined #openstack-containers14:15
*** sergmelikyan has quit IRC14:19
*** briancurtin has quit IRC14:19
*** muralia has joined #openstack-containers14:20
*** mtanino has quit IRC14:20
*** briancurtin has joined #openstack-containers14:22
*** clsacramento has joined #openstack-containers14:25
*** sergmelikyan has joined #openstack-containers14:30
*** JoseMello has joined #openstack-containers14:33
*** randallburt has joined #openstack-containers14:34
*** sergmelikyan has quit IRC14:35
*** jmckind_ has joined #openstack-containers14:36
*** jmckind has quit IRC14:38
*** randallburt has quit IRC14:38
*** randallburt has joined #openstack-containers14:41
*** fragatina has quit IRC14:42
*** mjura_ has quit IRC14:53
*** chhavi has quit IRC14:54
*** vimal has quit IRC14:55
*** syed_ has joined #openstack-containers14:58
*** Drago1 has quit IRC15:02
*** Drago has joined #openstack-containers15:03
*** jerrygb has quit IRC15:07
*** Drago has quit IRC15:08
*** jerrygb has joined #openstack-containers15:08
*** tonanhngo has joined #openstack-containers15:08
*** Drago has joined #openstack-containers15:12
*** tonanhngo has quit IRC15:13
*** tonanhngo has joined #openstack-containers15:19
*** chhavi has joined #openstack-containers15:19
*** mtanino has joined #openstack-containers15:22
*** tonanhngo has quit IRC15:23
*** Jeffrey4l has joined #openstack-containers15:38
*** Jeffrey4l has quit IRC15:39
*** sergmelikyan has joined #openstack-containers15:40
*** Jeffrey4l has joined #openstack-containers15:40
*** Jeffrey4l has quit IRC15:41
*** apuimedo has quit IRC15:42
*** Jeffrey4l has joined #openstack-containers15:42
*** tonanhngo has joined #openstack-containers15:49
*** tonanhngo has quit IRC15:53
Dragorochaporto: ping15:57
*** srwilkers has joined #openstack-containers15:57
*** swatson_ has joined #openstack-containers15:57
Dragostrigazi: ping15:59
*** chetna has joined #openstack-containers16:05
*** absubram has quit IRC16:12
*** AlexeyAbashkin has quit IRC16:13
*** AlexeyAbashkin has joined #openstack-containers16:15
*** jmckind_ has quit IRC16:17
*** anush has joined #openstack-containers16:19
*** chetna has quit IRC16:19
*** chetna has joined #openstack-containers16:20
strigazihey Drago16:20
DragoHey strigazi, about the NodeGroup discussion at the summit16:20
Dragostrigazi: Do you remember why rochaporto said it wasn't acceptable to not have a reference to the CT in the Cluster?16:21
Dragostrigazi: For some reason, simply comparing all of the important attributes in a Cluster to a supported ClusterTemplate wasn't sufficient to know if a Cluster was "supported"16:22
strigaziDrago, I think it was for the upgrades, to have the increasing counter16:22
Dragojvgrant ^16:23
jvgrantstrigazi, counter of current version? not sure i understand16:24
strigazibe back in 10'16:25
Dragojvgrant: The idea is that as the CT gets updated, it can have an incrementing version along with it16:25
*** jmckind has joined #openstack-containers16:25
*** dimtruck is now known as zz_dimtruck16:25
*** zz_dimtruck is now known as dimtruck16:26
jvgrantok, so it is about wanting to maintain versioning information on cluster creation16:30
Dragojvgrant: I'm not sure anymore. I feel like I'm speculating at this point. The upgrade part didn't come in until near the end of the conversation we had about it16:31
jvgrantDrago: ok, probably need to have some further discussion on that use case then.16:32
*** rafael__ has joined #openstack-containers16:34
*** kbyrne has joined #openstack-containers16:41
*** absubram has joined #openstack-containers16:41
Dragostrigazi: You there?16:46
*** tonanhngo has joined #openstack-containers16:50
*** david-lyle has joined #openstack-containers16:51
*** Jeffrey4l has quit IRC16:52
*** tonanhngo has quit IRC16:54
*** tonanhngo has joined #openstack-containers16:58
*** belmoreira has quit IRC16:58
*** tonanhngo has quit IRC17:02
*** srwilkers has quit IRC17:09
Dragojvgrant: Thinking more about it, I think the upgrade story wasn't any more complicated than that. When you update the CT, it increments its version, so you can then query Clusters created from foo_ct v1, v2, etc17:11
jvgrantDrago: ok so there would be a new version field in the cluster for CT version?  or are we going back to separating the objects into cluster and clustertemplate again?17:13
jvgranti guess if we just add it to the cluster object then the version is set when the cluster create happens.17:15
jvgranti think that works fine if we just add a CT_name attribute and CT_version attribute. when CTs are created/updated they are changed and in the case of a cluster create they are filled in from the CT(if present) or left unset to indicate it was not created from a CT17:17
Dragojvgrant: Since we're using a relational DB, I'd think we would add the immutable CT's FK to the Cluster and the the immutable CT would have the version in it17:17
jvgrantDrago: that works as well, but would end up with a lot more db entries17:17
*** tonanhngo has joined #openstack-containers17:18
DragoWorkflow: Create a CT (version is 1). Update it (version bumps to 2). Create a Cluster - immutable CT gets created that, naturally, has v2 and set the FK on the Cluster to it. Create another cluster - uses previously-created immutable CT17:19
Dragojvgrant: CTs should still be prototypes and updatable17:19
Dragojvgrant: And Clusters should still have all attributes, since who knows which ones will be updatable. I think the immutable CT should be there just to be reference-able.17:20
jvgrantDrago: ok, makes sense17:21
jvgrantDrago: can you delete CTs then?17:21
*** tonanhngo has quit IRC17:22
Dragojvgrant: Good question. Should be able to, not sure how it'd work with what we're talking about.17:22
jvgrantDrago: yeah, seems a little complicated with now versioned CTs17:23
Dragojvgrant: Might want to do something like have the client prompt to make sure the user really wants to delete the CT and then delete all versioning information17:24
jvgrantDrago: what if it is referenced in a cluster?17:24
*** srwilkers has joined #openstack-containers17:25
jvgrantDrago: maybe the reference in the cluster should be more informational.  Just the name and version. They can look it up but it might not be there17:25
Dragojvgrant: It wouldn't be an issue if the relation between immutable CTs and Clusters was many-to-many. Reason for that is you can create a Cluster from multiple CTs right now, and I like that feature17:25
Dragojvgrant: Not sure I'm a fan of that17:26
jvgrantDrago: it is up to the operator to maintain the versions if they wish. A updated CT version is really just a copy of the original with a new version number and the changes17:27
*** jwcroppe has quit IRC17:27
jvgrantDrago: i'm feeling like we are going back to required CTs that are separate objects really17:27
*** jwcroppe has joined #openstack-containers17:28
strigaziDrago, sorry there was an issue with upgrade we did17:29
Dragojvgrant: I don't see how. What we're talking about is the same as we have in the spec except for the addition of a reference to an immutable, informational copy of the CT used17:29
Dragojvgrant: Once the cluster is created, the CT still has nothing to do with it, functionally17:30
Dragostrigazi: No problem17:30
jvgrantDrago: i'm ok with that if that is all it is. But if it is also making it so we now require the original CT to not be deleted, etc.. then i think that is more complicated17:31
*** jwcroppe_ has joined #openstack-containers17:31
jvgrantDrago: if we are just storing a snapshot then i don't see a problem17:31
Dragojvgrant: I think we need to figure out what we want to do about the version information upon deletion, but all the other operations are the same (besides incrementing the CT version)17:32
*** jwcroppe has quit IRC17:32
strigaziwhat about the NGTs?17:33
strigaziDrago, jvgrant ^^17:33
jvgrantthey would follow the same rules as the CTs17:33
Dragostrigazi: I don't know what the edge cases are for NGTs, but yes, the same rules should apply17:33
*** yuanying has joined #openstack-containers17:34
jvgranteach cluster would have references to any templates it used to create itself and the contained nodegroups as well17:34
strigaziDrago, jvgrant, the reasoning behind version is that we want to track where a cluster came from17:34
Dragostrigazi: So a query like "give me clusters from my_ct v1" is what you desire?17:35
jvgrantstrigazi: all the info of it or just something that could be used to track it?  Meaning a snapshot of the CT used or just a name/version info that could be used to look it up?17:36
strigaziIf we don't allow deletions name/version should be enough17:37
*** yuanying has quit IRC17:38
strigaziTo manage clusters in bulk you need to have them grouped17:38
strigaziThese clusters come from CT_x, do action action_A on them17:39
jvgranti'm assuming you also want to be able to block any overrides during cluster creation then from the CT?17:39
strigazijvgrant, Drago, make sense?17:39
Dragostrigazi: So the user could create a CT of the same name and it would come up in your query?17:40
strigaziWe talked about that too, locking should be applied when needed17:40
strigaziDrago, even if it comes up we shouldn't care, not sure how this can be handled17:42
*** jwcroppe_ has quit IRC17:42
jvgrantthis seems like it could be handled through admin settings limiting the creation/deletion of CTs. then the references with name/version would be enough for the grouping17:43
chhavijvgrant, Drago: I am trying to create a cluster, its failing in os-collect-config for cfn ssl verification failure.17:43
strigaziDrago jvgrant, Do you still have concerns why we want to keep track of CTs?17:44
chhaviits hitting this bug: https://bugs.launchpad.net/heat/+bug/148251017:45
openstackLaunchpad bug 1482510 in heat "OS::Heat::SoftwareDeployment failed due SSL certificate verification error" [Medium,In progress] - Assigned to Steve Baker (steve-stevebaker)17:45
Dragostrigazi, jvgrant: Seems janky to have a feature like that just to not have references to things in the data model17:45
jvgrantstrigazi: i think i understand the use case now a little better.  Just want to make sure we don't over engineer a solution that some small changes on top could fix17:45
strigazi"some small changes on top could fix" what do you mean?17:45
Dragochhavi: Using the Mesos driver?17:46
DragoI think that's the only one with os-collect-config17:47
chhaviyes i am using ubuntu mesos image17:47
chhavion ppc64le17:47
jvgrantstrigazi: meaning instead of implementing a full versioning functionality for CTs and storing an additional object for each template on creation, could we get the same use case by simple references and other admin options like limiting the creation/deletion when desired17:47
Dragochhavi: If you want, you can configure Heat to use a different software config transport by default. It uses the CFN API by default, and that's probably not what you really want. Change it to use Heat, or swift or zaqar if you want17:48
jvgrantstrigazi, Drago: we might still need to store the additional info, i'm just playing devil's advocate here to make sure we aren't over complicating this17:49
Dragojvgrant: From what I understand, strigazi doesn't want to stop users from creating their own CTs.17:49
*** dave-mccowan has quit IRC17:49
strigaziDrago, ^^ yes17:49
strigazibut to manage cluster, specifically for upgrade, we don't want to allow unilimited combinations of attributes as in the proposed model17:50
strigazibut to manage clusters, specifically for upgrades, we don't want to allow unilimited combinations of attributes as in the proposed model17:50
Dragostrigazi: Right, locked attributes covers that one though17:51
DragoJust not the tracking17:51
jvgrantstrigazi: so you want to know which template(s) were used to create any CT17:51
strigaziDrago, you need tracking17:51
Dragochhavi: https://github.com/openstack/heat/blob/master/heat/common/config.py#L195-L21417:51
chhaviDrago: is the cfn-api not functional for mesos17:51
jvgrantstrigazi: any cluster not CT17:51
strigaziDrago, we won't always upgrade all clusters in one go, some will upgrade now some later17:52
strigazijvgrant, yes?17:52
strigazijvgrant, yes17:52
Dragochhavi: Mesos has nothing to do with it. It's probably just a bug with softwareconfig and the CFN API. I would just switch away from the CFN API anyway, which would also solve your problem17:53
*** tushark has joined #openstack-containers17:53
chhaviDrago: ok i will give a try to use heat, thanks17:53
jvgrantstrigazi: what if you deleted the CT?17:53
Dragostrigazi: And how will you track the ones you already did vs later?17:54
strigaziYou don't if it's referenced17:54
strigaziupgraded clusters will have a bumbed version.17:55
Dragostrigazi: In the model we're talking about, all CTs that had a Cluster created from them would be "referenced" so I think that's a tough policy to sell17:55
strigaziDrago, that can be true only in some cases I guess17:56
strigaziI understand the desire to create clusters at will but we must also track them17:56
Dragostrigazi: The main reason is that you can update the CT independently. It makes sense to keep the *versioned* (immutable) CT around, but not the one you can create Clusters from17:56
jvgrantstrigazi, Drago: what if we don't allow CT updates?  You have to create a new one. It can be based on the old, but has a new name17:57
Dragojvgrant: short answer: No17:57
jvgrantstrigazi,Drago: and then we give an option to block CT deletes17:58
Dragojvgrant: long answer: Noooooo17:58
strigaziDrago, what do you propose then?17:58
strigaziSolve the following problem17:59
Dragojvgrant: Why a new name?17:59
jvgrantstrigazi, Drago: it seems like the main use case we are talking about is tracking and labeling. Know what template a cluster/nodegroup came from.17:59
Dragojvgrant: I guess honestly, the system we're imagining so far is kind of like what you said, except the immutable CT is created when you create the cluster, while the "normal" CT is mutable18:00
jvgrantif i have MesosCT_v1 and then i want an update cluster i just create it referencing MesosCT_v1 and name it MesosCT_v218:01
jvgrantsince as an admin operator i blocked CT deletion of "public" CTs18:01
Dragojvgrant: I think versioning would be nicer than name munging18:01
DragoFor the same effect18:01
jvgrantall i need in the cluster is a reference to the name18:01
Dragojvgrant: And with names you have the danger of collisioins18:02
Drago*collisions18:02
jvgrantthe problem is the reference is just a snap shot and if the actually CT was deleted or changed it doesn't really tell the operator anything accept what was used18:02
jvgrantDrago: yeah, it could be a version field instead of name18:03
strigaziIf you snapshot inside the cluster object you can't query I guess18:03
Dragojvgrant: I kind of see your point with making CTs immutable, but I wouldn't want a ton of CTs showing up in the UI18:04
strigaziThink of the two types of clusters18:04
strigazisupported by the ops team18:04
strigaziand the ones created by users18:04
strigaziwe want to manage the supported clusters18:04
strigaziTotal freedom on how to create clusters and be able to sell it18:05
strigaziapplies to the second type18:05
strigaziWe also want to sell18:05
Dragojvgrant: What if we had the CTs all reference a "parent" thing that would help track the different CT versions, since they'd all be linked to it. In the UI we can expose only the most recent CT version found18:05
strigazirun your prodution service here and you'll get the new version without downtime18:05
jvgrantdo controls over "public"(for ops team) and "private" CT help that?  Limit what can be done to "public" CTs18:06
strigaziI think it helps18:07
Dragojvgrant: To be more clear, when create a new CT, the CT parent (for lack of a better name) would be created as well. When you modify a CT, it creates a new CT of the next version that also references this parent18:07
strigazithis the only way to do versions18:07
strigazithis is the only way to do versions18:07
DragoIf you wanted to delete the CT, you'd delete that new one and the parent would stick around18:08
*** achanda has joined #openstack-containers18:08
Dragojvgrant, strigazi: Up until now we've been talking about the versions of a CT referencing the original CT. I'm saying switch that to something that only has the purpose of "gathering" the CT versions together18:09
jvgrantDrago: we are now talking about a new versioning feature on top of templates18:09
achandaeliqiao: is this feature complete now? https://blueprints.launchpad.net/magnum/+spec/support-insecure-registry18:10
Dragojvgrant: Well, yeah, the conversation has been moving towards that18:10
jvgrantDrago: i like that better than trying to imbed too much into the templates18:10
jvgrantand clusters18:10
*** tonanhngo has joined #openstack-containers18:12
strigaziI'm leaving guys, it's late here. I'll do my best to describe the upgrades in detail18:12
Dragostrigazi: See ya18:12
jvgrantstrigazi: thanks for your help18:12
Dragojvgrant: Creating a new CT entry for every modification feels like overkill. Unless there are good reasons for tracking every modification, I'd rather track the modifications that actually make it into a cluster18:13
Dragojvgrant: So, have a "real" CT that gets modified, and create a *single* immutable CT for clusters that use a given version18:14
jvgrantDrago: so the immutable CT is create on CT modification, not on cluster create18:15
*** chhavi has quit IRC18:15
Dragojvgrant: I'm saying I'd rather have it on cluster create18:15
*** tonanhngo has quit IRC18:17
jvgrantDrago: that doesn't really help with the tracking issue does it? I guess i don't understand the need for knowing all the details of what was used. This seems more like labeling the cluster so it can be tracked vs needing to know all the values taht were used18:17
jvgrantDrago: in the use cases mentioned it only matters if there is a valid public CT that it can match to18:18
jvgrantDrago: if that CT is gone, then the info stored doesnt' really mean much18:18
Dragojvgrant: I'm not sure what you're responding to, because that seems orthogonal to what I was saying18:19
Dragojvgrant: I think we should vidyo18:19
jvgrantDrago: sure, send me a link. we might be going different directions on this18:19
*** dave-mccowan has joined #openstack-containers18:19
*** jmckind has quit IRC18:21
*** tonanhngo has joined #openstack-containers18:22
*** jmckind has joined #openstack-containers18:22
*** jmckind_ has joined #openstack-containers18:25
*** tonanhngo has quit IRC18:26
*** jmckind has quit IRC18:29
*** EricGonczer_ has joined #openstack-containers18:36
*** EricGonczer_ has quit IRC18:37
tusharkHi, I have kubernetes cluster with TLS enabled and setup with SkyDns, but the kubedns fails to talk to the api-server.18:40
tusharkE1031 17:08:18.998416       1 reflector.go:214] pkg/dns/dns.go:155: Failed to list *api.Endpoints: Get https://10.240.126.7:6443/api/v1/endpoints?resourceVersion=0: x509: failed to load system roots and no roots provided18:41
tusharkE1031 17:08:18.998703       1 reflector.go:214] pkg/dns/dns.go:156: Failed to list *api.Service: Get https://10.240.126.7:6443/api/v1/services?resourceVersion=0: x509: failed to load system roots and no roots provided18:41
tusharkAlthough I'm not configuring secrets for the service account, is this causing the above failure?18:41
*** chetna has quit IRC18:45
*** chetna has joined #openstack-containers18:45
*** fragatina has joined #openstack-containers18:53
*** fragatina has quit IRC19:13
*** tonanhngo has joined #openstack-containers19:14
*** tonanhngo has quit IRC19:18
*** randallburt has quit IRC19:23
*** tonanhngo has joined #openstack-containers19:30
*** apuimedo has joined #openstack-containers19:30
*** tonanhngo has quit IRC19:34
*** apuimedo has quit IRC19:37
*** tonanhngo has joined #openstack-containers19:40
openstackgerritVijendar Komalla proposed openstack/magnum: [WIP]Admin api to provide cluster stats  https://review.openstack.org/39130119:43
*** tonanhngo_ has joined #openstack-containers19:44
*** tonanhngo has quit IRC19:44
*** tonanhngo_ has quit IRC19:48
*** tonanhngo has joined #openstack-containers19:49
*** anush has quit IRC19:52
*** tonanhngo has quit IRC19:53
*** mikelekkas has joined #openstack-containers19:58
*** mikelekkas has quit IRC19:59
*** Drago has quit IRC20:03
*** muralia has quit IRC20:09
*** muralia has joined #openstack-containers20:09
*** muralia has quit IRC20:14
*** dave-mccowan has quit IRC20:15
*** achanda has quit IRC20:16
*** DanyC has joined #openstack-containers20:19
*** drago has joined #openstack-containers20:20
*** JoseMello has quit IRC20:22
*** drago has quit IRC20:26
*** DanyC has left #openstack-containers20:27
*** drago has joined #openstack-containers20:28
*** Drago5 has joined #openstack-containers20:33
*** drago has quit IRC20:38
*** Drago5 is now known as Drago20:40
*** jwcroppe has joined #openstack-containers20:44
*** dave-mccowan has joined #openstack-containers20:45
*** jerrygb__ has joined #openstack-containers20:48
*** jerrygb has quit IRC20:49
*** srwilkers has quit IRC20:51
*** jerrygb__ has quit IRC20:52
*** jwcroppe has quit IRC20:55
*** chris_hultin is now known as chris_hultin|AWA21:01
*** DanyC has joined #openstack-containers21:06
*** DanyC has quit IRC21:11
*** apuimedo has joined #openstack-containers21:14
*** openstackgerrit has quit IRC21:18
*** openstackgerrit has joined #openstack-containers21:19
*** vijendar has joined #openstack-containers21:28
*** askb has joined #openstack-containers21:29
*** dave-mccowan has quit IRC21:38
*** tonanhngo has joined #openstack-containers21:49
*** absubram has quit IRC21:50
*** vijendar has quit IRC21:51
*** vijendar has joined #openstack-containers21:54
*** tonanhngo has quit IRC21:54
*** jerrygb has joined #openstack-containers21:59
*** jerrygb has quit IRC22:04
*** sergmelikyan has quit IRC22:19
*** vije5904 has joined #openstack-containers22:23
*** vije5904 has left #openstack-containers22:23
*** vijendar has quit IRC22:24
*** vijendar has joined #openstack-containers22:25
*** tonanhngo has joined #openstack-containers22:28
*** sergmelikyan has joined #openstack-containers22:29
*** tonanhngo has quit IRC22:33
*** vijendar has quit IRC22:37
*** sergmelikyan has quit IRC22:39
*** jerrygb has joined #openstack-containers22:42
*** jerrygb_ has joined #openstack-containers22:45
*** chetna has quit IRC22:48
*** jerrygb has quit IRC22:48
*** tonanhngo has joined #openstack-containers22:53
*** vijendar has joined #openstack-containers22:55
*** apuimedo has quit IRC22:56
*** muralia has joined #openstack-containers22:57
*** tonanhngo has quit IRC22:57
*** vijendar1 has joined #openstack-containers22:58
*** srwilkers has joined #openstack-containers22:59
openstackgerritVijendar Komalla proposed openstack/magnum: Admin api to provide cluster stats  https://review.openstack.org/39130122:59
*** muralia has quit IRC23:00
*** muralia has joined #openstack-containers23:00
*** tonanhngo has joined #openstack-containers23:01
*** rafael__ has quit IRC23:05
*** vijendar has quit IRC23:05
*** vijendar1 has quit IRC23:05
*** vijendar has joined #openstack-containers23:06
*** tonanhngo has quit IRC23:06
*** vijendar has quit IRC23:07
*** apuimedo has joined #openstack-containers23:07
*** vijendar has joined #openstack-containers23:07
*** chetna has joined #openstack-containers23:07
*** vijendar_ has joined #openstack-containers23:08
*** clsacramento has quit IRC23:25
*** vijenda__ has joined #openstack-containers23:26
*** clsacramento has joined #openstack-containers23:26
openstackgerritStephen Watson proposed openstack/magnum: [WIP] Adds support for non-ID suffix  https://review.openstack.org/38981123:27
*** vijendar_ has quit IRC23:28
*** vijendar1 has joined #openstack-containers23:28
*** vijendar has quit IRC23:28
*** apuimedo has quit IRC23:32
*** Drago has quit IRC23:32
*** yuanying has joined #openstack-containers23:38
*** tonanhngo has joined #openstack-containers23:42
*** apuimedo has joined #openstack-containers23:43
*** vijendar has joined #openstack-containers23:44
*** vijendar1 has quit IRC23:45
*** vijenda__ has quit IRC23:45
*** tonanhngo has quit IRC23:48
*** vijendar1 has joined #openstack-containers23:49
*** chetna has quit IRC23:53
« Sunday, 2016-10-30 Index Tuesday, 2016-11-01 »

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