Nova has two specs approved for Queens for filtering instance actions
and migrations by the 'changes-since' filter, which filters on the
updated_at field.
https://review.openstack.org/#/c/507762/
https://review.openstack.org/#/c/506030/
Those APIs don't take a sort key like the servers API do
The qcow2 checksums are correct. They run via nova.
I seem to recall that the cinder checksum calculation when reading in an
image is faulty. I'm simply going to remove the offending code.
-Chris
- Christopher T. Hull
My contract at NASA has ended and I am seeking new opportunities.
For update
Hi All,
I’m running into an issue with a new Ocata deployment. I’m unable to boot
an instance directly from the provider network. Instance logs show that it
keeps repeating “failed to raise interfaces” so it doesn’t get an IP
assigned, and then can’t reach the metatdata servers.
Booting an in
HI guys;
This used to work. Trying to come up with an update / backup strategy
here. Successfully created an image from a volume (must do as admin it
seems, but that's not an issue.) The image runs just fine as an instance
(creates it's root drive on the controller/cumpute node).
But when I tr
Hey all,
Now that we're finishing up the last few bits of v2.0 removal, I'd like
to send out a reminder that *Queens* will not include the *v2.0 keystone
APIs* except the ec2-api. Authentication and validation of v2.0 tokens
has been removed (in addition to the public and admin APIs) after a
lengt
Hello,
I have been trying to modify my ceilometer setup in order to include hardware
measurement but have not been able to do so. Looking into the logs there are a
lot of errors like this:
2017-10-19 12:09:46.467 30274 ERROR ceilometer.agent.manager NoMatches: No
'ceilometer.hardware.inspect
