Team,
I announce my candidacy for, and respectfully request your support to serve as
your Magnum PTL again for the Pike release cycle.
Here are are my achievements and OpenStack experience and that make me the
best choice for this role:
* Founder of the OpenStack Containers Team
* Established
Yup, all that should be needed is to read the docs and adjust it.
"once" - print only the first occurrence of matching warnings,
regardless of location
"always" - always print matching warnings
Changing it to 'once' should gather less repeated logs; IMHO 'always'
should never be used, so tha
I love it!
Top-posting from my phone
On Jan 28, 2017 3:08 PM, "Brian Rosmaita"
wrote:
> Hello Glancers,
>
> Attached is the new draft logo of the Glance mascot. It looks to me
> like this draft captures the key features we requested (and is much more
> personable than the previous version). I
2017-01-29 1:31 GMT+08:00 Matt Riedemann :
> On 1/27/2017 3:37 AM, Alex Xu wrote:
>
>> The patches about validation the filters and sorts for servers API are
>> merged [0]. But we still have something left [1].
>>
>> The left is about the proposal of introducing the new rule
>> 'os_compute_api:ser
Graham, Sławek,
Have you seen this?
Neutron has/uses a WarningFixture:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/base.py#n161
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/tools.py#n70
Which uses filterwarnings:
http://git.openstack.org/cgit/openstac
hmmm, it says "not for usage questions" so maybe I'll just propose a change
to nova/conf/compute.py as supporting affined hosts is a perfectly valid
PRODUCTION reason for setting this (above and beyond the single node
testing.)
On Sat, Jan 28, 2017 at 5:15 PM, David Medberry
wrote:
> Hi,
>
> If
Hi,
If you allow "affinity" server via the ServerGroupAffinityFilter it looks
like you need to set allow_resize_to_same_host to true. Should I add a bit
more description that this is needed to the description (reason) in the
config file?
(Users do need to sometimes resize things that are in an af
Hello,
Thanks. I just filled bug report to oslo project:
https://bugs.launchpad.net/oslo.context/+bug/1660088
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On Sat, 28 Jan 2017, Hayes, Graham wrote:
> On 28/01/17 20:54, Sławek Kapłoński wrote:
> > Hello,
> >
> > I pushed to
Ok, progress. I've encoded my cert and key to base64 strings and specified
them in my haproxy config, and seem to be getting past the padding error.
My issue now, is that I am not seeing the cert/key in /etc/ssl/private on
the haproxy host once deployed. I'm thinking specifying the ssl cert/key
wil
On 28/01/17 20:54, Sławek Kapłoński wrote:
> Hello,
>
> I pushed today patch in Neutron to gerrit [1] and I noticed that functional
> tests are failing. In logs there is huge number of deprecation warnings
> displayed [2]. Tests are failing because of global timeout is reached and IMO
> reason
Hello Glancers,
Attached is the new draft logo of the Glance mascot. It looks to me
like this draft captures the key features we requested (and is much more
personable than the previous version). If you have a contrary opinion,
please reply quickly as Heidi Joy's team wants to have all the logos
I'm having issues with padding when trying to specify key/cert as config
options for Haproxy, and have experienced the same issue in the past, when
trying to specify key/cert for the Openstack charms. Could someone give an
example of what the correct padding of a base64 encoded ssl cert might look
Hello,
I pushed today patch in Neutron to gerrit [1] and I noticed that functional
tests are failing. In logs there is huge number of deprecation warnings
displayed [2]. Tests are failing because of global timeout is reached and IMO
reason of this timeout is this huge amount of deprecation warn
On 1/27/2017 1:24 AM, Sergey Nikitin wrote:
Hi, folks!
I'm asking a FFE for restore-vm-diagnostics [1]. There are 3 patches and
yesterday I had five +2 on them from Alex Xu, Stephen Finucane and John
Garbutt. Unfortunatly I lost 3 of them because of nits fixing. I mean
that patches are totally r
On 1/27/2017 3:37 AM, Alex Xu wrote:
The patches about validation the filters and sorts for servers API are
merged [0]. But we still have something left [1].
The left is about the proposal of introducing the new rule
'os_compute_api:servers:all_tenants_visible' which is soft enforcement.
The new
Hello All,
I am installing watcher following[1].
I have executed the commands mentioned here[2] to install the watcher.
When i execute the command 'watcher strategy list', i am getting below
exception:
AttributeError: 'module' object has no attribute 'epoll' in watcher-api.
Full stack trace of
Stackalytics cores:
I reported a bug on ownership of commits in stackalytics months ago[1]. It
seems to be caused by obsoleted email address in user default data.
In `user_processor`, it merges email addresses from `default_data.json` to
runtime storage[2]. It seems removing email address from us
17 matches
Mail list logo