Wednesday, 2016-11-02

*** jerrygb has joined #openstack-containers00:17
*** adrian_otto has joined #openstack-containers00:17
*** jerrygb_ has joined #openstack-containers00:20
adrian_ottowell done, Drago00:22
*** jerrygb has quit IRC00:23
*** apuimedo has quit IRC00:25
*** dfflanders has quit IRC00:27
*** adrian_otto has quit IRC00:28
*** mtanino has quit IRC00:35
*** jerrygb_ has quit IRC00:52
*** vijendar has joined #openstack-containers00:56
*** vijendar1 has joined #openstack-containers01:00
*** vijendar has quit IRC01:00
*** chetna has quit IRC01:08
*** vijendar has joined #openstack-containers01:09
*** EricGonczer_ has quit IRC01:16
*** Drago5 has joined #openstack-containers01:22
*** vijendar has quit IRC01:23
*** vijendar has joined #openstack-containers01:32
*** sergmelikyan has joined #openstack-containers01:33
*** adrian_otto has joined #openstack-containers01:36
*** sergmeli_ has joined #openstack-containers01:36
*** adrian_otto has quit IRC01:38
*** sergmelikyan has quit IRC01:39
openstackgerritMerged openstack/magnum-ui: Don't include openstack/common in flake8 exclude list  https://review.openstack.org/39149301:41
*** mtanino has joined #openstack-containers01:42
*** masayukig_ has joined #openstack-containers01:45
*** masayukig has quit IRC01:50
*** masayukig_ is now known as masayukig01:52
*** mtanino has quit IRC02:01
*** syed_ has quit IRC02:05
*** jerrygb has joined #openstack-containers02:05
*** vijendar has quit IRC02:08
openstackgerritfeng.shengqin proposed openstack/magnum: remove google_containers in INSECURE_REGISTRY_URL  https://review.openstack.org/39235602:12
*** vijendar has joined #openstack-containers02:13
*** Drago5 has quit IRC02:14
*** jvgrant has quit IRC02:14
*** jvgrant has joined #openstack-containers02:14
*** sergmeli_ has quit IRC02:37
*** sergmelikyan has joined #openstack-containers02:37
*** sergmelikyan has quit IRC02:42
*** ramishra_ has joined #openstack-containers02:50
*** ramishra has quit IRC02:51
*** yatin has joined #openstack-containers02:55
*** dave-mccowan has quit IRC02:57
*** vijendar has quit IRC02:59
*** Jeffrey4l has joined #openstack-containers03:07
*** adrian_otto has joined #openstack-containers03:10
*** vijendar has joined #openstack-containers03:17
*** vijendar has quit IRC03:30
*** mtanino has joined #openstack-containers03:33
*** vijendar has joined #openstack-containers03:35
*** chhavi has joined #openstack-containers03:40
*** vijendar has quit IRC03:53
*** vijendar has joined #openstack-containers03:57
*** sergmelikyan has joined #openstack-containers04:02
*** absubram has joined #openstack-containers04:04
*** absubram_ has joined #openstack-containers04:05
*** absubram has quit IRC04:08
*** absubram_ is now known as absubram04:08
*** vijendar has quit IRC04:09
*** vijendar has joined #openstack-containers04:14
*** jerrygb has quit IRC04:19
*** jerrygb has joined #openstack-containers04:24
*** vijendar has quit IRC04:24
*** yuanying has quit IRC04:24
*** vijendar has joined #openstack-containers04:30
*** yuanying has joined #openstack-containers04:36
*** absubram has quit IRC04:37
*** mtanino has quit IRC04:48
*** chhavi has quit IRC04:48
*** vijendar has quit IRC04:49
*** vijendar has joined #openstack-containers04:56
*** mkrai has joined #openstack-containers05:00
*** jerrygb has quit IRC05:03
*** jerrygb has joined #openstack-containers05:06
*** vijendar has quit IRC05:10
*** vijendar has joined #openstack-containers05:12
*** vijendar has quit IRC05:30
*** sheel has joined #openstack-containers05:33
*** vijendar has joined #openstack-containers05:34
*** vmud213 has joined #openstack-containers05:46
*** jerrygb has quit IRC05:53
openstackgerritfeng.shengqin proposed openstack/magnum: Remove google_containers in INSECURE_REGISTRY_URL  https://review.openstack.org/39235605:55
*** jerrygb has joined #openstack-containers05:57
*** vijendar has quit IRC05:57
*** vijendar has joined #openstack-containers06:01
*** vijendar has quit IRC06:11
*** vijendar has joined #openstack-containers06:16
*** jerrygb has quit IRC06:22
*** sergmelikyan has quit IRC06:26
*** jerrygb has joined #openstack-containers06:27
*** sergmelikyan has joined #openstack-containers06:27
*** sergmelikyan has quit IRC06:31
*** ramishra_ has quit IRC06:34
*** ramishra has joined #openstack-containers06:34
*** ramishra has quit IRC06:35
*** ramishra has joined #openstack-containers06:35
*** vijendar has quit IRC06:36
*** adrian_otto has quit IRC06:37
*** vijendar has joined #openstack-containers06:40
*** yuanying has quit IRC06:46
*** yuanying has joined #openstack-containers06:49
*** rcernin has joined #openstack-containers06:50
*** noama has quit IRC06:51
*** noama has joined #openstack-containers06:53
*** noama_ has joined #openstack-containers06:53
*** noama has quit IRC06:54
*** noama_ has quit IRC06:54
*** noama has joined #openstack-containers06:54
*** noama_ has joined #openstack-containers06:54
*** noama_ has quit IRC06:54
*** noama has quit IRC06:55
*** noama has joined #openstack-containers06:55
*** noama has quit IRC06:57
*** noama has joined #openstack-containers06:57
*** ramishra has quit IRC06:59
*** ramishra has joined #openstack-containers06:59
*** noama has quit IRC07:00
*** noama has joined #openstack-containers07:01
*** ramishra has joined #openstack-containers07:03
*** mjura has joined #openstack-containers07:04
*** vijendar has quit IRC07:06
*** jerrygb has quit IRC07:06
*** belmoreira has joined #openstack-containers07:09
*** vijendar has joined #openstack-containers07:10
*** jerrygb has joined #openstack-containers07:10
*** mjura has quit IRC07:11
*** mjura has joined #openstack-containers07:11
*** vijendar has quit IRC07:26
openstackgerritMerged openstack/magnum: [suse] Update copyright/ownership information  https://review.openstack.org/38934807:26
*** fragatina has joined #openstack-containers07:30
*** vijendar has joined #openstack-containers07:34
*** fragatina has quit IRC07:39
*** fragatina has joined #openstack-containers07:39
*** jerrygb has quit IRC07:42
*** jerrygb has joined #openstack-containers07:46
*** tonanhngo has joined #openstack-containers07:46
*** janonymous has joined #openstack-containers07:46
*** tobberyd_ has joined #openstack-containers07:47
*** tobberydberg has joined #openstack-containers07:47
*** openstackgerrit has quit IRC07:48
*** openstackgerrit has joined #openstack-containers07:48
*** ricolin_ has joined #openstack-containers07:48
*** ricolin_ has quit IRC07:49
*** ricolin has joined #openstack-containers07:49
*** vijendar has quit IRC07:50
*** jerrygb_ has joined #openstack-containers07:50
*** jerrygb has quit IRC07:52
*** vijendar has joined #openstack-containers07:54
*** tonanhngo has quit IRC07:54
*** jerrygb has joined #openstack-containers07:56
*** jerrygb_ has quit IRC07:58
*** tonanhngo has joined #openstack-containers08:00
*** mkrai has quit IRC08:02
*** jerrygb has quit IRC08:08
*** vijendar has quit IRC08:12
*** jerrygb has joined #openstack-containers08:13
*** vijendar has joined #openstack-containers08:18
*** jerrygb_ has joined #openstack-containers08:27
*** xek__ is now known as xek08:28
*** jerrygb has quit IRC08:29
*** vijendar has quit IRC08:30
*** tonanhngo has quit IRC08:31
*** vijendar has joined #openstack-containers08:37
*** vijendar has quit IRC08:41
*** vijendar has joined #openstack-containers08:44
*** vijendar has quit IRC08:54
*** GB21 has joined #openstack-containers08:55
*** noama has quit IRC08:57
*** noama has joined #openstack-containers08:58
*** vijendar has joined #openstack-containers08:59
*** chhavi has joined #openstack-containers09:00
*** jerrygb_ has quit IRC09:08
*** vijendar has quit IRC09:12
*** jerrygb has joined #openstack-containers09:12
*** GB21 has quit IRC09:15
*** vijendar has joined #openstack-containers09:19
*** takashi has joined #openstack-containers09:20
*** vijendar has quit IRC09:27
*** vijendar has joined #openstack-containers09:34
*** ricolin has quit IRC09:39
*** strigazi_AFK is now known as strigazi09:44
*** vijendar has quit IRC09:46
*** vijendar has joined #openstack-containers09:53
*** jerrygb has quit IRC09:54
*** jerrygb has joined #openstack-containers09:58
*** swatson_ has quit IRC09:59
*** vijendar has quit IRC10:06
*** vmud213 has quit IRC10:06
*** vmud213 has joined #openstack-containers10:07
*** vijendar has joined #openstack-containers10:10
tobberydbergHi! Having issues creating trustee: "TrusteeCreateFailed: Failed to create trustee". Have double checked the config according to documentation, and that user exists with correct roles etc. Does someone have any experience or tips on how to resolve this issue?10:11
strigazitobberydberg, what is in your trust section in magnum.conf?10:12
tobberydbergtrustee_domain_name = magnum10:16
tobberydbergtrustee_domain_admin_name = magnum_domain_admin10:16
tobberydbergtrustee_domain_admin_password = <pwd>10:16
tobberydbergHave also tried with trustee_domain_id and trustee_domain_admin_id which I saw in some docs...10:17
strigaziDo you use mitaka or newton?10:18
tobberydbergmitaka10:19
strigaziin mitaka, you must use definately id10:19
tobberydbergok, I'll switch to that and try again10:19
strigazirestart api and conductor after the change10:20
tobberydbergGet the same error. Authed as a user tenant trying to create a new "bay": First error is "Failed to create trustee"10:24
tobberydbergServer-side error: "Failed to create trustee dac48602-efcf-4b19-a0c9-2a30acb837c6 in domain 85333b0b485e4e539743df6ebdb3bb1110:24
tobberydbergIDs looks correct10:25
strigaziin [keystone_authtoken] do you have something like: auth_uri = http://controller:5000/v3 ?10:27
*** vijendar has quit IRC10:29
*** askb has quit IRC10:30
tobberydbergversion not specified in my string: "https://controller:5000"10:30
strigaziI think it should, have a look at the code snippet here: http://docs.openstack.org/developer/magnum/troubleshooting-guide.html#trustee-for-cluster10:31
strigaziI mean to test only this bit10:32
strigaziI'll try to remove the v3 and see what happens10:32
tobberydbergI'll try to add and see10:32
strigaziI got Failed to create trustee and trust for Cluster:10:34
*** vijendar has joined #openstack-containers10:34
strigaziThat might be it10:35
tobberydbergI get another error instead, so yes, that might be it... Will look into my new error and see what that can be10:36
tobberydbergThanks a lot! Might get back with more questions regarding my new error ;-)10:37
strigazibeware that for mitaka you need lbaas v110:37
strigaziThat is the usual next error10:38
tobberydbergahhh....belive I have that but will double check10:38
tobberydbergThanks10:38
*** vijendar has quit IRC10:47
*** vijendar has joined #openstack-containers10:53
*** takashi has quit IRC11:01
*** vijendar has quit IRC11:03
*** yatin has quit IRC11:08
*** vijendar has joined #openstack-containers11:09
*** Oku_OS is now known as Oku_OS-away11:12
*** GB21 has joined #openstack-containers11:15
*** vijendar has quit IRC11:17
*** vijendar has joined #openstack-containers11:21
*** yatin has joined #openstack-containers11:22
*** Oku_OS-away is now known as Oku_OS11:30
*** GB21 has quit IRC11:33
*** Administrator__ has quit IRC11:34
*** Administrator__ has joined #openstack-containers11:35
*** dave-mccowan has joined #openstack-containers11:35
*** zhugaoxiao has joined #openstack-containers11:37
*** Administrator__ has quit IRC11:40
*** vijendar has quit IRC11:44
*** mtanino has joined #openstack-containers11:46
*** EricGonczer_ has joined #openstack-containers11:46
*** vijendar has joined #openstack-containers11:49
*** yuanying_ has joined #openstack-containers11:49
*** chhavi has quit IRC11:50
*** mtanino has quit IRC11:52
*** EricGonc_ has joined #openstack-containers11:56
*** EricGonczer_ has quit IRC11:57
*** swatson_ has joined #openstack-containers11:59
*** chhavi has joined #openstack-containers12:04
*** yatin has quit IRC12:05
*** vijendar has quit IRC12:06
*** apuimedo has joined #openstack-containers12:07
*** vijendar has joined #openstack-containers12:11
*** EricGonc_ has quit IRC12:14
*** yatin has joined #openstack-containers12:17
*** vijendar has quit IRC12:23
*** apuimedo has quit IRC12:25
*** celebdor has joined #openstack-containers12:25
*** vijendar has joined #openstack-containers12:28
*** jerrygb has quit IRC12:42
*** vijendar has quit IRC12:42
*** yolanda has quit IRC12:44
*** yolanda has joined #openstack-containers12:44
*** jerrygb has joined #openstack-containers12:45
*** vijendar has joined #openstack-containers12:48
*** celebdor has quit IRC12:48
*** sheel has quit IRC13:00
*** vijendar has quit IRC13:01
*** swatson_ has quit IRC13:01
*** vmud213 has quit IRC13:02
*** yuanying_ has quit IRC13:05
*** mtanino has joined #openstack-containers13:11
*** vijendar has joined #openstack-containers13:12
*** vijendar has quit IRC13:18
*** vijendar has joined #openstack-containers13:27
*** absubram has joined #openstack-containers13:30
*** adrian_otto has joined #openstack-containers13:39
*** adrian_otto1 has joined #openstack-containers13:41
*** adrian_otto has quit IRC13:44
*** vijendar has quit IRC13:46
*** adrian_otto1 has quit IRC13:47
*** adrian_otto has joined #openstack-containers13:48
*** Drago5 has joined #openstack-containers13:51
*** vijendar has joined #openstack-containers13:54
*** GB21 has joined #openstack-containers14:01
*** vijendar2 has joined #openstack-containers14:01
*** vijendar_ has joined #openstack-containers14:02
*** vijendar1 has quit IRC14:03
*** vijendar has quit IRC14:03
*** Drago5 is now known as Drago14:04
*** chris_hultin|AWA is now known as chris_hultin14:11
*** Guest37512 has quit IRC14:18
*** rods has joined #openstack-containers14:20
*** EricGonczer_ has joined #openstack-containers14:26
*** anush has quit IRC14:36
*** chhavi has quit IRC14:41
*** mtanino has quit IRC14:52
*** mtanino has joined #openstack-containers14:53
*** randallburt has joined #openstack-containers14:54
*** syed_ has joined #openstack-containers14:55
*** randallburt has quit IRC14:58
*** vijendar2 has quit IRC14:59
*** vijendar_ has quit IRC14:59
*** randallburt has joined #openstack-containers15:01
*** vijendar has joined #openstack-containers15:03
*** vijendar_ has joined #openstack-containers15:05
*** srwilkers has joined #openstack-containers15:08
*** vijendar_ has quit IRC15:13
*** yuanying_ has joined #openstack-containers15:17
*** anush has joined #openstack-containers15:17
*** muralia_ has joined #openstack-containers15:18
*** muralia has quit IRC15:19
*** yuanying_ has quit IRC15:21
*** vijendar_ has joined #openstack-containers15:22
*** vijendar1 has joined #openstack-containers15:24
*** vijendar has quit IRC15:25
openstackgerritRandall Burt proposed openstack/magnum: Add cluster driver encapsulation spec  https://review.openstack.org/38983515:30
openstackgerritOpenStack Proposal Bot proposed openstack/magnum: Updated from global requirements  https://review.openstack.org/39273715:33
openstackgerritOpenStack Proposal Bot proposed openstack/magnum-ui: Updated from global requirements  https://review.openstack.org/39273815:33
openstackgerritSpyros Trigazis proposed openstack/magnum: WIP: Make cinder volume optional  https://review.openstack.org/39183015:41
*** chhavi has joined #openstack-containers15:50
adrian_ottorandallburt: the pep8 job failed on https://review.openstack.org/38983515:52
adrian_ottoI voted +2 anyway, but we should address it regardless.15:53
*** adrian_otto has quit IRC15:53
randallburtadrian_otto:  ugh. stupid line length limitations. 1 sec15:53
*** vijendar1 has quit IRC15:59
*** vijendar_ has quit IRC16:00
DragoHi strigazi, jvgrant16:00
strigaziHi16:00
jvgrantgood morning16:00
jvgrantor evening :)16:00
openstackgerritRandall Burt proposed openstack/magnum: Add cluster driver encapsulation spec  https://review.openstack.org/38983516:00
*** adrian_otto has joined #openstack-containers16:01
randallburtadrian_otto: should be fixed now ^^16:01
*** srwilkers has quit IRC16:01
randallburtadrian_otto: should be fixed now16:01
adrian_ottotx randallburt16:02
randallburtnp16:02
jvgrantstrigazi, thanks for feedback on spec16:02
jvgrantDrago, did you get a chance to look at it?16:02
Dragojvgrant: No16:02
*** adrian_otto has quit IRC16:02
Dragojvgrant: I also didn't get a chance to write the flattening spec16:02
*** anushkrishnamurt has joined #openstack-containers16:02
DragoLooking now16:03
*** vijendar_ has joined #openstack-containers16:04
jvgranti don't know if i explained the alternative well enough to cover what you were thinking it would add Drago16:04
jvgrantfeel free to add more if you feel strongly on it16:05
*** tobberyd_ has quit IRC16:05
*** tobberydberg has quit IRC16:06
DragoOkay16:06
jvgranti don't think that one was as divided an idea as the flattening part16:07
*** rcernin has quit IRC16:09
*** vijendar_ has quit IRC16:10
*** anush has quit IRC16:10
*** vijendar_ has joined #openstack-containers16:11
strigazijvgrant commented on versions16:14
strigazijvgrant: I commented on versions16:14
*** vijendar_ has quit IRC16:14
jvgrantstrigazi: confused still on the uuid comment.  each version will still have different uuid. I'm just saying that on cluster create if they use the uuid of the parent or any obsolete version it will use the latest version same as with the name16:15
*** srwilkers has joined #openstack-containers16:16
strigazijvgrant. I get it. But having the same uuid in many entries seems to me really wrong16:16
jvgrantthey won't. each entry has a different uuid16:17
strigaziok16:17
strigaziWhich uuid is the same then?16:17
strigazithe parent?16:17
jvgrantright now you can use the uuid or name on cluster-create16:17
strigaziI said yes to this16:17
strigaziyeap16:17
strigazilet me read it one more time16:18
jvgrantso i'm saying that when it checks to use that template it will use latest version not necessarily that exact uuid template entry16:18
jvgranti might just be explaining it poorly16:18
jvgranti think i was trying to get across that whether you use name or uuid when specifying your template versioning would still work16:19
jvgrantthat is because we currently don't limit templates from sharing the same name16:20
strigaziso16:20
jvgrantso there are cases where the uuid must be used16:20
strigaziwhen you do ct-update you go from version n to n+1 and the uuid changes, but16:21
strigaziyou can always refer to the v1 uuid? And get by default the latest?16:21
*** adrian_otto has joined #openstack-containers16:22
strigazicluster-create -ct <v1_uuid> and you get the latest. That is what you mean?16:23
jvgrantfor implementation, i was thinking that whenever you use a template the code will look at the parent id of the entry. It will then make sure the latest version that "parent_id" group is used16:23
jvgrantyes16:23
jvgrantwhen you use cluster-create -ct <template name/uuid> it will always get the latest version in the set16:24
strigazimakes sense16:24
jvgrantthey could use the name or uuid from any version in the set and it would always use latest16:24
jvgrantso if they changed names, or used a uuid from a middle version, it would still work16:24
jvgranthaving the parent_id in each entry links them all together so it will be a pretty simple check16:25
DragoThat last point is a bit odd16:25
strigaziit is a bit strange behavior, I don't disagree16:25
Drago*about the middle version uuids working16:25
strigaziDrago +116:26
jvgranti don't know if anyone would do it16:26
jvgrantbut it does allow us to allow the name to change and still have backward compatiblity with both names16:27
strigaziEven if we change the name16:28
strigaziwe can only allow the latest name and uuid to work16:28
DragoThe ambiguity between using the v1 uuid to refer to a specific version and using it to refer to the CT in general rubs me the wrong way16:28
jvgrantstrigazi: we can easily do that as well16:29
DragoThe "simplicity" of using v1 as the parent is going to force us to deal with corner cases, a lot of which we're talking about now16:30
strigaziThat is why I think that all old version should be marked as delete16:31
strigazisorry16:31
strigaziobsolete16:31
DragoThe way it's explained in the spec, I don't see any need for obsolete16:31
strigaziand allow only the latest to create clusters16:31
strigaziDrago, n+1 is the latest, and we list only that one16:32
jvgrantright now the spec only allows 1 version to be non-obsolete16:32
strigazibut let's say that the user gives version n16:32
jvgrantit is always the latest16:33
strigaziusing the old uuid16:33
strigaziwhat then?16:33
jvgrantmy thought is it just jumps to the latest16:33
jvgrantwhy not, we know what the latest it16:33
jvgrantis16:33
*** zul_ has joined #openstack-containers16:33
*** mjura has quit IRC16:33
*** zul_ has quit IRC16:33
jvgrantwe could just error out, or we could jump to what is the valid version they probably mean16:33
DragoI would either allow it, or give an error, not implicitly use a different version16:33
jvgranti can see it both ways16:33
strigazierror out16:34
strigaziand say use the latest16:34
DragoWhy wouldn't an operator want to have two valid versions available?16:34
DragoFor, say, the last two versions of k8s supported16:34
strigazimaintenance overhead, users could create old clusters16:35
DragoIf we're going to have an obsolete field on every version, we could enable a use case like that at some point16:35
*** zul has quit IRC16:35
*** zul has joined #openstack-containers16:36
strigaziok, with obsolete field makes sense16:36
jvgranti think those would be 2 separate templates16:36
strigaziand if an operator wants he could support many versions16:36
DragoA transition period is always a nice thing to have for your users16:37
strigaziI think that the best practice is to maintain one\16:37
strigaziYes, but16:37
strigaziHave a transition period of created cluster is what we want16:38
jvgranthmmm... this makes me lean towards the alternative implementation if you want to allow more than one version supported at a time16:38
randallburtif you don't want users creating things with old versions, don't let them. if you do, then be explicit when they do something that's "wrong" and tell them what it was.16:38
strigaziAllow them to create the old ones is not good16:38
randallburtbut don't do "unexpected things"16:38
strigazirandallburt. that's why I want only the latest to be available16:39
strigazik8s 1.2 is over folks, do 1.416:39
*** zul has quit IRC16:39
jvgranti think the easiest answer is we lock the name. The user always uses the same name(or parent_uuid) to target a template, and the latest version is always used16:39
strigazithose who have 1.2 can upgrade later16:39
*** zul has joined #openstack-containers16:39
jvgrantthe uuid's of the versions are not known to the users16:40
randallburtI can get behind that. Create is only for latest version while keeping the old ones around for updates (though still not convinced that's totally needed)16:40
*** anushkrishnamurt has quit IRC16:40
strigaziIf you have the old versions you can monitor the old cluster and plan the upgrades16:41
strigaziotherwise you will query based on a set of fields16:41
jvgrantyou will still see the versions, just on create you will only be able to use the latest16:44
randallburtso sorry to butt in, but with this spec does that mean that if templates are 1-to-1 with drivers that we'd have to have a separate driver for each version or do we envision doing the hoop jumping in the driver?16:45
jvgrantno, these will be within the current attributes of the clusters/nodegroups16:46
strigazi+116:46
strigazi+1 to jaycen16:47
*** chhavi has quit IRC16:47
Dragorandallburt: Templates are not 1 to 116:47
randallburtk16:48
*** Drago has quit IRC16:48
jvgrantok, i "think" we have understanding on cluster-create usage now.  Name and uuid(of v1) will be the only valid ways to specify a version for creation16:49
*** Drago has joined #openstack-containers16:49
jvgrantand it will always use the latest version16:49
jvgrantname cannot be changed or updated?16:49
DragoIf name is common to all versions, that's another benefit of having a separate ParentTemplate table16:50
strigaziI think the way Jaycen descibed it, the v1 CT will act like the ParentTemplate16:51
DragoYes, but that's the key difference - it will "act" like the ParentTemplate16:52
jvgrantyeah, it would be. But it wouldn't be in a separate table or a different type of entry16:52
strigaziThey way I described it, only the latest is valid16:52
strigaziany reference to create from an old version would return an error16:53
DragoIf you only allow the lastest version and have a ParentTemplate with a latest version field, you don't have to mark anything as obsolete16:53
*** belmoreira has quit IRC16:53
*** Drago5 has joined #openstack-containers16:53
DragoYou also don't have marked_for_delete in every template, just one place16:53
*** Drago has quit IRC16:54
*** Drago5 is now known as Drago16:54
strigaziWhat is the advantage of this? Computational cost?16:55
DragoYou're structuring the data according to how it will actually be used16:55
strigaziThe Parent table you descibe would be better to be a sql view16:56
strigaziThat's what a view does16:56
DragoIf there is only 1 common name for N versions, why have a name field on every version? If deletion must apply identically to every version, why have a value for each version?16:57
Dragostrigazi: I am not talking about a view16:57
*** celebdor has joined #openstack-containers16:58
*** vijendar has joined #openstack-containers16:58
strigaziIf deletion must  apply identically to every version"  what do you mean?16:58
DragoParentTemplate is a table that would be a one-to-many relationship with the versions16:58
jvgrantit is all or nothing right now on delete16:58
*** vijendar has quit IRC16:58
Dragostrigazi: ^16:58
DragoYou don't mark specific versions to delete, you mark them all16:58
*** srwilkers has quit IRC16:59
*** celebdor has quit IRC16:59
*** vijendar has joined #openstack-containers16:59
jvgrantwhich is why in current spec i use the parent entry as the only one that matters for delete flag16:59
Dragobut without a separate table for that common information, you have to duplicate values across all the version entries16:59
strigaziSo, we can not mark them for deletion16:59
*** celebdor has joined #openstack-containers16:59
Dragojvgrant: Which I find to be hacky17:00
jvgrantwe are talking the exact same functionality, just whether to use a new table and parent entry or use the initial parent template entry as that17:00
strigaziyeap the functionality would be tha same17:01
strigaziyeap the functionality would be the same17:01
jvgranti get where Drago is coming from on this.  Structurally it makes sense and it would be clean. But I also don't like the extra overhead of a new table and objects that have to be maintained17:02
DragoThe separate table is to pull out common fields so that the values don't have to be duplicated. That's what relational DBs and foreign keys are for17:02
Dragojvgrant: You have the overhead of maintaining the constraints in code that should, and could, be in your DB just by the way the data is organized17:03
jvgranti see it for when we have the attributes between cluster and cluster template since taht is like 30 fields, but for this it is only 1 or 217:03
DragoAnd on top of that, the developer burden of having to deal with the logic of "all the entries being the same structure, but a specific set of entries is really different and you should ignore things on the rest"17:04
strigaziWe can count the computational cost of both cases. With the parent approach are we going to need a table for NGT too?17:05
DragoYep17:06
strigaziSince the functionality is the same it's not a blocker for me17:06
jvgrantnot a blocker for me either. just implementation opinion17:07
strigaziWe need to elaborate on the second approach17:07
DragoIf you want to get all the data in one DB query, you can do a JOIN between ParentTemplate and ClusterTemplate17:07
strigazitrue17:07
strigaziDrago, I think we can remove the field in line 137 then17:08
strigaziSo name, uuid, latest_version, is_deleted17:09
jvgrantyep17:09
Dragostrigazi: In the DB, yes. We can of course do anything we want and have such an attribute in the python object17:09
*** adrian_otto has quit IRC17:11
*** vijendar has quit IRC17:11
DragoI'm pretty sure it will be more painful computationally to treat v1 as the parent than it would be to use a ParentTemplate17:11
jvgranti agree with that. not that painful but it would be some17:12
strigazibe right back17:12
jvgranti'll update the spec with more in the alternative... or are we deciding that we are switch this to the main option?17:13
DragoFor example, to get all useful information on the latest CT version (which is what you want most of the time)17:13
Dragoah, yes this is ugly17:13
DragoUSING the uuid of the v1 template, since that's the "parent"17:13
DragoYou'd have to do a self-join on the CT table, with the UUID of the parent and the constraint NOT obsolete17:14
Dragojvgrant: We can discuss it more17:14
jvgrantthat is what would give you latest17:14
Dragojvgrant: ^ Do you think that would get the latest CT version in one query?17:15
jvgrantshould be parent_uuid + obsolete=false17:15
DragoFor a moment I thought it would require 2 queries, but nevermind. It will probably be slower than the ParentTemplate version, but not by much to matter17:15
Dragojvgrant: Right17:15
DragoNot as ugly as I was thinking :)17:16
jvgrantwhich is why i said before it didn't matter what name or uuid they give since we always just look at parent_uuid and search for non-obselete17:16
DragoBut you would then have some fields you have to ignore (and hopefully not accidentally use the wrong version of the field, since you're getting two copies)17:16
DragoWith ParentTemplate, you don't have to deal with any extra fields17:17
Dragoin your code17:17
jvgrantyeah, but since it is only a couple, the trade offs are really close between the options17:18
Dragojvgrant: With ParentTemplate there's also no ambiguity between specifying the UUID for a particular version or the one that represents "the" CT17:18
*** chetna has joined #openstack-containers17:18
strigazi+117:18
jvgrantyeah you are always specifying the parentTemplate17:19
strigaziin list queries we only query the Parent table17:19
jvgrantwhich was like my limitation on only supporting the v1 name/uuid17:19
Dragojvgrant: But when you're choosing the fields to expose outside of the DB API layer, you have two sets, and you have pick the right one for ALL of them, not just a couple17:19
DragoIt's just that a couple come from one and the rest come from another17:20
jvgrantdo we think that we will had additional versioning features in the future?17:20
jvgrantto make it more complex?17:20
strigaziI think not17:20
DragoAre you joking17:20
DragoOf course we will17:21
Drago:P17:21
*** harlowja has quit IRC17:21
strigaziVersion all the objects17:21
jvgrantwell, i'm about as dead center on this as you can come, so i'm ok with either option now :P17:21
jvgranti think we are set on what the functionality will be, so i'm ok either way17:22
strigaziWith one more iteration on the alteranative option we can decide17:23
DragoIf there were literally no additional versioning features that would ever be added, I would probably still be on the side of ParentTemplate, but since ParentTemplate is more future-proof, I think it's the better option in that regard too17:23
jvgrantok, i'll work with Drago on that17:23
strigaziI'll add a few comments on the alternate option17:24
DragoThanks strigazi17:24
jvgrantDrago: i'll do an update with some of the changes from comments and another pass on the ParentTemplate section. Then i'll have you help be expand it17:26
Dragojvgrant: Alright, sounds good17:27
Dragojvgrant: I'll be back in 30. I've run out of food in my house!17:28
jvgrantDrago: yeah don't go hungry :)17:29
*** fragatina has quit IRC17:40
*** vijendar has joined #openstack-containers17:42
*** vijendar_ has joined #openstack-containers17:43
*** harlowja has joined #openstack-containers17:44
*** vijendar has quit IRC17:47
*** tonanhngo has joined #openstack-containers17:49
*** anush has joined #openstack-containers17:55
*** srwilkers has joined #openstack-containers18:01
*** sergmelikyan has joined #openstack-containers18:01
*** Jeffrey4l has quit IRC18:02
*** vijendar_ has quit IRC18:02
*** vijendar has joined #openstack-containers18:02
*** vijendar_ has joined #openstack-containers18:03
*** vijendar has quit IRC18:07
*** srwilkers has quit IRC18:08
openstackgerritRandall Burt proposed openstack/magnum: Add cluster driver encapsulation spec  https://review.openstack.org/38983518:09
randallburtDrago:  so embarassing18:10
*** tonanhngo has quit IRC18:10
Dragorandallburt: :)18:11
randallburtthat's why we code review kids.18:11
*** anush has quit IRC18:14
*** jvgrant_ has joined #openstack-containers18:15
*** yuanying_ has joined #openstack-containers18:17
openstackgerritJaycen Grant proposed openstack/magnum: Spec for adding template versions  https://review.openstack.org/39232718:17
*** openstackgerrit has quit IRC18:18
*** openstackgerrit has joined #openstack-containers18:18
*** jvgrant has quit IRC18:18
Dragojvgrant_: I figured out a better name for ParentTemplate18:22
*** yuanying_ has quit IRC18:22
Dragojvgrant_: ClusterTemplate and ClusterTemplateVersion18:22
jvgrant_Drago: like it18:22
Dragojvgrant_: Is it ready for me to edit?18:22
swatsonDrago: That's an improvement for sure18:22
jvgrant_Drago: ParentTemplate was awkward18:22
DragoHeh, yeah18:22
jvgrant_Drago: go for it18:22
DragoThanks18:22
*** GB21 has quit IRC18:24
Dragojvgrant_, swatson: I have a k8s question18:24
DragoI have a Magnum cluster, which is running k8s 1.2. From what I can tell, ConfigMaps should be available. However, I get a 404 when doing `kubectl get configmaps`18:25
DragoI had the same problem with deployments, but I can enable those by enabling extensions/v1beta118:26
*** srwilkers has joined #openstack-containers18:26
*** anush has joined #openstack-containers18:26
swatsonDrago: My expertise at this point is pretty Magnum-specific :P18:27
Dragoswatson: Sadly, mine too :(18:27
DragoAnd documentation for 1.2 is sparse18:30
swatsonDrago: Yeah I'm not the guy to ask for k8s :X18:30
*** vijendar_ has quit IRC18:35
*** vijendar_ has joined #openstack-containers18:37
*** vijenda__ has joined #openstack-containers18:37
*** srwilkers has quit IRC18:40
*** vijendar_ has quit IRC18:41
*** yuanying has quit IRC19:03
*** celebdor has quit IRC19:07
*** anush has quit IRC19:11
*** jerrygb has quit IRC19:21
*** jerrygb has joined #openstack-containers19:22
*** vijenda__ has quit IRC19:24
*** jerrygb has quit IRC19:26
Dragojvgrant_: In the spec, using "template" instead of "ClusterTemplate" is awkward19:29
jvgrant_Drago: i was trying to make in generic so it is valid for all the templates(both cluster and nodegroup)19:36
jvgrant_if it is easier to understand we can just make it all ClusterTemplate and then we can make a section that says the same applies to NodeGroupTemplate as well19:37
Dragojvgrant_: I realize that. It just makes it harder to use concrete examples19:37
Dragojvgrant_: So far, I can work with it19:38
*** jperry has joined #openstack-containers19:38
jvgrant_Drago: ok, it not I don't have a problem changing it19:38
*** jerrygb has joined #openstack-containers19:42
*** anush has joined #openstack-containers19:44
*** rcernin has joined #openstack-containers19:45
*** dave-mccowan has quit IRC19:48
*** dave-mcc_ has joined #openstack-containers19:48
*** adrian_otto has joined #openstack-containers19:56
*** openstack has joined #openstack-containers20:00
*** anushkrishnamurt has joined #openstack-containers20:05
*** anush has quit IRC20:05
*** sergmelikyan has joined #openstack-containers20:09
*** anushkrishnamurt has quit IRC20:09
*** openstackgerrit has quit IRC20:18
*** openstackgerrit has joined #openstack-containers20:18
*** sergmelikyan has quit IRC20:19
*** sergmelikyan has joined #openstack-containers20:20
*** sergmelikyan has quit IRC20:37
*** sergmelikyan has joined #openstack-containers20:44
*** adrian_otto has quit IRC20:45
*** adrian_otto has joined #openstack-containers20:47
*** adrian_otto has quit IRC20:49
*** sergmelikyan has quit IRC20:49
*** code34 has joined #openstack-containers20:54
*** adrian_otto has joined #openstack-containers20:54
code34hello, i need assistance with magnum during creation of cluster, i have an urlerror msg templates/cluster.yaml doesnt exist20:55
*** adrian_otto has quit IRC20:55
code34does anyone know how to solve this ? it s on newton proposed version20:55
*** adrian_otto has joined #openstack-containers20:56
*** EricGonczer_ has quit IRC20:57
jvgrant_code34: can you share the ClusterTemplate info you are using?20:59
code34it s a cluster template that i build before20:59
code34from the command line20:59
jvgrant_it worked with the previous version?21:00
*** yuanying has joined #openstack-containers21:00
code34i dont know its the first time i build it :)21:00
*** askb has joined #openstack-containers21:00
jvgrant_i have to run to a quick meeting for 30 min but if you can share the clustertemplate and cluster settings you have and any logs of the error, i can take a look21:01
jvgrant_when i get back21:01
code34ok :)21:02
code34thanks you21:02
*** sergmelikyan has joined #openstack-containers21:03
*** yuanying has quit IRC21:05
*** dave-mcc_ has quit IRC21:24
*** vijendar has joined #openstack-containers21:28
*** adrian_otto has quit IRC21:34
openstackgerritDrago proposed openstack/magnum: Spec for adding template versions  https://review.openstack.org/39232721:51
*** Drago has quit IRC21:51
*** Drago2 has joined #openstack-containers21:54
Drago2test21:54
jvgrant_Drago2: i think it worked21:54
Drago2Yeah, but this is me on freenode's webchat, while I wait for adium to reconnect21:55
Drago2jvgrant_: Tell me what you think :)21:56
*** muralia_ has quit IRC21:56
jvgrant_Drago2: I think that is enough :) It makes sense. It can be done the other way as well, but this is cleaner21:57
*** Drago5 has joined #openstack-containers21:59
Drago2jvgrant_: I was trying to dispel the notion that using one table had more advantages than drawbacks22:00
*** Drago2 has quit IRC22:00
jvgrant_Drago2: i think it is just general fear of the db :)22:00
*** adrian_otto has joined #openstack-containers22:01
Drago5Fear of the DB is silly22:01
*** Drago5 is now known as Drago22:01
jvgrant_agreed but it happens as developers often would rather add more code around it then make the db more complicated22:02
*** jperry has quit IRC22:02
*** harlowja has quit IRC22:02
Dragojvgrant_: The DB can do so much for you! And wielded correctly, it can really reduce the amount of pain you go through writing and debugging code22:03
DragoI know this because of the things I see over on the Heat team22:03
jvgrant_Drago: which is why it is good to have people to push us in the right direction. I think this is even more important on the attributes table as migrations and updates are a pain. I don't want to have to update them twice when we rename something22:04
Drago+122:04
jvgrant_and i know a thing or 2 about renaming :)22:05
DragoYou more than most!22:05
jvgrant_i'll let people read through the new alternative info you put, but then i'll switch it over to being the main option for the spec22:07
jvgrant_it is good info as it will be the same arguement for attributes22:07
*** chris_hultin is now known as chris_hultin|AWA22:09
Dragojvgrant_: Cool22:11
openstackgerritDrago proposed openstack/magnum: Spec for adding template versions  https://review.openstack.org/39232722:12
*** Drago has quit IRC22:12
*** adrian_otto has quit IRC22:12
*** tonanhngo has joined #openstack-containers22:13
*** drago2 has joined #openstack-containers22:15
drago2jvgrant_: Do you think I can fix the pep8 error (line 158, unexpected indentation) by adding a blank line above it?22:18
jvgrant_maybe...22:19
*** Drago5 has joined #openstack-containers22:20
*** askb has quit IRC22:20
jvgrant_i think as long as there is a line it won't compare the indent to the above22:20
*** sergmelikyan has quit IRC22:21
openstackgerritDrago proposed openstack/magnum: Spec for adding template versions  https://review.openstack.org/39232722:22
*** askb has joined #openstack-containers22:22
jvgrant_yep that will fix it22:22
Drago5I hope so22:22
*** drago2 has quit IRC22:22
jvgrant_or you could fight with pep8 all afternoon :)22:23
*** vijendar has quit IRC22:24
Drago5jvgrant_: I'll have the attributes spec up tonight, now that I'm done with that22:28
*** Drago5 is now known as Drago22:28
*** flaper87 has quit IRC22:29
jvgrant_cool22:29
*** adrian_otto has joined #openstack-containers22:30
*** adrian_otto has quit IRC22:30
*** vijendar has joined #openstack-containers22:33
*** adrian_otto has joined #openstack-containers22:33
*** vijendar_ has joined #openstack-containers22:33
*** chetna has quit IRC22:36
*** chetna has joined #openstack-containers22:37
*** vijendar has quit IRC22:37
*** syed_ has quit IRC22:45
*** sergmelikyan has joined #openstack-containers22:57
*** david-lyle has quit IRC23:04
*** chris_hultin|AWA is now known as chris_hultin23:08
*** harlowja has joined #openstack-containers23:08
*** absubram has quit IRC23:09
*** yuanying has joined #openstack-containers23:11
*** chris_hultin is now known as chris_hultin|AWA23:15
*** yuanying has quit IRC23:16
*** mtanino has quit IRC23:20
*** swatson_ has joined #openstack-containers23:24
*** david-lyle has joined #openstack-containers23:30
*** rcernin has quit IRC23:31
*** dave-mccowan has joined #openstack-containers23:31
chetnaI am trying to attach docker volume to CoreOS cluster. When I attempt to delete the cluster deletion fails. Resource DELETE failed: KeyError: resources.kube_masters.resources[0].resources.master_wait_condition: 'outputs'"23:34
chetnaCould someone please suggest what could be wrong. I have attached details in https://bugs.launchpad.net/magnum/+bug/163874123:34
openstackLaunchpad bug 1638741 in Magnum "Magnum: k8s CoreOS Cluster deletion fails with docker volume attached" [Undecided,New]23:34
*** chetna has quit IRC23:40

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