Package Details: cloud-init 18.5-3

Git Clone URL: https://aur.archlinux.org/cloud-init.git (read-only)
Package Base: cloud-init
Description: The standard for customising cloud instances
Upstream URL: https://cloud-init.io
Licenses: GPL3
Submitter: Barthalion
Maintainer: Sparadox
Last Packager: Sparadox
Votes: 4
Popularity: 0.281751
First Submitted: 2018-01-06 19:15
Last Updated: 2019-02-12 12:30

Latest Comments

bitfehler commented on 2019-04-15 17:03

Hi,

thanks for maintaining this! I am successfully using a modified version of this package using python3 instead of python2 (removing some obsolete deps along the way): https://gitlab.com/bitfehler/cloud-init/tree/bitfehler/py3 It works well for me on EC2, but of course it is always hard to test all aspects of cloud-init. However, I checked the imports in the cloud-init source code, so I have at least some confidence that the updated dependencies are correct. Could I maybe interest you in testing that and maybe merging those changes into your package? :)

antoinemartin commented on 2019-02-15 12:00

Hello Etienne,

I'm in the process of deploying K8S on OpenStack and currently using a VM image with a outdated version of cloud-init (0.7.7), the one used in https://github.com/hartwork/image-bootstrap.

Sparadox commented on 2019-02-12 11:45

Hello Antoine,

Good catch, thanks a lot for this remark :) I added pkgconf as a build dependency. According to the build logs, this indeed moves systemd files from "/lib/systemd" to "/usr/lib/systemd", which feels much better.

I also noticed that dhclient was required (an exception in the cloud-init logs led me there: https://github.com/cloud-init/cloud-init/blob/ad170db966492e845b9dc23346cc7297e8a99032/cloudinit/net/dhcp.py#L127 , installing dhclient fixes the issue).

I've just made a commit to fix both issues.

Out of curiosity antoine, on which platform are you using cloud-init ? I'm using it on ScaleWay and EC2 and would love to gather a bit of feedback about people using it on other platforms :)

antoinemartin commented on 2019-02-11 13:10

Hello, you need to add pkgconf as dev dependencies. setup.py relies on pkg-config to find the location of the systemd units. The fallbacks (look at pkg_config_read are in /lib/systemd).

In consequence, you need to either sed the default entries or provide pkg-config during the build.

Sparadox commented on 2019-02-07 10:15

Updating this package to the 18.5 version, I'm now the maintainer of this package. Feel free to contact me by e-mail or on IRC (handle: Sparadox on FreeNode).

Shibumi commented on 2018-05-19 19:56

Just want to inform you I will push this package back to community.

City-busz commented on 2018-01-07 21:48

Reported bugs:

https://bugs.archlinux.org/task/53036

https://bugs.archlinux.org/task/54785

https://bugs.archlinux.org/task/54898

https://bugs.archlinux.org/task/54911