On Wed, Feb 18, 2015 at 8:54 PM, Dean Troyer dtro...@gmail.com wrote:
I think one thing needs to be clarified...what you are talking about is
utilizing keystoneclient's auth plugins in neutronclient. Phrasing it as
'novaclient parity' reinforces the old notion that novaclient is the model
Hi,
I was playing around with the various dhcp/radvd options of neutron.
Very helpful was the matrix [1] that describes the combinations of ra
and adress mode that can be configured.
For dhcpv6-stateful (ra adress mode) it says: VM obtains IPv6 address
from dnsmasq using DHCPv6 stateful and
On Thu, Feb 19, 2015 at 12:24:14PM +0600, Renat Akhmerov wrote:
Guys,
I really appreciate the input of you all.
We decided that ideally we need to agree on that syntax within days, not
weeks or months. But anyway, since we started this discussion yesterday I
just want to give
On Feb 19, 2015, at 11:52, Terry Wilson twil...@redhat.com wrote:
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
https://jenkins04.openstack.org/job/gate-neutron-pylint/1383/console
2015-02-19
Hi xarses,
As you said, I changed nic type from vmxnet3 to e1000 and set security
policy to permissive for all the networks. Now I am able to successfully
deploy VM as additional compute node in existing openstack environment.
Thanks for you time!
--
Thanks Regards
E-Mail:
The Keystone development team is planning to deprecate deployment of Keystone
under Eventlet during the Kilo cycle. Support for deploying under eventlet will
be dropped as of the “M”-release of OpenStack.
The reasoning behind this move is multifaceted but the core of the reasons are
as
Sorry, I dropped the ball here. This is now released.
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
https://jenkins04.openstack.org/job/gate-neutron-pylint/1383/console
2015-02-19 18:37:06.932 |
Imo, neutron has wrong usage of novaclient.
https://review.openstack.org/#/c/152907/ should fix this issue.
On Thursday, February 19, 2015, Terry Wilson twil...@redhat.com
javascript:_e(%7B%7D,'cvml','twil...@redhat.com'); wrote:
Sorry, I dropped the ball here. This is now released.
I can do another release if needed once we've landed a fix, although
it sounds like this can be fixed in neutron?
Michael
On Fri, Feb 20, 2015 at 7:33 AM, melanie witt melwi...@gmail.com wrote:
On Feb 19, 2015, at 11:52, Terry Wilson twil...@redhat.com wrote:
Unfortunately, the new novaclient
On Thu, Feb 19, 2015, at 01:09 PM, Ben Nemec wrote:
Hi,
Mike Bayer recently tracked down an issue with database errors in Cinder
to a single database connection being shared over multiple processes.
This is not something that should happen, and it turns out to cause
intermittent failures
I can do another release if needed once we've landed a fix, although
it sounds like this can be fixed in neutron?
It's just pylint being silly, from the sound of it. I don't think there
is anything we need to do in novaclient, since the transition adapter
works. Either convince neutron pylint
Hi,i followed
http://docs.openstack.org/developer/keystone/configure_federation.html, im
using icehouse on ubuntu 12.04
From: aks...@outlook.com
To: openstack-dev@lists.openstack.org
Subject: Error Enabling Federation Extension
Date: Thu, 19 Feb 2015 17:22:36 +0530
im getting “Target WSGI
On Wed, Feb 18, 2015 at 7:14 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Wed, Feb 18, 2015, at 10:07 AM, Donald Stufft wrote:
On Feb 18, 2015, at 10:00 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Tue, Feb 17, 2015, at 03:17 PM, Joe Gordon wrote:
On Tue, Feb 17,
On Thu, Feb 19, 2015, at 03:59 PM, Joe Gordon wrote:
On Wed, Feb 18, 2015 at 7:14 AM, Doug Hellmann d...@doughellmann.com
wrote:
On Wed, Feb 18, 2015, at 10:07 AM, Donald Stufft wrote:
On Feb 18, 2015, at 10:00 AM, Doug Hellmann d...@doughellmann.com
wrote:
On
On Feb 19, 2015, at 12:48, Dan Smith d...@danplanet.com wrote:
Either convince neutron pylint not to care, or just convert the
uses in neutron to v2.
In pylint, E0611 is the check which could be disabled to ignore this case.
http://pylint-messages.wikidot.com/messages:e0611
melanie (melwitt)
My guess is that your dhcp client running inside the VM set up the subnet
mask as /128. Dhcpv6 doesn¹t provide prefix length, but the client system
sometime adds the net mask based on the link type. Some of the dhcp
clients use a script to configure the interface, and I think you can use
/64 if
Nova contains a config variable osapi_compute_unique_server_name_scope.
Its help text describes it pretty well:
When set, compute API will consider duplicate hostnames invalid within
the specified scope, regardless of case. Should be empty, project or
global.
So, by default hostnames are not
On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
I entcountered a similar case more recently on powerkvm 2.1.0
(defect with the libguestfs)
What's the actual bug? We've worked hard, with IBM, to make
libguestfs work on POWER 7 and POWER 8 systems. I have full access to
those
im getting “Target WSGI script ‘/var/www/cgi-bin/keystone/main’ cannot be
loaded as Python module”while configuring federation for keystone any help
[info] [client 10.10.10.12] mod_wsgi (pid=25248, process=’keystone’,
application=’10.1.193.250:5000|’): Loading WSGI script
Dear All,
I have Openstack HA environment (all are physical machine) deployed using
Fuel 5.1. I want to bring one more compute node in VM(VM is running in
vCenter and configured 4 nic).
How to deploy a compute node in VM and bring this to existing openstack
environment?
Any help.
--
Thanks
Thank you Ben!,
Cross posting [1] to openstack list /neutron.
[1] http://benpfaff.org/~blp/dist-docs.
On Thursday, 19 de February de 2015 at 09:13, Ben Pfaff wrote:
On Thu, Feb 19, 2015 at 12:12:26AM -0800, Ben Pfaff wrote:
This commit adds preliminary design documentation for Open
I think all these operations for nodes (grouping, sorting, filtering) can
be done on the backend, but we can do it completely on the UI side and
shouldn't wait for backend implementation. We can switch to it after it
becomes available.
2015-02-17 19:44 GMT+07:00 Sergey Vasilenko
Hi !
From those three I'd choose only { ... }, it looks better for YAML while
'%' sign looks foreign for YAML. Moreover, it needs extra spaces for
writing expressions:
Compare:
1. %$.var + 1%
2. % $.var + 1 %
3. {$.var + 1}
One more point from me: We can't do things just beacuse it is familiar
On 18/02/15 18:23, Raphael Glon wrote:
Hi,
This is about review:
https://review.openstack.org/#/c/156633/
1 line, can be controversial
Its purpose is to add the possibility not to use libguestfs for data
injection in nova, even when installed.
Not discussing about the fact that
On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
Hi,
This is about review:
https://review.openstack.org/#/c/156633/
1 line, can be controversial
Its purpose is to add the possibility not to use libguestfs for data
injection in nova, even when installed.
Not discussing
Hey folks,
I’d like to invite the broader OpenStack community to participate in developing
milestone #3 of Kolla – a Project to Containerize the deployment of OpenStack.
This is a major refactoring of Kolla to make it viable for use by projects such
as TripleO or Fuel.
We have an aggressive
Hello Jonathan,
On 18.02.15 18:13, Halterman, Jonathan wrote:
1. Swift should allow authorized services to place a given number
of object replicas onto a particular rack, and onto separate
racks.
This is already possible if you use zones and regions in your ring
files. For example, if you
Folks, one more thing to consider: the next big release of yaql (1.0,
coming really soon) will get support of curly braces (by default - to
initialise dictionaries in the following way:
v0.2/v0.3 syntax: dict(key1=value1, key2=value2)
v1 syntax: {key1=value1, key2=value2} (the old syntax
@Renat, They are conceptually different:
- regular tokens are created for the owner of addressed resource
- trust scoped tokens are for trustees and have some security restrictions.
The case is about disallowing a trustee to aquire a regular token allowing
him anything the trustor is allowed. It'd
-Original Message-
From: Clark Boylan [mailto:cboy...@sapwetik.org]
Sent: Tuesday, February 17, 2015 6:06 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] The root-cause for IRC private channels (was
Re: [all][tc] Lets keep our community open, lets fight for it)
On 2/12/2015 6:55 PM, Michael Still wrote:
This was discussed in the nova meeting this morning. In that meeting
we declared ourselves unwedged and ready to do a release, and I said
I'd do that today.
On reflection, I want to recant just a little -- I think its a bad
idea for me to do a
Hi everyone!
On one of our meetings [1] we agreed on keeping *ED states (DELETED,
INSPECTED, CLEANED, etc) as no-ops for now. Since then, however, the
inspection patch [2] got several comments from cores requesting removal
of INSPECTED state. That was done by Nisha.
Today we decided to
Hi Akshik,
Could you give some more details about the steps you did for configuring
federation as well as the environment you are using?
Is it devstack? What version of Keystone do you use?
Thanks,
Marek
On 19.02.2015 12:52, Akshik DBK wrote:
im getting “Target WSGI script
- Original Message -
From: Irena Berezovsky irenab@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
On Thu, Feb 5, 2015 at 9:01 PM, Steve Gordon sgor...@redhat.com wrote:
- Original Message -
From:
Hello folks
we have a bunch of upcoming initiatives to help out new contributors to
OpenStack and we need mentors willing to help newcomers go from zero to
(at least) one merged patch.
OpenStack has always been a welcoming community despite being complex to
navigate for new contributors. If you
Hello-
The Ironic team is pleased to announce the release of the 2014.2.1 stable
Juno release. This release contains a number of backported fixes that have
accrued in our stable branch since the release of 2014.2. These updates to
Juno are intended to be low risk with no intentional
regressions
Hi,
Mike Bayer recently tracked down an issue with database errors in Cinder
to a single database connection being shared over multiple processes.
This is not something that should happen, and it turns out to cause
intermittent failures in the Cinder volume service. Full details can be
found in
On 02/19/2015 05:18 AM, Matthew Booth wrote:
Nova contains a config variable osapi_compute_unique_server_name_scope.
Its help text describes it pretty well:
When set, compute API will consider duplicate hostnames invalid within
the specified scope, regardless of case. Should be empty, project
@Renat, I like the idea. For now we have a spec:
https://github.com/openstack/keystone-specs/blob/master/api/v3/identity-api-v3-os-trust-ext.rst
It's consiedered to be enough but as for me it lacks TL;DR section :)
On Thu, Feb 19, 2015 at 8:15 PM, Renat Akhmerov rakhme...@mirantis.com
wrote:
Sorry, I dropped the ball here. This is now released.
As promised last week in the nova meeting I've checked the docs on the
wiki for releases
(https://wiki.openstack.org/wiki/Nova/Client_Release_Process) and
fixed some small errors. I'll look at adding John Garbutt and Matt
Riedemann to the
On 2015-02-19 17:03:49 +0100 (+0100), Deepak Shetty wrote:
[...]
For some reason we are seeing the centos7 glusterfs CI job getting
aborted/ killed either by Java exception or the build getting
aborted due to timeout.
[...]
Hoping to root cause this soon and get the cinder-glusterfs CI job
The Neutron team is proud to announce the release of the latest version of
python-neutronclient. This release includes the following bug fixes and
improvements:
3e5c6ba Updated from global requirements
a774e84 Add unit tests for agentscheduler related commands
069b14c Fix for incorrect parameter
- Original Message -
On Feb 19, 2015, at 11:52, Terry Wilson twil...@redhat.com wrote:
Unfortunately, the new novaclient release ended up completely breaking the
neutron gate. The v1_1 deprecation broke our (voting) pylint test:
Kudos!
Edgar
From: Kyle Mestery mest...@mestery.commailto:mest...@mestery.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, February 19, 2015 at 1:35 PM
To: OpenStack Development
This creates a bit of a problem for downstream (packagers and probably
others) Shipping a requirements.txt with explicit pins will end up
producing an egg with a requires.txt that reflects those pins, unless there
is some other magic planned that I'm not aware of. I can't speak for all
packaging
[moving this conversation to openstack-dev because it's more
interesting there and that avoids crossposting to a subscribers-only
list]
On Thu, Feb 19, 2015 at 10:57:02AM +0100, Miguel ??ngel Ajo wrote:
I specially liked the VIF port lifecycle, looks good to me, Ionly miss
some
Thanks. It looks like openstack-dev only accepts posts from
subscribers, so I've followed up to your more detailed feedback only
on that list. For anyone following along at home, here's an archives
link:
http://lists.openstack.org/pipermail/openstack-dev/2015-February/057376.html
On Thu, Feb
Neutron should not depend on versioning implementation in novaclient.
There is get_contrib_module function in
https://review.openstack.org/#/c/152569/9/novaclient/client.py , which
should help to renounce the use of direct import of versioning stuff of
novaclient, but now, imo, we should use
[Adding neutron tag to subject, comments below.]
On Thu, Feb 19, 2015 at 3:55 PM, Ben Pfaff b...@nicira.com wrote:
[moving this conversation to openstack-dev because it's more
interesting there and that avoids crossposting to a subscribers-only
list]
On Thu, Feb 19, 2015 at 10:57:02AM
Here's the news from doc land.
Install Guides are no longer publishing to docs.openstack.org/trunk. They
are published only to a release such as docs.openstack.org/juno or
docs.openstack.org/icehouse. Also this patch removes the Debian Install
Guide until the instructions are fixed so that users
Hi Kyle, Ihar,
It looks promising to have our patch upstreamed. Please take a look at this
pull request
https://github.com/tomaszmrugalski/dibbler/pull/26#issuecomment-75144912. Most
importantly, Tomek asked if it’s sufficient to have the code up in his master
branch. I guess you guys may be
On Thu, Feb 19, 2015 at 1:48 PM, Adam Gandelman ad...@ubuntu.com wrote:
This creates a bit of a problem for downstream (packagers and probably
others) Shipping a requirements.txt with explicit pins will end up
producing an egg with a requires.txt that reflects those pins, unless there
is
Hi Team
Please discuss the bug given below:
https://bugs.launchpad.net/python-novaclient/+bug/1415319
Is it a bug ? the bug is left for discussion.
Thanks,
Amandeep
Mail to: rattenpal.amand...@tcs.com
=-=-=
Notice: The information contained in this e-mail
message and/or
On Fri, Feb 20, 2015 at 07:27:33AM +0100, Philipp Marek wrote:
Potentially corrupted images are bad; depending on the affected data it
might only be diagnosed some time after installation, so IMO the fix is
needed.
Sure but there is a (potentially hefty) performance impact.
Only a minor
On Thu, Feb 19, 2015 at 5:53 PM, Tony Breeds t...@bakeyournoodle.com wrote:
Hi all,
In September I started working on a simple (but controvertial) fix in
nova[1]
to avoid some disk corruption issues. John kindly ran with a similar fix to
cinder[2].
John's review ended up in merge
On Feb 19, 2015, at 13:38, Terry Wilson twil...@redhat.com wrote:
We've currently just disabled the pylint gate tests, and I've posted a patch
for neutron to resolve the issue. Looks like there was a similar patch
already up for review as well, though it only catches one of our uses of
On Feb 19, 2015, at 17:54, Matt Riedemann mrie...@linux.vnet.ibm.com wrote:
Regarding the novaclient change, the plan is to get either the devstack cells
exercise job voting on novaclient changes again (which it was at some point
prior to the 2.21 release and should have caught this
On 2/19/2015 6:06 PM, Henry Gessau wrote:
The fix: https://review.openstack.org/157606
On Thu, Feb 19, 2015, Joe Gordon joe.gord...@gmail.com wrote:
neutronclient is requiring a keystone client that is way too new for icehouse.
2.3.11 was released (And breaks with semver), but icehouse has a
Hi All,
I would like to discuss the Chassis Discovery Tool Blueprint -
https://review.openstack.org/#/c/134866/
The blueprint suggests Hardware enrollment and introspection for properties at
the Chassis layer. Suitable for micro-servers that have an active chassis to
query for details.
Hi Team
Please discuss the bug given below:
https://bugs.launchpad.net/python-novaclient/+bug/1415319
Is it a bug ? the bug is left for discussion.
Thanks,
Amandeep
Mail to: rattenpal.amand...@tcs.com
=-=-=
Notice: The information contained in this e-mail
message and/or
Hi Team
As per V2 API specification load balancer healthmonitor has a parameter type
which can not be parsed by JSON parser.
So, it must be replaced by healthmonitor_type as per the OpenDayLight Bug-
( https://bugs.opendaylight.org/show_bug.cgi?id=1674 )
I reported a bug related to this
Thanks for both of those bits of information.
I've added an allow-related action for v3.
On Thu, Feb 19, 2015 at 06:38:46PM -0800, Kevin Benton wrote:
Yes, if there is an action similar to the 'RELATED' and 'ESTABLISHED'
keywords, then that should be adequate to replace the iptables solution
Hi all,
I requested a session for future lbaas features and prioritizing (and attaching
contributors to those features.) Assuming that happens, I started an etherpad
here, starting with Sam’s info:
https://etherpad.openstack.org/p/lbaas-vancouver-planning
Its more than just the naming. In the original proposal, requirements.txt
is the compiled list of all pinned deps (direct and transitive), while
requirements.in reflects what people will actually use. Whatever is in
requirements.txt affects the egg's requires.txt. Instead, we can keep
In September I started working on a simple (but controvertial) fix in
nova[1]
to avoid some disk corruption issues. John kindly ran with a similar fix
to cinder[2].
John's review ended up in merge conflict so I tried my own version [3].
Thanks for sending this out, and for the
And this just broke icehouse jobs. Which means devstack-gate is broken.
http://logs.openstack.org/53/157553/1/check/check-tempest-dsvm-full-icehouse/6c63b71//logs/devstacklog.txt.gz#_2015-02-19_22_21_21_419
There where some questions regarding direction for this on the fuel meeting
today. Can you elaborate on the status?
On Thu, Feb 12, 2015 at 12:01 PM, Andrew Woodward xar...@gmail.com wrote:
On Thu, Feb 12, 2015 at 3:59 AM, Tomasz Napierala tnapier...@mirantis.com
wrote:
On 10 Feb 2015,
Hey Everyone,
Anteaya was kind enough to ask in the Cinder channel about some tests
that were added to the gate for SheepDog [1]. I would like to know
why there's no process for the projects that are impacted by these
changes to have input? At the very least if someone is adding test
Joshua Harlow harlo...@outlook.com wrote:
Doug Hellmann wrote:
On Thu, Feb 19, 2015, at 01:09 PM, Ben Nemec wrote:
Hi,
Mike Bayer recently tracked down an issue with database errors in Cinder
to a single database connection being shared over multiple processes.
This is not something
Hi clarkb, fungi,
As discussed in
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-02-19.log
( 2015-02-19T14:51:46 onwards), I am starting this thread to track the
abrupt job failures seen on cinder-glusterfs CI job in the recent past.
A small summary of the
Can the *ED states be optional? If a state would be a NO-OP, then don't
use it. But if it is useful then use it.
It seems ugly to me to just have two 'change state' calls to move it
through the *ED state.
If an *ED state needs to be added later I think it could be added without
too much
1. Query neutron data from DB
2. Discover to which computation node it belongs
you can query port's information with neutron command.
like neutron port-list -c id -c device_owner and find device_owner ==
compute:* ports.
and also find compute node witch port(and instance) deployed on.
you can
On 19 Feb 2015, at 18:32, Alexander Makarov amaka...@mirantis.com wrote:
@Renat, They are conceptually different:
- regular tokens are created for the owner of addressed resource
- trust scoped tokens are for trustees and have some security restrictions.
The case is about disallowing a
I was discussing the problems of configuring active/passive HA earlier
where the active and passive nodes have a different `host` configured.
There are lots of problems, as I've mentioned before, but Gary pointed
out that it probably affects image cache management, too. This had the
potential for
I think that if there is a use case for an *ED state, then we should have
it. And if we have one *ED state, I think it makes sense (and is
consistent) to have them for all the active states.
If we have *ED states, I would prefer that we add them in when the active
state is added. So add stateING,
Hi,
Following error is being reported by zuul and any one facing this issue ?
zuul is failing with No valid host was found. There are not enough hosts
available for https://review.openstack.org/#/c/153999/.
I tried twice to build this patch and same error is reported. I think this
error is
On 2/2/15, 15:41, Morgan Fainberg morgan.fainb...@gmail.com wrote:
On February 2, 2015 at 1:31:14 PM, Joe Gordon (joe.gord...@gmail.com)
wrote:
On Mon, Feb 2, 2015 at 10:28 AM, Morgan Fainberg
morgan.fainb...@gmail.com wrote:
I think the simple answer is yes. We (keystone) should emit
On 2015-02-19 12:12:30 + (+), Kuvaja, Erno wrote:
[...]
[3] The data protection rules are applicable not only when the
controller is established within the EU, but whenever the
controller uses equipment situated within the EU in order to
process data. (art. 4) Controllers from outside
Matt Riedemann wrote:
This was ready to go as of Monday. Can we really only have the PTL do
this release? As far as I know, any core on python-novaclient should be
able to do this if they have a GPG key to launchpad, then they just need
to push the tagged release per [1].
The way
Hi,
I have been using openstack in multi-node setup - pre stable/juno release -
and recently updated the setup to stable/juno and noticed after launching
an instance, spoofing rules on all compute nodes are getting updated,
whereas updating spoofing rules only on the compute node the instance is
Hi, magnetians!
Just to remind that our IRC weekly meetings are held every week on
Thursdays 14:00 UTC at #magnetodb on Freenode. Please join.
Meeting agenda:
https://wiki.openstack.org/wiki/MagnetoDB/WeeklyMeetingAgenda
If you have an item to share, please add it to agenda.
Andrey Ostapenko
The fix: https://review.openstack.org/157606
On Thu, Feb 19, 2015, Joe Gordon joe.gord...@gmail.com wrote:
neutronclient is requiring a keystone client that is way too new for icehouse.
2.3.11 was released (And breaks with semver), but icehouse has a limit
of 2.4. So global-requirements for
Proposals for the fishbowl, working and sprint sessions with the block
storage project Cinder can be submitted now:
https://etherpad.openstack.org/p/cinder-liberty-proposed-sessions
On April 27th, we will be discussing these together in the Cinder IRC
meeting [1]. This will allow time to set
Hi,
The Nova API subgroup is planning on releasing V2.1 on Monday (changing its
status from experimental to CURRENT) and merging the first patch which uses
microversions on top of 2.1 on the Wednesday.
In the meantime we'd appreciate it if reviewers did not +A any patchset
which changes the REST
Hi all,
In September I started working on a simple (but controvertial) fix in
nova[1]
to avoid some disk corruption issues. John kindly ran with a similar fix to
cinder[2].
John's review ended up in merge conflict so I tried my own version [3].
While (trying) to add workarounds to nova
On Thu, Feb 19, 2015, at 04:38 PM, John Griffith wrote:
Hey Everyone,
Anteaya was kind enough to ask in the Cinder channel about some tests
that were added to the gate for SheepDog [1]. I would like to know
why there's no process for the projects that are impacted by these
changes to
Hello all,
Over the past few weeks the os-ansible-deployment team has been working on
getting the repository (https://github.com/stackforge/os-ansible-deployment)
into a more community friendly state. For anyone who’s look at the project in
the past and thought it was too Rackspace specific
neutronclient is requiring a keystone client that is way too new for
icehouse. 2.3.11 was released (And breaks with semver), but icehouse has a
limit of 2.4. So global-requirements for icehouse needs to be fixed.
2015-02-19 22:21:21.419
Doug Hellmann wrote:
On Thu, Feb 19, 2015, at 01:09 PM, Ben Nemec wrote:
Hi,
Mike Bayer recently tracked down an issue with database errors in Cinder
to a single database connection being shared over multiple processes.
This is not something that should happen, and it turns out to cause
On Thu, Feb 19, 2015 at 5:59 PM, Clark Boylan cboy...@sapwetik.org wrote:
On Thu, Feb 19, 2015, at 04:38 PM, John Griffith wrote:
Hey Everyone,
Anteaya was kind enough to ask in the Cinder channel about some tests
that were added to the gate for SheepDog [1]. I would like to know
why
Morgan Fainberg morgan.fainb...@gmail.com wrote:
The Keystone development team is planning to deprecate deployment of Keystone
under Eventlet during the Kilo cycle. Support for deploying under eventlet
will be dropped as of the “M”-release of OpenStack.
The reasoning behind this move is
On 20 February 2015 at 08:32, Morgan Fainberg morgan.fainb...@gmail.com wrote:
The Keystone development team is planning to deprecate deployment of
Keystone under Eventlet during the Kilo cycle. Support for deploying under
eventlet will be dropped as of the “M”-release of OpenStack.
\o/
-Rob
All,
As we all know, bug triage rotation really helps us to respond Tempest bugs
as quick as possible and keep bug count low.
Thanks for signing up in bug triage rotation.
To continue the same strategy and keeping good progress on bugs, we need
more volunteers to sign-up for coming weeks.
The novaclient 2.21 release had a bug in some bash completion code that
blows up the voting devstack cells job that runs exercises. The bug
tracking the novaclient issue is:
https://bugs.launchpad.net/nova/+bug/1423695
We're blocking the 2.21 release in global-requirements to get master
Yes, if there is an action similar to the 'RELATED' and 'ESTABLISHED'
keywords, then that should be adequate to replace the iptables solution
that we have now.
You are correct about the reason behind the explosion of rules. In security
groups, we allow the source/dest field to be a reference to a
The glance_store release management team is pleased to announce:
glance_store version 0.1.11 has been released on Thursday Feb 19th around
23.40 UTC.
For more information, please find the details at:
https://launchpad.net/glance-store/v0/v0.1.11
Please report the issues through
Doug Hellmann d...@doughellmann.com wrote:
5) Allow this sort of connection sharing to continue for a deprecation
period with apppropriate logging, then make it a hard failure.
This would provide services time to find and fix any sharing problems
they might have, but would delay the
97 matches
Mail list logo
