Re: [openstack-dev] [Fuel] FFE for Ubuntu bootstrap

+1 to extend FFE by 1 day Nastya. On Tue, Dec 8, 2015 at 9:51 PM, Dmitry Klenov wrote: > Hi Folks, > > I would like to ask for FFE extension by 1 day. Reason: we didn't have > green BVT today due to BUD network connectivity issue. > > Commits to merge: > >-

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

I just noticed you suggested " "; if that's the prevailing form, then I'd suggest "Change password (self-service)". On Tue, Dec 8, 2015 at 9:31 PM, Dolph Mathews wrote: > This is implemented as a "self-service user password change" on the v2 > public API. The user is

[openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

Hi All: Just to inform Steve and all the folks who brought up this talk ;We did some benchmarking using wsgi, apache and nginx for keystone with mysql as token backend and we got following results on Juno version. Hence I am just giving you brief highlight about the results we got. spawning

[openstack-dev] [cinder] Dependencies of snapshots on volumes

Hi all, Currently when deleting a volume, it checks whether there are snapshots created from it. If yes deletion is prohibited. But it allows to extend the volume, no check whether there are snapshots from it. The two behaviors in Cinder are not consistent from my viewpoint. In backend

[openstack-dev] Mesos Conductor using container-create operations

Hi, As we have discussed in last meeting, we cannot continue with changes in container-create[1] as long as we have suitable use case. But I honestly feel to have some kind of support for mesos + marathon apps, because magnum supports COE related functionalities for docker swarm

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-09 6:02 GMT+09:00 Andrew Laski : >> >> I'm fine with a new RPC call for getting the schema, but as I explained, I >> think the schema should be accepting all the in-tree filter hints (ie. >> nova.scheduler.filters.all_filters method), not only those which are enabled >>

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 3 December 2015 at 02:21, Thierry Carrez wrote: > Armando M. wrote: > > On 2 December 2015 at 01:16, Thierry Carrez > > wrote: > >> Armando M. wrote: > >> >> One solution is, like you mentioned, to make some

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

This is implemented as a "self-service user password change" on the v2 public API. The user is required to have a token for the password they are changing, and is required to know the original password before a new one can be set. There is a similar "administrative password reset" call on the v2

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

Hi Dolph, Thank you for your quick feedback, 2015-12-09 12:33 GMT+09:00 Dolph Mathews : > I just noticed you suggested " "; if that's the prevailing > form, then I'd suggest "Change password (self-service)". Nice title for the api-site. Now Tempest's method is

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Hi Sylvain, 2015-12-04 17:48 GMT+09:00 Sylvain Bauza : >> >> That leaves the out-of-tree discussion about custom filters and how we >> could have a consistent behaviour given that. Should we accept something in >> a specific deployment while another deployment could 401 against

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

+1 On Tue, Dec 8, 2015 at 4:15 PM, Matt Fischer wrote: > +1 > > On Tue, Dec 8, 2015 at 2:07 PM, Rich Megginson > wrote: > >> On 12/08/2015 09:49 AM, Emilien Macchi wrote: >> >> Hi, >> >> Back in "old days", Cody was already core on the modules, when

Re: [openstack-dev] [Fuel] Patch size limit

Hey Igor! Thank you for the response! On 7 December 2015 at 12:03, Igor Kalnitsky wrote: > Hey Andrii, > > I'm totally agree with you about contribution guides, except one thing > - we need and should force users to split huge patches into set of > small ones. > I

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

Hi Flavio, On Tue, Dec 8, 2015 at 9:52 PM, Flavio Percoco wrote: > > > Oh, I meant ocasionally. Whenever a missing test for an API is found, > it'd be easy enough for the implementer to sohw up at the meeting and > bring it up. >From my experience as a Tempest reviewer, I'd

[openstack-dev] [tripleo] Monitoring support

Hi, I've been spending some time on deploying monitoring in TripleO with Sensu. I recently made good progress. If you are interested by this work, feel free to look an etherpad I started [1]. Feel free to comment, review, and give any feedback, Thank you, [1]

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

+1 On Tue, Dec 8, 2015 at 2:07 PM, Rich Megginson wrote: > On 12/08/2015 09:49 AM, Emilien Macchi wrote: > > Hi, > > Back in "old days", Cody was already core on the modules, when they were > hosted by Puppetlabs namespace. > His contributions [1] are very valuable to the

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev tohorizon-core

David and all the fellow Horizoneers, Thank you very much for the trust you put in me :). I'll do my best to be up to it! On Tue, 8 Dec 2015 at 22:47, David Lyle wrote: > Since the results are unanimous, closing early. Welcome Timur! > > David > > On Thu, Dec 3, 2015 at

<    1   2