Further things that someone may want to read/try (if the below is true),
https://en.wikipedia.org/wiki/ReDoS
Joshua Harlow wrote:
Just the paranoid person in me, but is it safe to say that the filter
that you are showing here does not come from user text?
Ie these two lines don't come from a
Just the paranoid person in me, but is it safe to say that the filter
that you are showing here does not come from user text?
Ie these two lines don't come from a user input directly (without going
through some filter) do they?
On Thu, Oct 26, 2017 at 10:35:47PM -0500, Matt Riedemann wrote:
> On 10/26/2017 9:54 PM, Tony Breeds wrote:
> > Can you use RLIKE/REGEX? or is that too MySQL specific ?
>
> I thought about that, and my gut response is 'no' because even if it does
> work for mysql, I'm assuming regex pattern
On 10/26/2017 9:54 PM, Tony Breeds wrote:
Can you use RLIKE/REGEX? or is that too MySQL specific ?
I thought about that, and my gut response is 'no' because even if it
does work for mysql, I'm assuming regex pattern matching for postgresql
is different. And then you have different API
Hi John,
>@Nisha I think that should largely allow you to construct the same
behavior you have today, or am I totally missing what you are wanting to do?
Yes, i agree that qualitative capabilities are covered by your spec and
will give us the behaviour as its today with your spec implemented.
Hi Akihiro,
Much appreciated for giving us the right direction.
We are totally on same page as you & will let you know when
heat-dashboard is ready.
> AFAIK, the only patch which landed after the heat-dashboard repo was created
> is
> https://review.openstack.org/#/c/498838/
Thanks! will pick
On Thu, Oct 26, 2017 at 09:23:50PM -0500, Matt Riedemann wrote:
> Nova has had this long-standing known performance issue if you're filtering
> a large number of instances by IP. The instance IPs are stored in a JSON
> blob in the database so we don't do filtering in SQL. We pull the instances
>
On Oct 26, 2017, at 6:57 PM, Wan-yen Hsu wrote:
> In Nisha's message, "capabilities" refers to "ComputeCapabilitiesFilter".
> "capabilities" provides a lot of flexibility for scheduling. It supports
> qualitative as well as quantitative attributes. It supports a
On Thu, Oct 26, 2017 at 10:23 PM, Matt Riedemann
wrote:
> Nova has had this long-standing known performance issue if you're
> filtering a large number of instances by IP. The instance IPs are stored in
> a JSON blob in the database so we don't do filtering in SQL. We pull
Nova has had this long-standing known performance issue if you're
filtering a large number of instances by IP. The instance IPs are stored
in a JSON blob in the database so we don't do filtering in SQL. We pull
the instances out of the database, deserialize the JSON and then apply a
regex
In Nisha's message, "capabilities" refers to "ComputeCapabilitiesFilter".
"capabilities" provides a lot of flexibility for scheduling. It supports
qualitative as well as quantitative attributes. It supports a variety of
operators such as ">=", "<", "=", etc. For instance, with "capabilities",
On Thu, Oct 26, 2017 at 01:36:01PM -0700, Boris Pavlovic wrote:
> Hi,
>
> Someone somehow deleted 0.9.* branches from GitHub repo
> https://github.com/openstack/rally
> A lot of end users are using these branches and are affected by this
> change.
>
> Can someone help to restore them?
So sorry
On 10/25/2017 12:55 PM, Mathieu Gagné wrote:
Hi,
On Wed, Oct 25, 2017 at 10:17 AM, Loo, Ruby wrote:
Hello ironic'ers,
A while ago, we approved a spec to add node tag support to ironic [1]. The
feature itself did not land yet (although some of the code has). Now that
the
Hi,
Someone somehow deleted 0.9.* branches from GitHub repo
https://github.com/openstack/rally
A lot of end users are using these branches and are affected by this
change.
Can someone help to restore them?
Best regards,
Boris Pavlovic
Excerpts from Sean McGinnis's message of 2017-10-26 13:46:23 -0500:
> With much anticipation, our regular release countdown email.
>
> Development Focus
> -
>
> Now that the Queens-1 milestone is passed*, teams should now be focused on
> feature development and completion of
On Oct 26, 2017, at 9:52 AM, Doug Hellmann wrote:
>
> It would also be good to see some discussion of those issues outside
> of campaign periods. Some of the questions, like the one about user
> perspectives held by the candidates, were clearly meant to elicit
> more info
On Oct 25, 2017, at 10:36 PM, Tony Breeds wrote:
> The whole election takes close to 3 weeks of officials time so I'd like
> to ask we be mindful of that before we extend things too much
There isn’t really a need for the self-nomination period to be very long.
Announce
With much anticipation, our regular release countdown email.
Development Focus
-
Now that the Queens-1 milestone is passed*, teams should now be focused on
feature development and completion of release goals [0].
[1] https://governance.openstack.org/tc/goals/queens/index.html
*
Hi all,
As previously discussed over, we'll move the weekly Congress team meeting
to the new time of Fridays 02:30 UTC, with the first new meeting on
November 3rd. Same channel #openstack-meeting.
Just to reiterate, there will be no meeting on November 2nd 00:00 (old
meeting time).
As always,
On 26/10/17 10:52 -0400, Doug Hellmann wrote:
Excerpts from Jeremy Stanley's message of 2017-10-26 13:30:53 +:
On 2017-10-26 14:42:35 +0200 (+0200), Flavio Percoco wrote:
[...]
> I personally don't think the campaing period was too short. I saw
> enough interactions between candidates and
Greetings OpenStack community,
Another short meeting this week. Participants have very busy radar; can't see for the
trees, nor the mixed metaphors. The main topic of discussion is the work required to
prepare for summit, where there will be an API-SIG forum session [5]. Also a bug has been
Hi Kaz,
Thanks for sharing the current status of heat-dashboard.
Queens-2 sounds a reasonable milestone.
I summarize the near-future below. Right?
- heat-dashboard team is preparing for heat dashboard split-out.
The horizon parity (including stability) is the current focus.
- Heat related
Hi everyone,
In case you missed the news last week, it's now confirmed: the next PTG
will happen in Dublin (Ireland), the week of February 26, 2018.
We are still working on locking down the exact location, so please stay
tuned for more details. But you can already mark this date and location
in
Excerpts from Jeremy Stanley's message of 2017-10-26 13:30:53 +:
> On 2017-10-26 14:42:35 +0200 (+0200), Flavio Percoco wrote:
> [...]
> > I personally don't think the campaing period was too short. I saw
> > enough interactions between candidates and the rest of the
> > community, which was
On 2017-10-26 14:42:35 +0200 (+0200), Flavio Percoco wrote:
[...]
> I personally don't think the campaing period was too short. I saw
> enough interactions between candidates and the rest of the
> community, which was useful for me to make up my mind and vote.
> This is, of course, my own view and
On 26/10/17 11:27 +0200, Thierry Carrez wrote:
Tony Breeds wrote:
On Wed, Oct 25, 2017 at 10:06:46PM -0400, David Moreau Simard wrote:
Was it just me or did the "official" period for campaigning/questions was
awfully short ?
The schedule [1] went:
TC Campaigning: (Start) Oct 11, 2017 23:59
Dear all,
today we had our QA office hours.
We will have the next office hours in two weeks from now.
The IRC report [0] and full log [1] are available through meetbot.
Below a details of the bugs we triaged today.
Kind regards,
Andrea Frittoli (andreaf)
Bug #1715859 in tempest: "After
On 10/26/2017 06:14 AM, Emilien Macchi wrote:
On Wed, Oct 25, 2017 at 1:59 PM, Emilien Macchi wrote:
Quick update before being afk for some hours:
- Still trying to land https://review.openstack.org/#/c/513701 (thanks
Paul for promoting it in gate).
Landed.
- Disabling
Hi Tony and folks,
I missed the original thread (had read just [charms][fuel][Packaging-Deb]
tags), so disappeared branch surprised me a lot.
stable/0.9 branch of Rally project was created for supporting the previous
major release (last week, 0.9 was the current major release).
We released
On 10/26/2017 10:17 AM, Pranav Sarwate wrote:
> How do I debug this further? What logs can I look at? Also, it would be
> great if someone can validate that we are using the correct reference link.
Hi Pranav,
I can't help you about the validation, but I bet the error at that stage
means that
Tony Breeds wrote:
> On Wed, Oct 25, 2017 at 10:06:46PM -0400, David Moreau Simard wrote:
>> Was it just me or did the "official" period for campaigning/questions was
>> awfully short ?
>>
>> The schedule [1] went:
>> TC Campaigning: (Start) Oct 11, 2017 23:59 UTC (End) Oct 14, 2017 23:45
>> UTC
Thank you for working on this!
I know it is needed to unblock development of tripleo. I have though a
few comments inline.
On 10/26/17 6:14 AM, Emilien Macchi wrote:
On Wed, Oct 25, 2017 at 1:59 PM, Emilien Macchi wrote:
Quick update before being afk for some hours:
-
Hi,
I am currently attempting to deploy containerized overcloud using steps
documented @
https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/overcloud.html
. But the overcloud deployment fails at step3 of controller configuration.
Documenting the steps and error
Hello,
i see this in impl_rabbit.py
# NOTE(sileht): if purpose is PURPOSE_LISTEN
# the consume code does the heartbeat stuff
# we don't need a thread
self._heartbeat_thread = None
if purpose == rpc_common.PURPOSE_SEND:
34 matches
Mail list logo