Wednesday, 2015-08-19

*** sergmelikyan has quit IRC00:13
*** tiswanso has joined #puppet-openstack00:14
*** sergmelikyan has joined #puppet-openstack00:22
*** tiswanso has quit IRC00:25
*** sergmelikyan has quit IRC00:26
*** xingchao has joined #puppet-openstack00:31
*** chem has quit IRC00:34
openstackgerritXingchao Yu proposed openstack/puppet-trove: Add notification system options in trove  https://review.openstack.org/20081800:40
*** sergmelikyan has joined #puppet-openstack00:42
openstackgerritXingchao Yu proposed openstack/puppet-trove: Fix guestagent_config_file option default value  https://review.openstack.org/20843100:43
*** sergmelikyan has quit IRC00:44
openstackgerritXingchao Yu proposed openstack/puppet-trove: Fix default value of guestagent_config_file option  https://review.openstack.org/20843100:47
*** ducttape_ has joined #puppet-openstack00:49
*** sergmelikyan has joined #puppet-openstack00:52
*** tiswanso has joined #puppet-openstack00:52
*** sergmelikyan has quit IRC00:53
*** serg_melikyan has joined #puppet-openstack00:53
*** gildub has joined #puppet-openstack00:53
*** tiswanso has quit IRC00:54
*** tiswanso has joined #puppet-openstack00:54
*** gildub has quit IRC00:55
mfischEmilienM: can you or yanis take a peek at https://review.openstack.org/#/c/212091 again01:02
*** linkedinyou has joined #puppet-openstack01:12
*** sergmelikyan has joined #puppet-openstack01:17
*** sergmelikyan has quit IRC01:17
*** xarses has joined #puppet-openstack01:19
*** gildub has joined #puppet-openstack01:23
*** sergmelikyan has joined #puppet-openstack01:23
*** sergmelikyan has quit IRC01:36
*** xingchao has quit IRC01:36
*** ilbot3 has quit IRC01:44
*** xingchao has joined #puppet-openstack01:47
*** ilbot3 has joined #puppet-openstack01:47
*** xingchao has quit IRC01:52
*** xingchao has joined #puppet-openstack01:53
*** ducttape_ has quit IRC01:55
*** xingchao_ has joined #puppet-openstack01:56
*** xingcha__ has joined #puppet-openstack01:57
*** xingchao has quit IRC01:58
EmilienMmfisch: will do01:58
*** xingchao_ has quit IRC02:01
*** sergmelikyan has joined #puppet-openstack02:06
*** sergmelikyan has quit IRC02:07
*** xingchao has joined #puppet-openstack02:14
*** xingcha__ has quit IRC02:16
*** gildub has quit IRC02:27
*** ducttape_ has joined #puppet-openstack02:41
*** nigelk has joined #puppet-openstack02:45
*** ducttape_ has quit IRC02:47
*** gildub has joined #puppet-openstack02:47
*** ducttape_ has joined #puppet-openstack02:55
*** ducttape_ has quit IRC02:57
*** imcsk8_ has joined #puppet-openstack03:02
*** imcsk8 has quit IRC03:02
*** tiswanso has quit IRC03:25
*** logan2 has quit IRC03:31
*** zacdev has quit IRC03:53
gildubnibalizer, Hi, I'm trying to debug a functional upgrade test failing on puppet-keystone, I'm getting up to speed with beaker but trying to make the link with zuul04:01
gildubnibalizer, https://review.openstack.org/#/c/213598/04:01
*** xingchao has quit IRC04:02
gildubnibalizer, I'm looking for a pointer between project-config:jenkins/jobs/puppet-module-jobs.yaml and the gate-puppet-keystone-puppet-beaker-rspec-upgrade-dsvm-trusty/centos so I know what to look for when I'll ask the infra guys to hold the host for investigation04:03
*** social has quit IRC04:52
*** LimorStotland has joined #puppet-openstack05:24
*** xingchao has joined #puppet-openstack05:53
*** xingchao_ has joined #puppet-openstack05:56
openstackgerritXingchao Yu proposed openstack/puppet-trove: Add rabbit_ha_queues option  https://review.openstack.org/21445805:57
*** xingchao has quit IRC05:59
openstackgerritXingchao Yu proposed openstack/puppet-designate: Add enabled_notification_handlers option  https://review.openstack.org/21446506:08
*** sergmelikyan has joined #puppet-openstack06:12
openstackgerritXingchao Yu proposed openstack/puppet-designate: Add enabled_notification_handlers option  https://review.openstack.org/21446506:13
openstackgerritXingchao Yu proposed openstack/puppet-trove: Add rabbit_ha_queues option  https://review.openstack.org/21445806:16
*** paramite has joined #puppet-openstack06:18
*** paramite is now known as paramite|afk06:28
*** paramite|afk is now known as paramite06:28
openstackgerritMichael Polenchuk proposed openstack/puppet-nova: Activate fping api extension  https://review.openstack.org/21413206:36
*** sergmelikyan has quit IRC06:50
openstackgerritXingchao Yu proposed openstack/puppet-trove: Introduce amqp_durable_queues option  https://review.openstack.org/21447706:58
*** aimon has quit IRC06:59
*** aimon has joined #puppet-openstack07:00
*** ddmitriev1 has joined #puppet-openstack07:11
*** xingchao has joined #puppet-openstack07:12
*** xingchao_ has quit IRC07:13
*** jpena has joined #puppet-openstack07:17
*** social has joined #puppet-openstack07:21
*** jtomasek has quit IRC07:26
*** c0m0 has joined #puppet-openstack07:33
*** gfidente has joined #puppet-openstack07:35
openstackgerritSergey Kolekonov proposed openstack/puppet-neutron: Allow deployment when DVR is enabled and L2 pop and tunneling are disabled  https://review.openstack.org/21449807:53
openstackgerritYanis Guenane proposed openstack/puppet-tuskar: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20988308:01
openstackgerritYanis Guenane proposed openstack/puppet-sahara: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987708:05
*** dgurtner has joined #puppet-openstack08:09
*** gildub has quit IRC08:19
*** saikrishna has joined #puppet-openstack08:19
*** timbyr_ has joined #puppet-openstack08:21
*** markvoelker has quit IRC08:22
openstackgerritYanis Guenane proposed openstack/puppet-monasca: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987408:24
*** derekh has joined #puppet-openstack08:27
openstackgerritYanis Guenane proposed openstack/puppet-ceilometer: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20986808:28
openstackgerritYanis Guenane proposed openstack/puppet-heat: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20988208:31
*** saikrishna has quit IRC08:31
*** jistr has joined #puppet-openstack08:34
openstackgerritYanis Guenane proposed openstack/puppet-heat: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20988208:37
openstackgerritYanis Guenane proposed openstack/puppet-ceilometer: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20986808:37
openstackgerritYanis Guenane proposed openstack/puppet-sahara: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987708:38
*** v1k0d3n has quit IRC08:38
openstackgerritYanis Guenane proposed openstack/puppet-nova: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987608:45
openstackgerritYanis Guenane proposed openstack/puppet-cinder: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20986908:49
*** rochaporto has joined #puppet-openstack08:54
openstackgerritYanis Guenane proposed openstack/puppet-designate: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987008:57
*** chem has joined #puppet-openstack08:57
openstackgerritYanis Guenane proposed openstack/puppet-gnocchi: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987109:00
openstackgerritYanis Guenane proposed openstack/puppet-ironic: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987209:03
*** saikrishna has joined #puppet-openstack09:04
*** social has quit IRC09:11
*** social has joined #puppet-openstack09:14
*** chem has quit IRC09:15
*** xingchao has quit IRC09:19
openstackgerritYanis Guenane proposed openstack/puppet-trove: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20988009:21
*** markvoelker has joined #puppet-openstack09:23
*** markvoelker has quit IRC09:28
openstackgerritYanis Guenane proposed openstack/puppet-tempest: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987909:41
openstackgerritYanis Guenane proposed openstack/puppet-tempest: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987909:42
*** jtomasek has joined #puppet-openstack09:55
openstackgerritYanis Guenane proposed openstack/puppet-swift: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987810:00
*** saikrishna has quit IRC10:00
*** paramite is now known as paramite|afk10:05
*** aimon has quit IRC10:06
*** aimon has joined #puppet-openstack10:06
*** paramite|afk is now known as paramite10:07
openstackgerritMichael Polenchuk proposed openstack/puppet-nova: Handle libvirt/cpu_model option  https://review.openstack.org/21454210:15
openstackgerritYanis Guenane proposed openstack/puppet-monasca: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987410:17
openstackgerritYanis Guenane proposed openstack/puppet-manila: Rely on autorequire for config resource ordering  https://review.openstack.org/21190210:26
openstackgerritYanis Guenane proposed openstack/puppet-manila: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987310:26
*** v1k0d3n has joined #puppet-openstack10:39
openstackgerritYanis Guenane proposed openstack/puppet-glance: Rely on autorequire for config resource ordering  https://review.openstack.org/21193710:42
openstackgerritYanis Guenane proposed openstack/puppet-glance: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20989410:42
*** v1k0d3n has quit IRC10:44
*** paramite is now known as paramite|afk10:44
openstackgerritYanis Guenane proposed openstack/puppet-neutron: Reflect provider change in puppet-openstacklib  https://review.openstack.org/20987510:48
openstackgerritYanis Guenane proposed openstack/puppet-neutron: Rely on autorequire for config resource ordering  https://review.openstack.org/21195810:48
*** saikrishna has joined #puppet-openstack11:11
*** paramite|afk is now known as paramite11:15
*** paramite is now known as paramite|afk11:16
openstackgerritMichael Polenchuk proposed openstack/puppet-nova: Handle libvirt/cpu_model option  https://review.openstack.org/21454211:17
*** stamak has joined #puppet-openstack11:19
*** jtomasek has quit IRC11:22
*** markvoelker has joined #puppet-openstack11:24
*** mjblack has quit IRC11:25
*** markvoelker has quit IRC11:28
*** cdelatte has joined #puppet-openstack11:31
*** saikrishna has quit IRC11:36
*** jtomasek has joined #puppet-openstack11:37
*** saikrishna has joined #puppet-openstack11:46
*** jayg|g0n3 is now known as jayg11:57
*** saikrishna has quit IRC11:58
*** morazi has joined #puppet-openstack12:00
*** dprince has joined #puppet-openstack12:08
*** ducttape_ has joined #puppet-openstack12:12
*** paramite|afk is now known as paramite12:25
*** jpena is now known as jpena|lunch12:30
*** logan2 has joined #puppet-openstack12:39
*** markvoelker has joined #puppet-openstack12:40
*** v1k0d3n has joined #puppet-openstack12:40
*** gildub has joined #puppet-openstack12:43
*** v1k0d3n has quit IRC12:45
openstackgerritMerged openstack/puppet-keystone: Adding wsgi log formatting  https://review.openstack.org/21209112:49
*** sergmelikyan has joined #puppet-openstack12:59
*** v1k0d3n has joined #puppet-openstack12:59
*** ducttape_ has quit IRC13:00
EmilienMgood morning13:01
iurygregorymorning13:01
*** paramite is now known as paramite|afk13:02
*** paramite|afk is now known as paramite13:03
*** tiswanso has joined #puppet-openstack13:15
gildubEmilienM, Could you (or any core member) please merge https://review.openstack.org/213598?13:19
EmilienMgildub: will look today13:19
gildubEmilienM, Thanks!13:19
EmilienMgildub: I already +213:19
EmilienMwhat can I do?13:19
gildubEmilienM, merge? Unless it has to be done by someone else...13:20
EmilienMgildub: it does not work like this13:21
*** pabelanger has joined #puppet-openstack13:26
*** prad_ has joined #puppet-openstack13:32
iurygregoryhey EmilienM , when i'm running keystone spec/acceptance/basic_keystone_spec.rb fails in  Port "5000"   should be listening (FAILED - 1)   Port "35357"   should be listening (FAILED - 2)13:33
iurygregorybut when i run spec/acceptance/keystone_wsgi_apache_spec.rb no error occurs13:33
gildubEmilienM, Once +2 the merge should be cleared, isn't? https://wiki.openstack.org/wiki/Puppet#How_code_gets_merged13:34
EmilienMgildub: I did the first +2, another core should +2 +A13:34
EmilienMthat's the rule13:34
EmilienMiurygregory: sorry, but I can't help you without debug13:34
EmilienMiurygregory: logs?13:34
* EmilienM brb13:34
gildubEmilienM, yeah I remember those discussion a some summit a while ago, but the doco is behind. Anyway, I'll ask for another +2 review.13:35
gildubiurygregory, what's the review?13:36
iurygregoryEmilienM, logs -> http://paste.openstack.org/show/421858/ and http://paste.openstack.org/show/421863/13:37
iurygregorygildub, i'm just trying to run acceptance test in my enviroment =)13:37
gildubiurygregory, yeah that's fine, that should run either in local or through CI13:38
iurygregoryyeah, but the basic says that the por is not listen =/13:39
iurygregorywhen i run udo netstat -tapen | grep ":5000" the output is tcp6       0      0 :::5000                 :::*                    LISTEN      0          73547       30523/apache213:39
*** jpena|lunch is now known as jpena13:40
gildubiurygregory, hard to tell unless you have a review that works (or fails) so we can try the same patch in local.13:41
gildubiurygregory, I would say that your keystone install has failed, something wrong either in your environment or the bootstrap part of the acceptance test => https://github.com/openstack/puppet-keystone/blob/master/spec/acceptance/basic_keystone_spec.rb#L813:43
EmilienMiurygregory: I was asking for keystone.log13:44
iurygregoryoh wait13:46
openstackgerritEmilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/21331513:50
openstackgerritEmilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/21331513:51
EmilienMiurygregory: it's running out of the box for me13:55
EmilienMiurygregory: I suggest you to read http://my1.fr/blog/puppet-module-functional-testing-with-vagrant-openstack-and-beaker/13:55
EmilienMno shame, I promote my blog here13:55
EmilienMlol13:55
*** prad_ is now known as pradk13:56
gildubmgagne, could you please review https://review.openstack.org/213598 and https://review.openstack.org/213603 ?13:59
gildubEmilienM, When you get a chance to check the the second one too ^. Thanks14:00
*** gildub has quit IRC14:02
iurygregorythanks EmilienM i'll read14:02
*** linkedinyou has quit IRC14:04
*** kbyrne has quit IRC14:07
*** timbyr_ has quit IRC14:07
*** kbyrne has joined #puppet-openstack14:11
*** aimon has quit IRC14:12
openstackgerritGilles Dubreuil proposed openstack/puppet-keystone: Purely cosmetic change on keystone provider  https://review.openstack.org/21359814:12
openstackgerritGilles Dubreuil proposed openstack/puppet-keystone: Authentication URLs and endpoint clarity re-factor  https://review.openstack.org/21360314:13
openstackgerritGilles Dubreuil proposed openstack/puppet-keystone: Endpoints are APIs version-less  https://review.openstack.org/21395714:13
*** dfisher has joined #puppet-openstack14:15
*** paramite is now known as paramite|afk14:17
*** ducttape_ has joined #puppet-openstack14:20
openstackgerritAndrey Yevsyukov proposed openstack/puppet-neutron: Add support for neutron-agent-mlnx deployment  https://review.openstack.org/20999714:22
*** ducttape_ has quit IRC14:24
*** ducttape_ has joined #puppet-openstack14:25
*** ducttape_ has quit IRC14:25
openstackgerritJavier Peña proposed openstack/puppet-swift: Add support for swift-object-expirer service  https://review.openstack.org/21154914:27
openstackgerritEmilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/21331514:30
pabelangerEmilienM: is there anything holding back the open manual msync reviews from actually landing for the puppet modules?14:32
EmilienMpabelanger: I guess not, people need to review14:32
EmilienMpabelanger: it was on my TODO for today14:32
pabelangerhttps://review.openstack.org/#/q/+topic:msync_rspec_version,n,z14:33
pabelangerya, if we can land them, it will help us move to automation sooner14:33
EmilienMpabelanger: looking now14:35
*** ducttape_ has joined #puppet-openstack14:44
*** aimon_ has joined #puppet-openstack14:52
*** fedexo has joined #puppet-openstack14:53
*** paramite|afk is now known as paramite14:54
*** xingchao has joined #puppet-openstack14:55
EmilienMpabelanger: done14:55
*** linkedinyou has joined #puppet-openstack14:58
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/20707814:59
*** logan2 has quit IRC15:01
*** paramite has quit IRC15:02
*** paramite has joined #puppet-openstack15:04
*** logan2 has joined #puppet-openstack15:05
pabelangerEmilienM: did you see my comments on ^ ?15:13
EmilienMpabelanger: not yet15:13
EmilienMreading now15:13
EmilienMpabelanger: tempest is configured like another service (mysql or keystone) - I don't see why it should be extracted *now*15:14
EmilienMwhen we will have another scenario, I totally agree though15:14
EmilienMI can add a comment in the manifest to explain that maybe15:15
pabelangerEmilienM: I man point is, tempest is a testing tool. Not production. So, I my mind, we should setup the production environment first, then setup testing.  Honestly, you'd never run puppet-nova and puppet-tempest in a production cloud, we should do the same for our integration test15:16
pabelangerwe did just that we the previous patchsets, this new version seems to revert that15:16
EmilienMpabelanger: this is testing here not production, I don't see the technical different between installing tempest in the same time15:16
EmilienMpuppet-tempest is just cloning a repo and feeding a tempest.conf15:17
EmilienMthere is nothing else here15:17
EmilienMit's a loss of time if we run puppet a 3rd time and a 4th time to check idempotent15:17
pabelangerya, that is wrong to me.  So much so, tempest to me should be an external node15:17
EmilienMpabelanger: sure! that's the plan15:18
EmilienMone day, when we have the basic bits in place15:18
pabelangerwe want to setup the OS to run openstack projects, nova, keystone etc.  tempest is a testing tool that should not be installed along side those projects.  Afterwards is fine, but not the same time15:18
EmilienMand feedback incoming from these basics bits15:18
* EmilienM daily scrum now15:18
pabelangerright, but I don't see why you reverted the change. It was setup and working with tempest.pp15:18
EmilienMpabelanger: like I said, running puppet *after* installing keystone is useless, since you need to run puppet 2 times more15:20
EmilienMand we're just feeding a tempest.conf15:20
pabelangerno, it is not useless. We are installing production environement in 1 step, then creating testing tools to run against the production environment15:21
pabelangerby installing puppet-tempest, you are infact changing the environment, from a puppet POV, to resolve dependency orders and such.15:22
pabelangerI don't see why you'd be apposed to moving tempest out of the scenario15:22
pabelangeropposed*15:22
*** xingchao has quit IRC15:23
pabelangermy ideal way of seeing it work.  We actually create run_puppet.sh, jenkins launches this to provision a cloud, using scenarios that have been created.  Once jenkins successfully runs that, we then invoke our testing tools to validate the cloud was created. Something like run_tempest.sh or run_test.sh to actually do that testing.  This process then setups any testing tools that are needed to run15:26
pabelangeragainst puppet15:26
pabelangerWe are only using puppet-tempest because it has been packaged, I could also see a job or test, to use tempest from git or a local version of tempest.  Externalizing it now to our cloud setup just make sense more sense to me right out of the box15:28
EmilienMpabelanger: I'm back!15:35
* EmilienM reading15:35
*** xingchao has joined #puppet-openstack15:36
*** xingchao has quit IRC15:36
*** xingchao has joined #puppet-openstack15:37
EmilienMpabelanger: the 2 reasons I like having tempest class in the scenario is: 1/ it allows to run only 2 puppet run in the job and 2/ the tempest configuration is related to your scenario itself. I don't think we will share the tempest code across scenarios, I'm even sure actually.15:38
*** xingchao has quit IRC15:41
*** sanjayu_ has joined #puppet-openstack15:43
pabelangerOur tempest configuration might change between scenarios, but we don't need to to run and install each time.  Our testing tools should be the last thing we install / configure before running them. I just can shake the feeling, that installing tempest at the same time we build the cloud is wrong. No operator would run tempest / puppet-tempest when installing puppet-keystone. Not sure why we would do15:44
pabelangerit15:44
*** paramite is now known as paramite|afk15:45
pabelangerIMO, this integration puppet module should be working more like a real world cloud with proper dependencies if possible15:45
*** paramite|afk is now known as paramite15:45
*** xarses_ has joined #puppet-openstack15:46
EmilienMpabelanger: the tempest config will change all the time. So that means we should keep - for now at least - the tempest puppet code in the scenario, it won't be installed all the time, since puppet run is idempotent, and it will be run at the end of run_tests.sh *now* but we can create a run_tempest.sh later if we want that15:47
EmilienMpabelanger: but we don't *run* tempest during the puppet run !15:47
EmilienMwe run tempest at the end !15:47
EmilienMhttps://review.openstack.org/#/c/207078/18/run_tests.sh,cm15:48
EmilienMby using tox15:48
*** sanjayu has quit IRC15:48
pabelangerIsn't the point of the puppet-openstack-integration module to see how the puppet-keystone, puppet-nova, services work together and help debug issues with them running in a cloud environment?15:49
EmilienMpabelanger: I guess you thought we were running tempest during puppet run15:49
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/20707015:50
EmilienMpabelanger: it does15:50
*** xarses has quit IRC15:50
pabelangertechnically no, because now you have the puppet-tempest module being a dependency now for that run.15:50
EmilienMpabelanger: tell me the difference15:50
EmilienMbetween configuring tempest.conf during keystone configuration & after15:51
pabelangermoving it to _after_ removes that from the dependency15:51
*** dprince has quit IRC15:51
EmilienMwhat is the benefit?15:51
EmilienM*now* I mean15:51
pabelangerthe difference to me is, puppet would never be installed on a cloud out side of our scenario15:51
pabelangerwe are actively tainting it by doing so15:51
EmilienMs/puppet/tempest/ ?15:51
pabelangeryes15:51
EmilienMwhy15:52
EmilienMour installers are installing tempest15:52
EmilienMRDO Director is installing Tempest15:52
EmilienMI wrote an installer at eNovance, we instaleld Tempest on the installation node15:52
EmilienMFuel is probably installing Rally which is doing testing15:52
pabelangerTempest - The OpenStack Integration Test Suite15:53
EmilienMI just don't see why you are complicating this, while, we only need something KISS now15:53
pabelangerIMO, test suites should not exists on production nodes15:53
pabelangerother wise, you don't have a production node, it is now a testing node15:53
EmilienMwe have one single node now15:53
EmilienMso let's keep it simple and run the manifest in a single .pp15:54
pabelangerBut, is moving puppet-tempest into a second run really complicating things?  It was working, and was just reverted a patch a go15:54
EmilienMbecause for *now* there is no plus value to have 2 .pp files15:54
EmilienMI'm sure we will split it later15:54
EmilienMbut for now, there is no value at all15:54
EmilienMpabelanger: it's not a second run15:54
*** paramite has quit IRC15:54
EmilienMit's a third and then a fourth15:55
EmilienMwe need to test if it's idempotent, keep in mind15:55
pabelangerI'm actually a little concerned we keep kicking issues like this down the road because we are disagreeing on them. Rather then hashing them out.15:55
pabelangerIf we are going to fix them down the road, lets just do it now and be done with it.  Why get a testing environment running, and potentially gating, only to refactor some time down the road15:56
EmilienMpabelanger: so you want to run puppet 4 times?15:56
openstackgerritJiri Stransky proposed openstack/puppet-neutron: Configure Big Switch ML2 plugin  https://review.openstack.org/21468615:56
EmilienMand maintain 2 .pp files15:56
pabelangerit doesn't matter how many times it runs.  It is going to run way more times in the gate15:56
pabelangerif we are concerned with puppet running multiple times, then drop puppet-tempest and manually configure it with bash15:57
EmilienMwe might want to keep jobs as short as possible also15:57
EmilienMwhen crinkle and I started this work, we agreed to keep it KISS and iterate15:58
EmilienMwe are not iterating here15:58
EmilienMyou want to hash out all future things15:58
EmilienMwhile we are not scaling now, we're just building the basic bits15:58
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/20707015:59
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/20707815:59
pabelangerRight, but I am planning to do mulit-node testing shortly.  In fact, I want to start with it. Since I have time and resources.  So, I am asking to get the code into master now, so I don't have to deal with it in my branch. If people think this is complicating the setup, I won't bringing it up again.15:59
EmilienMpabelanger: shortly? we even don't have a basic structure16:00
pabelangerthat we agree on, yes. That is why I am trying to get that defined.16:00
pabelangerbut, I keep hearing of down the road. :(16:00
EmilienMpabelanger: if we could have merged the basic structure and make progress on this, you could already work on multi node16:00
pabelangerEither way, I have code locally that does multi node stuff, I'll branch it from master and just work in parallel for now.16:01
EmilienMpabelanger: I know you have time and resource. But we are doing that together, we are working on CI things for quite a while now16:01
*** fedexo has quit IRC16:02
pabelangerEmilienM: Right, but sadly it has taken more then 6 weeks to get to here.  Which, to be honest, isn't very much.  Lets just do this, I'll let you and crinkle get this patchset merged, and I am going to start on multi-node support for scenerio002.16:04
EmilienMpabelanger: work in // is not effective16:04
EmilienMpabelanger: you should rather work on infra side to see our eventual blockers to run multi node16:04
EmilienMis that so easy to run multi node?16:04
EmilienMI have no idea16:04
EmilienMscenario002 is really cool, you can focus on that, I'm fine with that, but don't keep your code local16:05
*** stamak has quit IRC16:05
EmilienMshare it often so you have early feedback from puppet group16:05
pabelangerits not that multi-node is easy, I just understand how it would work. I have a local nodepool instance that I can also test against.16:06
pabelangergetting an experimental job going it not much work either16:06
EmilienMpabelanger: honestly (and I'm probably wrong), I don't see a lot of value of multi node jobs for Puppet CI16:07
EmilienMexcept for nova maybe16:07
EmilienMbut devstack is running on a single host AFIK16:07
EmilienMand devstack != puppet -> they gate openstack code while we are gating manifests that deploy that code16:08
pabelangerwell, some of this code I hope to also do in -infra16:08
EmilienMwhich code?16:09
pabelangerAnd, if we can allow mid-stream / downstream and easy tool to build production clouds in upstream, the better coverage we get16:09
EmilienMyou're not telling me why we need multi host, what is the use case?16:09
pabelangerHA setup for example16:10
mwhahahamultinode would be useful to test some of the auth/endpoint interactions across machines16:10
pabelangerDVR for neutron16:10
mwhahahait would catch cases where assumptions are being made about configs being available, etc16:10
pabelangerkeystone federation maybe/16:10
EmilienMpabelanger: our manifest do not deploy HA, except some buildin OpenStack features (DVR, etc)16:11
pabelangerEmilienM: right, but if we had an environment to test against, it would help drive development, no?16:12
EmilienMpabelanger: wait - what are we gating here - puppet modules or usecases/installers ? because deploying with HA is a long way (people will want HAproxy some not... some other Pacemaker, some not... some other Keepalived, some not.. etc)16:13
EmilienMour modules don't take care of HA setups, it's up to composition layers to handle that (with puppetlabs-haproxy, pacemaker, etc)16:13
EmilienMie: tripleo16:13
EmilienMthey have their CI jobs16:13
EmilienMdprince did that16:13
EmilienMthey even test HA16:14
pabelangerI don't know what we are gating on to be honest, I want to give people the environments in the gate to do stuff.16:14
EmilienMthere is gate-tripleo-ironic-overcloud-f21puppet-nonha and gate-tripleo-ironic-overcloud-f21puppet-ha16:14
EmilienMI'll focus on having scenario001 covering a single node use case (devstack like) with a maximum of projects installed16:15
EmilienMthen, I'll focus on a grenade job like (the current upgrade jobs, but implemented in puppet-openstack-integration repo)16:15
EmilienMbut testing HA is IMHO not up to our Puppet modules16:16
EmilienMexcept (again) for OpenStack builtin HA features16:16
EmilienMlike DVR, etc16:16
EmilienMand mwhahaha's examples16:16
*** rochaporto has quit IRC16:17
*** dprince has joined #puppet-openstack16:19
EmilienMdprince: why aren't we gating tripleo HA jobs in puppet modules?16:20
dprinceEmilienM: just haven't got there yet I suppose16:21
EmilienMdprince: wdyt?16:21
dprinceEmilienM: the main difference is pacemaker I guess for now which isn't part of OPM really16:21
EmilienMdprince: pabelanger wants to have scenarios like this16:21
EmilienMdprince: see backlog: http://eavesdrop.openstack.org/irclogs/%23puppet-openstack/16:22
dprinceEmilienM: we can do it if there is interest16:22
pabelangerI want to give people the ability to have them, if somebody see value in them.16:22
pabelangerI don't doubt our puppet module work well on a single node.16:23
pabelangersince a lot of people use them for a single node16:23
dprincepabelanger: sure16:23
pabelangerI would want to make sure our puppet modules work well under multi-node16:23
dprincepabelanger: the existing puppet job is multi node, just to be clear you want a multi-controller job right?16:23
EmilienMpabelanger: why not? they work in a single node I think16:23
EmilienMoh sorry, don't doubt - I should learn english one day.16:24
pabelangerso, that is either HA or not. But basically running nova over more then 1 node16:24
dprincepabelanger: the existing tripleo job is multi node, a single controller, multiple computes16:24
EmilienMpabelanger: tripleo is already perfectly doing that16:24
dprincepabelanger: we could optionally throw ceph into the mix as well (which we also support deploying alongside of things)16:25
EmilienMspredzy: manila packaging is fixed, I do the rechecks16:25
pabelangerSo, them maybe I am working in the wrong arena.16:25
*** aimon_ has quit IRC16:25
EmilienMpabelanger: no, you're good here16:25
EmilienMpabelanger: we might need a multi node scenario for ceph16:25
EmilienMpabelanger: you should talk with ceph folks ( xarses_ , dgurtner ... ) and investigate a job deploying openstack + ceph and testing backends (glance, cinder, nova)16:26
EmilienMso we can actually test our manifest deploy openstack+ceph stacks and it works16:26
pabelangereither way, yet another reason I want a spec :) And hopefully mid-cycle will help clear this up.16:26
EmilienMthat's a good use case a lot of people is using today16:26
dprinceEmilienM: we have a tripleo ceph job for that already, doing those things FWIW16:26
* xarses_ wakes up16:26
*** xarses_ is now known as xarses16:26
pabelangerThe honest answer is, a lot of mid stream and down stream stuff is happening for testing puppet modules in general. I just want to move some of it, what ever that includes, upstream.  And allows people to get their tests working in gate (voting or not) to make our puppet modules better16:27
EmilienMdprince++16:27
EmilienMpabelanger: like gating our installers?16:28
EmilienMfuel+rdo are consuming our modules16:28
pabelangerAnd eventually, what ever it looks like, I want to pull this concept into -infra to test our puppet modules. In a multi-node setup16:28
pabelangerEmilienM: no, not gating installers.16:29
pabelangerfor example, deploy 10 node cloud with puppet module. What ever current functionality works.... run tempest, does it pass16:30
pabelangerIf there is no HA, fine16:30
*** jistr has quit IRC16:30
EmilienMpabelanger: you still need manifests (composition layer)16:30
pabelangerwe'll, we'd need something16:31
dprincepabelanger: 79075516:31
dprincepabelanger: ha! there is a token code for you BTW :)16:31
pabelangerwith zuulv3 changes coming, it will be ansible. So, ansible would run puppet-openstack-integration on the ndoe16:31
*** ukitanuki has joined #puppet-openstack16:31
pabelangerdprince: nice, I was looking in gerrit for a review16:32
dprincepabelanger: what I was going to say was... there are likely many ways to do this sort of thing with the installers out there. w/ tripleo the goal is to ues OpenStack to do it (i.e. Heat templates). We've got a nice composition layer to do it that gives you several roles.16:33
pabelangerEmilienM: So, how is this for a use case. Move mysql to external node, make sure puppet modules work as expected16:33
*** jpena is now known as jpena|away16:34
dprincepabelanger: 32149116:34
* dprince sighs16:34
pabelangerdprince: right, tripleo could be a place to do some of this too. Which, might be the place to do it.  I was just looking to see if we could do it directly in the puppet-openstack team16:35
pabelangerLike I said, my ultimate goal is to take some of this multi-node setup back into -infra for our puppet modules. If puppet-openstack does think multi-node is much important, that works for me.  It just means, puppet-openstack and openstack-infra won't have a common place for testing code.  puppet-openstack, is upstream for -infra for puppet specific tooling in my eyes16:37
*** xingchao has joined #puppet-openstack16:38
*** pabelanger has quit IRC16:39
nibalizerpabelanger: i mean sure? but really the tooling has been built by the infra parts of puppet-openstack16:39
nibalizeryou can innovate in -infra if you want16:39
nibalizereveryone wears lots of hats16:39
*** zacdev has joined #puppet-openstack16:40
dgurtnerxarses: while you're waking up, can I get a review :) https://review.openstack.org/#/c/214135/ - without this the gatejobs for the module break half of the time16:41
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Revert "Revert "Initial run_tests.sh script""  https://review.openstack.org/21041216:42
nibalizerprobably in a happy end-state the beaker node, the tempest node, and the other nodes should all be separate vms16:42
nibalizerand nodepool multinode makes that doable16:42
nibalizerI got a repo openstack-infra/beaker-nodepool so that we can write a little ruby to neatly handle nodepool multinode (and maybe the nodepool rest api if it ever goes)16:43
nibalizerbut I haven't had time to code that yet16:43
*** pabelanger has joined #puppet-openstack16:43
pabelangerfinally, znc is back16:43
nibalizeras it is, devstack runs tempest on the same node16:43
*** xingchao has quit IRC16:43
nibalizerso I agree with separting it for purity but hard to say that is the most important thing to solve now16:43
*** c0m0 has quit IRC16:44
xarsesdgurtner: is this because the apache version changed?16:44
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/20129816:44
xarsesdgurtner: or has it been a problem for a while, and we just haven't noticed?16:44
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/20707016:44
EmilienMpabelanger: HA is a good use case and we might need to want it. You just need to be sure what is already tested by current CI, and the use cases we want to cover16:45
dgurtnerxarses: tbh I'm not sure - I just looked at the logs and noticed that instead of creating the logs it's trying to put them in a file called "true" and thus fixed it ;)16:45
EmilienMpabelanger: of course, if tooling is consistent between infra & puppet groups, that's awesome16:45
*** jtomasek has quit IRC16:46
xarsesdgurtner: sounds good, looks good. I approved it.16:46
dgurtnerxarses: cool, thanks :)16:48
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/21041216:50
*** derekh has quit IRC16:51
*** pabelanger has quit IRC16:53
*** sergmelikyan has quit IRC16:57
*** sergmelikyan has joined #puppet-openstack16:59
*** xarses has quit IRC16:59
*** aimon has joined #puppet-openstack17:00
*** sergmelikyan has quit IRC17:03
openstackgerritMerged stackforge/puppet-ceph: Fix RGW Apache syslog creation  https://review.openstack.org/21413517:04
*** pabelanger has joined #puppet-openstack17:04
*** sanjayu has joined #puppet-openstack17:05
*** sanjayu_ has quit IRC17:08
*** angdraug has joined #puppet-openstack17:17
*** dgurtner has quit IRC17:19
*** saneax has joined #puppet-openstack17:19
*** xarses has joined #puppet-openstack17:20
pabelangerMy last plea, can we please hold off on any other checks to puppet-openstack-integration until mid-cycle17:25
pabelangerif that is too far away, I suggest we get in a room / conference soon17:25
EmilienMpabelanger: other checks == extending scenarios001 after it got merged?17:26
pabelangerI feel, all of the existing work I have done over the last 6 weeks is just getting reverted to speed things up, with is just frustrating the heck out of me17:26
pabelangers/check/changes17:26
EmilienMpabelanger: we will probably merge this first iteration17:27
pabelangerwe are not reverting code in https://review.openstack.org/#/c/210412/ which has been running for the last 6 weeks17:27
pabelangervery frustrating17:27
pabelangerand now proposing gate changes17:27
EmilienMpabelanger: I don't see how being in the same room will help us to agree17:28
EmilienMwe can setup videoconference if you want/need17:28
*** tiswanso has quit IRC17:28
EmilienMI don't see how an iteration is frustrating17:28
*** tiswanso has joined #puppet-openstack17:28
pabelangerremoving functionality from a patchset, which was merged to be reverted is.17:29
EmilienMpabelanger: yeah your patch broke our CI17:30
EmilienMbecause I did not carefully review it17:30
EmilienMnow I'm reverting the revert but without breaking our CI17:30
EmilienMbeaker runs puppet as root17:30
EmilienMso we need to adjust that17:30
EmilienMI don't understand frustration here - we just wanna make it work on both jobs17:31
*** austin81 has joined #puppet-openstack17:39
*** timrc has joined #puppet-openstack17:39
*** jesusaurus has joined #puppet-openstack17:41
*** ericpeterson has joined #puppet-openstack17:55
*** ducttape_ has quit IRC17:57
*** ericpeterson has quit IRC18:09
*** danieru has quit IRC18:26
*** pabelanger has quit IRC18:34
*** xingchao has joined #puppet-openstack18:41
*** paramite has joined #puppet-openstack18:44
*** paramite has quit IRC18:46
*** mjblack has joined #puppet-openstack18:47
*** xingchao has quit IRC18:50
openstackgerritMerged openstack/puppet-modulesync-configs: Create sync-projects.sh script  https://review.openstack.org/21052818:51
*** ducttape_ has joined #puppet-openstack19:02
*** jpena|away has quit IRC19:07
*** danieru has joined #puppet-openstack19:12
*** zacdev has quit IRC19:28
*** gfidente has quit IRC19:34
iurygregorythere is a reason for the acceptance basic use is_expected.to be_listening.with('tcp') and the acceptance wsgi use it { is_expected.to be_listening } ?19:53
EmilienMiurygregory: yes19:53
EmilienMiurygregory: when binding API with API, it seems serverspec can't find out 5000 is binded on tcp or udp19:53
EmilienMoops19:53
EmilienMAPI with WSGI*19:53
iurygregorythanks EmilienM19:54
*** angdraug has quit IRC19:56
*** saneax has quit IRC19:57
*** jpena has joined #puppet-openstack20:00
*** chem has joined #puppet-openstack20:02
*** stamak has joined #puppet-openstack20:03
*** stamak has quit IRC20:38
*** zacdev has joined #puppet-openstack20:43
*** leanderthal has quit IRC20:46
*** xingchao has joined #puppet-openstack20:48
*** xingchao has quit IRC20:52
openstackgerritEmilien Macchi proposed openstack/puppet-keystone: CI - do not merge - testing https://review.openstack.org/#/c/210412/  https://review.openstack.org/21479321:01
openstackgerritRamkumar Gowrishankar proposed openstack/puppet-neutron: This changelist introduces support for Nuage Neutron plugin configration and Nuage VRS configuration. The associated spec tests and custom types and providers have also been added. This follows the same pattern as other plugins such as midonet and opencon  https://review.openstack.org/21479821:12
EmilienMrgowrishankar: you might need to split your commit message ^21:13
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/21041221:13
*** austin81 has left #puppet-openstack21:15
*** bogdando has quit IRC21:15
*** bogdando has joined #puppet-openstack21:18
*** jpena has quit IRC21:23
rgowrishankaremilienM: Do you want me to cancel this one and create a new one? The message shows up correctly on the review webpage.21:23
EmilienMrgowrishankar: please use git amend21:23
rgowrishankarok, will do.21:23
rgowrishankari was not sure if I use git amend without any changes in files whether the review tool would get confused21:24
EmilienMrgowrishankar: and eventually look https://wiki.openstack.org/wiki/GitCommitMessages21:24
*** tiswanso has quit IRC21:25
openstackgerritAdam Vinsh proposed openstack/puppet-swift: WIP: Introduce swift_service class  https://review.openstack.org/20322021:30
openstackgerritRamkumar Gowrishankar proposed openstack/puppet-neutron: Support for Nuage Neutron plugin configration and Nuage VRS configuration in puppet-neutron.  https://review.openstack.org/21479821:39
rgowrishankarEmilienM: Sent out the review again with *hopefully* better commit message.21:41
EmilienMrgowrishankar: cool!21:41
EmilienMrgowrishankar: well, your commit is still not correct I'm sorry21:42
EmilienMyou should not go up to > 80 characters per line21:42
*** xingchao has joined #puppet-openstack21:48
openstackgerritRamkumar Gowrishankar proposed openstack/puppet-neutron: Support for Nuage Neutron plugin and Nuage VRS in puppet-neutron  https://review.openstack.org/21479821:49
rgowrishankarEmilien: third times the charm?21:49
EmilienMrgowrishankar: don't worry, you'll have more patchsets, I had a quick review and I have a lot of comments21:50
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/21041221:50
*** aimon has quit IRC21:51
rgowrishankarEmilienM: ok, at least I got the commit message correct :) Logging off now.. I will look out for the comments on the review tomorrow and hop on to the IRC channel..21:52
EmilienMrgowrishankar: cool21:52
*** xingchao has quit IRC21:53
*** jayg is now known as jayg|g0n321:56
*** morazi has quit IRC21:58
*** dprince has quit IRC21:59
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/21041222:14
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/20129822:15
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/20129822:19
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/20707022:20
*** gildub has joined #puppet-openstack22:23
*** pradk has quit IRC22:23
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/20707822:23
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/21041222:42
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/20129822:44
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/20707022:45
*** saneax has joined #puppet-openstack22:45
openstackgerritDavid Gurtner proposed stackforge/puppet-ceph: Drop no longer supported releases  https://review.openstack.org/21410422:45
openstackgerritEmilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/20707822:45
openstackgerritDavid Gurtner proposed stackforge/puppet-ceph: use full length APT key  https://review.openstack.org/20998122:45
openstackgerritDavid Gurtner proposed stackforge/puppet-ceph: Be more specific with CentOS7 package exclude  https://review.openstack.org/21409322:46
openstackgerritMerged openstack/puppet-openstack-specs: Enabling-federation  https://review.openstack.org/19036122:48
*** xingchao has joined #puppet-openstack22:49
*** dgurtner has joined #puppet-openstack22:50
*** saneax has quit IRC22:52
*** saneax has joined #puppet-openstack23:00
*** xingchao has quit IRC23:08
*** ducttape_ has quit IRC23:11
*** aimon has joined #puppet-openstack23:16
*** fedexo has joined #puppet-openstack23:37
*** dgurtner has quit IRC23:45
*** tiswanso has joined #puppet-openstack23:53
openstackgerritPaul Belanger proposed openstack/puppet-openstack-integration: [WIP] And example commit to keep beaker-jobs and integration happy  https://review.openstack.org/21489723:57
*** tiswanso has quit IRC23:58

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