-- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph:
303/443-3786
-Original Message- From: Jay Pipes
[mailto:jaypi...@gmail.com] Sent: Wednesday, October 22, 2014 10:10
AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]
[gantt] Scheduler group meeting
Hello Glancers,
Peter and I are having issues working with a Juno Glance endpoint.
Specifically, a glance image-create ... --is_public=True CLI command
that *was* working in our Icehouse cloud is now failing in our Juno
cloud with a 403 Forbidden.
The specific command in question is:
Yup, can do! :)
-jay
On 10/27/2014 01:55 PM, Doug Wiegley wrote:
Hi Jay,
Let’s add that as an agenda item at our Weekly IRC meeting. Can you make
this timeslot?
https://wiki.openstack.org/wiki/Octavia#Meetings
Thanks,
Doug
On 10/27/14, 11:27 AM, Jay Pipes jaypi...@gmail.com wrote
On 10/27/2014 06:18 PM, Jesse Cook wrote:
In the glance mini-summit there was a request for some documentation on
the architecture ideas I was discussing relating to: 1) removing data
consistency as a concern for glance 2) bootstraping vs baking VMs
Here's a rough draft:
/ReleaseNotes/Juno#Upgrade_Notes_3
* The ability to upload a public image is now admin-only by default. To
continue to use the previous behaviour, edit the publicize_image flag in
etc/policy.json to remove the role restriction.
Regards,
Tom
On 28/10/14 01:22, Jay Pipes wrote:
Hello Glancers,
Peter
On 10/28/2014 07:44 AM, Daniel P. Berrange wrote:
One option would be a more CSV like syntax eg
pci_passthrough_whitelist = address=*0a:00.*,physical_network=physnet1
pci_passthrough_whitelist = vendor_id=1137,product_id=0071
But this gets confusing if we want to specifying multiple
On 10/23/2014 07:57 PM, Elzur, Uri wrote:
We’d like to bring it up in the coming design summit. Where do you think
it needs to be discussed: cross project tack? Scheduler discussion? Other?
I’ve just added a proposed item 17.1 to the
On 10/29/2014 07:22 AM, Sean Dague wrote:
On 10/28/2014 05:22 PM, Russell Bryant wrote:
A draft schedule has been posted for the cross-project design summit track:
http://kilodesignsummit.sched.org/overview/type/cross-project+workshops#.VFAFFXVGjUa
If you have any schedule changes to propose
On 10/29/2014 09:07 PM, Russell Bryant wrote:
On 10/29/2014 06:46 PM, Rochelle Grober wrote:
Any chance we could use the opening to move either the Refstack
session or the logging session from their current joint (and
conflicting) time (15:40)? QA really would be appreciated at both.
And I'd
On 10/31/2014 08:00 AM, Thierry Carrez wrote:
Vishvananda Ishaya wrote:
Another option:
3) People consider the lower choices on their list to be
equivalent. I personally tend to vote in tiers (these 3 are top
choices, these 3 are secondary choices, these 6 are third choices)
and I don’t
On 10/28/2014 02:15 PM, Aleksandra Fedorova wrote:
Vitaly,
though comments like this are definitely better than nothing, I think
we should address these issues in a more formal way.
For random failures we have to retrigger the build until it passes.
Yes, it could take some time (two-three
On 11/04/2014 01:08 AM, Heald, Mike wrote:
Thanks for that, Steven :)
So just to clarify, results are ordered by the relevant timestamps to
ensure consistent order and so that new records would never show on
previous pages and be missed, and we're limited to just a next
page navigation, and we
Good morning Stackers,
At the summit in Paris, we put together a plan for work on the Nova
resource tracker and scheduler in the Kilo timeframe. A large number of
contributors across many companies are all working on this particular
part of the Nova code base, so it's important that we keep
++ from me.
On 11/11/2014 05:35 PM, Adam Young wrote:
Recent recurrence of the Why ios everything on its own port question
triggered my desire to take this pattern and put it to rest.
My suggestion, from a while ago, was to have a naming scheme that
deconflicts putting all of the services onto
On 11/17/2014 02:47 PM, Shaunak Kashyap wrote:
Hi,
I’ve been working with the Poppy project[1] while they are designing their
APIs. Poppy has a concept of a flavor. A single flavor resource has the URI,
{base}/flavors/{flavor_id}.
Please, can we as a community kill the term flavor in a
decompose the flavor into a set of capabilities that are
standardized across deployers of the Poppy API, then you have an API
that cannot be interoperable across deployers.
Best,
-jay
Amit.
On 11/17/14, 3:18 PM, Jay Pipes jaypi...@gmail.com wrote:
I personally do not think that a flavor
On 11/18/2014 07:29 AM, Daniel P. Berrange wrote:
On Tue, Nov 18, 2014 at 07:06:59AM -0500, Sean Dague wrote:
Nova currently has 197 patches that have seen no activity in the last 4
weeks (project:openstack/nova age:4weeks status:open).
Of these
* 108 are currently Jenkins -1
On 11/18/2014 06:48 PM, Matt Riedemann wrote:
I just started noticing today that the v3 integrated api samples tests
seem to be taking a lot longer than the other non-v3 integrated api
samples tests. On my 4 VCPU, 4 GB RAM VM some of those tests are taking
anywhere from 15-50+ seconds, while the
Hi Eugene, please see comments inline. But, bottom line, is that setting
the transaction isolation level to READ_COMMITTED should be avoided.
On 11/18/2014 01:38 PM, Eugene Nikanorov wrote:
Hi neutron folks,
There is an ongoing effort to refactor some neutron DB logic to be
compatible with
On 11/18/2014 07:25 PM, Andrew Woodward wrote:
On Tue, Nov 18, 2014 at 3:18 PM, Andrew Beekhof abeek...@redhat.com wrote:
* Openstack services are not managed by Pacemaker
Oh?
fuel doesn't (currently) set up API services in pacemaker
Nor should it, IMO. Other than the Neutron dhcp-agent,
On 11/19/2014 04:00 PM, Matt Riedemann wrote:
On 11/19/2014 9:40 AM, Jay Pipes wrote:
On 11/18/2014 06:48 PM, Matt Riedemann wrote:
I just started noticing today that the v3 integrated api samples tests
seem to be taking a lot longer than the other non-v3 integrated api
samples tests. On my 4
On 11/19/2014 04:27 PM, Eugene Nikanorov wrote:
Wow, lots of feedback in a matter of hours.
First of all, reading postgres docs I see that READ COMMITTED is the
same as for mysql, so it should address the issue we're discussing:
/Read Committed/ is the default isolation level in PostgreSQL.
Hi Sergey! Comments inline.
On 11/20/2014 05:25 AM, Sergey Vasilenko wrote:
Nor should it, IMO. Other than the Neutron dhcp-agent, all OpenStack
services that run on a controller node are completely stateless.
Therefore, I don't see any reason to use corosync/pacemaker for
On 11/20/2014 08:47 AM, Salvatore Orlando wrote:
Aloha guardians of the API!
LOL :)
I haven recently* reviewed a spec for neutron [1] proposing a distinct
URI for returning resource count on list operations.
This proposal is for selected neutron resources, but I believe the topic
is general
...the statement sets the default transaction level for all subsequent
transactions performed within the current session.
All the best, and thanks for the informative lesson of the week!
-jay
On 11/21/2014 03:24 AM, Eugene Nikanorov wrote:
Comments inline:
On Thu, Nov 20, 2014 at 4:34 AM, Jay
On 11/24/2014 08:56 AM, Sean Dague wrote:
Having XML payloads was never a universal part of OpenStack services.
During the Icehouse release the TC declared that being an OpenStack
service requires having a JSON REST API. Projects could do what they
wanted beyond that. Lots of them deprecated and
On 11/24/2014 11:01 AM, Vladimir Kuklin wrote:
Fuelers
I am writing to you to suggest adding prefixes for Fuel subprojects/ as
it becomes more and more difficult to read all the emails in mailing
lists. Adding these prefixes should significantly improve ability of our
engineers to filter out
On 11/24/2014 10:43 AM, Mike Bayer wrote:
On Nov 24, 2014, at 9:23 AM, Adam Young ayo...@redhat.com wrote:
For pieces such as the Nova compute that talk almost exclusively on
the Queue, we should work to remove Monkey patching and use a clear
programming model. If we can do that within the
On 11/24/2014 12:04 PM, Vladimir Kuklin wrote:
[Fuel][Library] for compatibility with other projects. Let's negotiate
the list of prefixes and populate them on our wiki so that everyone can
configure his filters.
++
-jay
___
OpenStack-dev mailing
On 11/24/2014 01:02 PM, pcrews wrote:
On 11/24/2014 09:40 AM, Ben Nemec wrote:
On 11/24/2014 08:50 AM, Matthew Gilliard wrote:
1/ assertFalse() vs assertEqual(x, False) - these are semantically
different because of python's notion of truthiness, so I don't think
we ought to make this a rule.
On 11/13/2014 01:12 AM, Robert Collins wrote:
On 11 November 2014 13:30, Angus Salkeld asalk...@mirantis.com wrote:
Hi all
I just wanted to make sure we are all under the same understanding of the
outcomes and what the next steps for the versioned objects session are.
1. There is a lot of
On 11/24/2014 03:11 PM, Joshua Harlow wrote:
Dan Smith wrote:
3. vish brought up one draw back of versioned objects: the difficulty in
cherry picking commits for stable branches - Is this a show stopper?.
After some discussion with some of the interested parties, we're
planning to add a third
On 11/26/2014 06:20 AM, Nicolas Trangez wrote:
On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote:
I think pointing out that the default failure
message for testtools.TestCase.assertEqual() uses the terms
reference
(expected) and actual is a reason why reviewers *should* ask patch
submitters
On 11/26/2014 09:28 AM, Nicolas Trangez wrote:
On Wed, 2014-11-26 at 08:54 -0500, Jay Pipes wrote:
On 11/26/2014 06:20 AM, Nicolas Trangez wrote:
On Mon, 2014-11-24 at 13:19 -0500, Jay Pipes wrote:
I think pointing out that the default failure
message for testtools.TestCase.assertEqual() uses
.
Why not use the same thing for monitoring the Fuel master host as we do
for the docker containers/cluster?
P.
On 11/26/2014 02:58 PM, Jay Pipes wrote:
On 11/26/2014 08:18 AM, Fox, Kevin M wrote:
So then in the end, there will be 3 monitoring systems to learn,
configure, and debug? Monasca
, the puppet manifests already exist for it and
are used for monitoring other things apparently.
-jay
On Wed, Nov 26, 2014 at 4:39 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 11/26/2014 10:22 AM, Przemyslaw Kaminski wrote:
We want to monitor Fuel master node while
On 11/25/2014 09:34 PM, Mike Bayer wrote:
On Nov 25, 2014, at 8:15 PM, Ahmed RAHAL ara...@iweb.com wrote:
Hi,
Le 2014-11-24 17:20, Michael Still a écrit :
Heya,
This is a new database, so its our big chance to get this right. So,
ideas welcome...
Some initial proposals:
- we do what we
On 11/20/2014 08:12 AM, Sandy Walsh wrote:
Hey y'all,
To avoid cross-posting, please inform your -infra / -operations buddies about
this post.
We've just started thinking about where notification schema files should live
and how they should be deployed. Kind of a tricky problem. We could
On 11/19/2014 01:25 PM, Mike Bayer wrote:
OK so here is why EngineFacade as described so far doesn’t work, because if it
is like this:
def some_api_operation -
novaobject1.save() -
@writer
def do_some_db_thing()
novaobject2.save() -
On 11/27/2014 04:20 PM, Michael Still wrote:
On Fri, Nov 28, 2014 at 2:59 AM, Jay Pipes jaypi...@gmail.com wrote:
On 11/26/2014 04:24 PM, Mike Bayer wrote:
Precisely. Why is the RDBMS the thing that is used for
archival/audit logging? Why not a NoSQL store or a centralized log
facility? All
On 11/17/2014 05:49 PM, Salvatore Orlando wrote:
Hi all,
I am resuming this thread following the session we had at the summit in
Paris (etherpad here [1])
While there was some sort of consensus regarding what this library
should do, and how it should do it, the session ended with some open
Hi Fuel Devs,
I'm not entirely sure why we are running our own infrastructure Gerrit
for Fuel, as opposed to using the main review.openstack.org site that
all OpenStack and Stackforge projects use (including Fuel repositories
on stackforge...). Could someone please advise on why we are doing
On 06/17/2013 02:30 PM, Ben Nemec wrote:
Is there ever a situation where you would use tenant_id and not want
all_tenants=1? If there is then I can maybe see leaving it, but if
tenant_id implies all_tenants=1 then IMHO it's rather poor to force the
user to remember to set it.
To be honest, as
On 06/18/2013 12:43 PM, Martina Kollarova wrote:
Jenkins keeps running all the tests, even if the basic pep8 test fails,
and runs all of the (very slow) Tempest Quantum tests, even though
almost all of them are failing.
I propose that it should fail and stop all of the other tests once there
is
On 06/24/2013 04:49 AM, Wang, Shane wrote:
Hi
I am looking at ceilometer DB code. I find there are 3 tables (UniqueName, Event, Trait), and in
Trait, the two columns name_id and event_id refer to table UniqueName and
table Event.
My question is why we need UniqueName and Event, because in
On 07/01/2013 07:49 PM, Jamie Lennox wrote:
On Mon, 2013-07-01 at 14:09 -0700, Nachi Ueno wrote:
Hi folks
I'm interested in it too.
I'm working on VPN support for Neutron.
Public key authentication is one of feature milestone in the IPsec
implementation.
But I believe key-pair management api
On 07/02/2013 05:32 AM, Victor Sergeyev wrote:
Hello All.
I have a question about the patch `Add unique constraint to FixedIp`
(see https://review.openstack.org/#/c/29364/), which is a part of
blueprint `Complete db unique key enforcement on all tables dbs`
On 07/02/2013 08:26 AM, Simo Sorce wrote:
On Mon, 2013-07-01 at 21:03 -0400, Jay Pipes wrote:
On 07/01/2013 07:49 PM, Jamie Lennox wrote:
On Mon, 2013-07-01 at 14:09 -0700, Nachi Ueno wrote:
Hi folks
I'm interested in it too.
I'm working on VPN support for Neutron.
Public key authentication
is in Keystone.
Best,
-jay
[1]
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L611
I'm open to other options - we are going to build this type of
functionality and I'm interested in how people would like to use it.
Jarret
On 7/2/13 7:46 AM, Jay Pipes jaypi
On 07/02/2013 11:12 AM, Bryan D. Payne wrote:
I don't understand. Users already have custody of their own keys. The
only thing that Keystone/Nova has is the public key fingerprint
[1], not
the private key...
You acatually have the public key, not just the fingerprint,
On 07/04/2013 04:50 PM, Gordon Chung wrote:
hi Folks,
just wanted to bring everyone's attention to this blueprint we have in
Ceilometer:
_https://blueprints.launchpad.net/ceilometer/+spec/support-standard-audit-formats_(detailed
bp:
On 07/08/2013 05:18 PM, Sean Dague wrote:
On 07/01/2013 01:35 PM, Clint Byrum wrote:
The way the new keystone-manage command token_flush works right now
is quite broken by MySQL and InnoDB's gap locking behavior:
https://bugs.launchpad.net/1188378
Presumably other SQL databases like
The way that folsom and nova + nova-network works is that you create a
bunch of unassigned (no tenant assigned to the networks) networks and
when a tenant first launches an instance, nova grabs an available
network for the tenant and assigns it to the tenant. Then each instance
the tenant
made more complicated for the tenant. Instead
of just launching their instance, the tenant now needs to create a
subnet and then launch their instance, passing the subnet ID in the nova
boot command.
-jay
2013/7/16 Jay Pipes jaypi...@gmail.com:
The way that folsom and nova + nova-network
On 07/18/2013 10:44 AM, Murray, Paul (HP Cloud Services) wrote:
Hi All,
I would like to chip in with something from the side here (sorry to stretch the
discussion out).
I was looking for a mechanism to do something like this in the context of this
blueprint on network aware scheduling:
On 07/18/2013 10:09 AM, Sandy Walsh wrote:
Hey y'all!
Running into an interesting little dilemma with a branch I'm working on.
Recently, I introduced a branch in oslo-common to optionally .reject() a
kombu message on an exception. Currently, we always .ack() all messages
even if the processing
On 07/24/2013 02:19 PM, Alex Gaynor wrote:
I think moving towards mock is a better long term strategy:
a) I don't you're correct that it's the most familiar for most python
developers. By PyPi installs (A TERRIBLE METRIC, but it's all we have).
Mock has 24k in the last week, mox has 3.5k
b)
On 07/25/2013 04:21 PM, Joe Gordon wrote:
Hi All,
We have recently hit some performance issues with nova-network. It
turns out the root cause of this was we do roughly 20 rootwrapped shell
commands, many inside of global locks.
(https://bugs.launchpad.net/oslo/+bug/1199433)
It turns out
On 07/26/2013 01:59 PM, Jonathan Proulx wrote:
On Fri, Jul 26, 2013 at 1:01 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 07/25/2013 08:24 PM, Joshua Harlow wrote:
You mean process/forking API right?
Honestly I'd sort of think the whole limits.py
On 07/28/2013 08:04 PM, Angus Salkeld wrote:
On 26/07/13 09:43 -0700, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2013-07-26 06:37:09 -0700:
On 25/07/13 19:07, Bartosz Górski wrote:
We want to start from something simple. At the beginning we are
assuming
no dependencies between
On 07/29/2013 04:29 PM, James E. Blair wrote:
Hi,
Jenkins Job Builder project (part of the Infrastructure program) has
proven to be quite popular!
There are a number of folks who contribute valuable reviews to the
project, and among those, four in particular have stood out recently.
On 07/29/2013 05:12 PM, Michael Basnight wrote:
Rackspace is interested in creating a redis implementation for Trove, as well
as haomai wang is looking to leverage Trove for leveldb integration. Ive done a
proof of concept for redis and it was ~200 lines of guest impl code and I had
to make
I have a question for the auth_token middleware developers.
The default auth_port is set to 35357, which is the admin API port for
Keystone:
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L201
However, the token validation API call
Hi Jessica!
Unfortunately, I'm getting This account's public links are generating
too much traffic and have been temporarily disabled! when I go to that
link...
Is there an alternate location? I'm quite curious about the task flow
library and am looking forward to watching the vid :)
Thanks much!
On 08/02/2013 12:06 PM, Jessica Lucci wrote:
Yes - sorry about that. Wasn't thinking ahead when I uploaded the video. :p
You can view it on youtube here: http://www.youtube.com/watch?v=SJLc3U-KYxQ
*
*
On Aug 2, 2013, at 10:49 AM, Jay Pipes jaypi...@gmail.com
mailto:jaypi
On 08/02/2013 06:26 PM, Herndon, John Luke (HPCS - Ft. Collins) wrote:
Hello, I'm currently implementing the event api blueprint[0], and am
wondering what access controls we should impose on the event api. The
purpose of the blueprint is to provide a StackTach equivalent in the
ceilometer api. I
On 08/06/2013 10:45 AM, David Chadwick wrote:
On 06/08/2013 14:46, Jay Pipes wrote:
API extensions are more hassle than anything else. Let us promote
standards, not endless extensibility at the expense of usability.
This is the crux of the issue. Everyone who participates in
standardisation
On 08/06/2013 01:21 PM, David Chadwick wrote:
On 06/08/2013 18:11, Jay Pipes wrote:
What SMTP, DNS and LDAP extensions are in use by systems that need to
interoperate in the same way that Keystone does? -- This is a genuine
question, not sarcasm. I'm truly curious.
Take SMTP for example. My
On 08/12/2013 08:27 PM, Adam Young wrote:
On 08/12/2013 05:34 PM, Henry Nash wrote:
Hi
I'm working on extending the pagination into the backends. Right now,
we handle the pagination in the v3 controller classand in fact it
is disabled right now and we return the whole list irrespective of
On 08/13/2013 03:05 AM, Yee, Guang wrote:
Passing the query parameters, whatever they are, into the driver if the
given driver supports pagination and allowing the driver to override the
manager default pagination functionality seem reasonable to me.
Please do use the standards that are
, ordering, or other
DB-like operations, then a pagination implementation in the controller
would have to be provided. Not efficient, but better than nothing.
-jay
Mark.
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Tuesday, August 13, 2013 10:10 AM
To: openstack-dev
. Instead, a good filter/search UI would be
better, with just next/prev links.
Best,
-jay
Thanks,
Kiall
On 13/08/13 22:45, Jay Pipes wrote:
On 08/13/2013 05:04 PM, Gabriel Hurley wrote:
I have been one of the earliest, loudest, and most consistent PITA's about
pagination, so I probably
On 08/14/2013 04:31 PM, Jay Buffington wrote:
network is layer 2 and subnet is layer 3.
That's quite confusing.
A common use case would be that one tenant creates a network with a
10.1.1.0/24 http://10.1.1.0/24 subnet. Another tenant wants to use
that same network, so they create a new
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 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 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
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 08/17/2013 03:10 AM, Julien Danjou wrote:
On Fri, Aug 16 2013, Jay Pipes wrote:
Actually, that's the opposite of what I'm suggesting :) I'm suggesting
getting rid of the resource_metadata column in the meter table and using the
resource table in joins...
I think there's a lot of scenario
not speaking about database scalability issues but rather pure
query performance...
Best,
-jay
On Aug 16, 2013, at 12:07 PM, Jay Pipes jaypi...@gmail.com wrote:
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
On 08/18/2013 06:28 PM, Joe Gordon wrote:
On Aug 18, 2013 3:58 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
On 08/18/2013 03:53 AM, Joshua Harlow wrote:
I always just liked SQL as the database abstraction layer ;)
On a more serious note I think novas new object
On 08/18/2013 07:44 PM, Joshua Harlow wrote:
Using an ORM how does the ORM know what attributes u might access (forgive me
if this is a documented sqlalchemy pattern/solution). Doesn't it have to give u
back the full model since the ORM layer can't predict what u might do with the
model
On 08/18/2013 11:07 PM, Robert Collins wrote:
On 19 August 2013 14:22, Jay Pipes jaypi...@gmail.com wrote:
I'm completely with Joshua here - the ORM layer is more often than not
a source of bugs and performance issues.
If used improperly, yep.
http://www.codinghorror.com/blog/2006/06
On 08/19/2013 12:56 AM, Joshua Harlow wrote:
Another good article from an ex-coworker that keeps on making more and
more sense the more projects I get into...
http://seldo.com/weblog/2011/08/11/orm_is_an_antipattern
Your mileage/opinion though may vary :)
I don't disagree with most of that
On 08/18/2013 10:33 PM, Joe Gordon wrote:
An alternative I think would be better would be to scrap the use of
the SQLAlchemy ORM; keep using the DB engine abstraction support.
+1, I am hoping this will provide noticeable performance benefits while
being agnostic of what DB
I'm throwing this up here to get some feedback on something that's
always bugged me about the model base used in many of the projects.
There's a mixin class that looks like so:
class SoftDeleteMixin(object):
deleted_at = Column(DateTime)
deleted = Column(Integer, default=0)
def
OK, cool. I'm in agreement with your explained storage/logic separation
below.
Cheers,
-jay
On 08/19/2013 03:12 AM, Robert Collins wrote:
On 19 August 2013 18:35, Jay Pipes jaypi...@gmail.com wrote:
http://www.codinghorror.com/blog/2006/06/object-relational-mapping-is-the-vietnam
that we can have proper unique constraints by setting it
to `id` on deletion. This was not the case until Grizzly, and before Grizzly I
would have agreed completely.
- Chris
On Aug 19, 2013, at 12:39 AM, Jay Pipes jaypi...@gmail.com wrote:
I'm throwing this up here to get some feedback on something
entry deleted and 1 entry not deleted. Using deleted=`id` to mark
deletion solves that problem. You could use deleted_at… but 2 creates and
deletes within the same second would not work. :)
- Chris
On Aug 20, 2013, at 7:33 AM, Jay Pipes jaypi...@gmail.com wrote:
*sigh* I wish I'd been aware
On 08/20/2013 05:52 PM, Vishvananda Ishaya wrote:
On Aug 20, 2013, at 2:44 PM, Mike Perez thin...@gmail.com
mailto:thin...@gmail.com wrote:
On Tue, Aug 20, 2013 at 1:59 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
We should take a look at look at the various
On 08/20/2013 05:52 PM, Vishvananda Ishaya wrote:
On Aug 20, 2013, at 2:44 PM, Mike Perez thin...@gmail.com
mailto:thin...@gmail.com wrote:
On Tue, Aug 20, 2013 at 1:59 PM, Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com wrote:
We should take a look at look at the various
On 08/19/2013 08:27 AM, Sandy Walsh wrote:
On 08/19/2013 05:08 AM, Julien Danjou wrote:
On Sun, Aug 18 2013, Jay Pipes wrote:
I'm proposing that in these cases, a *new* resource would be added to the
resource table (and its ID inserted in meter) table with the new
flavor/instance's metadata
Hey all,
I'm trying to figure out what is going wrong with my code for this patch:
https://review.openstack.org/41316
I had previously added a sqlalchemy-migrate migration script to add an
event_type table, and had that working, but then was asked to instead
use Alembic for migrations. So, I
compared it to the other migrations and it seems fine.
-S
On 08/26/2013 02:34 PM, Jay Pipes wrote:
Hey all,
I'm trying to figure out what is going wrong with my code for this patch:
https://review.openstack.org/41316
I had previously added a sqlalchemy-migrate migration script to add
migrations and it seems fine.
-S
On 08/26/2013 02:34 PM, Jay Pipes wrote:
Hey all,
I'm trying to figure out what is going wrong with my code for this
patch:
https://review.openstack.org/41316
I had previously added a sqlalchemy-migrate migration script to add an
event_type table, and had
://paste.openstack.org/show/44512/
I've compared it to the other migrations and it seems fine.
-S
On 08/26/2013 02:34 PM, Jay Pipes wrote:
Hey all,
I'm trying to figure out what is going wrong with my code for this
patch:
https://review.openstack.org/41316
I had previously added a sqlalchemy-migrate
On 08/27/2013 11:22 AM, Sandy Walsh wrote:
On 08/27/2013 05:32 AM, Boris Pavlovic wrote:
Jay,
I should probably share to you about our work around DB.
Migrations should be run only in production and only for production
backends (e.g. psql and mysql)
In tests we should use Schemas created by
done in some projects, IIRC... (Glance used to be this
way, at least)
But in OpenStack is not so simple to implement such huge changes, so it
take some time=)
Best regards,
Boris Pavlovic
---
Mirantis Inc.
On Tue, Aug 27, 2013 at 12:02 AM, Jay Pipes jaypi...@gmail.com
mailto:jaypi
Hi Murali, welcome to the OpenStack community. Some comments inline...
On 08/28/2013 06:12 PM, Murali Balcha wrote:
Hello Stackers,
We would like to introduce a new project Raksha, a Data Protection As a
Service (DPaaS) for OpenStack Cloud.
Raksha’s primary goal is to provide a comprehensive
On 08/30/2013 04:37 AM, Nikolay Starodubtsev wrote:
Hi, everyone!
We have created a proposal for Climate REST API
https://docs.google.com/document/d/1U36k5wk0sOUyLl-4Cz8tmk8RQFQGWKO9dVhb87ZxPC8/
And we like to discuss it with everyone.
If you enable commenting on the proposal, then we can put
So I went to do the work I said I was going to do at last week's
Ceilometer meeting -- translate the 2 Alembic migrations in the
Ceilometer source into SA-migrate migrations -- and then rebased my
branch only to find 2 more Alembic migrations added in the last few days:
801 - 900 of 2014 matches
Mail list logo
