[Bug 1578833] Re: pollinate should not run in containers and only for first boot

2016-05-06 Thread Dustin Kirkland 
** Description changed: Booting a xenial cloud image in lxd shows that pollinate by far is the biggest bottleneck: $ systemd-analyze blame - 2.756s pollinate.service -656ms cloud-init-local.service -598ms cloud-init.service -509ms cloud-config.service -393ms

[Bug 1579130] Re: need to support systemd.link renaming of devices in container

2016-05-06 Thread Scott Moser
** Description changed: We're interested in supporting network configuration of lxc containers via maas/cloud-init yaml format. The end goal is to do: $ lxc init xenial x1 # enter into container and modify /var/lib/cloud/seed/nocloud-net/network-config # to have something like:

[Bug 1578833] Re: pollinate should not run in containers and only for first boot

2016-05-06 Thread Dustin Kirkland 
** Changed in: pollinate (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1578833 Title: pollinate should not run in

[Bug 1578833] Re: pollinate should not run in containers and only for first boot

2016-05-06 Thread Dustin Kirkland 
** Changed in: pollinate (Ubuntu Xenial) Milestone: None => xenial-updates -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1578833 Title: pollinate should not run in