[openstack-dev] [Horizon] Horizon tutorial didn`t work
Hello everyone, I`m following a tutorial of Building a Dashboard using Horizon. (link: https://docs.openstack.org/horizon/latest/contributor/tutorials/dashboard.html#tutorials-dashboard ) However, provided custom management command doesn't create boilerplate code. I typed tox -e manage -- startdash mydashboard --target openstack_dashboard/dashboards/mydashboard and the attached screenshot file is the execution result. Are there any recommendations to solve this problem? Regards. [image: result_jmlim.PNG] __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue
hi, what kind of jobs should it be? eg. unit tests, tempest, etc... On Sun, Sep 30, 2018 at 9:43 AM Miguel Lavalle wrote: > > Dear networking Stackers, > > During the recent PTG in Denver, we discussed measures to prevent patches > merged in the Neutron repo breaking Stadium and related networking projects > in general. We decided to implement the following: > > 1) For Stadium projects, we want to add non-voting jobs to the Neutron check > queue > 2) For non stadium projects, we are inviting them to add 3rd party CI jobs > > The next step is for each project to propose the jobs that they want to run > against Neutron patches. > > Best regards > > Miguel > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [kolla][octavia] Containerize the amphora-agent
I was coming to the same conclusion for a completely different goal -- baking lighter weight VMs (and eliminating a number of compatibility issues) by putting exactly what we need in containers and making the base OS irrelevant. So, I am interested in helping to do this in a way that will work well for both goals. My thought is that containerizing the agent AND using (existing?) containerized haproxy distributions, we can better standardize things between different amphora base OSes at the same time as setting up for full containerization. We should discuss further on IRC next week maybe, if we can find a good time. --Adam On Sun, Sep 30, 2018, 11:56 Hongbin Lu wrote: > Hi all, > > I am working on the Zun integration for Octavia. I did a preliminary > research and it seems what we need to do is to containerize the amphora > agent that was packaged and shipped by a VM image. I wonder if anyone > already has a containerized docker image that I can leverage. If not, I > will create one. > > Best regards, > Hongbin > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron][neutron-lib] Seeking neutron-lib developers
Dear Neutron community, As everybody knows, neutron-lib "is an OpenStack library project used by Neutron, Advanced Services, and third-party projects that aims to provide common functionality across all such consumers" ( https://docs.openstack.org/neutron-lib/latest/). In general terms, the effort in neutron-lib consists of two steps: 1. Extract common functionality from Neutron and re-home it in neutron-lib. 2. Consume the re-homed functionality by Neutron and all its related networking projects. This has been an on-going effort for several cycles and there is still a lot do. During the recent Stein PTG in Denver, the team agreed to send a message to the mailing list to invite community developers to help with this effort. If you are interested in participating, please add your name to this etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list. Once we have a group of volunteers, Boden Russel (itc: boden) has agreed to create a to-do list. Best regards Miguel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [kolla][octavia] Containerize the amphora-agent
Hi all, I am working on the Zun integration for Octavia. I did a preliminary research and it seems what we need to do is to containerize the amphora agent that was packaged and shipped by a VM image. I wonder if anyone already has a containerized docker image that I can leverage. If not, I will create one. Best regards, Hongbin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Placement extraction update
On 9/30/2018 11:02 AM, Matt Riedemann wrote: Maybe that's some conditional branch logic we can hack into devstack-gate [7] like we do for neutron? [8] I'm hoping this works: https://review.openstack.org/#/c/606853/ -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Placement extraction update
I finally got a passing neutron-grenade run in change [1]. That's the grenade change which populates the placement DB in Stein from the placement-related table contents of the nova_api DB from Rocky. It also writes out the placement.conf file for Stein before starting the Stein services. As a result, I'm +2 on Dan's mysql-migrate-db.sh script [2]. The grenade change is also dependent on three other changes for neutron [3], ironic [4] and heat [5] grenade jobs to require the openstack/placement project when zuul/devstack-gate clones its required projects before running grenade.sh. Those are just the related project grenade jobs that are hit as part of the grenade patch. There could be others I'm missing, which means projects might need to update their grenade job definitions after the grenade change merges. It looks like that could be quite a few projects [6]. If the infra/QA teams have a better idea of how to require openstack/placement in stein+ only, I'm all ears. Maybe that's some conditional branch logic we can hack into devstack-gate [7] like we do for neutron? [8] [1] https://review.openstack.org/#/c/604454/ [2] https://review.openstack.org/#/c/603234/ [3] https://review.openstack.org/#/c/604458/ [4] https://review.openstack.org/#/c/606850/ [5] https://review.openstack.org/#/c/606851/ [6] http://codesearch.openstack.org/?q=export%20PROJECTS%3D%22openstack-dev%5C%2Fgrenade%20%5C%24PROJECTS%22&i=nope&files=&repos= [7] https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L138 [8] https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L195 -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][python-novaclient] A Test issue in python-novaclient.
On 9/29/2018 10:01 PM, Tao Li wrote: I found this test is added about ten days ago in this patch https://review.openstack.org/#/c/599276/, I checked it and don’t know why it failed. I think my commit shouldn’t cause this issue. So do you any suggestion to me? Yes it must be an intermittent race bug introduced by that change for the 2.66 microversion. Since it deals with filtering based on time, we might not have a time window that is big enough (we expect to get a result of changes < $before but are getting <= $before). http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22%7C%20%20%20%20%20testtools.matchers._impl.MismatchError%3A%20%5B'create'%5D%20!%3D%20%5B'create'%2C%20'stop'%5D%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d Please report a bug against python-novaclient. The 2.66 test is based on a similar changes_since test, so we should see why they are behaving differently. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
