Re: [openstack-dev] Minimum version of shred in our supported distros?

Hey, On 21.08.2017 02:59, Tony Breeds wrote: On Mon, Aug 21, 2017 at 10:40:31AM +1000, Michael Still wrote: If there's really only one distro which hasn't updated, I'd also be inclined to try and push them to update before they move to Queens. Surely that's a thing we can ask them nicely to

Re: [openstack-dev] Minimum version of shred in our supported distros?

On Mon, Aug 21, 2017 at 10:40:31AM +1000, Michael Still wrote: > If there's really only one distro which hasn't updated, I'd also be > inclined to try and push them to update before they move to Queens. Surely > that's a thing we can ask them nicely to do? It might also be that SLES-11 isn't a

[openstack-dev] [tricircle]stable/pike brach has been created.

Hello, all, Thank you all for the great contribution, stable/pike has been created on Aug.18: https://git.openstack.org/cgit/openstack/tricircle/log/?h=stable/pike Release notes could be found here: https://docs.openstack.org/releasenotes/tricircle/pike.html Best Regards Chaoyi Huang

Re: [openstack-dev] Minimum version of shred in our supported distros?

On 17-08-21 10:20:11, Tony Breeds wrote: > On Sun, Aug 20, 2017 at 03:43:22PM +1000, Michael Still wrote: > > Hi, > > > > nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could > > use shred to zero out volumes efficiently if we could assume that shred > > 8.22 was in all our

Re: [openstack-dev] Minimum version of shred in our supported distros?

If there's really only one distro which hasn't updated, I'd also be inclined to try and push them to update before they move to Queens. Surely that's a thing we can ask them nicely to do? Michael On Mon, Aug 21, 2017 at 10:20 AM, Tony Breeds wrote: > On Sun, Aug 20,

Re: [openstack-dev] Minimum version of shred in our supported distros?

On Sun, Aug 20, 2017 at 03:43:22PM +1000, Michael Still wrote: > Hi, > > nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could > use shred to zero out volumes efficiently if we could assume that shred > 8.22 was in all our downstream distros [1]. shred 8.22 shipped in 2013 [2].

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On Thu, Aug 17, 2017 at 4:13 PM, Steve Baker wrote: > > > On Thu, Aug 17, 2017 at 10:47 AM, Emilien Macchi > wrote: > >> >> > Problem #3: from Ocata to Pike: all container images are >> > uploaded/specified, even for services not deployed >> >

Re: [openstack-dev] [tricircle-North South Networking via Direct Provider Networks]

Also, you can upload a new image with OpenStack client, when horizon service is not running: https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/image.html#image-create Since Nova service is running on RegionOne and RegionTwo, the image should be also uploaded to

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

Hi Chris, thanks for taking this on. Comments inline. On 08/18/2017 01:23 PM, Chris Dent wrote: (I put [api] in the subject tags because this might be of interest to a wider audience that cares about APIs.) Long ago and far away I made this bug:

Re: [openstack-dev] [Nova] On idmapshift deprecation

I'm going to take the general silence on this as permission to remove the idmapshift binary from nova. You're welcome. Michael On Sat, Jul 29, 2017 at 10:09 AM, Michael Still wrote: > Hi. > > I'm working through the process of converting the libvirt driver in Nova > to

Re: [openstack-dev] Minimum version of shred in our supported distros?

Specifically we could do something like this: https://review.openstack.org/#/c/495532 Michael On Sun, Aug 20, 2017 at 3:43 PM, Michael Still wrote: > Hi, > > nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could > use shred to zero out volumes efficiently