On 03/03/2015 02:17 AM, Deepak Shetty wrote:
Hi all,
Can someone give +A to https://review.openstack.org/156940 - we have
the rest. Need to get this merged for glusterfs CI to pass the
snapshot_when_volume_in_use testcases.
thanx,
deepak
Hi Folks,
I was wondering if anyone can comment on the intended behavior of how
instance.host is supported to be set during reschedule operations. For
example, take this scenario:
1. Assume an environment with a single host… call it host-1
2. Deploy a VM, but force an exception in the spawn
On Mar 3, 2015, at 8:34 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:
I’m pretty sure it has always done this: leave the host set on the final
scheduling attempt. I agree that this could be cleared which would free up
room for future scheduling attempts.
Thanks Vish for the
From: John Griffith [mailto:john.griffi...@gmail.com]
Sent: 03 March 2015 14:46
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] auto-abandon changesets considered harmful (was
Re: [stable][all] Revisiting the 6 month release cycle [metrics])
On
On 03/03/2015 10:24 AM, Claudiu Belu wrote:
Hello.
I've talked with Christopher Yeoh yesterday and I've asked him about the
microversions and when will they be able to merge. He said that for now, this
commit had to get in before any other microversions:
Hi,
Is there a way to specify the Juno version to be installed using devstack.
For now we can only specify stable/juno
*git clone -b stable/juno https://github.com/openstack-dev/devstack.git
https://github.com/openstack-dev/devstack.git /opt/stack/devstack*
but this installs 2014.2.3 which
You can specify specific tags for each component in your local.conf file, e.g.:
NOVA_BRANCH=2014.2
CINDER_BRANCH=2014.2
GLANCE_BRANCH=2014.2
HORIZON_BRANCH=2014.2
KEYSTONE_BRANCH=2014.2
KEYSTONECLIENT_BRANCH=2014.2
NOVACLIENT_BRANCH=2014.2
SWIFT_BRANCH=2014.2
HEAT_BRANCH=2014.2
HTH
Alec
I'm in an all day board meeting.
My update is https://launchpad.net/congress/kilo is cleaned up. tagged
https://github.com/stackforge/congress/tree/2015.1.0b2 is out. I am still
working out getting the tarred file out to http://tarballs.openstack.org/ as
part of the process.
~ sean
On Tue, Mar 3, 2015 at 8:46 AM, John Griffith john.griffi...@gmail.com
wrote:
On Tue, Mar 3, 2015 at 7:18 AM, Kuvaja, Erno kuv...@hp.com wrote:
-Original Message-
From: Thierry Carrez [mailto:thie...@openstack.org]
Sent: 03 March 2015 10:00
To:
Hello.
I've talked with Christopher Yeoh yesterday and I've asked him about the
microversions and when will they be able to merge. He said that for now, this
commit had to get in before any other microversions:
https://review.openstack.org/#/c/159767/
He also said that he'll double check
Sean Dague s...@dague.net writes:
Right, I think this is the 'procedural -2' case, which feels like we
need another state for things that are being held for procedural
reasons, which is unrelated to normal code-review.
We have been looking into that and believe we may be able to do
something
John Griffith john.griffi...@gmail.com writes:
Should we just rename this thread to Sensitivity training for
contributors?
I do not think that only new contributors might feel it is negative. I
think that both some new and long-time contributors do.
My oldest patch is from July -- it's
I feel the need to abandon changes that seem abandoned. I believe this has
been covered to death now, so I'm going to shelve that conversation for a
while, and talk about missing tooling in gerrit.
One of the examples of something that was auto-abandoned wrongly was a
patch on hold until some
Nikhil Komawar wrote:
I would like to propose Zhi Yan Liu for the role of stable maintainer
for Glance program.
I'll reach out to Zhi Yan to make sure he is aware of the stable branch
policy[1], then proceed to add him.
[1] https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy
On 3 March 2015 at 17:23, Doug Hellmann d...@doughellmann.com wrote:
Does the tool ignore patches with Workflow-1 set (work in progress)?
So if it doesn't then we can easily change it to do so, however, I think a
WIP progress patch that hasn't been updated for months counts as abandoned
for
You have to make sure it's in ENABLED_SERVICES in stackrc. It was removed by
default, but then apparently restored via
b9f2e25fa8afb2ea17a89ed76c4fac03689b5f07, so if you have that commit, you
should be good.
Otherwise, you can either add it to the ENABLED_SERVICES variable (either in
The Oslo team is pleased to announce the release of:
oslo.config 1.8.0: Oslo Configuration API
For more details, please see the git log history below and:
http://launchpad.net/oslo/+milestone/1.8.0
Please report issues through launchpad:
http://bugs.launchpad.net/oslo
Changes in
Thank you, Thierry!
-Nikhil
From: Thierry Carrez thie...@openstack.org
Sent: Tuesday, March 3, 2015 10:26 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [stable] [Glance] Nomination for
glance-stable-maint
Nikhil Komawar wrote:
The Oslo team is pleased to announce the release of:
cliff 1.10.0: Command Line Interface Formulation Framework
For more details, please see the git log history below and:
https://launchpad.net/python-cliff/+milestone/1.10.0
Please report issues through launchpad:
Hi everyone,
We are replacing our CI network infrastructure today.Therefor it is
necessary for us to postpone the Hyper-V meeting until next week.
p
Peter J. Pouliot CISSP
Microsoft Enterprise Cloud Solutions
C:\OpenStack
New England Research Development Center
1 Memorial Drive
Cambridge,
James Bottomley wrote:
Actually, this is possible: look at Linux, it freezes for 10 weeks of a
12 month release cycle (or 6 weeks of an 8 week one). More on this
below.
I'd be careful with comparisons with the Linux kernel. First it's a
single bit of software, not a collection of
As we know Tempest provides many great tests for verification of
conformance with OpenStack interfaces - the tempest/api directory is
full of such useful stuff. However, regarding the #1422728 ticket [1]
(dependency on private HTTP header of Swift), I think we all need to
answer for one single but
On Tue, Mar 03, 2015 at 09:53:23AM +0100, Miguel Ángel Ajo wrote:
https://review.openstack.org/#/c/159840/1/doc/source/testing/openflow-firewall.rst
I may need some help from the OVS experts to answer the questions from
henry.hly.
Ben, Thomas, could you please? (let me know if you
If it was not clear in my previous message, I would like to again emphasize
that I truly appreciate the vigor and intent behind Flavio's proposal. We need
to be proactive and keep making the community better in such regards.
However, at the same time we need to act fairly, with patience and
So I’m +1 on giving these cores notice and perhaps voting on their removal
separately (as was recently done in another project or two).
Perhaps the way to compromise here would be to submit a change to the
relevant documentation in Glance outlining when a core can be removed (or
when the proposal
On 2/27/2015 1:44 AM, Rattenpal Amandeep wrote:
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
Hi Sahara folks,
FPF [1] will be at Mar 5 and it means that all CRs should be proposed for
features and all new features related CRs will need FPF exception to be
merged.
[1] https://wiki.openstack.org/wiki/FeatureProposalFreeze
--
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
The Oslo team is pleased to announce the release of:
oslosphinx 2.5.0: OpenStack Sphinx Extensions and Theme
For more details, please see the git log history below and:
http://launchpad.net/oslosphinx/+milestone/2.5.0
Please report issues through launchpad:
Hi Christian,
Sorry for the slow response. I was looking into the feasibility of your
suggestion for Sahara in particular and it took a bit.
On 2/19/15, 2:46 AM, Christian Schwede christian.schw...@enovance.com
wrote:
Hello Jonathan,
On 18.02.15 18:13, Halterman, Jonathan wrote:
1. Swift
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This
is primarily in service of getting rid of the custom workers we
Oooh, ok! Yeah, additional tests for that would help us clearly see that solved.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
On 03 Mar 2015, at 18:03, Peter Razumovsky prazumov...@mirantis.com wrote:
Hi Renat,
We solved problem with referencing. I'll add more tests for understanding,
how
Hey all,
It appears that currently a number of OpenStack services are not
generating version catalogs correctly when the service sits behind a
proxy. (Reference: https://bugs.launchpad.net/glance/+bug/1384379) Glance
already has a fix that was accepted for kilo-1 but it is suboptimal and
assumes
On 03/03/2015 11:28 AM, Radoslaw Zarzynski wrote:
As we know Tempest provides many great tests for verification of
conformance with OpenStack interfaces - the tempest/api directory is
full of such useful stuff. However, regarding the #1422728 ticket [1]
(dependency on private HTTP header of
On Tue, 2015-03-03 at 17:10 +0200, Duncan Thomas wrote:
I feel the need to abandon changes that seem abandoned
I think there is an agreement that there should be a way to have a clean
view of changesets that are being actively worked on, changes where the
owner is responding to comments, working
Hi Stackers,
I am referring to one of the action item related to metadata discussed
here;
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
Can some help with the final take away (Sorry I could not find any thread
related to its decision after this meeting).
Is common sense an option here?
More specifically I mean leveraging the common sense of both contributors
and core reviewers (or whoever is authorized to abandon patches).
The formers should abandon patches they're not working on anymore, and
expect somebody else to do that if the patches they
On Tue, Mar 3, 2015 at 12:51 AM, Luis Pabon lpa...@redhat.com wrote:
What is the status on virtfs? I am not sure if it is being maintained.
Does anyone know?
The last i knew its not maintained.
Also for what its worth, p9 won't work for windows guest (unless there is a
p9 driver for windows
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
(As of Mon, 02 Mar 17:00 UTC)
Open: 129 (-7)
3 new (-4), 32 in progress (-4), 0 critical, 18 high and 7 incomplete
security bug found and
Hello,
I would vote for 2nd, but i also think that we can generate same
information, on merge for example, that will be printed during first run
and place it directly in repository (maybe even README?). I guess this is
what your 3rd approach is about?
So, can we go with both?
On Tue, Mar 3,
There have been a couple of patches [1] [2] proposed to neutron recently that
could impact our support for Xen+OVS, but I don’t see an easy way for us to
validate such changes. I’m not aware of a 3rd party CI job that runs against
Xen, and I don’t know of any active contributors able to
We certainly care about this but converting the XenServer CI to Neutron+OVS has
been hitting a number of issues (notably a few concurrency ones – although
there are a few missing features) that we’ve been trying to sort through.
I am certainly hoping that we’ll have everything stable enough to
On Feb 25, 2015, at 10:47 AM, Doug Hellmann
d...@doughellmann.commailto: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
It might make sense to send this to the users list as well. There may be a
large deployment out there with resources willing to at least test changes
even if they don't have any upstream development resources.
On Tue, Mar 3, 2015 at 12:50 PM, Maru Newby ma...@redhat.com wrote:
There have been a
On 03/03/2015 01:10 AM, Rui Chen wrote:
Hi all,
When we boot instance from volume, we find some ambiguous description
about flavor root_gb in operations guide,
http://docs.openstack.org/openstack-ops/content/flavors.html
/Virtual root disk size in gigabytes. This is an ephemeral disk the base
On 03/03/2015 06:55 AM, Joe Cropper wrote:
On Mar 3, 2015, at 8:34 AM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
I’m pretty sure it has always done this: leave the host set on the
final scheduling attempt. I agree that this could be cleared which
would free up room for future scheduling
On Mar 3, 2015, at 1:06 PM, Kevin Benton blak...@gmail.com wrote:
It might make sense to send this to the users list as well. There may be a
large deployment out there with resources willing to at least test changes
even if they don't have any upstream development resources.
Good call,
Hi Marek,
I tried with the auto-generated shibboleth2.xml, just added the application
override attribute, now im stuck with looping issue,
when i access v3/OS-FEDERATION/identity_providers/idp_2/protocols/saml2/auth
for the first time it is prompting for username and password once provided it
Hi,
I'm trying to listen to events of type compute.instance.* (e.g.
compute.instance.update).
I tried the following code:
from oslo_config import cfg
import oslo_messaging
class NotificationEndpoint(object):
filter_rule =
oslo_messaging.NotificationFilter(publisher_id='compute.*',
After update my devstack to obtain b9f2e25fa8afb2ea17a89ed76c4fac03689b5f07, it
works now.
Thanks very much.
-chen
-Original Message-
From: Solly Ross [mailto:sr...@redhat.com]
Sent: Tuesday, March 03, 2015 11:48 PM
To: OpenStack Development Mailing List (not for usage questions)
Am 03.03.2015 um 19:31 schrieb Deepak Shetty:
[...]
For us security is very critical, as the performance is too. The
first solution via ganesha is not what we prefer (to use CephFS
via p9 and NFS would not perform that well I guess). The second
solution, to use CephFS directly to the VM would
On Mar 3, 2015, at 1:44 PM, Bob Ball bob.b...@citrix.com wrote:
We certainly care about this but converting the XenServer CI to Neutron+OVS
has been hitting a number of issues (notably a few concurrency ones –
although there are a few missing features) that we’ve been trying to sort
On Thu, Feb 26, 2015 at 3:32 PM, Doug Hellmann d...@doughellmann.com
wrote:
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
The glance_store release management team is pleased to announce:
glance_store version 0.1.12 has been released on Tuesday March 3rd around
23.51 UTC.
For more information, please find the details at:
https://launchpad.net/glance-store/+milestone/v0.1.12
Please report the issues
Hi,
Don't let the subject throw you off :)
I wasn't sure how to phrase what I wanted to capture in this mail, and
that seemed reasonable enough. I wanted to kick off a discussion about
what gaps people think are missing from TripleO before we can meet the
goal of realistically being able to use
Added [swift] to topic.
On 03/03/2015 07:41 AM, Matthew Farina wrote:
Radoslaw,
Unfortunately the documentation for OpenStack has some holes. What you
are calling a private API may be something missed in the documentation.
Is there a documentation bug on the issue? If not one should be
Logged a bug [1] and submitted a fix [2]. Review away!
[1] https://bugs.launchpad.net/nova/+bug/1427944
[2] https://review.openstack.org/#/c/161069/
- Joe
On Mar 3, 2015, at 4:42 PM, Jay Pipes jaypi...@gmail.com wrote:
On 03/03/2015 06:55 AM, Joe Cropper wrote:
On Mar 3, 2015, at 8:34
On Wed, Mar 4, 2015 at 5:10 AM, Danny Al-Gaaf danny.al-g...@bisect.de
wrote:
Am 03.03.2015 um 19:31 schrieb Deepak Shetty:
[...]
For us security is very critical, as the performance is too. The
first solution via ganesha is not what we prefer (to use CephFS
via p9 and NFS would not
@Christian I'm so glad to hear you are interested! I'm adding more details
below :)
@John Thanks for sharing your experience! It's great to know that both you
and mahatic enjoyed the internship
So, more details about the internship
For mentees,
From March 3rd to March 24th mentees have time to
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
Thursday, March 5th at 22:00 UTC in the #openstack-meeting channel.
The agenda for the meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to
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-scheduler.
I had registered a blueprint and commit a patch to implement it.
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 and
Thank you for reply, @Jay.
+1 for
There should not be any magic setting for root_gb that needs to be
interpreted both by the user and the Nova code base.
I will try to restart the patch 136284 on the other way, like: instance
object.
Best Regards
2015-03-04 4:45 GMT+08:00 Jay Pipes
While it is entirely possible that the feature is broken, it seems that in
this case you're expecting the allowed_address_pairs to populate fixed_ips.
Neutron does many crazy and unreasonable things but asking you to pass an
attribute in the request to populate another attribute is not one of
On Tue, Feb 24, 2015, at 08:15 PM, Solly Ross wrote:
Those scripts have mostly moved into oslotest, so they don't need to be
synced any more to be used. If you have all of your code, and it follows
the cookiecutter template, we can look at it and propose post-import
tweaks. What's the
Ian, thanks for raising the issue here.
The X-Forwarded headers are the standard way to deal with URLs for services
behind proxies. I already commented on the Heat proposal to that effect, I
think that is the proper way to support services behind proxies.
Now in our case, there is also another
Hello,
Recently we've found that break_on property of RetryPolicy is not working
now.
I tried to solve this problem but faced the another problem: How does
'break_on' supposed to work?
Will 'break_on' change the task state to ERROR or SUCCESS?
if ERROR, it means 'we interrupt all retry
Hi,
I have a question regarding the implicit volume resources that created by Nova
during persistent
VM's snapshot creation. Here is a sample scenario that leaves a set of volume
resources as residue,
1. Create a bootable volume, bv_1
2. Create an instance vm_1, from the bootable volume bv_1
-Original Message-
From: Thierry Carrez [mailto:thie...@openstack.org]
Sent: 03 March 2015 10:00
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] auto-abandon changesets considered harmful
(was Re: [stable][all] Revisiting the 6 month release cycle [metrics])
Bump.
I'd really appreciate some answers to the question Sean asked. I still
have the 2.4 in my review (the very one Sean mentioned) but it seems
that it might not be the case.
Best regards,
Alex Levine
On 3/2/15 2:30 PM, Sean Dague wrote:
This change for the additional attributes for
https://review.openstack.org/#/c/159840/1/doc/source/testing/openflow-firewall.rst
I may need some help from the OVS experts to answer the questions from
henry.hly.
Ben, Thomas, could you please? (let me know if you are not registered to
the openstack review system, I could answer in your
Hi all,
When we boot instance from volume, we find some ambiguous description about
flavor root_gb in operations guide,
http://docs.openstack.org/openstack-ops/content/flavors.html
*Virtual root disk size in gigabytes. This is an ephemeral disk the base
image is copied into. You don't use it
Hi Peter,
Thanks for sharing this.. Overall it looks good to me, I just left a couple of
comments/questions in
https://review.openstack.org/#/c/147645/17/contrib/heat_mistral/heat_mistral/tests/test_workflow.py
Hi all,
Next round application deadline for Outreachy is close and and we need
mentors willing to help newcomers to get involved with OpenStack and help
them start contributing [0][1].
This would be the 5th time OpenStack joins Outreachy and for now we can say
we are having a great outcome for
Hi all! The email, that I sent on 2/24 didn't make it to the mailing list
(no wonder I didn't get responses!). I think I had an issue with my email
address used - sorry for the confusion!
So, I'll hold the meeting today (1500 UTC meeting-4, if it is still
available), and we can discuss this...
Anteaya,
In general i agree, but because of TZ differences, not always you can do
that.
Also i sent mail only for the case where we had all +1, +2, just needed
workflow +1, which I think is justfiable !
thanx,
deepak
On Tue, Mar 3, 2015 at 1:30 PM, Anita Kuno ante...@anteaya.info wrote:
On
I’m pretty sure it has always done this: leave the host set on the final
scheduling attempt. I agree that this could be cleared which would free up room
for future scheduling attempts.
Vish
On Mar 3, 2015, at 12:15 AM, Joe Cropper cropper@gmail.com wrote:
Hi Folks,
I was wondering if
On Tue, Mar 3, 2015, at 07:56 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:15 PM, Jeremy Stanley wrote:
After a long wait and much testing, we've merged a change[1] which
moves the remainder of Python 3.3 based jobs to Python 3.4. This
is
Hi,
I see that the neutron port resource has a property named as
allowed_address_pairs and I tried to use this property to create a port,
but seems it does not working.
I want to create a port with mac as fa:16:3e:05:d5:9f and ip as
192.168.0.58, but after create with a heat template, the final
Nikhil,
If I recall correctly this matter was discussed last time at the start of the
L-cycle and at that time we agreed to see if there is change of pattern to
later of the cycle. There has not been one and I do not see reason to postpone
this again, just for the courtesy of it in the hopes
Hi folks!
According to the refactoring plan [1] we are going to release the 6.1 version
of python-fuelclient which is going to contain recent changes but will keep
backwards compatibility with what was before. However, the next major release
will bring users the fresh CLI that won’t be
80 matches
Mail list logo
