On May 28, 2013, at 8:38 PM, Markus Barth wrote:
> Hello everyone,
>
> Nova-cells filter has been merged now, so I'd like to make use of them
> and set up an installation for a proof of concept.
>
> My goal is to create new filters and then spawn instances in a demo.
Awesome. I'd be happy to
I'm having a hard time understanding the original problem. nova boot should
return in milliseconds. There's no blocking on provisioning.
- Chris
On Apr 3, 2013, at 8:32 PM, Rafael Rosa wrote:
> API wise I was thinking about something like "nova boot
> --custom-instance-uuid ABC..." or somet
Hi all,
I'd like to announce my candidacy for a seat on the OpenStack
Technical Committee.
- General background -
I have over 15 years of experience designing and building distributed
systems. I am currently a Senior Software Developer at Rackspace,
where I have been for a 2 and a half years n
On Feb 25, 2013, at 9:40 PM, Sam Morrison wrote:
>
> On 26/02/2013, at 4:31 PM, Chris Behrens wrote:
>
>> After thinking more, it does seem like we're doing something wrong if the
>> query itself is returning 300k rows. :) I can take a better look at it in
>> f
After thinking more, it does seem like we're doing something wrong if the query
itself is returning 300k rows. :) I can take a better look at it in front of
the computer later if no one beats me to it.
On Feb 25, 2013, at 9:28 PM, Chris Behrens wrote:
> Replying from my phone, so
Replying from my phone, so I can't look, but I wonder if we have an index
missing.
On Feb 25, 2013, at 8:54 PM, Sam Morrison wrote:
> On Tue, Feb 26, 2013 at 3:15 PM, Sam Morrison wrote:
>>
>> On 26/02/2013, at 2:15 PM, Chris Behrens wrote:
>>
>>>
&
On Feb 25, 2013, at 6:39 PM, Joe Gordon wrote:
>
> It looks like the scheduler issues are related to the rabbitmq issues.
> "host 'qh2-rcc77' ... is disabled or has not been heard from in a while"
>
> What does 'nova host-list' say? the clocks must all be synced up?
Good things to check.
Well, you probably don't want world writeable, but :) 755 on dirs and 644
on files is probably more appropriate! But at least you know the issue.
- Chris
On Feb 20, 2013, at 9:21 PM, harryxiyou wrote:
> On Thu, Feb 21, 2013 at 12:14 PM, Chris Behrens wrote:
>> [Remove
[Removed the dev list -- no need to cross-post.]
It looks like you have broken permissions on
'/usr/local/lib/python2.7/dist-packages/httplib2-0.7.7-py2.7.egg' and/or
subdirectories. Make sure everything is world readable.
- Chris
On Feb 20, 2013, at 7:48 PM, harryxiyou wrote:
> On Wed, Fe
+1
On Jan 22, 2013, at 5:38 PM, Matt Dietz wrote:
> All,
>
>I think Trey Morris has been doing really well on reviews again, so I'd
> like to propose him to be reinstated for Nova core. Thoughts?
>
> -Dietz
>
>
>
> ___
> Mailing list: https://
the cell when booting
> an instance.
>
> Cheers,
> Sam
>
>
> On 02/10/2012, at 1:06 PM, Chris Behrens wrote:
>
>> Yup, it's done. I just have to deal with some conflicts with our internal
>> branch and my public one..
>>
>>
>> On O
/ Cinder as well or? I guess this will be affected
> by the same thing?
>
> Endre.
>
> 2012/10/3 Chris Behrens
> The simplest explanation is that Cells gives you a way to tie multiple nova
> deployments together under a single API. Each cell has its own DB and
> Rab
On Oct 2, 2012, at 11:09 PM, Endre Karlson wrote:
> What is a cell contra Aggregate or Zone?
>
> Den 3. okt. 2012 07:46 skrev "Chris Behrens" følgende:
> Yup… looking forward to seeing those contributions! I'm working on getting
> the branch updated right now.
I'd like to contribute.
>
> Also we are looking at the ability for you to specify the cell when booting
> an instance.
>
> Cheers,
> Sam
>
>
> On 02/10/2012, at 1:06 PM, Chris Behrens wrote:
>
>> Yup, it's done. I just have to deal with some
Yup, it's done. I just have to deal with some conflicts with our internal
branch and my public one..
On Oct 1, 2012, at 7:47 PM, Sam Morrison wrote:
> On 02/10/2012, at 12:33 PM, Chris Behrens wrote:
>
>> Thanks, Tom! I have changes to push up that add rpc versioning,
Thanks, Tom! I have changes to push up that add rpc versioning, etc. Maybe I
can get those up tomorrow.
On Oct 1, 2012, at 7:08 PM, Tom Fifield wrote:
> Hi all,
>
> As Chris is a rather busy guy, I've taken the liberty of putting up a
> blueprint and wiki page for Nova Compute Cells.
>
> h
Hi all,
I'd like to announce my candidacy for a seat on the OpenStack
Technical Committee.
- General background -
I have over 15 years of experience designing and building distributed
systems. I am currently a Senior Software Developer at Rackspace,
where I have been for a little over 2 years n
I agree it's disappointing that it's not in trunk yet… and it needs to get in
there ASAP. I'm definitely happy to hear that others have been doing a bit of
hacking on it, wrt security groups and so forth!
I just got back from 2 weeks of vacation and I need to get my branch rebased.
There's a
.openstack.org
- Chris
On Aug 1, 2012, at 9:03 PM, Chris Behrens wrote:
> Ah, hit send early from my phone. There's a few additions I have in a
> private branch along with it being up2date with trunk. Will get that into
> the public branch and get the update out tomorrow!
Ah, hit send early from my phone. There's a few additions I have in a private
branch along with it being up2date with trunk. Will get that into the public
branch and get the update out tomorrow!
On Aug 1, 2012, at 9:01 PM, Chris Behrens wrote:
> I'll push up the latest tomo
I'll push up the latest tomorrow, promise! And I'll give an update at that
time. Sorry, been crazy times lately preparing for Rackspace's release today.
We are live with cells, and I'm extremely anxious to start getting it into
trunk. There's been a few additions not in the branch on github."
You may still have to reset the instance's task_state to NULL in the DB
(instances table) to delete ones already in this state.
- Chris
On Jul 30, 2012, at 1:48 PM, Kevin L. Mitchell wrote:
> On Mon, 2012-07-30 at 13:03 -0400, Jonathan Proulx wrote:
>> I have an instance that has been in this
Capacity based scheduling currently adds up all instance usage in
host_manager.py
There's another review marked as WIP that will be ready when retries go in that
cleans that and the capacity tracking up. Look for it from Brian Elliott.
On Jul 13, 2012, at 6:38 AM, "Day, Phil" wrote:
> Hi Fol
Sorry about this. I've had other priorities at Rackspace lately, but I have a
functioning implementation that I can hope to start to merge ASAP.
I'm on vacation for a couple days, so I can provide a better update on Monday.
On Jul 12, 2012, at 4:29 PM, Jaesuk Ahn wrote:
> +1 here.
>
> I am
Partially developed. This probably isn't much use, but I'll throw it out
there: http://comstud.com/cells.pdf
ATM the messy code speaks for itself here:
https://github.com/comstud/nova/tree/cells_service
The basic architecture is:
Top level cell with API service has DB, rabbit, and the nova-ce
Hi Jon,
There's actually a review up right now proposing to add an OS API extension to
be able to give some of this data:
https://review.openstack.org/#/c/9544/
I don't know how you may be looking to query it, but it's not too difficult to
get it directly from the instances table in the databa
That's correct. If there's an .ovf, it's currently ignored. It's also not
generated when we upload images (snapshots). I'm sure there's plans in
someone's head to implement that support at some point.. but right now we
expect the .vhds to have specific names in the tar file.
- Chris
On Ju
> "Networking" to "Block Device Mapping". I was kind of expecting that to
> be more part of the "compute.exists" messages than the update.
>
> Do we have something that catalogues the various notification messages and
> their payloads ?
>
>
On Jul 1, 2012, at 3:04 PM, "Day, Phil" wrote:
> Rather than adding debug statements could we please add additional
> notification events (for example a notification event whenever task_state
> changes)
>
This has been in trunk for a month or maybe a little longer.
FYI
- Chris
___
There's only 1 rpc call unless you're running cactus or something. All
schedulers have a loop...not API.
min-count is unfortunately special cased right now to be a single call vs cast,
though. I was going to fix that real soon. Problem is scheduler creating the
DB records vs API in this case
It had some problems… now it just seems backed up… trying to catch up.
On Jun 27, 2012, at 12:04 PM, Gary Kotton wrote:
> Hi,
> Is anyone aware of a problem with Jenkins?
> Thanks
> Gary
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post
doesn't hit them
before they've forked again.
http://paste.openstack.org/show/18338/
Only recourse may be to reboot my VM.
On Jun 4, 2012, at 4:57 PM, Chris Behrens wrote:
> The only thing I notice is about a 50% increase in the unit test run time
> very recently… I don't k
Ok, I take that back. I do see one issue. It looks like each test run is
leaving 2 stuck runner.py's for me… even if the tests complete successfully.
On Jun 4, 2012, at 4:57 PM, Chris Behrens wrote:
> The only thing I notice is about a 50% increase in the unit test run time
> ve
The only thing I notice is about a 50% increase in the unit test run time very
recently… I don't know when that started.. maybe today. Not seeing the 100s
of python processes. Hm!
- Chris
On Jun 4, 2012, at 4:00 PM, Kevin L. Mitchell wrote:
> Today I've noticed some significant problems wi
Doug,
That's the behavior I'd like to see and think it makes the most sense. It's
really a requirement if we want a great cells implementation. instance_types
table should only be used at the top level API cell. The data contained in
the table is passed in the messaging and stored with the
Or better unit tests in nova would help. :)
Fix just got approved, so it'll be going in shortly.
- Chris
On May 17, 2012, at 10:24 AM, Dan Wendlandt wrote:
> Hi Gary,
>
> Thanks for reporting this.
>
> After some digging, the bug seems to have been introduced by an error in a
> blanket ch
That's the traceback from novaclient. If you're getting a 503, there's likely
a traceback in the nova-api service logs.
- Chris
On May 9, 2012, at 5:38 PM, James R Penick wrote:
> Sorry, forgot to include that:
>
> bash-4.1$ nova —debug image-list
> connect: (127.0.0.1, 5000)
> send: 'POST /
On Apr 3, 2012, at 8:00 AM, Russell Bryant wrote:
[…]
>
> 3) nova.local
>
> This looks like a good candidate for moving to openstack-common and
> switching all usage of nova.local to be openstack.common.local.
>
Yeah, this one might be kind of weird, because it's used to set the 'nova
context
+1 from me
On Apr 27, 2012, at 8:09 AM, Dan Prince wrote:
> Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the
> Nova security team. He has been helping chipping away at reviews and
> contributing to discussions for some time now.
>
> I'd like to seem him Nova core s
+1 and good on the time here
On Apr 23, 2012, at 10:21 AM, John Garbutt wrote:
> Hi,
>
> Are people keen for a XenAPI virt layer meetup on IRC every month?
>
> I have added a suggested time to the wiki, as a starting point:
> Monthly, second Wednesday at 17:00 UTC
>
> Does that seem a reas
I'm noticing that core reviewers aren't tagged as a +2 anymore in the general
review box. Instead, it just shows a check. (Except for my own reviews, which
show as a +2). I have to look at the review comments to see if others voted
+2 now.
- Chris
On Apr 12, 2012, at 4:23 PM, James E. Blai
Awesome, thanks :)
On Apr 2, 2012, at 3:46 PM, Russell Bryant wrote:
> I just threw up a patch a little while ago:
>
> https://review.openstack.org/6119
>
> --
> Russell Bryant
>
> On 04/02/2012 06:37 PM, Chris Behrens wrote:
>> Seems like a sensible plan. C
Seems like a sensible plan. Carrot can go now. I marked it deprecated so we
can remove in folsom. I can take care of this today, even.
On Apr 2, 2012, at 3:02 PM, Duncan McGreggor wrote:
> +1
>
> Thanks for exploring this, Russell!
>
> Next step: getting a common REST API abstraction in pl
I have some plans for being able to set arbitrary "capabilities" for hosts via
nova.conf that you can use to build scheduler filters.
Right now, there are capabilities, but I believe we're only creating these from
hypervisor stats. You can filter on those today. What I'm planning on adding
is
My issue with using the URL is someone could easily DoS any tenant. Maybe you
said that below. I only have a brief moment to scan email ATM. :)
On Mar 29, 2012, at 5:26 PM, "Kevin L. Mitchell"
wrote:
> On Thu, 2012-03-29 at 22:58 +0100, Day, Phil wrote:
>> - As you get the tenant id from the
+1
I'd like to see a way for plugins to be able to modify the DB schema. There's
no easy way for a plugin to be able to add a column to a core nova table, for
instance.
In any case, I'm +1 on removing the vsa code for Essex.
On Mar 15, 2012, at 10:08 AM, Ghe Rivero wrote:
> I think is time
pip install xenapi
- Chris
On Mar 15, 2012, at 10:00 AM, Eduardo Nunes wrote:
> got this error on log, 2012-03-15 16:52:33,809 ERROR nova.compute.manager
> [-] Unable to load the virtualization driver: No module named XenAPI
> my nova-compute version diablo 2011.3
> __
I wonder if the issue is gone as well.
After the db_pool code was removed, I was doing some separate testing of
sqlalchemy's with_lockmode().. and I was able to reproduce a traceback from
sqlalchemy that looked extremely similar or identical to the traceback we were
hitting when using eventle
Right.
We want the API to return as quickly as possible. It should not block. I'd
argue that live migration should not block the API as well. Any errors should
be reported via the instance faults table,
but it's definitely less important than builds.
Nicolae: Note that the scheduler also do
On Mar 4, 2012, at 8:56 PM, Gabe Westmaas
> I agree with this paragraph whole heartedly! I would definitely like to see
> this separation not only for the reasons you list above (performance, all
> installations behaving the same way) but also because I think it gives us a
> lot more power
Pretty much +1 to all of that. The other problem I see that a separate 'view'
for the API solves...is state tracking. I feel API should be keeping its own
state on things. What the API allows per the spec should be completely
separated from the services state tracking. As you mention, comput
It's not just you
On Mar 2, 2012, at 10:35 AM, Joshua Harlow wrote:
> Does anyone else feel that the following seems really “dirty”, or is it just
> me.
>
> “adding a few sleep(0) calls in various places in the
> Nova codebase (as was recently added in the _sync_power_states()
> periodic task)
On Mar 1, 2012, at 12:36 PM, Vishvananda Ishaya wrote:
> Yes it does. We actually tried to use a pool at diablo release and it was
> very broken. There was discussion about moving over to a pure-python mysql
> library, but it hasn't been tried yet.
>
I know some people have tried this... and
On Mar 1, 2012, at 12:27 PM, Adam Young wrote:
> On 03/01/2012 02:45 PM, Yun Mao wrote:
>> There are plenty eventlet discussion recently but I'll stick my
>> question to this thread, although it's pretty much a separate
>> question. :)
>>
>> How is MySQL access handled in eventlet? Presumably it
ouldn't need DHCP, right?
There should be iptables rules to allow you to talk to the metadata service
over 169.254.* (And linux should give you a default link-local address that
allows you to talk to the MD service magically)
Do you have a non-nova DHCP server running as well?
- Ch
I'd assume FlatDHCPManager works much like FlatManager, but maybe I'm wrong. I
use FlatManager and I always end up having to modify the fixed_ips table
manually after running nova-manage because I think I'm trying to do something
similar as you. I have a /23... and I want to give nova a /25 ou
On Feb 18, 2012, at 11:36 AM, Ed Leafe wrote:
> I still prefer 'cell'. The parallel to single celled / multi-cellular
> life forms makes sense, and there is really no overloading of the word in the
> world of computers.
I like 'cell' too. It makes sense.
But "'cell' reminds me too much
Of those, I'd probably prefer 'Knots'.
- Chris
>
> On Feb 18, 2012 1:57 PM, "Chris Behrens" wrote:
> Sector?
>
>
> On Feb 17, 2012, at 9:06 AM, Ed Leafe wrote:
>
> > On Feb 15, 2012, at 10:07 AM, Armando Migliaccio wrote:
> >
> >
Sector?
On Feb 17, 2012, at 9:06 AM, Ed Leafe wrote:
> On Feb 15, 2012, at 10:07 AM, Armando Migliaccio wrote:
>
>> I think you touched the crucial point here: what is exposed to the user and
>> what not. Reading:
>>
>> http://wiki.openstack.org/MultiClusterZones#Design
>>
>> one would think
h set, at the risk
> of not catching a possible conflict when you upload.
>
> Vish
>
> On Feb 16, 2012, at 5:22 PM, Chris Behrens wrote:
>
>> Hm. It shouldn't have uploaded a new patch set for 3990 if you did not
>> modify the commit in 3990.
>>
>>
Hm. It shouldn't have uploaded a new patch set for 3990 if you did not modify
the commit in 3990.
However, it does appear that you modified 3990's commit. This method was added:
test_get_rrd_server()
in nova/tests/test_xenapi.py
You can see it here:
https://review.openstack.org/#patch,unifi
On Feb 14, 2012, at 2:31 PM, Chris Behrens wrote:
[...]
> With that, we have 2 branches up for review to remove the current zones code:
>
> novaclient:
> https://review.openstack.org/4163
>
> nova:
> https://review.openstack.org/4062
Oops... should have been: https:/
As per today's meeting (which I think Vish will send a separate update about),
we've decided to remove the current zones implementation for the Essex release.
I'll be maintaining a branch that has a new implementation until F opens up.
With that, we have 2 branches up for review to remove the
Shards'. :) Not sure I
dig that name completely, although it makes sense. Thoughts?
- Chris
On Feb 9, 2012, at 10:29 AM, Leandro Reox wrote:
> Awesome Chris !!!
>
> Lean
>
> On Thu, Feb 9, 2012 at 3:26 PM, Alejandro Comisario
> wrote:
> Niceee !!
>
> A
+1
On Feb 9, 2012, at 9:11 AM, Matt Dietz wrote:
> Any more hits on this? I fear that this was lost in the torrent of email, and
> I really do think Dragon deserves to be a core developer for all the hard
> work he's been doing.
>
> From: Paul Voccio
> Date: Tue, 7 Feb 2012 12:38:15 -0600
> T
I should be pushing something up by end of day... Even if it's not granted an
FFE, I'll have a need to keep my branch updated and working, so I should at
least always have a branch pushed up to a github account somewhere until F1
opens up. So, I guess worst case... there'll be a branch somewh
gt;>> now ).
>>>> So, if there is a new zone architecture that actually works ( we want to
>>>> stop using our own deployer to do that ) or has a chance to be fully
>>>> working when 2012-1 is out, (we would prefer not to wait till Folsom) we
>>>&
I wonder if we can use some of the architecture of the new code and move the
current implementation to that model. It'd preserve the existing
functionality, set us up for the new implementation, and fits in with 'cleanup'
for E4, etc.
On Feb 1, 2012, at 2:41 PM, Vishvananda Ishaya wrote:
>
ke to minimize the
impact in case it is unstable or people simply want the current behavior.
(I posted the same comments on the review)
- Chris
On Jan 31, 2012, at 11:02 AM, Vishvananda Ishaya wrote:
> I'm ok with this going in, but I would like to leave it up to the guys who
> are u
Vish: Looks like it's only in ec2 api.
Tomoe: The support will need to be added in an extension, since it's not in the
current API spec. Ie, it'll need to go under
nova/api/openstack/compute/contrib in the tree, not directly in
compute/servers.py.
- Chris
On Jan 17, 2012, at 9:21 PM, Vishva
On Jan 12, 2012, at 12:00 PM, Yang, Fred wrote:
> Vish,
>
> Mark and I have worked a while and yet to have a get a better approach. Let
> me describe key features need to be addressed and a possible approach for
> base discussion
>
> Nova scheduler's select_and_run can dispatch N instances d
On Dec 28, 2011, at 5:36 AM, Ask Solem wrote:
[...]
>
> amqplib does not support heartbeats so there may be cases
> where the client/server does not properly detect that the socket
> has been closed, this usually only a problem with some particular intermediate
I received a private reply from Ro
Hi Roman,
Are you using diablo or trunk (both of which use kombu by default and should
support reconnecting)?
If so, can you 'egrep' for the following strings in logs and provide the
output? You can reply to me directly so we're not spamming this list.
"Unable to connect to AMQP server"
"Conn
Hm. I've just been going off of this doc string in db/api.py:
"Functions in this module are imported into the nova.db namespace. Call these
functions from nova.db namespace, not the nova.db.api namespace.
All functions in this module return objects that implement a dictionary-like
interface. Cur
her cleanup code we added along the way.
>
>
>
> Feels like this approach would be a bit roundabout, but each step feels safe,
> and it seem like it would get us to where we want to be in the course of a
> few weeks (perhaps a couple of months, worst case).
>
> Thoughts?
&g
Yes, that was what I was saying. :)
On Dec 15, 2011, at 12:06 AM, Soren Hansen wrote:
> 2011/12/15 Jesse Andrews :
>> I agree except I though the preference was for
>>
>>> instance_uuid = instance['uuid']
>>
>> not
>>
>>> instance_uuid = instance.uuid
>>
>> (use dict's and don't assume sqlalc
I've seen a number of patches lately that have code like this:
instance = db.instance_get(...)
instance_uuid = instance.uuid
instead of:
instance_uuid = instance['uuid']
There's a mix of usage throughout the code, and I know some people are just
matching the surrounding code. But, in a numbe
to get in first. So,
I'm currently splitting these out into a couple of different reviews.
- Chris
On Nov 30, 2011, at 1:53 PM, Duncan McGreggor wrote:
> On 30 Nov 2011 - 19:26, Chris Behrens wrote:
>> I need to catch up a bit with this thread, but I wanted to mention I
>>
I need to catch up a bit with this thread, but I wanted to mention I have a
huge patch coming that refactors almost all of the scheduler tests into true
unit tests. I'd started this for other reasons and I hope it jives with the
plans here. But if anyone is looking at the scheduler tests, we s
Yeah, been noticing this too and thinking about nominating him. +1 from me!
- Chris
On Nov 29, 2011, at 12:05 PM, Vishvananda Ishaya wrote:
> Mark is maintaining openstack for Fedora and has made some excellent
> contributions to nova. He has also been very prolific with reviews lately.
> L
+1 on the thoughts here. Exactly what I meant by my reply. Not sure what the
interface should look like for #2, but we must be able to do it somehow.
- Chris
On Nov 29, 2011, at 11:55 AM, Vishvananda Ishaya wrote:
> e) is the right solution imho. The only reason joinedloads slipped in is for
e) sounds good as long as we don't remove the ability to joinload up front.
Sometimes we need to join. Sometimes we can be lazy. With 'list instances
with details', we need to get all instances from the DB and join network
information in a single DB query. Doing 1 + (n*x) DB queries to suppo
+1 -- For a while now, I've been going to review things, finding Johannes's
name already in the review list quite often. I also agree with his reviews. :)
- Chris
On Nov 9, 2011, at 6:02 AM, Brian Waldon wrote:
> I'd like to nominate Johannes for nova-core, as he has definitely been doing
>
Yep... +1
On Nov 9, 2011, at 5:59 AM, Brian Waldon wrote:
> Vek has absolutely stepped up and started doing quite few reviews, so I'd
> like to nominate him to be added to nova-core.
>
> Waldon
>
>
> ___
> Mailing list: https://launchpad.net/~open
uest you
> mentioned anywhere in the api code.
>
> Correct me if I'm wrong, but - consoles.py talks to Consoles.API when i think
> to get the actual output of things we need to talk to Compute.API if we want
> to get the actual output of a console and not just info abou
+1
On Oct 21, 2011, at 10:37 AM, Jay Pipes wrote:
> ++
>
> I also believe the requirements to:
>
> a) Have a single-line <80 characters brief description AND a long description
> b) Start the description on the same line as the beginning """
>
> are silly.
>
> I think this:
>
> """
> This i
For OSAPI:
There's POST /version/project/servers//consoles to create a console
Use GET to get consoles for that server_id
Then you can use: GET
/version/project/servers//consoles/ to get the detailed
info.
I don't think there's support for this in nova-client.
(Look at nova/api/openstack/co
+3
On Oct 11, 2011, at 1:59 PM, Brian Waldon wrote:
> I would like to propose we remove our implementation of OSAPI v1.0 from Nova
> for the following reasons:
>
> 1) Our implementation is incomplete, and there are no (visible) plans to
> complete it. Shared IP Groups and Backup Schedules h
Not sure the 'data that are shared' is the right wording below, but I think I
get the point. The one thing that jumps out to me as a current 'issue' is the
fact that the instance_types table must be kept in sync. I can't think of
anything else at the moment, but there might be something.
And
There's currently no parsing of manifest.ovf in an .ova. nova assumes that an
'image.vhd' exists within the .ova archive if disk_format is vhd..
- Chris
On Sep 23, 2011, at 9:49 AM, Jay Pipes wrote:
> On Wed, Sep 21, 2011 at 4:02 PM, Joshua Harlow wrote:
>> It would be really cool if there
Thanks!
On Sep 22, 2011, at 8:59 AM, Soren Hansen wrote:
> I just added Chris to nova-core. Welcome to the team, Chris! I'll add
> you to the review rotation next time that schedule gets updated.
>
> --
> Soren Hansen| http://linux2go.dk/
> Ubuntu Developer| http://www.ubuntu.com/
>
+1 !
On Sep 12, 2011, at 2:10 PM, Sandy Walsh wrote:
>
>
> From: Jay Pipes [jaypi...@gmail.com]
>
>> Can we discuss pulling novaclient into Nova's source tree at the design
>> summit?
>
> +1
> This email may include confidential information. If you r
Sure, I agree with the below. I tend to think the PPB is the place for the
decision for the reasons you state below (though that's more than 3-4 people
tops). But whether it's the PPB or some other small group of people, I'd want
to see everybody have a chance to provide enough feedback for th
On Sep 7, 2011, at 11:46 AM, Jay Pipes wrote:
> On Wed, Sep 7, 2011 at 2:19 PM, Chris Behrens
> wrote:
>>
>> On Sep 7, 2011, at 9:21 AM, Jay Pipes wrote:
>>> The problem is that instead of spending time coding on features and
>>> bugs for Nova, Glance, Swi
On Sep 7, 2011, at 9:21 AM, Jay Pipes wrote:
> The problem is that instead of spending time coding on features and
> bugs for Nova, Glance, Swift and Keystone, a bunch of devs are instead
> spending time working on an alternate solution to what has already
> been decided by the PPB, discussed publ
Jay,
On Sep 4, 2011, at 10:52 AM, Jay Pipes wrote:
> 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.
>
>
ace.
>
>
>
> On Fri, Sep 2, 2011 at 11:34 AM, Chris Behrens
> wrote:
>
> On Sep 2, 2011, at 8:07 AM, Paul Voccio wrote:
>
> > On Fri, Sep 2, 2011 at 8:01 AM, Soren Hansen wrote:
> > [...]
> > The potential for filesystem bugs that could bring the h
On Sep 2, 2011, at 8:07 AM, Paul Voccio wrote:
> On Fri, Sep 2, 2011 at 8:01 AM, Soren Hansen wrote:
> [...]
> The potential for filesystem bugs that could bring the host down gives
> me the heebie jeebies. I really, really don't want to mount people's
> filesystems.
>
>
> Can you explain a bi
Vish,
I think Rackspace ozone/titan has some upcoming work to do for the resizing for
xenserver that might close some of the gap.
I think we need some options (flags) if we are to synchronize libvirt/xen. At
some point, Rackspace also needs an API extension to support a couple different
ways
This email wasn't sent sooner, because there was an assumption that since
glance already depended on kombu.. and that nova depends on glance... that
kombu is already a required dependency for nova. However, this must not be
completely true because we just got a merge failure because of kombu n
1 - 100 of 131 matches
Mail list logo
