I suggested a couple alternative solutions for implementations in one of the
reviews. Hoping to hear back from fred yang/intel on whether one of those
solutions will work. Copied suggestions here in case anyone else is following
along.
Brian Waldon and I were discussing the possibility of a c
nova-manage does not talk to keystone, and exporting credentials will not work.
If you want to use keystone with nova, your best bet is to see how devstack
sets up users [1] and paste config [2] and credentials [3].
[1]
https://github.com/openstack-dev/devstack/blob/stable/diablo/files/keyston
Awesome!
+1
Do we have a non-gating one for trunk so that we can at least see red/green?
Vish
On Dec 8, 2011, at 2:12 PM, James E. Blair wrote:
> Hi,
>
> A lot of people would like to see us with more commit gating jobs that
> test functionality across the full range of core OpenStack project
list is efficient in terms of information per
> second, it's an inefficient place for coordinating. Solve this and I'm on
> board.
>
> On Thu, Dec 8, 2011 at 7:26 AM, Soren Hansen wrote:
> 2011/12/8 Thierry Carrez :
> > Soren Hansen wrote:
> >> 2011/12/7
Hello Everyone,
The Nova subteams have now been active for a month and a half. Some things are
going very well, and others could use a little improvement. To keep things
moving forward, I'd like to make the following changes:
1) Weekly meeting for team leads. This is a time for us to discuss
The purpose of the stable branch and the maint team that theirry mentioned
earlier is to vet patches. Are you suggesting that we need a point release
system for openstack outside of relying on distros to pick release points?
Vish
On Dec 6, 2011, at 1:21 PM, Tim Bell wrote:
>
> We need more t
Just read through the description and the code. I don't have any issues with
the way it is implemented, although others may have some suggestions/tweaks. I
think it is most important to get the common code established, so I'm up for
implementing you changes in Nova. I think it is important to
IIRC it was to ensure that the instance could be deleted from the db even if
the virt layer didn't know about it. It seems equally valid to raise an
exception and catch it in manager and continue the delete process.
Vish
On Dec 4, 2011, at 7:30 AM, Mark Washenberger wrote:
> Team,
>
> I was
On Nov 30, 2011, at 4:18 AM, Thierry Carrez wrote:
> Soren Hansen wrote:
>> I propose we start building packages from the stable branches and put
>> them in an appropriately named/labeled PPA, such as nova-core/diablo-qa
>> or nova-core/diablo-not-for-production (or perhaps under
>> openstack-sta
It was here:
http://area51.stackexchange.com/proposals/31788
It was rejected on the grounds of being able to be covered on StackOverflow and
ServerFault.
Vish
On Nov 29, 2011, at 10:10 AM, Lloyd Dewolf wrote:
> On Fri, Nov 18, 2011 at 10:38 AM, Anne Gentle
> wrote:> We had put forward an Ope
Inline
On Nov 29, 2011, at 11:16 AM, Soren Hansen wrote:
> 2011/11/29 Vishvananda Ishaya :
>> e) is the right solution imho. The only reason joinedloads slipped in is
>> for efficiency reasons.
>>
>> In an ideal world the solution would be:
>>
>> 1)
+1. This sounds like a bug. FYI there are some issues related to adding source
group rules that specify ports that need to be fixed. We have also discussed
whether or not the same group should be allow all by default. In ec2 it does.
I personally like having it explicit like this, but I don't
Mark is maintaining openstack for Fedora and has made some excellent
contributions to nova. He has also been very prolific with reviews lately.
Lets add him to core and make his reviews count towards potential merges!
Vish
___
Mailing list: https://la
Lorin has been a great contributor to Nova for a long time and has been
participating heavily in reviews over the past couple of months. I think he
would be a great addition to nova-core.
Vish
___
Mailing list: https://launchpad.net/~openstack
Post to
e) is the right solution imho. The only reason joinedloads slipped in is for
efficiency reasons.
In an ideal world the solution would be:
1) (explicitness) Every object or list of related objects is retrieved with an
explicit call:
instance = db.instance_get(id)
ifaces = db.interfaces_get_by
This is a bug. The dhcp least time flag is supposed to be used in place of the
120s. It must have been removed at some point.
Can you please file a bug on launchpad. If you are able to submit a review
request in gerrit as well, that would be fantastic.
Vish
On Nov 22, 2011, at 9:45 PM, ljvs
It most definitely is possible. It just hasn't been implemented.
https://blueprints.launchpad.net/nova/+spec/libvirt-resize
Vish
On Nov 21, 2011, at 6:48 AM, Razique Mahroua wrote:
> Hi Openstackers :)
>
> I've a question - I know the instance's resizing only works with XEN. Now my
> questi
Openstack Object Storage usually refers to the swift project.
Vish
On Nov 21, 2011, at 4:18 AM, David Busby wrote:
> Also, as I recall Object Store is deprecated in favour of glance, at least
> this was the case in October during the training course.
>
> Added cc to openstack@lists.launchpad.n
Hello Everyone,
We are modifying the way that we are targeting blueprints a little bit for
nova. We are now marking blueprints accepted for essex only when they have a
milestone target and an assignee. That will keep this page a bit cleaner:
https://blueprints.launchpad.net/nova/essex
You can
On Nov 15, 2011, at 2:17 PM, Ewan Mellor wrote:
>
>
> With the bug in the Swift backend fixed, I think it will work just fine
> to stream through a glance client in this way.
Only if the image is < 5 GB. Otherwise swift will blow up trying to store it.
Vish
>
> Cheers,
>
> Ewan.
>
>
As thierry mentioned, the releases are tagged. It is also worth mentioning
that each project has a branch for release + fixes. For the last release
the branch name is stable/diablo
On Nov 15, 2011 2:43 AM, "Julien Danjou" wrote:
> Hi,
>
> Would it be possible to use git tags to mark released vers
I think we need a straight copy of Nova 1.1 -> Nova 2.0 that simply renames
everything from 1.1 -> 2.0 and changes the endpoint url v1.1 -> v2
Also a big note saying that 2.0 is exactly the same as 1.1 but was renamed to
avoid confusion with 1.0 when we pulled out the minor version from the url.
On Nov 10, 2011, at 6:22 AM, Mark McLoughlin wrote:
> But wait! Vish +2ed a stable branch patch yesterday:
>
> https://review.openstack.org/328
I don't mind losing my powers over stable/diablo.
On a related note, is there a way we can change the color scheme in gerrit (to
red??) for stable
The main thing that the idea of host-aggregates provides is the ability to
specify metadata at a group of hosts level. If you put 10 hosts into a single
aggregate, you can specify characteristics for those hosts as a group (i.e.
which san they are backing files onto, whether they support live m
Hey Nova Core.
It is that time again. We've fallen behind on reviews. I know everyone is
extremely busy, but we can't make progress on merging patches if we don't have
people doing reviews. Here are the stats on the number of different change
sets each person in nova core has reviewed in the
This is a bug. It is residual from previous code where source groups didn't
allow specific protocols to be specified. I think there may be a bug already,
but if not, can you please file one? If you see where it is happening in the
code a patch would also be appreciated.
Vish
On Nov 7, 2011,
Passing this on to the main openstack list because I'm not sure that the boot
from volume athours and users are on this mailing list.
On Nov 3, 2011, at 1:35 PM, Renuka Apte wrote:
> Hello,
>
> What is the current state of “boot from volume”? Is there any documentation
> about how it works, de
The only code that is used from gflags ls ReadFlagsFromFiles which recursively
reads flags from files and converts them into args (removing comments). We
could rewrite or copy this code and remove the gflags dependency, but if we are
moving towards a config file instead of a flag file we will be
Sounds like we can work around this pretty easily by sorting the disks before
we pass them into the xml template.
Vish
On Nov 1, 2011, at 9:52 AM, Gaurav Gupta wrote:
> Hi all, I asked a question on Launchpad. but haven't heard back anything yet.
> Trying this forum to see if someone has any i
> scoped_sessions, and/or willing to help us understand the issues we’re seeing
> in the Unit Tests.
>
> And of course I’d like to know what the communities feeling is towards a
> simpler approach to fixing the issue in Diablo.Final vs the backport of DB
> simplification changes
All of the workers are single-threaded, so I'm not sure that scoped sessions
are really necessary.
We did however decide that objects from the db layer are supposed to be simple
dictionaries. We currently allow nested dictionaries to optimize joined
objects. Unfortunately we never switched to
This is correct Unfortunately, you won't be able to use euca-upload-bundle
properly. I am trying to figure out a way to allow euca-upload-bundle to work,
but for now it will only work with deprecated auth.
Devstack shows how you can create users, tenants, roles and credentials in
keystone tha
hem in the nova code per se.
Vish
On Oct 27, 2011, at 9:22 AM, Joseph Heck wrote:
> On Oct 27, 2011, at 9:19 AM, Vishvananda Ishaya wrote:
>> On Oct 25, 2011, at 12:05 PM, Joseph Heck wrote:
>>> Q: What's the keystone-manage command for "credential add" do? There
On Oct 25, 2011, at 12:05 PM, Joseph Heck wrote:
>
> Q: What's the keystone-manage command for "credential add" do? There's also
> no corresponding delete or disable - is this password update for the
> passwords that are set on "keystone-manage user add"? If not, how are those
> passwords upd
I haven't seen this happen. Sounds like it may be a libvirt bug.
On Oct 27, 2011, at 7:48 AM, mao weijie wrote:
> I have found nova-compute often stopped that no update info in log and
> service status is XXX. Then I restart nova-compute, but it is still stop in
> "DEBUG nova.virt.libvirt_conn
Hello Again,
I intended to post a link to the essex blueprints. Here it is:
https://blueprints.launchpad.net/nova/essex
Also, I've moved a number of blueprints into a sort of backlog. These are
blueprints that seem to be stalled out, or that are good ideas but don't have
anyone particular to
Hello Everyone,
I've (finally managed) to get all of the blueprints organized and assigned to
essex. I've assigned any that had no user assigned to them to the subteams.
From here on I will need help from the subteam leads to:
a) Assign blueprints to the individual(s) that will be implementin
Speaking of keystone diablo tag, it is currently missing the following commit:
https://github.com/openstack/keystone/commit/2bb474331d73e7c6d2a507cb097c50cfe65ad6b6
This commit is required for the ec2 api to work with keystone. Seems like we
need to move the tag or create a keystone/stable bran
try restarting libvirt-bin service?
Vish
On Oct 19, 2011, at 6:11 PM, DeadSun wrote:
> my server is 11,10 and nova is installed via apt-get
>
> after two days running, using nova-manage service list show
> nova-compute XXX state
>
> then I restart nova-compute service, but the log nova-compute
Lets get this going asap. We don't really have a place to point people who are
deploying diablo and running into bugs.
Jim, does diablo-stable, essex-stable work?
Vish
On Oct 17, 2011, at 4:10 AM, Mark McLoughlin wrote:
> Hi James,
>
> On Fri, 2011-10-14 at 12:43 -0400, James E. Blair wrote:
subscribe to each of the mailing lists, unless the openstack mailing list
> is cc'd in all the emails, at which point it becomes pointless to have the
> subteam mailing lists.
>
>
> Nirmal
>
> On Mon, Oct 17, 2011 at 9:35 AM, Jay Pipes wrote:
> On Mon, Oct 17, 2011
Hello Everyone,
I've been assimilating the plans from the design summit into blueprints. In
the process i've noticed that we have a lot planned for the next few months.
Some of these changes are quite large and involve people from many different
companies that are working on openstack. In or
Strange, I haven't seen this. It sounds like maybe you have a mac address
conflict somehow. The only time I've seen duplicate icmp responses is when I
was running inside of virtualbox and due to the way vagrant was setting up vms,
I had multiple vms with same mac.
Vish
On Oct 14, 2011, at 5:
I think the arguments for removing 1.0 are sound. Lets nuke it!
Vish
On Oct 12, 2011, at 7:39 AM, Gabe Westmaas wrote:
> On 10/12/11 9:22 AM, "Jay Pipes" wrote:
>
>> On Wed, Oct 12, 2011 at 8:13 AM, Gabe Westmaas
>> wrote:
>>> I definitely get why developers working on the code base are in
Hey Everyone,
We had a great design summit. Lots of new features were presented, along with
some great proposals for cleanup, stability, upgradability, etc. I'm
attempting to capture all of the proposed action items in one etherpad, with
links to specific blueprints. You can find the etherpa
For some reason tables are getting created as default type. There is a
migration in the history to convert tables to InnoDB, but anything created
after that migration will go in as the default type. We can add another
migration to convert all of the other tables, but I think the right method h
; --sql_connection=mysql://root:root@10.0.254.6/nova
> --network_manager=nova.network.manager.FlatManager
> --flat_network_bridge=xenbr0
> --libvirt_type=xen
> --xenapi_remap_vbd_dev=true
> --glance_api_servers=10.0.254.6:9292
> --image_service=nova.image.glance.GlanceImageServi
This is a bug that is a result of changing the behavior of source groups. For
a while we emulated the old style aws source group style that doesn't allow
specifying protocol and ports. This was changed recently and it looks like
this check was missed.
Vish
On Oct 6, 2011, at 6:20 AM, Aleksan
It looks like if you change your authurl to port 35357 in your glancerc that
you can use glance index without passing in the auth key.
On Oct 9, 2011, at 5:45 PM, Jae Sang Lee wrote:
> Hi,
>
> This is my glance and nova-client rc. Change User, Key value for your
> configuration.
>
> glancerc:
anything destined to 169.254.169.254/32
> port 80 to 10.0.254.6:8773. But that isn't happening even with telnet. Does
> the nova-compute-PREROUTING rule have a part in this? The configuration I've
> done is just running "iptables -A PREROUTING -d 169.254.169.254/32 -p
> [0.183386] Freeing unused kernel memory: 308k freed
> [0.184074] Freeing unused kernel memory: 1612k freed
> mountall: Disconnected from Plymouth
>
>
> Both of them are assigned IPs for the configured nova-network in the
> "euca-describe-instances
tenant == project in nova
tenant == account in swift
We are hoping to rename all of the project_id to tenant_id eventually to make
it simpler, but you should think of them as exactly the same.
Vish
On Sep 30, 2011, at 2:51 AM, l jv wrote:
> Hi:
> There is something confuse.
> Origina
They were removed because they no longer worked correctly and they were based
on twisted code. There is no current plan to replace them. Rather than
generating graphs via internal software, it makes more sense to write very
simple plugins for external monitoring services like munin.
Example u
Hi Carlo,
Due to keystone changing rapidly around release time, it was not working with
the diablo release. We removed the middleware and moved them into the keystone
project, so that when keystone is ready it can include the middleware for all
of the projects. So the ToToken middleware shoul
the network host for a 'normal' network will always get the gateway ip, but it
doesn't delete the existing ip. It should also show the original ip if you do:
ip addr show
One thing to keep in mind though, you will need to mark that ip reserved in the
database if don't want it assigned to the vm
If our real goal is scaling the api, It seems like we can scale much more
easily by simply running more copies of nova-api and load balancing across
them. Then we don't need any background connection pooling magic. If it
really is limited to issues with eventlet then utils.synchronized might s
Hey everyone,
I'm a bit concerned with the connection pooling in the db. It seems that
things are not getting cleaned up properly. I have a repro-case that causes
failures that we have seen before. if I revert the
nova/db/sqlalchemy/session.py to before the eventlet db pool was added I get n
It looks like you need to update python-novaclient to a newer version.
Nova depends on python-novaclient for some tests, but it is shipped separately.
Vish
On Sep 25, 2011, at 3:48 AM, Thomas Goirand wrote:
> Hi,
>
> During the build process, I could see:
> test_add_image_with_image_data_as_fi
looks like there is a typo on that line:
https://github.com/openstack/keystone/blob/master/keystone/middleware/ec2_token.py#L71
should be keystone_ec2_url
(note the 2 instead of 1
On Sep 24, 2011, at 1:44 AM, KoDer wrote:
> Hi, all.
>
> I install Diablo using nova.sh script and next documentati
Hey Nova-Core,
A couple of apologies:
1) Sorry about not communicating more about the Gerrit move. Somehow I assumed
that everyone already knew we were moving as soon as diablo was finalized, but
I never made an official announcement. I will try to stay on top of these
things in the future.
it helps other n00bs like myself.
>
> -S
>
>
> From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
> [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf
> of Mark McLoughlin [mar...@redhat.com
Hey Everyone,
Now that we've cut the Diablo release, we are moving Nova code hosting over to
Github and reviews to Gerrit. Gerrit is new for those of you who haven't been
contributing to the other projects that have already moved. You can find a set
of instructions for getting up and running
It works fine in a virtual machine. You should set:
--libvirt_type=qemu
so that it uses software virtualization. Note that the guests will be very slow.
Vish
On Sep 19, 2011, at 12:52 AM, Khaled Ben Bahri wrote:
> Hi all,
>
> I am a novice in utilization of openstack, i want to install it on
I have tried it with vlan mode. It works fine. Getting the metadata server to
work is a little challenging, as it seems that syns that come in via one
interface can't be acked through a different interface. You might have to do
some tricky routing to get it to work. In my last deployment, i
+1
On Sep 15, 2011, at 2:13 PM, Brian Waldon wrote:
> Chris (comstud) has been a great help with reviews lately and has quite a bit
> of knowledge of the system overall. I think he would add a great amount to
> the team, so I'm proposing we add him to nova-core.
>
> Brian Waldon
>
>
>
>
Diablo will still support old style auth. Essex will not.
Vish
On Sep 15, 2011, at 3:00 AM, Day, Phil wrote:
>> Looks pretty good. It's worth mentioning that some (many?) of the
>> tables that deal with Identity information are being removed because
>> they duplicate data in Keystone. So, table
Looks like the version of nova that is installed in pymodules is old. You
somehow have a new api-paste.ini but old actual nova code.
Vish
On Sep 12, 2011, at 10:27 AM, Marc Peiser wrote:
> Hi all,
>
> I'm having issues with keystone install with nova/glance. I seem to be
> missing something
t; Regards,
> Kei
>
>
> 差出人: openstack-bounces+masumotok=nttdata.co...@lists.launchpad.net
> [openstack-bounces+masumotok=nttdata.co...@lists.launchpad.net] は Vishvananda
> Ishaya [vishvana...@gmail.com] の代理
> 送信日時: 2011年9月9日 6:12
> 宛先: Ale
On Sep 6, 2011, at 9:57 AM, Alex Lyakas wrote:
> Greetings everybody,
> I have been reading the nova code (pretty close to the latest version) and I
> have a couple of questions regarding it.
>
> Live migration:
> I see that VIR_MIGRATE_NON_SHARED_INC flag is used, meaning that at
> destinati
On Sep 8, 2011, at 2:27 AM, Chris Behrens wrote:
>
> I say this for future decisions. At the moment, Gerrit is what was chosen
> and I'm just interested in seeing if we can alleviate some of the pain my
> team is having working with it.
>
I still believe that we can get the best of all world
>
> Can you elaborate on this? Both methods resize the disk, how does the
> second method impose more limitations than the first?
In the first case it is perfectly reasonable to have a whole disk image that is
of a decent size for the base image, so you can get by just fine with the
secondary
Hey guys,
We have a very annoying discrepancy between how local space is used in the xen
driver vs the libvirt driver. I think it is vital that this is rectified
before the Diablo release. We already have a few functional gaps between the
drivers, but the fact that disks are partitioned compl
Hey Everyone,
We managed to get a lot of features in for Diablo-4, and a few have gone in
afterwards. There are still a few that I would like to see land:
https://code.launchpad.net/~cbehrens/nova/rpc-kombu/+merge/73096
(fixes a number of bugs with rpc, leaves the carrot code in place so we can
ion?
Haven't solved this yet. It may have to be a manual process or external tool.
Access and secret keys are stored in keystone with the new code, so it will
have to get the data and then generate the creds.
> 3. Are the changes you mentioned in the Nova trunk already?
Yes
>
This is correct. Well, they are still there, but marked deprecated. One can
still use the old user and project system by using the --use_deprecated_auth
flag and using the modified middleware stack that is commented out in the
default paste.ini file.
Vish
On Aug 30, 2011, at 11:37 AM, Nguye
using two different versions of nova on the different hosts will cause a
problem. 0.9.1 is ancient at this point.
On Aug 30, 2011, at 12:34 AM, Rasika Karunathilaka wrote:
>
> Hi Team,
>
> When I am trying to attach a compute node into Cloud Control node , I am
> getting following error on
With keystone in use, there is no user and project object in nova anymore. So
the only thing that would make sense inside of nova is: delete all resources
associated with a given project_id string.
Vish
On Aug 30, 2011, at 11:11 AM, Nguyen, Liem Manh wrote:
> How is Nova project/user deleti
users/tenants should be managed with keystone. So this would really be in the
purview of the keystone admin api.
On Aug 30, 2011, at 10:20 AM, Nguyen, Liem Manh wrote:
> Hi Glen,
>
> This may be a tangential question, but I don’t see a Nova Admin API to allow
> creation/deletion of projects
Hmm, the _ is installed when nova is imported. I'm nots sure what would make
it get missed. Is it possible you have an old version of nova installed in
your path somewhere that doesn't have an __init__.py that does gettext.install?
from nova import flags and similar lines should be installing
If the instance is going into shutdown, it is having trouble booting for some
reason.
If you check /var/log/libvirt/qemu/instance-.log, you should see an
error message explaining why the image failed to boot. It could be permissions
or a bad kernel, but you should get some info there.
It should be created for you automatically on the network host.
you might need to set ip_forward to 1 in sysctl, but it should be working.
Request failed seems like an odd error, it may be that you are connecting from
the wrong ip somehow so the metadata server can't figure out which metadata t
Hey Ed,
Great idea. I think there are a lot of ways we can go with this. I started
working on a branch called tasks that did something like this. It essentially
allowed you to put every action into a tasks database and you could re-run
tasks that didn't complete properly. It was based on the
I've seen this issue exactly when running openstack in a vm. There is a line
of code in the cloud init script in the ttylinux image which checks its
processor speed and disables generating keys and starting sshd if it is too
low. If you feel comfortable mounting and hacking the image you can d
Inline
On Aug 22, 2011, at 4:59 PM, Jorge Williams 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 that fundamentally the
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 the source tree with non-RST
> documentation, but as you know, reviewing diffs of XML is just about
> makes people want to slit their thr
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. This has been impossible up until now because the canonical spec has
been in the openstack-manuals project.
My s
There was an issue on one version of ubuntu (I think it was natty?), where xen
was using /dev/sd* instead of /dev/xd*. I remember discussion on the mailing
list or a bug about having to have a specific workaround.
On Aug 19, 2011, at 1:42 AM, Thomas Goirand wrote:
> On 08/19/2011 01:31 PM, Isa
On Aug 18, 2011, at 3:45 PM, Somik Behera wrote:
> Hi Vish,
>
> That would be one very reasonable way to do it, but in that case we are
> fragmenting AuthZ in multiple services instead of Keystone taking care of
> AuthZ across all services.
We can't necessarily depend on keystone to keep tra
On Aug 18, 2011, at 2:08 PM, Somik Behera wrote:
>
> 2.2) Quantum needs to ensure Tenant-X( or user with access to Tenant-X)
> owns Virtual Network Interface named "instance-0001-eth0" available in Nova -
> This is where we need AuthZ help from Keystone
It seems simpler to me to have a qu
On Aug 17, 2011, at 5:34 PM, Wayne A. Walls wrote:
> Greetings, Josh!
>
> Just update the bridge in the db, I've done that in the past to get things
> aligned with Xen. Seems to do the trick...
>
> Cheers,
>
> Wayne
>
And in the future you can specify the bridge when you create the networ
uot;/home/ctoteam/nova/nova/exception.py",
> line 124, in wrapped
> (nova.compute.manager): TRACE: raise Error(str(e))
> (nova.compute.manager): TRACE: Error: POST operation failed: xend_post: error
> from xen daemon: (xend.err "(22, 'Invalid argument')")
> (
for the libvirt library
> ii libvirt0 0.9.3-4
> library for interfacing with different virtualization systems
> ii python-libvirt 0.9.3-4
> libvirt Python bindings
> ii qemu-kvm
NBD shouldn't be needed for xen. You probably need to set
--nouse_cow_images
which will stop nova from trying to use qcow2 as the image format.
Vish
On Aug 16, 2011, at 11:06 AM, Joshua Harlow wrote:
> ctoteam@buildingbuild:~$ sudo modprobe nbd
> ctoteam@buildingbuild:~$
>
> Is there supposed
This looks like a bug. It appears that you are using xen through libvirt which
hasn't had a whole lot of testing.
Vish
On Aug 15, 2011, at 7:18 PM, Joshua Harlow wrote:
> Hi all,
>
> Another error that others may have seen:
> Is it supposed to continue even if this fails?
> This is for runnin
t
> readers.get(fileno, noop).cb(fileno)
> File "/home/ctoteam/nova/nova/image/s3.py", line 271, in delayed_create
> raise
> TypeError: exceptions must be old-style classes or derived from
> BaseException, not NoneType
>
> Still not very helpful :-/
> Any ideas
tions must be old-style classes or derived from
> BaseException, not NoneType
>
> Still not very helpful :-/
> Any ideas?
>
> On 8/15/11 4:31 PM, "Vishvananda Ishaya" wrote:
>
> The underlying exception is getting eaten, so it is hard to say what the
> u
neType
>
> Still not very helpful :-/
> Any ideas?
>
> On 8/15/11 4:31 PM, "Vishvananda Ishaya" wrote:
>
> The underlying exception is getting eaten, so it is hard to say what the
> underlying exception was. I just pushed a branch here which should allow
The underlying exception is getting eaten, so it is hard to say what the
underlying exception was. I just pushed a branch here which should allow you
to see the underlying exception that caused the failed upload:
https://code.launchpad.net/~vishvananda/nova/lp827024
If you run that branch you
On Aug 2, 2011, at 4:23 PM, Zed A. Shaw wrote:
> Hi All,
> I'm going to be spending my days for a little while just taking tests
> and source files that haven't been touched in a while and refactoring
> them or cleaning them up.
Awesome. This should be very helpful.
> The first one I picked wa
Due to some hard work over the last few days (lots of thanks to tr3buchet, jk0,
and bcwaldon), we've managed to get all of the known release-blocker bugs fixed
in the milestone proposed branch. If we don't see any big issues crop up, we
should be cutting the milestone tomorrow morning
Please t
501 - 600 of 718 matches
Mail list logo
