[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Thanks for the information, Robie. I am assigned to 1317680 as well, so I'll keep your comments in mind. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Oops, looks like I was mistaken. I'm not assigned. I see you cross- linked your comment, so whomever gets assigned should have enough to go on. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Thanks for the information, Robie. I am assigned to 1317680 as well, so I'll keep your comments in mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Oops, looks like I was mistaken. I'm not assigned. I see you cross- linked your comment, so whomever gets assigned should have enough to go on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
The first half of this fix has been landed into trunk. When users specify a stream in the image-stream config setting, Juju will use this to determine which simple stream to sync. By specifying daily, new machines will receive a more up-to-date image thus shortening the time it takes to perform apt-get update/upgrade. The second half which is designed to make OS update behavior configurable is in the works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Note that bug 1317680 may be a potential issue here. If you end up in the situation that you've previously synced the same release from both a daily and a released stream, then an attempt to create a container will be unambiguous and thus fail. In that bug the issue was that the user had manually done it locally. Here, the problem may be that Juju trips itself up by ending up in that situation, if Juju mixes use of released and daily streams. I suppose a wider issue here is that we don't currently have a good answer inside simplestreams for syncing images from multiple streams into the same pool. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
The first half of this fix has been landed into trunk. When users specify a stream in the image-stream config setting, Juju will use this to determine which simple stream to sync. By specifying daily, new machines will receive a more up-to-date image thus shortening the time it takes to perform apt-get update/upgrade. The second half which is designed to make OS update behavior configurable is in the works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Note that bug 1317680 may be a potential issue here. If you end up in the situation that you've previously synced the same release from both a daily and a released stream, then an attempt to create a container will be unambiguous and thus fail. In that bug the issue was that the user had manually done it locally. Here, the problem may be that Juju trips itself up by ending up in that situation, if Juju mixes use of released and daily streams. I suppose a wider issue here is that we don't currently have a good answer inside simplestreams for syncing images from multiple streams into the same pool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Assignee: (unassigned) = Katherine Cox-Buday (cox-katherine-e) ** Changed in: juju-core Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Changed in: juju-core Assignee: (unassigned) = Katherine Cox-Buday (cox-katherine-e) ** Changed in: juju-core Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
The ability to specify a different image stream to allow daily images to be used query simpleastreams images was added in 1.17.2, but this was for cloud nodes started by the provider directly in the cloud, not images fetched by uvt-simplestreams-libvirt as is done when creating a kvm container. We can extend the kvm provisioning component of Juju to also honour the image-stream configuration setting. Additionally, there is now also agreement that we are to introduce configuration settings to disable apt update/upgrade steps at bootstrap, reducing provisioning time even further. ** Changed in: juju-core Milestone: next-stable = 1.21-alpha1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
The ability to specify a different image stream to allow daily images to be used query simpleastreams images was added in 1.17.2, but this was for cloud nodes started by the provider directly in the cloud, not images fetched by uvt-simplestreams-libvirt as is done when creating a kvm container. We can extend the kvm provisioning component of Juju to also honour the image-stream configuration setting. Additionally, there is now also agreement that we are to introduce configuration settings to disable apt update/upgrade steps at bootstrap, reducing provisioning time even further. ** Changed in: juju-core Milestone: next-stable = 1.21-alpha1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
looks like part of the problem was that we were running with constraints on cpu greater then the level1 KVM had allocated to it. base KVM had 1 cpu, juju was asking for three: juju add-machine --constraints mem=3G root-disk=20G cpu-cores=3 if we modify the base KVM to have 3 cpus the time drops from 13.5 miutes to 4.5 minutes. Adding cache='unsafe' further reduces the time down to 3 minutes. That said, I still think we need to have an option to tell juju to pull the latest daily images in order to reduce the number of updates applied via cloudinit. uvt-simplestreams-libvirt --verbose sync --source http://cloud- images.ubuntu.com/daily release=precise arch=amd64 ^^ This would be the uvtool cmdline to sync the latest daily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
So it looks like this should be reclassified against juju again? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
using latest dailies images and/or hacking juju to not blindly issue apt-get update/upgrade is something i often to do safe a minute per unit (x100s). its also the only way to get kernel updates sans rebooting a machine post deploy. a daily should get us to the same place as the last release plus upgrades, however it does not get qa'd by the cloud images team. On Thu, May 29, 2014 at 11:33 AM, Serge Hallyn 1322...@bugs.launchpad.net wrote: So it looks like this should be reclassified against juju again? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Actually the first two suggestions in comment #23 seem perfectly valid against juju - do not overprovision, at least, and perhaps, conditionally, use cache=unsafe. I would assume that in a developer situation, if power is lost during a juju deploy, all vms would get wiped and the charms re-deployed from scratch anyway. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Ok, then it sounds like the bug should be either invalid or wontfix - be it against qemu or juju. Probably both, since it is the case for both. As I've been repeatedly told, nested qemu (especially on intel) is a convenience/developer feature, and all but unsupported upstream. So we either need to take it upon ourselves to move resources to address it ourselves (as much as possible), or accept facts as they are when designing on top of it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
cache=unsafe only helps a litte. we either need to support daily or more frequent images by default, mainly to avoid the cost of kernel updates or support a feature in juju to allow us to configure what images we want to pull. as a side note, I am happy to get ride of nested kvm if we can get all Openstack services running in containers. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Quoting Daniel Westervelt (daniel.westerv...@canonical.com): cache=unsafe only helps a litte. In comment #23 you said it brought the time from 4.5 to 3 minutes, a 33% improvement. we either need to support daily or more frequent images by default, mainly to avoid the cost of kernel updates or support a feature in juju to allow us to configure what images we want to pull. That still all falls under the purvue of juju. All I am pointing out is that the bug should be marked affecting juju. as a side note, I am happy to get ride of nested kvm if we can get all Openstack services running in containers. One step in this direction would be if we could use mountlo, which is fuse-based, in a container. I haven't had a chance to test it, but it is packaged and in theory it should work. But that is unrelated to the fact that this bug's status against qemu is either invalid (upstream) or wontfix (ubuntu package). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Package changed: qemu (Ubuntu) = juju-core (Ubuntu) ** Changed in: juju-core (Ubuntu) Assignee: Canonical Server Team (canonical-server) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided = High ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Milestone: None = next-stable -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
looks like part of the problem was that we were running with constraints on cpu greater then the level1 KVM had allocated to it. base KVM had 1 cpu, juju was asking for three: juju add-machine --constraints mem=3G root-disk=20G cpu-cores=3 if we modify the base KVM to have 3 cpus the time drops from 13.5 miutes to 4.5 minutes. Adding cache='unsafe' further reduces the time down to 3 minutes. That said, I still think we need to have an option to tell juju to pull the latest daily images in order to reduce the number of updates applied via cloudinit. uvt-simplestreams-libvirt --verbose sync --source http://cloud- images.ubuntu.com/daily release=precise arch=amd64 ^^ This would be the uvtool cmdline to sync the latest daily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
So it looks like this should be reclassified against juju again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
using latest dailies images and/or hacking juju to not blindly issue apt-get update/upgrade is something i often to do safe a minute per unit (x100s). its also the only way to get kernel updates sans rebooting a machine post deploy. a daily should get us to the same place as the last release plus upgrades, however it does not get qa'd by the cloud images team. On Thu, May 29, 2014 at 11:33 AM, Serge Hallyn 1322...@bugs.launchpad.net wrote: So it looks like this should be reclassified against juju again? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Actually the first two suggestions in comment #23 seem perfectly valid against juju - do not overprovision, at least, and perhaps, conditionally, use cache=unsafe. I would assume that in a developer situation, if power is lost during a juju deploy, all vms would get wiped and the charms re-deployed from scratch anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Ok, then it sounds like the bug should be either invalid or wontfix - be it against qemu or juju. Probably both, since it is the case for both. As I've been repeatedly told, nested qemu (especially on intel) is a convenience/developer feature, and all but unsupported upstream. So we either need to take it upon ourselves to move resources to address it ourselves (as much as possible), or accept facts as they are when designing on top of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
cache=unsafe only helps a litte. we either need to support daily or more frequent images by default, mainly to avoid the cost of kernel updates or support a feature in juju to allow us to configure what images we want to pull. as a side note, I am happy to get ride of nested kvm if we can get all Openstack services running in containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Quoting Daniel Westervelt (daniel.westerv...@canonical.com): cache=unsafe only helps a litte. In comment #23 you said it brought the time from 4.5 to 3 minutes, a 33% improvement. we either need to support daily or more frequent images by default, mainly to avoid the cost of kernel updates or support a feature in juju to allow us to configure what images we want to pull. That still all falls under the purvue of juju. All I am pointing out is that the bug should be marked affecting juju. as a side note, I am happy to get ride of nested kvm if we can get all Openstack services running in containers. One step in this direction would be if we could use mountlo, which is fuse-based, in a container. I haven't had a chance to test it, but it is packaged and in theory it should work. But that is unrelated to the fact that this bug's status against qemu is either invalid (upstream) or wontfix (ubuntu package). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Package changed: qemu (Ubuntu) = juju-core (Ubuntu) ** Changed in: juju-core (Ubuntu) Assignee: Canonical Server Team (canonical-server) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided = High ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Milestone: None = next-stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Reproducer steps: Create a trusty virtual machine using the defaults provided with uvt tool. ssh into that virtual machine and setup juju environments.yaml to be a local provider with a container-type: kvm juju bootstrap juju add-machine -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
environments.yaml: default: local environments: local: type: local container: kvm lxc-use-clone: true -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
It takes 164 seconds in cloud init to bring up the first machine. What's the outer VM config (resources), likewise, what's the host machine resource level? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Summary
---
Add-machine: Wed May 28 14:31:56 UTC 2014 (0)
KVM Ssh'able:Wed May 28 14:33:15 UTC 2014 (+79)
Cloud-init done: Wed May 28 14:35:14 UTC 2014 (+119)
Juju status started: Wed May 28 14:35:38 UTC 2014 (+24)
Total time: 222 seconds: 3 min, 40 seconds.
ubuntu@kvmjuju:~$ date; juju add-machine --constraints cpu-cores=4
root-disk=20G
Wed May 28 14:31:56 UTC 2014
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:32:02 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
instance-id: pending
series: trusty
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:32:24 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ juju ssh 5 date
ERROR machine 5 has no public address
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:33:15 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:34:36 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:14 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:19 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:21 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:23 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:38 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: started
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1322302
Title:
local provider is very slow to tranistion from agent-status: pending
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
One modification to the outer KVM that may help here: adding --unsafe-cache to your first level KVM will use host ram to cache guest writes to the qcow2 image -- this means what it means, if kill your VMs or host machine has power failure, you'll lose data.With that in place the same test resulted in add-machine to status: started of: 149 seconds. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
A note from the juju side of the fence - Juju currently just syncs the latest released image when calling uvt-simplestreams-libvirt. It could be configured to add a --source arg to get a daily image if required. But configuration adds complexity so if the released kvm images were updated more often, I guess that would be preferable. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
environments.yaml: default: local environments: local: type: local container: kvm lxc-use-clone: true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Reproducer steps: Create a trusty virtual machine using the defaults provided with uvt tool. ssh into that virtual machine and setup juju environments.yaml to be a local provider with a container-type: kvm juju bootstrap juju add-machine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
It takes 164 seconds in cloud init to bring up the first machine. What's the outer VM config (resources), likewise, what's the host machine resource level? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Summary
---
Add-machine: Wed May 28 14:31:56 UTC 2014 (0)
KVM Ssh'able:Wed May 28 14:33:15 UTC 2014 (+79)
Cloud-init done: Wed May 28 14:35:14 UTC 2014 (+119)
Juju status started: Wed May 28 14:35:38 UTC 2014 (+24)
Total time: 222 seconds: 3 min, 40 seconds.
ubuntu@kvmjuju:~$ date; juju add-machine --constraints cpu-cores=4
root-disk=20G
Wed May 28 14:31:56 UTC 2014
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:32:02 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
instance-id: pending
series: trusty
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:32:24 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ juju ssh 5 date
ERROR machine 5 has no public address
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:33:15 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:34:36 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: pending
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:14 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:19 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:21 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:23 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$ date; juju status
Wed May 28 14:35:38 UTC 2014
environment: local
machines:
0:
agent-state: started
agent-version: 1.18.3.1
dns-name: localhost
instance-id: localhost
series: trusty
5:
agent-state: started
agent-version: 1.18.3.1
dns-name: 10.0.3.67
instance-id: ubuntu-local-machine-5
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=512M root-disk=20480M
services: {}
ubuntu@kvmjuju:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322302
Title:
local provider is very slow to tranistion from agent-status: pending
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
One modification to the outer KVM that may help here: adding --unsafe-cache to your first level KVM will use host ram to cache guest writes to the qcow2 image -- this means what it means, if kill your VMs or host machine has power failure, you'll lose data.With that in place the same test resulted in add-machine to status: started of: 149 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
A note from the juju side of the fence - Juju currently just syncs the latest released image when calling uvt-simplestreams-libvirt. It could be configured to add a --source arg to get a daily image if required. But configuration adds complexity so if the released kvm images were updated more often, I guess that would be preferable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
I think investigation needs to start from a qemu performance perspective. It may be that uvtool needs to tell libvirt to tell qemu to do something differently, but in that case I need to know what. ** Project changed: uvtool = qemu ** Project changed: qemu = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Can someone show the actual dpkg term log to show how much needed upgrading? Can you confirm that kvm is being run with acceleration? Since you're using uvtool I assume you're also using a qcow2, which further degrades performance... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
I think investigation needs to start from a qemu performance perspective. It may be that uvtool needs to tell libvirt to tell qemu to do something differently, but in that case I need to know what. ** Project changed: uvtool = qemu ** Project changed: qemu = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322302] Re: local provider is very slow to tranistion from agent-status: pending
Can someone show the actual dpkg term log to show how much needed upgrading? Can you confirm that kvm is being run with acceleration? Since you're using uvtool I assume you're also using a qcow2, which further degrades performance... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322302 Title: local provider is very slow to tranistion from agent-status: pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
