From pabelanger at redhat.com Thu Aug 2 15:00:25 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Thu, 2 Aug 2018 11:00:25 -0400 Subject: [OpenStack-Infra] Reworking zuul base jobs In-Reply-To: <20180723152213.GA5814@localhost.localdomain> References: <20180723152213.GA5814@localhost.localdomain> Message-ID: <20180802150025.GA23485@localhost.localdomain> On Mon, Jul 23, 2018 at 11:22:13AM -0400, Paul Belanger wrote: > Greetings, > > A few weeks ago, I sent an email to the zuul-discuss[1] ML talking about the > idea of splitting a base job in project-config into trusted / untrusted parts. > Since then we've actually implemented the idea in rdoproject.org zuul and seems > to be working very well. > > Basically, I'd like to do the same here with our base job but first wanted to > give a heads up. Here is the basic idea: > > > project-config (trusted) > - job: > name: base-minimal > parent: null > description: top-level job > > - job: > name: base-minimal-test > parent: null > description: top-level job for testing base-minimal > > openstack-zuul-jobs (untrusted) > - job: > name: base > parent: base-minimal > > This then allows us to start moving tasks / roles like configure-mirrors from > trusted into untrusted, since it doesn't really need trusted context on the > executor. > > In rdoproject, our base-minimal job is much smaller then openstack-infra today, > but really has just become used for handling secrets (post-run playbooks) and > zuul_stream (pre). Everything else has been moved into untrusted. > > Here, we likely need to have a little more discussion around what we move into > untrusted from trusted, but once we've done the dance to place base into > openstack-zuul-jobs and parent to base-minimal in project-config, we can start > testing. > > We'd still need to do the base-minimal / base-minimal-test dance for trusted > context, but it should be much smaller the things we need to test. As a working > example, the recent changes to pypi mirrors I believe would have been much > easier to test in this setup. > > - Paul > > [1] http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-July/000508.html I've gone ahead an pushed up a stack of changes at topic:base-minimal-jobs[2]. We need to rename the current base-minimal job to base-ozj first, then depending on how minimal the new base-minimal is, we might be able to remove base-ozj once everything is finished. - Paul [2] https://review.openstack.org/#/q/topic:base-minimal-jobs From aschultz at redhat.com Thu Aug 2 16:57:20 2018 From: aschultz at redhat.com (Alex Schultz) Date: Thu, 2 Aug 2018 10:57:20 -0600 Subject: [OpenStack-Infra] Request to keep Fedora 28 images around until Fedora 30 comes out Message-ID: Ahoy infra folks, So TripleO/RDO is currently working on our transition from python2 to python3 and would like to stabilize on Fedora 28 during the Stein cycle until a newer version of CentOS comes out with proper python3 support. So we would like to ask if it would be possible to keep Fedora 28 around until Fedora 30 comes out + 1 month. This is the published maintenance schedule[0]. Based on current assumptions this would mean that Fedora 28 would be EOL around June, 2019. Ideally our plan would be to migrate off of the Fedora 28 jobs before it is officially EOL. We are aware that release schedules can change and are definitely keeping an eye on that in terms of Fedora. The next release of Fedora 29 is slated to include python 3.7 which may be too new for OpenStack[1] so we would like to start work on the 3.6 that is available from 28. We've already started working on getting packaging working for Fedora 28. Our first goal is to get the various services and deployments working under 3.6. Once that has been tackled, an upgrade to Fedora 29 or newer will likely be less work than trying to go from 2.7 to 3.7. We would like to use fedora 28 rather than something like python3 from EPEL7 in that it would be a better representation of a Red Hat based OS without any python2 support. We're looking to uncover the python 2 to 3 transition issues with TripleO as well as starting to pull in other newer dependencies. Thanks, -Alex [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132179.html From pabelanger at redhat.com Thu Aug 2 17:06:42 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Thu, 2 Aug 2018 13:06:42 -0400 Subject: [OpenStack-Infra] [zuul] Change publication interface to be directories on node, not executor In-Reply-To: References: Message-ID: <20180802170642.GB5070@localhost.localdomain> On Tue, Oct 10, 2017 at 05:42:12PM -0500, Monty Taylor wrote: > Hey everybody! > > I'd like to make a proposal for changing how we do logs/artifacts/docs > collection based on the last few weeks/months of writing things- and of > having to explain to people how to structure build and publish jobs over the > last couple of weeks. > > tl;dr - I'd like to change the publication interface to be directories on > the remote node, not directories on the executor > > Rationale > ========= > > If jobs have to copy files back to the executor as part of the publication > interface, then the zuul admins can't change the mechanism of how artifacts, > logs or docs are published without touching a ton of potentially in-tree job > content. > > Doing so should also allow us to stop having a second copy of build logic in > the artifact release jobs. > > Implementation > ============== > > Define a root 'output' dir on the remote nodes. Different types of output > can be collected by putting them into subdirectories of that dir on the > remote nodes and expecting that base jobs will take care of them. > > People using jobs defined in zuul-jobs should define a variable > "zuul_output_dir", either in site-variables or in their base job. Jobs in > zuul-jobs can and will depend on that variable existing - it will be > considered part of the base job interface zuul-jobs expects. > > Jobs in zuul-jobs will recognize three specific types of job output: > * logs > * artifacts > * docs > > Jobs in zuul-jobs will put job outputs into "{{ zuul_output_dir }}/logs", > "{{ zuul_ouptut_dir }}/artifacts" and "{{ zuul_output_dir }}/docs" as > appropriate. > > A role will be added to zuul-jobs that can be used in base jobs that will > ensure those directories all exist. > > Compression > ----------- > > Deployers may choose to have their base job compress items in {{ > zuul_output_dir }} as part of processing them, or may prefer not to > depending on whether CPU or network is more precious. Jobs in zuul-jobs > should just move/copy things into {{ zuul_output_dir }} on the node and > leave compression, transfer and publication as a base-job operation. > > Easy Output Copying > ------------------- > > A role will also be added to zuul-jobs to facilitate easy/declarative output > copying. > > It will take as input a dictionary of files/folders named > 'zuul_copy_output'. The role will copy contents into {{ zuul_output_dir }} > on the remote node and is intended to be used before output fetching in a > base job's post-playook. > > The input will be a dictionary so that zuul variable merging can be used for > accumulating. > > Keys of the dictionary will be things to copy. Valid values will be the type > of output to copy: > > * logs > * artifacts > * docs > * null # ansible null, not the string null > > null will be used for 'a parent job said to copy this, but this job wants to > not do so' > > The simple content copying role will not be flexible or powerful. People > wanting more expressive output copying have all of the normal tools for > moving files around at their disposal. It will obey the following rules: > > * All files/folders will be copied if they exist, or ignored if they don't > * Items will be copied as-if 'cp -a' had been used. > * Order of files is undefined > * Conflicts between declared files are an error. > > Jobs defined in zuul-jobs should not depend on the {{ zuul_copy_output }} > variable for content they need copied in place on a remote node. Jobs > defined in zuul-jobs should instead copy their output to {{ zuul_output_dir > }} This prevents zuul deployers from being required to put the easy output > copying role into their base jobs. Jobs defined in zuul-jobs may use the > role behind the scenes. > > Filter Plugin > ------------- > > Since the pattern of using a dictionary in job variables to take advantage > of variable merging is bound to come up more than once, we'll define a > filter plugin in zuul called 'zuul_list_from_value' (or some better name) > that will return the list of keys that match a given value. So that given > the following in a job defintion: > > vars: > zuul_copy_output: > foo/bar.html: logs > other/logs/here.html: logs > foo/bar.tgz: artifacts > > Corresponding Ansible could do: > > - copy: > src: {{ item }} > dest: {{ zuul_log_dir }} > with_items: {{ zuul_copy_output | zuul_list_from_value(logs) }} > > For OpenStack Today > =================== > > We will define zuul_output_dir to be "{{ ansible_user_dir }}/zuul-output" in > our site-variables.yaml file. > > Implement the following in OpenStack's base job: > > We will have the base job will include the simple copying role. > > Logs > ---- > > Base job post playbook will always grab {{ zuul_output_dir }}/logs from > nodes, same as today: > * If there are more than one node, grab it into {{ zuul.executor.log_dir > }}/{{ inventory_hostname }}. > * If only one node, grab into {{ zuul.executor.log_dir }} directly > > This will mean moving things like 'fetch-tox-output' logic into the 'tox' > role itself, so after it's run the appropriate tox logs will be copied to {{ > zuul_output_dir }}/logs > > Artifacts and docs > ------------------ > > Base job will always ... > > * Grab {{ zuul_output_dir }}/artifacts and {{ zuul_output_dir }}/docs to {{ > zuul.executor.work_dir }}/artifacts and {{ zuul.executor.work_dir }}/docs > * Publish docs content to logs.openstack.org/{{ zuul_log_path }}/docs - > allows for easy setting of success-url to 'docs/html" in base jobs > regardless of the subdir the job puts docs in to (see docs vs. releasenotes) > * rsync docs content to logs.o.o/{{ zuul_log_path }}/docs after contents of > {{ zuul_output_dir }}/logs so that explicit docs win if there is overlap > * Sign each artifact > * Copy each artifact to {{ zuul.project.short_name }}.{{ zuul.tag }}.{{ > suffix }} OR {{ zuul.project.short_name }}.{{ zuul.branch }}.{{ suffix }} > depending on if {{ zuul.tag exists }} or not > * If {{ zuul.change }} is set, upload artifacts to {{ zuul_log_path > }}/artifacts - to allow people to iterate on artifact upload jobs in check > and verify that they work > * If {{ zuul.change }} is not set, upload artifacts to > tarballs.openstack.org/{{ zuul.project.short_name }, same as today. > Communicate artifact and docs upload paths to child jobs using: > https://review.openstack.org/#/c/504808/ > ++ I've made one small change your current logic, by creating new fetch-zuul-log[2] and fetch-zuul-docs[3] roles. Only because I think it is much easier to read then adding everything into a single fetch-output role. We'd do the same for artifacts, and any new folder a zuul user would create. This also allows an operator the ability to choose which role to also include for their base jobs. [2] https://review.openstack.org/583346/ [3] https://review.openstack.org/583350/ > Artifact Release jobs > ===================== > > The release jobs become similar to v2 release jobs, but can be much more > generalized and reusable. They can also mostly be nodeless jobs (javascript > npm publication is a notable exception - it will need a node) > > Artifacts > --------- > > * Fetch artifacts and signatures from tarballs.openstack.org/{{ > zuul.project.short_name }} - based on values set by parent job > Verify fetched signature is correct > * Upload artifact to appropriate destination(s) (pypi, npm, maven, etc) > > Docs > ---- > > * Rsync docs from logs.openstack.org/{{ zuul_log_path }}/docs - based on > values set by parent job > * Publish to release-job-specific destination as the current jobs do > > This should allow us to make job/project/content specific publication jobs > without needing those jobs to duplicate content in the build jobs. > > It means we can ALSO put jobs like 'publish-to-pypi' in zuul-jobs without > needing a second copy in openstack-zuul-jobs because openstack happens to > builds tarballs differently. The pypi publication step is the same no matter > how the tarball is produced. > > - jobs: > - build-openstack-sphinx-docs > - publish-sphinx-docs-to-afs: > dependencies: > - build-openstack-sphinx-docs > > Rollout > ======= > > The steps should be fairly straightforward (and are fine to do post rollout) > > * Add variable to site-variables > * Add support to base job for creating directories and then copying content > back > * Add easy copy helper role > * Start transitioning jobs in zuul-jobs and openstack-zuul-jobs to using the > new interface - can be done one at a time > * Update usage > > If people are ok with the direction generally, we should be able to get the > enablement pieces in pretty quickly. > > Monty > I'd like to first land our base-minimal[3] (trusted) / base (untrusted) changes then this. But I've already done some testing of new log publishing[4] and works as expected. - Paul [3] https://review.openstack.org/#/q/topic:base-minimal-jobs [4] https://review.openstack.org/584614/ From cboylan at sapwetik.org Thu Aug 2 18:45:34 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 02 Aug 2018 11:45:34 -0700 Subject: [OpenStack-Infra] Request to keep Fedora 28 images around until Fedora 30 comes out In-Reply-To: References: Message-ID: <1533235534.3248134.1461522256.6CC51AB5@webmail.messagingengine.com> On Thu, Aug 2, 2018, at 9:57 AM, Alex Schultz wrote: > Ahoy infra folks, > > So TripleO/RDO is currently working on our transition from python2 to > python3 and would like to stabilize on Fedora 28 during the Stein > cycle until a newer version of CentOS comes out with proper python3 > support. So we would like to ask if it would be possible to keep > Fedora 28 around until Fedora 30 comes out + 1 month. This is the > published maintenance schedule[0]. Based on current assumptions this > would mean that Fedora 28 would be EOL around June, 2019. Ideally our > plan would be to migrate off of the Fedora 28 jobs before it is > officially EOL. > > We are aware that release schedules can change and are definitely > keeping an eye on that in terms of Fedora. The next release of Fedora > 29 is slated to include python 3.7 which may be too new for > OpenStack[1] so we would like to start work on the 3.6 that is > available from 28. We've already started working on getting packaging > working for Fedora 28. Our first goal is to get the various services > and deployments working under 3.6. Once that has been tackled, an > upgrade to Fedora 29 or newer will likely be less work than trying to > go from 2.7 to 3.7. > > We would like to use fedora 28 rather than something like python3 from > EPEL7 in that it would be a better representation of a Red Hat based > OS without any python2 support. We're looking to uncover the python 2 > to 3 transition issues with TripleO as well as starting to pull in > other newer dependencies. > > Thanks, > -Alex > > [0] > https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule > [1] > http://lists.openstack.org/pipermail/openstack-dev/2018-July/132179.html The main reason for wanting to move up the list of Fedora releases quickly was the people supporting the Fedora images didn't want to invest in older releases once they were superseded. If tripleo (or others) are willing to help care for those images and fix them when they break, we should be able to support them through the entirety of their designated lifetime. I do not expect we would keep images around for releases that have reached their end of life. It just isn't practical to try and keep up with security issues, and we should move on. Considering that, I think we can hold off removing Fedora 28 images until that release's EOL date or if they break for a prolonged period of time with no one working to fix it. As a note, Fedora 28 does come with python2.7. It is installed so that Zuul related ansible things can execute under python2 on the test nodes. There is the possibility that ansible's python3 support is working well enough that we could switch to it, but that requires testing and updates to software and images and config. Hope this helps, Clark From aschultz at redhat.com Thu Aug 2 19:04:04 2018 From: aschultz at redhat.com (Alex Schultz) Date: Thu, 2 Aug 2018 13:04:04 -0600 Subject: [OpenStack-Infra] Request to keep Fedora 28 images around until Fedora 30 comes out In-Reply-To: <1533235534.3248134.1461522256.6CC51AB5@webmail.messagingengine.com> References: <1533235534.3248134.1461522256.6CC51AB5@webmail.messagingengine.com> Message-ID: On Thu, Aug 2, 2018 at 12:45 PM, Clark Boylan wrote: > On Thu, Aug 2, 2018, at 9:57 AM, Alex Schultz wrote: >> Ahoy infra folks, >> >> So TripleO/RDO is currently working on our transition from python2 to >> python3 and would like to stabilize on Fedora 28 during the Stein >> cycle until a newer version of CentOS comes out with proper python3 >> support. So we would like to ask if it would be possible to keep >> Fedora 28 around until Fedora 30 comes out + 1 month. This is the >> published maintenance schedule[0]. Based on current assumptions this >> would mean that Fedora 28 would be EOL around June, 2019. Ideally our >> plan would be to migrate off of the Fedora 28 jobs before it is >> officially EOL. >> >> We are aware that release schedules can change and are definitely >> keeping an eye on that in terms of Fedora. The next release of Fedora >> 29 is slated to include python 3.7 which may be too new for >> OpenStack[1] so we would like to start work on the 3.6 that is >> available from 28. We've already started working on getting packaging >> working for Fedora 28. Our first goal is to get the various services >> and deployments working under 3.6. Once that has been tackled, an >> upgrade to Fedora 29 or newer will likely be less work than trying to >> go from 2.7 to 3.7. >> >> We would like to use fedora 28 rather than something like python3 from >> EPEL7 in that it would be a better representation of a Red Hat based >> OS without any python2 support. We're looking to uncover the python 2 >> to 3 transition issues with TripleO as well as starting to pull in >> other newer dependencies. >> >> Thanks, >> -Alex >> >> [0] >> https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule >> [1] >> http://lists.openstack.org/pipermail/openstack-dev/2018-July/132179.html > > The main reason for wanting to move up the list of Fedora releases quickly was the people supporting the Fedora images didn't want to invest in older releases once they were superseded. If tripleo (or others) are willing to help care for those images and fix them when they break, we should be able to support them through the entirety of their designated lifetime. I do not expect we would keep images around for releases that have reached their end of life. It just isn't practical to try and keep up with security issues, and we should move on. > Yes we would assist in addressing breakages as necessary and also agree about not keeping them past EOL. We'll probably end up targeting having some sort of basic gate job during stein so we'll be very aware of breakages. > Considering that, I think we can hold off removing Fedora 28 images until that release's EOL date or if they break for a prolonged period of time with no one working to fix it. > > As a note, Fedora 28 does come with python2.7. It is installed so that Zuul related ansible things can execute under python2 on the test nodes. There is the possibility that ansible's python3 support is working well enough that we could switch to it, but that requires testing and updates to software and images and config. > Hmm ok, we'll have to make sure that doesn't conflict. Good to know. Thanks, -Alex > Hope this helps, > Clark > > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From iwienand at redhat.com Fri Aug 3 04:57:49 2018 From: iwienand at redhat.com (Ian Wienand) Date: Fri, 3 Aug 2018 14:57:49 +1000 Subject: [OpenStack-Infra] Request to keep Fedora 28 images around until Fedora 30 comes out In-Reply-To: <1533235534.3248134.1461522256.6CC51AB5@webmail.messagingengine.com> References: <1533235534.3248134.1461522256.6CC51AB5@webmail.messagingengine.com> Message-ID: <118dc76f-6fbc-8b38-9d2f-8f002481243d@redhat.com> On 08/03/2018 04:45 AM, Clark Boylan wrote: > On Thu, Aug 2, 2018, at 9:57 AM, Alex Schultz wrote: > As a note, Fedora 28 does come with python2.7. It is installed so > that Zuul related ansible things can execute under python2 on the > test nodes. There is the possibility that ansible's python3 support > is working well enough that we could switch to it, but that > requires testing and updates to software and images and config. Python 3 only images are possible -- dib has a whole "dib-python" thing for running python scripts inside the chroot in a distro & version independent way -- but not with the pip-and-virtualenv element setup we do as that drags in both [1]. You can go through a "git log" of that element to see some of the many problems :) OpenStack has always managed to tickle bugs in pip/setuptools/virtualenv which is why we go to the effort of installing the latest out-of-band. This is not to say it couldn't be reconsidered, especially for a distro like Fedora which packages up-to-date packages. But this would definitely be the first port-of-call for anyone interested in going down that path in infra. -i [1] https://git.openstack.org/cgit/openstack/diskimage-builder/tree/diskimage_builder/elements/pip-and-virtualenv/install.d/pip-and-virtualenv-source-install/04-install-pip From mordred at inaugust.com Fri Aug 3 19:16:26 2018 From: mordred at inaugust.com (Monty Taylor) Date: Fri, 3 Aug 2018 14:16:26 -0500 Subject: [OpenStack-Infra] replacing puppetmaster.o.o underway - interim procedures for hiera secrets Message-ID: <0a35cf98-d2ed-b8e5-c8d7-d0056bcd0b5b@inaugust.com> Hey all! (This really only concerns infra-root folks, so feel free to skip otherwise) As part of the update configuration management effort, we have spun up a new host to replace puppetmaster.openstack.org. It is called bridge.openstack.org. It's running Ubuntu Bionic and has Ansible 2.6 installed on Python 3. (how fancy and future-looking is that?) It has been configured using only ansible, so puppet is not even installed on it. The contents of /root on puppetmaster have been synced to /root on brige. The hiera secrets in /etc/puppet/hieradata have been copied to /etc/ansible/hosts. fqdn and group directories have been renamed to host_vars and group_vars. On bridge the 'production' subdirectory has been removed. This means that the data is in both places, but the local git repos holding it have diverged a little bit. Hopefully we'll be able to cut over to running everything from bridge very soon, but in the meantime - if you need to change any secret hiera data, it needs to be done on both hosts. Thanks! Monty From doug at doughellmann.com Mon Aug 6 15:54:35 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 06 Aug 2018 11:54:35 -0400 Subject: [OpenStack-Infra] starting zuul migration for Oslo team repositories Message-ID: <1533570869-sup-4488@lrrr.local> The Zuul project settings for the Oslo repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack-dev/cookiecutter - openstack-dev/oslo-cookiecutter - openstack-dev/pbr - openstack/automaton - openstack/castellan - openstack/debtcollector - openstack/devstack-plugin-amqp1 - openstack/devstack-plugin-kafka - openstack/devstack-plugin-pika - openstack/devstack-plugin-zmq - openstack/futurist - openstack/mox3 - openstack/oslo-specs - openstack/oslo.cache - openstack/oslo.concurrency - openstack/oslo.config - openstack/oslo.context - openstack/oslo.db - openstack/oslo.i18n - openstack/oslo.limit - openstack/oslo.log - openstack/oslo.messaging - openstack/oslo.middleware - openstack/oslo.policy - openstack/oslo.privsep - openstack/oslo.reports - openstack/oslo.rootwrap - openstack/oslo.serialization - openstack/oslo.service - openstack/oslo.tools - openstack/oslo.utils - openstack/oslo.versionedobjects - openstack/oslo.vmware - openstack/oslosphinx - openstack/oslotest - openstack/osprofiler - openstack/sphinx-feature-classification - openstack/stevedore - openstack/taskflow - openstack/tooz From cboylan at sapwetik.org Tue Aug 7 22:40:16 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 07 Aug 2018 15:40:16 -0700 Subject: [OpenStack-Infra] PTG Logistics Message-ID: <1533681616.3837609.1466802984.416E2EBB@webmail.messagingengine.com> Hello everyone, The PTG is just over a month away. Figured now is a good time to start thinking about that event. The Infrastructure team is scheduled to have a room on Wednesday and Thursday [0]. We will also be participating in the Monday and Tuesday "Ask me anything help room". I will be around all week, so if we want to do something ad hoc on Friday I'm happy to do that too. Please update the planning etherpad [1] with ideas of things we should try to work on while in Denver. I just added a couple more thoughts to the config management updates as well. We typically have a team dinner at these events and last time we were in Denver the Lowry Beer Garden worked great [2]. If you are interested in heading to the beer garden with us please indicate interest and availability on this spreadsheet [3]. This location is outdoor so depends on weather, but is large and avoids logistics around covering food and drinks (we will each be on our own, it is counter service). Finally, if we want to do something other than meetings on Friday we could do something a little less serious. Last time we were in Denver some of us went bowling. Looks like Axe throwing and Top Golf may be options too. Or maybe we figure out how to operate a grill at one of the nearby city parks. [0] https://www.openstack.org/ptg/#tab_schedule [1] https://etherpad.openstack.org/p/infra-ptg-denver-2018 [2] https://www.lowrybeergarden.com/ [3] https://ethercalc.openstack.org/fgry72wu42qw Thank you, Clark From doug at doughellmann.com Tue Aug 14 15:27:18 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 14 Aug 2018 11:27:18 -0400 Subject: [OpenStack-Infra] [goal][python3] starting zuul migration for Documentation team repositories Message-ID: <1534260430-sup-6822@lrrr.local> The Zuul project settings for the Documentation repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/constellations - openstack/contributor-guide - openstack/docs-specs - openstack/openstack-doc-tools - openstack/openstack-manuals - openstack/openstackdocstheme - openstack/os-api-ref - openstack/rst2bash - openstack/training-guides - openstack/training-labs - openstack/whereto From doug at doughellmann.com Thu Aug 16 13:28:54 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 16 Aug 2018 09:28:54 -0400 Subject: [OpenStack-Infra] [goal][python3] starting zuul migration for Documentation team repositories In-Reply-To: <1534260430-sup-6822@lrrr.local> References: <1534260430-sup-6822@lrrr.local> Message-ID: <1534426095-sup-7896@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-14 11:27:18 -0400: > The Zuul project settings for the Documentation repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/constellations > - openstack/contributor-guide > - openstack/docs-specs > - openstack/openstack-doc-tools > - openstack/openstack-manuals > - openstack/openstackdocstheme > - openstack/os-api-ref > - openstack/rst2bash > - openstack/training-guides > - openstack/training-labs > - openstack/whereto The Documentation team has merged all of the patches to import the zuul settings into their repository, and we are ready to proceed with removing them from the project-config repo by approving https://review.openstack.org/#/c/591760. Doug From doug at doughellmann.com Thu Aug 16 13:57:03 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 16 Aug 2018 09:57:03 -0400 Subject: [OpenStack-Infra] [goal][python3][ironic] starting ironic team migration Message-ID: <1534427819-sup-7673@lrrr.local> The Zuul project settings for the ironic repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/bifrost - openstack/ironic - openstack/ironic-inspector - openstack/ironic-inspector-specs - openstack/ironic-lib - openstack/ironic-python-agent - openstack/ironic-python-agent-builder - openstack/ironic-specs - openstack/ironic-tempest-plugin - openstack/ironic-ui - openstack/molteniron - openstack/networking-baremetal - openstack/networking-generic-switch - openstack/networking-generic-switch-tempest-plugin - openstack/python-ironic-inspector-client - openstack/python-ironicclient - openstack/sushy - openstack/sushy-tools - openstack/virtualbmc From mordred at inaugust.com Thu Aug 16 23:37:20 2018 From: mordred at inaugust.com (Monty Taylor) Date: Thu, 16 Aug 2018 18:37:20 -0500 Subject: [OpenStack-Infra] Status update on puppetmaster/bridge cutover Message-ID: <8e012f88-3e71-8cfd-566b-18aa2f7ca5cc@inaugust.com> Hey everybody! puppet is no longer being run from puppetmaster - it has been turned off, almost certainly for good. The puppetmaster server is still around while we finish transitioning, but bridge.openstack.org is now the new hotness. We tested running the new ansible base.yaml playbook and the remote puppet stuff several times on various of the trickier servers and all seems to be looking good. However, due to EOD we're not quite finished. SO ... ansible/puppet cronjob is not turned on yet on bridge. This means puppet is not running anywhere and new projects will not get created. We'll finish it up in the morning, but if something happens overnight that needs a puppet run, kick.sh FROM bridge.openstack.org should be fine to run. Thanks! Monty From joshua.hesketh at gmail.com Fri Aug 17 02:08:58 2018 From: joshua.hesketh at gmail.com (Joshua Hesketh) Date: Fri, 17 Aug 2018 12:08:58 +1000 Subject: [OpenStack-Infra] Status update on puppetmaster/bridge cutover In-Reply-To: <8e012f88-3e71-8cfd-566b-18aa2f7ca5cc@inaugust.com> References: <8e012f88-3e71-8cfd-566b-18aa2f7ca5cc@inaugust.com> Message-ID: Yay, awesome work to those involved. Thanks for keeping us informed :-) On Fri, Aug 17, 2018 at 9:38 AM Monty Taylor wrote: > Hey everybody! > > puppet is no longer being run from puppetmaster - it has been turned > off, almost certainly for good. The puppetmaster server is still around > while we finish transitioning, but bridge.openstack.org is now the new > hotness. > > We tested running the new ansible base.yaml playbook and the remote > puppet stuff several times on various of the trickier servers and all > seems to be looking good. However, due to EOD we're not quite finished. > > SO ... > > ansible/puppet cronjob is not turned on yet on bridge. This means puppet > is not running anywhere and new projects will not get created. > > We'll finish it up in the morning, but if something happens overnight > that needs a puppet run, kick.sh FROM bridge.openstack.org should be > fine to run. > > Thanks! > Monty > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 05:24:52 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 14:24:52 +0900 Subject: [OpenStack-Infra] starting zuul migration for vitrage team repositories Message-ID: The Zuul project settings for the vitrage repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-vitrageclient - openstack/vitrage - openstack/vitrage-dashboard - openstack/vitrage-specs - openstack/vitrage-tempest-plugin -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 05:59:18 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 14:59:18 +0900 Subject: [OpenStack-Infra] starting zuul migration for cyborg team repositories Message-ID: The Zuul project settings for the cyborg repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/cyborg - openstack/cyborg-specs - openstack/os-acc - openstack/python-cyborgclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 08:12:29 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 17:12:29 +0900 Subject: [OpenStack-Infra] starting zuul migration for solum team repositories Message-ID: The Zuul project settings for the solum repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-solumclient - openstack/solum - openstack/solum-dashboard - openstack/solum-specs - openstack/solum-tempest-plugin -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 12:19:31 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 21:19:31 +0900 Subject: [OpenStack-Infra] starting zuul migration for tacker team repositories Message-ID: The Zuul project settings for the tacker repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-tackerclient - openstack/tacker - openstack/tacker-horizon - openstack/tacker-specs -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 12:20:23 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 21:20:23 +0900 Subject: [OpenStack-Infra] starting zuul migration for masakari team repositories Message-ID: The Zuul project settings for the masakari repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/masakari - openstack/masakari-dashboard - openstack/masakari-monitors - openstack/masakari-specs - openstack/python-masakariclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 12:20:59 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 21:20:59 +0900 Subject: [OpenStack-Infra] starting zuul migration for congress team repositories Message-ID: The Zuul project settings for the congress repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/congress - openstack/congress-dashboard - openstack/congress-specs - openstack/congress-tempest-plugin - openstack/python-congressclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 17 12:22:30 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 17 Aug 2018 21:22:30 +0900 Subject: [OpenStack-Infra] starting zuul migration for designate team repositories Message-ID: The Zuul project settings for the designate repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/designate - openstack/designate-dashboard - openstack/designate-specs - openstack/designate-tempest-plugin - openstack/python-designateclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Sat Aug 18 06:08:20 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sat, 18 Aug 2018 15:08:20 +0900 Subject: [OpenStack-Infra] starting zuul migration for mistral team repositories Message-ID: The Zuul project settings for the mistral repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/mistral - openstack/mistral-dashboard - openstack/mistral-extra - openstack/mistral-lib - openstack/mistral-specs - openstack/mistral-tempest-plugin - openstack/python-mistralclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From honjo.rikimaru at po.ntt-tx.co.jp Sat Aug 18 07:06:48 2018 From: honjo.rikimaru at po.ntt-tx.co.jp (Rikimaru Honjo) Date: Sat, 18 Aug 2018 16:06:48 +0900 Subject: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page Message-ID: Hello, I have a question about third-party CI. I'm preparing my third-party CI. So I read the following document. https://docs.openstack.org/infra/system-config/third_party.html But, I couldn't understand how to display the result of tests in the upper right of a gerrit page. e.g. I'd like to display the result of tests like IBM PowerKVM CI,INFINIDAT CI... of this page: https://review.openstack.org/#/c/593202/1 Should I add my CI account to -ci group? Best regards, -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikimaru at po.ntt-tx.co.jp From nguyentrihai93 at gmail.com Sat Aug 18 16:09:09 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sun, 19 Aug 2018 01:09:09 +0900 Subject: [OpenStack-Infra] starting zuul migration for watcher team repositories Message-ID: The Zuul project settings for the watcher repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-watcherclient - openstack/watcher - openstack/watcher-dashboard - openstack/watcher-specs - openstack/watcher-tempest-plugin -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcin at koprowski.eu Sun Aug 19 08:46:42 2018 From: marcin at koprowski.eu (Marcin Koprowski) Date: Sun, 19 Aug 2018 10:46:42 +0200 Subject: [OpenStack-Infra] Volunteer Systems Administrator Message-ID: Hello, First of all, allow me to introduce myself. My name is Marcin and I work in Poland as an Infrastructure Analyst. I used to be a Systems Administrator, IT Manager, IT Support Analyst, etc. I have a few years of experience administering Ubuntu Server and a bunch of Open Source applications/services. I don't have any experience with OpenStack, but I'm very keen to learn. The reason why I'm writing here is that I have more than 10 hours per week to spare and I would like to help you out somehow. My interest is Systems Administration and DevOps. Please let me know if you are interested, and if you are, I will provide you with my CV and link to my Linkedin profile. Thank you. Best regards, Marcin -------------- next part -------------- An HTML attachment was scrubbed... URL: From anteaya at anteaya.info Sun Aug 19 13:24:07 2018 From: anteaya at anteaya.info (Anita Kuno) Date: Sun, 19 Aug 2018 09:24:07 -0400 Subject: [OpenStack-Infra] Volunteer Systems Administrator In-Reply-To: References: Message-ID: <84543435-9c85-51a2-1e1d-19b21bde651f@anteaya.info> On 2018-08-19 04:46 AM, Marcin Koprowski wrote: > Hello, > > First of all, allow me to introduce myself. My name is Marcin and I work in > Poland as an Infrastructure Analyst. I used to be a Systems Administrator, > IT Manager, IT Support Analyst, etc. I have a few years of experience > administering Ubuntu Server and a bunch of Open Source > applications/services. > > I don't have any experience with OpenStack, but I'm very keen to learn. > > The reason why I'm writing here is that I have more than 10 hours per week > to spare and I would like to help you out somehow. My interest is Systems > Administration and DevOps. Please let me know if you are interested, and if > you are, I will provide you with my CV and link to my Linkedin profile. > > Thank you. > > Best regards, > > Marcin > Hi Marcin: You are more than welcome to participate, no application process necessary. There are plenty of tasks available for you to help with, the best way to find out which ones and how to learn the systems are by spending time in the infra channel (#openstack-infra on the freenode network, you will need to register your irc nickname to join the channel) and by participating in the weekly infra meeting, #openstack-meeting 19:00 utc on Tuesdays. Root access to servers is granted to those who demonstrate commitment and experience with our systems and the only way to get experience is to participate. Your participation would be appreciated. There is usually someone in the irc channel in most time zones, weekends tend to be quiet. Welcome, Anita From aj at suse.com Sun Aug 19 16:47:33 2018 From: aj at suse.com (Andreas Jaeger) Date: Sun, 19 Aug 2018 18:47:33 +0200 Subject: [OpenStack-Infra] Retiring some repos? Message-ID: I've did a quick scripted check to search for repositories that did not merge a change in the last 12 months and here's the output. I removed gerrit from the list since it's special. So, out of 169 repos in openstack-finra, I list below 33 old repos with the last merge date. Are there any repos in here that we should retire? Which ones are not used anymore? ========================================================================================== Found old openstack-infra/activity-board Last update was 2016-04-14T12:04:56+02:00 ========================================================================================== Found old openstack-infra/askbot-theme Last update was 2015-08-11T18:45:16+02:00 ========================================================================================== Found old openstack-infra/beaker-localhost Last update was 2015-06-30T15:08:25+00:00 ========================================================================================== Found old openstack-infra/beaker-nodepool Last update was 2015-06-30T15:08:34+00:00 ========================================================================================== Found old openstack-infra/bugdaystats Last update was 2016-10-05T16:59:36+00:00 ========================================================================================== Found old openstack-infra/err2d2 Last update was 2016-08-01T13:58:29-07:00 ========================================================================================== Found old openstack-infra/featuretracker Last update was 2017-04-21T16:44:46-04:00 ========================================================================================== Found old openstack-infra/gearman-plugin Last update was 2016-03-21T09:44:28+01:00 ========================================================================================== Found old openstack-infra/germqtt Last update was 2016-09-29T18:31:36-04:00 ========================================================================================== Found old openstack-infra/git-restack Last update was 2016-02-04T00:05:41+00:00 ========================================================================================== Found old openstack-infra/groups-static-pages Last update was 2016-08-18T10:52:48+08:00 ========================================================================================== Found old openstack-infra/js-afs-blob-store Last update was 2016-08-09T14:24:52+02:00 ========================================================================================== Found old openstack-infra/js-generator-openstack Last update was 2016-11-03T13:47:42+08:00 ========================================================================================== Found old openstack-infra/js-openstack-registry-hooks Last update was 2016-08-09T14:30:57+02:00 ========================================================================================== Found old openstack-infra/lodgeit Last update was 2017-02-25T13:51:52+09:00 ========================================================================================== Found old openstack-infra/log_processor Last update was 2015-11-23T15:32:06-08:00 ========================================================================================== Found old openstack-infra/logstash-filters Last update was 2017-05-03T11:33:17-07:00 ========================================================================================== Found old openstack-infra/lpmqtt Last update was 2016-12-21T17:48:47+00:00 ========================================================================================== Found old openstack-infra/meetbot Last update was 2017-02-21T17:57:11+00:00 ========================================================================================== Found old openstack-infra/mqtt_statsd Last update was 2017-04-03T22:59:11-04:00 ========================================================================================== Found old openstack-infra/nose-html-output Last update was 2017-06-22T19:29:16+09:00 ========================================================================================== Found old openstack-infra/openstackweb Last update was 2015-01-07T14:32:46+00:00 ========================================================================================== Found old openstack-infra/project-config-example Last update was 2016-11-29T17:52:14+02:00 ========================================================================================== Found old openstack-infra/puppet-docker_registry Last update was 2016-11-17T19:50:34+00:00 ========================================================================================== Found old openstack-infra/pynotedb Last update was 2017-04-28T20:42:20+00:00 ========================================================================================== Found old openstack-infra/pypi-mirror Last update was 2015-07-15T09:27:21+01:00 ========================================================================================== Found old openstack-infra/releasestatus Last update was 2015-06-30T14:27:24+02:00 ========================================================================================== Found old openstack-infra/reviewstats Last update was 2017-04-19T14:34:43+01:00 ========================================================================================== Found old openstack-infra/trystack-site Last update was 2016-06-15T18:20:23+00:00 ========================================================================================== Found old openstack-infra/vinz Last update was 2014-06-12T20:36:19+00:00 ========================================================================================== Found old openstack-infra/vinz-webclient Last update was 2014-06-12T20:36:45+00:00 ========================================================================================== Found old openstack-infra/zmq-event-publisher Last update was 2016-04-13T17:24:01-07:00 ========================================================================================== Found old openstack-infra/zuul-packaging Last update was 2013-11-12T17:27:02-05:00 ... done A quick search with codesearch suggests that these can be retired since I couldn't find a user: openstack-infra/activity-board openstack-infra/beaker-localhost openstack-infra/beaker-nodepool openstack-infra/err2d2 openstack-infra/featuretracker (together with puppet-featuretracker, not listed above) openstack-infra/js-afs-blob-store openstack-infra/js-generator-openstack openstack-infra/js-openstack-registry-hooks openstack-infra/nose-html-output openstack-infra/openstackweb openstack-infra/puppet-docker_registry openstack-infra/project-config-example openstack-infra/pynotedb openstack-infra/pypi-mirror openstack-infra/releasestatus (together with puppet-releasestatus, not listed above) openstack-infra/trystack-site openstack-infra/vinz openstack-infra/vinz-webclient openstack-infra/zuul-packaging That's 21 repositories. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Sun Aug 19 16:59:02 2018 From: aj at suse.com (Andreas Jaeger) Date: Sun, 19 Aug 2018 18:59:02 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: References: Message-ID: <8feb9113-54fd-3115-6341-425d199aeb26@suse.com> Just for the curious ones, of the 1453 repos that I have checked out on my system, 447 have not seen a change in the last 12 months. Largest group is fuel with 149 repos. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Sun Aug 19 19:41:05 2018 From: aj at suse.com (Andreas Jaeger) Date: Sun, 19 Aug 2018 21:41:05 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: References: Message-ID: One more infra deliverable that looks unused: Found old openstack-dev/openstack-nose Last update was 2015-05-20T15:27:36-04:00 Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From amotoki at gmail.com Sun Aug 19 21:04:56 2018 From: amotoki at gmail.com (Akihiro Motoki) Date: Mon, 20 Aug 2018 06:04:56 +0900 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: References: Message-ID: Comments on nose related projects : nose-html-output and openstack-nose I am not sure that no update means non-used. > A quick search with codesearch suggests that these can be retired since > I couldn't find a user: [...] > openstack-infra/nose-html-output You need to search by 'nosehtmloutput'. http://codesearch.openstack.org/?q=nosehtmloutput&i=nope&files=&repos= This is used mainly by horizon plugins and swift related projects. Regarding horizon plugins, horizon no longer depends on nose and nose usage in official (TC governed) horizon plugin projects is now being clean up in https://review.openstack.org/#/q/topic:django-test-runner+(status:open+OR+status:merged) Non-official horizon plugins are not covered by my patch series as I don't know the activiness of them. After horizon plugin cleanup, the only users will be swift related projects and stx-clients. > Found old openstack-dev/openstack-nose > Last update was 2015-05-20T15:27:36-04:00 You need search this by "openstack.nose-plugin" in the codesearch. This is mainly used by horizon plugins, but the usage will be cleanup soon or later as nose is no longer a dependency in horizon tests as mentioned above. The other users are trove, python-zaqarclient, and stx-clients. Thanks, Akihiro Motoki (amotoki) 2018年8月20日(月) 1:48 Andreas Jaeger : > > I've did a quick scripted check to search for repositories that did not > merge a change in the last 12 months and here's the output. > > I removed gerrit from the list since it's special. > > So, out of 169 repos in openstack-finra, I list below 33 old repos with > the last merge date. > > Are there any repos in here that we should retire? Which ones are not > used anymore? > > ========================================================================================== > Found old openstack-infra/activity-board > Last update was 2016-04-14T12:04:56+02:00 > ========================================================================================== > Found old openstack-infra/askbot-theme > Last update was 2015-08-11T18:45:16+02:00 > ========================================================================================== > Found old openstack-infra/beaker-localhost > Last update was 2015-06-30T15:08:25+00:00 > ========================================================================================== > Found old openstack-infra/beaker-nodepool > Last update was 2015-06-30T15:08:34+00:00 > ========================================================================================== > Found old openstack-infra/bugdaystats > Last update was 2016-10-05T16:59:36+00:00 > ========================================================================================== > Found old openstack-infra/err2d2 > Last update was 2016-08-01T13:58:29-07:00 > ========================================================================================== > Found old openstack-infra/featuretracker > Last update was 2017-04-21T16:44:46-04:00 > ========================================================================================== > Found old openstack-infra/gearman-plugin > Last update was 2016-03-21T09:44:28+01:00 > ========================================================================================== > Found old openstack-infra/germqtt > Last update was 2016-09-29T18:31:36-04:00 > ========================================================================================== > Found old openstack-infra/git-restack > Last update was 2016-02-04T00:05:41+00:00 > ========================================================================================== > Found old openstack-infra/groups-static-pages > Last update was 2016-08-18T10:52:48+08:00 > ========================================================================================== > Found old openstack-infra/js-afs-blob-store > Last update was 2016-08-09T14:24:52+02:00 > ========================================================================================== > Found old openstack-infra/js-generator-openstack > Last update was 2016-11-03T13:47:42+08:00 > ========================================================================================== > Found old openstack-infra/js-openstack-registry-hooks > Last update was 2016-08-09T14:30:57+02:00 > ========================================================================================== > Found old openstack-infra/lodgeit > Last update was 2017-02-25T13:51:52+09:00 > ========================================================================================== > Found old openstack-infra/log_processor > Last update was 2015-11-23T15:32:06-08:00 > ========================================================================================== > Found old openstack-infra/logstash-filters > Last update was 2017-05-03T11:33:17-07:00 > ========================================================================================== > Found old openstack-infra/lpmqtt > Last update was 2016-12-21T17:48:47+00:00 > ========================================================================================== > Found old openstack-infra/meetbot > Last update was 2017-02-21T17:57:11+00:00 > ========================================================================================== > Found old openstack-infra/mqtt_statsd > Last update was 2017-04-03T22:59:11-04:00 > ========================================================================================== > Found old openstack-infra/nose-html-output > Last update was 2017-06-22T19:29:16+09:00 > ========================================================================================== > Found old openstack-infra/openstackweb > Last update was 2015-01-07T14:32:46+00:00 > ========================================================================================== > Found old openstack-infra/project-config-example > Last update was 2016-11-29T17:52:14+02:00 > ========================================================================================== > Found old openstack-infra/puppet-docker_registry > Last update was 2016-11-17T19:50:34+00:00 > ========================================================================================== > Found old openstack-infra/pynotedb > Last update was 2017-04-28T20:42:20+00:00 > ========================================================================================== > Found old openstack-infra/pypi-mirror > Last update was 2015-07-15T09:27:21+01:00 > ========================================================================================== > Found old openstack-infra/releasestatus > Last update was 2015-06-30T14:27:24+02:00 > ========================================================================================== > Found old openstack-infra/reviewstats > Last update was 2017-04-19T14:34:43+01:00 > ========================================================================================== > Found old openstack-infra/trystack-site > Last update was 2016-06-15T18:20:23+00:00 > ========================================================================================== > Found old openstack-infra/vinz > Last update was 2014-06-12T20:36:19+00:00 > ========================================================================================== > Found old openstack-infra/vinz-webclient > Last update was 2014-06-12T20:36:45+00:00 > ========================================================================================== > Found old openstack-infra/zmq-event-publisher > Last update was 2016-04-13T17:24:01-07:00 > ========================================================================================== > Found old openstack-infra/zuul-packaging > Last update was 2013-11-12T17:27:02-05:00 > ... done > > A quick search with codesearch suggests that these can be retired since > I couldn't find a user: > > openstack-infra/activity-board > openstack-infra/beaker-localhost > openstack-infra/beaker-nodepool > openstack-infra/err2d2 > openstack-infra/featuretracker (together with puppet-featuretracker, not > listed above) > openstack-infra/js-afs-blob-store > openstack-infra/js-generator-openstack > openstack-infra/js-openstack-registry-hooks > openstack-infra/nose-html-output > openstack-infra/openstackweb > openstack-infra/puppet-docker_registry > openstack-infra/project-config-example > openstack-infra/pynotedb > openstack-infra/pypi-mirror > openstack-infra/releasestatus (together with puppet-releasestatus, not > listed above) > openstack-infra/trystack-site > openstack-infra/vinz > openstack-infra/vinz-webclient > openstack-infra/zuul-packaging > > That's 21 repositories. > > Andreas > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From aj at suse.com Mon Aug 20 04:21:25 2018 From: aj at suse.com (Andreas Jaeger) Date: Mon, 20 Aug 2018 06:21:25 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: References: Message-ID: On 2018-08-19 23:04, Akihiro Motoki wrote: > Comments on nose related projects : nose-html-output and openstack-nose > I am not sure that no update means non-used. Thanks for your insight and comments - so, yes, those two need to stay around, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From nguyentrihai93 at gmail.com Mon Aug 20 06:47:07 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Mon, 20 Aug 2018 15:47:07 +0900 Subject: [OpenStack-Infra] starting zuul migration for glance team repositories Message-ID: The Zuul project settings for the glance repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/glance - openstack/glance-specs - openstack/glance_store - openstack/python-glanceclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From adolfo.duarte at suse.com Fri Aug 17 20:46:54 2018 From: adolfo.duarte at suse.com (Adolfo Duarte) Date: Fri, 17 Aug 2018 13:46:54 -0700 Subject: [OpenStack-Infra] Delete mispelled branch from openstack/networking-vsphere please Message-ID: <01a101d4366b$6f212230$4d636690$@suse.com> Hi openstack-infra team, Could you plese delete the branch "stable/queen" from the openstack/networking-vsphere (https://review.openstack.org/#/admin/projects/openstack/networking-vsphere) It was a typo, missing "s". I already created a new one called "stable/queens" but its best to remove the "stable/queen" one to not confuse folks. Thanks a million Adolfo Duarte -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Mon Aug 20 14:58:33 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 20 Aug 2018 10:58:33 -0400 Subject: [OpenStack-Infra] [requirements][goal][python3] starting requirements repo zuul settings migration Message-ID: <1534777090-sup-6135@lrrr.local> The migration of Zuul project settings for the requirements repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/requirements Doug From doug at doughellmann.com Mon Aug 20 17:22:26 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 20 Aug 2018 13:22:26 -0400 Subject: [OpenStack-Infra] [tc][goal][python3][election] starting migration of zuul settings for TC repos Message-ID: <1534785720-sup-4416@lrrr.local> The migration of Zuul project settings for the Technical Committee repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/api-wg - openstack/election - openstack/goal-tools - openstack/governance - openstack/openstack-specs - openstack/project-navigator-data - openstack/project-team-guide - openstack/service-types-authority From doug at doughellmann.com Mon Aug 20 20:36:21 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 20 Aug 2018 16:36:21 -0400 Subject: [OpenStack-Infra] [sahara][goal][python3] beginning zuul migration for sahara Message-ID: <1534797377-sup-9523@lrrr.local> The migration of Zuul project settings for the sahara repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-saharaclient - openstack/sahara - openstack/sahara-dashboard - openstack/sahara-extra - openstack/sahara-image-elements - openstack/sahara-specs - openstack/sahara-tests From gouthampravi at gmail.com Mon Aug 20 20:48:26 2018 From: gouthampravi at gmail.com (Goutham Pacha Ravi) Date: Mon, 20 Aug 2018 13:48:26 -0700 Subject: [OpenStack-Infra] starting zuul migration for manila team repositories Message-ID: The migration of Zuul project settings for the manila repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/manila - openstack/manila-image-elements - openstack/manila-specs - openstack/manila-tempest-plugin - openstack/manila-test-image - openstack/manila-ui - openstack/python-manilaclient A WIP change for project-config is at [1]. Will remove the W-1 on that once all of [2] changes have merged. -- Goutham Pacha Ravi [1] https://review.openstack.org/#/c/593898/ [2] https://review.openstack.org/#/q/topic:python3-first+project:%22%255E(openstack/manila.*%257Copenstack/python-manilaclient)%22 From doug at doughellmann.com Mon Aug 20 21:02:39 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 20 Aug 2018 17:02:39 -0400 Subject: [OpenStack-Infra] [sig][goal][python3] starting zuul migration for SIG repos Message-ID: <1534798936-sup-7767@lrrr.local> The migration of Zuul project settings for the SIG repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/governance-sigs - openstack/anchor - openstack/ossa - openstack/security-analysis - openstack/security-doc - openstack/security-specs - openstack/syntribos - openstack/syntribos-openstack-templates - openstack/syntribos-payloads - openstack/self-healing-sig - openstack/operations-guide - openstack/api-sig From nguyentrihai93 at gmail.com Tue Aug 21 05:04:24 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Tue, 21 Aug 2018 14:04:24 +0900 Subject: [OpenStack-Infra] starting zuul migration for vitrage team repositories In-Reply-To: References: Message-ID: All the patched related to Zuul job settings in vitrage are merged. Please process this patch. https://review.openstack.org/#/c/592828/ Thank you. On Fri, Aug 17, 2018 at 2:24 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the vitrage repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-vitrageclient > - openstack/vitrage > - openstack/vitrage-dashboard > - openstack/vitrage-specs > - openstack/vitrage-tempest-plugin > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Tue Aug 21 05:56:59 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Tue, 21 Aug 2018 14:56:59 +0900 Subject: [OpenStack-Infra] [searchlight][goal][python3] beginning zuul migration for searchlight Message-ID: The Zuul project settings for the searchlight repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-searchlightclient - openstack/searchlight - openstack/searchlight-specs - openstack/searchlight-ui Nguyen Hai -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Tue Aug 21 08:28:05 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Tue, 21 Aug 2018 17:28:05 +0900 Subject: [OpenStack-Infra] [horizon][goal][python3] beginning zuul migration for horizon Message-ID: The Zuul project settings for the horizon repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/django_openstack_auth - openstack/horizon - openstack/tempest-horizon -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Tue Aug 21 15:21:49 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 21 Aug 2018 11:21:49 -0400 Subject: [OpenStack-Infra] [sahara][goal][python3] beginning zuul migration for sahara In-Reply-To: <1534797377-sup-9523@lrrr.local> References: <1534797377-sup-9523@lrrr.local> Message-ID: <1534864887-sup-3424@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-20 16:36:21 -0400: > The migration of Zuul project settings for the > sahara repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/python-saharaclient > - openstack/sahara > - openstack/sahara-dashboard > - openstack/sahara-extra > - openstack/sahara-image-elements > - openstack/sahara-specs > - openstack/sahara-tests The import patches have been approved and we are ready to proceed with approving the cleanup patch: https://review.openstack.org/#/c/593938/ From mihailmed at gmail.com Tue Aug 21 17:20:33 2018 From: mihailmed at gmail.com (Mikhail Medvedev) Date: Tue, 21 Aug 2018 12:20:33 -0500 Subject: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page In-Reply-To: References: Message-ID: On Sat, Aug 18, 2018 at 2:06 AM, Rikimaru Honjo wrote: > > Hello, > > I have a question about third-party CI. > > I'm preparing my third-party CI. So I read the following document. > > https://docs.openstack.org/infra/system-config/third_party.html > > But, I couldn't understand how to display the result of tests in the > upper right of a gerrit page. Hi, The table on the gerrit page is created by the script: https://github.com/openstack-infra/system-config/blob/d148f5f8efe9b66329600b445e9a6f4f46223896/modules/openstack_project/files/gerrit/hideci.js . It parses all the comments posted on a patch to generate the list. For your third-party CI to be listed on that table it should post a comment adhering to a certain format. Press the "Toggle CI" to see other CI comments for examples of formatting. > > e.g. > I'd like to display the result of tests like IBM PowerKVM CI,INFINIDAT CI... > of this page: > https://review.openstack.org/#/c/593202/1 > > Should I add my CI account to -ci group? For your CI to be able to post a comment and to be added to the table it does not have to be added to -ci group. You only need to add your CI to -ci group to vote +/-1 Verified on the project's changes. The Verified vote would show up at the top, e.g. "Verified +1 Zuul". What is the name of the third-party CI you are setting up? I can add it to the email filter list https://review.openstack.org/#/admin/groups/270 > > Best regards, > -- > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > Rikimaru Honjo > E-mail:honjo.rikimaru at po.ntt-tx.co.jp > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Mikhail Medvedev IBM From fungi at yuggoth.org Tue Aug 21 18:33:06 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 21 Aug 2018 18:33:06 +0000 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming Message-ID: <20180821183306.yy72bamjfhttxnec@yuggoth.org> The Infra team has been brainstorming and collecting feedback in https://etherpad.openstack.org/p/infra-services-naming as to what actual name/domain the Winterscale effort will use. If you've not been following along, the earlier discussions can be found in the following mailing list threads: http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html So far the "short list" at the bottom of the pad seems to contain only one entry: OpenDev. The OpenStack Foundation has offered to let us take control of opendev.org for this purpose if we would like. They have it mainly as a defensive registration to protect the OpenDev Conference brand, but use a separate opendevconf.org domain for that at present. The opendev.org domain is just sitting parked on the same nameservers as openstack.org right now, not in use for anything. The brand itself has a positive connotation in the community so far, and the OpenDev Conferences share a lot of similar goals (bringing communities of people together to collaborate openly on design and development activities) so this even provides some useful synergy around the name and possible promotional tie-ins with the events if we like. I know lots of us are eager to move forward on the rebranding, so I wanted to wake this discussion back up and try to see if we can drive it to a conclusion. As we continue to take on hosting for additional large projects, having somewhere for them to send the contributors and users in their community which has a distinct identity unclouded by OpenStack itself will help make our services much more welcoming. If you don't particularly like the OpenDev idea or have alternatives you think might achieve greater consensus within our team and present a better image to our extended community, present and future, please update the above mentioned pad or follow up to this mailing list thread. Thanks! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From mnaser at vexxhost.com Tue Aug 21 19:38:42 2018 From: mnaser at vexxhost.com (Mohammed Naser) Date: Tue, 21 Aug 2018 15:38:42 -0400 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <20180821183306.yy72bamjfhttxnec@yuggoth.org> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> Message-ID: It's a +1 for me, I really like the name. On Tue, Aug 21, 2018 at 2:33 PM, Jeremy Stanley wrote: > The Infra team has been brainstorming and collecting feedback in > https://etherpad.openstack.org/p/infra-services-naming as to what > actual name/domain the Winterscale effort will use. If you've not > been following along, the earlier discussions can be found in the > following mailing list threads: > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > So far the "short list" at the bottom of the pad seems to contain > only one entry: OpenDev. > > The OpenStack Foundation has offered to let us take control of > opendev.org for this purpose if we would like. They have it mainly > as a defensive registration to protect the OpenDev Conference brand, > but use a separate opendevconf.org domain for that at present. The > opendev.org domain is just sitting parked on the same nameservers as > openstack.org right now, not in use for anything. The brand itself > has a positive connotation in the community so far, and the OpenDev > Conferences share a lot of similar goals (bringing communities of > people together to collaborate openly on design and development > activities) so this even provides some useful synergy around the > name and possible promotional tie-ins with the events if we like. > > I know lots of us are eager to move forward on the rebranding, so I > wanted to wake this discussion back up and try to see if we can > drive it to a conclusion. As we continue to take on hosting for > additional large projects, having somewhere for them to send the > contributors and users in their community which has a distinct > identity unclouded by OpenStack itself will help make our services > much more welcoming. If you don't particularly like the OpenDev idea > or have alternatives you think might achieve greater consensus > within our team and present a better image to our extended > community, present and future, please update the above mentioned pad > or follow up to this mailing list thread. Thanks! > -- > Jeremy Stanley > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser at vexxhost.com W. http://vexxhost.com From mordred at inaugust.com Tue Aug 21 20:14:47 2018 From: mordred at inaugust.com (Monty Taylor) Date: Tue, 21 Aug 2018 15:14:47 -0500 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <20180821183306.yy72bamjfhttxnec@yuggoth.org> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> Message-ID: On 08/21/2018 01:33 PM, Jeremy Stanley wrote: > The Infra team has been brainstorming and collecting feedback in > https://etherpad.openstack.org/p/infra-services-naming as to what > actual name/domain the Winterscale effort will use. If you've not > been following along, the earlier discussions can be found in the > following mailing list threads: > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > So far the "short list" at the bottom of the pad seems to contain > only one entry: OpenDev. > > The OpenStack Foundation has offered to let us take control of > opendev.org for this purpose if we would like. They have it mainly > as a defensive registration to protect the OpenDev Conference brand, > but use a separate opendevconf.org domain for that at present. The > opendev.org domain is just sitting parked on the same nameservers as > openstack.org right now, not in use for anything. The brand itself > has a positive connotation in the community so far, and the OpenDev > Conferences share a lot of similar goals (bringing communities of > people together to collaborate openly on design and development > activities) so this even provides some useful synergy around the > name and possible promotional tie-ins with the events if we like. > > I know lots of us are eager to move forward on the rebranding, so I > wanted to wake this discussion back up and try to see if we can > drive it to a conclusion. As we continue to take on hosting for > additional large projects, having somewhere for them to send the > contributors and users in their community which has a distinct > identity unclouded by OpenStack itself will help make our services > much more welcoming. If you don't particularly like the OpenDev idea > or have alternatives you think might achieve greater consensus > within our team and present a better image to our extended > community, present and future, please update the above mentioned pad > or follow up to this mailing list thread. Thanks! ++ to OpenDev From pabelanger at redhat.com Tue Aug 21 20:25:55 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Tue, 21 Aug 2018 16:25:55 -0400 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <20180821183306.yy72bamjfhttxnec@yuggoth.org> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> Message-ID: <20180821202555.GA6383@localhost.localdomain> On Tue, Aug 21, 2018 at 06:33:06PM +0000, Jeremy Stanley wrote: > The Infra team has been brainstorming and collecting feedback in > https://etherpad.openstack.org/p/infra-services-naming as to what > actual name/domain the Winterscale effort will use. If you've not > been following along, the earlier discussions can be found in the > following mailing list threads: > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > So far the "short list" at the bottom of the pad seems to contain > only one entry: OpenDev. > > The OpenStack Foundation has offered to let us take control of > opendev.org for this purpose if we would like. They have it mainly > as a defensive registration to protect the OpenDev Conference brand, > but use a separate opendevconf.org domain for that at present. The > opendev.org domain is just sitting parked on the same nameservers as > openstack.org right now, not in use for anything. The brand itself > has a positive connotation in the community so far, and the OpenDev > Conferences share a lot of similar goals (bringing communities of > people together to collaborate openly on design and development > activities) so this even provides some useful synergy around the > name and possible promotional tie-ins with the events if we like. > > I know lots of us are eager to move forward on the rebranding, so I > wanted to wake this discussion back up and try to see if we can > drive it to a conclusion. As we continue to take on hosting for > additional large projects, having somewhere for them to send the > contributors and users in their community which has a distinct > identity unclouded by OpenStack itself will help make our services > much more welcoming. If you don't particularly like the OpenDev idea > or have alternatives you think might achieve greater consensus > within our team and present a better image to our extended > community, present and future, please update the above mentioned pad > or follow up to this mailing list thread. Thanks! > -- > Jeremy Stanley > +1 Exciting! - Paul From honjo.rikimaru at po.ntt-tx.co.jp Wed Aug 22 05:50:44 2018 From: honjo.rikimaru at po.ntt-tx.co.jp (Rikimaru Honjo) Date: Wed, 22 Aug 2018 14:50:44 +0900 Subject: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page In-Reply-To: References: Message-ID: <8f0fb4ab-2306-283f-6418-57e6c9d8e3ed@po.ntt-tx.co.jp> Hi Mikhail, Thank you for replying! On 2018/08/22 2:20, Mikhail Medvedev wrote: > On Sat, Aug 18, 2018 at 2:06 AM, Rikimaru Honjo > wrote: >> >> Hello, >> >> I have a question about third-party CI. >> >> I'm preparing my third-party CI. So I read the following document. >> >> https://docs.openstack.org/infra/system-config/third_party.html >> >> But, I couldn't understand how to display the result of tests in the >> upper right of a gerrit page. > > Hi, > > The table on the gerrit page is created by the script: > https://github.com/openstack-infra/system-config/blob/d148f5f8efe9b66329600b445e9a6f4f46223896/modules/openstack_project/files/gerrit/hideci.js > . It parses all the comments posted on a patch to generate the list. > For your third-party CI to be listed on that table it should post a > comment adhering to a certain format. Press the "Toggle CI" to see > other CI comments for examples of formatting. I got it. I confirm the comment format of my CI. > >> >> e.g. >> I'd like to display the result of tests like IBM PowerKVM CI,INFINIDAT CI... >> of this page: >> https://review.openstack.org/#/c/593202/1 >> >> Should I add my CI account to -ci group? > > For your CI to be able to post a comment and to be added to the table > it does not have to be added to -ci group. You only need to > add your CI to -ci group to vote +/-1 Verified on the > project's changes. The Verified vote would show up at the top, e.g. > "Verified +1 Zuul". > > What is the name of the third-party CI you are setting up? I can add > it to the email filter list > https://review.openstack.org/#/admin/groups/270 My third-party CI is "Networking-spp Integration CI". This is the wiki page about it. https://wiki.openstack.org/wiki/ThirdPartySystems/Networking-spp_Integration_CI >> >> Best regards, >> -- >> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ >> Rikimaru Honjo >> E-mail:honjo.rikimaru at po.ntt-tx.co.jp >> >> >> _______________________________________________ >> OpenStack-Infra mailing list >> OpenStack-Infra at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > -- > Mikhail Medvedev > IBM > -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikimaru at po.ntt-tx.co.jp From nguyentrihai93 at gmail.com Wed Aug 22 06:20:13 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 22 Aug 2018 15:20:13 +0900 Subject: [OpenStack-Infra] [karbor][goal][python3] beginning zuul migration for karbor Message-ID: The Zuul project settings for the karbor repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/karbor - openstack/karbor-dashboard - openstack/python-karborclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Wed Aug 22 13:09:39 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 22 Aug 2018 09:09:39 -0400 Subject: [OpenStack-Infra] [kuryr][goal][python3] starting zuul migration for kuryr Message-ID: <1534943375-sup-3843@lrrr.local> The migration of Zuul project settings for the kuryr repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/fuxi - openstack/fuxi-golang - openstack/fuxi-kubernetes - openstack/kuryr - openstack/kuryr-kubernetes - openstack/kuryr-libnetwork - openstack/kuryr-tempest-plugin From doug at doughellmann.com Wed Aug 22 13:30:21 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 22 Aug 2018 09:30:21 -0400 Subject: [OpenStack-Infra] [powervmstackers][goal][python3] starting zuul migration for powervmstackers Message-ID: <1534944617-sup-3890@lrrr.local> The migration of Zuul project settings for the PowerVMStackers repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/ceilometer-powervm - openstack/networking-powervm - openstack/nova-powervm From nguyentrihai93 at gmail.com Wed Aug 22 15:24:45 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 23 Aug 2018 00:24:45 +0900 Subject: [OpenStack-Infra] [zun][goal][python3] starting zuul migration for zun Message-ID: The Zuul project settings for the zun repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-zunclient - openstack/zun - openstack/zun-tempest-plugin - openstack/zun-ui -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Aug 22 16:26:14 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 22 Aug 2018 16:26:14 +0000 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: References: Message-ID: <20180822162614.sm5nedavyslanmug@yuggoth.org> On 2018-08-22 08:53:26 -0700 (-0700), David van der Bokke wrote: > We are curious about when the next version of git-review will be tagged so > that we can create a debian package release for it. Specifically we want > to pick up the change in > https://git.openstack.org/cgit/openstack-infra/git-review/commit/?id=694f532ca803882d7b3446c31f5fc690e9669042 > before refs/publish is completely removed. I've redirected this to the openstack-infra at lists.openstack.org mailing list where it's more on topic; please continue corresponding there instead and drop openstack at lists.openstack.org from any further replies. Have the Gerrit maintainers indicated what version will drop support for the refs/publish path? Or is the urgency more about silencing the deprecation warning? Looking at the currently merged commits since 1.26.0, I see some which are feature additions so we're likely talking about tagging this as 1.27.0 rather than 1.26.1 (depending on whether dropping the vestigial -c command line option counts as a reason to make it 2.0.0 instead, but I feel like it's probably not warranted). Are there other outstanding changes which are important to get into 1.27.0? At a minimum I think we'll want to get https://review.openstack.org/593670 and its parent change merged so that the release note about -c going away will be included in the release. Anything else? -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From bokke at google.com Wed Aug 22 17:11:20 2018 From: bokke at google.com (David van der Bokke) Date: Wed, 22 Aug 2018 10:11:20 -0700 Subject: [OpenStack-Infra] git-review tagging schedule Message-ID: Thanks Jeremy. I am trying to get an exact date from the Gerrit team, but I can say that tagging/releasing a new git-review is a likely precursor given that the team had actually removed the ref and subsequently reverted the change after discovering that git-review needed an update for it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Aug 22 18:18:56 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 22 Aug 2018 18:18:56 +0000 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: References: Message-ID: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> On 2018-08-22 10:11:20 -0700 (-0700), David van der Bokke wrote: > Thanks Jeremy. I am trying to get an exact date from the Gerrit > team, but I can say that tagging/releasing a new git-review is a > likely precursor given that the team had actually removed the ref > and subsequently reverted the change after discovering that > git-review needed an update for it. Thanks! That definitely helps. When they added it in Gerrit 2.3 the release notes[*] indicated refs/for was deprecated, so the update proposed to git-review to switch back was really the first we'd heard of it being un-deprecated again (I'm not finding a similar release note about it, and the ACLs release note in 2.16 about refs/for still talks about people using refs/publish too). [*] https://gerrit.googlesource.com/gerrit/+/v2.15.3/ReleaseNotes/ReleaseNotes-2.3.txt#21 -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From mihailmed at gmail.com Wed Aug 22 19:05:52 2018 From: mihailmed at gmail.com (Mikhail Medvedev) Date: Wed, 22 Aug 2018 14:05:52 -0500 Subject: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page In-Reply-To: <8f0fb4ab-2306-283f-6418-57e6c9d8e3ed@po.ntt-tx.co.jp> References: <8f0fb4ab-2306-283f-6418-57e6c9d8e3ed@po.ntt-tx.co.jp> Message-ID: On Wed, Aug 22, 2018 at 12:50 AM, Rikimaru Honjo wrote: > Hi Mikhail, > > Thank you for replying! > > On 2018/08/22 2:20, Mikhail Medvedev wrote: >> >> On Sat, Aug 18, 2018 at 2:06 AM, Rikimaru Honjo >> wrote: >>> >>> >>> Hello, >>> >>> I have a question about third-party CI. >>> >>> I'm preparing my third-party CI. So I read the following document. >>> >>> https://docs.openstack.org/infra/system-config/third_party.html >>> >>> But, I couldn't understand how to display the result of tests in the >>> upper right of a gerrit page. >> >> >> Hi, >> >> The table on the gerrit page is created by the script: >> >> https://github.com/openstack-infra/system-config/blob/d148f5f8efe9b66329600b445e9a6f4f46223896/modules/openstack_project/files/gerrit/hideci.js >> . It parses all the comments posted on a patch to generate the list. >> For your third-party CI to be listed on that table it should post a >> comment adhering to a certain format. Press the "Toggle CI" to see >> other CI comments for examples of formatting. > > I got it. > I confirm the comment format of my CI. > >> >>> >>> e.g. >>> I'd like to display the result of tests like IBM PowerKVM CI,INFINIDAT >>> CI... >>> of this page: >>> https://review.openstack.org/#/c/593202/1 >>> >>> Should I add my CI account to -ci group? >> >> >> For your CI to be able to post a comment and to be added to the table >> it does not have to be added to -ci group. You only need to >> add your CI to -ci group to vote +/-1 Verified on the >> project's changes. The Verified vote would show up at the top, e.g. >> "Verified +1 Zuul". >> >> What is the name of the third-party CI you are setting up? I can add >> it to the email filter list >> https://review.openstack.org/#/admin/groups/270 > > My third-party CI is "Networking-spp Integration CI". > This is the wiki page about it. > https://wiki.openstack.org/wiki/ThirdPartySystems/Networking-spp_Integration_CI > Thanks Rikimaru, I've added networking-spp-integration-ci to the mail filter list. > >>> >>> Best regards, >>> -- >>> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ >>> Rikimaru Honjo >>> E-mail:honjo.rikimaru at po.ntt-tx.co.jp >>> >>> >>> _______________________________________________ >>> OpenStack-Infra mailing list >>> OpenStack-Infra at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> >> >> -- >> Mikhail Medvedev >> IBM >> > > -- > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > Rikimaru Honjo > E-mail:honjo.rikimaru at po.ntt-tx.co.jp > > > From fungi at yuggoth.org Wed Aug 22 20:36:31 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 22 Aug 2018 20:36:31 +0000 Subject: [OpenStack-Infra] Volunteer Systems Administrator In-Reply-To: References: Message-ID: <20180822203631.axjv4gftasfuou2u@yuggoth.org> On 2018-08-19 10:46:42 +0200 (+0200), Marcin Koprowski wrote: [...] > The reason why I'm writing here is that I have more than 10 hours > per week to spare and I would like to help you out somehow. My > interest is Systems Administration and DevOps. [...] Welcome! In addition to Anita's great suggestions, an excellent place to start is https://docs.openstack.org/infra/system-config/project.html which attempts to describe in detail who we are and what we do (same link I included in my reply to the personal E-mail you sent me). If you have any questions, any at all, please feel free to ask them here on the mailing list or in our IRC channel. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From doug at doughellmann.com Wed Aug 22 22:02:44 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 22 Aug 2018 18:02:44 -0400 Subject: [OpenStack-Infra] [powervmstackers][goal][python3] starting zuul migration for powervmstackers In-Reply-To: <1534944617-sup-3890@lrrr.local> References: <1534944617-sup-3890@lrrr.local> Message-ID: <1534975343-sup-2832@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-22 09:30:21 -0400: > The migration of Zuul project settings for the > PowerVMStackers repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/ceilometer-powervm > - openstack/networking-powervm > - openstack/nova-powervm All of the migration patches for the PowerVMStackers team have merged and we are ready to approve https://review.openstack.org/#/c/595004/ Doug From fungi at yuggoth.org Wed Aug 22 22:21:51 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 22 Aug 2018 22:21:51 +0000 Subject: [OpenStack-Infra] Delete mispelled branch from Message-ID: <20180822222151.hl63xoitt6th3bhw@yuggoth.org> openstack/networking-vsphere please Reply-To: In-Reply-To: <01a101d4366b$6f212230$4d636690$@suse.com> On 2018-08-17 13:46:54 -0700 (-0700), Adolfo Duarte wrote: > Could you plese delete the branch "stable/queen" from the > openstack/networking-vsphere > > It was a typo, missing "s". I already created a new one called > "stable/queens" but its best to remove the "stable/queen" one to > not confuse folks. Apologies for the delay, this has been completed now. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From aj at suse.com Thu Aug 23 05:23:12 2018 From: aj at suse.com (Andreas Jaeger) Date: Thu, 23 Aug 2018 07:23:12 +0200 Subject: [OpenStack-Infra] How to display the result of tests on the upper right of a gerrit page In-Reply-To: <8f0fb4ab-2306-283f-6418-57e6c9d8e3ed@po.ntt-tx.co.jp> References: <8f0fb4ab-2306-283f-6418-57e6c9d8e3ed@po.ntt-tx.co.jp> Message-ID: <1e34768a-7c76-7924-2ba6-bb3265f0983c@suse.com> Seeing this is about networking-spp, please review and approve: https://review.openstack.org/#/c/592656/ https://review.openstack.org/#/c/592664/ Please do not have the pipeline configuration for your own CI in OpenStack git repos. The job definition is fine but not the pipeline - it fails now in OpenStack Zuul, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From nguyentrihai93 at gmail.com Thu Aug 23 09:04:39 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 23 Aug 2018 18:04:39 +0900 Subject: [OpenStack-Infra] starting zuul migration for mistral team repositories In-Reply-To: References: Message-ID: All of the migration patches for the mistral team have merged and we are ready to approve https://review.openstack.org/#/c/593264/ On Sat, Aug 18, 2018 at 3:08 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the mistral repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/mistral > - openstack/mistral-dashboard > - openstack/mistral-extra > - openstack/mistral-lib > - openstack/mistral-specs > - openstack/mistral-tempest-plugin > - openstack/python-mistralclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Thu Aug 23 12:13:15 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 23 Aug 2018 08:13:15 -0400 Subject: [OpenStack-Infra] starting zuul migration for mistral team repositories In-Reply-To: References: Message-ID: <1535026386-sup-8392@lrrr.local> Excerpts from Nguyễn Trí Hải's message of 2018-08-23 18:04:39 +0900: > All of the migration patches for the mistral team have merged > and we are ready to approve https://review.openstack.org/#/c/593264/ https://review.openstack.org/593232 has not merged yet. > > On Sat, Aug 18, 2018 at 3:08 PM Nguyễn Trí Hải > wrote: > > > The Zuul project settings for the mistral repositories > > has begun. Please do not approve any changes to > > openstack-infra/project-config/zuul.d/projects.yaml for > > the following repositories: > > > > - openstack/mistral > > - openstack/mistral-dashboard > > - openstack/mistral-extra > > - openstack/mistral-lib > > - openstack/mistral-specs > > - openstack/mistral-tempest-plugin > > - openstack/python-mistralclient > > > > -- > > > > Nguyen Tri Hai / Ph.D. Student > > > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > > > > > *[image: > > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > > * > > > From doug at doughellmann.com Thu Aug 23 12:33:07 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 23 Aug 2018 08:33:07 -0400 Subject: [OpenStack-Infra] [monasca][goal][python3] starting zuul migration for monasca Message-ID: <1535027582-sup-293@lrrr.local> The migration of Zuul project settings for the monasca repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/monasca-agent - openstack/monasca-analytics - openstack/monasca-api - openstack/monasca-ceilometer - openstack/monasca-common - openstack/monasca-events-api - openstack/monasca-grafana-datasource - openstack/monasca-kibana-plugin - openstack/monasca-log-api - openstack/monasca-notification - openstack/monasca-persister - openstack/monasca-specs - openstack/monasca-statsd - openstack/monasca-tempest-plugin - openstack/monasca-thresh - openstack/monasca-transform - openstack/monasca-ui - openstack/python-monascaclient From nguyentrihai93 at gmail.com Thu Aug 23 13:23:02 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 23 Aug 2018 22:23:02 +0900 Subject: [OpenStack-Infra] [octavia][goal][python3] starting zuul migration for octavia Message-ID: The Zuul project settings for the octavia repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/neutron-lbaas - openstack/neutron-lbaas-dashboard - openstack/octavia - openstack/octavia-dashboard - openstack/octavia-tempest-plugin - openstack/python-octaviaclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavinux at gmail.com Fri Aug 24 00:46:38 2018 From: xavinux at gmail.com (Javier Romero) Date: Thu, 23 Aug 2018 21:46:38 -0300 Subject: [OpenStack-Infra] Contribution. Message-ID: Hi Team, My name is Javier and live in Buenos Aires, Argentina. Work in the Network Operations Center of an Internet Service Provider where I deploy and manage mission critical Linux Servers. Would like to know, if there is something I can help with on the OpenStack Infraestructure Team. Thanks for your attention. Best Regards, -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 24 07:32:46 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 24 Aug 2018 16:32:46 +0900 Subject: [OpenStack-Infra] [tricircle][goal][python3] starting zuul migration for tricircle Message-ID: The Zuul project settings for the tricircle repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-tricircleclient - openstack/tricircle -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 24 07:48:27 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 24 Aug 2018 16:48:27 +0900 Subject: [OpenStack-Infra] [swift][goal][python3] starting zuul migration for swift Message-ID: The Zuul project settings for the swift repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-swiftclient - openstack/swift - openstack/swift-bench - openstack/swift-specs -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Fri Aug 24 08:06:52 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 24 Aug 2018 17:06:52 +0900 Subject: [OpenStack-Infra] [blazar][goal][python3] starting zuul migration for blazar Message-ID: The Zuul project settings for the blazar repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/blazar - openstack/blazar-dashboard - openstack/blazar-nova - openstack/blazar-tempest-plugin - openstack/python-blazarclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Fri Aug 24 18:15:26 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 24 Aug 2018 11:15:26 -0700 Subject: [OpenStack-Infra] Berlin Community Contributor Awards Message-ID: Hello Everyone! As we approach the Summit (still a ways away thankfully), I thought I would kick off the Community Contributor Award nominations early this round. For those of you that already know what they are, here is the form[1]. For those of you that have never heard of the CCA, I'll briefly explain what they are :) We all know people in the community that do the dirty jobs, we all know people that will bend over backwards trying to help someone new, we all know someone that is a savant in some area of the code we could never hope to understand. These people rarely get the thanks they deserve and the Community Contributor Awards are a chance to make sure they know that they are appreciated for the amazing work they do and skills they have. So go forth and nominate these amazing community members[1]! Nominations will close on October 21st at 7:00 UTC and winners will be announced at the OpenStack Summit in Berlin. -Kendall (diablo_rojo) [1] https://openstackfoundation.formstack.com/forms/berlin_stein_ccas -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Aug 24 18:26:01 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 24 Aug 2018 18:26:01 +0000 Subject: [OpenStack-Infra] Contribution. In-Reply-To: References: Message-ID: <20180824182600.hcq7rqkxkpe5ctz5@yuggoth.org> On 2018-08-23 21:46:38 -0300 (-0300), Javier Romero wrote: > My name is Javier and live in Buenos Aires, Argentina. Welcome! > Work in the Network Operations Center of an Internet Service > Provider where I deploy and manage mission critical Linux Servers. That sounds remarkably exciting. I used to do something similar for many years (before I got heavily involved in helping develop the OpenStack community). > Would like to know, if there is something I can help with on the > OpenStack Infraestructure Team. Absolutely, if you're interested that is. Probably the best place to get started is to (if you haven't already) read the description of what we do and how we do it: https://docs.openstack.org/infra/system-config/project.html That page has an entire section on contributing to our effort. Feel free to ask us any questions in here or in the #openstack-infra channel on the Freenode IRC network too. The more questions you ask, the faster you'll get up to speed with the rest of the team. Thanks for your interest, and I hope we'll see you around! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From aj at suse.com Fri Aug 24 20:01:54 2018 From: aj at suse.com (Andreas Jaeger) Date: Fri, 24 Aug 2018 22:01:54 +0200 Subject: [OpenStack-Infra] Broken Setup for ATT Airship-CI Message-ID: <6ca8b43a-8f3a-f71c-f3e1-514ab2166011@suse.com> Hi ATT Airship-CI contact, I noticed on https://review.openstack.org/#/c/596433/ (and other changes) two separate reports from Airship-CI: 1) "Build Failed https://jenkins-nc.mtn13b1.cci.att.com/job/images/job/airship/job/deckhand/job/deckhand/413/ : FAILURE" 2) "Build Failed http://10.24.20.18:30081/job/images/job/airship/job/deckhand/job/deckhand/360/ : FAILURE" Could you update your CI system to follow the CI policy as documented at https://docs.openstack.org/infra/system-config/third_party.html, please? Let me cite the following items: "A third-party system may only leave one comment per patch set (unless it is retriggered)." -> yours left two "All comments from your CI system must contain a link to the wiki page for your CI system." -> no such link was left "Include a public link to all test artifacts to make debugging failed tests easier (using a dns name over a hardcoded ip is recommended). This should include:" -> Neither of the links above is public. Thus your reporting is not helping the community at large. Please update your system to follow our policy - and especially those three items above. thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From xavinux at gmail.com Fri Aug 24 22:11:12 2018 From: xavinux at gmail.com (Javier Romero) Date: Fri, 24 Aug 2018 19:11:12 -0300 Subject: [OpenStack-Infra] Contribution. In-Reply-To: <20180824182600.hcq7rqkxkpe5ctz5@yuggoth.org> References: <20180824182600.hcq7rqkxkpe5ctz5@yuggoth.org> Message-ID: Hi Jeremy, Thank you for your time to answer. I'm reading the information in that page and hope I can be useful for the Infra team, now at the irc channel.... Best Regards, *Javier Romero* El vie., 24 ago. 2018 a las 15:26, Jeremy Stanley () escribió: > On 2018-08-23 21:46:38 -0300 (-0300), Javier Romero wrote: > > My name is Javier and live in Buenos Aires, Argentina. > > Welcome! > > > Work in the Network Operations Center of an Internet Service > > Provider where I deploy and manage mission critical Linux Servers. > > That sounds remarkably exciting. I used to do something similar for > many years (before I got heavily involved in helping develop the > OpenStack community). > > > Would like to know, if there is something I can help with on the > > OpenStack Infraestructure Team. > > Absolutely, if you're interested that is. Probably the best place to > get started is to (if you haven't already) read the description of > what we do and how we do it: > https://docs.openstack.org/infra/system-config/project.html > > That page has an entire section on contributing to our effort. Feel > free to ask us any questions in here or in the #openstack-infra > channel on the Freenode IRC network too. The more questions you ask, > the faster you'll get up to speed with the rest of the team. > > Thanks for your interest, and I hope we'll see you around! > -- > Jeremy Stanley > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Sat Aug 25 04:50:14 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sat, 25 Aug 2018 13:50:14 +0900 Subject: [OpenStack-Infra] starting zuul migration for solum team repositories In-Reply-To: References: Message-ID: The import patches have been approved and we are ready to proceed with approving the cleanup patch: https://review.openstack.org/#/c/592923/ On Fri, Aug 17, 2018 at 5:12 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the solum repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-solumclient > - openstack/solum > - openstack/solum-dashboard > - openstack/solum-specs > - openstack/solum-tempest-plugin > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Sat Aug 25 05:48:14 2018 From: aj at suse.com (Andreas Jaeger) Date: Sat, 25 Aug 2018 07:48:14 +0200 Subject: [OpenStack-Infra] Broken Setup for ATT Airship-CI In-Reply-To: <6ca8b43a-8f3a-f71c-f3e1-514ab2166011@suse.com> References: <6ca8b43a-8f3a-f71c-f3e1-514ab2166011@suse.com> Message-ID: fyi, just got an answer that the CI is disabled. ATT team, if you need help with setup, please read the referenced page and reach out - having third party CI testing is good ;), just let's do it so that it's beneficial for everybody, thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From nguyentrihai93 at gmail.com Mon Aug 27 06:52:17 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Mon, 27 Aug 2018 15:52:17 +0900 Subject: [OpenStack-Infra] [zun][goal][python3] starting zuul migration for zun In-Reply-To: References: Message-ID: The import patches have been approved and we are ready to proceed with approving the cleanup patch: https://review.openstack.org/#/c/595221/ On Thu, Aug 23, 2018 at 12:24 AM Nguyễn Trí Hải wrote: > The Zuul project settings for the zun repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-zunclient > - openstack/zun > - openstack/zun-tempest-plugin > - openstack/zun-ui > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Mon Aug 27 13:29:45 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Mon, 27 Aug 2018 22:29:45 +0900 Subject: [OpenStack-Infra] [horizon][goal][python3] beginning zuul migration for horizon In-Reply-To: References: Message-ID: The import patches have been approved and we are ready to proceed with approving the cleanup patch: https://review.openstack.org/#/c/594069/ On Tue, Aug 21, 2018 at 5:28 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the horizon repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/django_openstack_auth > - openstack/horizon > - openstack/tempest-horizon > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Mon Aug 27 23:21:34 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 27 Aug 2018 16:21:34 -0700 Subject: [OpenStack-Infra] Launch node and the new bridge server Message-ID: <1535412094.3083990.1488076528.706DBF6D@webmail.messagingengine.com> Hello everyone, I've been trying to help mnaser bootstrap a new cloud region in nodepool. Part of this requires launching a new mirror node in that cloud region and I have discovered some interesting things related to our migration to launch node and how they affect our ability to boot new instances. I'm going to try and summarize all that I have learned as you may find yourself needing to launch nodes too. Also there is plenty to do to help make this better if interested :) The first thing I ran into was that /etc/openstack/clouds.yaml is not managed by ansible on bridge.openstack.org. This meant the new region info was not automatically added to that file. I made a copy of the clouds.yaml file in my homedir, updated it with new region, tested that it worked, then updated the global file with these changes manually. Pabelanger has volunteered to work on getting this managed by ansible and https://review.openstack.org/#/c/593029/ seemed to be where Monty had started. While testing the clouds.yaml changes I ran into the lack of openstackclient installation which had me learn that virtualenv is weird on Bionic with python3. `python3 /usr/lib/python3/dist-packages/virtualenv.py --python=python3 venv` is what I ended up using to create a virtualenv to install openstackclient into. With that done I ran launch-node.py and ran into a couple issues. First we need volume size specification support for boot from volume hosts (added in https://review.openstack.org/554313). I also updated docs to be clear we run under python3 in https://review.openstack.org/#/c/596859/1 and fixed a bug with unlinking ansible caches at https://review.openstack.org/#/c/596873/1. Reviews much appreciated. This got the instance booting happily but then ssh wasn't working which was the result of not running cloud launcher on bridge.o.o yet (and its not running on old puppet master either). I went ahead and manually triggered cloud launcher against both new accounts in this cloud region to update ssh root keys and security groups. We will need to get this running automatically on bridge.o.o. This resulted in launch-node.py exiting successfully but then the puppet cron failed to run puppet on the host to turn it into a new mirror node because there is no python2 installed on Xenial by default. https://review.openstack.org/#/c/596913/ is a work around for this (explicitly install python2 on xenial for now, this will help transition us from trusty to xenial too). But also resulted in some other attempts to address this at https://review.openstack.org/#/c/596905/, https://review.openstack.org/#/c/596911/1, and https://review.openstack.org/#/c/596894/. Once again reviews welcome. The last thing to note out of this is that Trusty comes with python3.4 and centos7 doesn't have python3 and we can't run ansible under python3 on these platforms. This means launch-node.py cannot currently boot trusty or centos nodes. If we end up needing to boot a trusty or centos node we will have to force it to use python2 on the remote instead. TL;DR We need to: * Manage clouds.yaml with ansible * Fix a couple bugs in launch-node.py * Run cloud launcher on bridge.openstack.org * Figure out our python2 to python3 transition plan for Ansible Hopefully this helps you out if you end up needing to launch a new node while we transition to bridge.openstack.org. Clark From cboylan at sapwetik.org Mon Aug 27 23:48:59 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 27 Aug 2018 16:48:59 -0700 Subject: [OpenStack-Infra] Launch node and the new bridge server In-Reply-To: <1535412094.3083990.1488076528.706DBF6D@webmail.messagingengine.com> References: <1535412094.3083990.1488076528.706DBF6D@webmail.messagingengine.com> Message-ID: <1535413739.3089829.1488108136.66AF217B@webmail.messagingengine.com> On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote: > Hello everyone, > > I've been trying to help mnaser bootstrap a new cloud region in > nodepool. Part of this requires launching a new mirror node in that > cloud region and I have discovered some interesting things related to > our migration to launch node and how they affect our ability to boot new > instances. I'm going to try and summarize all that I have learned as you > may find yourself needing to launch nodes too. Also there is plenty to > do to help make this better if interested :) > > The first thing I ran into was that /etc/openstack/clouds.yaml is not > managed by ansible on bridge.openstack.org. This meant the new region > info was not automatically added to that file. I made a copy of the > clouds.yaml file in my homedir, updated it with new region, tested that > it worked, then updated the global file with these changes manually. > Pabelanger has volunteered to work on getting this managed by ansible > and https://review.openstack.org/#/c/593029/ seemed to be where Monty > had started. > > While testing the clouds.yaml changes I ran into the lack of > openstackclient installation which had me learn that virtualenv is weird > on Bionic with python3. `python3 /usr/lib/python3/dist-packages/ > virtualenv.py --python=python3 venv` is what I ended up using to create > a virtualenv to install openstackclient into. > > With that done I ran launch-node.py and ran into a couple issues. First > we need volume size specification support for boot from volume hosts > (added in https://review.openstack.org/554313). I also updated docs to > be clear we run under python3 in > https://review.openstack.org/#/c/596859/1 and fixed a bug with unlinking > ansible caches at https://review.openstack.org/#/c/596873/1. Reviews > much appreciated. > > This got the instance booting happily but then ssh wasn't working which > was the result of not running cloud launcher on bridge.o.o yet (and its > not running on old puppet master either). I went ahead and manually > triggered cloud launcher against both new accounts in this cloud region > to update ssh root keys and security groups. We will need to get this > running automatically on bridge.o.o. > > This resulted in launch-node.py exiting successfully but then the puppet > cron failed to run puppet on the host to turn it into a new mirror node > because there is no python2 installed on Xenial by default. > https://review.openstack.org/#/c/596913/ is a work around for this > (explicitly install python2 on xenial for now, this will help transition > us from trusty to xenial too). But also resulted in some other attempts > to address this at https://review.openstack.org/#/c/596905/, > https://review.openstack.org/#/c/596911/1, and > https://review.openstack.org/#/c/596894/. Once again reviews welcome. > > The last thing to note out of this is that Trusty comes with python3.4 > and centos7 doesn't have python3 and we can't run ansible under python3 > on these platforms. This means launch-node.py cannot currently boot > trusty or centos nodes. If we end up needing to boot a trusty or centos > node we will have to force it to use python2 on the remote instead. > > TL;DR We need to: > * Manage clouds.yaml with ansible > * Fix a couple bugs in launch-node.py > * Run cloud launcher on bridge.openstack.org > * Figure out our python2 to python3 transition plan for Ansible > > Hopefully this helps you out if you end up needing to launch a new node > while we transition to bridge.openstack.org. One quick new observation. launch-node.py does not install puppet at all so the subsequent ansible runs on the newly launched instances will fail when attempting to stop the puppet service (and will continue on to fail to run puppet as well I think). Clark From iwienand at redhat.com Tue Aug 28 09:50:31 2018 From: iwienand at redhat.com (Ian Wienand) Date: Tue, 28 Aug 2018 19:50:31 +1000 Subject: [OpenStack-Infra] Launch node and the new bridge server In-Reply-To: <1535413739.3089829.1488108136.66AF217B@webmail.messagingengine.com> References: <1535412094.3083990.1488076528.706DBF6D@webmail.messagingengine.com> <1535413739.3089829.1488108136.66AF217B@webmail.messagingengine.com> Message-ID: On 08/28/2018 09:48 AM, Clark Boylan wrote: > On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote: > One quick new observation. launch-node.py does not install puppet at > all so the subsequent ansible runs on the newly launched instances > will fail when attempting to stop the puppet service (and will > continue on to fail to run puppet as well I think). I think we should manage puppet on the hosts from Ansible; we did discuss that we could just manually run system-config:install_puppet.sh after launching the node; but while that script does contain some useful things for getting various puppet versions, it also carries a lot of extra cruft from years gone by. I've proposed the roles to install puppet in [1]. This runs the roles under Zuul for integration testing. For the control-plane, we need a slight tweak to the inventory writer to pass through groups [2] and then we can add the roles to the base playbook [3]. Thanks, -i [1] https://review.openstack.org/596968 [2] https://review.openstack.org/596994 [3] https://review.openstack.org/596997 From corvus at inaugust.com Tue Aug 28 15:02:46 2018 From: corvus at inaugust.com (James E. Blair) Date: Tue, 28 Aug 2018 08:02:46 -0700 Subject: [OpenStack-Infra] Launch node and the new bridge server In-Reply-To: (Ian Wienand's message of "Tue, 28 Aug 2018 19:50:31 +1000") References: <1535412094.3083990.1488076528.706DBF6D@webmail.messagingengine.com> <1535413739.3089829.1488108136.66AF217B@webmail.messagingengine.com> Message-ID: <87r2iir0tl.fsf@meyer.lemoncheese.net> Ian Wienand writes: > On 08/28/2018 09:48 AM, Clark Boylan wrote: >> On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote: >> One quick new observation. launch-node.py does not install puppet at >> all so the subsequent ansible runs on the newly launched instances >> will fail when attempting to stop the puppet service (and will >> continue on to fail to run puppet as well I think). > > I think we should manage puppet on the hosts from Ansible; we did > discuss that we could just manually run > system-config:install_puppet.sh after launching the node; but while > that script does contain some useful things for getting various puppet > versions, it also carries a lot of extra cruft from years gone by. > > I've proposed the roles to install puppet in [1]. This runs the roles > under Zuul for integration testing. Unlike the afs/krb roles, I don't believe we have plans to run these roles directly in Zuul jobs, so a better choice might be to exercise them in the eventual per-hostgroup jobs that we write, which test end-to-end deployment of each host. That will be a more realistic exercise of the roles. How about we temporarily add these to the system-config-run-base job until we write our first hostgroup job for a puppet host, then remove it? -Jim From bokke at google.com Tue Aug 28 16:23:18 2018 From: bokke at google.com (David van der Bokke) Date: Tue, 28 Aug 2018 09:23:18 -0700 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> References: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> Message-ID: So it looks like the gerrit team is actually waiting for this to get to tagged before putting the refs/publish removal into a new release but would like to do it before the end of the quarter. On Wed, Aug 22, 2018 at 11:20 AM Jeremy Stanley wrote: > On 2018-08-22 10:11:20 -0700 (-0700), David van der Bokke wrote: > > Thanks Jeremy. I am trying to get an exact date from the Gerrit > > team, but I can say that tagging/releasing a new git-review is a > > likely precursor given that the team had actually removed the ref > > and subsequently reverted the change after discovering that > > git-review needed an update for it. > > Thanks! That definitely helps. When they added it in Gerrit 2.3 > the release notes[*] indicated refs/for was deprecated, so the > update proposed to git-review to switch back was really the first > we'd heard of it being un-deprecated again (I'm not finding a > similar release note about it, and the ACLs release note in 2.16 > about refs/for still talks about people using refs/publish too). > > [*] > https://gerrit.googlesource.com/gerrit/+/v2.15.3/ReleaseNotes/ReleaseNotes-2.3.txt#21 > -- > Jeremy Stanley > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Tue Aug 28 20:07:34 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 28 Aug 2018 16:07:34 -0400 Subject: [OpenStack-Infra] starting zuul migration for Oslo team repositories In-Reply-To: <1533570869-sup-4488@lrrr.local> References: <1533570869-sup-4488@lrrr.local> Message-ID: <1535486823-sup-382@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-06 11:54:35 -0400: > The Zuul project settings for the Oslo repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack-dev/cookiecutter > - openstack-dev/oslo-cookiecutter > - openstack-dev/pbr > - openstack/automaton > - openstack/castellan > - openstack/debtcollector > - openstack/devstack-plugin-amqp1 > - openstack/devstack-plugin-kafka > - openstack/devstack-plugin-pika > - openstack/devstack-plugin-zmq > - openstack/futurist > - openstack/mox3 > - openstack/oslo-specs > - openstack/oslo.cache > - openstack/oslo.concurrency > - openstack/oslo.config > - openstack/oslo.context > - openstack/oslo.db > - openstack/oslo.i18n > - openstack/oslo.limit > - openstack/oslo.log > - openstack/oslo.messaging > - openstack/oslo.middleware > - openstack/oslo.policy > - openstack/oslo.privsep > - openstack/oslo.reports > - openstack/oslo.rootwrap > - openstack/oslo.serialization > - openstack/oslo.service > - openstack/oslo.tools > - openstack/oslo.utils > - openstack/oslo.versionedobjects > - openstack/oslo.vmware > - openstack/oslosphinx > - openstack/oslotest > - openstack/osprofiler > - openstack/sphinx-feature-classification > - openstack/stevedore > - openstack/taskflow > - openstack/tooz All of the patches to import the zuul settings into these repositories are approved and we are ready to proceed with https://review.openstack.org/#/c/588842 From doug at doughellmann.com Tue Aug 28 21:43:18 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 28 Aug 2018 17:43:18 -0400 Subject: [OpenStack-Infra] [goal][python3][heat] starting zuul migration for heat Message-ID: <1535492577-sup-1439@lrrr.local> The migration of Zuul project settings for the heat repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack-dev/heat-cfnclient - openstack/heat - openstack/heat-agents - openstack/heat-cfntools - openstack/heat-dashboard - openstack/heat-specs - openstack/heat-tempest-plugin - openstack/heat-templates - openstack/heat-translator - openstack/python-heatclient - openstack/tosca-parser From cboylan at sapwetik.org Tue Aug 28 21:50:40 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 28 Aug 2018 14:50:40 -0700 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: References: Message-ID: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote: > A quick search with codesearch suggests that these can be retired since > I couldn't find a user: > > openstack-infra/activity-board > openstack-infra/beaker-localhost > openstack-infra/beaker-nodepool > openstack-infra/err2d2 > openstack-infra/featuretracker (together with puppet-featuretracker, not > listed above) > openstack-infra/js-afs-blob-store > openstack-infra/js-generator-openstack > openstack-infra/js-openstack-registry-hooks > openstack-infra/nose-html-output > openstack-infra/openstackweb > openstack-infra/puppet-docker_registry > openstack-infra/project-config-example > openstack-infra/pynotedb > openstack-infra/pypi-mirror > openstack-infra/releasestatus (together with puppet-releasestatus, not > listed above) > openstack-infra/trystack-site > openstack-infra/vinz > openstack-infra/vinz-webclient > openstack-infra/zuul-packaging > > That's 21 repositories. > > Andreas I think these repos can definitely be retired: # Was part of bitergia work with openstack which is no longer done openstack-infra/activity-board # These may have been attempts at having puppet beaker testing play nice with our CI but we hacked around it by pointing the beaker config at localhost. There are no commits here should be safe to retire. openstack-infra/beaker-localhost openstack-infra/beaker-nodepool # Part of a plan to make our IRC bots errbot driven but more recent spec has us sticking with supybot fork and plugins. openstack-infra/err2d2 # Allowed us to mirror npm packages on afs until npm grew too large. I think we can retire this as we don't mirror npm any longer openstack-infra/js-afs-blob-store openstack-infra/js-openstack-registry-hooks # Appears to be a cookiecutter like system for openstack js projects. Maybe we should just use cookiecutter? openstack-infra/js-generator-openstack # Was tooling to make a mirror of a subset of pypi. We moved to bandersnatch and now just proxy cache pypi openstack-infra/pypi-mirror # Trystack has been retired due to spam and the passport program is suggested instead openstack-infra/trystack-site # Project to provide alternate Gerrit UI that never got commits openstack-infra/puppet-vinz openstack-infra/vinz openstack-infra/vinz-webclient Repos we should probably keep: # This is/was meant to be the upstream home of the openstack website but the transition stalled when the devs continued to use github after creating this repo in gerrit. openstack-infra/openstackweb # this is intended to show consumers of infra config management what a project-config looks like openstack-infra/project-config-example We should directly reach out to the authors of the other projects listed to see if they should be retired. Hope this helps, Clark From fungi at yuggoth.org Tue Aug 28 22:55:08 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 28 Aug 2018 22:55:08 +0000 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> Message-ID: <20180828225508.7kequ5xadqmpsjxs@yuggoth.org> On 2018-08-28 14:50:40 -0700 (-0700), Clark Boylan wrote: [...] > # Project to provide alternate Gerrit UI that never got commits > openstack-infra/puppet-vinz > openstack-infra/vinz > openstack-infra/vinz-webclient [...] As an aside, if we ever decide to rename nodepool, recycling this name gets my vote. ;) -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From nguyentrihai93 at gmail.com Wed Aug 29 03:13:24 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 29 Aug 2018 12:13:24 +0900 Subject: [OpenStack-Infra] starting zuul migration for congress team repositories In-Reply-To: References: Message-ID: All of the patches to import the zuul settings into these repositories are approved and we are ready to proceed with https://review.openstack.org/#/c/592970/ On Fri, Aug 17, 2018 at 9:20 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the congress repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/congress > - openstack/congress-dashboard > - openstack/congress-specs > - openstack/congress-tempest-plugin > - openstack/python-congressclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Wed Aug 29 04:44:02 2018 From: aj at suse.com (Andreas Jaeger) Date: Wed, 29 Aug 2018 06:44:02 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> Message-ID: On 2018-08-28 23:50, Clark Boylan wrote: > [...] > I think these repos can definitely be retired: > # Was part of bitergia work with openstack which is no longer done > openstack-infra/activity-board > > # These may have been attempts at having puppet beaker testing play nice with our CI but we hacked around it by pointing the beaker config at localhost. There are no commits here should be safe to retire. > openstack-infra/beaker-localhost > openstack-infra/beaker-nodepool > > # Part of a plan to make our IRC bots errbot driven but more recent spec has us sticking with supybot fork and plugins. > openstack-infra/err2d2 > > # Allowed us to mirror npm packages on afs until npm grew too large. I think we can retire this as we don't mirror npm any longer > openstack-infra/js-afs-blob-store > openstack-infra/js-openstack-registry-hooks > > # Appears to be a cookiecutter like system for openstack js projects. Maybe we should just use cookiecutter? > openstack-infra/js-generator-openstack > > # Was tooling to make a mirror of a subset of pypi. We moved to bandersnatch and now just proxy cache pypi > openstack-infra/pypi-mirror > > # Trystack has been retired due to spam and the passport program is suggested instead > openstack-infra/trystack-site > > # Project to provide alternate Gerrit UI that never got commits > openstack-infra/puppet-vinz > openstack-infra/vinz > openstack-infra/vinz-webclient I've started retiring of these above with https://review.openstack.org/597370, thanks for reviewing the list and giving a rationale, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Wed Aug 29 05:03:29 2018 From: aj at suse.com (Andreas Jaeger) Date: Wed, 29 Aug 2018 07:03:29 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> Message-ID: <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> I digged into the remaining and will investigate whether we can retire them: openstack-infra/zuul-packaging Paul, should we abandon this one as well? openstack-infra/featuretracker (together with puppet-featuretracker) these work together with openstack/development-proposals from the product working group, I'll reach out to them. puppet-docker-registry: See https://review.openstack.org/#/c/399221/ - there's already another tool which we should use, never any commits merged to it. pynotedb I'll reach out to storyboard team. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From adam.coldrick at codethink.co.uk Wed Aug 29 07:14:48 2018 From: adam.coldrick at codethink.co.uk (Adam Coldrick) Date: Wed, 29 Aug 2018 08:14:48 +0100 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> Message-ID: <1535526888.2089.9.camel@codethink.co.uk> On Wed, 2018-08-29 at 07:03 +0200, Andreas Jaeger wrote: > pynotedb >    I'll reach out to storyboard team. This is a port of a perl library implementing notedb that never got fully completed when it was being actively worked on. As far as I'm concerned it can be retired, I don't think any of the contributors have the time or motivation to do any further work on it at this point. Adam From aj at suse.com Wed Aug 29 08:12:19 2018 From: aj at suse.com (Andreas Jaeger) Date: Wed, 29 Aug 2018 10:12:19 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> Message-ID: <7392834e-c617-d656-27eb-3c0bcefb0a81@suse.com> On 2018-08-28 23:50, Clark Boylan wrote: > On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote: >> A quick search with codesearch suggests that these can be retired since >> I couldn't find a user: >> >[...] >> openstack-infra/releasestatus (together with puppet-releasestatus, not >> listed above) AFAIK we can remove these two as well - looking at: https://review.openstack.org/254817 Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From adam.coldrick at codethink.co.uk Wed Aug 29 09:03:16 2018 From: adam.coldrick at codethink.co.uk (Adam Coldrick) Date: Wed, 29 Aug 2018 10:03:16 +0100 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <1535526888.2089.9.camel@codethink.co.uk> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> <1535526888.2089.9.camel@codethink.co.uk> Message-ID: <1535533396.2089.12.camel@codethink.co.uk> On Wed, 2018-08-29 at 08:14 +0100, Adam Coldrick wrote: > On Wed, 2018-08-29 at 07:03 +0200, Andreas Jaeger wrote: > > pynotedb > >    I'll reach out to storyboard team. > > This is a port of a perl library implementing notedb that never got > fully > completed when it was being actively worked on. > > As far as I'm concerned it can be retired, I don't think any of the > contributors have the time or motivation to do any further work on it at > this point. I've been informed that this isn't entirely true and that some people may be interested in working on this after all. Please hold off on retiring it for the time being. Thanks, Adam From thierry at openstack.org Wed Aug 29 09:40:16 2018 From: thierry at openstack.org (Thierry Carrez) Date: Wed, 29 Aug 2018 11:40:16 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <7392834e-c617-d656-27eb-3c0bcefb0a81@suse.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> <7392834e-c617-d656-27eb-3c0bcefb0a81@suse.com> Message-ID: <9e1ca2de-dc8d-c202-c366-89d89c90f329@openstack.org> Andreas Jaeger wrote: > On 2018-08-28 23:50, Clark Boylan wrote: >> On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote: >>> A quick search with codesearch suggests that these can be retired since >>> I couldn't find a user: >>> >> [...] > >>> openstack-infra/releasestatus (together with puppet-releasestatus, not >>> listed above) > > AFAIK we can remove these two as well - looking at: > > https://review.openstack.org/254817 Yes releasestatus is not used anymore. -- Thierry Carrez (ttx) From pabelanger at redhat.com Wed Aug 29 12:16:49 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Wed, 29 Aug 2018 08:16:49 -0400 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> Message-ID: <20180829121649.GA7919@localhost.localdomain> On Wed, Aug 29, 2018 at 07:03:29AM +0200, Andreas Jaeger wrote: > I digged into the remaining and will investigate whether we can retire them: > > openstack-infra/zuul-packaging > > Paul, should we abandon this one as well? > Yes > openstack-infra/featuretracker (together with puppet-featuretracker) > > these work together with openstack/development-proposals from the > product working group, I'll reach out to them. > > puppet-docker-registry: > See https://review.openstack.org/#/c/399221/ - there's already another > tool which we should use, never any commits merged to it. > > pynotedb > I'll reach out to storyboard team. > > Andreas > -- > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From nguyentrihai93 at gmail.com Wed Aug 29 12:34:37 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 29 Aug 2018 21:34:37 +0900 Subject: [OpenStack-Infra] [goal][python3][dragonflow] starting zuul migration for dragonflow Message-ID: The migration of Zuul project settings for the dragonflow repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/dragonflow -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Wed Aug 29 12:44:11 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 29 Aug 2018 21:44:11 +0900 Subject: [OpenStack-Infra] [senlin][goal][python3] beginning zuul migration for senlin Message-ID: The migration of Zuul project settings for the senlin repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-senlinclient - openstack/senlin - openstack/senlin-dashboard - openstack/senlin-tempest-plugin -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Wed Aug 29 14:01:26 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 29 Aug 2018 23:01:26 +0900 Subject: [OpenStack-Infra] [searchlight][goal][python3] beginning zuul migration for searchlight In-Reply-To: References: Message-ID: All of the patches to import the zuul settings into these repositories are approved and we are ready to proceed with https://review.openstack.org/#/c/594033/ On Tue, Aug 21, 2018 at 2:56 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the searchlight repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-searchlightclient > - openstack/searchlight > - openstack/searchlight-specs > - openstack/searchlight-ui > > Nguyen Hai > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Wed Aug 29 14:05:00 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Wed, 29 Aug 2018 23:05:00 +0900 Subject: [OpenStack-Infra] [goal][python3][rally] starting zuul migration for rally Message-ID: The migration of Zuul project settings for the rally repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/performance-docs - openstack/rally -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Wed Aug 29 16:18:44 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 29 Aug 2018 12:18:44 -0400 Subject: [OpenStack-Infra] [tc][goal][python3][election] starting migration of zuul settings for TC repos In-Reply-To: <1534785720-sup-4416@lrrr.local> References: <1534785720-sup-4416@lrrr.local> Message-ID: <1535559506-sup-1535@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-20 13:22:26 -0400: > The migration of Zuul project settings for the > Technical Committee repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/api-wg > - openstack/election > - openstack/goal-tools > - openstack/governance > - openstack/openstack-specs > - openstack/project-navigator-data > - openstack/project-team-guide > - openstack/service-types-authority The import patches for these repositories have all merged and we are ready to proceed with approving https://review.openstack.org/#/c/593706 From cboylan at sapwetik.org Wed Aug 29 18:06:55 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 29 Aug 2018 11:06:55 -0700 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <20180821183306.yy72bamjfhttxnec@yuggoth.org> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> Message-ID: <1535566015.1818990.1490374560.5A36A045@webmail.messagingengine.com> On Tue, Aug 21, 2018, at 11:33 AM, Jeremy Stanley wrote: > The Infra team has been brainstorming and collecting feedback in > https://etherpad.openstack.org/p/infra-services-naming as to what > actual name/domain the Winterscale effort will use. If you've not > been following along, the earlier discussions can be found in the > following mailing list threads: > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > So far the "short list" at the bottom of the pad seems to contain > only one entry: OpenDev. > > The OpenStack Foundation has offered to let us take control of > opendev.org for this purpose if we would like. They have it mainly > as a defensive registration to protect the OpenDev Conference brand, > but use a separate opendevconf.org domain for that at present. The > opendev.org domain is just sitting parked on the same nameservers as > openstack.org right now, not in use for anything. The brand itself > has a positive connotation in the community so far, and the OpenDev > Conferences share a lot of similar goals (bringing communities of > people together to collaborate openly on design and development > activities) so this even provides some useful synergy around the > name and possible promotional tie-ins with the events if we like. > > I know lots of us are eager to move forward on the rebranding, so I > wanted to wake this discussion back up and try to see if we can > drive it to a conclusion. As we continue to take on hosting for > additional large projects, having somewhere for them to send the > contributors and users in their community which has a distinct > identity unclouded by OpenStack itself will help make our services > much more welcoming. If you don't particularly like the OpenDev idea > or have alternatives you think might achieve greater consensus > within our team and present a better image to our extended > community, present and future, please update the above mentioned pad > or follow up to this mailing list thread. Thanks! I am a fan of OpenDev. I think it gives a path forward that works for the immediate future and long term. https://review.opendev.org seems like a reasonable place to do code review for a project :) I do think it would be good to continue collecting input particularly from those involved in the day to day infra activities. If we can reach rough consensus over the next week or so that would give us the opportunity to use time at the PTG to do a rough sketch of how we can start "migrating" to the new name. Your feedback much appreciated. Thank you, Clark From aj at suse.com Wed Aug 29 19:47:35 2018 From: aj at suse.com (Andreas Jaeger) Date: Wed, 29 Aug 2018 21:47:35 +0200 Subject: [OpenStack-Infra] Retiring some repos? In-Reply-To: <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> References: <1535493040.914780.1489307944.40732C0E@webmail.messagingengine.com> <9a0c684e-4a1a-b7e3-331a-98d8cdfa0f3a@suse.com> Message-ID: <13fe0755-cfad-955f-002c-e6f3ed909c6c@suse.com> On 2018-08-29 07:03, Andreas Jaeger wrote: > I digged into the remaining and will investigate whether we can retire > them: > > openstack-infra/zuul-packaging > >   Paul, should we abandon this one as well? > > openstack-infra/featuretracker (together with puppet-featuretracker) > >   these work together with openstack/development-proposals from the >   product working group, I'll reach out to them. the product WG is retired, see http://lists.openstack.org/pipermail/user-committee/2018-February/002599.html the URL http://featuretracker.openstack.org/ is also dead. So, we can retire these two as well, Andreas > puppet-docker-registry: >   See https://review.openstack.org/#/c/399221/ - there's already another >   tool which we should use, never any commits merged to it. > > pynotedb >   I'll reach out to storyboard team. > > Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From doug at doughellmann.com Wed Aug 29 20:16:30 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 29 Aug 2018 16:16:30 -0400 Subject: [OpenStack-Infra] [goal][python3][keystone] starting zuul migration for keystone team Message-ID: <1535573784-sup-141@lrrr.local> The migration of Zuul project settings for the keystone repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/keystone - openstack/keystone-specs - openstack/keystone-tempest-plugin - openstack/keystoneauth - openstack/keystonemiddleware - openstack/ldappool - openstack/pycadf - openstack/python-keystoneclient From doug at doughellmann.com Thu Aug 30 00:00:20 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 29 Aug 2018 20:00:20 -0400 Subject: [OpenStack-Infra] [goal][python3][tripleo] starting zuul migration for tripleo Message-ID: <1535587210-sup-359@lrrr.local> The migration of Zuul project settings for the tripleo repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack-infra/tripleo-ci - openstack/ansible-role-container-registry - openstack/ansible-role-k8s-cinder - openstack/ansible-role-k8s-cookiecutter - openstack/ansible-role-k8s-glance - openstack/ansible-role-k8s-keystone - openstack/ansible-role-k8s-mariadb - openstack/ansible-role-k8s-rabbitmq - openstack/ansible-role-k8s-tripleo - openstack/ansible-role-openstack-operations - openstack/ansible-role-redhat-subscription - openstack/ansible-role-tripleo-aodh - openstack/ansible-role-tripleo-barbican - openstack/ansible-role-tripleo-ceilometer - openstack/ansible-role-tripleo-cinder - openstack/ansible-role-tripleo-cookiecutter - openstack/ansible-role-tripleo-designate - openstack/ansible-role-tripleo-glance - openstack/ansible-role-tripleo-gnocchi - openstack/ansible-role-tripleo-haproxy - openstack/ansible-role-tripleo-heat - openstack/ansible-role-tripleo-horizon - openstack/ansible-role-tripleo-ironic - openstack/ansible-role-tripleo-keepalived - openstack/ansible-role-tripleo-keystone - openstack/ansible-role-tripleo-manila - openstack/ansible-role-tripleo-memcached - openstack/ansible-role-tripleo-mistral - openstack/ansible-role-tripleo-modify-image - openstack/ansible-role-tripleo-neutron - openstack/ansible-role-tripleo-nova - openstack/ansible-role-tripleo-octavia - openstack/ansible-role-tripleo-opendaylight - openstack/ansible-role-tripleo-ovn - openstack/ansible-role-tripleo-panko - openstack/ansible-role-tripleo-qdrouterd - openstack/ansible-role-tripleo-rabbitmq - openstack/ansible-role-tripleo-rsyslog-sidecar - openstack/ansible-role-tripleo-sahara - openstack/ansible-role-tripleo-sensu - openstack/ansible-role-tripleo-swift - openstack/ansible-role-tripleo-tacker - openstack/ansible-role-tripleo-tempest - openstack/ansible-role-tripleo-ui - openstack/ansible-role-tripleo-zaqar - openstack/dib-utils - openstack/instack - openstack/instack-undercloud - openstack/os-apply-config - openstack/os-collect-config - openstack/os-net-config - openstack/os-refresh-config - openstack/paunch - openstack/puppet-pacemaker - openstack/puppet-tripleo - openstack/python-tripleoclient - openstack/tempest-tripleo-ui - openstack/tripleo-ansible - openstack/tripleo-common - openstack/tripleo-common-tempest-plugin - openstack/tripleo-docs - openstack/tripleo-ha-utils - openstack/tripleo-heat-templates - openstack/tripleo-image-elements - openstack/tripleo-ipsec - openstack/tripleo-puppet-elements - openstack/tripleo-quickstart - openstack/tripleo-quickstart-extras - openstack/tripleo-repos - openstack/tripleo-specs - openstack/tripleo-ui - openstack/tripleo-upgrade - openstack/tripleo-validations From doug at doughellmann.com Thu Aug 30 00:06:04 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 29 Aug 2018 20:06:04 -0400 Subject: [OpenStack-Infra] [goal][python3][neutron] starting zuul migration for neutron Message-ID: <1535587560-sup-2159@lrrr.local> The migration of Zuul project settings for the neutron repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/networking-bagpipe - openstack/networking-bgpvpn - openstack/networking-midonet - openstack/networking-odl - openstack/networking-ovn - openstack/networking-sfc - openstack/neutron - openstack/neutron-dynamic-routing - openstack/neutron-fwaas - openstack/neutron-fwaas-dashboard - openstack/neutron-lib - openstack/neutron-specs - openstack/neutron-tempest-plugin - openstack/neutron-vpnaas - openstack/neutron-vpnaas-dashboard - openstack/ovsdbapp - openstack/python-neutronclient From nguyentrihai93 at gmail.com Thu Aug 30 04:55:11 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 30 Aug 2018 13:55:11 +0900 Subject: [OpenStack-Infra] starting zuul migration for designate team repositories In-Reply-To: References: Message-ID: All python3-first patches in designate repositories are merged. Please process the remove job settings for designate repositories. https://review.openstack.org/#/c/592865/ On Fri, Aug 17, 2018 at 9:22 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the designate repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/designate > - openstack/designate-dashboard > - openstack/designate-specs > - openstack/designate-tempest-plugin > - openstack/python-designateclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Thu Aug 30 13:31:15 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 30 Aug 2018 22:31:15 +0900 Subject: [OpenStack-Infra] [goal][python3][rally] starting zuul migration for rally In-Reply-To: References: Message-ID: It is ready for removing configuration on project-config: https://review.openstack.org/#/c/597517/ On Wed, Aug 29, 2018 at 11:05 PM Nguyễn Trí Hải wrote: > The migration of Zuul project settings for the > rally repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/performance-docs > - openstack/rally > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Thu Aug 30 13:33:53 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 30 Aug 2018 22:33:53 +0900 Subject: [OpenStack-Infra] starting zuul migration for cyborg team repositories In-Reply-To: References: Message-ID: It is ready for remove Zuul configuration in project-config: https://review.openstack.org/#/c/592849/ On Fri, Aug 17, 2018 at 2:59 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the cyborg repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/cyborg > - openstack/cyborg-specs > - openstack/os-acc > - openstack/python-cyborgclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Thu Aug 30 22:17:42 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 30 Aug 2018 18:17:42 -0400 Subject: [OpenStack-Infra] [goals][python3][interop] starting zuul migration for InteropWG Message-ID: <1535667459-sup-2168@lrrr.local> The migration of Zuul project settings for the InteropWG repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/interop - openstack/python-tempestconf - openstack/refstack - openstack/refstack-client From doug at doughellmann.com Thu Aug 30 23:01:04 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 30 Aug 2018 19:01:04 -0400 Subject: [OpenStack-Infra] [goals][python3][uc] starting zuul migration for user committee repositories Message-ID: <1535670061-sup-6332@lrrr.local> The migration of Zuul project settings for the User Committee repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/development-proposals - openstack/enterprise-wg - openstack/governance-uc - openstack/ops-tags-team - openstack/publiccloud-wg - openstack/scientific-wg - openstack/uc-recognition - openstack/workload-ref-archs From doug at doughellmann.com Fri Aug 31 11:52:45 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 07:52:45 -0400 Subject: [OpenStack-Infra] [goals][python3][chef] starting zuul migration for chef team Message-ID: <1535716359-sup-7426@lrrr.local> The migration of Zuul project settings for the Chef OpenStack repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/cookbook-openstack-application-catalog - openstack/cookbook-openstack-block-storage - openstack/cookbook-openstack-client - openstack/cookbook-openstack-common - openstack/cookbook-openstack-compute - openstack/cookbook-openstack-dashboard - openstack/cookbook-openstack-dns - openstack/cookbook-openstack-identity - openstack/cookbook-openstack-image - openstack/cookbook-openstack-integration-test - openstack/cookbook-openstack-network - openstack/cookbook-openstack-ops-database - openstack/cookbook-openstack-ops-messaging - openstack/cookbook-openstack-orchestration - openstack/cookbook-openstack-telemetry - openstack/cookbook-openstackclient - openstack/openstack-chef - openstack/openstack-chef-repo - openstack/openstack-chef-specs From doug at doughellmann.com Fri Aug 31 11:57:42 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 07:57:42 -0400 Subject: [OpenStack-Infra] [goals][python3][adjutant] starting zuul migration for adjutant Message-ID: <1535716657-sup-8713@lrrr.local> The migration of Zuul project settings for the adjutant repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/adjutant - openstack/adjutant-ui - openstack/python-adjutantclient From doug at doughellmann.com Fri Aug 31 12:12:43 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 08:12:43 -0400 Subject: [OpenStack-Infra] [goals][python3][telemetry] starting zuul migration for telemetry Message-ID: <1535717560-sup-1843@lrrr.local> The migration of Zuul project settings for the Telemetry repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/aodh - openstack/ceilometer - openstack/ceilometermiddleware - openstack/panko - openstack/python-aodhclient - openstack/python-pankoclient - openstack/telemetry-specs - openstack/telemetry-tempest-plugin From doug at doughellmann.com Fri Aug 31 12:51:15 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 08:51:15 -0400 Subject: [OpenStack-Infra] [goals][python3][puppet] starting zuul migration for puppet team Message-ID: <1535719871-sup-5001@lrrr.local> The migration of Zuul project settings for the Puppet OpenStack repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/puppet-aodh - openstack/puppet-barbican - openstack/puppet-ceilometer - openstack/puppet-ceph - openstack/puppet-cinder - openstack/puppet-cloudkitty - openstack/puppet-congress - openstack/puppet-designate - openstack/puppet-ec2api - openstack/puppet-freezer - openstack/puppet-glance - openstack/puppet-glare - openstack/puppet-gnocchi - openstack/puppet-heat - openstack/puppet-horizon - openstack/puppet-ironic - openstack/puppet-keystone - openstack/puppet-magnum - openstack/puppet-manila - openstack/puppet-mistral - openstack/puppet-monasca - openstack/puppet-murano - openstack/puppet-neutron - openstack/puppet-nova - openstack/puppet-octavia - openstack/puppet-openstack-cookiecutter - openstack/puppet-openstack-guide - openstack/puppet-openstack-integration - openstack/puppet-openstack-specs - openstack/puppet-openstack_extras - openstack/puppet-openstack_spec_helper - openstack/puppet-openstacklib - openstack/puppet-oslo - openstack/puppet-ovn - openstack/puppet-panko - openstack/puppet-qdr - openstack/puppet-rally - openstack/puppet-sahara - openstack/puppet-senlin - openstack/puppet-swift - openstack/puppet-tacker - openstack/puppet-tempest - openstack/puppet-trove - openstack/puppet-vitrage - openstack/puppet-vswitch - openstack/puppet-watcher - openstack/puppet-zaqar From doug at doughellmann.com Fri Aug 31 13:03:07 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 09:03:07 -0400 Subject: [OpenStack-Infra] [goals][python3][cloudkitty] starting zuul migration for cloudkitty Message-ID: <1535720569-sup-902@lrrr.local> The migration of Zuul project settings for the cloudkitty repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/cloudkitty - openstack/cloudkitty-dashboard - openstack/cloudkitty-specs - openstack/cloudkitty-tempest-plugin - openstack/python-cloudkittyclient From doug at doughellmann.com Fri Aug 31 14:13:51 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 10:13:51 -0400 Subject: [OpenStack-Infra] [goals][python3][packaging-rpm] starting zuul migration for packaging-rpm team Message-ID: <1535724817-sup-4377@lrrr.local> The migration of Zuul project settings for the Packaging-rpm repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/pymod2pkg - openstack/renderspec - openstack/rpm-packaging - openstack/rpm-packaging-tools From doug at doughellmann.com Fri Aug 31 15:42:40 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 11:42:40 -0400 Subject: [OpenStack-Infra] [goals][python3][puppet] starting zuul migration for puppet team In-Reply-To: <1535719871-sup-5001@lrrr.local> References: <1535719871-sup-5001@lrrr.local> Message-ID: <1535730120-sup-6518@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-31 08:51:15 -0400: > The migration of Zuul project settings for the > Puppet OpenStack repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/puppet-aodh > - openstack/puppet-barbican > - openstack/puppet-ceilometer > - openstack/puppet-ceph > - openstack/puppet-cinder > - openstack/puppet-cloudkitty > - openstack/puppet-congress > - openstack/puppet-designate > - openstack/puppet-ec2api > - openstack/puppet-freezer > - openstack/puppet-glance > - openstack/puppet-glare > - openstack/puppet-gnocchi > - openstack/puppet-heat > - openstack/puppet-horizon > - openstack/puppet-ironic > - openstack/puppet-keystone > - openstack/puppet-magnum > - openstack/puppet-manila > - openstack/puppet-mistral > - openstack/puppet-monasca > - openstack/puppet-murano > - openstack/puppet-neutron > - openstack/puppet-nova > - openstack/puppet-octavia > - openstack/puppet-openstack-cookiecutter > - openstack/puppet-openstack-guide > - openstack/puppet-openstack-integration > - openstack/puppet-openstack-specs > - openstack/puppet-openstack_extras > - openstack/puppet-openstack_spec_helper > - openstack/puppet-openstacklib > - openstack/puppet-oslo > - openstack/puppet-ovn > - openstack/puppet-panko > - openstack/puppet-qdr > - openstack/puppet-rally > - openstack/puppet-sahara > - openstack/puppet-senlin > - openstack/puppet-swift > - openstack/puppet-tacker > - openstack/puppet-tempest > - openstack/puppet-trove > - openstack/puppet-vitrage > - openstack/puppet-vswitch > - openstack/puppet-watcher > - openstack/puppet-zaqar The import patch has merged and we are ready to proceed with the cleanup in https://review.openstack.org/598614 Doug From aschultz at redhat.com Fri Aug 31 16:11:12 2018 From: aschultz at redhat.com (Alex Schultz) Date: Fri, 31 Aug 2018 10:11:12 -0600 Subject: [OpenStack-Infra] [goals][python3][puppet] starting zuul migration for puppet team In-Reply-To: <1535730120-sup-6518@lrrr.local> References: <1535719871-sup-5001@lrrr.local> <1535730120-sup-6518@lrrr.local> Message-ID: On Fri, Aug 31, 2018 at 9:42 AM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2018-08-31 08:51:15 -0400: >> The migration of Zuul project settings for the >> Puppet OpenStack repositories has begun. >> Please do not approve any changes to >> openstack-infra/project-config/zuul.d/projects.yaml >> for the following repositories: >> >> - openstack/puppet-aodh >> - openstack/puppet-barbican >> - openstack/puppet-ceilometer >> - openstack/puppet-ceph >> - openstack/puppet-cinder >> - openstack/puppet-cloudkitty >> - openstack/puppet-congress >> - openstack/puppet-designate >> - openstack/puppet-ec2api >> - openstack/puppet-freezer >> - openstack/puppet-glance >> - openstack/puppet-glare >> - openstack/puppet-gnocchi >> - openstack/puppet-heat >> - openstack/puppet-horizon >> - openstack/puppet-ironic >> - openstack/puppet-keystone >> - openstack/puppet-magnum >> - openstack/puppet-manila >> - openstack/puppet-mistral >> - openstack/puppet-monasca >> - openstack/puppet-murano >> - openstack/puppet-neutron >> - openstack/puppet-nova >> - openstack/puppet-octavia >> - openstack/puppet-openstack-cookiecutter >> - openstack/puppet-openstack-guide >> - openstack/puppet-openstack-integration >> - openstack/puppet-openstack-specs >> - openstack/puppet-openstack_extras >> - openstack/puppet-openstack_spec_helper >> - openstack/puppet-openstacklib >> - openstack/puppet-oslo >> - openstack/puppet-ovn >> - openstack/puppet-panko >> - openstack/puppet-qdr >> - openstack/puppet-rally >> - openstack/puppet-sahara >> - openstack/puppet-senlin >> - openstack/puppet-swift >> - openstack/puppet-tacker >> - openstack/puppet-tempest >> - openstack/puppet-trove >> - openstack/puppet-vitrage >> - openstack/puppet-vswitch >> - openstack/puppet-watcher >> - openstack/puppet-zaqar > > The import patch has merged and we are ready to proceed with the cleanup > in https://review.openstack.org/598614 > That's a chef repo? > Doug > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From doug at doughellmann.com Fri Aug 31 16:17:01 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Fri, 31 Aug 2018 12:17:01 -0400 Subject: [OpenStack-Infra] [goals][python3][puppet] starting zuul migration for puppet team In-Reply-To: References: <1535719871-sup-5001@lrrr.local> <1535730120-sup-6518@lrrr.local> Message-ID: <0358E6BC-0D5C-4A3E-AE99-14E72FABA1B6@doughellmann.com> > On Aug 31, 2018, at 12:11 PM, Alex Schultz wrote: > > On Fri, Aug 31, 2018 at 9:42 AM, Doug Hellmann > wrote: >> Excerpts from Doug Hellmann's message of 2018-08-31 08:51:15 -0400: >>> The migration of Zuul project settings for the >>> Puppet OpenStack repositories has begun. >>> Please do not approve any changes to >>> openstack-infra/project-config/zuul.d/projects.yaml >>> for the following repositories: >>> >>> - openstack/puppet-aodh >>> - openstack/puppet-barbican >>> - openstack/puppet-ceilometer >>> - openstack/puppet-ceph >>> - openstack/puppet-cinder >>> - openstack/puppet-cloudkitty >>> - openstack/puppet-congress >>> - openstack/puppet-designate >>> - openstack/puppet-ec2api >>> - openstack/puppet-freezer >>> - openstack/puppet-glance >>> - openstack/puppet-glare >>> - openstack/puppet-gnocchi >>> - openstack/puppet-heat >>> - openstack/puppet-horizon >>> - openstack/puppet-ironic >>> - openstack/puppet-keystone >>> - openstack/puppet-magnum >>> - openstack/puppet-manila >>> - openstack/puppet-mistral >>> - openstack/puppet-monasca >>> - openstack/puppet-murano >>> - openstack/puppet-neutron >>> - openstack/puppet-nova >>> - openstack/puppet-octavia >>> - openstack/puppet-openstack-cookiecutter >>> - openstack/puppet-openstack-guide >>> - openstack/puppet-openstack-integration >>> - openstack/puppet-openstack-specs >>> - openstack/puppet-openstack_extras >>> - openstack/puppet-openstack_spec_helper >>> - openstack/puppet-openstacklib >>> - openstack/puppet-oslo >>> - openstack/puppet-ovn >>> - openstack/puppet-panko >>> - openstack/puppet-qdr >>> - openstack/puppet-rally >>> - openstack/puppet-sahara >>> - openstack/puppet-senlin >>> - openstack/puppet-swift >>> - openstack/puppet-tacker >>> - openstack/puppet-tempest >>> - openstack/puppet-trove >>> - openstack/puppet-vitrage >>> - openstack/puppet-vswitch >>> - openstack/puppet-watcher >>> - openstack/puppet-zaqar >> >> The import patch has merged and we are ready to proceed with the cleanup >> in https://review.openstack.org/598614 >> > > That's a chef repo? Oops, wrong thread. We’re not ready with the puppet cleanup and I still have a W-1 on that patch. > >> Doug >> >> _______________________________________________ >> OpenStack-Infra mailing list >> OpenStack-Infra at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Fri Aug 31 18:41:43 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 31 Aug 2018 11:41:43 -0700 Subject: [OpenStack-Infra] Migrating job configs into infra repositories Message-ID: <1535740903.1341276.1492864688.575F1FED@webmail.messagingengine.com> Hello, OpenStack is currently in the process of migrating project CI job configs into individual repos. Part of the motivation for this was to remove us (the Infra team) as a roadblock to getting job config changes merged. This is particular important for OpenStack as it is trying to update its job configs to be python3 first so there will be a fair bit of job churn over the Stein cycle. This is great for OpenStack, but the question has come up about whether or not we (the Infra team) want to do similar for our projects. My initial thought is that it isn't as urgent for us because infra-core already manage both the separate repos and the central job config. This means we can manage the job churn ourselves regardless of the location. Considering the other items we currently have on our place (namely Winterscale and config management updates) I'm willing to defer on this for now. If you think we should make moving job config into our repos a priority please let me know. More than happy to accommodate this work, but we will likely need a volunteer to help do it. (I don't expect we'll be able to piggy back off of the OpenStack work as we have many non standard jobs from OpenStack's perspective). Thanks, Clark