Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

No, I mean, Consul would be an extra dependency in a big list of dependencies OpenStack already has. OpenStack has so many it is causing operators to reconsider adoption. I'm asking, if existing dependencies can be made to solve the problem without adding more? Stateful dependencies are

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

On 17.10.2018 15:45, Florian Engelmann wrote: On 10.10.2018 09:06, Florian Engelmann wrote: Now I get you. I would say all configuration templates need to be changed to allow, eg. $ grep http /etc/kolla/cinder-volume/cinder.conf glance_api_servers = http://10.10.10.5:9292 auth_url =

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

On 10/14/18 5:07 PM, Emilien Macchi wrote: > I recently wrote a blog post about how we could upgrade an host from > Docker containers to Podman containers. > > http://my1.fr/blog/openstack-containerization-with-podman-part-3-upgrades/ thanks Emilien this looks nice and I believe the basic

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

currently we are testing what is needed to get consul + registrator and kolla/kolla-ansible play together nicely. To get the services created in consul by registrator all kolla containers running relevant services (eg. keystone, nova, cinder, ... but also mariadb, memcached, es, ...) need to

Re: [openstack-dev] [Openstack-sigs] [FEMDC] [Edge] [tripleo] On the use of terms "Edge" and "Far Edge"

Hi, I’m adding the ECG mailing list to the discussion. I think the root of the problem is that there is no single definition of „the edge” (except for [1]), but it changes from group to group or use case to use case. What I recognise as the

[openstack-dev] [cinder]ceph rbd replication group support

Hi: I have a question about rbd replication group, I want to know the plan or roadmap about it? Anybody work on it? Blueprint: https://blueprints.launchpad.net/cinder/+spec/ceph-rbd-replication-group-support Thanks 保密：本函仅供收件人使用，如阁下并非抬头标明的收件人，请您即刻删除本函，勿以任何方式使用及传播，并请您能将此误发情形通知发件人，谢谢！

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

This appears to be another in-transit job conflict with the py3 work. Things should be fine, but we will need to manually propose the constraint update since it was skipped. On Fri, Oct 19, 2018, 09:14 wrote: > Build failed. > > - release-openstack-python3 >

[openstack-dev] Proposal for a process to keep up with Python releases

There hasn't been a Python 2 release in 8 years, and during that time we've gotten used to the idea that that's the way things go. However, with the switch to Python 3 looming (we will drop support for Python 2 in the U release[1]), history is no longer a good guide: Python 3 releases drop as

Re: [openstack-dev] [manila] [contribute]

On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote: Hi all. I've downloaded the manila project from GitHub as a zip file, unpacked it and have run `git fetch --depth=1` and been progressively running `git fetch --deepen=5` to get the commit history I need. For future reference, would a

Re: [openstack-dev] Forum Schedule - Seeking Community Review

Colleen Murphy October 17, 2018 at 12:55 AM Couple of things: 1. I noticed Julia's session "Community outreach when culture, time zones, and language differ" and Thierry's session "Getting OpenStack users involved in the project" are scheduled at the same time

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

Hi melanie, thanks for your reply. The version of my cinder and nova is Rocky. The scope of the cinder spec[1] is only for available volume migration between two pools from the same ceph cluster. If the volume is in-use status[2], it will call the generic migration function. So that as you

[openstack-dev] Next Manila meeting cancelled

We have a number of manila cores and regular participants who cannot attend the regular Thursday Manila meeting this coming week so it is cancelled. We will meet as normal the following Thursday, 1 November, at 1500 UTC on #openstack-meeting-alt [1]. Cheers, -- Tom Barron (tbarron) [1]

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

+1 On Fri, Oct 19, 2018 at 6:29 AM Emilien Macchi wrote: > > On Fri, Oct 19, 2018 at 8:24 AM Juan Antonio Osorio Robles > wrote: >> >> I would like to propose Bob Fournier (bfournie) as a core reviewer in >> TripleO. His patches and reviews have spanned quite a wide range in our >> project, his

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

On 19/10/2018 16.19, Sean McGinnis wrote: This appears to be another in-transit job conflict with the py3 work. Things should be fine, but we will need to manually propose the constraint update since it was skipped. On Fri, Oct 19, 2018, 09:14 > wrote: Build

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

On Fri, 19 Oct 2018 11:33:52 +0800 (GMT+08:00), Boxiang Zhu wrote: When I use the LVM backend to create the volume, then attach it to a vm. I can migrate the volume(in-use) from one host to another. The nova libvirt will call the 'rebase' to finish it. But if using ceph backend, it raises

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

+1 On Fri, Oct 19, 2018 at 9:46 AM Alex Schultz wrote: > > +1 > On Fri, Oct 19, 2018 at 6:29 AM Emilien Macchi wrote: > > > > On Fri, Oct 19, 2018 at 8:24 AM Juan Antonio Osorio Robles > > wrote: > >> > >> I would like to propose Bob Fournier (bfournie) as a core reviewer in > >> TripleO. His

Re: [openstack-dev] [Openstack-operators] [goals][upgrade-checkers] Week R-26 Update

Top posting just to try and summarize my thought that for the goal in Stein, I think we should focus on getting the base framework in place for each service project, along with any non-config (including policy) specific upgrade checks that make sense for each project. As Ben mentioned, there

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

On Fri, 19 Oct 2018 23:21:01 +0800 (GMT+08:00), Boxiang Zhu wrote: The version of my cinder and nova is Rocky. The scope of the cinder spec[1] is only for available volume migration between two pools from the same ceph cluster. If the volume is in-use status[2], it will call the generic

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

Ed Leafe wrote: On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: I'd like some input from the community on how we'd like this to go. I would say it depends on the long-term plans for paste. Are we planning on weaning ourselves off of paste, and simply need to maintain it until that can be

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

+1 On Fri, Oct 19, 2018 at 9:47 AM John Fulton wrote: > +1 > On Fri, Oct 19, 2018 at 9:46 AM Alex Schultz wrote: > > > > +1 > > On Fri, Oct 19, 2018 at 6:29 AM Emilien Macchi > wrote: > > > > > > On Fri, Oct 19, 2018 at 8:24 AM Juan Antonio Osorio Robles < > jaosor...@redhat.com> wrote: > >

[openstack-dev] [goals][upgrade-checkers] Week R-25 Update

The big news this week is we have a couple of volunteer developers from NEC (Akhil Jain and Rajat Dhasmana) who are pushing the base framework changes across a lot of the projects [1]. I'm trying to review as many of these as I can. The request now is for the core teams on these projects to

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

Adding a stateless service provider on the existing etcd key value store would be pretty easy with something like coredns I think without adding another stateful storage dependency. I don't really have a horse in the game other then I'm an operator and we're feeling overwhelmed by all the

[openstack-dev] [glance] next python-glanceclient release

Hello Glancers, I was looking at a Cinder patch [0] and it made me realize that we should do a glanceclient release that includes the multihash-download-verification [1] before the next scheduled Stein release (which was to be 3.0.0, basically Rocky with v1 support removed; see [2]). I think it

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: > > On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > > Additionally I took a stab at combining the puppet/docker service > > definitions for the aodh services in a similar structure to start > > reducing the overhead we've had from

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On Fri, Oct 19, 2018, at 8:17 AM, Zane Bitter wrote: > There hasn't been a Python 2 release in 8 years, and during that time > we've gotten used to the idea that that's the way things go. However, > with the switch to Python 3 looming (we will drop support for Python 2 > in the U release[1]),

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > Additionally I took a stab at combining the puppet/docker service > definitions for the aodh services in a similar structure to start > reducing the overhead we've had from maintaining the docker/puppet > implementations seperately. You can

Re: [openstack-dev] [mistral][oslo][messaging] Removing “blocking” executor from oslo.messaging

Hi Renat, After discussing this a bit with Ben on IRC we're going to push the removal off to T milestone 1. I really like Ben's idea re: adding a blocking entry to your project's setup.cfg file. We can remove the explicit check for blocking in oslo.messaging so you won't get an annoying warning

[openstack-dev] [oslo] Next meeting cancelled

Hi, Sorry for the late notice, but I just found out I'm going to be travelling next week, which will mean I can't run the meeting. Since Doug is also out and it's really late to find someone else to run it, we're just going to skip it. We'll resume as normal the following week. Also note

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 19/10/18 12:30 PM, Clark Boylan wrote: On Fri, Oct 19, 2018, at 8:17 AM, Zane Bitter wrote: Unit Tests -- For unit tests, the most important thing is to test on the versions of Python we target. It's less important to be using the exact distro that we want to target, because unit

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 19/10/18 11:17 AM, Zane Bitter wrote: I'd like to propose that we handle this by setting up a unit test template in openstack-zuul-jobs for each release. So for Stein we'd have openstack-python3-stein-jobs. This template would contain: * A voting gate job for the highest minor version of

[openstack-dev] [Octavia] SSL errors polling amphorae and missing tenant network interface

Apologies for cross-posting, but in the event that these might be worth filing as bugs, I wanted the Octavia devs to see it as well... I've been wrestling with getting Octavia up and running and have become stuck on two issues. I'm hoping someone has run into these before. My google foo has come

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 10/19/2018 01:58 PM, Andreas Jaeger wrote: On 19/10/2018 18.30, Clark Boylan wrote: > [...] Because zuul config is branch specific we could set up every project to use a `openstack-python3-jobs` template then define that template differently on each branch. This would mean you only have to

Re: [openstack-dev] Proposal for a process to keep up with Python releases

On 19/10/2018 18.30, Clark Boylan wrote: > [...] Because zuul config is branch specific we could set up every project to use a `openstack-python3-jobs` template then define that template differently on each branch. This would mean you only have to update the location where the template is

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

On 19.10.2018 10:21, Florian Engelmann wrote: On 17.10.2018 15:45, Florian Engelmann wrote: On 10.10.2018 09:06, Florian Engelmann wrote: Now I get you. I would say all configuration templates need to be changed to allow, eg. $ grep http /etc/kolla/cinder-volume/cinder.conf

Re: [openstack-dev] [Octavia] SSL errors polling amphorae and missing tenant network interface

Hi Erik, Sorry to hear you are still having certificate issues. Issue #2 is probably caused by issue #1. Since we hot-plug the tenant network for the VIP, one of the first steps after the worker connects to the amphora agent is finishing the required configuration of the VIP interface inside the

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

On Fri, Oct 19, 2018 at 4:24 AM Giulio Fidente wrote: > 1) create the podman systemd unit > 2) delete the docker container > We finally went with "stop the docker container" 3) start the podman container > and 4) delete the docker container later in THT upgrade_tasks. And yes +1 to do the

[openstack-dev] [placement] update 18-42

HTML: https://anticdent.org/placement-update-18-42.html After a gap from when I was away last week, here's this week's placement update. The situation this week remains much the same as last week: focus on specs and the bigger issues associated with extraction. # Most Important The major

[openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

Hello! I would like to propose Bob Fournier (bfournie) as a core reviewer in TripleO. His patches and reviews have spanned quite a wide range in our project, his reviews show great insight and quality and I think he would be a addition to the core team. What do you folks think? Best Regards

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

On Fri, Oct 19, 2018 at 8:24 AM Juan Antonio Osorio Robles < jaosor...@redhat.com> wrote: > I would like to propose Bob Fournier (bfournie) as a core reviewer in > TripleO. His patches and reviews have spanned quite a wide range in our > project, his reviews show great insight and quality and I

Re: [openstack-dev] [manila] [contribute]

Hi all. I've downloaded the manila project from GitHub as a zip file, unpacked it and have run `git fetch --depth=1` and been progressively running `git fetch --deepen=5` to get the commit history I need. For future reference, would a shallow clone e.g. `git clone depth=1` be enough to start

[openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

Wracking my brains over this one, would appreciate any pointers... Setup: Small test deployment with just 3 compute nodes, Queens on Ubuntu Bionic. The first compute node is an NFS server for /var/lib/nova/instances, and the other compute nodes mount that as NFS clients. Problem: Sometimes, when

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

Hi, On Fri, Oct 19, 2018 at 10:24 AM Giulio Fidente wrote: > On 10/14/18 5:07 PM, Emilien Macchi wrote: > > I recently wrote a blog post about how we could upgrade an host from > > Docker containers to Podman containers. > > > > >

Re: [openstack-dev] [Openstack-sigs] [all] Naming the T release of OpenStack

On Thu, Oct 18, 2018 at 05:35:39PM +1100, Tony Breeds wrote: > Hello all, > As per [1] the nomination period for names for the T release have > now closed (actually 3 days ago sorry). The nominated names and any > qualifying remarks can be seen at2]. > > Proposed Names > * Tarryall > *