Excerpts from Robert Collins's message of 2015-07-09 11:07:44 +1200:
On 9 July 2015 at 09:08, Sean Dague s...@dague.net wrote:
So I think the issue is that we used to have a manual process (reviewing
g-r adds), and some automated stuff that happens after that.
Now we seem to have a
Excerpts from Sergey Kraynev's message of 2015-07-09 18:26:09 +0300:
Hi community.
I want to raise couple questions about openstack clients.
In Heat we use other python-*clients for manipulating service's resources,
but some stuff placed in shell.py modules and we are forced to duplicate
I missed this whole thread due to my mail filtering. Sorry about that.
Anyway, Ivan and I have an open Blueprint here:
https://blueprints.launchpad.net/cinder/+spec/use-cinder-without-nova
That starts the discussion of adding the end to end ability of attaching
a Cinder
volume to a host
On Jul 9, 2015, at 9:35 AM, Russell Bryant rbry...@redhat.com wrote:
On 07/09/2015 09:19 AM, Neil Jerram wrote:
In the hope of forestalling an unnecessary sub-thread...
Mita was #1 in the vote, so has presumably already been ruled out by
OpenStack's legal review.
That is correct.
Hi
Greetings,
Before I even get started with this email, I'd like to make it clear
that I'm sending it out assuming the good faith of everyone and the
willingness of the Glance community to work together on improving our
workflow. We all do what we do on the best interests of the project.
My
And I realized all of a sudden that even more interesting than unittest
framework itself would be some analog of Python mock for shell scripts.
Though I doubt that anyone ever really gone that far.
--
Best regards,
Oleg Gelbukh
On Thu, Jul 9, 2015 at 5:12 PM, Jeremy Stanley fu...@yuggoth.org
Ok, I guess I'll bite my own thread and provide some feedback:
We hold a glance-drivers meeting every week on Tuesdays at 14 UTC. In
this week's meetingi[0], we discussed a bit the problems we have in the
current workflow. Here's some feedback from that meeting. (Please,
other folks, do chime
On 08/07/15 18:12, Steve Baker wrote:
On 09/07/15 04:39, Zane Bitter wrote:
On 08/07/15 09:03, Sean Dague wrote:
Personally, I'm running out of steam on tags for this cycle, but Zane
brought up a good point in the TC meeting yesterday, which was that it
would be nice to have tags for criteria
Cinder now doesn't check the existing resource when user lower the quota.
It's reasonable for admin can adjust the quota limit to lower level than
current usage.
But it also bring confusion that I have received to end user, they saw the
current usage
was more than limit, but they can't create
Hi,
Can you describe what problems do you have with bring code changes into a
live Devstack environment, and test them.
If you want a real-time QA experience you can ask your questions at
#murano on freenode.
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
On 07/09/2015 07:06 PM, Andrew Woodward wrote:
It has come to my attention that we spend an enormous amount of time in
Fuel when switching between OpenStack releases. A good amount of this
seems to be due to a chicken and the egg problem. We cant deploy updated
packages with out updated
Yes I'm talking about vetting by legal since the community already vets via
the usual process. Legal has stricter guidelines so we could start future
vetting with legal to remove the options we can't use even if we wanted to.
That's where the inefficiency lies imho. The issue with this particular
Thanks Vipin*, *it's very helpful.
2015-06-14 16:23 GMT+08:00 Vipin Balachandran vbalachand...@vmware.com:
Sorry for the long delay. This is fixed in oslo.vmware 0.9.0.
https://github.com/openstack/oslo.vmware/commit/a229faf8ba59724a4fda3f37d5a7473376f93d9c
*From:* hao wang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
First of all, apologies for my absence over the past couple of weeks. I
took some time off to spend with my daughter while she was on school
holidays, and then got ill! It never rains but it pours ;) While I was
out, our M release was
Better late than never.
We have the pleasure to announce stable/kilo (6.0.0) release of 20
repositories, all part of Puppet OpenStack project:
puppet-ceilometer
puppet-cinder
puppet-designate
puppet-glance
puppet-heat
puppet-horizon
puppet-ironic
puppet-keystone
Currently I found the spec about the trove monitoring framework in
https://review.openstack.org/#/c/186040/
And what's the process about that now?
We're developing MySQL and redis service upon trove. And we're glad to discuss
and contribute to this
Hi guys
My problem looks simple:
Running tox -e pep8, the result says ok, not pep8 mistakes.
Running pep8 ., a lot of pep8 mistkes come out.
But in your project's tox.ini, there isn't such a long ignore list. So what
makes this difference happen?
Kun
Hi,
Not sure if what I met if the same as yours.
In my case, pep8 . reported many errors located in the virtual environment
folder. In my case, things like:
./.venv/lib/python2.7/site-packages/virtualenv.py:260:13: E265 block comment
should start with '# '
To work around it, I use pep8
Hi,
I am using puppet-swift to deploy a swift multi node cluster (Icehouse),
following the setup in supplied tests/site.pp. I am running into two
issues that seem to be related to the subject above:
1/ Errors when the storage replication services try to start before the
ring files exist.
On 2015-07-09 18:04:49 -0700 (-0700), Adam Lawson wrote:
Yes I'm talking about vetting by legal since the community already
vets via the usual process. Legal has stricter guidelines so we
could start future vetting with legal to remove the options we
can't use even if we wanted to. That's
Team,
Tom Cammann (tcammann) has become a valued Magnum contributor, and consistent
reviewer helping us to shape the direction and quality of our new
contributions. I nominate Tom to join the magnum-core team as our newest core
reviewer. Please respond with a +1 vote if you agree.
+1 to Tom for his great reviews.
Regards,
Madhuri
On Fri, Jul 10, 2015 at 11:20 AM, Adrian Otto adrian.o...@rackspace.com
wrote:
Team,
Tom Cammann (tcammann) has become a valued Magnum contributor, and
consistent reviewer helping us to shape the direction and quality of our
new
Hi Glance experts,
I'd like to send this mail again, hope I can get help and suggest from
glance experts. The question is from a bug
https://bugs.launchpad.net/glance/+bug/1462315,
If an image-member is deleted, then create it again with the same
parameters, glance searches db to see if there
2 weeks seems too small for me. We easy can be in situation when fix for
medium bug is done, but SCF starts. And gap between SCF and release easily
can be more than a month. So, 2 months seems okay for me if speaking about
forcibly applying auto-abandon by major vote. And I'm personally against
Sorry for the long delay, I'd like to help to review those patches, and I
don't find the patch about refactoring manage_existing flow in manager yet,
so maybe I can have a try.
2015-06-02 17:45 GMT+08:00 Dulko, Michal michal.du...@intel.com:
Right now we’re working on refactoring current
On Thu, Jul 9, 2015 at 10:24 AM, Matthew Mosesohn mmoses...@mirantis.com
wrote:
What about bashate? It is already in use in several OpenStack projects?
https://github.com/openstack-dev/bashate
To be honest, I don't see any value of using bashate. It does some basic
checks
but none of them is
Feel free to give input on the Mitaka proposal.
Tim
-Original Message-
From: Jonathan Bryce [mailto:jbr...@jbryce.com]
Sent: 09 July 2015 20:52
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Openstack] Rescinding the M name decision
On Thu, Jul 9, 2015 at 1:33 PM, Michael Krotscheck krotsch...@gmail.com
wrote:
Hey everyone!
We've been hard at work getting some solid, shared code style rules in
place for our javascript code, and nobody's been more diligent about this
than Cindy Lu. Since we've managed to encapsulate our
Hi all,
We are scheduled to publish 2015.1.1 Kilo point releases,
on Thursday July 16th for Ceilometer, Cinder, Glance, Heat, Horizon,
Ironic, Keystone, Neutron, Nova, Sahara and Trove.
We'd appreciate anyone who could test the candidate 2015.1.1 tarballs, which
include all changes aside from
Hi Everyone,
Thanks for joining the service chaining project meeting on 7/9/2015. Here is
the link to the meeting logs:
http://eavesdrop.openstack.org/meetings/service_chaining/2015/
Thanks,
Cathy
__
OpenStack Development
Hi all,
Just FYI, here is a sample script I'm using for testing os-brick which
attaches/detaches the cinder volume to the host using cinderclient and
os-brick:
https://gist.github.com/tsekiyama/ee56cc0a953368a179f9
python attach.py volume-uuid will attach the volume to the executed
host and
Thanks Ihar comments!
Is Neutron ready to be upgradable with minimal downtime of services
and no VM access downtime?
As the ovs bug you refer to above, no, at least not in reference
implementation. That's for data plane.
My understanding is that after the ovs neutron agent will be
On 16:47 Jun 30, Mike Perez wrote:
On 12:24 Jun 26, Matt Riedemann wrote:
snip
So the question is, is everyone OK with this and ready to make that change?
Thanks for all your work on this Matt.
I'm fine with this. I say bite the bullet and we'll see the CI's surface that
aren't
Hey everyone!
We've been hard at work getting some solid, shared code style rules in
place for our javascript code, and nobody's been more diligent about this
than Cindy Lu. Since we've managed to encapsulate our eslint configuration
into a separate project (much like hacking), I'd like to
On 10:58 Jun 29, Sheng Bo Hou wrote:
Hi everyone,
For folks who are working on Dell, Storpool and Infortrend drivers:
I have got a new patch for https://review.openstack.org/#/c/180873. There
is a change about how to implement the method update_migrated_volume for
each driver.
The code
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has experience in deploying and
maintaning Glance production environments.
Stuart has shown his interest in
On 21:48 Jul 06, Ivan Kolodyazhny wrote:
snip
Aslo, what do you think about moving cinderclient functional tests from
experimental to non-voting queue to make it more public and run it with
every patch to python-cinderclient?
I'm fine with this as long as the job has been stable since it was
On 08:49 Jun 23, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
Cinder client asks Keystone to find a
On 02:08 Jul 01, liuxinguo wrote:
Hi Mike,
We have solved the problem of Huawei CI, and it is running and reporting
stably now. The logs is also ok to access.
We will be very appreciate if you can have a consider of remove the -2 review
to Huawei driver, thanks! ☺
The following patchs
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has experience in deploying and
maintaning Glance production environments.
Stuart has shown his interest in
Apparently I sent this email twice... disregard this one
On 09/07/15 21:13 +0200, Flavio Percoco wrote:
Greetings,
I'd like to propose Stuart Mclaren for the glance-drivers team. Stuart
has a huge amount of knowledge about Glance's history, he knows the
Glance codebase well and he also has
Hello OpenStackers, hello TC,
Haikel and I have just submitted an update to the change to the governance
repo to add RPM packaging to the OpenStack projects:
https://review.openstack.org/#/c/191587
As a start there we'd like to do a dual PTL from Red Hat (Haikel) and SUSE
(myself) and we'd like
That's a very good plan (Initial feedback/triage) Mike.
thanks,
dims
On Thu, Jul 9, 2015 at 3:23 PM, Mike Scherbakov
mscherba...@mirantis.com wrote:
+1 for just reusing existing script, and adjust it on the way. No need to
immediately switch from infinite time to a couple of weeks, we can
I think another important question is how to represent this to the user on
the login screen. Keystone Endpoint: matches the setting, but seems like
a weird choice to me. Is there a better terminology to use for the label
for this on the login screen?
I see the related selector has no label at all
+1
On 10 July 2015 at 05:53, David Lyle dkly...@gmail.com wrote:
On Thu, Jul 9, 2015 at 1:33 PM, Michael Krotscheck krotsch...@gmail.com
wrote:
Hey everyone!
We've been hard at work getting some solid, shared code style rules in
place for our javascript code, and nobody's been more
The is the expected, although security conservative approach to admin
endpoints in fuel, it does pretty much block all actions in keystone other
then auth from outside the cluster. It pre-dates me, and fuel 3.0.1; my
understanding of the intent here is that we don't want a compromise to
result in
It has come to my attention that we spend an enormous amount of time in
Fuel when switching between OpenStack releases. A good amount of this seems
to be due to a chicken and the egg problem. We cant deploy updated packages
with out updated manifests, and we we cant update (in that CI won't pass)
It seems we have a golden opportunity here to improve efficiency by vetting
names before we vote on them. Seems that voting for a bunch of names then
eliminating all of the top votes because they won't work doesn't strike me
as very efficient (i.e. why vote on names that MIGHT be valid).
The
Hi Russell and Gurucharan,
On Thu, Jul 9, 2015 at 5:09 PM, Gurucharan Shetty shet...@nicira.com wrote:
Yes. Though the code that I have has been mostly written with OVN and
Open vSwitch in mind, it uses Neutron APIs and integrates well with
OpenStack. The docker plugin code that I have
We need this. Please find a tool which suites best, and we will let
Dmitry's team to enable it. I assume there is not such a thing in OpenStack
Infra (otherwise we could just reuse it).
Also, I would add a check, that any new bash file should not contain, let's
say, more than 50 lines. If it is
We often have bugs which create really poor User eXperience (UX) but our
current bug priority criteria prevent nearly all of them from being higher
than medium (as they nearly always have workarounds). We need to identify
what should qualify as a critical, or high UX defect so that they can
On 07/09/2015 10:11 AM, Ihar Hrachyshka wrote:
On 07/09/2015 09:01 AM, Artur Korzen wrote:
Hi all,
I've been researching the Neutron project as a part of work on
Openstack rolling upgrades, my primary assignments included
testing if there is no VM access downtime when performing
upgrade.
Hi,
I'm running Fuel 6.1 and i've seen an interesting behavior which i think
match bug [1]
Basically the adminUrl publicUrl part of keystone endpoint are different
And the result of that is that you can't run keystone cli - i.e create/list
tenants etc
keystone --debug tenant-list
On 07/09/2015 12:21 PM, Tomoki Sekiyama wrote:
Hi all,
Just FYI, here is a sample script I'm using for testing os-brick which
attaches/detaches the cinder volume to the host using cinderclient and
os-brick:
https://gist.github.com/tsekiyama/ee56cc0a953368a179f9
python attach.py volume-uuid
+1 for just reusing existing script, and adjust it on the way. No need to
immediately switch from infinite time to a couple of weeks, we can always
adjust it later. But 1-2 month should be a good start already.
Our current stats [1] look just terrible. Before we enable an auto-abandon,
we need to
Hi Daniel,
answer is no - actually there is no strong dependency between public and
internal/admin endpoints. In your case keystone client ask keystone on
address 10.52.71.39 (which, I think, was provided by system
variable OS_AUTH_URL), auth on it and then keystone give endpoints list to
client.
Hello,
I am wondering if there is any documentation for new contributors that
explains how to get up-to-speed with Murano development; something that
covers how to bring code changes into a live Devstack environment, and
test them.
I've looked at the Murano documentation online and have not
On Thu, Jul 9, 2015 at 4:49 PM, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/09/2015 10:55 AM, Antoni Segura Puimedon wrote:
Names: Kuryr - Czech name for Courier since it is delivering
networking to containers. v: apuimedo+1
:) If you
On 07/09/2015 07:16 PM, Adam Lawson wrote:
It seems we have a golden opportunity here to improve efficiency by vetting
names before we vote on them.
The vetting from the crowd was intended to happen on the wikipage. I'm
not sure how much vetting did take place but obviously not enough to
give
On Thu, Jul 09, 2015 at 05:19:06PM +0530, Pradeep kumar wrote:
Hi Hans,
I did traced the function responsible for segmentation fault itz in file
ceval.c. find below
if (*next_instr == SETUP_FINALLY) {
/* Make the last opcode before
a try: finally:
Team,
We held the IRC discussion as scheduled today 2015-07-09 at 23:30 in
#openstack-containers. We tried using Meetbot to log the meeting but that
apparently failed because we crossed the date line to July 10th before we ended
the meeting, so the transcript is available in two parts starting
61 matches
Mail list logo
