On 03/06/2015 03:24 AM, Dillon, Nathaniel wrote:
> Awesome, thanks everyone! Very excited to help out with the great work
> already going on!
Welcome, Nathaniel!
Andreas
> Nathaniel
>
>> On Mar 5, 2015, at 5:05 PM, Bryan D. Payne wrote:
>>
>> Thanks everyone. I've added Nathaniel to security
On 05/03/15 19:49, Adam Young wrote:
>
> I'd like to drop port 5000 all-together, as we are using a port assigned
> to a different service. 35357 is also problematic as it is in the
> middle of the Ephemeral range. Since we are talking about running
> everything in one web server anywya, using
Hi All,
The OpenStack Group Based Policy team of contributors has submitted a
proposal [1] to add “Group Based Policy” as a project in the OpenStack
namespace in accordance with the new governance changes [2]. We would
request the TC to take note and consider this proposal during the next
meeting.
+1 on Nathan!
Andreas
On Thu, Mar 5, 2015 at 10:14 PM, Bryan D. Payne wrote:
> To security-doc core and other interested parties,
>
> Nathaniel Dillon has been working consistently on the security guide since
> our first mid-cycle meet up last summer. In that time he has come to
> understand t
I meant Nathaniel - sorry for the typo,
Andreas
On Fri, Mar 6, 2015 at 7:18 AM, Andreas Jaeger wrote:
> +1 on Nathan!
>
> Andreas
>
> On Thu, Mar 5, 2015 at 10:14 PM, Bryan D. Payne wrote:
>
>> To security-doc core and other interested parties,
>>
>> Nathaniel Dillon has been working consisten
Hi all,
I would also vote for (A) with 1500 UTC which is 23:00 in Beijing time
-:)
On Fri, Mar 6, 2015 at 1:22 PM, Mohammad Hanif wrote:
> Hi all,
>
> I would also vote for (C) with 1600 UTC or later. This will hopefully
> increase more participation from the Pacific time zone.
>
> Th
Hi Sean,
That is very nice idea to keep only 1 set of tests and run those twice via
tox.
Actually my main goal was-
- 1. Create clean sample file structure for V2. V2.1 and micro-versions
Something like below-
api_samples/
extensions/
v2.0/ - v2 sample files
Hi all,
I would also vote for (C) with 1600 UTC or later. This will hopefully
increase more participation from the Pacific time zone.
Thanks,
—Hanif.
From: Mathieu Rohon
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, March 5, 2015 at 1:52 AM
To: "Open
On Wed, Mar 4, 2015 at 12:10 PM, ozamiatin wrote:
> Hi,
>
> By this e-mail I'd like to start a discussion about current zmq driver
> internal design problems I've found out.
> I wish to collect here all proposals and known issues. I hope this
> discussion will be continued on Liberty design summi
Hi all, actually I'm writing the same mail topic for zeromq driver,
but I haven't done it yet. Thank you for proposing this topic,
ozamiatin.
1. ZeroMQ functionality
Actually I proposed a session topic in the coming summit to show our
production system, named 'Distributed Messaging System for Ope
I commented on this in your patch (https://review.openstack.org/#/c/161837/)
and posted a patch to help you along -
https://review.openstack.org/#/c/161945/. This patch will
make "create_snapshot" and "create_volume_from_snapshot" method use
snapshot objects. By using snapshot objects in both met
Awesome, thanks everyone! Very excited to help out with the great work already
going on!
Nathaniel
> On Mar 5, 2015, at 5:05 PM, Bryan D. Payne wrote:
>
> Thanks everyone. I've added Nathaniel to security-doc core. Welcome
> Nathaniel!
>
> Cheers,
> -bryan
___
Ihar, please see responses (inline).
-amrith
| -Original Message-
| From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
| Sent: Thursday, March 05, 2015 9:43 AM
| To: openstack-dev@lists.openstack.org
| Subject: Re: [openstack-dev] [Trove] request to backport the fix for bug
| 1333852 to j
Thank you very much for in-depth discussion about this topic, @Nikola and
@Sylvain.
I agree that we should solve the technical debt firstly, and then make the
scheduler better.
Best Regards.
2015-03-05 21:12 GMT+08:00 Sylvain Bauza :
>
> Le 05/03/2015 13:00, Nikola Đipanov a écrit :
>
> On 03/
Attila Fazekas wrote:
> I see lot of improvements,
> but cPython is still cPython.
>
> When you benchmarking query related things, please try to
> get the actual data from the returned objects
that goes without saying. I’ve been benching SQLAlchemy and DBAPIs for many
years. New performance i
Marcus,
Don’t turn off ci, because then you could miss another regression.
Instead, simply exclude that test case:
e.g.
export
DEVSTACK_GATE_TEMPEST_REGEX="^(?=.*tempest.api.volume)(?!.*test_snapshots_actions).*"
Ramy
From: Marcus Vinícius Ramires do Nascimento [mailto:marcus...@gmail.com]
Se
Thanks everyone. I've added Nathaniel to security-doc core. Welcome
Nathaniel!
Cheers,
-bryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:uns
stuck with following
https://zenodo.org/record/11982/files/CERN_openlab_Luca_Tartarini.pdf
when i tried, python ecp.py -d testshib
https://Centos-SAML:5000/v3/OSFEDERATION/identity_providers/testshib/protocols/saml2/auth
myself
im getting
send: 'GET /v3/OSFEDERATION/identity_providers/testshib
On Thu, Mar 5, 2015, at 03:15 PM, Dr. Jens Rosenboom wrote:
> Am 05/03/15 um 17:52 schrieb Doug Hellmann:
> >
> >
> > On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
> >> The clients in general do not back port patches. Someone should work with
> >> stable-maint to raise the cap in Icehouse
I think yes, it does. But I mean that now we're writing a document called
Glance Review Guidelines
https://docs.google.com/document/d/1Iia0BjQoXvry9XSbf30DRwQt--ODglw-ZTT_5RJabsI/edit?usp=sharing
and it has a section "For cores". It's easy to include some concrete rules
there to add more clarity.
“extra_info” is no longer a key in the stats pool, nor the “physical_function”.
If you check pci/stats.py, the keys are pool_keys = ['product_id',
'vendor_id', 'numa_node’] plus whatever tags are used in the whitelist. So I
believe it’s something like this:
"os-pci:pci_stats": [
{
"count": 5
Paul, you are right that the 'extra_info' should not be in the
os-pci:pci_stats, since it's not part of 'pool-keys' anymore, but I'm not sure
if both 'key1' and 'phys_function' will be part of the pci_stats.
Thanks
--jyh
From: Murray, Paul (HP Cloud) [mailto:pmur...@hp.com]
Sent: Thursday, Marc
On 03/05/2015 10:14 PM, Bryan D. Payne wrote:
> I'd like to bring him on as a core member of security-doc so that he can
> help with the review and approval process for new changes to the book.
> Please chime in with your agreement or concerns.
+1.
Christian.
___
Sounds great! Thanks for growing the team, too!
On Thu, Mar 5, 2015 at 3:14 PM, Bryan D. Payne wrote:
> To security-doc core and other interested parties,
>
> Nathaniel Dillon has been working consistently on the security guide since
> our first mid-cycle meet up last summer. In that time he ha
On 03/04/2015 07:48 PM, GHANSHYAM MANN wrote:
> Hi Sean,
>
> Yes having V3 directory/file names is very confusing now.
>
> But current v3 sample tests cases tests v2.1 plugins. As /v3 url is
> redirected to v21 plugins, v3 sample tests make call through v3 url and
> test v2.1 plugins.
>
> I thi
On 03/05/2015 12:02 AM, Nikhil Komawar wrote:
> The python-glanceclient release management team is pleased to announce:
> python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th
> around 04:56 UTC.
>
> For more information, please find the details at:
>
>
> https://lau
Hello
I'm a developer at SAP and interested on understanding How Openstack works. I
would really appreciate if some of you can explain the following questions I
have.
1. How we connect certain version of Openstack with its module versions?
Eg: Openstack Juno and Nova folsom-rc3
2.
On 05/03/2015 21:37, "Nathan Kinder" wrote:
>
>
>On 03/05/2015 01:14 PM, Bryan D. Payne wrote:
>> To security-doc core and other interested parties,
>>
>> Nathaniel Dillon has been working consistently on the security guide
>> since our first mid-cycle meet up last summer. In that time he has c
On 03/05/2015 01:14 PM, Bryan D. Payne wrote:
> To security-doc core and other interested parties,
>
> Nathaniel Dillon has been working consistently on the security guide
> since our first mid-cycle meet up last summer. In that time he has come
> to understand the inner workings of the book an
To security-doc core and other interested parties,
Nathaniel Dillon has been working consistently on the security guide since
our first mid-cycle meet up last summer. In that time he has come to
understand the inner workings of the book and the doc process very well.
He has also been a consistent
Hi,
Also, in either Gerrit's web UI or Gertty, there is an option for
displaying unified diffs, rather than side-by-side (it's a link on the
change page in Gerrit, and a config file option in Gertty). I do not
know if that would be helpful, but would be happy to learn.
Thanks,
Jim
I have submitted a proposal[0] to include OpenStackClient as an official
OpenStack project. It has existed in the git openstack/ namespace since
the beginning of the project.
In addition we propose to include two library repos that are primarily used
for client support: openstack/cliff and stackf
Hi John,
I’m not visually impaired myself, but have you taken a look at Gertty? It’s a
console-based interface so you may be able to take advantage of other console
customizations you’ve made (font sizing for example) and it has options that
allow you to set color palettes (e.g. to increase co
Hi all,
On Wed, Mar 04, 2015 at 10:52:10AM -0330, Brent Eagles wrote:
> Hi all,
> > Thanks Maxime. I've made some updates to the etherpad.
> > (https://etherpad.openstack.org/p/nova_vif_plug_script_spec)
> > I'm going to start some proof of concept work these evening. If I get
> > anything wor
I see lot of improvements,
but cPython is still cPython.
When you benchmarking query related things, please try to
get the actual data from the returned objects and try to do
something with data what is not expected to be optimized out even by
a smarter compiler.
Here is my play script and severa
On Thu, Mar 5, 2015, at 02:31 PM, Steve Martinelli wrote:
> We are thrilled to announce the first official release of oslo.policy:
>
> oslo.policy 0.3.0: Oslo common policy enforcement
>
> The main driving factor behind the graduation work was to have the
> security sensitive policy code m
Am 05/03/15 um 17:52 schrieb Doug Hellmann:
On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client break
We are pleased to announce the release of:
oslo.vmware 0.11.0: Oslo VMware library for OpenStack projects
For more details, please see the git log history below and:
http://launchpad.net/oslo.vmware/+milestone/0.11.0
Please report issues through launchpad:
http://bugs.launchpad.net/osl
We are chuffed to announce the release of:
oslo.context 0.2.0: oslo.context library
This release includes a fix for a stability issue in nova’s
unit tests.
For more details, please see the git log history below and:
http://launchpad.net/oslo.context/+milestone/0.2.0
Please report issues th
On Thu, Mar 05, 2015 at 07:39:23PM +, Murray, Paul (HP Cloud) wrote:
> Hi All,
>
> I know Yunhong Jiang and Daniel Berrange have been involved in the following,
> but I thought it worth sending to the list for visibility.
>
> While writing code to convert the resource tracker to use the Comp
Hello folks,
I¹m curious what tools visually impaired OpenStack contributors have found
helpful for performing Gerrit reviews (the UI is difficult to scan,
especially for in-line code comments) and for Python development in
general?
Thanks,
John
_
Hi All,
I know Yunhong Jiang and Daniel Berrange have been involved in the following,
but I thought it worth sending to the list for visibility.
While writing code to convert the resource tracker to use the ComputeNode
object realized that the api samples used in the functional tests are not th
We are thrilled to announce the first official release of oslo.policy:
oslo.policy 0.3.0: Oslo common policy enforcement
The main driving factor behind the graduation work was to have the
security sensitive policy code managed in a library. Should a CVE level
defect arise, releasing a new v
I'm trying to get a grip on what the HTTPD configuration should be for
Horizon in order for it to use HTTPS. This rally should be the default,
but the devstack and puppet choice of putting the Horizon config inside
a Virtualhoat *:80 section in the config file makes it tricky. If I
remove th
- Original Message -
> To turn this stuff off, you don't need to revert. I'd suggest just
> setting the namespace contants to None, and that will result in the same
> thing.
>
> http://git.openstack.org/cgit/openstack/neutron/tree/neutron/common/constants.py#n152
>
> It's definitely a
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Wednesday, March 4, 2015 9:56 AM
> To: Jiang, Yunhong
> Cc: openstack-dev@lists.openstack.org; Xu, Hejie
> Subject: Re: [nova][libvirt] The None and 'none' for CONF.libvirt.cpu_mode
>
> On Wed, Mar 04, 20
Am 05/03/15 um 17:37 schrieb Ian Cordasco:
The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client breaking other projects.
Proposals can be made though and ideal
On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
> The clients in general do not back port patches. Someone should work with
> stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
> that those caps were added due to the client breaking other projects.
> Proposals can be ma
To turn this stuff off, you don't need to revert. I'd suggest just
setting the namespace contants to None, and that will result in the same
thing.
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/common/constants.py#n152
It's definitely a non-backwards compatible change. That was a
The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client breaking other projects.
Proposals can be made though and ideally, openstack/requirements’ gate
jobs will ca
Since the first microversion is merged (
https://review.openstack.org/#/c/140313/),
please, pay attention to a novaclient upgrade to work with microversions (
https://review.openstack.org/#/c/152569/)
On Mon, Mar 2, 2015 at 2:30 PM, Sean Dague wrote:
> This change for the additional attributes
Am 05/03/15 um 06:02 schrieb Nikhil Komawar:
The python-glanceclient release management team is pleased to announce:
python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th
around 04:56 UTC.
The release includes a bugfix for [1], which is affecting us in
Icehouse, most
I worked on bug [1] and pushed change request [2] and I got Ryu CI check
failing [5], because flat_networks is not set in config. For vlan networks
empty list in 'network_vlan_ranges' means that no physical networks are
allowed [3], for flat networks there is only help string for config option
[4]
Hi all!
I've made a bug fix release for ironic-discoverd today, and it's
available on PyPI! Two issues fixed:
* Authentication was too strict, and it wasn't possible to talk to the
API using Ironic service user. Unfortunately fixing it lead to a new
dependency on keystonemiddleware and new con
On Thu, Mar 5, 2015 at 9:29 AM, Salvatore Orlando
wrote:
> Considering my current load I expect code to be ready by wednesday March
> 11th.
> Maybe we can say that we can grant a FFE as long as the code makes it - in
> full - by that date?
>
> That's reasonable to me. Consider it done!
Kyle
>
On Thu, Mar 5, 2015 at 9:31 AM, Oleg Bondarev
wrote:
>
>
> On Thu, Mar 5, 2015 at 6:03 PM, Kyle Mestery wrote:
>
>> On Thu, Mar 5, 2015 at 3:29 AM, Salvatore Orlando
>> wrote:
>>
>>> I was hoping to push code today for [1], but unfortunately I got caught
>>> by something else during this week a
Sorry to resurrect this almost a year later! I've recently run into this
issue, and it does make logging into Windows instances, via the console,
quite challenging.
On Fri, Jun 6, 2014 at 3:46 PM, Ben Nemec wrote:
> This sounds like a reasonable thing to open a bug against Horizon on
> Launchpad
On Thu, Mar 5, 2015 at 6:03 PM, Kyle Mestery wrote:
> On Thu, Mar 5, 2015 at 3:29 AM, Salvatore Orlando
> wrote:
>
>> I was hoping to push code today for [1], but unfortunately I got caught
>> by something else during this week and I'll miss the code proposal deadline.
>>
>> I would like to appl
Considering my current load I expect code to be ready by wednesday March
11th.
Maybe we can say that we can grant a FFE as long as the code makes it - in
full - by that date?
Salvatore
On 5 March 2015 at 16:03, Kyle Mestery wrote:
> On Thu, Mar 5, 2015 at 3:29 AM, Salvatore Orlando
> wrote:
>
On Thu, Mar 5, 2015, at 06:59 AM, Alexis Lee wrote:
> Doug Hellmann said on Wed, Mar 04, 2015 at 11:10:31AM -0500:
> > I used to use email to track such things, but I have reached the point
> > where keeping up with the push notifications from gerrit would consume
> > all of my waking time.
>
>
On Thu, Mar 5, 2015 at 3:29 AM, Salvatore Orlando
wrote:
> I was hoping to push code today for [1], but unfortunately I got caught by
> something else during this week and I'll miss the code proposal deadline.
>
> I would like to apply for a FFE; however, since I've experienced FFEs in
> previous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/05/2015 11:35 AM, Mikhail Fedosin wrote:
> Yes, it's absolutely right. For example, Nova and Neutron have
> official rules for that:
> https://wiki.openstack.org/wiki/Nova/CoreTeam where it says: "A
> member of the team may be removed at any tim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not being involved in trove, but some general comments on backports.
On 03/04/2015 08:33 PM, Amrith Kumar wrote:
> There has been a request to backport the fix for bug 1333852
> (https://bugs.launchpad.net/trove/+bug/1333852) which was fixed in
> Kil
Why do we need that, by the way?
REST API tests will cover database access, and database is not used for
anything else than API anyway. Additional DB layer will bring additional
complexity which we will consume time to maintain it. So if we do not
know why exactly we need such layer, I think we sh
Le 05/03/2015 13:00, Nikola Đipanov a écrit :
On 03/04/2015 09:23 AM, Sylvain Bauza wrote:
Le 04/03/2015 04:51, Rui Chen a écrit :
Hi all,
I want to make it easy to launch a bunch of scheduler processes on a
host, multiple scheduler workers will make use of multiple processors
of host and enh
Hi all,
We had our first logging workgroup meeting [1] yesterday where we agreed 3 main
priorities for the group to focus on. Please review and provide your feedback:
1) Educating the community About the Logging Guidelines spec
a.
http://specs.openstack.org/openstack/openstack-spec
On 03/04/2015 09:23 AM, Sylvain Bauza wrote:
>
> Le 04/03/2015 04:51, Rui Chen a écrit :
>> Hi all,
>>
>> I want to make it easy to launch a bunch of scheduler processes on a
>> host, multiple scheduler workers will make use of multiple processors
>> of host and enhance the performance of nova-sch
Doug Hellmann said on Wed, Mar 04, 2015 at 11:10:31AM -0500:
> I used to use email to track such things, but I have reached the point
> where keeping up with the push notifications from gerrit would consume
> all of my waking time.
Jim said if his patch was auto-abandoned, he would not find out. T
On 03/04/2015 07:48 PM, GHANSHYAM MANN wrote:
> Hi Sean,
>
> Yes having V3 directory/file names is very confusing now.
>
> But current v3 sample tests cases tests v2.1 plugins. As /v3 url is
> redirected to v21 plugins, v3 sample tests make call through v3 url and
> test v2.1 plugins.
>
> I thi
No doubt about it!
+1 Cheers for a new extremely good core member!
Thanks,
Edgar
From: Kyle Mestery mailto:mest...@mestery.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, March 4, 2015 at 11:42 AM
To: "
Yes, it's absolutely right. For example, Nova and Neutron have official
rules for that:
https://wiki.openstack.org/wiki/Nova/CoreTeam
where it says: "A member of the team may be removed at any time by the PTL.
This is typically due to a drop off of involvement by the member such that
they are no lo
Update:
Cinder - GlusterFS CI job (ubuntu based) was added as experimental (non
voting) to cinder project [1]
Its running successfully without any issue so far [2], [3]
We will monitor it for few days and if it continues to run fine, we will
propose a patch to make it check (voting)
[1]: http
My BP aims is launching multiple nova-scheduler processes on a host, like
nova-conductor.
If we run multiple nova-scheduler services on separate hosts, that will
work, forking the multiple nova-scheduler
child processes on a host that will work too? Different child processes had
different HostStat
On 3/4/15 11:31 PM, Thierry Carrez wrote:
Flavio Percoco wrote:
[...]
I personally don't think adding new cores without cleaning up that
list is something healthy for our community, which is what we're
trying to improve here. Therefore I'm still -2-W on adding new folks
without removing non-acti
Hi,
I'm fine with C) and 1600 UTC would be more adapted for EU time Zone :)
However, I Agree that neutron-vpnaas meetings was mainly focus on
maintaining the current IPSec implementation, by managing the slip out,
adding StrongSwan support and adding functional tests.
Maybe we will get a broader
Flavio Percoco wrote:
> [...]
> I personally don't think adding new cores without cleaning up that
> list is something healthy for our community, which is what we're
> trying to improve here. Therefore I'm still -2-W on adding new folks
> without removing non-active core members.
It's also *extrem
I was hoping to push code today for [1], but unfortunately I got caught by
something else during this week and I'll miss the code proposal deadline.
I would like to apply for a FFE; however, since I've experienced FFEs in
previous release cycles, please treat this request as best-effort if there
o
Le 05/03/2015 08:54, Rui Chen a écrit :
We will face the same issue in multiple nova-scheduler process case,
like Sylvain say, right?
Two processes/workers can actually consume two distinct resources on
the same HostState.
No. The problem I mentioned was related to having multiple threads
Big +1
On Thu, Mar 5, 2015 at 10:47 AM, Gary Kotton wrote:
> +100Š.000
>
> Very long overdue!
>
> On 3/4/15, 10:23 PM, "Maru Newby" wrote:
>
> >+1 from me, Ihar has been doing great work and it will be great to have
> >him finally able to merge!
> >
> >> On Mar 4, 2015, at 11:42 AM, Kyl
79 matches
Mail list logo
