hi Guys, As we get ready to start publishing Cloud Images ( or rather images consumable in various virt platforms, including public and private clouds ) - it would be great to have a baseline package manifest worked out. What / how many images should we build. At this time we were thinking of doing : - CentOS-5 32bit minimal - CentOS-6 32bit minimal - CentOS-5 64bit minimal - CentOS-6 64bit minimal - CentOS-5 64bit LAMP - CentOS-6 64bit LAMP What would be the minimal functional requirements people would expect from these images ? and what rpms should be installed ? Should root login be enabled or should we require people to go in via a 'centos' user. Should the image be self-updating, or should we have a post-login message that indicates outstanding updates ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc
On 03.10.2012 17:29, Karanbir Singh wrote:> hi Guys, > > As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest > worked > out. > > What / how many images should we build. At this time we were thinking > of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMP > > What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ? Should root > login be enabled or should we require people to go in via a 'centos' > user. Should the image be self-updating, or should we have a > post-login > message that indicates outstanding updates ?Hi, Since I've already been messing with such images I kind of know what I need: 1 - acpid, so virsh reboot/shutdown will work 2 - cloud-init for openstack images; also it would be nice if the image could resize itself at first boot 3 - nano & wget to make the life easier for newbies I don't think it's worth the effort to build Centos LAMP images, since it's just Centos minimal + "yum install httpd mysql-server php-mysql etc". -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
could these be used as vagrant base boxes? On Oct 3, 2012, at 12:29 PM, Karanbir Singh <mail-lists at karan.org> wrote:> hi Guys, > > As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out. > > What / how many images should we build. At this time we were thinking of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMP > > What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ? Should root > login be enabled or should we require people to go in via a 'centos' > user. Should the image be self-updating, or should we have a post-login > message that indicates outstanding updates ? > > > > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax > GnuPG Key : http://www.karan.org/publickey.asc > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt
On Wed, 2012-10-03 at 17:29 +0100, Karanbir Singh wrote:> hi Guys, > > As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out. > > What / how many images should we build. At this time we were thinking of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMP > > What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ? Should root > login be enabled or should we require people to go in via a 'centos' > user. Should the image be self-updating, or should we have a post-login > message that indicates outstanding updates ?Are you using existing RPMs or creating new ones with stripped dependencies? What advantages will these images have over a kickstart install from a local repo?
On 10/03/2012 05:29 PM, Karanbir Singh wrote:> As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out.and.. thoughts on Selinux ? Disable it ? Enable it ? Or should we just leave it in Permissive mode, along with a bit of text on howto enable it for people who want it ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc
On Wed, Oct 3, 2012 at 12:29 PM, Karanbir Singh <mail-lists at karan.org> wrote:> hi Guys, > > As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out. > > What / how many images should we build. At this time we were thinking of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMPFunny you should ask!! I'm on an open source project that does precisely this. It depends heavily on whether you're using standard packages from CentOS itself, or whether you use Perl modules, Nagios, NRPE, or other tools such as git or puppet that are not in the bae upstream packages from the upstream vendor. So a base LAMP install for me would absolutely contain epel-release, installed by hook or by crook, and the rpmforge-release package with /etc/yum.repos.d/rpmforge.repo disabled by default. It would also include postfix, rather than sendmail, for ease of management, and would include emacs and xorg-x11-xauth to allow X based Emacs sessions, which are often more useful than pure screen sessions, and I'd actually consider installing firefox in order to be able to run a remote web browser and see what shows up on the server itself. That's incredibly useful when people are doing.... odd things to firewalls and you want to make sure it's actually displaying content. "curl" as well as wget is very useful. So is "lynx", for text based web checking, and the tools for whatever source control you feel useful, especially including the 'rcs' package for local file management. (That was invaluable today, as I was manipulating /etc/sysconfig/network-scripts files for funky network setups.)> What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ? Should root > login be enabled or should we require people to go in via a 'centos' > user. Should the image be self-updating, or should we have a post-login > message that indicates outstanding updates ?Root should be disabled, if feasible. I'm afraid that many sites don't handle such passwords well. Local user management can be awkward. Ask sometime about Kerberos authentication and local account management, I've got a lot of recent experience with these and Centrify's AD based account management. The Nagios "check-updates" plugin is priceless for notifying a central NOC of required updates: rather than self updating. Post install scripting, or system management, to set the 'root' alias is critical. Again, ask about that if curious: handling Postfix based smarthost setups, but making sure cron jobs for 'root' go to the right external email address, is a bit of an advenure.> > -- > Karanbir Singh > +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh > ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax > GnuPG Key : http://www.karan.org/publickey.asc > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt
On 10/03/2012 06:29 PM, Karanbir Singh wrote:> hi Guys, > > As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out. > > What / how many images should we build. At this time we were thinking of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMP > > What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ? Should root > login be enabled or should we require people to go in via a 'centos' > user. Should the image be self-updating, or should we have a post-login > message that indicates outstanding updates ?Have you considered equipping these with cloud-init? While i don't have any practical experience with myself yet it should allow to build a minimal image yet allow the creation cutomized flavors for users. The problem I see is that the moment you include say vim-enhanced instead of emacs or postfix instead of sendmail you'll get into a political fight. The only way I see is to make the minimal images truly as minimal as possible and then allow people to pull in stuff using cloud-init (or alternative mechanisms). Regards, Dennis
On Wed, Oct 3, 2012 at 9:59 PM, Karanbir Singh <mail-lists at karan.org> wrote:> As we get ready to start publishing Cloud Images ( or rather images > consumable in various virt platforms, including public and private > clouds ) - it would be great to have a baseline package manifest worked > out.Nice to have.> What / how many images should we build. At this time we were thinking of > doing : > > - CentOS-5 32bit minimal > - CentOS-6 32bit minimal > > - CentOS-5 64bit minimal > - CentOS-6 64bit minimal > > - CentOS-5 64bit LAMP > - CentOS-6 64bit LAMPA good starting point. I have been doing something similar - create a bunch of image templates At present, we have 1. A portable desktop appliance - basically a LXDE desktop install that can be dd'd onto a 4GB pen drive. 2. Min. server with ssh and ntp enabled. 3. LAMP (PHP, Python, MySQL, postgreSQL) for web development platform. 4. Desktop KDE with KDM supporting XDMCP for a quick demo of remote desktop 5. Desktop with Qt SDK 6. Desktop with GTK SDK 7. Server with postfix+dovecot+roundcube for email server deployment 8. DB server (MySQL, postgreSQL) for production deployment. The above is in a mix of CentOS, Debian, and Ubuntu base. Whenever anyone needs a pristine base, I copy the appropriate image file, boot it with virt-manager, change the network parameters, hostname etc. and hand it over to the developer/sysadmin.> What would be the minimal functional requirements people would expect > from these images ? and what rpms should be installed ?Take a look at the turnkeylinux.org appliances to see what others are doing.> Should root > login be enabled or should we require people to go in via a 'centos' > user.I vote for the sudo approach. One can always do "sudo su -" as that user and would be equivalent to ssh root at somehost.> Should the image be self-updating, or should we have a post-login > message that indicates outstanding updates ?I vote for a post login message. The VM sysadmin has more control. Keep us posted on the progress. -- Arun Khan
Hi Guys, Hoping to publish some testing images today late evening ( UTC ) - the targets I hope to hit are : - CentOS-6/32 bit/s3 backed - CentOS-6/64 bit/s3 backed - CentOS-6/32 bit/ebs backed - CentOS-6/64 bit/s3 backed - CentOS-5/64 bit/s3 backed - CentOS-5/64 bit/ebs backed ( is there any interest in C-5/32 ? ) Also, whats the best way to publish these images in a way that they can go away once the test-phase is done ( and ideally we really need them to go away ) -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc
On Mon, Oct 15, 2012 at 3:00 AM, Karanbir Singh <mail-lists at karan.org> wrote:> Hi Guys, > > Hoping to publish some testing images today late evening ( UTC ) - the > targets I hope to hit are : > > - CentOS-6/32 bit/s3 backed > - CentOS-6/64 bit/s3 backed > - CentOS-6/32 bit/ebs backed > - CentOS-6/64 bit/s3 backed > > - CentOS-5/64 bit/s3 backed > - CentOS-5/64 bit/ebs backed > > ( is there any interest in C-5/32 ? )Any update on this, please, Karanbir? I'd like to request a virtualbox image as well, if I may, please. Yours, Aleksey