On 07-11-16 17:42:02, Lee Yarwood wrote:
> Hello all,
>
> The following bug was recently discovered where encrypted volumes
> created prior to Newton use a slightly mangled passphrase :
>
> The passphrase used to encrypt or decrypt volumes was mangled prior to Newton
> https
f you were
present at the previous discussions in Boston!
https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades
Thanks in advance and see you in Denver!
Lee
--
Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
___
On 21-08-17 15:56:53, Lee Yarwood wrote:
> Hello all,
>
> This is a brief announcement to highlight that there will be a skip
> level upgrades room again at the PTG in Denver. I'll be chairing the
> room and have seeded the etherpad below with a few goal and topic ideas.
fline-migration
[3]
https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html
[4]
https://governance.openstack.org/tc/reference/tags/assert_supports-accessible-upgrade.html
[5]
https://github.com/NguyenHoaiNam/Jump-Over-Release/blob/test_dynamic_section/README.md
--
Lee Yarwood
ant to reach out to him to help craft the agenda for the
session based on our discussions in Denver.
Thanks again,
Lee
--
Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
___
OpenStack-operators mailing list
OpenSta
pu with
libvirt) etc upgrades that require reboots or instances to be restarted
(either hard or via live-migration). If you're unable or just unwilling
to take downtime for instances that can't be moved when these components
require an update then you have bigger problems IMHO.
Regar
pad, I'd really like to see some
concrete action items finally come from these discussions ahead of R.
Thanks in advance and see you in Dublin!
--
Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
signature.asc
Description: PGP sign
stack.org/nova/latest/cli/nova-status.html
> [3] https://review.openstack.org/#/c/575125/
Cheers,
--
Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
heading off this class of bug by disabling it for non-cinder
> callers.
I'm definitely in favor of hiding this from users eventually but
wouldn't this require some form of deprecation cycle?
Warnings within the API documentation would also be useful and even
something we could backpor
being used?
Is there a specific use case where plain is better than LUKS and thus
needs to stay around?
Thanks in advance,
Lee
--
Lee Yarwood
Senior Software Engineer
Red Hat
PGP : A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
___
OpenStack-oper
10 matches
Mail list logo