Tuesday, 2016-11-29

*** hongbin has quit IRC00:02
*** yuanying has joined #openstack-containers00:03
*** yuanying_ has joined #openstack-containers00:03
*** yuanying has quit IRC00:08
*** catintheroof has joined #openstack-containers00:08
*** mtanino has quit IRC00:27
*** huzhengchuan has joined #openstack-containers00:52
*** dave-mccowan has quit IRC00:56
*** anush has joined #openstack-containers00:59
*** vijendar has joined #openstack-containers00:59
*** tonanhngo has quit IRC01:01
*** vijendar_ has joined #openstack-containers01:05
*** vijendar has quit IRC01:09
*** tonanhngo has joined #openstack-containers01:10
*** tovin07 has joined #openstack-containers01:10
*** anush has quit IRC01:11
*** huzhengchuan has quit IRC01:13
*** huzhengchuan has joined #openstack-containers01:13
*** tonanhngo has quit IRC01:14
*** vijendar_ has quit IRC01:30
*** EricGonczer_ has joined #openstack-containers01:31
*** EricGonczer_ has quit IRC01:32
*** askb has quit IRC01:32
*** yamamot__ has joined #openstack-containers01:41
*** yamamot__ has quit IRC01:44
*** askb has joined #openstack-containers01:44
*** EricGonczer_ has joined #openstack-containers01:48
*** EricGonczer_ has quit IRC01:48
*** EricGonczer_ has joined #openstack-containers01:49
*** EricGonczer_ has quit IRC01:49
*** askb has quit IRC01:52
*** tkarke has quit IRC01:55
*** sdake_ has joined #openstack-containers01:55
*** sdake has quit IRC01:58
*** anush has joined #openstack-containers02:01
*** anush has quit IRC02:02
*** yamamot__ has joined #openstack-containers02:04
*** catintheroof has quit IRC02:16
*** syed__ has quit IRC02:16
*** catintheroof has joined #openstack-containers02:16
*** catintheroof has quit IRC02:20
*** hongbin has joined #openstack-containers02:22
*** vijendar has joined #openstack-containers02:28
*** huzhengchuan has quit IRC02:33
*** huzhengchuan has joined #openstack-containers02:45
*** kevinz has joined #openstack-containers02:58
*** kevinz has quit IRC02:59
*** kevinz has joined #openstack-containers02:59
*** yuanying_ has quit IRC03:00
kevinzd03:01
*** syed__ has joined #openstack-containers03:16
*** yamamo___ has joined #openstack-containers03:22
*** catintheroof has joined #openstack-containers03:25
*** yamamot__ has quit IRC03:26
*** vijendar has quit IRC03:27
*** vijendar has joined #openstack-containers03:28
*** vijendar has quit IRC03:52
*** Jeffrey4l has quit IRC03:54
*** Jeffrey4l has joined #openstack-containers03:55
*** yuanying has joined #openstack-containers03:59
*** kevinz has quit IRC04:02
*** mdnadeem has joined #openstack-containers04:03
*** tonanhngo has joined #openstack-containers04:08
*** tonanhngo has quit IRC04:09
*** jwcroppe has joined #openstack-containers04:21
*** tonanhngo has joined #openstack-containers04:21
*** tonanhngo has quit IRC04:22
*** chhavi has joined #openstack-containers04:22
*** catinthe_ has joined #openstack-containers04:23
*** hongbin has quit IRC04:24
*** catintheroof has quit IRC04:26
*** catinthe_ has quit IRC04:26
*** catintheroof has joined #openstack-containers04:27
*** catintheroof has quit IRC04:27
*** masayukig has quit IRC04:40
*** masayukig has joined #openstack-containers04:43
*** ram_ has joined #openstack-containers04:48
*** snarwade has joined #openstack-containers04:49
*** tonanhngo has joined #openstack-containers05:04
*** tonanhngo has quit IRC05:06
*** ramishra has quit IRC05:16
*** ramishra has joined #openstack-containers05:18
*** dimtruck is now known as zz_dimtruck05:19
*** PanFengyun has joined #openstack-containers05:21
*** Drago1 has joined #openstack-containers05:40
*** chhavi has quit IRC05:42
*** Drago1 has quit IRC05:44
*** bks has joined #openstack-containers05:46
*** vimal has joined #openstack-containers05:48
*** sdake_ has quit IRC05:52
*** vijendar has joined #openstack-containers05:53
*** vijendar has quit IRC05:55
*** vijendar has joined #openstack-containers05:55
*** chhavi has joined #openstack-containers05:56
*** vijendar has quit IRC06:00
*** drago_ has joined #openstack-containers06:05
*** Jeffrey4l has quit IRC06:12
*** Jeffrey4l has joined #openstack-containers06:12
*** Drago1 has joined #openstack-containers06:13
*** yatin has joined #openstack-containers06:24
*** jwcroppe has quit IRC06:30
*** ricolin has joined #openstack-containers06:38
*** ricolin has quit IRC06:48
*** ricolin has joined #openstack-containers06:49
*** mjura has joined #openstack-containers06:53
*** mjura has quit IRC07:01
*** mjura has joined #openstack-containers07:01
*** yamamo___ has quit IRC07:02
*** chhavi has quit IRC07:03
*** chhavi has joined #openstack-containers07:06
*** syed__ has quit IRC07:16
*** yuanying has quit IRC07:20
*** pcaruana has joined #openstack-containers07:21
openstackgerritEli Qiao proposed openstack/magnum: functional: don't create flavors if ironic testing  https://review.openstack.org/40405807:26
*** yuanying has joined #openstack-containers07:26
*** chhavi has quit IRC07:28
*** takashi has joined #openstack-containers07:30
*** ricolin has quit IRC07:39
*** yamamot__ has joined #openstack-containers07:39
*** zenoway has joined #openstack-containers07:45
*** vijendar has joined #openstack-containers08:00
*** vijendar has quit IRC08:05
*** yuanying has quit IRC08:17
openstackgerritOpenStack Proposal Bot proposed openstack/magnum-ui: Imported Translations from Zanata  https://review.openstack.org/40407708:30
*** yolanda has quit IRC08:31
*** yolanda has joined #openstack-containers08:43
*** rcernin has joined #openstack-containers08:56
*** kevinz has joined #openstack-containers09:02
*** ricolin has joined #openstack-containers09:03
openstackgerritEli Qiao proposed openstack/magnum: Doc: update server type in userguide  https://review.openstack.org/40409709:05
*** chhavi has joined #openstack-containers09:18
*** hvlad has joined #openstack-containers09:21
*** bobbyd has joined #openstack-containers09:34
bobbydMorning! :)09:34
*** bobby___ has joined #openstack-containers09:36
bobby___Morning :)09:37
*** bobbyd has quit IRC09:37
bobby___Hope y’all well. Looking for some tips with magnum if anyone is available? We’ve just upgraded to Mitaka, but not having any luck with the Magnum client connecting.09:37
bobby___magnum bay-list09:38
bobby___ERROR: public endpoint for container service not found09:38
bobby___OS_AUTH_URL=https://mydomain.com:1300009:39
bobby___OS_PASSWORD=xxx-xxx-xxx-xxx09:39
bobby___OS_PROJECT_ID=12312312312312312309:39
bobby___OS_PROJECT_NAME=xxxxxxx Bobby Demo09:39
bobby___OS_USERNAME=xxxxxxx@xxxxxx.com09:39
bobby___OS_IDENTITY_API_VERSION=309:39
bobby___Any recommendations?09:39
bobby___TIA :)09:39
openstackgerritMathieu Velten proposed openstack/magnum: Remove underscores from Nova server names  https://review.openstack.org/40267709:41
Drago1bobby___: What's your magnumclient version?09:47
*** openstackgerrit has quit IRC09:48
*** openstackgerrit has joined #openstack-containers09:49
*** yolanda has quit IRC09:55
*** yolanda has joined #openstack-containers09:57
*** vijendar has joined #openstack-containers10:02
ram_Hi all. Kolla, magnum and kuryr serve different goals right. Just I came to know the functionality/purpose of each project from https://www.openstack.org/videos/barcelona-2016/containers-and-openstack-mapping-the-landscape. I want to do a small POC on these three projects. For this what I need to do with the minimal setup. Please anyone provide me the details.10:04
*** vijendar has quit IRC10:07
bobby___@Drago1 magnum --version10:21
bobby___2.3.110:21
bobby___➜  ~10:21
*** tovin07 has quit IRC10:29
Drago1bobby___: It sounds like the endpoint is missing from the service catalog10:29
bobby___Yeah,I agree. Is this something that was missed when upgrading to Mitaka?10:32
bobby___How can we populate the service catalog? (Sorry, I’m not the one that upgraded - I’ve not installed/rolled out the openstack stuff) - I just consume the awesomeness :)10:32
Drago1bobby___: Magnum's project type was changed from container to container-infra in either Mitaka or Newton10:33
Drago1bobby___: You may need to add endpoints for container-infra10:34
Drago1bobby___: Example: http://docs.openstack.org/liberty/install-guide-rdo/keystone-services.html10:35
Drago1Replace keystone with magnum and identity with container-infra10:36
yatinDrago1, bobby___ : i think in newton we changed from container to container-infra10:39
Drago1ram_: The kolla/magnum part will not be too difficult. I would start with http://docs.openstack.org/developer/kolla/quickstart.html to get an openstack environment with magnum up and running10:40
bobby___ok cool thanks guys - will take al ook10:40
Drago1ram_: I don't have any experience with kuryr10:40
Drago1yatin: Do you have an experience with k8s 1.4 or kube-dns?10:41
yatinDrago1, No10:42
Drago1k10:42
yatinDrago1, we changed from container to container-infra10:42
yatinin newton10:42
Drago1ok10:42
Drago1yatin: I'm not sure if that would be bobby___'s problem then10:42
yatinDrago1, we can check with openstack endpoint list then10:43
bobby___Not sure as I’m very much new to OpenStack.. don’t really know what you mean by, ‘it changed’. I’m just trying to used my openstack installtion running Mitaka. SHouldn’t it just work? :(10:43
Drago1bobby___: There are a lot of moving parts10:43
bobby___Fair10:43
*** ram_ has quit IRC10:44
Drago1bobby___: What does `openstack catalog list` show?10:44
Drago1yatin: Are you coming to the PTG in February?10:45
bobby___cinder, glance, heat, horizon, nova, keystone, swift cinderv2, aodh,  neutron, ceilometer, gnocchi & sahara10:45
Drago1bobby___: Your magnumclient uses the catalog to know where to go to talk to the magnum service. Without a catalog entry, it is lost10:46
Drago1bobby___: From your list, it has no entry for magnum10:46
bobby___Yeah, that sucks doesn’t it.10:46
bobby___So, Mitaka doesn’t come with Magnum by default?10:46
Drago1bobby___: No10:46
bobby___D’oh. Sorry, my misunderstanding then.10:46
Drago1bobby___: And it heavily depends on what you're using to deploy openstack10:47
yatinDrago1, I applied yesterday for Travel support and IL, Let's see10:47
bobby___we’re on the Redhat Director version, using TripleO10:47
Drago1bobby___: I have heard a lot about TripleO, but haven't ever tried it10:47
*** ram___ has joined #openstack-containers10:48
bobby___Ok, thanks guys, I think theres plenty I can do from my end before i pester you guys any more. A the very least getting Magnum into the client list!10:48
Drago1bobby___: therve in #heat can help you install magnum. He works on TripleO10:48
bobby___Ah - thanks Drago1 :)10:48
Drago1Welcome, good luck!10:48
bobby___ty :)10:49
ram___Dragol: Hi. This is an all in one setup right. You mean kolla will deploy magnum service right. Kolla-kubernetes released?10:49
ram___Dragol: OK. Then what about kuryr.10:50
Drago1ram___: Yes, just make sure kolla is configured to deploy magnum. It may not be enabled by default10:50
Drago1yatin: Do you know anything about magnum and kuryr? Can you even use kuryr yet in magnum?10:50
yatinDrago1: I think it's not enabled yet, they work seperately10:51
yatinand for Kolla-kubernetes i heard it's in POC face10:51
ram___Dragol: OK . Thanks. How do I make sure that kolla is configured to deploy magnum? Because when i run kolla-build then all openstack services are going to be deployed. When we run kolla-build magnum service also be deployed?10:54
Drago1ram___: ^ So there you go. You can't use kuryr with magnum yet, but if you want to see where the progress is, here are Ton's patches for enabling kuryr in the swarm driver https://review.openstack.org/#/q/owner:%22Ton+Ngo+%253Cton%2540us.ibm.com%253E%22+kuryr10:55
Drago1ram___: In the link I sent you, there is "http://docs.openstack.org/developer/kolla/image-building.html" which goes to http://docs.openstack.org/developer/kolla/image-building.html that has information about that10:57
Drago1*that was supposed to say "Building Container Images"10:57
Drago1ram___: The kolla folks are in #openstack-kolla by the way10:58
Drago1They'll know lots more than me10:58
ram___Dragol: Ok. Thank you.10:59
*** takashi has quit IRC11:05
*** bks has quit IRC11:21
*** ram_ has joined #openstack-containers11:22
ram_Hi all. How do I make sure that kolla is configured to deploy magnum? along with the entire openstack config setup.11:23
ram_sry11:23
ram_I have to go #openstack-kolla11:24
*** chhavi has quit IRC11:25
*** bobby___ has quit IRC11:26
*** chhavi has joined #openstack-containers11:27
*** ram_ has quit IRC11:29
*** ricolin has quit IRC11:29
*** bobby___ has joined #openstack-containers11:32
*** mdnadeem has quit IRC11:34
*** hvlad has quit IRC11:40
*** yamamot__ has quit IRC11:46
*** bobby___ has quit IRC11:47
*** bobby___ has joined #openstack-containers11:48
*** mdnadeem has joined #openstack-containers11:50
*** wangbo has joined #openstack-containers12:00
*** vijendar has joined #openstack-containers12:03
*** vijendar has quit IRC12:03
*** vijendar has joined #openstack-containers12:03
*** vijendar has quit IRC12:09
*** sdake has joined #openstack-containers12:09
*** anush has joined #openstack-containers12:13
*** hvlad has joined #openstack-containers12:19
*** anush has quit IRC12:24
*** EricGonczer_ has joined #openstack-containers12:28
*** catinthe_ has joined #openstack-containers12:37
*** mdnadeem has quit IRC12:46
*** PanFengyun has quit IRC12:56
*** snarwade has quit IRC12:57
*** huzhengchuan has quit IRC12:59
*** chhavi has quit IRC13:02
*** vijendar has joined #openstack-containers13:09
*** vijendar has quit IRC13:10
*** vijendar has joined #openstack-containers13:10
*** manikanta_tadi has quit IRC13:11
*** vijendar has quit IRC13:15
*** yamamoto has joined #openstack-containers13:20
*** yamamoto_ has joined #openstack-containers13:22
*** yamamoto has quit IRC13:25
*** PanFengyun has joined #openstack-containers13:26
*** EricGonc_ has joined #openstack-containers13:29
*** chhavi has joined #openstack-containers13:30
*** EricGonczer_ has quit IRC13:30
*** bobby___ has quit IRC13:35
*** dave-mccowan has joined #openstack-containers13:43
*** bobby___ has joined #openstack-containers13:43
*** mdnadeem has joined #openstack-containers13:43
*** zz_dimtruck is now known as dimtruck13:53
openstackgerritfengbeihong proposed openstack/magnum: Support dcos installation on centos cluster  https://review.openstack.org/38643514:12
*** jperry has joined #openstack-containers14:14
*** huzhengchuan has joined #openstack-containers14:15
*** huzhengchuan is now known as zhengchuanhu14:18
*** zul has quit IRC14:18
*** zhengchuanhu has quit IRC14:19
*** huzhengchuan has joined #openstack-containers14:19
*** huzhengchuan_ has joined #openstack-containers14:23
*** vijaykc4 has joined #openstack-containers14:23
*** mdnadeem has quit IRC14:23
*** huzhengchuan has left #openstack-containers14:23
*** zenoway has quit IRC14:32
*** zenoway has joined #openstack-containers14:32
*** zenoway has quit IRC14:36
*** PanFengyun has quit IRC14:38
*** chhavi has quit IRC14:43
*** Drago1 has quit IRC14:45
*** mtanino has joined #openstack-containers14:51
*** jwcroppe has joined #openstack-containers14:55
*** jasond has joined #openstack-containers14:57
*** bobby___ has quit IRC14:58
*** dimtruck is now known as zz_dimtruck15:00
*** vijendar has joined #openstack-containers15:03
*** Jeffrey4l has quit IRC15:09
*** EricGonc_ has quit IRC15:11
*** jmckind has joined #openstack-containers15:12
*** EricGonczer_ has joined #openstack-containers15:12
*** EricGonczer_ has quit IRC15:16
*** FengShengqin1 has joined #openstack-containers15:17
*** huzhengchuan_ has quit IRC15:22
*** hongbin has joined #openstack-containers15:22
*** vijendar has quit IRC15:23
*** jmckind_ has joined #openstack-containers15:26
*** hvlad has quit IRC15:26
*** jmckind has quit IRC15:27
*** zz_dimtruck is now known as dimtruck15:28
*** randallburt has joined #openstack-containers15:28
*** hvlad has joined #openstack-containers15:29
*** chris_hultin|AWA is now known as chris_hultin15:31
*** vijendar has joined #openstack-containers15:32
*** randallburt has quit IRC15:33
*** mdnadeem has joined #openstack-containers15:33
*** tonanhngo has joined #openstack-containers15:33
*** huzhengchuan_ has joined #openstack-containers15:34
*** vijaykc4 has quit IRC15:35
*** syed__ has joined #openstack-containers15:37
openstackgerritMerged openstack/magnum: Doc: update server type in userguide  https://review.openstack.org/40409715:38
*** zul has joined #openstack-containers15:38
*** randallburt has joined #openstack-containers15:40
*** ricolin has joined #openstack-containers15:43
*** Jeffrey4l has joined #openstack-containers15:44
*** ricolin has quit IRC15:44
*** seanhandley has quit IRC15:46
*** seanhandley has joined #openstack-containers15:48
*** Jeffrey4l has quit IRC15:51
*** Jeffrey4l has joined #openstack-containers15:51
*** rpothier has joined #openstack-containers15:52
openstackgerritMathieu Velten proposed openstack/magnum: Remove underscores from Nova server names  https://review.openstack.org/40267715:55
*** adrian_otto has joined #openstack-containers15:55
adrian_ottoHello! Our team meeting will begin in 5 minutes at 1600 UTC in #openstack-meeting-alt15:56
*** Drago1 has joined #openstack-containers16:01
*** strigazi_AFK is now known as strigazi16:02
*** Drago_ has joined #openstack-containers16:02
*** rcernin has quit IRC16:03
*** mjura has quit IRC16:03
openstackgerritMathieu Velten proposed openstack/magnum: Factorize load balancer code into its own template  https://review.openstack.org/40131016:04
*** anush has joined #openstack-containers16:05
*** vijaykc4 has joined #openstack-containers16:06
*** Drago1 has quit IRC16:06
*** Drago1 has joined #openstack-containers16:12
*** kevinz has quit IRC16:15
Drago1adrian_otto: So I don't forget, this needs your +1 https://review.openstack.org/#/c/399869/16:15
adrian_ottook, got it16:16
*** Drago_ has quit IRC16:17
*** chhavi has joined #openstack-containers16:19
*** mdnadeem has quit IRC16:21
*** dimtruck is now known as zz_dimtruck16:26
*** huzhengchuan_ has quit IRC16:26
*** zz_dimtruck is now known as dimtruck16:28
*** vijendar1 has joined #openstack-containers16:29
*** pcaruana has quit IRC16:36
*** mtani____ has joined #openstack-containers16:39
*** mtanino has quit IRC16:40
*** zenoway has joined #openstack-containers16:49
*** jmckind has joined #openstack-containers16:51
strigaziDrago1: https://review.openstack.org/#/c/334967/9/ironic/tests/unit/db/sqlalchemy/test_migrations.py16:51
*** jmckind_ has quit IRC16:52
*** mtanino has joined #openstack-containers16:52
*** zenoway has quit IRC16:53
*** mtani____ has quit IRC16:53
*** adrian_otto has quit IRC17:01
Drago1jvgrant, strigazi, tonanhngo, hongbin, swatson: Care to discuss template versioning/cluster upgrades?17:01
*** rpothier has quit IRC17:01
jvgrantDrago1: sure, i'm updating the etherpad as well with the data structure info hongbin asked for17:02
tonanhngosure17:02
Drago1and yatin17:03
Drago1And whoever else I may be forgetting17:03
Drago1So, to recap the main issue - how to handle situations like these:17:03
*** sdake_ has joined #openstack-containers17:03
Drago1User creates a cluster from a clustertemplate with coe_version=117:04
yatinDrago1, It's late here: over 10:30 but can give some time17:04
Drago1User updates that cluster so that node_count=2 (was 1 before)17:04
yatinDrago1, it would help to further review other specs as well17:04
Drago1Operator wants to upgrade coe_version to 217:04
Drago1The operator updates the original clustertemplate so that coe_version=217:05
Drago1The operator does magnum cluster-upgrade {user's cluster} {upgraded CT}17:05
Drago1There is a conflict where the upgraded CT has a different node count than the cluster17:06
strigaziFor some attributes like node_counts and docker-volume-size we don't care if it will keep the original valurs from CT, could we make a separation on the attributes?17:06
Drago1The question is, how to handle this?17:06
*** sdake has quit IRC17:06
jvgrantmy opinion is it should be done by command not by the data structure.  Otherwise why have update and upgrade17:06
Drago1strigazi: Yes, that seems like what tonanhngo described, and I like that idea17:06
tonanhngoSo a major departure from the way things work now is that the attributes in the cluster and cluster template will diverge17:06
Drago1Having certain commands tied to certain attributes17:07
strigaziupgrade COE will be a very special operation17:07
jvgrantwhat is the difference between update -coe_version=2 and upgrade with template that is coe-version=217:07
jvgrantstrigazi: +117:07
jvgrantstrigazi: update is already pretty limited as well. you can't really cluster-update that many attributes17:08
tonanhngoSince the attributes will not be tied together anymore, should we direct the cluster upgrade to the cluster, instead of the template?17:08
jvgrantso let's keep the data structure simple and handle what is allowed to be changed in the commands17:08
yatinSilly query: What I can think off after flatten attributes, Templates(CT and NGT) became just a medium(reuse cluster attributes to create cluster)17:08
Drago1jvgrant: If that is possible, it depends on what attributes that upgrade will affect17:08
strigazitonanhngo, we want CTs to make the path of the lifecyle of the cluster17:09
Drago1yatin: Basically, plus they will be used to track what the cluster was created from17:09
jvgranttonanhngo: correct, cluster-update/upgrades no longer change templates at all17:09
Drago1Not that they ever did17:10
Drago1jvgrant: ^17:10
yatinDrago1, Ok, so the decison to remove the reference of cluster_template from cluster table is not there now.17:10
Drago1yatin: That is correct, and it is because of template versioning17:10
jvgrantDrago1: well before a cluster-template-update could have impacted a existing cluster in theory17:11
yatinDrago1, That makes sense then17:11
jvgrantDrago1: now there is no direct connection between the template data and cluster data17:11
strigazijvgrant, it could, but CT-update isn't possible for an CT in use17:11
Drago1yatin: It is still true that all of the attributes will be in cluster and CT attributes will not be used17:11
jvgrantstrigazi, that's right. more of in theory since the template was actually reference by the cluster17:12
yatinDrago1, Got it17:12
*** anush has quit IRC17:12
Drago1yatin: (except when upgrading a cluster, possibly, but still just copying attributes over)17:12
Drago1hongbin: Are you there?17:12
jvgrantnow there will be no limitation on modifying templates with existing clusters17:12
strigaziTo address the diverging attrs we can start from17:13
yatinDrago1, Yes, same way as create, update17:13
strigazispliting COE upgrade as a specila case17:13
strigaziand create a set of attrs that can be updated freely like node-count17:13
*** adrian_otto has joined #openstack-containers17:13
tonanhngostrigazi: is this because it makes it easier as a workflow for the cloud operator?17:14
strigazitonanhngo, which one?17:14
jvgrantstrigazi, does that need to be in the versioning or data structure though? why not just handle what can and can't be updated in the cluster-update commands?17:14
tonanhngostrigazi:  COE upgrade as a special case17:14
tonanhngostrigazi:  I guess I don't see a strong reason17:15
strigazitonanhngo, not about the operator17:15
strigazicurrently, the way we manage COE all upgrades are non trivial17:16
strigazieven if we mode k8s in containers which in theory would allow upgrading by specifing a new version17:17
strigaziit would require to start from the master and procceed to the workers17:17
*** chhavi has quit IRC17:17
strigazifor docker, I don't think it's going to be as easy because it will require an upgrade of the packages17:18
strigazisince they put everything in the docker binaries17:19
strigazimesos too17:19
tonanhngostrigazi:  is the current proposal to update the cluster template, then do cluster-upgrade to the cluster based on the template?17:19
strigaziyes17:20
*** anush has joined #openstack-containers17:20
tonanhngook, that's really my main question, can we just do cluster-upgrade directly to the cluster?17:20
tonanhngoI still see the tie between the template and the cluster17:21
tonanhngowhich may be confusing to the user17:21
*** FengShengqin1 has quit IRC17:21
strigazias I mentioned in the spec there will be two paths on upgrades17:21
strigazione directly on the cluster and one through the CT17:21
yatinstrigazi, is it same like passing attributes during cluster create17:23
tonanhngoThat's great, so what would be the reason for the path using the CT ?17:23
strigaziHow a user could upgrade the cluster by himself?17:23
strigaziHow a user could go from docker 1.12 to 1.13 ?17:24
strigaziby using another image, there is no other way17:24
tonanhngoI would imagine a user would find out through the doc or help message that certain upgrade is supported, then he/she would apply that upgrade17:25
strigazithe image would be built by the operator in most cases, I don't think that users will build qcow images17:25
tonanhngothe user would not be implementing the upgrade, but use what's supported17:26
tonanhngoyeah I think our thinking diverges here17:27
*** vijaykc4 has quit IRC17:27
strigaziadditionally, we can't rely only in docs to define what is supported17:28
tonanhngoI am thinking that the operator, or Magnum provides support for, say upgrading from docker 1.12 to 1.13, and the user would take advantage of that operation17:28
strigaziyes, this the higher level goal17:29
*** tkarke has joined #openstack-containers17:30
openstackgerritSpyros Trigazis proposed openstack/magnum: Change gate Fedora Atomic image to the automated f24 build  https://review.openstack.org/40059317:31
strigazitonanhngo. one more thing17:31
strigaziif we see the initial upgrade, it doesn't make a big difference17:32
strigaziwhen I say initial I mean from a starting COE version17:32
strigaziI gets complecated as soon user start upgrade their cluster by themselves17:33
*** vimal has quit IRC17:33
Drago1strigazi, tonanhngo: Was in a meeting, but don't forget that operators will have the ability to lock attributes. Potentially, that could mean the docker version can be locked and only updatable by operators17:34
Drago1In my opinion, that would work best when it could be locked on a per-template basis17:34
strigaziwe will have clusters with different attributes upgraded and will become difficult for ops to offer support17:34
tonanhngook, that's why I was wondering if the motivation for the path using CT is to help the cloud operator manages17:36
strigaziI think Ricardo can articulate better the problem. I'll try to get more feedback from him and put in comment in CT versions17:36
*** vijendar has quit IRC17:37
*** vijendar1 has quit IRC17:37
jvgrantright now the version spec is keeping things very simple. It just adds a new version everytime any attribute changes17:37
jvgrantthis allows commands to use that info of the differences between versions as they like17:38
tonanhngomy main point is to keep the concept simple for the users.  If it's possible to always separate the attributes in the CT and the cluster, then it helps.17:38
Drago1tonanhngo: The motivation is for operators to track what clusters are supported17:38
Drago1I'm caught up with the conversation now17:38
Drago1tonanhngo: CERN's use-case involves creating CTs that are "supported". Clusters created from these CTs should also be supported.17:39
*** anush has quit IRC17:40
Drago1Operators will be able to update the supported CT and then upgrade clusters with that new CT version as the target17:40
strigaziA lot of these ideas come from GKE17:40
Drago1So, un-upgraded clusters will have a reference to, say, SupportedCT:v1, and upgraded ones will be SupportedCT:v217:41
strigaziif you have a look on how they do upgrades17:41
strigaziWe also saw this need when writing docs17:42
strigaziInitially we had commands to create diffent CTs and the create the cluster17:43
strigazithe problem was not the two commands17:43
*** vijaykc4 has joined #openstack-containers17:44
strigazibut the complecity of the cluster-template create and that it was possible to make mistakes17:44
strigaziremove the CT step17:44
tonanhngoI think this is fine, we just need to explain the use cases clearly so users won't be confused which way is best for them17:44
strigazionly transfers the problem on the cluster-create17:44
tonanhngoit's not obvious from first look17:45
jvgrantagreed, i don't think the change to CT solves that problem. I don't think it is meant to. The change just makes ClusterTemplates behave like actual templates17:46
strigaziit's not, we relised after a few tickets opened from users :)17:46
jvgrantinstead of a ClusterParent object17:46
jvgrantif we didn't do this change then if we did versioning we would have to version CT and cluster itself to cover all the attributes17:47
yatinThanks guys for explanation, discussion. Understood till now. Will look to rest discussion Tomorrow.17:48
Drago1Thanks for joining the discussion, yatin :)17:48
jvgrantthanks yatin17:48
tonanhngoGood night!17:48
strigaziit's strange yatin's timezone is GMT +5:30 and not +5 or +6, good night17:49
tonanhngoI think India has this :30 timezone17:50
strigazifolks, is there any other point you want to discuss?17:50
tonanhngoThanks Spyros, end of the day for you also17:51
*** anush has joined #openstack-containers17:52
jvgrantjust add feedback to the spec reveiw if you can. It has kind of got stuck17:52
strigaziI'll add tomorrow17:52
jvgrantthanks17:52
*** adrian_otto has quit IRC17:53
strigaziI'm leaving guys, have a nice day17:53
Drago1Bye strigazi!17:54
*** strigazi is now known as strigazi_AFK17:54
*** jperry has quit IRC17:59
*** jperry has joined #openstack-containers17:59
*** jmckind_ has joined #openstack-containers18:06
*** jmckind has quit IRC18:07
*** vijaykc4 has quit IRC18:12
*** zul has quit IRC18:13
*** tonanhngo has quit IRC18:14
*** swatson_ has joined #openstack-containers18:16
*** zul has joined #openstack-containers18:21
swatson_Does anyone know if I need to do more than have extra files in specific directories to effectively "register" them with pecan/wsgi?18:21
Drago1swatson: You should ask swatson about that, he probably knows the most about pecan ;)18:22
swatson_Drago1: ;_;18:22
swatson_I ask because on the v2 stuff I'm getting a 400 back for "Value: 'v2'. unable to convert to ClusterTemplate"18:23
swatson_makes me think there's something else I need to tell Pecan that I'm missing18:23
swatson_And I just found something18:24
*** jmckind has joined #openstack-containers18:25
*** jmckind_ has quit IRC18:27
*** dimtruck is now known as zz_dimtruck18:28
*** jmckind_ has joined #openstack-containers18:32
*** jmckind has quit IRC18:33
*** jmckind has joined #openstack-containers18:39
*** hvlad has quit IRC18:39
*** jmckind_ has quit IRC18:40
*** vijendar1 has joined #openstack-containers18:45
*** vijendar has joined #openstack-containers18:45
*** zz_dimtruck is now known as dimtruck18:54
*** jmckind_ has joined #openstack-containers19:00
*** jmckind has quit IRC19:02
*** jmckind has joined #openstack-containers19:07
openstackgerritStephen Watson proposed openstack/magnum: [WIP] Add NodeGroups with v2 API  https://review.openstack.org/39927719:08
*** jmckind_ has quit IRC19:09
*** tonanhngo has joined #openstack-containers19:14
*** vijendar1 has quit IRC19:57
*** vijendar has quit IRC19:57
*** code34 has joined #openstack-containers19:59
*** syed__ is now known as syed_19:59
*** syed_ is now known as syed20:00
*** syed is now known as Syed20:00
*** code34 has quit IRC20:01
*** code34 has joined #openstack-containers20:04
swatson_Maybe I'm having a lapse of reading comprehension or something but how do I see my older changes in Gerrit?20:04
swatson_I'm looking for one that I abandoned a couple weeks back20:04
Drago1swatson: https://review.openstack.org/#/q/owner:%22Stephen+Watson+%253Cstephen.watson%2540intel.com%253E%2220:05
Drago1swatson: I clicked your name in gerrit and removed "status:open" in the search box20:06
swatson_Drago1: I just remembered filtering after posting that message :D20:06
swatson_Drago1: Part of my problem was clicking my own name just brings me to dashboard so there was no filtering20:06
Drago1ahaha20:06
Drago1Confusing.20:06
swatson_Yeah...Gerrit could use a few UI improvements20:07
swatson_TY though20:07
Drago1swatson: When I click my own name it doesn't go to my dashboard20:07
Drago1I am logged in too20:07
swatson_Drago1: Whoops, I meant clicking My->Changes20:07
Drago1Oh, got it20:07
randallburtmore than a few tbh. but I can't criticize. its what generally happens when programmers do user interface.20:09
swatson_randallburt: Haha agreed20:10
*** vijendar has joined #openstack-containers20:13
*** vijendar1 has joined #openstack-containers20:13
*** yatin has quit IRC20:34
*** catinthe_ has quit IRC20:35
openstackgerritStephen Watson proposed openstack/magnum: [WIP] Add NodeGroups with v2 API  https://review.openstack.org/39927720:38
*** yatin has joined #openstack-containers20:46
jasondis there a preferred way of running a post-creation utility script (eg. to replace SSL cert) on a node? i can't find any examples of that in magnum20:50
*** dimtruck is now known as zz_dimtruck20:52
*** FengShengqin1 has joined #openstack-containers20:54
*** adrian_otto has joined #openstack-containers21:00
Drago1jasond: SoftwareDeployment21:01
jasondDrago1: so just add it to the template and update?21:04
Drago1jasond: I would have it in the template already and set the actions to "UPDATE" so it doesn't trigger on create21:05
jasondDrago1: oh ok, so it would run on every update21:05
*** adrian_otto1 has joined #openstack-containers21:06
jasondDrago1: ideally it would just run the one time21:06
Drago1jasond: No, see https://review.openstack.org/#/c/368981/11/magnum/drivers/k8s_fedora_atomic_v1/templates/kubemaster.yaml21:06
Drago1jasond: Unless it has a reason to update, it wouldn't ever update. So, the TripleO solution is to add a parameter for updating21:06
*** dave-mccowan has quit IRC21:06
*** adrian_otto has quit IRC21:07
Drago1jasond: so you would do the equivalent of `heat stack-update -x -P updateparam=somerandomvalue`21:07
Drago1jasond: I was using a UUID https://review.openstack.org/#/c/368981/11/magnum/conductor/handlers/cluster_conductor.py@27321:08
jasondDrago1: oh ok, it will only updated when changed since it's a patch update21:09
*** zz_dimtruck is now known as dimtruck21:09
jasondDrago1: thanks, that helps!21:09
Drago1jasond: Well, the patch update is convenient because you don't have to resupply all the templates21:09
jasondyeah, and parameters21:10
Drago1jasond: Welcome. Like I've said, you'll have to get os-*-config working on the image that Spyros built for me21:10
Drago1jasond: I'll forward you the email21:10
jasondDrago1: i was focusing on the 1.2 driver first.  ok21:11
Drago1jasond: Yes, you either have to use a container (which is huge because of python) or have the packages preinstalled.21:11
Drago1I got the former working but abandoned it because it really was unworkable. Remember that was the problem I was having with the EOF error in docker because systemd was killing it after 90 seconds?21:12
jasondDrago1: ah yes21:12
Drago1jasond: http://test-strigazi-sharing.web.cern.ch/test-strigazi-sharing/fedora-atomic-23-heat-agent.qcow221:14
jasondDrago1: this has k8s 1.4?21:15
Drago1jasond: Best of luck… I didn't quite figure out the configuration of os-collect-config21:15
Drago1jasond: no, it's the same as the 1.2 upstream fedora atomic image, but with os-*-config21:15
*** sdake_ has quit IRC21:17
jasondDrago1: i was using fedora-atomic-latest.  just realized there's no os-collect-config.  how does that even work with magnum?21:18
Drago1jasond: It doesn't use softwaredeployments21:18
Drago1Just user data21:18
jasondDrago1: i see21:19
jasondso much for making this work with the upstream fedora atomic image :/21:20
randallburtjasond:  yeah, the current magnum images don't work with software config. IIRC, its kinda problematic to get it working with atomic. IIRC strigazi_AFK was working on it but could have been someone else21:21
*** anush has quit IRC21:21
Drago1randallburt: It was him and me21:22
Drago1randallburt, jasond: With the right configuration on the image I linked, it *should* work. However, that configuration was proving hard to figure out21:23
Drago1But I don't know software config well so there's that.21:23
randallburtDrago1:  right21:23
*** vijendar has quit IRC21:26
*** vijendar1 has quit IRC21:26
*** vijendar has joined #openstack-containers21:27
*** vijendar1 has joined #openstack-containers21:27
*** sdake has joined #openstack-containers21:32
*** adrian_otto1 has quit IRC21:32
*** vijendar has quit IRC21:32
*** vijendar1 has quit IRC21:32
*** vijendar has joined #openstack-containers21:33
*** adrian_otto has joined #openstack-containers21:33
*** vijendar1 has joined #openstack-containers21:33
*** catintheroof has joined #openstack-containers21:34
*** Jeffrey4l has quit IRC21:35
*** vijendar1 has quit IRC21:38
*** vijendar has quit IRC21:38
*** sdake_ has joined #openstack-containers21:38
*** vijendar has joined #openstack-containers21:38
*** catintheroof has quit IRC21:38
*** vijendar1 has joined #openstack-containers21:39
*** sdake has quit IRC21:41
*** vijendar1 has quit IRC21:44
*** vijendar has quit IRC21:44
*** vijendar has joined #openstack-containers21:44
*** vijendar1 has joined #openstack-containers21:46
*** Jeffrey4l has joined #openstack-containers21:47
*** catintheroof has joined #openstack-containers21:47
*** sdake has joined #openstack-containers21:47
*** vijendar1 has quit IRC21:50
*** vijendar has quit IRC21:50
*** vijendar has joined #openstack-containers21:50
*** sdake_ has quit IRC21:51
*** vijendar1 has joined #openstack-containers21:53
*** vijendar has quit IRC21:56
*** vijendar1 has quit IRC21:56
*** vijendar has joined #openstack-containers21:56
*** askb has joined #openstack-containers21:57
*** seanhandley has quit IRC21:58
*** vijendar1 has joined #openstack-containers22:02
*** chris_hultin is now known as chris_hultin|AWA22:06
*** vvro has quit IRC22:15
*** jwcroppe has quit IRC22:16
*** jwcroppe has joined #openstack-containers22:17
*** randallburt has quit IRC22:20
*** jwcroppe has quit IRC22:21
*** seanhandley has joined #openstack-containers22:23
*** vijendar_ has joined #openstack-containers22:24
*** vijendar1 has quit IRC22:27
*** vijendar has quit IRC22:28
*** vijendar_ has quit IRC22:29
*** vijendar has joined #openstack-containers22:29
*** vijendar_ has joined #openstack-containers22:30
*** adrian_otto has quit IRC22:31
*** swatson_ has quit IRC22:31
*** rcernin has joined #openstack-containers22:31
*** jmckind has quit IRC22:37
*** chris_hultin|AWA is now known as chris_hultin22:53
*** sahilsinha has quit IRC22:55
*** slagle has quit IRC22:57
*** dimtruck is now known as zz_dimtruck22:57
*** yatin has quit IRC22:59
*** rcernin has quit IRC23:01
*** chris_hultin is now known as chris_hultin|AWA23:03
*** FengShengqin1 has quit IRC23:03
*** catinthe_ has joined #openstack-containers23:03
*** rcernin has joined #openstack-containers23:04
*** sahilsinha has joined #openstack-containers23:05
*** zz_dimtruck is now known as dimtruck23:06
*** catintheroof has quit IRC23:06
*** rochaporto has quit IRC23:06
*** rochaporto has joined #openstack-containers23:08
*** jasond has quit IRC23:09
*** yatin has joined #openstack-containers23:11
*** yuanying has joined #openstack-containers23:16
*** chris_hultin|AWA is now known as chris_hultin23:16
*** jperry has quit IRC23:17
*** bobby___ has joined #openstack-containers23:25
*** yatin has quit IRC23:32
*** chris_hultin is now known as chris_hultin|AWA23:34
*** rcernin has quit IRC23:41
*** yatin has joined #openstack-containers23:44
*** bobby___ has quit IRC23:49
*** vijendar has quit IRC23:50
*** vijendar_ has quit IRC23:50
*** vijendar has joined #openstack-containers23:51
*** vijendar has quit IRC23:57
*** vijendar has joined #openstack-containers23:57
*** vijendar has quit IRC23:57
*** vijendar has joined #openstack-containers23:57

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