Hi Sumit,
This is a great question to be asking, as it gets to the heart of how
Quantum will work with Nova (or any any other OpenStack service that plugs
into the network). As you suggest, our goal here is to try and come up with
a clean separation between the responsibilities of Nova and
the
Hello everyone,
Our weekly team meeting will take place at 21:00 UTC this Tuesday in
#openstack-meeting on IRC. PTLs, if you can't make it, please name a
substitute on [2].
By the time of the meeting we should have Swift 1.4.0 out, while Nova
and Glance should soon be branched for the diablo-1
Hello everyone,
At the end of this day (or rather, at the very beginning of tomorrow),
we should branch trunk for Nova and Glance in order to prepare the
diablo-1 milestone delivery.
That means the last diablo-1 feature branches should be reviewed and
merged sometime today, so please help in
The problem is that every version would be stored on the same drives, which
is
gonna screw with storage distribution.
Could you please clarify this?
I understand that drives are selected based on account/container/object path
and do not depend on the current storage distribution. So, if
The idea to make ring implementation pluggable seems nice.
At the same time I am thinking that many developers might not will feel
comfortable with modifying existing ring structure, since it *works*
:) Probably, the other viable option for allowing data location compliance is
to
implement
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
Hi all.
what is happen here??
root@ubuntu:~# euca-associate-address -i i-007 10.10.10.6
FloatingIpNotFound: Floating ip not found for fixed address 10.10.10.6.
thanks.
___
Mailing list: https://launchpad.net/~openstack
Post to :
I think, from an audit and security standpoint, whatever component is
responsible for the placement of data needs to be solely responsible, and
needs to fail in a clean and transactional way. If the ring is modified to
guarantee that the *first* copy of an object is written into a specific zone
Hi Sumit, responses inline. Thanks,
Dan
On Tue, May 31, 2011 at 9:12 AM, Sumit Naiksatam (snaiksat)
snaik...@cisco.com wrote:
Hi Dan,
Thanks for your prompt response on this.
As I understand from your explanation, the knowledge of the “edge binding”
resides with Nova, and in the
While I was checking branch merges, I noticed that Brian Lamar (blamar), is not
listed as a nova-core developer. This is most definitely a travesty, as he has
been one of the most prolific coders/reviewers over the past few months. So
I'm proposing that he is added as a nova-core member.
+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 definitely a travesty, as
he has been one of the most prolific coders/reviewers
2011/5/31 Vishvananda Ishaya vishvana...@gmail.com:
While I was checking branch merges, I noticed that Brian Lamar (blamar), is
not listed as a nova-core developer. This is most definitely a travesty, as
he has been one of the most prolific coders/reviewers over the past few
months. So
Both Dan and I are traveling today. So, unless someone really objects,
we would like to reschedule today's netstack meeting to the same time
tomorrow.
Cheers,
Rick Clark
___
Mailing list: https://launchpad.net/~openstack
Post to :
+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
+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 definitely a travesty,
as he has been one of the most prolific coders/reviewers
Hi Jorge,
Thanks.
From what you described, should we say that all the extensions belonging
to one service will be grouped together?
For example, quantum.foo.com/v1.0/extensions query will list all the
extensions under the quantum service.
Then what's the relationship between core and the
+1 from me
On 5/31/11 3:10 PM, Jay Pipes jaypi...@gmail.com wrote:
+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
Well, since the pluggable ring idea *was* about this as well (I'm pretty sure,
since I proposed it), maybe it's time to talk merkle trees ;)
I'll circle back with notmyname and see what makes sense for breaking up this
discussion into manageable chunks.
Joshua McKenty
Piston Cloud Computing,
+1, although I'm concerned about what happens when he calls git blame. Is the
blamar then the blamee, or blameless?
Sorry, just had to get it out of my system.
Joshua McKenty
Piston Cloud Computing, Inc.
(650) 283-6846
jos...@piston.cc
On 2011-05-31, at 1:34 PM, Josh Kearney wrote:
+1
Let's say you're backing up a Nova instance to Swift every day using
versioning, and each backup is 5gb. After a few weeks, that hard
drive may be storing over 100gb for one file. Swift has no way of
taking that into account when placing files, so the distribution is
going to get clumpy,
I'm not sure I will be able to make it for tomorrow as I will be travelling as
well.
If that is the case, please accept my apologies for the absence.
Salvatore
-Original Message-
From: openstack-bounces+salvatore.orlando=eu.citrix@lists.launchpad.net
On May 31, 2011, at 4:49 PM, Rostyslav Slipetskyy wrote:
I assume that in this scenario there is only one user/file of huge size and
all
the other users/files are much smaller (in other case, there will be not much
difference in distribution among drives). But the suggested
Thanks, Anne!
On 01/06/2011, at 1:09 AM, Anne Gentle wrote:
Hi Mark -
Thanks for going through and making comments, it's very helpful. I'll have
Jorge address the questions that apply to the architecture decisions, but I
can address these:
A few nits about the document itself,
I know I don't get a vote here, but Brian asked to subscribe to all the doc
comments that come through on docs.openstack.org, and I love that. :)
Anne
*Anne Gentle*
a...@openstack.org
my blog http://justwriteclick.com/ | my
bookhttp://xmlpress.net/publications/conversation-community/|
LinkedIn
+1
Brian is a rock solid python developer.
Dan
-Original Message-
From: Vishvananda Ishaya vishvana...@gmail.com
Sent: Tuesday, May 31, 2011 3:16pm
To: Openstack openstack@lists.launchpad.net
Subject: [Openstack] Proposal for Brian Lamar to join Nova-Core
While I was checking branch
25 matches
Mail list logo
