~smoser/cloud-init/growroot : changes

~smoser/cloud-init/growroot » Changes from revision 796

From Revision 796 to 777

Rev	Summary	Authors	Date
796	pep8, pylint, make resize_devices return more useful pep8, pylint, make resize_devices return more useful resize_devices now contains what action occurred for each entry.	Scott Moser	11 years ago
795	add doc add doc	Scott Moser	11 years ago
794	change default mode to 'auto' change default mode to 'auto'	Scott Moser	11 years ago
793	remove 'log' passing. call growpart with --dry-run first. remove 'log' passing. call growpart with --dry-run first. growrun --dry-run will exit 1 if it wouldn't do anything. so call it, check for '1' and if no change, then just return.	Scott Moser	11 years ago
792	change default (no 'growpart' in config) to use 'auto' and '... change default (no 'growpart' in config) to use 'auto' and '/'	Scott Moser	11 years ago
791	test of resize, a couple small fixes test of resize, a couple small fixes	Scott Moser	11 years ago
790	add the unit test, fix a few issues add the unit test, fix a few issues	Scott Moser	11 years ago
789	merge from trunk merge from trunk	Scott Moser	11 years ago
788	more work more work	Scott Moser	11 years ago
787	add default log value to get_mount_info add default log value to get_mount_info	Scott Moser	11 years ago
786	initial stab at growpart module initial stab at growpart module	Scott Moser	11 years ago
785	skip unit test due to LP: #1124384 skip unit test due to LP: #1124384	Scott Moser	11 years ago
784	Support resizing btrfs filesystems. Support resizing btrfs filesystems. The existing code has two issues with btrfs: 1) The command to resize a btrfs filesystem uses a path to the mount point, not the underlying device: $ btrfs filesystem resize max /dev/vda1 ERROR: unable to resize '/dev/vda1' - Inappropriate ioctl for device Resize '/dev/vda1' of 'max' $ btrfs filesystem resize max / Resize '/' of 'max' 2) The code that is given a path and finds the ID of the device where the path is mounted doesn't work for btrfs: Use /proc/$$/mountinfo to find the device where path is mounted. This is done because with a btrfs filesystem using os.stat(path) does not return the ID of the device. Here, / has a device of 18 (decimal). $ stat / File: '/' Size: 234 Blocks: 0 IO Block: 4096 directory Device: 12h/18d Inode: 256 Links: 1 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2013-01-13 07:31:04.358011255 +0000 Modify: 2013-01-13 18:48:25.930011255 +0000 Change: 2013-01-13 18:48:25.930011255 +0000 Birth: - Find where / is mounted: $ mount \| grep ' / ' /dev/vda1 on / type btrfs (rw,subvol=@,compress=lzo) And the device ID for /dev/vda1 is not 18: $ ls -l /dev/vda1 brw-rw---- 1 root disk 253, 1 Jan 13 08:29 /dev/vda1 So use /proc/$$/mountinfo to find the device underlying the input path.	Blair Zajac	11 years ago
783	do not reload upstart configuration on upstart jobs do not reload upstart configuration on upstart jobs For now, we disable reloading upstart jobs due to bug 1124384. At some point in the future, we could enable it again when that bug is fixed. The change here allows for a boothook in a multipart input to write the file '/run/cloud-init-upstart-reload' and then have configuration reloaded.	Scott Moser	11 years ago
782	Few patches to make life on Debian 6 stable happier: Few patches to make life on Debian 6 stable happier: * Added arguments to packages/bddeb: -d pass through '-d' to debuild --no-cloud-utils don't depend on cloud-utils package (default: False) These are essential for building on Debian 6, because there are no python-mocker (build dependency) and cloud-utils (install dependency) in squeeze and squeeze-backports. * SysVinit startup scripts modified to run both on RHEL and Debian, * (Unfortunately) New option INIT_SYSTEM=sysvinit_deb for Debian /etc/init.d/ directory * Make separate Ubuntu and Debian APT source template (cc_apt_configure) I'm now generating working Debian 6 package following way: INIT_SYSTEM=sysvinit_deb packages/bddeb -us -uc --no-cloud-utils -d	Vlastimil Holer	11 years ago
781	DataSourceNoCloud: allow setting user-data and meta-data in ... DataSourceNoCloud: allow setting user-data and meta-data in config This allows a single file to declare and activate this data source. This could come from: * cloud-config-url on kernel cmdline * /etc/cloud/cloud.cfg.d * debian preseed of 'cloud-init/local-cloud-config' Also here is * some tests * a small fix to parse_cmdline_data found when writing those tests.	Scott Moser	11 years ago
780	Add initial docs about datasources. Add initial docs about datasources. Start moving the current README for datasources to a RST format and include those files in the rtd site.	harlowja	11 years ago
779	upstart/cloud-init-container.conf: ensure /run/network exist... upstart/cloud-init-container.conf: ensure /run/network exists ifquery will exit failure if there is no /run/network directory. normally that would get created by one of network-interface.conf or networking.conf. But, it is possible that we're running before either of those have.	Scott Moser	11 years ago
778	Changelog: reformat to limit to 80 chars wide Changelog: reformat to limit to 80 chars wide	Scott Moser	11 years ago
777	doc: fix example in cloud-config-write-files.txt doc: fix example in cloud-config-write-files.txt The write_files documentation incorrectly used 'perms' rather than 'permissions'.	Scott Moser	11 years ago

Older »