On Aug 15, 2013, at 12:50 PM, Joe Gordon joe.gord...@gmail.com wrote:
•
On Thu, Aug 15, 2013 at 12:22 PM, Sam Harwell sam.harw...@rackspace.com
wrote:
I like to take a different approach. If my commit message is going to take
more than a couple lines for people to understand the
On 2013?08?16? 14:34, Christopher Yeoh wrote:
On Fri, Aug 16, 2013 at 10:28 AM, Melanie Witt melw...@yahoo-inc.com
mailto:melw...@yahoo-inc.com wrote:
On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote:
+1 from me as long as this wouldn't change anything for the EC2
API's security
On 16 August 2013 20:15, Maru Newby ma...@redhat.com wrote:
This pattern has one slight issue, which is:
• Do not assume the reviewer has access to external web services/site.
In 6 months time when someone is on a train/plane/coach/beach/pub
troubleshooting a problem browsing GIT
On Wed, Aug 14, 2013 at 04:53:01PM -0700, Vishvananda Ishaya wrote:
Hi Everyone,
I have been trying for some time to get the code for the live-snapshot
blueprint[1]
in. Going through the review process for the rpc and interface code[2] was
easy. I
suspect the api-extension code[3] will
On Fri, Aug 16, 2013 at 11:05:19AM +0100, Daniel P. Berrange wrote:
On Wed, Aug 14, 2013 at 04:53:01PM -0700, Vishvananda Ishaya wrote:
Hi Everyone,
I have been trying for some time to get the code for the live-snapshot
blueprint[1]
in. Going through the review process for the rpc and
On 14/08/13 17:08 -0300, Sandy Walsh wrote:
At Eric's request in https://review.openstack.org/#/c/41979/ I'm
bringing this to the ML for feedback.
Currently, oslo-common rpc behaviour is to always ack() a message no
matter what.
Hey,
I don't think we should keep adding new features to Oslo's
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it instead
of custom implementation and so on. As there were a lot of questions it was
really hard to answer on all this questions in IRC. So we
Boris,
+1 to getting started on oslo.db
-- dims
On Fri, Aug 16, 2013 at 9:52 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix bugs, improve handling of sqla exceptions, provide
unique keys, and to use this code in
On Aug 16, 2013, at 6:52 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around DB code
in Grizzly and Havana to unify it, put all common parts into oslo-incubator,
fix bugs, improve handling of sqla exceptions, provide
+1
What about the keystone status in oslo?
On Fri, Aug 16, 2013 at 10:40 PM, David Ripton drip...@redhat.com wrote:
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common
I believe there are reviews in Keystone for bring this in:
https://review.openstack.org/#/c/38029/
https://review.openstack.org/#/c/38030/
https://blueprints.launchpad.net/keystone/+spec/use-common-oslo-db-code
Best Regards,
Lance Bragstad
Software Engineer - OpenStack
Cloud Solutions and
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and reviewing requirements
changes for a little while now. I think it would be extremely helpful to
+1
mark
On Aug 16, 2013, at 11:04 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote:
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and
Hi folks,
I’m glad to announce Savanna intention to apply for the incubation during
Icehouse release. In this email I would like to provide an update on our
current status and nearest plans and, as well as start the conversation to
solicit the feedback on Savanna from the community.
Let’s
On 08/16/2013 11:04 AM, Doug Hellmann wrote:
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and reviewing requirements
changes for a little
+1
On 08/16/2013 11:04 AM, Doug Hellmann wrote:
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and reviewing requirements
changes for a little
Hi,
I'm looking for help, ideally some code or curl examples, figuring out why
I can't consume trusts in the manner specified in the documentation:
https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3-os-trust-ext.md
I've been working on
On Thu, Aug 15, 2013 at 6:39 PM, Randall Burt randall.b...@rackspace.comwrote:
On Aug 15, 2013, at 6:20 PM, Angus Salkeld asalk...@redhat.com wrote:
On 15/08/13 17:50 -0500, Christopher Armstrong wrote:
2. There should be a new custom-built API for doing exactly what the
autoscaling
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix bugs, improve handling of sqla exceptions, provide
unique keys, and to use
On 08/16/2013 09:31 AM, Victor Sergeyev wrote:
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it
instead of custom implementation and so on. As there were a lot of
questions it was really
On Fri, Aug 16 2013, Boris Pavlovic wrote:
Thoughts?
Way to go.
--
Julien Danjou
/* Free Software hacker * freelance consultant
http://julien.danjou.info */
signature.asc
Description: PGP signature
___
OpenStack-dev mailing list
On Fri, Aug 16, 2013 at 9:31 AM, Victor Sergeyev vserge...@mirantis.com wrote:
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it instead
of custom implementation and so on. As there were a lot
On Tue, 2013-08-13 at 22:09 +0100, Mark McLoughlin wrote:
Hi
We're having an IRC meeting on Friday to sync up again on the messaging
work going on:
https://wiki.openstack.org/wiki/Meetings/Oslo
https://etherpad.openstack.org/HavanaOsloMessaging
Feel free to add other topics to the
On 16/08/13 11:42 -0400, Monty Taylor wrote:
On 08/16/2013 09:31 AM, Victor Sergeyev wrote:
Hello All.
Glance cores (Mark Washenberger, Flavio Percoco, Iccha Sethi) have some
questions about Oslo DB code, and why is it so important to use it
instead of custom implementation and so on. As
On Aug 16, 2013, at 2:12 AM, Robert Collins robe...@robertcollins.net wrote:
On 16 August 2013 20:15, Maru Newby ma...@redhat.com wrote:
This pattern has one slight issue, which is:
• Do not assume the reviewer has access to external web services/site.
In 6 months time when someone
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix bugs, improve handling of sqla exceptions, provide
unique keys, and to use this
On Fri, Aug 16, 2013 at 3:05 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Wed, Aug 14, 2013 at 04:53:01PM -0700, Vishvananda Ishaya wrote:
Hi Everyone,
I have been trying for some time to get the code for the live-snapshot
blueprint[1]
in. Going through the review process for the
On 2013-08-14 16:10, Matthew Treinish wrote:
On Wed, Aug 14, 2013 at 11:05:35AM -0500, Ben Nemec wrote:
On 2013-08-13 16:39, Clark Boylan wrote:
On Tue, Aug 13, 2013 at 1:25 PM, Matthew Treinish
mtrein...@kortar.org wrote:
Hi everyone,
So for the past month or so I've been working on getting
On 2013-08-16 11:58, Jay Pipes wrote:
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around
DB
code in Grizzly and Havana to unify it, put all common parts into
oslo-incubator, fix bugs, improve handling of sqla exceptions,
On 15/08/13 19:14, Chan, Winson C wrote:
I updated the implementation section of
https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy on instance
naming to support UpdatePolicy where in the case of the LaunchConfiguration
change, all the instances need to be replaced and to
Neutron has been in and out of the gate for the better part of the past month,
and it didn't slow the pace of development one bit. Most Neutron developers
kept on working as if nothing was wrong, blithely merging changes with no
guarantees that they weren't introducing new breakage. New bugs
I'd strongly agree with that, a project must always be gated by any tests
for it, even if they don't gate for other projects. I'd also argue that any
time there's a non-gating test (for any project) it needs a formal
explanation of why it's not gating yet, what the plan to get it to gating
is, and
Turns out I'll be traveling that day so won't be able to run the meeting. If
there's anyone who wants to volunteer to lead the meeting speak now, otherwise
we can just cancel next week.
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
I would prefer to pick and choose which parts of oslo common db code to
reuse in glance. Most parts there look great and very useful. However, some
parts seem like they would conflict with several goals we have.
1) To improve code sanity, we need to break away from the idea of having
one giant db
On 08/16/2013 02:25 PM, Maru Newby wrote:
Neutron has been in and out of the gate for the better part of the
past month, and it didn't slow the pace of development one bit. Most
Neutron developers kept on working as if nothing was wrong, blithely
merging changes with no guarantees that they
Excerpts from Maru Newby's message of 2013-08-16 11:25:07 -0700:
Neutron has been in and out of the gate for the better part of the past
month, and it didn't slow the pace of development one bit. Most Neutron
developers kept on working as if nothing was wrong, blithely merging changes
with
On 08/16/2013 01:17 PM, Vishvananda Ishaya wrote:
On Fri, Aug 16, 2013 at 3:05 AM, Daniel P. Berrange berra...@redhat.com
mailto:berra...@redhat.com wrote:
I don't think it is a good idea to add a feature which is considered to
be unsupportable by the developers of the virt
On 08/16/2013 02:41 PM, Mark Washenberger wrote:
I think the issue here for glance is whether or not oslo common code
makes it easier or harder to make other planned improvements. In
particular, using openstack.common.db.api will make it harder to
refactor away from a giant procedural interface
On Fri, Aug 16, 2013 at 01:03:57PM -0500, Ben Nemec wrote:
Getting this in before the H3 rush would be very helpful. When we made
the switch with Nova's unittests we fixed as many of the test bugs
that we could find, merged the change to switch the test runner, then
treated all failures as
On Tue, Aug 13, 2013 at 2:36 PM, Thomas Maddox
thomas.mad...@rackspace.comwrote:
Hello!
I was having some chats yesterday with both Julien and Doug regarding
some thoughts that occurred to me while digging through CM and Doug
suggested that I bring them up on the dev list for everyones
Excerpts from Ben Nemec's message of 2013-08-16 11:10:09 -0700:
On 2013-08-16 11:58, Jay Pipes wrote:
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around
DB
code in Grizzly and Havana to unify it, put all common
On 08/16/2013 04:00 PM, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2013-08-16 11:10:09 -0700:
On 2013-08-16 11:58, Jay Pipes wrote:
On 08/16/2013 09:52 AM, Boris Pavlovic wrote:
Hi all,
We (OpenStack contributors) done a really huge and great work around
DB
code in Grizzly and
I added a couple of comments in the wiki page. We should have at least one
summit session about this, I think, unless we work it out before then.
On Thu, Aug 15, 2013 at 12:20 PM, Sandy Walsh sandy.wa...@rackspace.comwrote:
Recently I've been focused on ensuring we don't drop notifications in
If you're saying that you want to register URLs without version info
embedded in them, and let the client work that part out by talking to the
service in question (or getting a version number from the caller), then
yes, please.
On Fri, Aug 16, 2013 at 1:47 AM, Robert Collins
On 17 August 2013 08:27, Doug Hellmann doug.hellm...@dreamhost.com wrote:
If you're saying that you want to register URLs without version info
embedded in them, and let the client work that part out by talking to the
service in question (or getting a version number from the caller), then
yes,
On 08/16/2013 04:37 PM, Doug Hellmann wrote:
On Fri, Aug 16, 2013 at 4:15 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 08/16/2013 03:52 PM, Doug Hellmann wrote:
However, that's just one example use case. Sometimes people do
want to
know
On Fri, Aug 16, 2013 at 4:43 PM, Jay Pipes jaypi...@gmail.com wrote:
On 08/16/2013 04:37 PM, Doug Hellmann wrote:
On Fri, Aug 16, 2013 at 4:15 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 08/16/2013 03:52 PM, Doug Hellmann wrote:
However, that's just
Is OpenStack supported on CentOS running Python 2.6?
Thanks,
Mark
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Fri, Aug 16, 2013 at 2:51 PM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:
Is OpenStack supported on CentOS running Python 2.6?
I can't speak to what features are supported and whether or not it is
practical for real deployments, but we do all upstream Python 2.6
I'm running the unit tests and can confirm they do work.
I'm currently developing support for xenserver-core on CentOS 6.4 and many of
the tempest tests pass, and I'm working through the failures that exist.
I haven't encountered anything yet which is caused by CentOS so I imagine it
will all
On Fri, Aug 16, 2013 at 8:04 AM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
I'd like to propose Alex Gaynor for core status on the requirements project.
Alex is a core Python and PyPy developer, has strong ties throughout the
wider Python community, and has been watching and reviewing
Hi,
I can see on following link that many of the latest code reviews are
reporting build failure at the same point?
https://review.openstack.org/#/q/status:open+project:openstack/python-neutronclient,n,z
The backtrace looks liike:
ft46.1:
My team has deployed hundreds of compute nodes on CentOS-5.4(with python26
installed and Xen as hypervisor ) based on Folsom. It does work on our
production system :)
2013/8/17 Miller, Mark M (EB SW Cloud - RD - Corvallis)
mark.m.mil...@hp.com
Is OpenStack supported on CentOS running Python
Now in Centos 6.x ,the Python is 2.6.6, the Openstack can run it. you can
check the RDO
http://openstack.redhat.com/Quickstart
On Sat, Aug 17, 2013 at 8:05 AM, Yufang Zhang yufang521...@gmail.comwrote:
My team has deployed hundreds of compute nodes on CentOS-5.4(with python26
installed and
I asked on #openstack-infra and clarkb immediately identified it as a
problem with cliff, and saw that the cliff folks have apparently already
fixed it in cliff 1.4.3, which is now on the openstack.org pypi mirror so
new gate jobs should start passing now.
On Fri, Aug 16, at 7:34 pm, Ronak Shah
without proxy , the test case is PASS. with proxy set in localrc,
euca-register will fail with a 400 code. it is weird that even 127.0.0.1 is
already included in no_proxy and it turned out that the api was never
through proxy.
Here I did a capture of both with and without proxy scenario, doing a
Excerpts from Thierry Carrez's message of 2013-08-16 13:55:46 -0700:
Jay Pipes wrote:
Are you going to create a separate Launchpad project for the library
and track bugs against it separately? Or are you going to use the oslo
project in Launchpad for that?
At the moment all of the
58 matches
Mail list logo
