Re: [Openstack-operators] State of Juno in Production
Cool, thanks, Jon. I've been following the thread on your scheduling issue on the OpenStack list. I can't see our users hitting that issue, but it's always good to keep in mind. :) On Tue, Feb 17, 2015 at 1:17 PM, Jonathan Proulx j...@jonproulx.com wrote: Recently (4 weeks?) moved from Icehouse to Juno. It was pretty smooth (neutron has been much more well behaved though I know that's not relevant to you). One negative difference I noticed, but haven't really dug into yet since it's not a common pattern here: If I schedule 20 instances in one API call I get conductor timeouts and zero launches. If I make many parallel scheduling calls for 20 instances each response is good and scaling out to several hundred parallel launches is much faster and with out the neutron timeout errors that plagued me since I switched over to quantum in Grizzly. As I said I've not looked deeply at this so it may be a local config issue rather than something systemic with Juno, but if it's an important use case for you be sure to take a good look at it. -Jon On Tue, Feb 17, 2015 at 12:56 PM, Joe Topjian j...@topjian.net wrote: Nice - thanks, Jesse. :) On Tue, Feb 17, 2015 at 10:35 AM, Jesse Keating j...@bluebox.net wrote: On 2/17/15 8:46 AM, Joe Topjian wrote: The only issue I'm aware of is that live snapshotting is disabled. Has anyone re-enabled this and seen issues? What was the procedure to re-enable? We've re-enabled it. Live snapshots take more system resources, which meant I had to dial back down my Rally test to validate how it could perform. To re-enable it, we reverted the upstream commit that disabled it. https://github.com/blueboxgroup/nova/commit/fa3a9208ea366489410b4828bd20a74a571287a6 Once that was clear, and we had an upgraded version of libvirt in place, live snapshots just happened. As for the rest of your mail, we're going from Havana to Juno, and we have neutron, so some of our experience won't necessarily apply to you. -- -jlk ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] State of Juno in Production
Hello, I'm beginning to plan for a Juno upgrade and wanted to get some feedback from anyone else who has gone through the upgrade and has been running Juno in production. The environment that will be upgraded is pretty basic: nova-network, no cells, Keystone v2. We run a RabbitMQ cluster, though, and per other recent discussions, see the same reported issues. The only issue I'm aware of is that live snapshotting is disabled. Has anyone re-enabled this and seen issues? What was the procedure to re-enable? Any other gotchas or significant differences seen from running Icehouse? Thanks, Joe ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] State of Juno in Production
Recently (4 weeks?) moved from Icehouse to Juno. It was pretty smooth (neutron has been much more well behaved though I know that's not relevant to you). One negative difference I noticed, but haven't really dug into yet since it's not a common pattern here: If I schedule 20 instances in one API call I get conductor timeouts and zero launches. If I make many parallel scheduling calls for 20 instances each response is good and scaling out to several hundred parallel launches is much faster and with out the neutron timeout errors that plagued me since I switched over to quantum in Grizzly. As I said I've not looked deeply at this so it may be a local config issue rather than something systemic with Juno, but if it's an important use case for you be sure to take a good look at it. -Jon On Tue, Feb 17, 2015 at 12:56 PM, Joe Topjian j...@topjian.net wrote: Nice - thanks, Jesse. :) On Tue, Feb 17, 2015 at 10:35 AM, Jesse Keating j...@bluebox.net wrote: On 2/17/15 8:46 AM, Joe Topjian wrote: The only issue I'm aware of is that live snapshotting is disabled. Has anyone re-enabled this and seen issues? What was the procedure to re-enable? We've re-enabled it. Live snapshots take more system resources, which meant I had to dial back down my Rally test to validate how it could perform. To re-enable it, we reverted the upstream commit that disabled it. https://github.com/blueboxgroup/nova/commit/fa3a9208ea366489410b4828bd20a74a571287a6 Once that was clear, and we had an upgraded version of libvirt in place, live snapshots just happened. As for the rest of your mail, we're going from Havana to Juno, and we have neutron, so some of our experience won't necessarily apply to you. -- -jlk ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
