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