From iwienand at redhat.com Fri Feb 2 06:15:10 2018 From: iwienand at redhat.com (Ian Wienand) Date: Fri, 2 Feb 2018 17:15:10 +1100 Subject: [OpenStack-Infra] Adding ARM64 cloud to infra In-Reply-To: References: Message-ID: Hi, A quick status update on the integration of the Linaro aarch64 cloud - Everything is integrated into the system-config cloud-launcher bits, so all auth tokens are in place, keys are deploying, etc. - I've started with a mirror. So far only a minor change to puppet required for the ports sources list [1]. It's a bit bespoke at the moment but up as mirror.cn1.linaro.openstack.org. - AFS is not supported out-of-the-box. There is a series at [2] that I've been working on today, with some success. I have custom packages at [3] which seem to work and can see our mirror directories. I plan to puppet this in for our immediate needs, and keep working to get it integrated properly upstream. - For building images, we are getting closer. The series at [4] is still very WIP but can produce a working gpt+efi image. I don't see any real blockers there; work will continue to make sure we get the interface if not perfect, at least not something we totally regret later :) - Once that is done, it should be straight forward to add a nodepool-builder in the cloud and have it build images, and zuul should be able to launch them just like any other node (famous last words). Thanks all, -i [1] https://review.openstack.org/539083 [2] https://gerrit.openafs.org/11940 [3] https://tarballs.openstack.org/package-afs-aarch64/ [4] https://review.openstack.org/#/c/539731/ From skratbag at gmail.com Tue Feb 6 04:09:17 2018 From: skratbag at gmail.com (David Logan) Date: Tue, 6 Feb 2018 13:39:17 +0930 Subject: [OpenStack-Infra] Help needed? Message-ID: Hi Folks, I'm a Unix/Linux Admin of some years experience, looking to contribute to Openstack as a community Sysadmin. I have experience in RH/SuSE/CentOS etc, use Puppet daily and am starting to look at Ansible. Am reasonably cloud aware, used AWS and Azure to a limited extent. Not much Openstack but we are looking :) If I can be of any help, please feel free to contact me. Cheers David Logan -- if in trouble, or in doubt run in circles, scream and shout -------------- next part -------------- An HTML attachment was scrubbed... URL: From anteaya at anteaya.info Tue Feb 6 13:45:26 2018 From: anteaya at anteaya.info (Anita Kuno) Date: Tue, 6 Feb 2018 08:45:26 -0500 Subject: [OpenStack-Infra] Help needed? In-Reply-To: References: Message-ID: On 2018-02-05 11:09 PM, David Logan wrote: > Hi Folks, > > I'm a Unix/Linux Admin of some years experience, looking to contribute to > Openstack as a community Sysadmin. > > I have experience in RH/SuSE/CentOS etc, use Puppet daily and am starting > to look at Ansible. Am reasonably cloud aware, used AWS and Azure to a > limited extent. Not much Openstack but we are looking :) > > If I can be of any help, please feel free to contact me. > > Cheers > David Logan > > Hi David: My suggestion would be to join the #openstack-infra channel on irc, the freenode network. Introduce yourself to clarkb, the Infra program team lead (ptl) and settle in for some reading of the backscroll. It is the most immediate and up to date source of information of the current goings on. Clark or others can help you find your way about, getting oriented with docs and links and such. I'm sure someone else has a more through suggestion but this approach would be a start. Welcome to infra, Anita. From hadi.amir at gmail.com Tue Feb 13 16:58:20 2018 From: hadi.amir at gmail.com (Amir Hadi) Date: Tue, 13 Feb 2018 17:58:20 +0100 Subject: [OpenStack-Infra] Shade on Python 2.7 in Ubuntu fails due to UCS2 problem Message-ID: <137F5B9A-52D0-4706-A7E6-8A81A5DD971C@gmail.com> Hi, we use the OpenStack Ansible Plugin, which depends on shade. The installed shade version is `shade==1.26.0`. Our ansible setup is in a docker images, which comes from `ubuntu:16.04`. Our deployment fails, because the openstack plugin reports the following: /home/builder/epoch/deployment/ansible/inventory/openstack.yml with openstack plugin: shade is required for the OpenStack inventory plugin. OpenStack inventory sources will be skipped. Then I fired up the python shell to `import shade` which results in the following error: >>> import shade Traceback (most recent call last): File "", line 1, in File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/shade/__init__.py", line 24, in from shade.openstackcloud import OpenStackCloud File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/shade/openstackcloud.py", line 46, in from shade import _legacy_clients File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/shade/_legacy_clients.py", line 18, in from shade import _utils File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/shade/_utils.py", line 20, in import netifaces ImportError: /home/builder/ansible_deploy/local/lib/python2.7/site-packages/netifaces.so: undefined symbol: PyUnicodeUCS2_FromString It looks like this is a problem with different ABIs (see https://stackoverflow.com/questions/31644056/is-python-2-7-wide-build-usc4-not-compatible-with-certain-libraries). Our Python seems to be compiled to use UCS4: >>> import sys >>> print sys.maxunicode 1114111 Any ideas how to resolve this? Best regards, Amir Hadi PS: It’s been a while that I have used mailing lists, I hope the formatting of this message is ok. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Tue Feb 13 17:04:26 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 13 Feb 2018 09:04:26 -0800 Subject: [OpenStack-Infra] Shade on Python 2.7 in Ubuntu fails due to UCS2 problem In-Reply-To: <137F5B9A-52D0-4706-A7E6-8A81A5DD971C@gmail.com> References: <137F5B9A-52D0-4706-A7E6-8A81A5DD971C@gmail.com> Message-ID: <1518541466.4169109.1269537536.5965EED9@webmail.messagingengine.com> On Tue, Feb 13, 2018, at 8:58 AM, Amir Hadi wrote: > Hi, > > we use the OpenStack Ansible Plugin, which depends on shade. The > installed shade version is `shade==1.26.0`. Our ansible setup is in a > docker images, which comes from `ubuntu:16.04`. > > Our deployment fails, because the openstack plugin reports the following: > /home/builder/epoch/deployment/ansible/inventory/openstack.yml with openstack > plugin: shade is required for the OpenStack inventory plugin. OpenStack > inventory sources will be skipped. > > Then I fired up the python shell to `import shade` which results in the > following error: > >>> import shade > Traceback (most recent call last): > File "", line 1, in > File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/ > shade/__init__.py", line 24, in > from shade.openstackcloud import OpenStackCloud > File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/ > shade/openstackcloud.py", line 46, in > from shade import _legacy_clients > File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/ > shade/_legacy_clients.py", line 18, in > from shade import _utils > File "/home/builder/ansible_deploy/local/lib/python2.7/site-packages/ > shade/_utils.py", line 20, in > import netifaces > ImportError: /home/builder/ansible_deploy/local/lib/python2.7/site- > packages/netifaces.so: undefined symbol: PyUnicodeUCS2_FromString > > It looks like this is a problem with different ABIs (see > https://stackoverflow.com/questions/31644056/is-python-2-7-wide-build-usc4-not-compatible-with-certain-libraries). > Our Python seems to be compiled to use UCS4: > >>> import sys > >>> print sys.maxunicode > 1114111 > > Any ideas how to resolve this? > > Best regards, > Amir Hadi > > PS: It’s been a while that I have used mailing lists, I hope the > formatting of this message is ok. The problem is in the upstream netifaces package and is being tracked at https://github.com/al45tair/netifaces/issues/2. Until that is fixed you can install netifaces without using wheels to avoid this problem. Something like `pip install --force-reinstall --upgrade --no-binary netifaces` Hope this helps, Clark From cboylan at sapwetik.org Tue Feb 13 22:50:00 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 13 Feb 2018 14:50:00 -0800 Subject: [OpenStack-Infra] PTG Scheduling Message-ID: <1518562200.933178.1269918552.06479C30@webmail.messagingengine.com> Hello, It sounded like a rough schedule would be helpful for people in the Infra meeting today so I've gone ahead ans started work on one. You can see the current iteration at https://ethercalc.openstack.org/cvro305izog2. Our PTG week is split in two. The first two days will be taken up by the Infra Helproom. If you are able to hang out in the room and help out the projects that will be signing up on the ethercalc that would be great (I expect I will be there the entire time). Then the last three days of the week will be spent on infra specific hacking and conversations etc. For these days I've pencilled in Zuul for the first half of our time because it is about half the total number of topics proposed and some people working on Zuul will be leaving early Friday. Then for the rest of the time I've penciled in rough topics based on the categorization I did at https://etherpad.openstack.org/p/infra-rocky-ptg. Please look this over and make sure it works for you. Let me know if there are major issues and we will do our best to accommodate everyone. You might also notice that Storyboard is not really on the schedule. More than happy to have them and make sure they have electricity and caffeine. I just wasn't sure when Zara and SotK and others would be around. Maybe the storyboarders can add a note on the ethercalc for when they will be around so that people interested in storyboarding can find the group? Some other general PTG scheduling item that might interest you include the board meeting on Monday and game night Thursday (https://etherpad.openstack.org/p/DUB_Game_Night). Thank you, Clark From pabelanger at redhat.com Thu Feb 15 20:17:58 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Thu, 15 Feb 2018 15:17:58 -0500 Subject: [OpenStack-Infra] Team dinner at Dublin PTG Message-ID: <20180215201758.GA6252@localhost.localdomain> Greetings, It is that time again when we all get out from behind our computers and attempt to be social for the evening. Talking about great subjects like sportsball and favorite beers. As usually, please indicate which datetime works better for you by adding your name and vote to ethercalc[1]. Right now, we are likely going to end up at a pub for drinks and food, if you have a specific place in mind, please reply. I'll do my best to find enough room for everybody, however unsure if everybody will sit together at a large table. [1] https://ethercalc.openstack.org/pqhemnrgnz7t From iwienand at redhat.com Mon Feb 19 03:25:34 2018 From: iwienand at redhat.com (Ian Wienand) Date: Mon, 19 Feb 2018 14:25:34 +1100 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders Message-ID: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> Hi, How should we go about restricting certain image builds to specific nodepool builder instances? My immediate issue is with ARM64 image builds, which I only want to happen on a builder hosted in an ARM64 cloud. Currently, the builders go through the image list and check "is the existing image missing or too old, if so, build" [1]. Additionally, all builders share a configuration file [2]; so builders don't know "who they are". I'd propose we add an arbitrary tag/match system so that builders can pickup only those builds they mark themselves capable of building? e.g. diskimages would specify required builder tags similar to: --- diskimages: - name: arm64-ubuntu-xenial elements: - block-device-efi - vm - ubuntu-minimal ... env-vars: TMPDIR: /opt/dib_tmp DIB_CHECKSUM: '1' ... builder-requires: architecture: arm64 --- The nodepool.yaml would grow another section similar: --- builder-provides: architecture: arm64 something_else_unique_about_this_buidler: true --- For OpenStack, we would template this section in the config file via puppet in [2], ensuring above that only our theoretical ARM64 build machine had that section in it's config. The nodepool-buidler build loop can then check that its builder-provides section has all the tags specified in an image's "builder-requires" section before deciding to start building. Thoughts welcome :) -i [1] https://git.openstack.org/cgit/openstack-infra/nodepool/tree/nodepool/builder.py#n607 [2] https://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/nodepool.yaml From remo at italy1.com Mon Feb 19 04:21:30 2018 From: remo at italy1.com (remo at italy1.com) Date: Sun, 18 Feb 2018 20:21:30 -0800 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> Message-ID: Content-Type: multipart/alternative; boundary="=_5837c9f000872ae1dfc7317ed2bea8a3" --=_5837c9f000872ae1dfc7317ed2bea8a3 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=utf-8 WW91IHByb2JhYmx5IG5lZWQgdG8gY2hhbmdlIHBvbGljeS5qc29uIGFuZCBjcmVhdGUgc29tZSBy dWxlcyB0aGVyZSB3aXRoIGF6IG9wdGlvbnMuIA0KDQrvo78gZGFsIG1pbyBpUGhvbmUgWCANCg0K PiBJbCBnaW9ybm8gMTggZmViIDIwMTgsIGFsbGUgb3JlIDE5OjI1LCBJYW4gV2llbmFuZCA8aXdp ZW5hbmRAcmVkaGF0LmNvbT4gaGEgc2NyaXR0bzoNCj4gDQo+IEhpLA0KPiANCj4gSG93IHNob3Vs ZCB3ZSBnbyBhYm91dCByZXN0cmljdGluZyBjZXJ0YWluIGltYWdlIGJ1aWxkcyB0byBzcGVjaWZp Yw0KPiBub2RlcG9vbCBidWlsZGVyIGluc3RhbmNlcz8gIE15IGltbWVkaWF0ZSBpc3N1ZSBpcyB3 aXRoIEFSTTY0IGltYWdlDQo+IGJ1aWxkcywgd2hpY2ggSSBvbmx5IHdhbnQgdG8gaGFwcGVuIG9u IGEgYnVpbGRlciBob3N0ZWQgaW4gYW4gQVJNNjQNCj4gY2xvdWQuDQo+IA0KPiBDdXJyZW50bHks IHRoZSBidWlsZGVycyBnbyB0aHJvdWdoIHRoZSBpbWFnZSBsaXN0IGFuZCBjaGVjayAiaXMgdGhl DQo+IGV4aXN0aW5nIGltYWdlIG1pc3Npbmcgb3IgdG9vIG9sZCwgaWYgc28sIGJ1aWxkIiBbMV0u ICBBZGRpdGlvbmFsbHksDQo+IGFsbCBidWlsZGVycyBzaGFyZSBhIGNvbmZpZ3VyYXRpb24gZmls ZSBbMl07IHNvIGJ1aWxkZXJzIGRvbid0IGtub3cNCj4gIndobyB0aGV5IGFyZSIuDQo+IA0KPiBJ J2QgcHJvcG9zZSB3ZSBhZGQgYW4gYXJiaXRyYXJ5IHRhZy9tYXRjaCBzeXN0ZW0gc28gdGhhdCBi dWlsZGVycyBjYW4NCj4gcGlja3VwIG9ubHkgdGhvc2UgYnVpbGRzIHRoZXkgbWFyayB0aGVtc2Vs dmVzIGNhcGFibGUgb2YgYnVpbGRpbmc/DQo+IA0KPiBlLmcuIGRpc2tpbWFnZXMgd291bGQgc3Bl Y2lmeSByZXF1aXJlZCBidWlsZGVyIHRhZ3Mgc2ltaWxhciB0bzoNCj4gDQo+IC0tLQ0KPiBkaXNr aW1hZ2VzOg0KPiAgLSBuYW1lOiBhcm02NC11YnVudHUteGVuaWFsDQo+ICAgIGVsZW1lbnRzOg0K PiAgICAgIC0gYmxvY2stZGV2aWNlLWVmaQ0KPiAgICAgIC0gdm0NCj4gICAgICAtIHVidW50dS1t aW5pbWFsDQo+ICAgICAgLi4uDQo+ICAgIGVudi12YXJzOg0KPiAgICAgIFRNUERJUjogL29wdC9k aWJfdG1wDQo+ICAgICAgRElCX0NIRUNLU1VNOiAnMScNCj4gICAgICAuLi4NCj4gICAgYnVpbGRl ci1yZXF1aXJlczoNCj4gICAgICBhcmNoaXRlY3R1cmU6IGFybTY0DQo+IC0tLQ0KPiANCj4gVGhl IG5vZGVwb29sLnlhbWwgd291bGQgZ3JvdyBhbm90aGVyIHNlY3Rpb24gc2ltaWxhcjoNCj4gDQo+ IC0tLQ0KPiBidWlsZGVyLXByb3ZpZGVzOg0KPiAgYXJjaGl0ZWN0dXJlOiBhcm02NA0KPiAgc29t ZXRoaW5nX2Vsc2VfdW5pcXVlX2Fib3V0X3RoaXNfYnVpZGxlcjogdHJ1ZQ0KPiAtLS0NCj4gDQo+ IEZvciBPcGVuU3RhY2ssIHdlIHdvdWxkIHRlbXBsYXRlIHRoaXMgc2VjdGlvbiBpbiB0aGUgY29u ZmlnIGZpbGUgdmlhDQo+IHB1cHBldCBpbiBbMl0sIGVuc3VyaW5nIGFib3ZlIHRoYXQgb25seSBv dXIgdGhlb3JldGljYWwgQVJNNjQgYnVpbGQNCj4gbWFjaGluZSBoYWQgdGhhdCBzZWN0aW9uIGlu IGl0J3MgY29uZmlnLg0KPiANCj4gVGhlIG5vZGVwb29sLWJ1aWRsZXIgYnVpbGQgbG9vcCBjYW4g dGhlbiBjaGVjayB0aGF0IGl0cw0KPiBidWlsZGVyLXByb3ZpZGVzIHNlY3Rpb24gaGFzIGFsbCB0 aGUgdGFncyBzcGVjaWZpZWQgaW4gYW4gaW1hZ2Uncw0KPiAiYnVpbGRlci1yZXF1aXJlcyIgc2Vj dGlvbiBiZWZvcmUgZGVjaWRpbmcgdG8gc3RhcnQgYnVpbGRpbmcuDQo+IA0KPiBUaG91Z2h0cyB3 ZWxjb21lIDopDQo+IA0KPiAtaQ0KPiANCj4gWzFdIGh0dHBzOi8vZ2l0Lm9wZW5zdGFjay5vcmcv Y2dpdC9vcGVuc3RhY2staW5mcmEvbm9kZXBvb2wvdHJlZS9ub2RlcG9vbC9idWlsZGVyLnB5I242 MDcNCj4gWzJdIGh0dHBzOi8vZ2l0Lm9wZW5zdGFjay5vcmcvY2dpdC9vcGVuc3RhY2staW5mcmEv cHJvamVjdC1jb25maWcvdHJlZS9ub2RlcG9vbC9ub2RlcG9vbC55YW1sDQo+IA0KPiBfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBPcGVuU3RhY2stSW5m cmEgbWFpbGluZyBsaXN0DQo+IE9wZW5TdGFjay1JbmZyYUBsaXN0cy5vcGVuc3RhY2sub3JnDQo+ IGh0dHA6Ly9saXN0cy5vcGVuc3RhY2sub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9vcGVu c3RhY2staW5mcmENCg== --=_5837c9f000872ae1dfc7317ed2bea8a3-- From remo at italy1.com Mon Feb 19 04:21:30 2018 From: remo at italy1.com (remo at italy1.com) Date: Sun, 18 Feb 2018 20:21:30 -0800 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> Message-ID: Content-Type: multipart/alternative; boundary="=_5837c9f000872ae1dfc7317ed2bea8a3" --=_5837c9f000872ae1dfc7317ed2bea8a3 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset=utf-8 WW91IHByb2JhYmx5IG5lZWQgdG8gY2hhbmdlIHBvbGljeS5qc29uIGFuZCBjcmVhdGUgc29tZSBy dWxlcyB0aGVyZSB3aXRoIGF6IG9wdGlvbnMuIA0KDQrvo78gZGFsIG1pbyBpUGhvbmUgWCANCg0K PiBJbCBnaW9ybm8gMTggZmViIDIwMTgsIGFsbGUgb3JlIDE5OjI1LCBJYW4gV2llbmFuZCA8aXdp ZW5hbmRAcmVkaGF0LmNvbT4gaGEgc2NyaXR0bzoNCj4gDQo+IEhpLA0KPiANCj4gSG93IHNob3Vs ZCB3ZSBnbyBhYm91dCByZXN0cmljdGluZyBjZXJ0YWluIGltYWdlIGJ1aWxkcyB0byBzcGVjaWZp Yw0KPiBub2RlcG9vbCBidWlsZGVyIGluc3RhbmNlcz8gIE15IGltbWVkaWF0ZSBpc3N1ZSBpcyB3 aXRoIEFSTTY0IGltYWdlDQo+IGJ1aWxkcywgd2hpY2ggSSBvbmx5IHdhbnQgdG8gaGFwcGVuIG9u IGEgYnVpbGRlciBob3N0ZWQgaW4gYW4gQVJNNjQNCj4gY2xvdWQuDQo+IA0KPiBDdXJyZW50bHks IHRoZSBidWlsZGVycyBnbyB0aHJvdWdoIHRoZSBpbWFnZSBsaXN0IGFuZCBjaGVjayAiaXMgdGhl DQo+IGV4aXN0aW5nIGltYWdlIG1pc3Npbmcgb3IgdG9vIG9sZCwgaWYgc28sIGJ1aWxkIiBbMV0u ICBBZGRpdGlvbmFsbHksDQo+IGFsbCBidWlsZGVycyBzaGFyZSBhIGNvbmZpZ3VyYXRpb24gZmls ZSBbMl07IHNvIGJ1aWxkZXJzIGRvbid0IGtub3cNCj4gIndobyB0aGV5IGFyZSIuDQo+IA0KPiBJ J2QgcHJvcG9zZSB3ZSBhZGQgYW4gYXJiaXRyYXJ5IHRhZy9tYXRjaCBzeXN0ZW0gc28gdGhhdCBi dWlsZGVycyBjYW4NCj4gcGlja3VwIG9ubHkgdGhvc2UgYnVpbGRzIHRoZXkgbWFyayB0aGVtc2Vs dmVzIGNhcGFibGUgb2YgYnVpbGRpbmc/DQo+IA0KPiBlLmcuIGRpc2tpbWFnZXMgd291bGQgc3Bl Y2lmeSByZXF1aXJlZCBidWlsZGVyIHRhZ3Mgc2ltaWxhciB0bzoNCj4gDQo+IC0tLQ0KPiBkaXNr aW1hZ2VzOg0KPiAgLSBuYW1lOiBhcm02NC11YnVudHUteGVuaWFsDQo+ICAgIGVsZW1lbnRzOg0K PiAgICAgIC0gYmxvY2stZGV2aWNlLWVmaQ0KPiAgICAgIC0gdm0NCj4gICAgICAtIHVidW50dS1t aW5pbWFsDQo+ICAgICAgLi4uDQo+ICAgIGVudi12YXJzOg0KPiAgICAgIFRNUERJUjogL29wdC9k aWJfdG1wDQo+ICAgICAgRElCX0NIRUNLU1VNOiAnMScNCj4gICAgICAuLi4NCj4gICAgYnVpbGRl ci1yZXF1aXJlczoNCj4gICAgICBhcmNoaXRlY3R1cmU6IGFybTY0DQo+IC0tLQ0KPiANCj4gVGhl IG5vZGVwb29sLnlhbWwgd291bGQgZ3JvdyBhbm90aGVyIHNlY3Rpb24gc2ltaWxhcjoNCj4gDQo+ IC0tLQ0KPiBidWlsZGVyLXByb3ZpZGVzOg0KPiAgYXJjaGl0ZWN0dXJlOiBhcm02NA0KPiAgc29t ZXRoaW5nX2Vsc2VfdW5pcXVlX2Fib3V0X3RoaXNfYnVpZGxlcjogdHJ1ZQ0KPiAtLS0NCj4gDQo+ IEZvciBPcGVuU3RhY2ssIHdlIHdvdWxkIHRlbXBsYXRlIHRoaXMgc2VjdGlvbiBpbiB0aGUgY29u ZmlnIGZpbGUgdmlhDQo+IHB1cHBldCBpbiBbMl0sIGVuc3VyaW5nIGFib3ZlIHRoYXQgb25seSBv dXIgdGhlb3JldGljYWwgQVJNNjQgYnVpbGQNCj4gbWFjaGluZSBoYWQgdGhhdCBzZWN0aW9uIGlu IGl0J3MgY29uZmlnLg0KPiANCj4gVGhlIG5vZGVwb29sLWJ1aWRsZXIgYnVpbGQgbG9vcCBjYW4g dGhlbiBjaGVjayB0aGF0IGl0cw0KPiBidWlsZGVyLXByb3ZpZGVzIHNlY3Rpb24gaGFzIGFsbCB0 aGUgdGFncyBzcGVjaWZpZWQgaW4gYW4gaW1hZ2Uncw0KPiAiYnVpbGRlci1yZXF1aXJlcyIgc2Vj dGlvbiBiZWZvcmUgZGVjaWRpbmcgdG8gc3RhcnQgYnVpbGRpbmcuDQo+IA0KPiBUaG91Z2h0cyB3 ZWxjb21lIDopDQo+IA0KPiAtaQ0KPiANCj4gWzFdIGh0dHBzOi8vZ2l0Lm9wZW5zdGFjay5vcmcv Y2dpdC9vcGVuc3RhY2staW5mcmEvbm9kZXBvb2wvdHJlZS9ub2RlcG9vbC9idWlsZGVyLnB5I242 MDcNCj4gWzJdIGh0dHBzOi8vZ2l0Lm9wZW5zdGFjay5vcmcvY2dpdC9vcGVuc3RhY2staW5mcmEv cHJvamVjdC1jb25maWcvdHJlZS9ub2RlcG9vbC9ub2RlcG9vbC55YW1sDQo+IA0KPiBfX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBPcGVuU3RhY2stSW5m cmEgbWFpbGluZyBsaXN0DQo+IE9wZW5TdGFjay1JbmZyYUBsaXN0cy5vcGVuc3RhY2sub3JnDQo+ IGh0dHA6Ly9saXN0cy5vcGVuc3RhY2sub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9vcGVu c3RhY2staW5mcmENCg== --=_5837c9f000872ae1dfc7317ed2bea8a3-- From shrewsbury.dave at gmail.com Mon Feb 19 13:28:27 2018 From: shrewsbury.dave at gmail.com (David Shrewsbury) Date: Mon, 19 Feb 2018 08:28:27 -0500 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> Message-ID: Hi, On Sun, Feb 18, 2018 at 10:25 PM, Ian Wienand wrote: > Hi, > > How should we go about restricting certain image builds to specific > nodepool builder instances? My immediate issue is with ARM64 image > builds, which I only want to happen on a builder hosted in an ARM64 > cloud. > > Currently, the builders go through the image list and check "is the > existing image missing or too old, if so, build" [1]. Additionally, > all builders share a configuration file [2]; so builders don't know > "who they are". > > Why not just split the builder configuration file? I don't see a need to add code to do this. > I'd propose we add an arbitrary tag/match system so that builders can > pickup only those builds they mark themselves capable of building? > > e.g. diskimages would specify required builder tags similar to: > > --- > diskimages: > - name: arm64-ubuntu-xenial > elements: > - block-device-efi > - vm > - ubuntu-minimal > ... > env-vars: > TMPDIR: /opt/dib_tmp > DIB_CHECKSUM: '1' > ... > builder-requires: > architecture: arm64 > --- > > The nodepool.yaml would grow another section similar: > > --- > builder-provides: > architecture: arm64 > something_else_unique_about_this_buidler: true > --- > > For OpenStack, we would template this section in the config file via > puppet in [2], ensuring above that only our theoretical ARM64 build > machine had that section in it's config. > > The nodepool-buidler build loop can then check that its > builder-provides section has all the tags specified in an image's > "builder-requires" section before deciding to start building. > > Thoughts welcome :) > > -i > > [1] https://git.openstack.org/cgit/openstack-infra/nodepool/ > tree/nodepool/builder.py#n607 > [2] https://git.openstack.org/cgit/openstack-infra/project- > config/tree/nodepool/nodepool.yaml > > _______________________________________________ > Zuul-discuss mailing list > Zuul-discuss at lists.zuul-ci.org > http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss > -- David Shrewsbury (Shrews) -------------- next part -------------- An HTML attachment was scrubbed... URL: From pabelanger at redhat.com Mon Feb 19 15:23:28 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Mon, 19 Feb 2018 10:23:28 -0500 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> Message-ID: <20180219152328.GA7920@localhost.localdomain> On Mon, Feb 19, 2018 at 08:28:27AM -0500, David Shrewsbury wrote: > Hi, > > On Sun, Feb 18, 2018 at 10:25 PM, Ian Wienand wrote: > > > Hi, > > > > How should we go about restricting certain image builds to specific > > nodepool builder instances? My immediate issue is with ARM64 image > > builds, which I only want to happen on a builder hosted in an ARM64 > > cloud. > > > > Currently, the builders go through the image list and check "is the > > existing image missing or too old, if so, build" [1]. Additionally, > > all builders share a configuration file [2]; so builders don't know > > "who they are". > > > > > > Why not just split the builder configuration file? I don't see a need to > add code > to do this. > In our case (openstack-infra) this will require another change to puppet-nodepool to support this. Not that we cannot, but it will now mean we'll have 7[1] different nodepool configuration files to now manage. 4 x nodepool-launchers, 3 x nodepool-builders, since we have 7 services running. We could update puppet to start templating or add support for nodepool.d (like zuul.d) and better split our configs too. I just haven't found time to write that patch. I did submit support homing diskimage builds to specific builder[2] a while back, which is more inline with what ianw is asking. This allows us to assign images to builders, if set. [1] http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool [2] https://review.openstack.org/461239/ > > > > > I'd propose we add an arbitrary tag/match system so that builders can > > pickup only those builds they mark themselves capable of building? > > > > e.g. diskimages would specify required builder tags similar to: > > > > --- > > diskimages: > > - name: arm64-ubuntu-xenial > > elements: > > - block-device-efi > > - vm > > - ubuntu-minimal > > ... > > env-vars: > > TMPDIR: /opt/dib_tmp > > DIB_CHECKSUM: '1' > > ... > > builder-requires: > > architecture: arm64 > > --- > > > > The nodepool.yaml would grow another section similar: > > > > --- > > builder-provides: > > architecture: arm64 > > something_else_unique_about_this_buidler: true > > --- > > > > For OpenStack, we would template this section in the config file via > > puppet in [2], ensuring above that only our theoretical ARM64 build > > machine had that section in it's config. > > > > The nodepool-buidler build loop can then check that its > > builder-provides section has all the tags specified in an image's > > "builder-requires" section before deciding to start building. > > > > Thoughts welcome :) > > > > -i > > > > [1] https://git.openstack.org/cgit/openstack-infra/nodepool/ > > tree/nodepool/builder.py#n607 > > [2] https://git.openstack.org/cgit/openstack-infra/project- > > config/tree/nodepool/nodepool.yaml > > > > _______________________________________________ > > Zuul-discuss mailing list > > Zuul-discuss at lists.zuul-ci.org > > http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss > > > > > > -- > David Shrewsbury (Shrews) > _______________________________________________ > Zuul-discuss mailing list > Zuul-discuss at lists.zuul-ci.org > http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss From corvus at inaugust.com Mon Feb 19 16:50:03 2018 From: corvus at inaugust.com (James E. Blair) Date: Mon, 19 Feb 2018 08:50:03 -0800 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <20180219152328.GA7920@localhost.localdomain> (Paul Belanger's message of "Mon, 19 Feb 2018 10:23:28 -0500") References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> <20180219152328.GA7920@localhost.localdomain> Message-ID: <87371wyldw.fsf@meyer.lemoncheese.net> Paul Belanger writes: > On Mon, Feb 19, 2018 at 08:28:27AM -0500, David Shrewsbury wrote: >> Hi, >> >> On Sun, Feb 18, 2018 at 10:25 PM, Ian Wienand wrote: >> >> > Hi, >> > >> > How should we go about restricting certain image builds to specific >> > nodepool builder instances? My immediate issue is with ARM64 image >> > builds, which I only want to happen on a builder hosted in an ARM64 >> > cloud. >> > >> > Currently, the builders go through the image list and check "is the >> > existing image missing or too old, if so, build" [1]. Additionally, >> > all builders share a configuration file [2]; so builders don't know >> > "who they are". >> > >> > >> >> Why not just split the builder configuration file? I don't see a need to >> add code >> to do this. >> > In our case (openstack-infra) this will require another change to > puppet-nodepool to support this. Not that we cannot, but it will now mean we'll > have 7[1] different nodepool configuration files to now manage. 4 x > nodepool-launchers, 3 x nodepool-builders, since we have 7 services running. This seems like a pretty legitimate case to split the config. Very little of the config for the arm64 builder will be shared with any of the other builders, so perhaps unlike the case where one simply wants high-availability launchers, this seems like a very sensible use of a separate config file. At any rate, that's what we should do in openstack-infra to solve the issue Ian asked about. -Jim From shrewsbury.dave at gmail.com Mon Feb 19 16:56:22 2018 From: shrewsbury.dave at gmail.com (David Shrewsbury) Date: Mon, 19 Feb 2018 11:56:22 -0500 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <20180219152328.GA7920@localhost.localdomain> References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> <20180219152328.GA7920@localhost.localdomain> Message-ID: On Mon, Feb 19, 2018 at 10:23 AM, Paul Belanger wrote: > On Mon, Feb 19, 2018 at 08:28:27AM -0500, David Shrewsbury wrote: > > Hi, > > > > On Sun, Feb 18, 2018 at 10:25 PM, Ian Wienand > wrote: > > > > > Hi, > > > > > > How should we go about restricting certain image builds to specific > > > nodepool builder instances? My immediate issue is with ARM64 image > > > builds, which I only want to happen on a builder hosted in an ARM64 > > > cloud. > > > > > > Currently, the builders go through the image list and check "is the > > > existing image missing or too old, if so, build" [1]. Additionally, > > > all builders share a configuration file [2]; so builders don't know > > > "who they are". > > > > > > > > > > Why not just split the builder configuration file? I don't see a need to > > add code > > to do this. > > > In our case (openstack-infra) this will require another change to > puppet-nodepool to support this. Not that we cannot, but it will now mean > we'll > have 7[1] different nodepool configuration files to now manage. 4 x > nodepool-launchers, 3 x nodepool-builders, since we have 7 services > running. > We don't have to have 1 config file per builder. Just one additional file for the arm64 builder. The others can still share the config we have now. -Dave -- David Shrewsbury (Shrews) -------------- next part -------------- An HTML attachment was scrubbed... URL: From iwienand at redhat.com Mon Feb 19 23:15:18 2018 From: iwienand at redhat.com (Ian Wienand) Date: Tue, 20 Feb 2018 10:15:18 +1100 Subject: [OpenStack-Infra] [nodepool] Restricting images to specific nodepool builders In-Reply-To: <20180219152328.GA7920@localhost.localdomain> References: <2a246157-8eff-169b-920b-d7f0ebee8580@redhat.com> <20180219152328.GA7920@localhost.localdomain> Message-ID: <787f7399-53b5-4d88-2a58-b6cc7f17f403@redhat.com> On 02/20/2018 02:23 AM, Paul Belanger wrote: >> Why not just split the builder configuration file? I don't see a >> need to add code to do this. I'm happy with this; I was just coming at it from an angle of not splitting the config file, but KISS :) > I did submit support homing diskimage builds to specific builder[2] a while > back, which is more inline with what ianw is asking. This allows us to assign > images to builders, if set. > [2] https://review.openstack.org/461239/ Only comment on this is that I think it might be better to avoid putting specific hostnames in there directly; but rather add meta-data to diskimage configurations describing the features they need on the builder, and have the builder then only choose those builds it knows it can do. Feels more natural for the message-queue/scale-out type environment where we can add/drop hosts at will. We've two real examples to inform design; needing the Xenial build host when all the others were trusty, and now the arm64 based ones. -i From pabelanger at redhat.com Mon Feb 19 23:57:29 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Mon, 19 Feb 2018 18:57:29 -0500 Subject: [OpenStack-Infra] Team dinner at Dublin PTG In-Reply-To: <20180215201758.GA6252@localhost.localdomain> References: <20180215201758.GA6252@localhost.localdomain> Message-ID: <20180219235729.GA13141@localhost.localdomain> On Thu, Feb 15, 2018 at 03:17:58PM -0500, Paul Belanger wrote: > Greetings, > > It is that time again when we all get out from behind our computers and attempt > to be social for the evening. Talking about great subjects like sportsball and > favorite beers. > > As usually, please indicate which datetime works better for you by adding your > name and vote to ethercalc[1]. > > Right now, we are likely going to end up at a pub for drinks and food, if you > have a specific place in mind, please reply. I'll do my best to find enough > room for everybody, however unsure if everybody will sit together at a large > table. > > [1] https://ethercalc.openstack.org/pqhemnrgnz7t Just a reminder to please take a moment to add your name to the team dinner list, so far it looks like we'll meet on Monday or Tuesday night. Thanks, Paul From kennelson11 at gmail.com Wed Feb 21 19:38:50 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 21 Feb 2018 19:38:50 +0000 Subject: [OpenStack-Infra] [PTG] StoryBoard Discussion Planning Message-ID: Hello Everyone! We have tentatively scheduled StoryBoard discussions Wednesday morning and will officialize it in the PTGbot soon. If there are specific things you wish to discuss please add them to our planning etherpad[1]! If you think you might attend, please also add your name to the list so we know you're interested. See you all next week! -Kendall (diablo_rojo) [1] https://etherpad.openstack.org/p/StoryBoard-Rocky-PTG -------------- next part -------------- An HTML attachment was scrubbed... URL: From emilien at redhat.com Thu Feb 22 10:01:02 2018 From: emilien at redhat.com (Emilien Macchi) Date: Thu, 22 Feb 2018 02:01:02 -0800 Subject: [OpenStack-Infra] [openstack-dev] [PTG] StoryBoard Discussion Planning In-Reply-To: References: Message-ID: On Wed, Feb 21, 2018 at 11:38 AM, Kendall Nelson wrote: > Hello Everyone! > > We have tentatively scheduled StoryBoard discussions Wednesday morning and > will officialize it in the PTGbot soon. If there are specific things you > wish to discuss please add them to our planning etherpad[1]! If you think > you might attend, please also add your name to the list so we know you're > interested. > > See you all next week! > > -Kendall (diablo_rojo) > > [1] https://etherpad.openstack.org/p/StoryBoard-Rocky-PTG > > Hey Kendall, Thanks a lot for making this happen. Unfortunately I won't be able to attend it since it overlaps with the TripleO sessions I really need to attend. But hopefully we can catch-up anytime during the week to discuss about TripleO / Storyboard future. Thanks, -- Emilien Macchi -------------- next part -------------- An HTML attachment was scrubbed... URL: From iwienand at redhat.com Fri Feb 23 05:35:16 2018 From: iwienand at redhat.com (Ian Wienand) Date: Fri, 23 Feb 2018 16:35:16 +1100 Subject: [OpenStack-Infra] Adding ARM64 cloud to infra In-Reply-To: References: Message-ID: <7a91e7aa-30f8-11c1-1490-b9e556e614a9@redhat.com> On 02/02/2018 05:15 PM, Ian Wienand wrote: > - Once that is done, it should be straight forward to add a > nodepool-builder in the cloud and have it build images, and zuul > should be able to launch them just like any other node (famous last > words). This roughly turned out to be correct :) In short, we now have ready xenial arm64 based nodes. If you request an ubuntu-xenial-arm64 node it should "just work" There are some caveats: - I have manually installed a diskimage-builder with the changes from [1] downwards onto nb03.openstack.org. These need to be finalised and a release tagged before we can remove nb03 from the emergency file (just means, don't run puppet on it). Reviews welcome! - I want to merge [2] and related changes to expose the image build logs, and also the webapp end-points so we can monitor active nodes, etc. It will take some baby-sitting so I plan on doing this next week. - We have mirror.cn1.linaro.openstack.org, but it's not mirroring anything that useful for arm64. We need to sort out mirroring of ubuntu ports, maybe some wheel builds, etc. - There's currently capacity for 8 nodes. So please take that into account when adding jobs. Everything seems in good shape at the moment. For posterity, here is the first ever arm64 ready node: nodepool at nl03:/var/log/nodepool$ nodepool list | grep arm64 | 0002683657 | linaro-cn1 | ubuntu-xenial-arm64 | c7bb6da6-52e5-4aab-88f1-ec0f1b392a0c | 211.148.24.200 | | ready | 00:00:03:43 | unlocked | :) -i [1] https://review.openstack.org/547161 [2] https://review.openstack.org/543671 From gema.gomez-solano at linaro.org Fri Feb 23 06:54:36 2018 From: gema.gomez-solano at linaro.org (Gema Gomez) Date: Fri, 23 Feb 2018 06:54:36 +0000 Subject: [OpenStack-Infra] Adding ARM64 cloud to infra In-Reply-To: <7a91e7aa-30f8-11c1-1490-b9e556e614a9@redhat.com> References: <7a91e7aa-30f8-11c1-1490-b9e556e614a9@redhat.com> Message-ID: <24fc59a5-4ce4-2733-b7e7-5712ee53013d@linaro.org> On 23/02/18 05:35, Ian Wienand wrote: > On 02/02/2018 05:15 PM, Ian Wienand wrote: >> - Once that is done, it should be straight forward to add a >> nodepool-builder in the cloud and have it build images, and zuul >> should be able to launch them just like any other node (famous last >> words). > > This roughly turned out to be correct :) > > In short, we now have ready xenial arm64 based nodes. If you request > an ubuntu-xenial-arm64 node it should "just work" > > There are some caveats: > > - I have manually installed a diskimage-builder with the changes from > [1] downwards onto nb03.openstack.org. These need to be finalised > and a release tagged before we can remove nb03 from the emergency > file (just means, don't run puppet on it). Reviews welcome! > > - I want to merge [2] and related changes to expose the image build > logs, and also the webapp end-points so we can monitor active > nodes, etc. It will take some baby-sitting so I plan on doing this > next week. > > - We have mirror.cn1.linaro.openstack.org, but it's not mirroring > anything that useful for arm64. We need to sort out mirroring of > ubuntu ports, maybe some wheel builds, etc. > > - There's currently capacity for 8 nodes. So please take that into > account when adding jobs. > > Everything seems in good shape at the moment. For posterity, here is > the first ever arm64 ready node: > > nodepool at nl03:/var/log/nodepool$ nodepool list | grep arm64 > | 0002683657 | linaro-cn1 | ubuntu-xenial-arm64 | c7bb6da6-52e5-4aab-88f1-ec0f1b392a0c | 211.148.24.200 | | ready | 00:00:03:43 | unlocked | > > :) Thank you, for the update! This is awesome news and great work \o/ Cheers, Gema > > -i > > [1] https://review.openstack.org/547161 > [2] https://review.openstack.org/543671 > -- Gema Gomez-Solano Tech Lead, SDI Linaro Ltd IRC: gema@#linaro on irc.freenode.net From rbergero at redhat.com Sun Feb 25 15:32:17 2018 From: rbergero at redhat.com (Robyn Bergeron) Date: Sun, 25 Feb 2018 08:32:17 -0700 Subject: [OpenStack-Infra] [PTG] Zuul interviews at PTG + still seeking a volunteer to talk infra Message-ID: Per the discussion in last week's Zuul meeting [1] -- I have signed some folks up, in a hopefully-conflicting fashion, to chat about Zuul on camera with Mr. Rich Bowen during the PTG. (One of his previous mails on this topic follows below, for those unfamiliar with what the heck I'm talking about.) This will be lovely content for us to have (a) on the zuul-ci.org page, and (b) to highlight in other places all the great work folks in Infra have been doing. 1: Jim Blair, Jesse Keating -- Fingers crossed, *Monday* at 1:30pm. (Note: Rich isn't officially recording folks on Monday, but is willing to bust out the gear anyway since it's Jesse's only day around. Rich, plz note!) This chat will largely be: What the heck is Zuul, why Ansible, and look, shiny new GitHub integrations that enable not-just-gerrit workflows! 2: Tuesday, 4:30pm: Monty, Ricky, and (hopefully) Tobias. (Tobias: I know you weren't at the irc meeting, but am hoping you're willing to chat on camera :D If not, lmk...) Topic for this one: Why enabling other communities and users with the power of Zuul matters, and look! Examples of folks using it for not-just-openstack! (And I'll be coming along / squirrel herding as well, though not to be on camera. :D) Also: STILL SEEKING a volunteer or two to talk about the other good things Infra is up to. Rich still has spots open, and I will keep poking people until someone volunteers :) I was thinking that a combo of pabelanger + fungi and/or clarkb would be grand (trying to not steal everyone simultaneously and all that jazz.) Feel free to add yourself to the schedule Rich has put together [2]. If folks have questions, or flames / praise for my schedule alignment skills, LMK. Cheers, -robyn [1] http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-02-19-22.01.html [2] https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ ---------- Forwarded message ---------- From: Rich Bowen Date: Mon, Feb 19, 2018 at 7:12 AM Subject: [openstack-dev] [PTG] Project interviews at the PTG To: openstack-dev at lists.openstack.org I promise this is the last time I'll bug you about this. (Except on-site, of course!) I still have lots and lots of space for team/project/whatever interviews at the PTG. You can sign up at https://docs.google.com/spread sheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0 You can see some examples of previous interviews at http://youtube.com/RDOCommunity For the most part, interviews focus on what your team accomplished during the Queens cycle and what you want to work on in Rocky. However, we can also talk about other things like governance, community, related projects, licensing, or anything else that you feel is related to the OpenStack community. I encourage you to talk with your team, and find 2 or 3 people who can speak most eloquently about what you are trying to do, and find a time that works for you. I'll also have the schedules posted on-site, so you can sign up there, if you're still unsure of your schedule. But signing up ahead of time lets me know whether Wednesday is really a vacation day. ;-) See you in Dublin! -- Rich Bowen - rbowen at redhat.com @RDOcommunity // @CentOSProject // @rbowen __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbowen at redhat.com Mon Feb 26 12:53:14 2018 From: rbowen at redhat.com (Rich Bowen) Date: Mon, 26 Feb 2018 12:53:14 +0000 Subject: [OpenStack-Infra] [PTG] Zuul interviews at PTG + still seeking a volunteer to talk infra In-Reply-To: References: Message-ID: <32ad9980-6714-6b56-0d0b-6ff5b0fa1a0c@redhat.com> FYI, Paul Belanger / Clark Boylan have signed up wednesday afternoon for "OpenStack Infrastructure". If anyone wants to do something more specific, I have times available. http://tm3.org/ptgr On 02/25/2018 03:32 PM, Robyn Bergeron wrote: > Also: STILL SEEKING a volunteer or two to talk about the other good > things Infra is up to. Rich still has spots open, and I will keep poking > people until someone volunteers :) I was thinking that a combo of > pabelanger + fungi and/or clarkb would be grand (trying to not steal > everyone simultaneously and all that jazz.) Feel free to add yourself to > the schedule Rich has put together [2]. -- Rich Bowen: Community Architect rbowen at redhat.com @rbowen // @RDOCommunity // @CentOSProject 1 859 351 9166 From pabelanger at redhat.com Mon Feb 26 22:52:18 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Mon, 26 Feb 2018 17:52:18 -0500 Subject: [OpenStack-Infra] Team dinner at Dublin PTG In-Reply-To: <20180219235729.GA13141@localhost.localdomain> References: <20180215201758.GA6252@localhost.localdomain> <20180219235729.GA13141@localhost.localdomain> Message-ID: <20180226225218.GA27289@localhost.localdomain> On Mon, Feb 19, 2018 at 06:57:29PM -0500, Paul Belanger wrote: > On Thu, Feb 15, 2018 at 03:17:58PM -0500, Paul Belanger wrote: > > Greetings, > > > > It is that time again when we all get out from behind our computers and attempt > > to be social for the evening. Talking about great subjects like sportsball and > > favorite beers. > > > > As usually, please indicate which datetime works better for you by adding your > > name and vote to ethercalc[1]. > > > > Right now, we are likely going to end up at a pub for drinks and food, if you > > have a specific place in mind, please reply. I'll do my best to find enough > > room for everybody, however unsure if everybody will sit together at a large > > table. > > > > [1] https://ethercalc.openstack.org/pqhemnrgnz7t > > Just a reminder to please take a moment to add your name to the team dinner > list, so far it looks like we'll meet on Monday or Tuesday night. > > Thanks, > Paul Greetings everybody! Hopefully this isnt' too late in the process, but it does seem Tuesday was the best evening for everybody to meet up. On Sunday I was at Fagan’s Pub, a short walk from The Croke Park hotel for drinks and food, and it seems very Irish like. So, I am proposing after the Official PTG Networking Reception @ 7:30pm we meet in the lobby of the hotel and walk over and obtain drinks and food. I haven't requested any sort of reservations, but if we think that is required. I'm happy to take some time tomorrow morning to confirm we can sit everybody. Thanks again, and hopefully clarkb won't slap me with a trout on IRC. Paul From mrhillsman at gmail.com Mon Feb 26 22:57:58 2018 From: mrhillsman at gmail.com (Melvin Hillsman) Date: Mon, 26 Feb 2018 22:57:58 +0000 Subject: [OpenStack-Infra] Team dinner at Dublin PTG In-Reply-To: <20180226225218.GA27289@localhost.localdomain> References: <20180215201758.GA6252@localhost.localdomain> <20180219235729.GA13141@localhost.localdomain> <20180226225218.GA27289@localhost.localdomain> Message-ID: I think reservation may make sense depending on who all will be attending. Count me in...? :) On Mon, Feb 26, 2018 at 10:52 PM, Paul Belanger wrote: > On Mon, Feb 19, 2018 at 06:57:29PM -0500, Paul Belanger wrote: > > On Thu, Feb 15, 2018 at 03:17:58PM -0500, Paul Belanger wrote: > > > Greetings, > > > > > > It is that time again when we all get out from behind our computers > and attempt > > > to be social for the evening. Talking about great subjects like > sportsball and > > > favorite beers. > > > > > > As usually, please indicate which datetime works better for you by > adding your > > > name and vote to ethercalc[1]. > > > > > > Right now, we are likely going to end up at a pub for drinks and food, > if you > > > have a specific place in mind, please reply. I'll do my best to find > enough > > > room for everybody, however unsure if everybody will sit together at a > large > > > table. > > > > > > [1] https://ethercalc.openstack.org/pqhemnrgnz7t > > > > Just a reminder to please take a moment to add your name to the team > dinner > > list, so far it looks like we'll meet on Monday or Tuesday night. > > > > Thanks, > > Paul > > Greetings everybody! Hopefully this isnt' too late in the process, but it > does > seem Tuesday was the best evening for everybody to meet up. > > On Sunday I was at Fagan’s Pub, a short walk from The Croke Park hotel for > drinks and food, and it seems very Irish like. > > So, I am proposing after the Official PTG Networking Reception @ 7:30pm we > meet > in the lobby of the hotel and walk over and obtain drinks and food. I > haven't > requested any sort of reservations, but if we think that is required. I'm > happy > to take some time tomorrow morning to confirm we can sit everybody. > > Thanks again, and hopefully clarkb won't slap me with a trout on IRC. > > Paul > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > -- Kind regards, Melvin Hillsman mrhillsman at gmail.com mobile: (832) 264-2646 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssbarnea at redhat.com Tue Feb 27 20:33:48 2018 From: ssbarnea at redhat.com (Sorin Sbarnea) Date: Tue, 27 Feb 2018 20:33:48 +0000 Subject: [OpenStack-Infra] extending python-jenkins-core group Message-ID: <5CD43122-6ED5-4160-B1AF-0270D1CFC41A@redhat.com> Hi! I would like to propose extending the list of people with commit access to python-jenkins because that repository needs more attention. As you know this is a key dependency of jenkins-job-builder and sometimes we need to fix bugs (or implement features) in the library. https://review.openstack.org/#/admin/groups/322,members Is seems that the current list of members is not long enough as even few trivial reviews were ignored for long time. I think that adding few others should give the project a boost, all of them already core committers on jenkins-job-builder-core: * Thanh Ha * Sorin Sbarnea (nominating myself, bit lame...) * Wayne Warren (picked based on who performed reviews recently) An alternative would be to add the entire jenkins-job-builder-core group as member of python-jenkins one. Please let me know what you think about this proposal. Thanks Sorin Sbarnea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: