Re: [openstack-dev] [keystone] Feature Status and Exceptions

On Fri, Jul 13, 2018, at 9:19 PM, Lance Bragstad wrote: > Hey all, > > As noted in the weekly report [0], today is feature freeze for > keystone-related specifications. I wanted to elaborate on each > specification so that our plan is clear moving forward. > > *Unified Limits** > ** > *I propose

Re: [openstack-dev] [nova]API update week 5-11

Thank you very much for the review and updates during the weekends. On Sat, Jul 14, 2018 at 4:05 AM Matt Riedemann wrote: > On 7/11/2018 9:03 PM, Zhenyu Zheng wrote: > > 2. Abort live migration in queued state: > > - > https://blueprints.launchpad.net/nova/+spec/abort-live-migration-in-q

Re: [openstack-dev] Need help on this neutron-server start error with vmware_nsx plugin enable

Hi Tong, after change vmware_nsx to vmware_nsxv, still can't load, here are the logs: 2018-07-16 09:56:35.889 10814 DEBUG oslo_concurrency.lockutils [-] Lock "plugin-directory" acquired by "neutron_lib.plugins.directory._create_plu gin_directory" :: waited 0.000s inner /usr/lib/python2.7/site-pack

Re: [openstack-dev] [tripleo] Rocky blueprints

On Fri, Jul 13, 2018 at 10:12:04AM +1000, Tony Breeds wrote: > On Wed, Jul 11, 2018 at 10:39:30AM -0600, Alex Schultz wrote: > > Currently open with pending patches (may need FFE): > > - https://blueprints.launchpad.net/tripleo/+spec/multiarch-support > > I'd like an FFE for this, the open reviews

Re: [openstack-dev] [tripleo] Plan to switch the undercloud to be containerized by default

On Sun, Jul 15, 2018 at 4:38 PM Emilien Macchi wrote: > On Tue, Jul 10, 2018, 7:57 PM Emilien Macchi, wrote: > >> with [tripleo] tag... >> >> On Tue, Jul 10, 2018 at 7:56 PM Emilien Macchi >> wrote: >> >>> This is an update on where things are regarding $topic, based on >>> feedback I've got fr

Re: [openstack-dev] [tripleo] Plan to switch the undercloud to be containerized by default

On Tue, Jul 10, 2018, 7:57 PM Emilien Macchi, wrote: > with [tripleo] tag... > > On Tue, Jul 10, 2018 at 7:56 PM Emilien Macchi wrote: > >> This is an update on where things are regarding $topic, based on feedback >> I've got from the work done recently: >> >> 1) Switch --use-heat to take a bool

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

Hi Remo, Attached are templates I used for the deployment. They are based on a deployment we did with OSP11. I made the changes for it to work with OSP13. I do think it's the roles_data.yaml file that is causing the error because if remove the " -r $TEMPLATES_DIR/roles_data.yaml" from the deploym

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

I still think there is something wrong with some of your yaml, the roles_data is elaborating based on what your yaml files are. Can you share your deployment script did you make any of the yaml files yourself? Remo > On Jul 15, 2018, at 8:57 AM, Remo Mattei wrote: > > Here is the one I use

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

Here is the one I use roles_data.yaml Description: Binary data On Jul 15, 2018, at 8:02 AM, Samuel Monderer wrote:It seems that the problem is in my roles_data.yaml file but I don't see what is the problemI've attached the file.On Sun, Jul 15, 2018 at 12:46 AM Remo M

Re: [openstack-dev] [Zun] Zun UI questions

Hi Amy, The wrong Keystone URI might be due to the an issue of the devstack plugins. I have proposed fixes [1] [2] for that. Thanks for the suggestion about adding a note for uninstalling pip packages. I have created a ticket [3] for that. [1] https://review.openstack.org/#/c/582799/ [2] https://

Re: [openstack-dev] [tripleo] Mistral workflow cannot establish connection

It seems that the problem is in my roles_data.yaml file but I don't see what is the problem I've attached the file. On Sun, Jul 15, 2018 at 12:46 AM Remo Mattei wrote: > It is a bad line in one of your yaml file. I would check them. > > Sent from my iPad > > On Jul 14, 2018, at 2:25 PM, Samuel M

Re: [openstack-dev] [Zun] Zun UI questions

Hongbin, Doing the pip uninstall did the trick with the Flask version, when running another debug I did notice an incorrect IP for the Keystone URI and have restarted the machines networking and cleaned up the /etc/hosts. When doing a second stack, I did need to uninstall the pip packages again f