<div dir="ltr"><div><div><br><br><br>On Tue, May 6, 2014 at 10:34 AM, Sam Kottler <<a href="mailto:s@shk.io">s@shk.io</a>> wrote:<br>><br>><br>> On 5/6/14, 2:27 PM, Shake Chen wrote:<br>> ><br>> ><br>
> ><br>> > On Tue, May 6, 2014 at 11:16 AM, Sam Kottler <<a href="mailto:s@shk.io">s@shk.io</a><br>> > <mailto:<a href="mailto:s@shk.io">s@shk.io</a>>> wrote:<br>> ><br>> ><br>> > On 5/6/14, 8:10 AM, Shake Chen wrote:<br>
> > > Hi<br>> > ><br>> > > Now the image whether support resize?<br>> > ><br>> > > CentOS can provide rpm<br>> > > for <a href="https://github.com/flegmatik/linux-rootfs-resize">https://github.com/flegmatik/linux-rootfs-resize</a>?<br>
> ><br>> > How is it different from cloud-initramfs-tools? If you're<br>> > interested in<br>> > having included a repo, it seems like EPEL is the right place.<br>> ><br>> > have same feature with cloud-initramfs-tools, let image can been resize.<br>
> ><br>> > now cloud-initramfs-tools only in Fedora, I hope can include in EPEL repo.<br>><br>> Nope, it's also included in EPEL 6 [1]. It's not available for EL5 via<br>> EPEL, though.<br><br>
</div>That's because there's no easy way to customize an initrd in CentOS/RHEL5. And nobody asked for it yet :-)<br><br></div>...Juerg<br><br><div><div><br>><br>> 1. <a href="https://admin.fedoraproject.org/pkgdb/acls/name/cloud-initramfs-tools">https://admin.fedoraproject.org/pkgdb/acls/name/cloud-initramfs-tools</a><br>
> ><br>> > I think the cloud image need include Cloud-init，cloud-utils and<br>> > cloud-initramfs-tools.<br>> ><br>> ><br>> ><br>> > ><br>> > ><br>> > ><br>
> > ><br>> > > On Tue, May 6, 2014 at 1:32 AM, Sam Kottler <<a href="mailto:s@shk.io">s@shk.io</a><br>> > <mailto:<a href="mailto:s@shk.io">s@shk.io</a>><br>> > > <mailto:<a href="mailto:s@shk.io">s@shk.io</a> <mailto:<a href="mailto:s@shk.io">s@shk.io</a>>>> wrote:<br>
> > ><br>> > ><br>> > > On 5/5/14, 11:31 PM, Juerg Haefliger wrote:<br>> > > ><br>> > > ><br>> > > ><br>> > > > On Mon, May 5, 2014 at 7:24 PM, Sam Kottler <<a href="mailto:s@shk.io">s@shk.io</a><br>
> > <mailto:<a href="mailto:s@shk.io">s@shk.io</a>><br>> > > <mailto:<a href="mailto:s@shk.io">s@shk.io</a> <mailto:<a href="mailto:s@shk.io">s@shk.io</a>>><br>> > > > <mailto:<a href="mailto:s@shk.io">s@shk.io</a> <mailto:<a href="mailto:s@shk.io">s@shk.io</a>> <mailto:<a href="mailto:s@shk.io">s@shk.io</a><br>
> > <mailto:<a href="mailto:s@shk.io">s@shk.io</a>>>>> wrote:<br>> > > > ><br>> > > > > During the cloud instance SIG meeting today we talked about<br>> > > future plans<br>
> > > > > for cloud-init in CentOS. Right now cloud-init is included as<br>> > > part of<br>> > > > > EPEL and that's where most CentOS users consume it from. The<br>
> > > problem is<br>> > > > > that cloud-init and related bits are critical for building<br>> > > images to run<br>> > > > > on a public or private cloud, and we need to build early guest<br>
> > > > > initialization tools into the cloud images we produce. Ideally<br>> > > this does<br>> > > > > not include adding EPEL or packages from EPEL which have not<br>> > been<br>
> > > > > rebuilt in our build systems.<br>> > > > ><br>> > > > > So, the proposal that there's general consensus upon within<br>> > > the SIG is<br>
> > > > > to maintain cloud-init, its dependencies, and any related<br>> > > packages on<br>> > > > > <a href="http://git.centos.org">git.centos.org</a> <<a href="http://git.centos.org">http://git.centos.org</a>><br>
> > <<a href="http://git.centos.org">http://git.centos.org</a>> <<a href="http://git.centos.org">http://git.centos.org</a>><br>> > > and rebuild them ourselves.<br>> > > > I'm one of the maintainers in<br>
> > > > > EPEL so I offered to maintain the git repos for CentOS, anyone<br>> > > else who<br>> > > > > would like to be involved in more than welcome to step up.<br>> > > ><br>
> > > > I'm the EPEL maintainer of cloud-utils and<br>> > cloud-initramfs-tools and<br>> > > > I'm willing to maintain those packages and their dependencies for<br>> > > > CentOS with the goal to keep them in sync.<br>
> > ><br>> > > Awesome, thanks!<br>> > ><br>> > > ><br>> > > > ...Juerg<br>> > > ><br>> > > > > Thoughts, questions, concerns?<br>
> > > > ><br>> > > > > -s<br>> > > > > _______________________________________________<br>> > > > > CentOS-devel mailing list<br>> > > > > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>
> > <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>>><br>> > > <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>
> > <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>>>><br>> > > > > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> > > ><br>> > > ><br>> > > ><br>> > > > _______________________________________________<br>> > > > CentOS-devel mailing list<br>> > > > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>
> > <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>>><br>> > > > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> > ><br>> > > _______________________________________________<br>> > > CentOS-devel mailing list<br>> > > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>
> > <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>>><br>> > > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> > ><br>> > ><br>> > ><br>> > ><br>> > > --<br>> > > Shake Chen<br>> > ><br>> > ><br>> > ><br>> > > _______________________________________________<br>
> > > CentOS-devel mailing list<br>> > > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>
> > > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>> ><br>> > _______________________________________________<br>
> > CentOS-devel mailing list<br>> > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a> <mailto:<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>><br>> > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
> ><br>> ><br>> ><br>> ><br>> > --<br>> > Shake Chen<br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > CentOS-devel mailing list<br>
> > <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>> > <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>><br>
> _______________________________________________<br>> CentOS-devel mailing list<br>> <a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>> <a href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
<br></div></div></div>