Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2015-08-19

| Channels | #puppet-openstack index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:14 tiswanso joined #puppet-openstack
00:22 sergmelikyan joined #puppet-openstack
00:31 xingchao joined #puppet-openstack
00:40 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Add notification system options in trove  https://review.openstack.org/200818
00:42 sergmelikyan joined #puppet-openstack
00:43 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Fix guestagent_config_file option default value  https://review.openstack.org/208431
00:47 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Fix default value of guestagent_config_file option  https://review.openstack.org/208431
00:49 ducttape_ joined #puppet-openstack
00:52 sergmelikyan joined #puppet-openstack
00:52 tiswanso joined #puppet-openstack
00:53 serg_melikyan joined #puppet-openstack
00:53 gildub joined #puppet-openstack
00:54 tiswanso joined #puppet-openstack
01:02 mfisch EmilienM: can you or yanis take a peek at https://review.openstack.org/#/c/212091 again
01:12 linkedinyou joined #puppet-openstack
01:17 sergmelikyan joined #puppet-openstack
01:19 xarses joined #puppet-openstack
01:23 gildub joined #puppet-openstack
01:23 sergmelikyan joined #puppet-openstack
01:47 ilbot3 joined #puppet-openstack
01:47 Topic for #puppet-openstack is now Puppet/OpenStack: Weekly meeting (every Tuesday 15:00 UTC): https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack - Logs http://eavesdrop.openstack.org/irclogs/%23puppet-openstack/ - On going efforts: https://trello.com/puppetopenstack
01:53 xingchao joined #puppet-openstack
01:56 xingchao_ joined #puppet-openstack
01:57 xingcha__ joined #puppet-openstack
01:58 EmilienM mfisch: will do
02:06 sergmelikyan joined #puppet-openstack
02:14 xingchao joined #puppet-openstack
02:41 ducttape_ joined #puppet-openstack
02:45 nigelk joined #puppet-openstack
02:47 gildub joined #puppet-openstack
02:55 ducttape_ joined #puppet-openstack
03:02 imcsk8_ joined #puppet-openstack
04:01 gildub nibalizer, 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 zuul
04:01 gildub nibalizer, https://review.openstack.org/#/c/213598/
04:03 gildub nibalizer, 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 investigation
05:24 LimorStotland joined #puppet-openstack
05:53 xingchao joined #puppet-openstack
05:56 xingchao_ joined #puppet-openstack
05:57 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Add rabbit_ha_queues option  https://review.openstack.org/214458
06:08 openstackgerrit Xingchao Yu proposed openstack/puppet-designate: Add enabled_notification_handlers option  https://review.openstack.org/214465
06:12 sergmelikyan joined #puppet-openstack
06:13 openstackgerrit Xingchao Yu proposed openstack/puppet-designate: Add enabled_notification_handlers option  https://review.openstack.org/214465
06:16 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Add rabbit_ha_queues option  https://review.openstack.org/214458
06:18 paramite joined #puppet-openstack
06:36 openstackgerrit Michael Polenchuk proposed openstack/puppet-nova: Activate fping api extension  https://review.openstack.org/214132
06:58 openstackgerrit Xingchao Yu proposed openstack/puppet-trove: Introduce amqp_durable_queues option  https://review.openstack.org/214477
07:00 aimon joined #puppet-openstack
07:10 ddmitriev1 joined #puppet-openstack
07:12 xingchao joined #puppet-openstack
07:16 jpena joined #puppet-openstack
07:21 social joined #puppet-openstack
07:33 c0m0 joined #puppet-openstack
07:35 gfidente joined #puppet-openstack
07:53 openstackgerrit Sergey Kolekonov proposed openstack/puppet-neutron: Allow deployment when DVR is enabled and L2 pop and tunneling are disabled  https://review.openstack.org/214498
08:01 openstackgerrit Yanis Guenane proposed openstack/puppet-tuskar: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209883
08:05 openstackgerrit Yanis Guenane proposed openstack/puppet-sahara: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209877
08:09 dgurtner joined #puppet-openstack
08:19 saikrishna joined #puppet-openstack
08:21 timbyr_ joined #puppet-openstack
08:24 openstackgerrit Yanis Guenane proposed openstack/puppet-monasca: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209874
08:27 derekh joined #puppet-openstack
08:28 openstackgerrit Yanis Guenane proposed openstack/puppet-ceilometer: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209868
08:30 openstackgerrit Yanis Guenane proposed openstack/puppet-heat: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209882
08:34 jistr joined #puppet-openstack
08:37 openstackgerrit Yanis Guenane proposed openstack/puppet-heat: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209882
08:37 openstackgerrit Yanis Guenane proposed openstack/puppet-ceilometer: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209868
08:38 openstackgerrit Yanis Guenane proposed openstack/puppet-sahara: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209877
08:45 openstackgerrit Yanis Guenane proposed openstack/puppet-nova: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209876
08:49 openstackgerrit Yanis Guenane proposed openstack/puppet-cinder: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209869
08:54 rochaporto joined #puppet-openstack
08:56 openstackgerrit Yanis Guenane proposed openstack/puppet-designate: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209870
08:57 chem joined #puppet-openstack
09:00 openstackgerrit Yanis Guenane proposed openstack/puppet-gnocchi: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209871
09:03 openstackgerrit Yanis Guenane proposed openstack/puppet-ironic: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209872
09:04 saikrishna joined #puppet-openstack
09:14 social joined #puppet-openstack
09:21 openstackgerrit Yanis Guenane proposed openstack/puppet-trove: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209880
09:23 markvoelker joined #puppet-openstack
09:41 openstackgerrit Yanis Guenane proposed openstack/puppet-tempest: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209879
09:42 openstackgerrit Yanis Guenane proposed openstack/puppet-tempest: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209879
09:55 jtomasek joined #puppet-openstack
10:00 openstackgerrit Yanis Guenane proposed openstack/puppet-swift: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209878
10:06 aimon joined #puppet-openstack
10:15 openstackgerrit Michael Polenchuk proposed openstack/puppet-nova: Handle libvirt/cpu_model option  https://review.openstack.org/214542
10:17 openstackgerrit Yanis Guenane proposed openstack/puppet-monasca: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209874
10:26 openstackgerrit Yanis Guenane proposed openstack/puppet-manila: Rely on autorequire for config resource ordering  https://review.openstack.org/211902
10:26 openstackgerrit Yanis Guenane proposed openstack/puppet-manila: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209873
10:39 v1k0d3n joined #puppet-openstack
10:42 openstackgerrit Yanis Guenane proposed openstack/puppet-glance: Rely on autorequire for config resource ordering  https://review.openstack.org/211937
10:42 openstackgerrit Yanis Guenane proposed openstack/puppet-glance: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209894
10:48 openstackgerrit Yanis Guenane proposed openstack/puppet-neutron: Reflect provider change in puppet-openstacklib  https://review.openstack.org/209875
10:48 openstackgerrit Yanis Guenane proposed openstack/puppet-neutron: Rely on autorequire for config resource ordering  https://review.openstack.org/211958
11:11 saikrishna joined #puppet-openstack
11:17 openstackgerrit Michael Polenchuk proposed openstack/puppet-nova: Handle libvirt/cpu_model option  https://review.openstack.org/214542
11:19 stamak joined #puppet-openstack
11:24 markvoelker joined #puppet-openstack
11:31 cdelatte joined #puppet-openstack
11:37 jtomasek joined #puppet-openstack
11:46 saikrishna joined #puppet-openstack
11:59 morazi joined #puppet-openstack
12:08 dprince joined #puppet-openstack
12:12 ducttape_ joined #puppet-openstack
12:39 logan2 joined #puppet-openstack
12:40 markvoelker joined #puppet-openstack
12:40 v1k0d3n joined #puppet-openstack
12:43 gildub joined #puppet-openstack
12:49 openstackgerrit Merged openstack/puppet-keystone: Adding wsgi log formatting  https://review.openstack.org/212091
12:59 sergmelikyan joined #puppet-openstack
12:59 v1k0d3n joined #puppet-openstack
13:01 EmilienM good morning
13:01 iurygregory morning
13:15 tiswanso joined #puppet-openstack
13:19 gildub EmilienM, Could you (or any core member) please merge https://review.openstack.org/213598?
13:19 EmilienM gildub: will look today
13:19 gildub EmilienM, Thanks!
13:19 EmilienM gildub: I already +2
13:19 EmilienM what can I do?
13:20 gildub EmilienM, merge? Unless it has to be done by someone else...
13:21 EmilienM gildub: it does not work like this
13:26 pabelanger joined #puppet-openstack
13:32 prad_ joined #puppet-openstack
13:33 iurygregory hey 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 iurygregory but when i run spec/acceptance/keystone_wsgi_apache_spec.rb no error occurs
13:34 gildub EmilienM, Once +2 the merge should be cleared, isn't? https://wiki.openstack.org/wiki/Puppet#How_code_gets_merged
13:34 EmilienM gildub: I did the first +2, another core should +2 +A
13:34 EmilienM that's the rule
13:34 EmilienM iurygregory: sorry, but I can't help you without debug
13:34 EmilienM iurygregory: logs?
13:34 * EmilienM brb
13:35 gildub EmilienM, 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:36 gildub iurygregory, what's the review?
13:37 iurygregory EmilienM, logs -> http://paste.openstack.org/show/421858/ and http://paste.openstack.org/show/421863/
13:37 iurygregory gildub, i'm just trying to run acceptance test in my enviroment =)
13:38 gildub iurygregory, yeah that's fine, that should run either in local or through CI
13:39 iurygregory yeah, but the basic says that the por is not listen =/
13:39 iurygregory when i run udo netstat -tapen | grep ":5000" the output is tcp6       0      0 :::5000                 :::*                    LISTEN      0          73547       30523/apache2
13:41 gildub iurygregory, hard to tell unless you have a review that works (or fails) so we can try the same patch in local.
13:42 gildub iurygregory, 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#L8
13:44 EmilienM iurygregory: I was asking for keystone.log
13:46 iurygregory oh wait
13:50 openstackgerrit Emilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/213315
13:51 openstackgerrit Emilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/213315
13:55 EmilienM iurygregory: it's running out of the box for me
13:55 EmilienM iurygregory: I suggest you to read http://my1.fr/blog/puppet-module-functional-testing-with-vagrant-openstack-and-beaker/
13:55 EmilienM no shame, I promote my blog here
13:55 EmilienM lol
13:59 gildub mgagne, could you please review https://review.openstack.org/213598 and https://review.openstack.org/213603 ?
14:00 gildub EmilienM, When you get a chance to check the the second one too ^. Thanks
14:02 iurygregory thanks EmilienM i'll read
14:11 kbyrne joined #puppet-openstack
14:12 openstackgerrit Gilles Dubreuil proposed openstack/puppet-keystone: Purely cosmetic change on keystone provider  https://review.openstack.org/213598
14:13 openstackgerrit Gilles Dubreuil proposed openstack/puppet-keystone: Authentication URLs and endpoint clarity re-factor  https://review.openstack.org/213603
14:13 openstackgerrit Gilles Dubreuil proposed openstack/puppet-keystone: Endpoints are APIs version-less  https://review.openstack.org/213957
14:15 dfisher joined #puppet-openstack
14:20 ducttape_ joined #puppet-openstack
14:22 openstackgerrit Andrey Yevsyukov proposed openstack/puppet-neutron: Add support for neutron-agent-mlnx deployment  https://review.openstack.org/209997
14:25 ducttape_ joined #puppet-openstack
14:27 openstackgerrit Javier Peña proposed openstack/puppet-swift: Add support for swift-object-expirer service  https://review.openstack.org/211549
14:30 openstackgerrit Emilien Macchi proposed openstack/puppet-nova: Implement WSGI support for Nova API  https://review.openstack.org/213315
14:32 pabelanger EmilienM: is there anything holding back the open manual msync reviews from actually landing for the puppet modules?
14:32 EmilienM pabelanger: I guess not, people need to review
14:32 EmilienM pabelanger: it was on my TODO for today
14:33 pabelanger https://review.openstack.org/#/q/+topic:msync_rspec_version,n,z
14:33 pabelanger ya, if we can land them, it will help us move to automation sooner
14:35 EmilienM pabelanger: looking now
14:44 ducttape_ joined #puppet-openstack
14:52 aimon_ joined #puppet-openstack
14:52 fedexo joined #puppet-openstack
14:55 xingchao joined #puppet-openstack
14:55 EmilienM pabelanger: done
14:58 linkedinyou joined #puppet-openstack
14:59 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/207078
15:04 paramite joined #puppet-openstack
15:05 logan2 joined #puppet-openstack
15:13 pabelanger EmilienM: did you see my comments on ^ ?
15:13 EmilienM pabelanger: not yet
15:13 EmilienM reading now
15:14 EmilienM pabelanger: tempest is configured like another service (mysql or keystone) - I don't see why it should be extracted *now*
15:14 EmilienM when we will have another scenario, I totally agree though
15:15 EmilienM I can add a comment in the manifest to explain that maybe
15:16 pabelanger EmilienM: 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 test
15:16 pabelanger we did just that we the previous patchsets, this new version seems to revert that
15:16 EmilienM pabelanger: this is testing here not production, I don't see the technical different between installing tempest in the same time
15:17 EmilienM puppet-tempest is just cloning a repo and feeding a tempest.conf
15:17 EmilienM there is nothing else here
15:17 EmilienM it's a loss of time if we run puppet a 3rd time and a 4th time to check idempotent
15:17 pabelanger ya, that is wrong to me.  So much so, tempest to me should be an external node
15:18 EmilienM pabelanger: sure! that's the plan
15:18 EmilienM one day, when we have the basic bits in place
15:18 pabelanger we 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 time
15:18 EmilienM and feedback incoming from these basics bits
15:18 * EmilienM daily scrum now
15:18 pabelanger right, but I don't see why you reverted the change. It was setup and working with tempest.pp
15:20 EmilienM pabelanger: like I said, running puppet *after* installing keystone is useless, since you need to run puppet 2 times more
15:20 EmilienM and we're just feeding a tempest.conf
15:21 pabelanger no, it is not useless. We are installing production environement in 1 step, then creating testing tools to run against the production environment
15:22 pabelanger by installing puppet-tempest, you are infact changing the environment, from a puppet POV, to resolve dependency orders and such.
15:22 pabelanger I don't see why you'd be apposed to moving tempest out of the scenario
15:22 pabelanger opposed*
15:26 pabelanger my 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 run
15:26 pabelanger against puppet
15:28 pabelanger We 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 box
15:35 EmilienM pabelanger: I'm back!
15:35 * EmilienM reading
15:36 xingchao joined #puppet-openstack
15:37 xingchao joined #puppet-openstack
15:38 EmilienM pabelanger: 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:43 sanjayu_ joined #puppet-openstack
15:44 pabelanger Our 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 do
15:44 pabelanger it
15:45 pabelanger IMO, this integration puppet module should be working more like a real world cloud with proper dependencies if possible
15:46 xarses_ joined #puppet-openstack
15:47 EmilienM pabelanger: 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 that
15:47 EmilienM pabelanger: but we don't *run* tempest during the puppet run !
15:47 EmilienM we run tempest at the end !
15:47 EmilienM https://review.openstack.org/#/c/207078/18/run_tests.sh,cm
15:48 EmilienM by using tox
15:49 pabelanger Isn'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 EmilienM pabelanger: I guess you thought we were running tempest during puppet run
15:50 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/207070
15:50 EmilienM pabelanger: it does
15:50 pabelanger technically no, because now you have the puppet-tempest module being a dependency now for that run.
15:50 EmilienM pabelanger: tell me the difference
15:51 EmilienM between configuring tempest.conf during keystone configuration & after
15:51 pabelanger moving it to _after_ removes that from the dependency
15:51 EmilienM what is the benefit?
15:51 EmilienM *now* I mean
15:51 pabelanger the difference to me is, puppet would never be installed on a cloud out side of our scenario
15:51 pabelanger we are actively tainting it by doing so
15:51 EmilienM s/puppet/tempest/ ?
15:51 pabelanger yes
15:52 EmilienM why
15:52 EmilienM our installers are installing tempest
15:52 EmilienM RDO Director is installing Tempest
15:52 EmilienM I wrote an installer at eNovance, we instaleld Tempest on the installation node
15:52 EmilienM Fuel is probably installing Rally which is doing testing
15:53 pabelanger Tempest - The OpenStack Integration Test Suite
15:53 EmilienM I just don't see why you are complicating this, while, we only need something KISS now
15:53 pabelanger IMO, test suites should not exists on production nodes
15:53 pabelanger other wise, you don't have a production node, it is now a testing node
15:53 EmilienM we have one single node now
15:54 EmilienM so let's keep it simple and run the manifest in a single .pp
15:54 pabelanger But, is moving puppet-tempest into a second run really complicating things?  It was working, and was just reverted a patch a go
15:54 EmilienM because for *now* there is no plus value to have 2 .pp files
15:54 EmilienM I'm sure we will split it later
15:54 EmilienM but for now, there is no value at all
15:54 EmilienM pabelanger: it's not a second run
15:55 EmilienM it's a third and then a fourth
15:55 EmilienM we need to test if it's idempotent, keep in mind
15:55 pabelanger I'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:56 pabelanger If 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 road
15:56 EmilienM pabelanger: so you want to run puppet 4 times?
15:56 openstackgerrit Jiri Stransky proposed openstack/puppet-neutron: Configure Big Switch ML2 plugin  https://review.openstack.org/214686
15:56 EmilienM and maintain 2 .pp files
15:56 pabelanger it doesn't matter how many times it runs.  It is going to run way more times in the gate
15:57 pabelanger if we are concerned with puppet running multiple times, then drop puppet-tempest and manually configure it with bash
15:57 EmilienM we might want to keep jobs as short as possible also
15:58 EmilienM when crinkle and I started this work, we agreed to keep it KISS and iterate
15:58 EmilienM we are not iterating here
15:58 EmilienM you want to hash out all future things
15:58 EmilienM while we are not scaling now, we're just building the basic bits
15:59 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/207070
15:59 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/207078
15:59 pabelanger Right, 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.
16:00 EmilienM pabelanger: shortly? we even don't have a basic structure
16:00 pabelanger that we agree on, yes. That is why I am trying to get that defined.
16:00 pabelanger but, I keep hearing of down the road. :(
16:00 EmilienM pabelanger: if we could have merged the basic structure and make progress on this, you could already work on multi node
16:01 pabelanger Either 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 EmilienM pabelanger: I know you have time and resource. But we are doing that together, we are working on CI things for quite a while now
16:04 pabelanger EmilienM: 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 EmilienM pabelanger: work in // is not effective
16:04 EmilienM pabelanger: you should rather work on infra side to see our eventual blockers to run multi node
16:04 EmilienM is that so easy to run multi node?
16:04 EmilienM I have no idea
16:05 EmilienM scenario002 is really cool, you can focus on that, I'm fine with that, but don't keep your code local
16:05 EmilienM share it often so you have early feedback from puppet group
16:06 pabelanger its 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 pabelanger getting an experimental job going it not much work either
16:07 EmilienM pabelanger: honestly (and I'm probably wrong), I don't see a lot of value of multi node jobs for Puppet CI
16:07 EmilienM except for nova maybe
16:07 EmilienM but devstack is running on a single host AFIK
16:08 EmilienM and devstack != puppet -> they gate openstack code while we are gating manifests that deploy that code
16:08 pabelanger well, some of this code I hope to also do in -infra
16:09 EmilienM which code?
16:09 pabelanger And, if we can allow mid-stream / downstream and easy tool to build production clouds in upstream, the better coverage we get
16:09 EmilienM you're not telling me why we need multi host, what is the use case?
16:10 pabelanger HA setup for example
16:10 mwhahaha multinode would be useful to test some of the auth/endpoint interactions across machines
16:10 pabelanger DVR for neutron
16:10 mwhahaha it would catch cases where assumptions are being made about configs being available, etc
16:10 pabelanger keystone federation maybe/
16:11 EmilienM pabelanger: our manifest do not deploy HA, except some buildin OpenStack features (DVR, etc)
16:12 pabelanger EmilienM: right, but if we had an environment to test against, it would help drive development, no?
16:13 EmilienM pabelanger: 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 EmilienM our modules don't take care of HA setups, it's up to composition layers to handle that (with puppetlabs-haproxy, pacemaker, etc)
16:13 EmilienM ie: tripleo
16:13 EmilienM they have their CI jobs
16:13 EmilienM dprince did that
16:14 EmilienM they even test HA
16:14 pabelanger I 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 EmilienM there is gate-tripleo-ironic-overcloud-f21puppet-nonha and gate-tripleo-ironic-overcloud-f21puppet-ha
16:15 EmilienM I'll focus on having scenario001 covering a single node use case (devstack like) with a maximum of projects installed
16:15 EmilienM then, I'll focus on a grenade job like (the current upgrade jobs, but implemented in puppet-openstack-integration repo)
16:16 EmilienM but testing HA is IMHO not up to our Puppet modules
16:16 EmilienM except (again) for OpenStack builtin HA features
16:16 EmilienM like DVR, etc
16:16 EmilienM and mwhahaha's examples
16:19 dprince joined #puppet-openstack
16:20 EmilienM dprince: why aren't we gating tripleo HA jobs in puppet modules?
16:21 dprince EmilienM: just haven't got there yet I suppose
16:21 EmilienM dprince: wdyt?
16:21 dprince EmilienM: the main difference is pacemaker I guess for now which isn't part of OPM really
16:21 EmilienM dprince: pabelanger wants to have scenarios like this
16:22 EmilienM dprince: see backlog: http://eavesdrop.openstack.org/irclogs/%23puppet-openstack/
16:22 dprince EmilienM: we can do it if there is interest
16:22 pabelanger I want to give people the ability to have them, if somebody see value in them.
16:23 pabelanger I don't doubt our puppet module work well on a single node.
16:23 pabelanger since a lot of people use them for a single node
16:23 dprince pabelanger: sure
16:23 pabelanger I would want to make sure our puppet modules work well under multi-node
16:23 dprince pabelanger: the existing puppet job is multi node, just to be clear you want a multi-controller job right?
16:23 EmilienM pabelanger: why not? they work in a single node I think
16:24 EmilienM oh sorry, don't doubt - I should learn english one day.
16:24 pabelanger so, that is either HA or not. But basically running nova over more then 1 node
16:24 dprince pabelanger: the existing tripleo job is multi node, a single controller, multiple computes
16:24 EmilienM pabelanger: tripleo is already perfectly doing that
16:25 dprince pabelanger: we could optionally throw ceph into the mix as well (which we also support deploying alongside of things)
16:25 EmilienM spredzy: manila packaging is fixed, I do the rechecks
16:25 pabelanger So, them maybe I am working in the wrong arena.
16:25 EmilienM pabelanger: no, you're good here
16:25 EmilienM pabelanger: we might need a multi node scenario for ceph
16:26 EmilienM pabelanger: you should talk with ceph folks ( xarses_ , dgurtner ... ) and investigate a job deploying openstack + ceph and testing backends (glance, cinder, nova)
16:26 EmilienM so we can actually test our manifest deploy openstack+ceph stacks and it works
16:26 pabelanger either way, yet another reason I want a spec :) And hopefully mid-cycle will help clear this up.
16:26 EmilienM that's a good use case a lot of people is using today
16:26 dprince EmilienM: we have a tripleo ceph job for that already, doing those things FWIW
16:26 * xarses_ wakes up
16:27 pabelanger The 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 better
16:27 EmilienM dprince++
16:28 EmilienM pabelanger: like gating our installers?
16:28 EmilienM fuel+rdo are consuming our modules
16:28 pabelanger And eventually, what ever it looks like, I want to pull this concept into -infra to test our puppet modules. In a multi-node setup
16:29 pabelanger EmilienM: no, not gating installers.
16:30 pabelanger for example, deploy 10 node cloud with puppet module. What ever current functionality works.... run tempest, does it pass
16:30 pabelanger If there is no HA, fine
16:30 EmilienM pabelanger: you still need manifests (composition layer)
16:31 pabelanger we'll, we'd need something
16:31 dprince pabelanger: 790755
16:31 dprince pabelanger: ha! there is a token code for you BTW :)
16:31 pabelanger with zuulv3 changes coming, it will be ansible. So, ansible would run puppet-openstack-integration on the ndoe
16:31 ukitanuki joined #puppet-openstack
16:32 pabelanger dprince: nice, I was looking in gerrit for a review
16:33 dprince pabelanger: 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 pabelanger EmilienM: So, how is this for a use case. Move mysql to external node, make sure puppet modules work as expected
16:34 dprince pabelanger: 321491
16:34 * dprince sighs
16:35 pabelanger dprince: 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 team
16:37 pabelanger Like 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 eyes
16:38 xingchao joined #puppet-openstack
16:39 nibalizer pabelanger: i mean sure? but really the tooling has been built by the infra parts of puppet-openstack
16:39 nibalizer you can innovate in -infra if you want
16:39 nibalizer everyone wears lots of hats
16:40 zacdev joined #puppet-openstack
16:41 dgurtner xarses: 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 time
16:42 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Revert "Revert "Initial run_tests.sh script""  https://review.openstack.org/210412
16:42 nibalizer probably in a happy end-state the beaker node, the tempest node, and the other nodes should all be separate vms
16:42 nibalizer and nodepool multinode makes that doable
16:43 nibalizer I 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 nibalizer but I haven't had time to code that yet
16:43 pabelanger joined #puppet-openstack
16:43 pabelanger finally, znc is back
16:43 nibalizer as it is, devstack runs tempest on the same node
16:43 nibalizer so I agree with separting it for purity but hard to say that is the most important thing to solve now
16:44 xarses dgurtner: is this because the apache version changed?
16:44 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/201298
16:44 xarses dgurtner: or has it been a problem for a while, and we just haven't noticed?
16:44 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/207070
16:45 EmilienM pabelanger: 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 cover
16:45 dgurtner xarses: 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 EmilienM pabelanger: of course, if tooling is consistent between infra & puppet groups, that's awesome
16:46 xarses dgurtner: sounds good, looks good. I approved it.
16:48 dgurtner xarses: cool, thanks :)
16:50 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/210412
16:59 sergmelikyan joined #puppet-openstack
17:00 aimon joined #puppet-openstack
17:04 openstackgerrit Merged stackforge/puppet-ceph: Fix RGW Apache syslog creation  https://review.openstack.org/214135
17:04 pabelanger joined #puppet-openstack
17:05 sanjayu joined #puppet-openstack
17:17 angdraug joined #puppet-openstack
17:19 saneax joined #puppet-openstack
17:20 xarses joined #puppet-openstack
17:25 pabelanger My last plea, can we please hold off on any other checks to puppet-openstack-integration until mid-cycle
17:25 pabelanger if that is too far away, I suggest we get in a room / conference soon
17:26 EmilienM pabelanger: other checks == extending scenarios001 after it got merged?
17:26 pabelanger I 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 me
17:26 pabelanger s/check/changes
17:27 EmilienM pabelanger: we will probably merge this first iteration
17:27 pabelanger we are not reverting code in https://review.openstack.org/#/c/210412/ which has been running for the last 6 weeks
17:27 pabelanger very frustrating
17:27 pabelanger and now proposing gate changes
17:28 EmilienM pabelanger: I don't see how being in the same room will help us to agree
17:28 EmilienM we can setup videoconference if you want/need
17:28 EmilienM I don't see how an iteration is frustrating
17:28 tiswanso joined #puppet-openstack
17:29 pabelanger removing functionality from a patchset, which was merged to be reverted is.
17:30 EmilienM pabelanger: yeah your patch broke our CI
17:30 EmilienM because I did not carefully review it
17:30 EmilienM now I'm reverting the revert but without breaking our CI
17:30 EmilienM beaker runs puppet as root
17:30 EmilienM so we need to adjust that
17:31 EmilienM I don't understand frustration here - we just wanna make it work on both jobs
17:39 austin81 joined #puppet-openstack
17:39 timrc joined #puppet-openstack
17:41 jesusaurus joined #puppet-openstack
17:55 ericpeterson joined #puppet-openstack
18:41 xingchao joined #puppet-openstack
18:44 paramite joined #puppet-openstack
18:47 mjblack joined #puppet-openstack
18:51 openstackgerrit Merged openstack/puppet-modulesync-configs: Create sync-projects.sh script  https://review.openstack.org/210528
19:02 ducttape_ joined #puppet-openstack
19:12 danieru joined #puppet-openstack
19:53 iurygregory there 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 EmilienM iurygregory: yes
19:53 EmilienM iurygregory: when binding API with API, it seems serverspec can't find out 5000 is binded on tcp or udp
19:53 EmilienM oops
19:53 EmilienM API with WSGI*
19:54 iurygregory thanks EmilienM
20:00 jpena joined #puppet-openstack
20:02 chem joined #puppet-openstack
20:03 stamak joined #puppet-openstack
20:43 zacdev joined #puppet-openstack
20:48 xingchao joined #puppet-openstack
21:01 openstackgerrit Emilien Macchi proposed openstack/puppet-keystone: CI - do not merge - testing https://review.openstack.org/#/c/210412/  https://review.openstack.org/214793
21:12 openstackgerrit Ramkumar 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/214798
21:13 EmilienM rgowrishankar: you might need to split your commit message ^
21:13 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/210412
21:15 austin81 left #puppet-openstack
21:18 bogdando joined #puppet-openstack
21:23 rgowrishankar emilienM: Do you want me to cancel this one and create a new one? The message shows up correctly on the review webpage.
21:23 EmilienM rgowrishankar: please use git amend
21:23 rgowrishankar ok, will do.
21:24 rgowrishankar i was not sure if I use git amend without any changes in files whether the review tool would get confused
21:24 EmilienM rgowrishankar: and eventually look https://wiki.openstack.org/wiki/GitCommitMessages
21:30 openstackgerrit Adam Vinsh proposed openstack/puppet-swift: WIP: Introduce swift_service class  https://review.openstack.org/203220
21:39 openstackgerrit Ramkumar Gowrishankar proposed openstack/puppet-neutron: Support for Nuage Neutron plugin configration and Nuage VRS configuration in puppet-neutron.  https://review.openstack.org/214798
21:41 rgowrishankar EmilienM: Sent out the review again with *hopefully* better commit message.
21:41 EmilienM rgowrishankar: cool!
21:42 EmilienM rgowrishankar: well, your commit is still not correct I'm sorry
21:42 EmilienM you should not go up to > 80 characters per line
21:48 xingchao joined #puppet-openstack
21:49 openstackgerrit Ramkumar Gowrishankar proposed openstack/puppet-neutron: Support for Nuage Neutron plugin and Nuage VRS in puppet-neutron  https://review.openstack.org/214798
21:49 rgowrishankar Emilien: third times the charm?
21:50 EmilienM rgowrishankar: don't worry, you'll have more patchsets, I had a quick review and I have a lot of comments
21:50 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/210412
21:52 rgowrishankar EmilienM: 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 EmilienM rgowrishankar: cool
22:14 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/210412
22:15 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/201298
22:19 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/201298
22:20 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/207070
22:23 gildub joined #puppet-openstack
22:23 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/207078
22:41 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Initial run_tests.sh script  https://review.openstack.org/210412
22:44 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: Create puppet folder layout  https://review.openstack.org/201298
22:45 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: deploy MySQL and Keystone (WSGI)  https://review.openstack.org/207070
22:45 saneax joined #puppet-openstack
22:45 openstackgerrit David Gurtner proposed stackforge/puppet-ceph: Drop no longer supported releases  https://review.openstack.org/214104
22:45 openstackgerrit Emilien Macchi proposed openstack/puppet-openstack-integration: scenario001: configure and run tempest  https://review.openstack.org/207078
22:45 openstackgerrit David Gurtner proposed stackforge/puppet-ceph: use full length APT key  https://review.openstack.org/209981
22:46 openstackgerrit David Gurtner proposed stackforge/puppet-ceph: Be more specific with CentOS7 package exclude  https://review.openstack.org/214093
22:48 openstackgerrit Merged openstack/puppet-openstack-specs: Enabling-federation  https://review.openstack.org/190361
22:49 xingchao joined #puppet-openstack
22:50 dgurtner joined #puppet-openstack
23:00 saneax joined #puppet-openstack
23:16 aimon joined #puppet-openstack
23:37 fedexo joined #puppet-openstack
23:53 tiswanso joined #puppet-openstack
23:57 openstackgerrit Paul Belanger proposed openstack/puppet-openstack-integration: [WIP] And example commit to keep beaker-jobs and integration happy  https://review.openstack.org/214897

| Channels | #puppet-openstack index | Today | | Search | Google Search | Plain-Text | summary