Tuesday, 2015-09-22

*** achanda has quit IRC00:03
*** achanda_ has quit IRC00:04
*** banix has quit IRC00:10
klindgrenhello - trying to get magnum started up for the first time... I mist be totally daft on this - but it seems like logging is totally fubar?00:15
klindgrenuse_stderr = false00:15
klindgrenstate_path = /var/lib/magnum00:15
klindgrenlogfile=magnum.log00:15
klindgrenlogdir=/var/log/magnum00:15
klindgrenverbose = true00:15
klindgrendebug = true00:15
klindgrenresults in nothing in /var/log/magnum being created00:15
klindgrentried log_dir, tried without log_file tryied passing --log-file on the CLI00:16
klindgrenI dont see any initialization message or anything00:16
*** kebray has quit IRC00:16
*** yuanying has quit IRC00:19
*** yuanying_ is now known as yuanying00:19
klindgrenapparently has to be specifically started with --log_dir on the CLI00:21
*** yuanying_ has joined #openstack-containers00:24
openstackgerritSurojit Pathak proposed openstack/python-magnumclient: Adding 'magnum service-list'  https://review.openstack.org/22610600:25
*** suro-patz has quit IRC00:26
klindgrenactually - spoke too soon that doesn't even seem to work00:26
*** yuanying has quit IRC00:29
*** yuanying_ is now known as yuanying00:29
*** yuanying_ has joined #openstack-containers00:30
*** Tango has quit IRC00:40
*** dims_ has quit IRC00:42
*** vilobhmm_111 has quit IRC00:47
*** vilobhmm_111 has joined #openstack-containers00:48
*** SourabhP has joined #openstack-containers00:49
*** hongbin has joined #openstack-containers00:51
*** harshs has quit IRC00:53
*** harshs has joined #openstack-containers00:53
*** suro-patz has joined #openstack-containers00:57
*** sdake_ has joined #openstack-containers01:04
*** sdake has quit IRC01:06
*** sdake_ has quit IRC01:07
*** sdake has joined #openstack-containers01:07
*** ganeshna has joined #openstack-containers01:07
*** ganeshna has quit IRC01:07
*** SourabhP has quit IRC01:07
*** ganeshna has joined #openstack-containers01:08
*** vilobhmm_111 has quit IRC01:10
*** ganeshna has quit IRC01:11
hongbinyuanying: yuanying_ ping01:12
*** vilobhmm_11 has quit IRC01:12
yuanying_hongbin: hi01:12
*** ganeshna has joined #openstack-containers01:12
*** suro-patz1 has joined #openstack-containers01:12
hongbinyuanying_: I want to talk about the review01:12
hongbinhttps://review.openstack.org/#/c/223025/1/magnum/conductor/template_definition.py01:12
hongbinwhat I don't like is the extra processing in template definition doesn't read very well01:13
*** ganeshna has quit IRC01:13
hongbinIf you can make it read better, I am fine with the approach01:13
*** suro-patz has quit IRC01:13
hongbinyuanying_: ^^01:14
*** ganeshna has joined #openstack-containers01:14
yuanying_hongbin: you mean, code is difficult to read?01:14
hongbinmaybe not, but the style is not consistent01:14
hongbinwith the rest of the code01:15
yuanying_ok01:15
hongbinyes, if the style can be more consistent, then it is fine01:16
yuanying_I’ll try to update OutputMapping01:16
hongbink. thx01:16
yuanying_to introduce extra config01:16
*** gangil has quit IRC01:18
*** ganeshna has quit IRC01:19
*** dims has joined #openstack-containers01:26
*** sthillma has quit IRC01:31
openstackgerritEli Qiao proposed openstack/magnum: Add functional test cases(containers actions) for swarm  https://review.openstack.org/22612501:37
openstackgerritSurojit Pathak proposed openstack/magnum: Backend support for magnum service healthcheck  https://review.openstack.org/22070201:52
*** erkules_ has joined #openstack-containers01:58
*** eghobo has quit IRC01:59
*** erkules has quit IRC02:01
openstackgerritSurojit Pathak proposed openstack/magnum: Documentation update for 'magnum service-list'  https://review.openstack.org/22613302:13
*** muralia has quit IRC02:15
openstackgerritMotohiro/Yuanying Otsuka proposed openstack/magnum: [WIP] Add TLS support in heat kubernetes template  https://review.openstack.org/20287302:18
*** yuanying_ has quit IRC02:19
*** suro-patz1 has quit IRC02:22
*** zz_dimtruck is now known as dimtruck02:27
*** achanda has joined #openstack-containers02:33
*** dims has quit IRC02:33
*** hongbin has quit IRC02:34
*** unicell has quit IRC02:36
*** sdake has quit IRC02:39
*** david-ly_ has joined #openstack-containers02:39
*** unicell has joined #openstack-containers02:40
*** david-lyle has quit IRC02:40
*** harshs has quit IRC02:40
*** unicell has quit IRC02:44
*** _hanhart has quit IRC02:47
*** tobe has joined #openstack-containers02:48
*** tobe has quit IRC02:48
*** yuanying_ has joined #openstack-containers02:49
*** muralia has joined #openstack-containers02:49
*** yuanying_ has quit IRC02:55
*** yuanying_ has joined #openstack-containers02:56
*** yuanying_ has quit IRC03:00
*** deepthi has joined #openstack-containers03:04
*** ganeshna has joined #openstack-containers03:06
*** kebray has joined #openstack-containers03:10
*** kebray has quit IRC03:10
*** kebray has joined #openstack-containers03:11
*** david-ly_ is now known as david-lyle03:17
*** ganeshna has quit IRC03:21
*** ganeshna has joined #openstack-containers03:23
*** Marga__ has joined #openstack-containers03:31
*** madhuri has joined #openstack-containers03:34
*** dims has joined #openstack-containers03:34
*** Marga_ has quit IRC03:34
*** Marga__ has quit IRC03:35
madhuriyuanying: Hi03:37
*** ganeshna_ has joined #openstack-containers03:43
*** ganeshna has quit IRC03:43
*** Tango has joined #openstack-containers03:46
*** eghobo has joined #openstack-containers03:49
*** ganeshna_ has quit IRC03:49
*** suro-patz has joined #openstack-containers03:49
madhuriTango: Hi04:08
TangoHi Madhuri04:08
*** harshs has joined #openstack-containers04:08
madhuriI just wanted to talk about the k8s v1 client04:08
madhuriI saw the new code04:09
*** dims has quit IRC04:09
madhuriBut other implementation is not updated04:09
*** dimtruck is now known as zz_dimtruck04:09
madhuriDo you know about it?04:09
TangoOther implementation?04:09
madhuriAre you or hongbin working on it?04:09
madhuriYes the new code is not used in k8s_conductor04:10
madhuriStill old code is used04:10
TangoWe have a patch that's has been under review for awhile that has this code:  20729904:10
TangoIt's a big patch because we have to switch everything at once04:11
madhuriOk thanks. I will check it04:12
madhuriTango: I will review it :)04:13
TangoThat would be very helpful, thanks madhuri04:14
*** vilobhmm_11 has joined #openstack-containers04:28
*** deepthi has quit IRC04:29
*** vilobhmm_111 has joined #openstack-containers04:30
*** deepthi has joined #openstack-containers04:30
*** vilobhmm_111 has quit IRC04:32
*** vilobhmm11 has joined #openstack-containers04:32
*** vilobhmm_11 has quit IRC04:33
openstackgerritMerged openstack/magnum: Change ignore-errors to ignore_errors  https://review.openstack.org/22574704:35
*** harshs has quit IRC04:36
openstackgerritMerged openstack/magnum: Validates baymodel network_driver requests  https://review.openstack.org/22233704:36
*** wenchma has joined #openstack-containers04:39
*** Marga_ has joined #openstack-containers04:47
*** Marga_ has quit IRC04:49
*** Marga_ has joined #openstack-containers04:49
*** suro-patz has quit IRC04:55
*** diga has joined #openstack-containers05:02
openstackgerritMerged openstack/magnum: Migrate to Kubernetes Release 1  https://review.openstack.org/20729905:02
*** Marga_ has quit IRC05:05
Tangomadhuri: Thanks Madhuri!05:17
madhuriMost welcome Tango :)05:17
TangoIt's a big patch so it probably scared off everyone :)05:17
madhuriYes I guess so05:17
madhuriBut it had to go all together05:18
*** vimal has joined #openstack-containers05:20
*** ganeshna has joined #openstack-containers05:21
*** eghobo has quit IRC05:22
*** ganeshna has quit IRC05:26
*** chandankumar has joined #openstack-containers05:34
*** kebray has quit IRC05:37
*** tbh has joined #openstack-containers05:52
*** yuanying_ has joined #openstack-containers05:56
madhuriyuanying_: Hi06:04
yuanying_madhuri: hi06:04
madhuriI was looking for you so long :)06:04
yuanying_sorry, I had a cold last week06:05
yuanying_I remaind a lot of tasks..06:05
*** preilly has quit IRC06:07
*** sthillma has joined #openstack-containers06:07
*** sthillma_ has joined #openstack-containers06:08
openstackgerritEli Qiao proposed openstack/magnum: Functional: Split python client functional testing case  https://review.openstack.org/22390706:09
openstackgerritEli Qiao proposed openstack/magnum: Add functional test cases(containers actions) for swarm  https://review.openstack.org/22612506:09
openstackgerritEli Qiao proposed openstack/magnum: Add functional test cases for swarm  https://review.openstack.org/22163306:09
*** sthillma has quit IRC06:12
*** sthillma_ is now known as sthillma06:12
*** preilly has joined #openstack-containers06:12
*** preilly is now known as Guest5920006:13
*** sthillma has quit IRC06:23
*** j___ has joined #openstack-containers06:24
*** BertrandN has joined #openstack-containers06:43
*** shuquan has joined #openstack-containers06:48
*** BertrandN has quit IRC06:52
*** shuquan has quit IRC06:54
*** Tango has quit IRC06:54
*** shuquan has joined #openstack-containers06:58
*** david-lyle has quit IRC06:58
*** shuquan has quit IRC07:03
*** subscope has quit IRC07:03
*** BertrandN has joined #openstack-containers07:08
*** vilobhmm11 has quit IRC07:09
*** david-lyle has joined #openstack-containers07:14
*** achanda has quit IRC07:17
*** vilobhmm11 has joined #openstack-containers07:21
*** vilobhmm11 has quit IRC07:28
openstackgerritEli Qiao proposed openstack/magnum: Fix container status when showing a paused containers  https://review.openstack.org/22618407:30
*** yuanying_ has quit IRC07:32
*** erw has quit IRC07:41
*** ewindisch has quit IRC07:41
*** ramishra has quit IRC07:41
*** zhenguo has quit IRC07:41
*** briancurtin has quit IRC07:41
*** briancurtin has joined #openstack-containers07:43
*** zhenguo has joined #openstack-containers07:45
*** ramishra has joined #openstack-containers07:49
openstackgerritEli Qiao proposed openstack/magnum: Fix container action debug log not accurate  https://review.openstack.org/22619407:56
*** chandankumar has quit IRC07:59
eliqiaohello, any one know why function failed due to "Cannot fulfill request with a Unset network_driver, expecting a flannel network_driver. (HTTP 400)"08:04
*** halfss has joined #openstack-containers08:11
*** i316653 has joined #openstack-containers08:11
*** mathspanda has joined #openstack-containers08:19
*** Shijia has joined #openstack-containers08:19
eliqiaocan anyone gives a hand?08:21
*** Marga_ has joined #openstack-containers08:27
*** Marga_ has quit IRC08:28
*** Marga_ has joined #openstack-containers08:29
*** Shijia has quit IRC08:36
*** Shijia has joined #openstack-containers08:36
*** Shijia has quit IRC08:37
*** Shijia has joined #openstack-containers08:37
eliqiaosigh .....08:38
*** Shijia_ has joined #openstack-containers08:42
*** Shijia has quit IRC08:42
*** Shijia_ has quit IRC08:43
*** Shijia has joined #openstack-containers08:43
*** mathspanda has quit IRC08:46
*** mathspanda has joined #openstack-containers08:47
*** Shijia_ has joined #openstack-containers08:56
*** Shijia has quit IRC08:56
*** Marga_ has quit IRC09:05
*** alex_klimov has joined #openstack-containers09:06
openstackgerritEli Qiao proposed openstack/magnum: Functional: Split python client functional testing case  https://review.openstack.org/22390709:08
openstackgerritEli Qiao proposed openstack/magnum: Add functional test cases(containers actions) for swarm  https://review.openstack.org/22612509:08
openstackgerritEli Qiao proposed openstack/magnum: Add functional test cases for swarm  https://review.openstack.org/22163309:08
*** alex_klimov has quit IRC09:09
*** alex_klimov has joined #openstack-containers09:10
*** mathspan_ has joined #openstack-containers09:14
*** mathspanda has quit IRC09:18
*** shuquan has joined #openstack-containers09:21
*** mathspan_ has quit IRC09:22
*** wanghua has joined #openstack-containers09:24
*** diga has quit IRC09:25
openstackgerritHua Wang proposed openstack/magnum: Add registry to template  https://review.openstack.org/22352609:30
madhuriyuanying: Hi, you there?09:34
openstackgerritMa Wen Cheng proposed openstack/magnum: Sync the description with Kubernetes Release 1 version  https://review.openstack.org/22622209:34
openstackgerritHua Wang proposed openstack/magnum: Code refactor for keystoneclient  https://review.openstack.org/21869909:37
*** shuquan has quit IRC09:45
*** shuquan has joined #openstack-containers09:47
*** dims has joined #openstack-containers09:47
openstackgerritMerged openstack/python-magnumclient: Change ignore-errors to ignore_errors  https://review.openstack.org/22581809:48
*** Shijia_ has quit IRC09:54
*** erw has joined #openstack-containers09:54
*** chandankumar has joined #openstack-containers09:58
*** ewindisch has joined #openstack-containers09:58
*** halfss has quit IRC10:03
*** shuquan has quit IRC10:04
*** shuquan has joined #openstack-containers10:11
*** shuquan has quit IRC10:22
i316653Is anyone here to help with an installation? I've just a few questions. I think most people here are US western time so GMT 17:00 is possibly a better time to get envolved!10:22
i316653*involved10:22
wanghuai316653: hi10:24
i316653@wanghua Hi, Could you help me with some questions about Magnum?10:25
wanghuai316653:ok, if I know10:25
i316653I have a source install of openstack (not via devstack) and I'm trying to get Magnum working. I can create a  baymodel no problem using a fedora-21-atomic-3 image, but when I create a bay it errors out with no valid hosts found? I haven't a clue what needs setup from there to allow it to find hosts on the netowork10:27
*** ganeshna has joined #openstack-containers10:27
i316653Do I need to create a nova instance and set it up to work with Magnum? Does it manage this itself using heat?10:28
wanghuaYou need not to create nova instance manually.10:29
wanghuaIt is created by magnum automatically.10:29
wanghuaHow many cores you env has10:30
wanghuaI think you can look into nova log to see why no valid host found10:30
wanghuanova-scheduler.log will tell you why10:31
i316653My env has 80 cores10:32
i316653I'll try running again and studying the logs. It looks likely because I setup a nova instance on that environment, it may of taken all resources?10:35
openstackgerritMerged openstack/magnum: Sync the description with Kubernetes Release 1 version  https://review.openstack.org/22622210:36
wanghuahow many host do you have10:38
wanghuaIf one, you can use nova hypervisor-show `hostname` to query the resources info10:38
i316653what value am I looking for?10:39
i316653I have got http://paste.openstack.org/show/lB3bHX5fne0JSi9fVclf/10:40
wanghuacore, ram, disk10:40
wanghuahypervisor_type ironic?10:41
i316653Yeah10:42
wanghuaAs I know, magnum has some bugs on ironic10:42
i316653What other approaches would you recommend?10:43
wanghuaWhy you need ironic10:43
wanghuaOr you just want to play with magnum10:43
wanghuahttps://bugs.launchpad.net/magnum?field.searchtext=ironic&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=10:44
i316653It's part of our larger openstack build10:45
wanghuaThe ironic bugs have not been fixed.10:45
i316653Oh, I see that now, what other ways is there to get magnum working? Is it possible without using ironic or would I need to do a devstack install of openstack?10:47
wanghuahttp://docs.openstack.org/developer/magnum/dev/dev-quickstart.html10:48
wanghuaYou can install magnum according to this tutorial10:48
i316653Thanks a million! @wanghua I will have a look into devstack to continue CaaS with openstack and revisit where I was in a while!11:03
*** ganeshna has quit IRC11:07
*** erkules_ is now known as erkules11:30
*** erkules has joined #openstack-containers11:30
*** deepthi has quit IRC11:32
*** julim has joined #openstack-containers11:37
*** zz_dimtruck is now known as dimtruck11:59
openstackgerritMerged openstack/magnum: Functional tests with Tempest - BayModel CRUD  https://review.openstack.org/22417012:00
*** dimtruck is now known as zz_dimtruck12:02
*** zz_dimtruck is now known as dimtruck12:34
*** achanda has joined #openstack-containers12:41
*** achanda has quit IRC12:42
*** xek has joined #openstack-containers12:47
*** alejandrito has joined #openstack-containers12:47
*** Tango has joined #openstack-containers12:52
*** rlrossit has joined #openstack-containers12:58
*** yuanying_ has joined #openstack-containers13:01
madhuriyuanying: Hi13:01
*** tbh has quit IRC13:02
madhuriyuanying_: Hi13:03
*** chandankumar has quit IRC13:05
*** dims has quit IRC13:14
*** dims has joined #openstack-containers13:15
yuanying_hi yuanying13:21
yuanying_misstake13:21
yuanying_hi madhuri13:21
madhuriyuanying_: Hi, I got into an issue13:25
madhuriWhere kube-apiserver was not running13:25
madhuriBut I think I get the issue13:25
madhuriI had to use fedora-atomic-513:26
madhuriThanks :)13:26
yuanying_maybe, kube v1 issue13:26
yuanying_I still use fedora-atomic-313:26
madhuriYes it is13:27
madhuriI will leave in 10 mins.13:28
madhuriHave a good night yuanying_13:28
yuanying_good night madhuri13:28
madhuriyuanying_: I think there is still issue with it.13:32
*** hongbin has joined #openstack-containers13:32
madhuriI see kube-apiserver running but all commands fail13:32
madhuriSome issue with kubernetes vq13:33
yuanying_at fedora-atomic-3?13:33
madhuriSorry v113:33
madhurifedora-atomic-513:33
madhuri[minion@fi-6lqbvanhh4-0-4fh4cja6js3k-kube-master-ddgqkm5fq6tz ~]$ kubectl get pods error: couldn't read version from server: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: connection refused13:33
yuanying_hmm13:34
madhurihongbin: might have idea about it13:34
yuanying_who doesn implement kube v1 heat templates?13:34
madhuriTango and hongbin13:35
madhurihongbin will you be around for an hour or so?13:35
hongbinyes13:35
madhuriyuanying_: I have to rush for cab.13:35
madhuriCatch you later13:36
yuanying_ok13:36
madhuriBye hongbin yuanying_13:36
*** madhuri has quit IRC13:36
hongbinyuanying_: hey, what is your question?13:36
yuanying_actually, I didn’t check around kube api v113:37
hongbinok13:37
yuanying_madhuri said, my templates doesn’t work at fedora-atomic-513:37
yuanying_I’m not sure what change is exist between v1 to v1beta313:38
hongbinyuanying_: check this review I046931ad491e8b7ee45943852901eac5c3df913e13:39
hongbinTongo modified the template to make it work with the *-5 image13:39
hongbinYou possibly need to apply his change.13:40
yuanying_thanks13:40
yuanying_oh, this templates is merged today13:40
TangoHi everyone, the templates that are merged already in patch 207299 should work13:40
TangoIf you get error, please let me know13:41
TangoOne thing I do run into occasionally is that etcd fails to come up, and that breaks k8s13:42
yuanying_hmm13:42
hongbinI guess it has something to do with the etcd discovery endpoint13:42
hongbinThe etcd cluster need to access public etcd discovery service to bootstrap. If the internet access is unstable, that might fail13:43
hongbinNeed to setup a local etcd discovery service to mitigate that13:44
*** fawadkhaliq has joined #openstack-containers13:44
TangoI do know my environment has a flaky switch so the external connection is flaky, so the etcd problem I see is probably just due to my set up.13:45
Tangousually I just restart the etcd service and it would be fine13:46
hongbink13:46
*** rpothier has joined #openstack-containers13:48
openstackgerritMotohiro/Yuanying Otsuka proposed openstack/magnum: [WIP] Add TLS support in heat kubernetes template  https://review.openstack.org/20287313:53
openstackgerritHongbin Lu proposed openstack/magnum: Docs update for new fedora atomic 1.0.4  https://review.openstack.org/22150413:54
*** fawadkhaliq has quit IRC13:59
*** fawadkhaliq has joined #openstack-containers14:01
*** fawadk has joined #openstack-containers14:02
*** dane_leblanc has joined #openstack-containers14:02
*** fawadkhaliq has quit IRC14:05
openstackgerritMurali Allada proposed openstack/magnum: WIP: Adding support for public baymodels  https://review.openstack.org/22633514:07
*** irenab_ has joined #openstack-containers14:08
*** fawadkhaliq has joined #openstack-containers14:09
*** irenab has quit IRC14:11
*** irenab_ is now known as irenab14:11
*** fawadk has quit IRC14:11
*** vimal has quit IRC14:17
*** wshao has joined #openstack-containers14:28
*** harshs has joined #openstack-containers14:29
*** banix has joined #openstack-containers14:31
*** Marga_ has joined #openstack-containers14:37
*** fawadkhaliq has quit IRC14:39
Tangohi hongbin14:44
TangoI am looking for your earlier patch where you added the option for discovery_url for etcd14:45
Tangowonder if you might have the link14:45
* hongbin finding the link14:45
hongbinTango: Here you go I9dd3a47f6d50ebadf74c4ee65701183f18c9d62914:46
TangoI want to look at an example how the api code handles the new option. I am trying to pass the password and got the client code, but somehow the api code is not forwarding to the RPC request14:47
*** harshs has quit IRC14:47
hongbinHere is the github commit link https://github.com/openstack/magnum/commit/bcdd70cf1e1fd1c1c52587202bf5a9a38703a44d14:47
hongbinTango: Another example is the adding of network_driver https://github.com/openstack/magnum/commit/c0ad7c376e18c500136fa39f8097b340cfe40fbf14:49
Tangook, thanks hongbin14:50
hongbinwelcome14:50
klindgrenhello - what release of the magnum client should be used with a kilo release of magnum.  Seems like there are only a few tags?  I was trying to use 0.0.1 - because everything else has liberty requirements.14:53
klindgrenHowever I couldn't setup a baymodel - because the client didn't support the required field --coe14:54
*** banix has quit IRC15:06
*** yuanying_ has quit IRC15:07
*** banix has joined #openstack-containers15:12
*** harshs has joined #openstack-containers15:12
*** annegentle has joined #openstack-containers15:14
*** Drago has joined #openstack-containers15:15
*** ganeshna has joined #openstack-containers15:16
*** dims has quit IRC15:20
*** Drago has quit IRC15:22
*** Drago has joined #openstack-containers15:23
*** j___ has quit IRC15:25
*** puranamr has joined #openstack-containers15:27
*** annegent_ has joined #openstack-containers15:27
*** puranamr has quit IRC15:27
*** dims has joined #openstack-containers15:28
*** harshs has quit IRC15:28
*** banix has quit IRC15:30
*** annegentle has quit IRC15:30
*** banix has joined #openstack-containers15:35
*** annegent_ has quit IRC15:36
*** annegentle has joined #openstack-containers15:36
*** i316653 has quit IRC15:39
*** Drago has quit IRC15:43
*** Drago1 has joined #openstack-containers15:43
hongbinklindgren: I saw there is a stable/kilo branch. Have you tried it?15:44
klindgrencan't pip install a stable/kilo branch of the client ;-) or atleast as far as I know you can't15:46
openstackgerritDane LeBlanc proposed openstack/python-magnumclient: Magnum show cmds display dictionaries with unicode u chars  https://review.openstack.org/22607615:51
*** daneyon has joined #openstack-containers15:54
*** daneyon_ has joined #openstack-containers16:02
*** alex_klimov has quit IRC16:03
*** kebray has joined #openstack-containers16:03
*** kebray has quit IRC16:03
*** whydidyoustealmy is now known as shakamunyi16:03
*** kebray has joined #openstack-containers16:03
*** daneyon has quit IRC16:05
*** annegent_ has joined #openstack-containers16:06
*** eghobo has joined #openstack-containers16:06
openstackgerritHongbin Lu proposed openstack/magnum: Implement bay monitoring and notifications  https://review.openstack.org/21533516:06
*** annegentle has quit IRC16:07
*** eghobo_ has joined #openstack-containers16:09
*** devkulkarni has joined #openstack-containers16:11
*** eghobo has quit IRC16:13
*** Marga_ has quit IRC16:13
devkulkarnihey folks.. I am looking for information about parameters that are passed in to magnum cli commands. Specifically, the magnum container-create command optionally takes in a json representation of the container. Where can I find information about what should be passed in the json body?16:14
openstackgerritMerged openstack/magnum-ui: Add magnum api client  https://review.openstack.org/22261716:17
*** puranamr has joined #openstack-containers16:17
*** chandankumar has joined #openstack-containers16:19
*** madhuri has joined #openstack-containers16:24
madhurihongbin: Hi16:24
*** sthillma has joined #openstack-containers16:25
*** sthillma_ has joined #openstack-containers16:26
*** BertrandN has quit IRC16:27
*** sthillma has quit IRC16:29
*** sthillma_ is now known as sthillma16:29
*** gangil has joined #openstack-containers16:32
*** Marga_ has joined #openstack-containers16:33
madhurihongbin: Are you around?16:39
*** annegent_ has quit IRC16:40
*** annegent_ has joined #openstack-containers16:42
madhuriTango: You around?16:45
devkulkarnimadhuri: hi16:45
devkulkarnimadhuri: I am looking for information about parameters that are passed in to magnum cli commands. Specifically, the magnum container-create command optionally takes in a json representation of the container. Where can I find information about what should be passed in the json body?16:46
madhuriHi devkulkarni16:46
*** harshs has joined #openstack-containers16:46
madhuriPlease wait16:46
devkulkarnisure16:46
*** david-lyle has quit IRC16:46
madhuridevkulkarni: Did you check quickstart?16:47
madhuridevkulkarni: https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-quickstart.rst16:47
*** achanda has joined #openstack-containers16:47
madhuriThis gives a simple example of creating container16:48
*** annegent_ has quit IRC16:48
devkulkarnimadhuri: thanks. I was following this: http://docs.openstack.org/cli-reference/content/magnumclient_commands.html16:48
devkulkarnimadhuri: I see an example of container-create in quick-start. cool. I assume that the json body is essentially contains as all the flags that are specified in the example16:50
devkulkarnimadhuri: regarding the 'image' flag in container-create .. where is that image located? is it glance?16:51
madhurimadhuri: These can be any docker container16:54
*** fawadkhaliq has joined #openstack-containers16:56
madhuridevkulkarni: This can be any docker container image16:56
madhuridevkulkarni: gkance image is just to deploy a bay16:56
*** Marga_ has quit IRC16:59
*** vilobhmm11 has joined #openstack-containers17:00
*** Marga_ has joined #openstack-containers17:00
*** adrian_otto has joined #openstack-containers17:01
*** Marga_ has quit IRC17:02
*** Marga_ has joined #openstack-containers17:03
*** gangil has left #openstack-containers17:05
*** Marga_ has quit IRC17:05
Tangomadhuri: Hi Madhuri17:05
*** Marga_ has joined #openstack-containers17:06
*** banix has quit IRC17:07
*** kebray has quit IRC17:09
*** ganeshna has quit IRC17:10
*** puranamr has quit IRC17:10
*** ganeshna has joined #openstack-containers17:10
*** suro-patz has joined #openstack-containers17:11
*** dimtruck is now known as zz_dimtruck17:12
*** devkulkarni has quit IRC17:14
Tangomadhuri: going to the office now, be back in 30 mins17:14
*** unicell has joined #openstack-containers17:14
*** achanda_ has joined #openstack-containers17:17
*** achanda has quit IRC17:17
*** Tango has quit IRC17:19
*** Marga_ has quit IRC17:20
*** Marga_ has joined #openstack-containers17:20
*** Marga_ has quit IRC17:21
*** diga has joined #openstack-containers17:21
*** kebray has joined #openstack-containers17:22
*** devkulkarni has joined #openstack-containers17:26
*** kebray has quit IRC17:26
hongbinmadhuri: just came back from lunch17:28
madhuriHi hongbin17:30
hongbinmadhuri: hey17:30
madhuriI created a k8s bay with fedora-atomic-517:30
madhuriAnd the k8s API doesn't seems to work17:30
hongbin.....17:31
hongbinany error?17:31
madhuriYes I sent it earlier17:31
*** dims has quit IRC17:31
madhuriI don't have it now17:31
*** puranamr has joined #openstack-containers17:31
madhuriIts late here, so won't be able to share again17:31
madhuriWhat is time there?17:32
*** dims has joined #openstack-containers17:32
hongbin1:32 pm17:32
hongbinyou are in indian?17:32
madhuriYes17:32
hongbinI see17:32
madhuriSo can we discuss tomorrow morning17:32
hongbinsure17:32
madhuriWhat time zone are you in?17:32
hongbinToronto17:32
*** Marga_ has joined #openstack-containers17:33
*** puranamr has quit IRC17:33
*** Marga_ has quit IRC17:34
*** Marga_ has joined #openstack-containers17:34
devkulkarnimadhuri: thanks17:34
madhuridevkulkarni: you're welcome17:34
madhurihongbin: I will leave a mail to you or if possible I will catch you tomorrow morning at 8:30 IST17:35
hongbinmadhuri: K. See you later17:36
devkulkarnimadhuri: still one more question actually. I understand that for bay creation the image is read from glance. but for the container-create command can the container image be in glance?17:36
hongbindevkulkarni: No, container image is downloaded from docker hub17:36
devkulkarnihongbin: I see17:37
madhuriNo devkulkarni, docker hub is the registry17:37
madhurihongbin: I will catch you tomorrow17:37
devkulkarnihongbin: is there any plan for supporting glance/swift in the container-create?17:37
madhuridevkulkarni: hongbin bye17:37
devkulkarnilater madhuri17:37
*** puranamr has joined #openstack-containers17:37
hongbinmadhuri: good night17:37
*** madhuri has quit IRC17:38
*** snrism has joined #openstack-containers17:39
hongbindevkulkarni: Check out this blueprint, it suggest to create a private docker registry and use swift as backend https://blueprints.launchpad.net/magnum/+spec/registryv2-in-master17:40
devkulkarnihongbin: thanks for the link17:41
devkulkarnilooking17:41
*** sthillma has quit IRC17:44
*** zz_dimtruck is now known as dimtruck17:44
openstackgerritMerged openstack/python-magnumclient: Magnum show cmds display dictionaries with unicode u chars  https://review.openstack.org/22607617:44
*** Tango has joined #openstack-containers17:49
devkulkarnihongbin: seems interesting. have few questions. how would one push custom docker images to the docker registry on each node of a bay? or, that is not necessary as the custom image can be stored in swift and Docker Distribution magic will make it appear in the docker registry on each node?17:49
hongbindevkulkarni: I am not working on that bp, need someone else to clarify it17:51
devkulkarnihongbin: ok17:51
hongbindevkulkarni: maybe you can send an email for the question17:51
devkulkarnihongbin: sure. I will also add myself to receive notifications on that bp17:52
hongbincool17:52
devkulkarniand will add my question there17:52
hongbinsure17:52
devkulkarnithanks hongbin17:52
*** chandankumar has quit IRC17:52
*** chandankumar has joined #openstack-containers17:55
*** rlrossit1 has joined #openstack-containers17:57
*** fawadkhaliq has quit IRC17:58
*** rlrossit has quit IRC17:58
*** ganeshna has quit IRC18:06
*** sthillma has joined #openstack-containers18:07
*** snrism has quit IRC18:08
*** chandankumar has quit IRC18:08
*** puranamr has quit IRC18:09
*** snrism has joined #openstack-containers18:11
*** achanda has joined #openstack-containers18:23
*** achanda_ has quit IRC18:24
*** snrism_ has joined #openstack-containers18:25
*** diga has quit IRC18:27
*** snrism has quit IRC18:28
*** jwcroppe has joined #openstack-containers18:29
*** vilobhmm11 has quit IRC18:32
*** vilobhmm11 has joined #openstack-containers18:32
openstackgerritSurojit Pathak proposed openstack/magnum: Backend support for magnum service healthcheck  https://review.openstack.org/22070218:35
vilobhmm11hongbin : ping18:36
hongbinvilobhmm11: yo18:36
vilobhmm11looks like the k8s_api changed a lot after your v1 patch merged in18:36
vilobhmm11just rebasing my change according to that18:36
hongbinack18:37
vilobhmm11I did saw your comment on the objects from bay patch18:37
*** snrism has joined #openstack-containers18:38
hongbinSorry, I should ask you to set a dependency on v1 patch18:38
hongbinhope rebasing won't incur too much overhead18:39
openstackgerritSurojit Pathak proposed openstack/magnum: Adding API support for magnum service  https://review.openstack.org/22607818:39
*** snrism_ has quit IRC18:41
*** ganeshna has joined #openstack-containers18:41
openstackgerritHongbin Lu proposed openstack/magnum: Fix funtional gate: specify missing network_driver  https://review.openstack.org/22649118:42
*** achanda has quit IRC18:42
*** ganeshna has quit IRC18:43
*** ganeshna has joined #openstack-containers18:44
*** ganeshna has quit IRC18:47
*** ganeshna has joined #openstack-containers18:47
*** achanda has joined #openstack-containers18:48
openstackgerritSurojit Pathak proposed openstack/magnum: Documentation update for 'magnum service-list'  https://review.openstack.org/22613318:48
klindgrenI have a question regarding the heat templates for a kube cluster creation.  It looks like there is a strong bias towards having end users create routers/private networks.  We don't do that in our environment, we are bascially doing flat networks with neutron.18:49
klindgrenI am looking at changing the heat templates - to support not doing private networks, it looks like in the comments for the templates this could be supported - but.. I want to make sure I understand what the req is for private networks and how they are used18:51
*** ganeshna has quit IRC18:51
openstackgerritDaneyon Hansen proposed openstack/magnum: WIP: Updates Swarm Heat Templates for Container Network Model  https://review.openstack.org/22436718:53
suro-patzdaneyon_: adrian_otto: you want to answer the question above from klindgren:? klindgren: is looking for a rollout of magnum18:55
* adrian_otto looking at scrollback18:56
daneyon_suro-patz thx for the heads-up18:56
klindgrenI just don't want to go in all crazy pants changing heat templates :-) - without understanding why they are doing what they are doing18:56
daneyon_klindgren I suggest sending a message to the ML before making changes to the heat templates.18:57
suro-patzdaneyon_: np18:57
adrian_ottoklindgren: great question. The issue is not so much the creation of isolated networks per bay, but how to make the bays accessible…. It's really more of an IPAM concern.18:58
klindgrenI assume opestanck-dev with the [magnum] tag18:58
klindgrenopenstack-dev*18:59
adrian_ottodepending on how you set up Nova, you might not be able to access your nova instances unless they have neutron assigned addresses18:59
daneyon_klindgren magnum will leverage whatever neutron networking you have implemented in your OS cloud. All you need to do is provide the id or name to external_network_id. external_network_id is the id/name of your neutron network that will assign floating ip's to the kube master/minions.18:59
adrian_ottokeep in mind that external-lb assumes that a neutron LB will be used to front-end apps that run within the k8s cluster on the bay.19:00
*** jcrubio has joined #openstack-containers19:00
adrian_ottoklindgren: will you be running apps that you expect will be load balanced using k8s "services"?19:01
suro-patzdaneyon_: I think the question is do we absolutely need neutron to deploy magnum. As there are a good number of nova-network deployment. Can magnum be rolled over nova-network?19:01
adrian_ottosuro-patz: strictly speaking, no we don't support nova-network today19:01
klindgrendaneyon_, see the thing is our networking setup is pretty unique.  Well neutron unique (not unique in the datacenter space).  So we already have a router created that ties the floating-ips network with the networks that vm's get.19:01
adrian_ottobut there are some simple use cases that would still work without neutron19:02
*** banix has joined #openstack-containers19:02
klindgrenBut we also route floating_ips to vm's vs's creating a L3 router to do it19:02
*** snrism has quit IRC19:02
adrian_ottoklindgren: ok, so it sounds like further work would need to be done to integrate the Kubernetes external-lb feature with what you are doing19:03
suro-patzadrian_otto: I think that might help some people to do POC deployment of magnum with nova-network19:03
adrian_ottounless you did all that as a neutron plugin, which it does not sound like what you described19:03
klindgrenadrian_otto, working on the POC to try to answer that.  I assume yes - we are working on getting a PCO using LBaaS working - but we identified a number of gaps with our LB vendor and their LbaaS integration19:03
adrian_ottosuro-patz: yes, that would be helpful. I don't think we are there yet though.19:04
daneyon_klindgren the neutron routers created by the heat templates are not used for floating-ip's. magnum expects an existing neutron floating-ip network (external_network_id) to be available.19:04
daneyon_How this existing floating-ip network is implemented does not matter to Magnum. Magnum will simply make the Neutron API call's to ask for a floating-ip from this network you provide and assign the ip to the kube master and minions.19:05
daneyon_klindgren I would take some more time diving into the heat-templates, do some test deployments, etc.. before considering any changes.19:06
* adrian_otto stepping out for lunch, then meetings adfter19:07
*** kebray has joined #openstack-containers19:07
daneyon_as for supporting nova-network, I would +1 if it's implementation is aligned with the goals of the magnum project.19:07
*** adrian_otto has quit IRC19:08
klindgrenI guess I am totally confused why the router is created then?  The issue is the default templates are pretty biased to services that you have to have running in the cloud (LBaaS, Cinder) so no matter what, to even poc I need to make changes to the template since we currently provide neither19:08
*** kebray has quit IRC19:08
*** kebray has joined #openstack-containers19:08
daneyon_suro-patz we do need  neutron b/c we make neutron-specific calls through our heat templates. We could support nova-net, it just comes down to implementing the codes and the implementation needs to align with the goals of the magnum project.19:08
suro-patzdaneyon_: Agree, but that code/template does not exist today. As a community, we have not invested in that19:09
*** jcrubio has quit IRC19:09
suro-patzKlindgren: as adrian_otto: suggested for POC, those changes/additional templates are welcome19:10
daneyon_klindgren cinder is needed to attach a vol to the nodes for mounting the docker container ns share.19:11
daneyon_klindgren a router is created, kube master/nodes are attached, etc..19:12
suro-patzdaneyon_: but cinder volume attachment is again not a necessity, as I understand19:13
daneyon_klindgren for POC purposes, why not use devstack?19:13
klindgrenis that volume moved around, when clusters are updated/changed or is it that you just wanted an extra disk associated with the instances?19:13
daneyon_lbass for ha/scaling kube services such as the api, etcd, etc..19:14
daneyon_the templates are focused on providing prod services and not a demo env. That is why we mount a cinder vol for the docker container ns.19:15
daneyon_the vol allows a user to take advantage of a cinder backend for storage mgt instead of having the containers running on ephemeral storage.19:16
daneyon_for poc/demo purposes, I suggest using devstack. It will provide a full-featured magnum experience.19:17
daneyon_I'm -1 for supporting demo/poc focused heat templates that strip out functionality. IMO we already have too many templates to support.19:18
eghobo_daneyon_: +1 for # templates19:19
daneyon_We are in the process of refactoring the templates to simplify things and reduce the number of templates. Here is the bp: https://blueprints.launchpad.net/magnum/+spec/generate-heat-templates Feel free to connect with tcammann1 tcammann_ on ideas related to improving the templates.19:20
*** rlrossit1 has quit IRC19:23
daneyon_For example, Ii added network-driver and labels support to the kube templates. I'm in the process of adding network-driver and labels support to swarm. The current swarm templates are quite different than the kube one's and it's taking me far too much time. If we execute on https://blueprints.launchpad.net/magnum/+spec/generate-heat-templates adding a feature across all bay types should be very simple.19:23
*** eghobo_ has quit IRC19:24
*** rlrossit has joined #openstack-containers19:25
*** puranamr has joined #openstack-containers19:27
*** puranamr has quit IRC19:28
*** wshao has quit IRC19:30
openstackgerritVilobh Meshram proposed openstack/magnum: Objects from Bay : Retrieve k8s API client  https://review.openstack.org/22034419:31
*** snrism has joined #openstack-containers19:32
*** adrian_otto has joined #openstack-containers19:33
*** rlrossit has quit IRC19:36
*** snrism has quit IRC19:37
*** achanda has quit IRC19:37
*** rlrossit has joined #openstack-containers19:38
*** bradjones has joined #openstack-containers19:46
*** bradjones has quit IRC19:46
*** bradjones has joined #openstack-containers19:46
*** kebray has quit IRC19:57
*** kebray has joined #openstack-containers19:58
*** banix has quit IRC20:01
*** annegentle has joined #openstack-containers20:02
klindgrensorry - back daneyon_ demo/poc in devstack is useless to me and my company.  Part of the POC is can I actually get magnum to work in my environment, and if I can with what feature set limitations (if any).  We are trying to roll out a company wide answer for containers, be that magnum (which we are rooting for) - nova-docker - docker via heat templates.20:04
klindgrenAll I am trying to do right now is figure out the requirement for kube cluster to be in its own private network with its own route attached to a provider network.  Seems like this based upon the assumption that this is how networking is done in the cloud, and this just creates those primitives to give the kube network a way to talk to the internet/ rest of the network.  I assume however, these primitives get used later on w20:05
klindgrenhen trying to do floating ips/lbaas for services (jsut what I am attempting to glean from looking at the heat templates).20:05
*** dane_leblanc has quit IRC20:05
klindgrenIn our cloud, every vm is plugged into the provider network, so they have network access through a real network gateway (vs's a linux box running hte l3 agent and iptables in a network name space) similarly floating ip support is handled via routing the IP in the network to the fixed_ip of the vm' vs's added a dnat rule on a router.20:06
klindgrenSo my main concern is how inside magnum and kube is the private network expected to be used?20:06
klindgrenAre the minions and the kube master tied to the same internal network with flanneld running on top of that and then micro-services exposed to end users via a floating ip?  What are the possible down sides of having multiple bay's attempting to run on the same provider network - without their own private network?20:07
klindgrenI guess what I really need is a design doc/spec that talks about what a bay is suppose to provide of kube - so I can answer some of these questions my self, and another on how containers will use the network provided for them by neutron20:08
daneyon_klindgren I have not deployed magnum on a neutron setup that uses provider networks, but it should work. You need to provide the name or uuid of the provider network to magnum when instantiating your baymodel using the external_network_id baymodel config flag.20:08
daneyon_klindgren it's been a while since i've used provider networks, but it's starting to come back to me now. I used to worked with provider networks quite a bit b/c of the l3-agent ha/scale issue.20:11
*** sthillma has quit IRC20:11
*** snrism has joined #openstack-containers20:12
*** eghobo has joined #openstack-containers20:13
*** achanda has joined #openstack-containers20:15
klindgrendaneyon_, I do that however - normal users on our cloud can't create a private network or a router.  So in the templates: https://github.com/openstack/magnum/blob/master/magnum/templates/heat-kubernetes/kubecluster-coreos.yaml#L120-L14920:16
daneyon_klindgren give me 5 min to look through the provider network doc's again.20:16
*** sthillma has joined #openstack-containers20:18
*** manjeets has joined #openstack-containers20:18
manjeetshongbin: ping20:18
klindgrenseems like thats exactly what thats trying to do?  But the comment makes it seem like this is only done for ease of use?20:19
klindgrendaneyon_, our network config is bascially: http://docs.openstack.org/havana/install-guide/install/apt/content/section_use-cases-multi-flat.html20:19
hongbinmanjeets: what's up20:20
klindgrenwith some additional tweaks/restrictions thrown in20:20
manjeetsyou removed dependency from patch ?20:21
manjeetsshould i remove WIP from it as well since its implemented ?20:21
manjeetshongbin:20:21
hongbinmanjeets: you are refering a review? which one?20:22
manjeetshttps://review.openstack.org/#/c/221504/20:22
daneyon_klindgren thaks for the info. the magnum router gets attached to your provider network. You need to supply magnum the name or id of the provider network using the external_network_id of your desired provider network when creating your baymodel.20:23
hongbindaneyon_: I think klindgren problem is that users don't have permission to create private net and router20:24
daneyon_The router will use IP's from the associated subnet of the provider network to assign to the neutron lbaas services and assign a floating-ip to the kube master/nodes.20:25
klindgrenI think we are talking past each other.  In our clouds users dont create networks and they dont create routers.  So the router create in the heat template fails.20:26
manjeetshongbin: https://review.openstack.org/#/c/221504/20:27
klindgrenso it sounds like, in my env I can change the assumption to that a floating_ip is all thats ultimately need for the lbaas services and the the kube masters/nodes and as long as that is able to provided it should work20:27
*** wshao has joined #openstack-containers20:28
klindgrenthe details of how a floating_ip is allocated is currently hard-coded into the template under the assumption that a router + external network id is needed for a flaoting IP to get allocated to a fixed_ip of an instance20:28
hongbinklindgren: so if you can change the heat template, what you would like to change?20:29
daneyon_klindgren see if the existing templates will work in your env. I understand magnum does not deploy the cluster in the same manner as you deploy vm's in your current env. I don't think magnum will ever replicate all the diff ways to deploy an OS cloud. Try playing around with the templates to meet the needs of your environment.20:31
daneyon_Before submitting a review to get any custom changes merged, I suggest filing a bp b/c imo it will take more than heat template changes to support different network topologies, etc..20:32
*** wshao has quit IRC20:32
hongbinWell, if klindgren env is a typical setup, then I think it is fine to make the adjustment on the template20:33
hongbinThe template should represent a setup that works in most of the cases20:34
daneyon_^ simply changing the heat templates can work, but more is needed by the conductor and api.20:35
daneyon_hongbin agreed20:35
daneyon_our template does work in most cases.20:35
klindgrenhongbin, thats a good question - I am not sure how to answer that at this point.  I get what what is done - has been done.  At this point I am just trying to figure out if this is done a specific way because thats the typical way to do it in neutron - or if their is additional assumptions made about tenant isolation20:35
daneyon_I'm +1 for adding provider networking support (if changes are even needed), but if we simply change the templates to work with provider networks, then they will not work in non-provider network setups.20:36
klindgrenI know some other larger enterprise deployments have similar kinda of networking to what we do.  I htink if this can work on nva-networking then it would work in my env as well.20:36
klindgrendaneyon_, agreed20:37
daneyon_imo we would need to expose an attr in the baymodel api such as --neutron-type that would allow a user to keep the default, select provider-networking, etc..20:37
klindgrenI think it comes down to are you doing mutli-tenant networking or not20:38
daneyon_I think trying to replicate a magnum cluster deployment to look just like the OS undercloud is a mistake. Too many variations. The cluster (i.e. bay type) should just work, calling the api's of the OS services. Granted, certain OS undercloud services must be available (i.e. Heat, Neutron, etc..).20:39
daneyon_adrian_otto feel free to chime in.20:39
klindgrenwhere multi-tenant allows everyone to create their own networking stack and non-multi-tenant is use the networking stack thats provided20:40
daneyon_klindgren agreed. I worked with several operators in the past that implemented provider networks. I created several OS HA guides that leveraged provider networks for HA and scale.20:40
klindgrenI would say at this point the majority of my end-users use cases (99%) are give me a compute resource thats has an ip in this network (which is typically more of a set of cidr's that have special meaning in the company (dev/test/prod/pci/pki)20:41
daneyon_I think magnum should be able to run on an OS cloud that uses provider networks. However, I don't believe the magnum bay deployment should be = to how existing operators deploy. It's a slippery slope of supporting a million different combinations.20:42
klindgrendaneyon_, I agree with you.20:43
daneyon_We should be able to specify the neutron external-network-id within the baymodel and have magnum plug bay's (i.e. the router's gw interface, master/minion floating-ip's) into that network.20:44
daneyon_klindgren, so does each of your tenant's have their own provider network?20:45
klindgrenthats something that we are restling with as well - as an enterprise do we really want every tenant to spinup a k8 cluster (and have to support that many possible clusters) or do we want to use magnum to spinup a few large enterprise clusters and ideally have minons in each tenant that can be used to house those projects containers20:45
klindgrendaneyon_, nope their are shared across every tenant20:45
openstackgerritManjeet Singh Bhatia proposed openstack/magnum: Docs update for new fedora atomic 1.0.4  https://review.openstack.org/22150420:47
klindgrenat current count we have like 4.5k tenants - if half of those want to do containers - we are duplicating a ton of infrastructure for possibly 3-4 containers20:47
adrian_ottook, so I'm partial to keeping it simple. Supporting every network topology under the sun is intractable.20:47
adrian_ottoin terms of whether an enterprise should allow its developers to have their own bays, or share them...20:47
adrian_ottothat's a decision that requires asking a lot of questions20:48
adrian_ottoin general, the overhead of running a bay is relatively low, but if you're going to be running thousands of them, then it will gradually add up.20:48
klindgrenadrian_otto, agreed - we (the openstack team at our company) are still trying to figure out how the people at our company are using containers20:48
klindgrenand what do they want to see - offset by the possible support/infra overhead on our end20:49
adrian_ottoklindgren: are you primarily concerned with offering business agility, standardizing support, or maximizing operational efficiency?20:49
klindgrenI am not opposed to the bay per tenant - but I know the "death by a thousand cuts"20:50
daneyon_klindgren I have to get ready for a meeting. Try the existing templates to see if you can simply plug magnum into your existing provider network. It would be helpful to know if that works, as it should. If you need to make changes to the templates to meet your needs, send a message to the ML and let's see how we can proceed in a manner that is consistent with the goals of the project.20:50
adrian_ottoMy suggestion would be to allow a bay per team at least, and see what sorts of bays they create, and ask them why they make those choices20:50
klindgrenCan I pick all three :-)20:51
adrian_ottoyes.20:51
klindgrenI would say the biggest two are business agility and standardization of support20:51
klindgrenour end users would love to try to stop woring about the infra pieces and start caring more about deploying code20:51
adrian_ottoif you want all three, then you probably want to have a nova that can create containers with the libvirt/lxc driver20:52
adrian_ottoand use those nodes to compose bays20:52
adrian_ottothat way you will get more dense packing of bays per compute node20:52
adrian_ottoand relatively high performance.20:52
adrian_ottogive your devs the ability to create their own bays, and customize their own bay node images.20:53
adrian_ottothen they can use the native tooling of their choice to interact with those bays.20:53
*** annegentle has quit IRC20:54
adrian_ottofor standardization of support, you can use a business policy (may not need technical enforcement) to suggest that a particular bay type (or list of types) will be supported by your team, and others will be use-at-your-own-risk…. or whatever makes sense in your corporate culture.20:56
manjeetsadrian: i agree there should some set of supported images and they should also be documentation if user wants own custom image20:57
manjeetsat own risk20:58
adrian_ottoif you find that for you it's important to enforce a more limited selection of choice, we should propose those as features for Magnum. Something like provider-supplied baymodels (prohibiting the creation of new baymodels unless you have a particular RBAC role in the identity system, such that normal users do not have the role.)20:58
adrian_ottosometimes you have really great developers that have a good reason to do something non-standard… it might be nice to have a way to allow that, as manjeets suggested.20:59
*** suro-patz has quit IRC21:00
manjeetsi feel this support  should be there to provide customers or users with more flexibility and they should every reason to use our product21:00
manjeetsthey should have* every reason21:01
*** suro-patz has joined #openstack-containers21:02
*** rebase33 has joined #openstack-containers21:05
*** manjeets has quit IRC21:09
*** adrian_otto has quit IRC21:09
*** rpothier has quit IRC21:20
*** rlrossit has left #openstack-containers21:20
*** Marga_ has quit IRC21:21
*** kebray has quit IRC21:21
*** achanda has quit IRC21:21
*** Marga__ has joined #openstack-containers21:22
*** annegentle has joined #openstack-containers21:24
*** eghobo has quit IRC21:25
*** alejandrito has quit IRC21:32
*** adrian_otto has joined #openstack-containers21:32
*** Drago1 has quit IRC21:32
*** alejandrito has joined #openstack-containers21:33
*** eghobo has joined #openstack-containers21:40
openstackgerritTon Ngo proposed openstack/magnum: Configure CoreOS for Kubernetes load balancer feature  https://review.openstack.org/19242521:43
openstackgerritTon Ngo proposed openstack/magnum: Configure Ironic for Kubernetes load balancer feature  https://review.openstack.org/19242621:43
openstackgerritTon Ngo proposed openstack/magnum: Configure Fedora Atomic for Kubernetes load balancer feature  https://review.openstack.org/19187821:43
adrian_ottoOur team meeting will begin at 22:00 UTC (15 min from now) in #openstack-meeting-alt21:45
vilobhmm11hongbin : ping21:47
hongbinvilobhmm11: yo21:47
vilobhmm11here https://review.openstack.org/#/c/213368/8/magnum/api/controllers/v1/replicationcontroller.py #8021:47
*** snrism has quit IRC21:49
hongbinvilobhmm11: I saw it linked to my comment. You have question?21:51
vilobhmm11you wanted the bay_uuid also to be passed right…which makes sense..21:52
vilobhmm11http://paste.openstack.org/show/473631/21:52
hongbinyes, since you add bay_uuid to the endpoint21:52
vilobhmm11rcs/{uuid}/rcs/{bay_uuid}21:53
vilobhmm11or any particular format21:53
vilobhmm11sorry my n/w is diconnecting today21:53
hongbinI don't know the format21:53
vilobhmm11sorry for later reply21:53
hongbinNP21:53
hongbinI think the link returned have to be correct21:54
vilobhmm11ok…np..will figure it out…just wanted to be sure…that if you wanted some specific format21:54
vilobhmm11sure21:54
*** annegentle has quit IRC21:54
hongbinIf the link is correct, then I am happy21:54
vilobhmm11cool thanks!21:54
vilobhmm11hongbin : ^^21:54
*** annegentle has joined #openstack-containers21:54
*** snrism_ has joined #openstack-containers21:57
*** wshao has joined #openstack-containers21:58
*** suro-patz has quit IRC22:01
*** Drago has joined #openstack-containers22:01
*** suro-patz has joined #openstack-containers22:03
*** wshao has quit IRC22:04
*** hongbin_ has joined #openstack-containers22:06
*** devkulkarni has quit IRC22:06
*** dimtruck is now known as zz_dimtruck22:06
*** hongbin has quit IRC22:07
*** devkulkarni has joined #openstack-containers22:07
*** jerrygb has joined #openstack-containers22:08
*** wshao has joined #openstack-containers22:11
*** zhenguo has quit IRC22:12
*** devkulkarni has quit IRC22:12
*** gus has quit IRC22:12
*** zhenguo has joined #openstack-containers22:13
*** gus has joined #openstack-containers22:14
*** sthillma has quit IRC22:19
*** achanda has joined #openstack-containers22:22
*** jwcroppe has quit IRC22:25
*** jwcroppe has joined #openstack-containers22:26
*** briancurtin has quit IRC22:26
*** puranamr has joined #openstack-containers22:26
*** banix has joined #openstack-containers22:27
*** achanda has quit IRC22:27
*** briancurtin has joined #openstack-containers22:29
*** puranamr has quit IRC22:29
*** jwcroppe has quit IRC22:30
*** eghobo has quit IRC22:35
*** vilobhmm11 has quit IRC22:36
*** vilobhmm11 has joined #openstack-containers22:36
*** devkulkarni has joined #openstack-containers22:48
*** sthillma has joined #openstack-containers22:48
*** zz_dimtruck is now known as dimtruck22:50
*** alejandrito has quit IRC22:55
*** wshao has quit IRC22:56
*** annegentle has quit IRC22:56
*** sthillma has quit IRC22:58
*** wanghua has quit IRC23:00
*** hongbin_ has quit IRC23:01
*** adrian_otto has quit IRC23:02
openstackgerritMerged openstack/magnum: Fix funtional gate: specify missing network_driver  https://review.openstack.org/22649123:05
*** sthillma has joined #openstack-containers23:08
*** snrism_ has quit IRC23:08
*** eghobo has joined #openstack-containers23:10
*** achanda has joined #openstack-containers23:12
*** Drago has quit IRC23:16
*** vilobhmm11 has quit IRC23:17
*** vilobhmm11 has joined #openstack-containers23:18
*** dims has quit IRC23:18
*** dimtruck is now known as zz_dimtruck23:18
*** vilobhmm111 has joined #openstack-containers23:19
*** vilobhmm11 has quit IRC23:22
*** zz_dimtruck is now known as dimtruck23:29
*** rebase33 has quit IRC23:48
*** dims has joined #openstack-containers23:54
*** dims has quit IRC23:55
*** Guest18166 has joined #openstack-containers23:55
*** eghobo has quit IRC23:56
*** ganeshna has joined #openstack-containers23:56

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