- Original Message -
From: Pasquale Porreca pasquale.porr...@dektech.com.au
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Thursday, February 19, 2015 3:24:03 AM
Subject: Re: [openstack-dev] [Keystone] [devstack] About
Hi All
Currently glance image-create works successfully with no parameters and a image
is created with a name None.
This can lead to confusion as multiple runs of glance image-create command
will create multiple images all with a name None.
So to end the confusion name should be added as a
Hi,
As part of tempest job gate-tempest-dsvm-full-glusterfs
http://logs.openstack.org/11/159711/1/experimental/gate-tempest-dsvm-full-glusterfs/b2cb37e/
run [1], the test case test_snapshot_create_with_volume_in_use [2] is
failing.
This is because demo user is unable to create online
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks Bharat for starting this thread
I would like to invite suggestions/opinions from tempest folks on whats the
right way to get this to work ?
1) Use priviledge user in cinder.conf
--or --
2) Modify tempest volume snapshot_in_use testcase to bump the user to
admin, run the test, revert
Sounds promising. We'll have to evaluate it for feature parity when the
time comes.
On Thu, Feb 26, 2015 at 8:21 PM, Ben Pfaff b...@nicira.com wrote:
This sounds quite similar to the planned support in OVN to gateway a
logical network to a particular VLAN on a physical port, so perhaps it
Tim:“So you’re saying we won’t have fresh enough data to make policy decisions?
If the data changes so frequently that we can’t get an accurate view, then I’m
guessing we shouldn’t be migrating based on that data anyway.”
Ramki: We have to keep in mind that VM migration could be an expensive
FYI
-Forwarded by Rattenpal Amandeep/DEL/TCS on 02/27/2015 01:14PM -
To: openstack-dev@lists.openstack.org
From: Rattenpal Amandeep/DEL/TCS
Date: 02/25/2015 11:43AM
Subject: [openstack-dev] [python-novaclient] [python-client] Queries regarding
how to run test cases of python-client in
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see if they were still
alive). I also know of a few
On Thu, 2015-02-26 at 14:18 -0600, Anne Gentle wrote:
Do the features listed in the Release Notes each have appropriate
documentation? So far we just link to the specifications for nova, for
example. [1] So to me, it could be a focus on the specification
acceptance means less time/energy for
The Keystone team has released python-keystoneclient 1.2.0.
This release can be installed from the following locations:
* http://tarballs.openstack.org/python-keystoneclient
* https://pypi.python.org/pypi/python-keystoneclient
Detailed changes in this release:
[sorry for ceph-devel double-post, forgot to include openstack-dev]
Hi everyone,
The online Ceph Developer Summit is next week[1] and among other things
we'll be talking about how to support CephFS in Manila. At a high level,
there are basically two paths:
1) Ganesha + the CephFS FSAL driver
+1 to the move!
On Feb 26, 2015 6:43 PM, Ben Nemec openst...@nemebean.com wrote:
On 02/26/2015 03:57 PM, Doug Hellmann wrote:
The team behind the unified command line tool is preparing to ask the TC
to allow us to become an official team. The
openstack/python-openstackclient repository will
This morning in the nova channel we were trying to get to the bottom of
the unit tests failing lxsi and gillard in en_GB on some string
comparisons. Something is breaking down in our i18n null fixture for the
tests.
However, in trying to track down the route of their messages I ran into
things
On 02/26/2015 07:06 PM, Ed Leafe wrote:
I think you've nailed where the disconnect is between the two sides of this
issue: what exactly do we see OpenStack being? You brought up several Linux
vendors who ship on a longish cycle, and who provide LTS for their releases.
But Linux itself is
Hi,
I’m trying to understand the path of a series of issues I’ve been interested in
for some time. Hopefully, someone can spend a few minutes to educate me on the
state of affairs, how/when incubation code might make it to the main project.
The bugs in question are:
Hi Przemek,
Thanks for detailed description of the issues you faced.
+1 for this approach, let's keep pure-UI implementation for 6.1 - it will
work for 99% of the cases.
2015-02-26 21:35 GMT+07:00 Przemyslaw Kaminski pkamin...@mirantis.com:
Hello,
Recently I've been asked to implement
On Wed, Feb 25, 2015 at 4:12 AM, Victor Stinner vstin...@redhat.com wrote:
Hi,
I also just put up another proposal to consider:
https://review.openstack.org/#/c/156711/
Sew over eventlet + patching with threads
My asyncio spec is unclear about WSGI, I just wrote
The spec doesn't
Hi,
I have proposed a recent patch, that when using Neutron as the
networking component in DevStack, the PUBLIC_INTERFACE that has been set
should automatically be added to the OVS_PHYSICAL_BRIDGE.
https://review.openstack.org/#/c/158424/
There are a couple motivations for this patch. The first
On Wed, Feb 25, 2015 at 10:47 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote:
Hi, stackers!
As was suggested in topic [1], using an HTTP header was a good solution
for
communicating common/standardized OpenStack API error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have some experience in i18n for other project (GNOME), so I have
some answers to your questions.
On 02/26/2015 02:18 PM, Sean Dague wrote:
This morning in the nova channel we were trying to get to the
bottom of the unit tests failing lxsi and
On Feb 25, 2015, at 6:06 PM, Thomas Goirand z...@debian.org wrote:
In fact, if you want to judge from the POV of our users, we should *SLOW
DOWN* our release cycles, and probably move to something like one
release every year or 2. We should also try to have longer periods of
support for our
2015-02-26 22:27 GMT+09:00 Tom Fifield t...@openstack.org:
On 26/02/15 21:18, Sean Dague wrote:
This morning in the nova channel we were trying to get to the bottom of
the unit tests failing lxsi and gillard in en_GB on some string
comparisons. Something is breaking down in our i18n null
On 02/26/2015 02:27 PM, Tom Fifield wrote:
On 26/02/15 21:18, Sean Dague wrote:
This morning in the nova channel we were trying to get to the bottom of
the unit tests failing lxsi and gillard in en_GB on some string
comparisons. Something is breaking down in our i18n null fixture for the
On Thu, 26 Feb 2015, Ed Leafe wrote:
OpenStack can't be all things to all people. Following the Linux
analogy, we need a few companies who want to become OpenStack
distributors, packagers, and supporters, in the manner of RedHat,
Canonical, etc., are for Linux. As a development project, we need
On 26/02/15 21:18, Sean Dague wrote:
This morning in the nova channel we were trying to get to the bottom of
the unit tests failing lxsi and gillard in en_GB on some string
comparisons. Something is breaking down in our i18n null fixture for the
tests.
However, in trying to track down the
On 02/26/2015 02:18 PM, Sean Dague wrote:
This morning in the nova channel we were trying to get to the bottom of
the unit tests failing lxsi and gillard in en_GB on some string
comparisons. Something is breaking down in our i18n null fixture for the
tests.
However, in trying to track down
Hello,
Recently I've been asked to implement Python side of a simple feature:
before deployment tell the UI user that network verification for current
cluster configuration has not been performed. Moreover, on the UI side
it's possible to do network checking on usaved cluster data -- in that
case
On 02/26/2015 08:28 AM, Ihar Hrachyshka wrote:
I have some experience in i18n for other project (GNOME), so I have
some answers to your questions.
On 02/26/2015 02:18 PM, Sean Dague wrote:
This morning in the nova channel we were trying to get to the
bottom of the unit tests failing lxsi
On Feb 26, 2015, at 9:49 AM, Ritesh Raj Sarraf r...@researchut.com wrote:
I think you've nailed where the disconnect is between the two sides of this
issue: what exactly do we see OpenStack being? You brought up several Linux
vendors who ship on a longish cycle, and who provide LTS for their
Hi Andrey,
IMO the first choice (adding a new structure) is better because of the
following reasons:
1. The only source of truth for the networks allocations by the user can
be the new roles_meta structure, while transformations can be changed in future
versions or by plugins, according
On Thu, Feb 26, 2015, at 03:03 AM, Deepak Shetty wrote:
On Wed, Feb 25, 2015 at 6:11 AM, Jeremy Stanley fu...@yuggoth.org
wrote:
On 2015-02-25 01:02:07 +0530 (+0530), Bharat Kumar wrote:
[...]
After running 971 test cases VM inaccessible for 569 ticks
[...]
Glad you're able to
Hi Andrey,
I don't have enough details to make some conclusions, but if the
problem can be solved with some python script which gets the data
and converts it into more readable format, lets do it this way.
Thanks,
On Wed, Feb 25, 2015 at 10:59 PM, Andrey Danin ada...@mirantis.com wrote:
Hi,
On Thu, Feb 26, 2015, at 07:24 AM, Boden Russell wrote:
What's the suggested approach for implementing a custom oslo messaging
driver given the existing impl [1] is private?
e.g. I want to provide my own notification messaging driver which adds
functionality atop the existing driver [1].
On Thu, Feb 26, 2015, at 11:22 AM, John Stanford wrote:
Hi,
I’m trying to understand the path of a series of issues I’ve been
interested in for some time. Hopefully, someone can spend a few minutes
to educate me on the state of affairs, how/when incubation code might
make it to the main
Inline.
From: ruby.krishnasw...@orange.commailto:ruby.krishnasw...@orange.com
ruby.krishnasw...@orange.commailto:ruby.krishnasw...@orange.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date:
On Wed, 2015-02-25 at 21:15 +, Ian Cordasco wrote:
I read it the same was as Doug. I don’t think Jeremy was trying to
imply your reviews would move through more quickly if you reviewed
other people’s work. Just that, as with most open source projects,
there’s always at least 2 distinct
On Thu, Feb 26, 2015 at 1:45 PM, Stefano Maffulli stef...@openstack.org
wrote:
On Wed, 2015-02-25 at 21:15 +, Ian Cordasco wrote:
I read it the same was as Doug. I don’t think Jeremy was trying to
imply your reviews would move through more quickly if you reviewed
other people’s work.
On Thu, Feb 26, 2015 at 1:10 PM, Walter A. Boring IV walter.bor...@hp.com
wrote:
Hey folks,
Today we found out that a patch[1] that was made against our lefthand
driver caused the driver to fail. The 3rd party CI that we have setup
to test our driver (hp_lefthand_rest_proxy.py) caught
I don't have a public repo -- have been PoCing using a private gitlab to
date... I figured any interest in the driver impl would come out of this
email discussion.
More than happy to provide my PoC code publicly (after a little
clean-up) if there's an interest.
On 2/26/15 12:01 PM, Sandy Walsh
Hey folks,
Today we found out that a patch[1] that was made against our
lefthand driver caused the driver to fail. The 3rd party CI that we
have setup
to test our driver (hp_lefthand_rest_proxy.py) caught the CI failure and
reported it correctly[2]. The patch that broke the driver was
Cool, I'm interested in creating some notification drivers outside of
olso-messaging as well (for Kafka support and schema-based notifications).
Do you have a repo started on this? I'd be keen to have a look.
-S
From: Boden Russell boden...@gmail.com
Thanks for filing the bug report...
My driver implementation effectively allows you to filter on
notification events and multicast matches to a given list of topics.
I've been calling it an messaging multicast notification driver and thus
the plugin stevedore entry point I've called
So, I'm wondering how much of this is unnecessarily splitting hairs on
what defines a cross-project spec. If you look at the currently merged
specs, they are in fact both Guidelines:
http://specs.openstack.org/openstack/openstack-specs/
Would renaming mine Eventlet Guidelines make it more
Hi Doug,
Thanks for the quick response and clarification on process. Sounds like there
are two key issues:
1) /dev/log is not portable
2) a code change was made that broke use_syslog=True
From the paper trail, it looks like the fix for use_syslog=True by reconnecting
/dev/log was down-voted
On Thu, Feb 26, 2015, at 01:41 PM, Boden Russell wrote:
Thanks for filing the bug report...
My driver implementation effectively allows you to filter on
notification events and multicast matches to a given list of topics.
I've been calling it an messaging multicast notification driver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2015 01:45 PM, Stefano Maffulli wrote:
The interesting bit of those charts is that overall for OpenStack
projects, it seems that the reviews (comments to patchsets) are arriving
quite quickly but the new patchsets take a lot more to be
On Thu, Feb 26, 2015, at 03:55 PM, Ben Nemec wrote:
So, I'm wondering how much of this is unnecessarily splitting hairs on
what defines a cross-project spec. If you look at the currently merged
specs, they are in fact both Guidelines:
http://specs.openstack.org/openstack/openstack-specs/
As we discussed in the meeting today, I’ve created a Doodle to coordinate a
good day and time for future meetings. I picked a bunch of options based on
when it looked like there were IRC rooms obviously available. If none of these
options suit us, I can dig harder to find other open times.
First pass at new docs are available here http://www.stacktach.com/
(API and glossary to follow)
Feedback and patches welcome!
-Sandy
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Wed, Feb 25, 2015 at 9:47 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Wed, Feb 25, 2015, at 02:59 PM, Robert Collins wrote:
On 26 February 2015 at 08:54, melanie witt melwi...@gmail.com wrote:
On Feb 25, 2015, at 10:51, Duncan Thomas duncan.tho...@gmail.com
wrote:
Is there
On 25/02/15 20:18, Joe Gordon wrote:
On Fri, Feb 20, 2015 at 3:48 AM, Matthew Booth mbo...@redhat.com
mailto:mbo...@redhat.com wrote:
Gary Kotton came across a doozy of a bug recently:
https://bugs.launchpad.net/nova/+bug/1419785
In short, when you start a Nova compute,
Hi folks!
The Oslo team is pleased to announce the release of: oslo.db - OpenStack
common DB library
Changes from the previous release:
$ git log --oneline --no-merges 1.4.1..1.5.0
7bfdb6a Make DBAPI class work with mocks correctly
96cabf4 Updated from global requirements
a3a1bdd Imported
I am developing as cinder plugin and I recently faced one problem while running
the cinder driver's certification test (
devstack/driver_certs/cinder_driver_cert.sh )
Here is what happened and my understanding of the problem (correct me if I am
wrong)
From the test logs I can see the
On Thu, Feb 26, 2015 at 01:06:14AM +0100, Thomas Goirand wrote:
On 02/24/2015 12:27 PM, Daniel P. Berrange wrote:
I'm actually trying to judge it from the POV of users, not just
developers. I find it pretty untenable that in the fast moving
world of cloud, users have to wait as long as 6
Sharing thoughts that I was having:
May be during the next summit it’s worth discussing the future of the
reference agent(s), I feel we’ll be replicating a lot of work across
OVN/OVS/RYU(ofagent) and may be other plugins,
I guess until OVN and it’s integration are ready we can’t stop, so it
In trying to move the flavor manage negative tests out of Tempest and
into the Nova functional tree, I ran into one set of tests which are
permissions checking. Basically that a regular user isn't allowed to do
certain things.
In (nearly) all our tests we use auth_strategy=noauth which takes you
On Wed, Feb 25, 2015 at 6:11 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-02-25 01:02:07 +0530 (+0530), Bharat Kumar wrote:
[...]
After running 971 test cases VM inaccessible for 569 ticks
[...]
Glad you're able to reproduce it. For the record that is running
their 8GB performance
That's just what I mean about horizontal, which is limited for some
features. For example, ports belonging to BSN driver and OVS driver can't
communicate with each other in the same tunnel network, neither does
security group across both sides.
There is no tunnel network in this case, just VLAN
Hi,
I never had a strong opinion on this but reading what Jay said makes
sense to me. I also like Robert suggestion about having a single +2/+A
for such small changes.
Cheers,
Lucas
On Wed, Feb 25, 2015 at 11:22 PM, Robert Collins
robe...@robertcollins.net wrote:
On 26 February 2015 at 05:26,
In anticipation of Mistral supporting in Heat, let's introduce using
Mistral in Heat.
1. For using Mistral resources workflow and cron-trigger in Heat, Mistral
must be installed to DevStack. Installation guide for DevStack on
https://github.com/stackforge/mistral/tree/master/contrib/devstack
On 02/26/2015 06:47 AM, Lucas Alvares Gomes wrote:
Hi,
I never had a strong opinion on this but reading what Jay said makes
sense to me. I also like Robert suggestion about having a single +2/+A
for such small changes.
+A
Cheers,
Lucas
On Wed, Feb 25, 2015 at 11:22 PM, Robert
What's the suggested approach for implementing a custom oslo messaging
driver given the existing impl [1] is private?
e.g. I want to provide my own notification messaging driver which adds
functionality atop the existing driver [1]. This can obviously be done
by extending the
The team behind the unified command line tool is preparing to ask the TC to
allow us to become an official team. The openstack/python-openstackclient
repository will be managed by this new team, and I suggested we also consider
transferring ownership of openstack/cliff from Oslo at the same
On Wed, 2015-02-25 at 14:54 -0500, Doug Hellmann wrote:
1. Should we have a unified developer guide for the project?
Yes. Absolutely. Yes.
2. Where should it live and how should we manage it?
I think the natural destination for it would be the URL
http://docs.openstack.org/developer (which
Hi Aaron,
I am new to congress and trying to write tempest tests for the newly added
murano datasource driver. Since the murano datasource tempest tests require
both murano and python-congress clients as the dependencies. I was told that I
can't just simply add the requirements in the
If OVN chooses not to support VLANs, we will still need the current OVS
reference anyway so it definitely won't be wasted work.
On Thu, Feb 26, 2015 at 2:56 AM, Miguel Angel Ajo Pelayo
majop...@redhat.com wrote:
Sharing thoughts that I was having:
May be during the next summit it’s worth
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli stef...@openstack.org wrote:
Does it make sense to purge old stuff regularly so we have a better
overview? Or maybe we should chart a distribution of age of proposed
changesets, too in order to get a better understanding of where the
outliers
1)
Ruby: One of the issues highlighted in OpenStack (scheduler) and also elsewhere
(e.g. Omega scheduler by google) is :
Reading “host utilization” state from the data bases and DB (nova:host table)
updates and overhead of maintaining in-memory state uptodate.
ð This is expensive and current
Update on this:
The tools for checking for and adding UUIDs has been completed and reviewed.
https://review.openstack.org/#/c/157273
https://review.openstack.org/#/c/157273
A new patch has been sent up that adds UUIDs to all tests
https://review.openstack.org/#/c/159633
On 02/26/2015 03:57 PM, Doug Hellmann wrote:
The team behind the unified command line tool is preparing to ask the TC to
allow us to become an official team. The openstack/python-openstackclient
repository will be managed by this new team, and I suggested we also
consider transferring
Looking good Sandy! Seems much more generalized than the original
StackTach. I'll have to give it a shot when I have a spare second or two.
On Thu, Feb 26, 2015 at 5:50 PM, Sandy Walsh sandy.wa...@rackspace.com
wrote:
First pass at new docs are available here http://www.stacktach.com/
(API
Stefano Maffulli stef...@openstack.org writes:
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see
On Thu, 2015-02-26 at 11:45 -0800, Stefano Maffulli wrote:
The interesting bit of those charts is that overall for OpenStack
projects, it seems that the reviews (comments to patchsets) are arriving
quite quickly but the new patchsets take a lot more to be submitted.
Too much debating and
The Log Working Group is a cross project (horizontal) and community group that
is working to rationalize log messages and logging practices across the
OpenStack ecosystem. This has been identified as a big concern within the user
communities. Anyone with an interest in improving logs, logging
Hi Tim, All,
The document is in great shape! Any global policies such as those impacting
compute and network (e.g. CPU utilization and network bandwidth utilization)
would be handled in Congress and not delegated. It would be worthwhile to
capture this.
Thanks,
Ramki
From: Tim Hinrichs
What kind of VLAN support would you need?
On Thu, Feb 26, 2015 at 02:05:41PM -0800, Kevin Benton wrote:
If OVN chooses not to support VLANs, we will still need the current OVS
reference anyway so it definitely won't be wasted work.
On Thu, Feb 26, 2015 at 2:56 AM, Miguel Angel Ajo Pelayo
This sounds quite similar to the planned support in OVN to gateway a
logical network to a particular VLAN on a physical port, so perhaps it
will be sufficient.
On Thu, Feb 26, 2015 at 05:58:40PM -0800, Kevin Benton wrote:
If a port is bound with a VLAN segmentation type, it will get a VLAN id
We held our doc team meeting this morning (sorry again for missing the
correct time) and you can read the minutes here:
http://eavesdrop.openstack.org/meetings/docteam/2015/docteam.2015-02-26-14.03.html
Here's more news that's fit to print:
__In review and merged__
110 patches merged this past
If a port is bound with a VLAN segmentation type, it will get a VLAN id and
a name of a physical network that it corresponds to. In the current plugin,
each agent is configured with a mapping between physical networks and OVS
bridges. The agent takes the bound port information and sets up rules to
81 matches
Mail list logo
