Re: [openstack-dev] [nova] Usability question for the server migrations API

2017-04-15 4:38 GMT+08:00 Chet Burgess : > On Fri, Apr 14, 2017 at 1:27 PM, Matt Riedemann > wrote: > >> The GET /servers/{server_id}/migrations API only lists in-progress live >> migrations. This is an artifact of when it was originally introduced as the

[openstack-dev] [qa][gate] tempest slow - where do we execute them in gate?

Hi all, so I tried to inject a failure in a tempest test and was surprised that no gate job failed because of that: https://review.openstack.org/#/c/457102/1 It turned out that the test is not executed because we always ignore all 'slow' tagged test cases:

[openstack-dev] [keystone] Integrate Identity with LDAP

Hi team, I am trying to integrate Identity (Ocata Release) with LDAP. Afer I following this page: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/integrate_with_identity_service/sec-active-directory I failed to log in to the dashboard by entering their AD DS

Re: [openstack-dev] [nova][deployment] FYI: changes to cells v2 setup guide (pike only)

Is it strange that the 'nova service-list' and 'nova host-list' return the hosts which didn't have host mapping yet? How the user to know whether a host was added to a cell or not? 2017-04-14 23:45 GMT+08:00 Matt Riedemann : > Nova is working on adding multi-cell aware

[openstack-dev] [ceilometer]

Hello everyone I am trying to get acquainted with the Ceilometer code base. I was reading through the Telemetry Admin Guide regarding publishers and noticed that there are many deprecated publishers such as *direct*, *kafka*,

[openstack-dev] [nova][trove] deleted instances appearing in nova's server-group list

TL;DR Nova's v2 server group API list() call returns a list of members which includes deleted instances. Is this valid behavior? Should requestors make the determination that these are deleted instances and act accordingly, or is this something that changed in Nova and that Nova will fix? The

Re: [openstack-dev] [tc][elections]questions about one platform vision

FWIW, I think the Lego analogy is not actually helpful for another reason: it has vastly too many ways of combining, and (hence) no sense at all of consistency / interoperability between the different things that you can construct with it. Whereas for OpenStack I believe you are also aiming for

Re: [openstack-dev] [glance][ironic][octavia] oslo.config 4.0 will break projects' unit test

As I expect, there are some failures in periodic tasks recently [1] if we set enforce_type with True by default, we'd better fix them before we release oslo.config 4.0. Some guys had been working on this : Nova: https://review.openstack.org/455534 should fix failures tempest: