I see that https://bugs.launchpad.net/horizon/+bug/1403129 is marked a wish
list. But it affects Glance and hence associated component with it
significantly.
The defect directly influence consumption of Horizon for Glance, especially
concurrency. If user wants to upload 3 images of large size
Radomir Dopieralski openst...@sheep.art.pl writes:
On 22/01/15 11:27, Martin Geisler wrote:
Maybe this is a dumb question, but if there already is a system
package for, say, Angular, why is the XStatic packge needed then?
Could the system package for Horizon not just point directly to where
Joe Gordon wrote:
On Mon, Jan 19, 2015 at 2:32 PM, ZhiQiang Fan aji.zq...@gmail.com
mailto:aji.zq...@gmail.com wrote:
I'm thinking that we should remove the all rights reserved words
if we're using Apache license.
Misleading is not a good thing, especially when it is for legal
+1
On 1/22/15, 2:18 AM, Akihiro Motoki amot...@gmail.com wrote:
+1 for Doug
2015-01-20 13:59 GMT+09:00 Aaron Rosen aaronoro...@gmail.com:
+1
On Fri, Jan 16, 2015 at 12:03 PM, Carl Baldwin c...@ecbaldwin.net
wrote:
+1
On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com
Qiming,
you are reading bits and pieces of my responses.if you checkout the
review guess i give up!
-- dims
On Wed, Jan 21, 2015 at 11:18 PM, Qiming Teng
teng...@linux.vnet.ibm.com wrote:
On Wed, Jan 21, 2015 at 10:55:37AM -0500, Davanum Srinivas wrote:
Qiming,
Guessing you were looking at
Thanks, Rick looks like GRO was something we was missing in our setup.
Here are some results form my tests
iperf with GRO disabled on server side : 2,5-3Gbps
iperf with GRO enabled on server side : 3,5-4 Gbps (gro was enabled on
eth0, br-eth0, br-storage)
Additionally i used OVS VLAN splinters
Hi Mike,
I received a email named “All Cinder Drivers Must Have a Third Party CI By
March 19th 2015” and I feel confused about the “*real* storage backend”.
One of the requirements is: Run Tempest [5][6] volume tests against the
devstack environment that's hooked up to your *real* storage
Hi guys,
I want to discuss the way we are working with deployment configuration that
were redefined for cluster.
In case it was redefined by API - we are using that information instead of
generated.
With one exception, we will generate new repo sources and path to manifest
if we are using update
On 01/22/2015 01:00 PM, Ettore zugliani wrote:
I am implementing the precommit part of a mechanism driver (ml2) right
now i'm having problems with sqlalchemy.
I made the class that uses the tables, but when the precommit is called
an error pops up telling that the tables don't exists.
To
On 22/01/15 11:27, Martin Geisler wrote:
Maybe this is a dumb question, but if there already is a system package
for, say, Angular, why is the XStatic packge needed then? Could the
system package for Horizon not just point directly to where the Angular
package has put its files?
Yes, that is
I am implementing the precommit part of a mechanism driver (ml2) right now
i'm having problems with sqlalchemy.
I made the class that uses the tables, but when the precommit is called an
error pops up telling that the tables don't exists.
To create the tables should i use a create all on
Please take a look at
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers to learn how
to configure devstack to use your driver rather than LVM.
On 22 January 2015 at 13:28, liuxinguo liuxin...@huawei.com wrote:
Hi Mike,
I received a email named “All Cinder Drivers Must Have a
Hi devs,
With online schema changes/No downtime DB upgrades things would be much lot
easier for OpenStack deployments.
Big kudos to Johannes who initiated this feature. But as a service provider,
I'm curious to understand what is the development process of adding new
features to Kilo and
On 21/01/15 19:04, Matthew Farina wrote:
Radomir, thanks for adding some clarity. I do have follow-on questions.
In your example the packages are managed by xstatic. The proposal for
horizon, as I understand it, is to move away from xstatic packages and
instead use bower for development and
It is caused by using old python-openstackclient [1]. We should be using
= 1.0.2 - fix is about to be merged [2].
Kuba
[1] https://bugs.launchpad.net/devstack/+bug/1413252
[2] https://review.openstack.org/#/c/148951/
On 01/22/2015 04:20 AM, Zhou, Zhenzan wrote:
Just noticed that your log has
On 22/01/15 09:48, Radomir Dopieralski wrote:
All of the XStatic packages had to be packaged for the respective
distributions in order to package Horizon. That was a lot of work, but
it has been done my the packagers of the distributions. As far as I
understand, most of those XStatic packages
Matthias Runge mru...@redhat.com writes:
On 22/01/15 09:48, Radomir Dopieralski wrote:
All of the XStatic packages had to be packaged for the respective
distributions in order to package Horizon. That was a lot of work, but
it has been done my the packagers of the distributions. As far as I
On Thu, Jan 22, 2015 at 09:42:50AM +0100, Jakub Libosvar wrote:
It is caused by using old python-openstackclient [1]. We should be using
= 1.0.2 - fix is about to be merged [2].
Thanks Jakub for helping me debug this on the IRC yesterday!
I hope these kind of backward incompatible changes can
On 01/22/2015 01:06 PM, Kevin Benton wrote:
There was a bug for this already.
https://bugs.launchpad.net/bugs/1413111
Thanks Kevin. I added more info to it, but don't think the patch proposed there
is correct. Something in the iptables manager defer_apply() code isn't quite
right.
-Brian
On 01/22/2015 10:28 AM, Salvatore Orlando wrote:
Hi,
We have attempted several times to start a conversation around the
interface between nova and neutron and its problems, starting with the
fact that it's chatter than two Italians arguing about football (*).
Indeed the first attempt at
There is a proposal from Armando to clear this up:
https://review.openstack.org/#/c/148745/
On 01/22/2015 03:53 PM, Sukhdev Kapur wrote:
Hi Ihar,
I have added this on the agenda for next neutron core meeting to discuss.
This email gives an excellent context to the issue at hand. Only one
Hi,
We have attempted several times to start a conversation around the
interface between nova and neutron and its problems, starting with the fact
that it's chatter than two Italians arguing about football (*).
Indeed the first attempt at fixing these problems goes back to the Fall
2012 summit
Hey all -
Concerning the enginefacade system, approved blueprint:
https://review.openstack.org/#/c/125181/
which will replace the use of oslo_db.sqlalchemy.EngineFacade ultimately across
all projects that use it (which is, all of them that use a database).
We are struggling to find a solution
Moreover I would suggest to use server spec as beaker is already
duplicating part of our infrastructure automatization.
On Thu, Jan 22, 2015 at 6:44 PM, Vladimir Kuklin vkuk...@mirantis.com
wrote:
Guys, I suggest that we create a blueprint how to integrate beaker with
our existing
Guys, I suggest that we create a blueprint how to integrate beaker with our
existing infrastructure to increase test coverage. My optimistic estimate
is that we can see its implementation in 7.0.
On Thu, Jan 22, 2015 at 2:07 AM, Andrew Woodward xar...@gmail.com wrote:
My understanding is
On 01/18/2015 02:11 PM, Morgan Fainberg wrote:
Hello all,
I would like to nominate Brad Topol for Keystone Spec core (core
reviewer for Keystone specifications and API-Specification only:
https://git.openstack.org/cgit/openstack/keystone-specs ). Brad has
been a consistent voice advocating
Hi Fuelers,
we've implemented pluggable architecture piece in 6.0, and got a number of
plugins already. Overall development process for plugins is still not fully
defined.
We initially thought that having all the plugins in one repo on stackforge
is Ok, we also put some docs into existing
On 01/22/2015 02:35 PM, Kevin Benton wrote:
Right, there are two bugs here. One is in whatever went wrong with defer_apply
and one is with this exception handling code. I would allow the fix to go in
for
the exception handling and then file another bug for the actual underlying
defer_apply
I think this warrants a bug report. Could you file one with what you
know so far?
Carl
On Wed, Jan 21, 2015 at 2:24 PM, Brian Haley brian.ha...@hp.com wrote:
On 01/21/2015 02:29 PM, Xavier León wrote:
On Tue, Jan 20, 2015 at 10:32 PM, Brian Haley brian.ha...@hp.com wrote:
On 01/20/2015 09:20
On Wed, Jan 21, 2015 at 10:27 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:
On 01/20/2015 05:40 PM, Paul Michali wrote:
Review https://review.openstack.org/#/c/146508/ is adding support for
StrongSwan VPN, which needs mount bind to be able to specify different
paths for config files.
Hi Ihar,
I have added this on the agenda for next neutron core meeting to discuss.
This email gives an excellent context to the issue at hand. Only one thing
I would like to add is that the deadline for stable/juno is only one week
away - hence, it raises the urgency to call for action.
Thanks
There was a thread named Wrong Status at the Dashboard - IceHouse Horizon mid
last year.
Thread archived here:
http://www.gossamer-threads.com/lists/openstack/dev/38332
I seem to have hit the same issue using Juno.
I had some bad passwords on a hypervisor while I was figuring out the deploy
On Wed, 2015-01-21 at 18:48 -0800, Joshua Harlow wrote:
Another thing that I just started whipping together:
https://gist.github.com/harlowja/5e39ec5ca9e3f0d9a21f
One problem, though, is that parse_requirements() now requires the
session keyword argument. In version 6.0.6,
On Thu, Jan 22, 2015 at 06:06:54AM -0500, Davanum Srinivas wrote:
Qiming,
you are reading bits and pieces of my responses.if you checkout the
review guess i give up!
-- dims
Ah, I see. I jumped directly into the code review dashboard without realizing
that patch is still WIP. That was my
+1
Welcome to the team Ivan!
On Fri, Jan 23, 2015 at 1:23 AM, Walter A. Boring IV
walter.bor...@hp.com wrote:
sorry I didn't see this earlier.
I'd welcome Ivan to the team!
+1
Walt
On Wed, Jan 21, 2015 at 10:14 AM, Mike Perez thin...@gmail.com wrote:
It gives me great pleasure to
For reference, most of our kickstart scripts for storage bricks go by size. The
little disks are system disks to be assembled into a software raid. The big
ones are raid arrays to be preserved.
Kickstart's ability to let you run a shell script on the host to build the
partitioning instructions
Seems like a simple fix?
https://github.com/pypa/pip/blob/1.5.6/pip/req.py#L1536
Make a new session somewhere in that gist/code and profit?
Kevin L. Mitchell wrote:
On Wed, 2015-01-21 at 18:48 -0800, Joshua Harlow wrote:
Another thing that I just started whipping together:
Hi all,
I am new to heat orchestration and am trying to create a coreOS cluster
with it. I have a OS::Heat::SoftwareConfig resource and a
OS::Heat::CloudConfig resource and I have joined them both in a
OS::Heat::MultipartMime resource which is then used as a user_data for a
OS::Nova::Server
On 01/22/2015 05:08 PM, Fox, Kevin M wrote:
There was a thread named Wrong Status at the Dashboard - IceHouse Horizon
mid last year.
Thread archived here:
http://www.gossamer-threads.com/lists/openstack/dev/38332
I seem to have hit the same issue using Juno.
I had some bad passwords on
On 22 January 2015 at 17:09, Sean Dague s...@dague.net wrote:
On 01/22/2015 10:28 AM, Salvatore Orlando wrote:
Hi,
We have attempted several times to start a conversation around the
interface between nova and neutron and its problems, starting with the
fact that it's chatter than two
Hi all,
Please join me in welcoming Flavio and Ian to the Glance Drivers team.
They have been doing some quality work in Glance; each of them brings in his
own skill set to the team. We would be happy to rely on the two main traits of
these individuals - they are aware about general workings
I can't imagine how MPLS/RSVP is suitable for the communications between
Nova and Neutron. Can you elaborate on what you meant?
On Thu, Jan 22, 2015 at 9:36 AM, Akilesh K akilesh1...@gmail.com wrote:
I had always wanted this to happen. It is really frustrating when nova
throws wierd python
On 01/22/2015 05:39 PM, Duncan Thomas wrote:
Please take a look at
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers to
learn how to configure devstack to use your driver rather than LVM.
On 22 January 2015 at 13:28, liuxinguo liuxin...@huawei.com
mailto:liuxin...@huawei.com
If we can consolidate that and use a single tool from the master neutron
repository, that would be my vote.
+1 with a hook mechanism so the sanity checks stay in the *aas repos and
they are only run if installed.
On Thu, Jan 22, 2015 at 7:30 AM, Kyle Mestery mest...@mestery.com wrote:
On Wed,
On 2015-01-22 11:53:10 -0500 (-0500), Matthew Farina wrote:
Has anyone done an inventory of xstatic packages that are
available as system packages? I ask because I started asking these
questions after doing a cursory inventory and finding few xstatic
packages as system packages.
[...]
Thanks to everyone who commented on the spec to change reset-state to involve
the driver: https://review.openstack.org/#/c/134366/
I've put some comments in reply, and I'm going to attempt to capture the
various ideas here. I hope we can discuss this at the Mid-Cycle in Austin.
1) The existing
Right, there are two bugs here. One is in whatever went wrong with
defer_apply and one is with this exception handling code. I would allow the
fix to go in for the exception handling and then file another bug for the
actual underlying defer_apply bug.
On Thu, Jan 22, 2015 at 10:32 AM, Brian Haley
Hi all,
Please find minutes and logs from this week's OpenStack Telco Working Group
meeting at the locations linked below:
* Minutes (HTML):
http://eavesdrop.openstack.org/meetings/telcowg/2015/telcowg.2015-01-21-22.00.html
* Log (HTML):
Congratulations Doug!
On Thu, 2015-01-22 at 11:21 -0600, Kyle Mestery wrote:
On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com
wrote:
The last time we looked at core reviewer stats was in December
[1]. In looking at the current stats, I'm going to propose
On 01/22/2015 10:17 AM, Carl Baldwin wrote:
I think this warrants a bug report. Could you file one with what you
know so far?
Carl,
Seems as though a recent change introduced a bug. This is on a devstack
I just created today, at l3/vpn-agent startup:
2015-01-22 11:55:07.961 4203 TRACE
Radomir and Matthias,
Has anyone done an inventory of xstatic packages that are available as
system packages? I ask because I started asking these questions after doing
a cursory inventory and finding few xstatic packages as system packages. It
appeared to me that the common case was the one
On Thu, Jan 15, 2015 at 4:31 PM, Kyle Mestery mest...@mestery.com wrote:
The last time we looked at core reviewer stats was in December [1]. In
looking at the current stats, I'm going to propose some changes to the core
team. Reviews are the most important part of being a core reviewer, so we
Hi Dmitry,
The problem with merging is usually it's not clear how system performs
merging.
For example you have the next hash {'list': [{'k': 1}, {'k': 2}, {'k':
3}]}, and I want
{'list': [{'k': 4}]} to be merged, what system should do? Replace the list
or add {'k': 4}?
Both cases should be
There was a bug for this already.
https://bugs.launchpad.net/bugs/1413111
On Thu, Jan 22, 2015 at 9:07 AM, Brian Haley brian.ha...@hp.com wrote:
On 01/22/2015 10:17 AM, Carl Baldwin wrote:
I think this warrants a bug report. Could you file one with what you
know so far?
Carl,
Seems as
On Fri Jan 23 2015 at 4:28:59 AM Matthew Farina m...@mattfarina.com wrote:
I would like to add one more nuance to this discussion that I don't
remember seeing.
JavaScript libraries run in web browser in their JavaScript engines (like
v8) rather than on the server. A version of a JS library
sorry I didn't see this earlier.
I'd welcome Ivan to the team!
+1
Walt
On Wed, Jan 21, 2015 at 10:14 AM, Mike Perez thin...@gmail.com wrote:
It gives me great pleasure to nominate Ivan Kolodyazhny (e0ne) for
Cinder core. Ivan's reviews have been valuable in decisions, and his
contributions
I would like to add one more nuance to this discussion that I don't
remember seeing.
JavaScript libraries run in web browser in their JavaScript engines (like
v8) rather than on the server. A version of a JS library may be fine on a
system, without any security issues, but contain browser issues.
On 01/14/2015 01:47 AM, Ton Ngo wrote:
Hi Tomas,
I think your patch is a great start so we can prototype quickly; I am
trying it out right now. We can break up the implementation into several
parts that can be updated more or less independently based on the feedback.
Ton,
snip
Hey
Thank you! I managed to do it following your tip and the guide you sent.
2015-01-22 10:54 GMT-02:00 Jakub Libosvar libos...@redhat.com:
On 01/22/2015 01:00 PM, Ettore zugliani wrote:
I am implementing the precommit part of a mechanism driver (ml2) right
now i'm having problems with
I had always wanted this to happen. It is really frustrating when nova
throws wierd python exceptions and difficult to comprehend log messages.
If the developers do agree to clean up the interface I would suggest they
make use of some well knows protocol (mpls/rsvp) to do this, instead of
relying
Jeremy, thanks for sharing this. I do have a couple more questions and
comments based on this.
When there is an update to our requirements, such as the recent version
increment in the version of angular used, a new package version doesn't
automatically show up as evident from that list. How would
Richard,
I'm quite familiar with node.js and browser development. I think some of
the issue here may be a lack of detailed explanations and assumptions. By
asking questions here I, and some others, have been learning details that
we didn't know before. And, we're getting to follow from the intent
On Thu, Jan 22, 2015 at 1:44 AM, Tim Bell tim.b...@cern.ch wrote:
-Original Message-
From: Victor Lowther [mailto:victor.lowt...@gmail.com]
Sent: 21 January 2015 21:06
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Ironic] RAID interface
On 2015-01-22 16:06:55 -0500 (-0500), Matthew Farina wrote:
[...]
When there is an update to our requirements, such as the recent
version increment in the version of angular used, a new package
version doesn't automatically show up as evident from that list.
How would that process be kicked
pls note that actually this patch doesn't have minumum kernel requirement
because it only uses 'mount --bind' and 'net namespace', not use 'mount
namespace'. ('mount --bind' is since linux 2.4, 'net namespace' is since
Linux 3.0, 'mount namespace' is since Linux 3.8).
so I think sanity checks for
Hi Harish,
Port binding in ML2 is the process by which a mechanism driver (or once
https://blueprints.launchpad.net/openstack/?searchtext=ml2-hierarchical-po
rt-binding
is merged, potentially a set of mechanism drivers) is selected for the
port, determining how connectivity is provided for that
So I am resurrecting this topic now because we put this discussion on a a brief
hold,
but are now discussing it again and need to decide asap. We've all agreed we
need a
provisioning_status and operating_status fields. We now need to decide where to
show
these statuses to the user.
Option 1:
67 matches
Mail list logo
