Hey all,
For the better part of the last week, I've been struggling to use
SQLAlchemy-Migrate to produce database migration scripts for Glance.
In Glance, unlike Nova, we have a unit test that tests that the
database for Glance's registry can be downgraded and upgraded
smoothly. In Nova, none of
On Mon, Mar 21, 2011 at 12:21 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
Do we have patches for approach #3?
For some things, not all.
I'm thinking that if we have a few
specific issues, that maybe we could maintain our own branch and/or
monkey-patch SA-migrate, and get a better
On Mon, Mar 21, 2011 at 1:08 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
By seemed powerful, did you actually try it on anything more than
simple add a table/drop a table scripts? Did you try it on more than a
single database? Did you use the SQL scripting as well as the Python
change
On Mon, Mar 21, 2011 at 5:42 PM, Brian Schott bfsch...@gmail.com wrote:
1.a.) Not yet, but our branch unit tests (when we get there) will certainly
test the architecture-related columns we added to instances, instance_types,
and compute_node tables.
1.b) Is that a unit test responsibility
I know you don't want to resurrect a past discussion. But, UUIDs are
designed to solve these kind of problems, frankly. The decision to go
with integer IDs is a poor one, and will be negatively affecting the
scalability and architecture of our systems well into the future.
I'd love to see a
On Mon, Mar 28, 2011 at 5:48 AM, Thierry Carrez thie...@openstack.org wrote:
I'd like to say that I dislike this type of behind closed doors
development, where things are developed without a blueprint, bug or
linked branch and then thrown very late into the review queue.
We do an open source
On Mon, Mar 28, 2011 at 1:38 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
No objection to a discussion during the summit, but I've been able to watch
all of these branches and others evolve here:
https://code.launchpad.net/nova
For example, when I wanted to add VNC support because my
On Mon, Mar 28, 2011 at 2:32 PM, Todd Willey t...@ansolabs.com wrote:
Open == Accessible. Open != Verbose. I'm willing to discuss more at
the design summit, but my biggest concern is that we let the most
people possible can contribute. This includes those who work behind
closed doors on
Just wanted to say thank you for putting together an excellent spec document.
Thanks,
jay
2011/3/31 石井 久治 ishii.hisah...@lab.ntt.co.jp:
Hi Everyone,
I have implemented a POC code for Pluggable Network Service at
lp:~ntt-pf-lab/nova/network-service. And wrote the document of it
On Thu, Mar 31, 2011 at 5:21 PM, Michael Barton
mike-launch...@weirdlooking.com wrote:
I'm gonna +1 Todd.
Actually, apache server has a great dev process. They have goals for
releases, but people are welcome to submit patches to their mailing
list any time, get comments on them, then they're
Well said. I don't disagree with any of your points or suggestions
below. Looking forward to a productive chat about it at the summit in
a few weeks.
-jay
On Thu, Mar 31, 2011 at 6:09 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
There has been a lot of great discussion and airing-out
On Fri, Apr 1, 2011 at 8:41 AM, FUJITA Tomonori
fujita.tomon...@lab.ntt.co.jp wrote:
I bet that we'll face more serious shortage of reviewing with
developers increasing. In genera, developers prefer to write own code
rather than reviewing. We can't change the nature.
Yes, this is certainly
On Fri, Apr 1, 2011 at 9:19 AM, FUJITA Tomonori
fujita.tomon...@lab.ntt.co.jp wrote:
Yeah, but discussion on the mailing list before the summit is useful
(developers who can't attend the summit are able to discuss, I might
not be able to make it too).
True enough :) Didn't mean to suggest the
Hey all,
Subject basically says it all. Justin has proven to be a regular and
thorough reviewer and unless he objects, I propose he join the
nova-core team as a core reviewer.
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to :
All,
In an effort to speed up our code development processes, reduce the
friction amongst existing contributors and reduce barriers to entry
for new contributors familiar with the popular git DVCS, we (the
OpenStack@Rackspace team) have been studying a transition of our code
hosting from
at 05:21:20PM -0400, Jay Pipes wrote:
All,
In an effort to speed up our code development processes, reduce the
friction amongst existing contributors and reduce barriers to entry
for new contributors familiar with the popular git DVCS, we (the
OpenStack@Rackspace team) have been studying
Hi Brian, comments inline :)
On Tue, Apr 12, 2011 at 12:34 PM, Brian Schott bfsch...@gmail.com wrote:
I'm trying to understand how best to implement our architecture-aware
scheduler for Diablo:
https://blueprints.launchpad.net/nova/+spec/schedule-instances-on-heterogeneous-architectures
Hey all,
We're in the planning stages for Diablo now, working on putting
together blueprints, which turn into sessions at the design summit.
I know the Glance team is small and our project narrow in scope, but
it would be great to get some feedback from the list about stuff you'd
like to see
Hi! Comments inline :)
2011/4/13 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com:
1) OVF support. I know it's not exactly a disk image format, but
probably we could look deeper if it make sense to add OVF or not. And
if not, where does it fit in the overall architecture.
2)
Thanks, Thierry, for all your assistance during the last couple weeks
organizing the various freezes. It's a thankless job and often very
frustrating. You keep your cool at all times. Thanks for that!
-jay
On Thu, Apr 14, 2011 at 4:46 AM, Thierry Carrez thie...@openstack.org wrote:
Hello
This is an excellent point, Mark, I'd forgotten about the quota system
for user-defined (and nova-ignored) metadata items. That does throw
a bit of a wrench into the mix. Perhaps a small edit to the
instance_metadata table to add a column for is_user_added that can be
used to segregate metadata
, Apr 15, 2011 at 11:56 AM, Ed Leafe ed.le...@rackspace.com wrote:
On Apr 15, 2011, at 11:43 AM, Jay Pipes wrote:
Yes, I'm aware of how the Zone Manager works. But, you still need a
persistent data store for attributes of the host. Just because you
store a cached in-memory copy of instance
and registry servers.
This test suite can serve as the basis for some integration tests that
stress Glance working with both Nova and Swift.
-jay
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On Apr 12, 2011, at 11:11 AM, Jay Pipes wrote:
Hey all,
We're in the planning
I don't see any blueprint proposed or anyone working on this, so I
think you're good to go! :)
On Mon, Apr 18, 2011 at 7:22 PM, masumo...@nttdata.co.jp wrote:
Hi,
Does anyone who is planning to implement kvm-pause/kvm-suspend? Currently,
nova pause(unpause) id or nova suspend(resume) id
Jay,
What are your ideas for a glance dashboard app above and beyond what the
OpenStack dashboard currently supports? This would be a great thing for us
to spend a bit of time talking about at the summit.
- Devin
On Apr 12, 2011, at 11:11 AM, Jay Pipes wrote:
Hey all,
We're
django module would
be super rad as well.
Yep, that's what I was talking about for OpenStack Dashboard.
And agreed on the Swift Django module, too :)
-jay
Vish
On Apr 19, 2011, at 10:28 AM, Jay Pipes wrote:
On Tue, Apr 19, 2011 at 1:23 PM, Ken Pepple ken.pep...@rabbityard.com
wrote:
On Apr
Yes, I'll defer to Devin's judgment on this one... :)
Devin, feel free to update the blueprint Ken mentioned below.
-jay
On Tue, Apr 19, 2011 at 2:52 PM, Ken Pepple ken.pep...@rabbityard.com wrote:
On Apr 19, 2011, at 11:08 AM, Devin Carlen wrote:
So anyone building a Django based UI that
On Mon, May 2, 2011 at 11:48 AM, Rick Clark r...@openstack.org wrote:
Since the number of projects seems to be increasing daily, I think we should
create a #openstack-meeting schedule page on the wiki, so we don't
accidentally conflict. It would also be a central place to see what teams
are
On Tue, May 3, 2011 at 7:16 PM, Ken Pepple ken.pep...@rabbityard.com wrote:
Do we have to break out all the projects into their own development channels
?
Can't we just have a #openstack-dev to cover them all ?
There are a lot of cross-project discussions (especially between
nova/glance, but
On Tue, May 3, 2011 at 7:58 PM, Jorge Williams
jorge.willi...@rackspace.com wrote:
On May 3, 2011, at 6:29 PM, Eldar Nugaev wrote:
Could you please provide information - why we want to see values
field in JSON and who is responsable for implementation this
specification in OS API 1.1?
We
Blueprints are typically used for specific features, but you can also
have supertask blueprints that serve as a way to group related
blueprints together. Each blueprint can have zero or more
dependencies, which allow you to construct dependency graphs. For an
example of this, see here:
Hey all!
Thanks for a great design summit last week. Just wanted to send a
quick note about what is planned for Glance in Diablo. We got a ton of
work done in Cactus to achieve better integration with Nova, and we're
excited to add more features and stability to Glance for the Diablo
series.
+1 for getting rid of em..
On Thu, May 5, 2011 at 10:00 AM, Soren Hansen so...@linux2go.dk wrote:
There's a couple of old PPA's that people still stumble upon. They
filled with ancient versions of OpenStack, so they're completely
useless.
https://launchpad.net/~nova-core/+archive/ppa
Sounds like some better cross-team communication is in order :)
On Thu, May 5, 2011 at 11:14 AM, Chuck Thier cth...@gmail.com wrote:
Hey Soren,
We've asked similar questions before :)
Ever since the packaging was pulled out of the source tree, we have been
mostly out of the packaging loop.
+1
On Tue, May 10, 2011 at 4:13 PM, Paul Voccio paul.voc...@rackspace.com wrote:
All,
I would like to nominate Dan Prince (https://launchpad.net/~dan-prince) for
nova-core. He has been a solid contributor in terms of code, reviews and
discussions during the summit.
Thanks,
pvo
Hey all,
We've been working to improve the Glance API. The first step to
improving the API, however, is to add versioning to it.
We've gotten a lot of the work done on this versioning of the API (see
https://code.launchpad.net/~jaypipes/glance/api-version/+merge/60130).
However, there is an
Mark's been a very good reviewer and an invaluable resource on the API
side, particularly regarding serialization. I propose he join
nova-core.
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Hey all,
I'm going to remove myself from the nova-core group. I'll still do
reviews and stuff, but I've been focusing a lot on Glance, and there
are much more knowledgeable folks already on and proposed for
nova-core.
Not sure if this is the way to go about resigning from nova-core,
but since
++ on your suggestions.
On Wed, May 11, 2011 at 3:38 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
Hello Everyone,
We have quite a large backlog of merge proposals here:
https://code.launchpad.net/~rlane/nova/lp773690/+merge/59565
I've been attempting to go through them to find some
On Tue, May 17, 2011 at 11:59 AM, Glen Campbell
glen.campb...@rackspace.com wrote:
If we are going to deploy Glance to support a global deployment of Nova,
would it make sense to have replicas in different regions for better
performance?
Or, to put it another way, is there a recommended way
Hi Jorge! Comments inline :)
On Mon, May 23, 2011 at 9:42 AM, Jorge Williams
jorge.willi...@rackspace.com wrote:
Hi Sandy,
My understanding (Correct me if i'm wrong here guys) is that creating
multiple instances with a single call is not in scope for the 1.1 API.
Actually, I don't think we
atomic operations on the instance creation level.
Cheers!
jay
On Mon, May 23, 2011 at 10:35 AM, Jorge Williams
jorge.willi...@rackspace.com wrote:
Comments inline:
On May 23, 2011, at 8:59 AM, Jay Pipes wrote:
Hi Jorge! Comments inline :)
On Mon, May 23, 2011 at 9:42 AM, Jorge Williams
On Mon, May 23, 2011 at 12:33 PM, Brian Schott
brian.sch...@nimbisservices.com wrote:
Why does getting the instance id require the API to block? I can create 1 or
1000 UUIDs in order (1) time in the API server and hand back 1000 instance
ids in a list of server entries in the same amount of
On Mon, May 23, 2011 at 5:54 PM, Sandy Walsh sandy.wa...@rackspace.com wrote:
We can have Feats of Strength later to decide how this should live on in an
OS API 2.0 world.
I'll bring the Festivus pole.
-jay
___
Mailing list:
I misspoke in my original email.
Marker should be the timestamp of the initial query.
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
On Wed, May 25, 2011 at 1:38 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
The SQL query using the PK would look like this (and there's no need for an
OFFSET clause):
SELECT *
FROM table
ORDER BY pk
WHERE pk @marker
AND (additional filters)
LIMIT pagesize
Without additional
This is what happens when I braindump a bunch of stuff into an
email... I get myself confused :)
I'm proposing the following. Please pick the strategy apart:
1) Pass the LIMIT and OFFSET parameters down into the database API queries
2) Add a default ORDER BY for all queries returning result sets
On Wed, May 25, 2011 at 3:10 PM, Greg Holt gh...@rackspace.com wrote:
Okay cool. Just stop using the term offset anywhere in your examples then and
drop the whole page= thing as well. :)
Sorry, I'm not understanding what you're getting at here. The offset
is required to pass to the database
On Wed, May 25, 2011 at 3:32 PM, Greg Holt gh...@rackspace.com wrote:
select w from x where y marker order by y limit z
This gives you consistent pagination, means the database doesn't have to
count matching rows to find an offset, and means you could shard by y later
in life if you need
On Wed, May 25, 2011 at 3:43 PM, Greg Holt gh...@rackspace.com wrote:
Okay, I give up then. Not sure what's different with what you have vs. Swift
dbs. Just trying to offer up what we do and have been doing for a while now.
The pagination in Swift is not consistent. Inserts into the Swift
On Thu, May 26, 2011 at 9:56 AM, Michael Barton
mike-launch...@weirdlooking.com wrote:
On Wed, May 25, 2011 at 2:40 PM, Jay Pipes jaypi...@gmail.com wrote:
The pagination in Swift is not consistent. Inserts into the Swift
databases in between the time of the initial query and the requesting
FYI, this has implications for both Nova and Glance.
Our relevant bug on Launchpad for this is here:
https://bugs.launchpad.net/glance/+bug/787296
Ta,
-jay
-- Forwarded message --
From: Jan Dittberner jan.dittber...@googlemail.com
Date: Thu, May 26, 2011 at 11:41 AM
Subject:
I think Erik's looking for a timeframe for this, too.
We could implement this tomorrow in Glance, but there's been a
conscience decision to use URIs as an image's globally-unique
identifier, and to allow Glance registries to implement whatever image
ID they wanted. This can, of course, change,
On Fri, May 27, 2011 at 8:52 PM, Mark Nottingham m...@mnot.net wrote:
Hi,
I've started looking at the 1.1 API draft [1] and want to give some feedback.
The draft says that feedback is welcome on the bug queue [2], but I suspect
it'd be better to have a dialogue, at least initially. Should I
If you are asking whether the virtualization abstraction layer in Nova
can be split out into a library, I think the answer would be with
some effort. I'm sure there are a few dependencies on other Nova code
not in /nova/virt/, but you can try to identify those pieces and then
try to remove that
+1
On Tue, May 31, 2011 at 4:00 PM, Todd Willey t...@ansolabs.com wrote:
+1
On Tue, May 31, 2011 at 3:16 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
While I was checking branch merges, I noticed that Brian Lamar (blamar), is
not listed as a nova-core developer. This is most
On Thu, Jun 2, 2011 at 1:54 PM, Rick Clark r...@openstack.org wrote:
Hi All,
Is it required for new openstack API's to support both JSON and XML, or
would it be acceptable to only support JSON?
Glance currently does not support XML and I have no plans in the
immediate future to add support for
, 2011, at 2:00 PM, Jay Pipes wrote:
On Thu, Jun 2, 2011 at 1:54 PM, Rick Clark r...@openstack.org wrote:
Hi All,
Is it required for new openstack API's to support both JSON and
XML, or would it be acceptable to only support JSON?
Glance currently does not support XML and I have no plans
On Fri, Jun 3, 2011 at 9:23 AM, James Weir james.w...@usharesoft.com wrote:
At the very minimum until/if OpenStack supports XML, when I client wishes to
receive media type application/xml OpenStack should return a:
HTTP: 415 response
The server is refusing to service the request because the
and we keep them as short as practical.
Thanks much!
Thorsten - CTO RightScale
On 6/2/2011 12:40 PM, Jay Pipes wrote:
On Thu, Jun 2, 2011 at 1:18 PM, George Reese george.re...@enstratus.com
wrote:
I hate UUIDs with a passion.
* They are text fields, which means slower database indexes
On Mon, Jun 6, 2011 at 3:15 PM, mohan.rajes...@gmail.com wrote:
Thanks Rafael and Jay.
By following the openstack installation manual, nova-direct-api is not
installed. To install it, should I just download openstack package and copy
the nova-direct-api and stack to the /usr/bin/ directory?
On Fri, Jun 17, 2011 at 8:03 PM, Thorsten von Eicken t...@rightscale.com
wrote:
We're very much looking forward to the new portable configuration
drive functionality and would like to provide feedback. If this is not
the best forum, please point me to it.
The blueprint
is:
Hi!
As I stated on our Skype chat about this the other day, I think that
the default port for HTTP services should be 80, with 8080 used for
administrative endpoints. Unless there's a good reason to have a
specific port assigned to what is essentially just an HTTP service, I
don't think we should
On Fri, Jun 24, 2011 at 10:10 AM, Todd Willey t...@ansolabs.com wrote:
I'd prefer to keep it convenient to develop and demo on a single
machine. I don't think there is any added inconvenience during
deployment if the ports are not the standard http ports.
Can you explain why having the
On Sun, Jun 26, 2011 at 3:15 AM, Soren Hansen so...@linux2go.dk wrote:
2011/6/25 Jay Pipes jaypi...@gmail.com:
Can you explain why having the *default* port be 80/8080 for HTTP
services would hinder that? Unless I'm mistaken, spinning up servers
on different ports is as simple as specifying
see HTTP as something we just happen to
have chosen. We should prefer convention over configuration, and embrace
the conventions of HTTP.
On 6/26/11 11:13 AM, Jay Pipes jaypi...@gmail.com wrote:
On Sun, Jun 26, 2011 at 3:15 AM, Soren Hansen so...@linux2go.dk wrote:
2011/6/25 Jay Pipes jaypi
Ping. I think Kei's suggestion below is a good one... can someone
knowledgeable with qemu respond?
-jay
On Tue, Jun 21, 2011 at 9:55 PM, masumo...@nttdata.co.jp wrote:
Hello,
I have a question about nova.virt.libvirt.connection.snapshot().
In my understandings, this method is currently used
Hey all,
Recently, Nova added support for multiple zones in the OpenStack API.
Using the nova-manage tool, you can get a list of instances in a
single zone or in multiple zones using the --recurse option. When just
querying a local zone's API server, the listed instance identifiers
will be
On Fri, Jul 8, 2011 at 9:54 AM, Soren Hansen so...@linux2go.dk wrote:
2011/7/8 Ed Leafe ed.le...@rackspace.com:
No, it would work more like: a new instance is requested, and the
host selected. A candidate UUID would be generated and checked for first 8
uniqueness (I had already added
On Wed, Jul 13, 2011 at 12:30 PM, Bryan Taylor btay...@rackspace.com wrote:
How is this different in effect than letting swift or nova be tenants? Each
tenant gets to define users, roles, and groups, right?
A service can have multiple tenants. For instance, an installation of
Nova might have a
Hey Thomas,
File a bug on this: https://bugs.launchpad.net/nova/+bug/810051
Cheers!
jay
On Mon, Jul 11, 2011 at 10:43 PM, Thomas Goirand tho...@goirand.fr wrote:
Hi,
Seems debian/copyright isn't correct and needs some refinement.
I don't think that openwrt-x86-ext2.image and
Hi Liem! Comments inline...
From: Nguyen, Liem Manh [mailto:liem_m_ngu...@hp.com]
Sent: Friday, July 15, 2011 05:56 PM
For Nova, the Keystone Tenant maps to a Nova project, and according to the
“Finalize Auth integration” blueprint, the Nova project is going away (“no
more project/roleuser
Both ideas seem good and reasonable to me. :)
-jay
On Mon, Jul 18, 2011 at 7:05 PM, Chuck Thier cth...@gmail.com wrote:
There are two concepts that I would like Nova Volumes to support:
1. Allow different storage classes within a storage driver. For
example, in our case we will have some
FYI, the command signature was missing a network name after create...
-jay
2011/7/20 Shehjar Tikoo shehj...@gluster.com:
Thanks. It still runs into the Index out of range error. Are there any
configurables we could look at to debug further?
-Shehjar
Diego Parrilla Santamaría wrote:
it
Hi Nova-core, all,
Rohit has asked for a review on his merge proposal. Please feel free
to oblige him.
https://code.launchpad.net/~tpatil/nova/add-options-network-create-os-apis/+merge/68292
Thanks,
jay
___
Mailing list:
=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+rohit.karajgi=vertex.co...@lists.launchpad.net] On
Behalf Of Jay Pipes
Sent: Wednesday, July 20, 2011 8:39 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Request for review on merge proposal
Hi Nova-core, all,
Rohit has
All,
Rick Harris has produced some excellent code that adds functionality
for a local filesystem cache on Glance API nodes. I'd really like to
get this functionality into the D3 milestone release scheduled for
later this week. We need to cut the milestone release branch tomorrow,
and that means
Here's the start of a skeleton project:
https://github.com/openstack/openstack-skeleton
Fork away. We can use the pull requests for discussion about what's
best practice, what isn't, etc...
-jay
On Tue, Jul 26, 2011 at 8:26 AM, Thierry Carrez thie...@openstack.org wrote:
Brian Lamar wrote:
I
Hi Glance contributors,
The time has come for us to move to the new code platform, using Git and Gerrit.
I'd like to know what date you think is a good time for us to begin
the transition?
Everyone should read the documentation Monty and Jim have been putting together:
On Mon, Aug 1, 2011 at 9:05 PM, Jan Drake jan_dr...@hotmail.com wrote:
Anyone got good recipe for swift/glance on centos?
Are you asking about RPM packaging or Chef recipes?
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to :
On Mon, Aug 8, 2011 at 11:02 AM, Thomas Goirand tho...@goirand.fr wrote:
- Original message -
Hi Thomas,
I don't think it's because nobody cares. You may have just posted to
the mailing list on release day :)
I didn't realize it, sorry!
It seems I'm the specialist to ask for stuff
can
use as a starting point for discussion on what improvements can be
made relative to the GitHub process? I couldn't find any reviews
that you've done in Gerrit.
Thanks,
jay
Dan
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Sent: Monday, August 8, 2011 2:50pm
To: openstack
-
From: Monty Taylor mord...@inaugust.com
Sent: Tuesday, August 9, 2011 2:29pm
To: Jay Pipes jaypi...@gmail.com
Cc: Dan Prince dan.pri...@rackspace.com, openstack@lists.launchpad.net
Subject: Re: [Openstack] Status of Git/Gerrit Code Hosting/Review
Lastly I kind of feel like we've bee dupped. When
Hello all!
I'd like everyone to welcome Stefano Maffulli to the OpenStack
project! Stefano is OpenStack's new community manager and will be
leading efforts to grow and strengthen OpenStack's user and developer
community. Stefano brings with him a wealth of community-building
experience from
Hi Vish! Comments inline...
On Mon, Aug 22, 2011 at 6:43 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
Hey Everyone,
We discussed at the Diablo design summit having API spec changes be proposed
along with code changes and reviewed according to the merge process that we
use for code.
++
On Mon, Aug 22, 2011 at 7:59 PM, Jorge Williams
jorge.willi...@rackspace.com wrote:
Hi Vish,
I don't have a problem moving the spec out of docs manuals and into another
project even the nova repo. But, I do have a number of issues with the
approach that you're proposing. First, I think
No problems with anything you say below...
-jay
On Mon, Aug 22, 2011 at 9:59 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
Inline
On Aug 22, 2011, at 4:15 PM, Jay Pipes wrote:
It may be just me, but having DocBookXML in the source tree is hideous
to me. Not only does it clutter
++
On Tue, Aug 23, 2011 at 10:06 AM, Brian Lamar brian.la...@rackspace.com wrote:
I see this happening more and more when deadlines are coming up:
There is a merge proposal which has 2+ Core Approvals and 1+ Core Needs
Fixings and the branch is marked as 'Approved'. This is fine, in my
On Tue, Aug 30, 2011 at 4:34 AM, kiran.mur...@csscorp.com wrote:
Hello List,
Hello! :)
I have been testing OpenStack for a while and would be interested in any
automated test suites that are available.
There are a number of them...
On searching what I could find was Soren's presentation
I actually didn't plan on responding all that much on this
conversation. We had months of discussion and debate about this, weeks
upon weeks of discussion in the PPB about project autonomy and
tooling, and the decision has been made.
I find it a bit unfortunate that all the people saying Gerrit
On Sun, Sep 4, 2011 at 12:39 PM, Chuck Thier cth...@gmail.com wrote:
Taking a bit of a step back, it seems to me that the biggest thing
that prevents us from using a pure github workflow is the absolute
requirement of a gated trunk.
I think the big step backwards would be not having a gated
On Tue, Sep 6, 2011 at 2:02 PM, Anne Gentle a...@openstack.org wrote:
Hi all -
I wanted to discuss some changes to the API documentation for each project
prior to implementation to make sure I'm not missing any crucial detail and
to ensure you all feel you have ownership of the solution and
I'd be fine with that, too, Anne.
Cheers!
jay
On Wed, Sep 7, 2011 at 7:57 AM, Anne Gentle a...@openstack.org wrote:
Hello again -
In yesterday's team meeting, Brian Lamar brought up a good point - why name
the API projects after the project name, why not the product name? This
makes a lot of
On Wed, Sep 7, 2011 at 11:18 AM, Sandy Walsh sandy.wa...@rackspace.com wrote:
Yup, if you look at
http://www.darksecretsoftware.com/static/hubcap.html
you'll see there's a slot there for core non-core approvals. We get the
core approvers from the repos teams.
And where are the comments in
On Wed, Sep 7, 2011 at 11:42 AM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
On Wed, 2011-09-07 at 11:24 -0400, Jay Pipes wrote:
In addition, this doesn't prevent anyone on the core team from doing a
straight close and merge of the pull request into trunk, potentially
breaking trunk
On Wed, Sep 7, 2011 at 11:34 AM, Sandy Walsh sandy.wa...@rackspace.com wrote:
But yes, there is a risk that a core member could just hit merge and close
and break trunk. That's perhaps the only real con I can think of.
That's the entire point of gerrit and a gated trunk, Sandy :)
-jay
On Wed, Sep 7, 2011 at 12:13 PM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
On Wed, 2011-09-07 at 11:59 -0400, Jay Pipes wrote:
So far as I know, there's no requirement that someone have merge
authority on a project in order to comment on pull requests. Do cores
have direct
On Wed, Sep 7, 2011 at 12:38 PM, Monsyne Dragon mdra...@rackspace.com wrote:
This is basically what gerrit and our current LP setup do. it's just a
matter of permissions.
Couldn't have said it better myself! Thanks, Monsyne!
-jay
___
Mailing list:
On Wed, Sep 7, 2011 at 12:24 PM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Wed, Sep 07, 2011, Jay Pipes jaypi...@gmail.com wrote:
On Wed, Sep 7, 2011 at 11:34 AM, Sandy Walsh sandy.wa...@rackspace.com
wrote:
But yes, there is a risk that a core member could just hit merge and
close
On Wed, Sep 7, 2011 at 1:03 PM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Wed, Sep 07, 2011, Jay Pipes jaypi...@gmail.com wrote:
On Wed, Sep 7, 2011 at 12:24 PM, Johannes Erdfelt johan...@erdfelt.com
wrote:
Why do core members have that merge and close option? Wouldn't it make
more
101 - 200 of 662 matches
Mail list logo
